Reply to topic

Plasma 5 - Could not mount the following device

User avatar vylaern
Registered Member
Posts
157
Karma
0
PostWysłany: Sob Lut 13, 2016 9:01 pm Temat postu: KDE Plasma 5 - problem with mount - polkit? Zgłoś tę wiadomość Odpowiedz z cytatem Zmień/Usuń ten post
Hi,

After an update into Plasma 5 I cannot mount eg. sd-card in my card reader
Could not mount the following device...
before that in KDE4 I had a question for a root password and I could use it, now is no such options.

What should I do to fix it?
luebking
Karma
0
Either your system cannot talk to the polkit daemon (cause it's not running?) or policykit is configured to deny such requests.
The latter would be odd, but the question "why is there no authentication question" cannot be answered - you need to describe your installation (it's gentoo?) in every detailed aspect.

I assume you're not using systemd/logind? do you have udisks (running) and is the KDE session started via ck-launch-session? and there are many more aspects to this
User avatar vylaern
Registered Member
Posts
157
Karma
0
luebking wrote:Either your system cannot talk to the polkit daemon (cause it's not running?) or policykit is configured to deny such requests.
The latter would be odd, but the question "why is there no authentication question" cannot be answered - you need to describe your installation (it's gentoo?) in every detailed aspect.

I assume you're not using systemd/logind? do you have udisks (running) and is the KDE session started via ck-launch-session? and there are many more aspects to this


Many thanks for the answer. I use Gentoo.
"why is there no authentication question"

I am not sure what are default settings for Gentoo, maybe no access at all?
I used to fix it manually through:
/usr/share/polkit-1/actions/org.freedesktop.udisks.policy
but I see some of the rules are now in:
/usr/share/polkit-1/actions/org.freedesktop.udisks2.policy

but looks like should be fine (but is not):
Code: Select all
$ pkaction --verbose --action-id org.freedesktop.udisks2.filesystem-mount
org.freedesktop.udisks2.filesystem-mount:
  description:       Mount a filesystem
  message:           Authentication is required to mount the filesystem
  vendor:            The udisks Project
  vendor_url:        http://udisks.freedesktop.org/
  icon:              drive-removable-media
  implicit any:      auth_admin
  implicit inactive: auth_admin
  implicit active:   yes


I am just wondering, why it was possible in KDE4 on the same laptop and moving into Plasma 5 cause the problem? It works for a root user.
What about KDE System Settings >> Removable Devices?
luebking
Karma
0
Is it a valid consolekit session?
Code: Select all
ck-list-sessions


The problem will be less Plasma 5 but how it's invoked (and thus whether polkit is consulted to leverage things)
User avatar vylaern
Registered Member
Posts
157
Karma
0
Code: Select all
$ ck-list-sessions
Session1:
        unix-user = '500'
        realname = '(null)'
        seat = 'Seat1'
        session-type = ''
        active = FALSE
        x11-display = ''
        x11-display-device = ''
        display-device = '/dev/tty1'
        remote-host-name = ''
        is-local = TRUE
        on-since = '2016-02-15T20:32:16.835039Z'
        login-session-id = '2'
luebking
Karma
0
Err... that is while and from a KDE login?
That of course explains it, but unfortunately I can't say *why* your session isn't listed in ck.

How do you start KDE? SDDM? XDM? startx?
User avatar vylaern
Registered Member
Posts
157
Karma
0
luebking wrote:How do you start KDE? SDDM? XDM? startx?


startx

p.s. What should be listed?
luebking
Karma
0
reasonable values for x11-display* and "active = TRUE"

What does your ~/.xinitrc say?
Code: Select all
exec ck-launch-session dbus-launch --sh-syntax --exit-with-session startkde

or
Code: Select all
exec dbus-launch --exit-with-session startkde
User avatar vylaern
Registered Member
Posts
157
Karma
0
Code: Select all
exec ck-launch-session dbus-launch --sh-syntax --exit-with-session startkde


Code: Select all
$ ck-list-sessions
Session4:
        unix-user = '500'
        realname = '(null)'
        seat = 'Seat1'
        session-type = ''
        active = FALSE
        x11-display = ''
        x11-display-device = ''
        display-device = '/dev/tty1'
        remote-host-name = ''
        is-local = TRUE
        on-since = '2016-02-18T08:21:37.559088Z'
        login-session-id = '3'
Session5:
        unix-user = '500'
        realname = '(null)'
        seat = 'Seat1'
        session-type = ''
        active = TRUE
        x11-display = ':0'
        x11-display-device = '/dev/tty7'
        display-device = '/dev/tty1'
        remote-host-name = ''
        is-local = TRUE
        on-since = '2016-02-18T08:23:43.142223Z'
        login-session-id = '3'


Code: Select all
exec dbus-launch --exit-with-session startkde


Code: Select all
$ ck-list-sessions
Session6:
        unix-user = '500'
        realname = '(null)'
        seat = 'Seat1'
        session-type = ''
        active = FALSE
        x11-display = ''
        x11-display-device = ''
        display-device = '/dev/tty1'
        remote-host-name = ''
        is-local = TRUE
        on-since = '2016-02-18T08:26:31.323867Z'
        login-session-id = '4'
luebking
Karma
0
Well, launching the session in console-kit certainly looks better, but the question was what's been in your xinitrc before.
Anyway, do things work now?
User avatar vylaern
Registered Member
Posts
157
Karma
0
luebking wrote:Well, launching the session in console-kit certainly looks better, but the question was what's been in your xinitrc before.
Anyway, do things work now?


Different options, still the same - no access to the memory card. :(

.xinitrc
Code: Select all
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto
exec startkde

 
Reply to topic

Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], claydoh, farid, Google [Bot], jacksong, joebuckley, Moldmaker, Section_8, Sogou [Bot], zfazylz