Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#760281: xfce4: cannot mount usb drive: "Not authorized to perform operation"
18 views
Skip to first unread message
Julian Gilbey
Sep 2, 2014, 10:30:01 AM9/2/14
to
Package: xfce4
Version: 4.10.1
Severity: important
Having recently updated testing, I discover that I can no longer mount
a USB drive by double-clicking on it in the panel. (If this should be
reassigned to xfce4-panel or elsewhere, please do so!) I am running
with a SysV init system, not systemd, so I wonder whether this bug is
similar to that described in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557
The error message which pops up says "Failed to mount "drive name" -
Not authorized to perform operation".
Julian
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xfce4 depends on:
ii gtk2-engines-xfce 3.0.1-2
ii libxfce4ui-utils 4.10.0-5
ii orage 4.10.0-1+b1
ii thunar 1.6.3-1
ii xfce4-appfinder 4.10.1-1
ii xfce4-mixer 4.10.0-3
ii xfce4-panel 4.10.1-1
ii xfce4-session 4.10.1-8
ii xfce4-settings 4.10.1-2
ii xfconf 4.10.0-2
ii xfdesktop4 4.10.2-3
ii xfwm4 4.10.1-2
Versions of packages xfce4 recommends:
ii desktop-base 7.0.3
ii tango-icon-theme 0.8.90-5
ii thunar-volman 0.8.0-4
ii xfce4-notifyd 0.2.4-3
ii xorg 1:7.7+7
Versions of packages xfce4 suggests:
pn gtk3-engines-xfce <none>
ii xfce4-goodies 4.10
ii xfce4-power-manager 1.2.0-5.1
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Version: 4.10.1
Severity: important
Having recently updated testing, I discover that I can no longer mount
a USB drive by double-clicking on it in the panel. (If this should be
reassigned to xfce4-panel or elsewhere, please do so!) I am running
with a SysV init system, not systemd, so I wonder whether this bug is
similar to that described in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557
The error message which pops up says "Failed to mount "drive name" -
Not authorized to perform operation".
Julian
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xfce4 depends on:
ii gtk2-engines-xfce 3.0.1-2
ii libxfce4ui-utils 4.10.0-5
ii orage 4.10.0-1+b1
ii thunar 1.6.3-1
ii xfce4-appfinder 4.10.1-1
ii xfce4-mixer 4.10.0-3
ii xfce4-panel 4.10.1-1
ii xfce4-session 4.10.1-8
ii xfce4-settings 4.10.1-2
ii xfconf 4.10.0-2
ii xfdesktop4 4.10.2-3
ii xfwm4 4.10.1-2
Versions of packages xfce4 recommends:
ii desktop-base 7.0.3
ii tango-icon-theme 0.8.90-5
ii thunar-volman 0.8.0-4
ii xfce4-notifyd 0.2.4-3
ii xorg 1:7.7+7
Versions of packages xfce4 suggests:
pn gtk3-engines-xfce <none>
ii xfce4-goodies 4.10
ii xfce4-power-manager 1.2.0-5.1
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Yves-Alexis Perez
Sep 2, 2014, 12:40:02 PM9/2/14
to
Control: reassign -1 systemd-shim
On mar., 2014-09-02 at 15:21 +0100, Julian Gilbey wrote:
> Having recently updated testing, I discover that I can no longer mount
> a USB drive by double-clicking on it in the panel. (If this should be
> reassigned to xfce4-panel or elsewhere, please do so!) I am running
> with a SysV init system, not systemd, so I wonder whether this bug is
> similar to that described in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557
>
> The error message which pops up says "Failed to mount "drive name" -
> Not authorized to perform operation".
As far as I can tell, this is due to systemd-shim, but it's a bit hard
to debug.
It might be the same thing as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757348 or
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747821 but it's not
completely sure. Any help appreciated.
Regards,
--
Yves-Alexis
On mar., 2014-09-02 at 15:21 +0100, Julian Gilbey wrote:
> Having recently updated testing, I discover that I can no longer mount
> a USB drive by double-clicking on it in the panel. (If this should be
> reassigned to xfce4-panel or elsewhere, please do so!) I am running
> with a SysV init system, not systemd, so I wonder whether this bug is
> similar to that described in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557
>
> The error message which pops up says "Failed to mount "drive name" -
> Not authorized to perform operation".
to debug.
It might be the same thing as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757348 or
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747821 but it's not
completely sure. Any help appreciated.
Regards,
--
Yves-Alexis
Julian Gilbey
Sep 2, 2014, 4:50:02 PM9/2/14
to
On Tue, Sep 02, 2014 at 06:26:36PM +0200, Yves-Alexis Perez wrote:
> Control: reassign -1 systemd-shim
>
> On mar., 2014-09-02 at 15:21 +0100, Julian Gilbey wrote:
> > Having recently updated testing, I discover that I can no longer mount
> > a USB drive by double-clicking on it in the panel. (If this should be
> > reassigned to xfce4-panel or elsewhere, please do so!) I am running
> > with a SysV init system, not systemd, so I wonder whether this bug is
> > similar to that described in
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557
> >
> > The error message which pops up says "Failed to mount "drive name" -
> > Not authorized to perform operation".
>
> As far as I can tell, this is due to systemd-shim, but it's a bit hard
> to debug.
I am happy to help debug, but I have very little idea how to do so. I
> Control: reassign -1 systemd-shim
>
> On mar., 2014-09-02 at 15:21 +0100, Julian Gilbey wrote:
> > Having recently updated testing, I discover that I can no longer mount
> > a USB drive by double-clicking on it in the panel. (If this should be
> > reassigned to xfce4-panel or elsewhere, please do so!) I am running
> > with a SysV init system, not systemd, so I wonder whether this bug is
> > similar to that described in
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557
> >
> > The error message which pops up says "Failed to mount "drive name" -
> > Not authorized to perform operation".
>
> As far as I can tell, this is due to systemd-shim, but it's a bit hard
> to debug.
have systemd version 208-8 installed, if that is of any significance,
and systemd-shim version 7-1.
Julian
Yves-Alexis Perez
Sep 3, 2014, 4:20:02 PM9/3/14
to
On mar., 2014-09-02 at 21:44 +0100, Julian Gilbey wrote:
> On Tue, Sep 02, 2014 at 06:26:36PM +0200, Yves-Alexis Perez wrote:
> > Control: reassign -1 systemd-shim
> >
> > On mar., 2014-09-02 at 15:21 +0100, Julian Gilbey wrote:
> > > Having recently updated testing, I discover that I can no longer mount
> > > a USB drive by double-clicking on it in the panel. (If this should be
> > > reassigned to xfce4-panel or elsewhere, please do so!) I am running
> > > with a SysV init system, not systemd, so I wonder whether this bug is
> > > similar to that described in
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557
> > >
> > > The error message which pops up says "Failed to mount "drive name" -
> > > Not authorized to perform operation".
> >
> > As far as I can tell, this is due to systemd-shim, but it's a bit hard
> > to debug.
>
> I am happy to help debug, but I have very little idea how to do so. I
> have systemd version 208-8 installed, if that is of any significance,
> and systemd-shim version 7-1.
Steve, is there anything we can do to help here? What kind of
> On Tue, Sep 02, 2014 at 06:26:36PM +0200, Yves-Alexis Perez wrote:
> > Control: reassign -1 systemd-shim
> >
> > On mar., 2014-09-02 at 15:21 +0100, Julian Gilbey wrote:
> > > Having recently updated testing, I discover that I can no longer mount
> > > a USB drive by double-clicking on it in the panel. (If this should be
> > > reassigned to xfce4-panel or elsewhere, please do so!) I am running
> > > with a SysV init system, not systemd, so I wonder whether this bug is
> > > similar to that described in
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557
> > >
> > > The error message which pops up says "Failed to mount "drive name" -
> > > Not authorized to perform operation".
> >
> > As far as I can tell, this is due to systemd-shim, but it's a bit hard
> > to debug.
>
> I am happy to help debug, but I have very little idea how to do so. I
> have systemd version 208-8 installed, if that is of any significance,
> and systemd-shim version 7-1.
information do you need?
Regards,
--
Yves-Alexis
Steve Langasek
Sep 5, 2014, 7:40:01 PM9/5/14
to
cherry-picked patch from upstream to fix a race condition, that would allow
systemd-shim to respond to a request before processes had actually been put
in the cgroup. This problem was diagnosed with lightdm on Ubuntu Phone, but
it's quite possible that the same problem is affected xfce.
Could someone please test whether systemd-shim fixes this problem for them?
If it does, great! If not, I'll schedule some time to dig into this bug
further.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slan...@ubuntu.com vor...@debian.org
Yves-Alexis Perez
Sep 6, 2014, 6:20:02 AM9/6/14
to
On ven., 2014-09-05 at 16:30 -0700, Steve Langasek wrote:
> I'm not sure, but note that I've just uploaded systemd-shim 7-3 with a
> cherry-picked patch from upstream to fix a race condition, that would allow
> systemd-shim to respond to a request before processes had actually been put
> in the cgroup. This problem was diagnosed with lightdm on Ubuntu Phone, but
> it's quite possible that the same problem is affected xfce.
>
> Could someone please test whether systemd-shim fixes this problem for them?
> If it does, great! If not, I'll schedule some time to dig into this bug
> further.
I don't have a sysv-rc-core/systemd-shim system at home so I can't
> I'm not sure, but note that I've just uploaded systemd-shim 7-3 with a
> cherry-picked patch from upstream to fix a race condition, that would allow
> systemd-shim to respond to a request before processes had actually been put
> in the cgroup. This problem was diagnosed with lightdm on Ubuntu Phone, but
> it's quite possible that the same problem is affected xfce.
>
> Could someone please test whether systemd-shim fixes this problem for them?
> If it does, great! If not, I'll schedule some time to dig into this bug
> further.
really test until monday. Julian if you could test that'd be nice.
Failing that, I'll try to ping the ranting crowd on the various Xfce bugs.
Regards,
--
Yves-Alexis
Clement Hermann
Sep 6, 2014, 10:10:03 AM9/6/14
to
Hi,
On Fri, 5 Sep 2014 16:30:49 -0700 Steve Langasek <vor...@debian.org> wrote:
> I'm not sure, but note that I've just uploaded systemd-shim 7-3 with a
> cherry-picked patch from upstream to fix a race condition, that would
allow
> systemd-shim to respond to a request before processes had actually
been put
> in the cgroup. This problem was diagnosed with lightdm on Ubuntu
Phone, but
> it's quite possible that the same problem is affected xfce.
>
> Could someone please test whether systemd-shim fixes this problem for
them?
> If it does, great! If not, I'll schedule some time to dig into this bug
> further.
I doesn't seem to fix the issue, at least for me :
- gdm3 doesn't list the users, as gnome-session fails to get the
session-id somehow. greeter.log :
gnome-session[12023]: WARNING: Could not get session id for session.
Check that logind is properly installed and pam_systemd is getting used
at login.
auth.log (debug=yes for pam_systemd.so) :
Sep 6 15:37:44 shadowfax gdm-launch-environment][11829]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
Sep 6 15:37:44 shadowfax gdm-launch-environment][11829]:
pam_systemd(gdm-launch-environment:session): Asking logind to create
session: uid=1000 pid=11829 service=gdm-launch-environment type=x11
class=greeter seat=seat0 vtnr=7 tty= display=:0 remote=no remote_user=
remote_host=
Sep 6 15:37:44 shadowfax gdm-launch-environment][11829]:
pam_systemd(gdm-launch-environment:session): Failed to parse message:
Argument 4 is specified to be of type "string", but is actually of type
"uint32"
Sep 6 15:37:44 shadowfax gdm-launch-environment][11829]:
pam_ck_connector(gdm-launch-environment:session): nox11 mode, ignoring
PAM_TTY :0
Sep 6 15:37:45 shadowfax dbus[2250]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.159" (uid=117 pid=11871
comm="gnome-shell --mode=gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.53" (uid=0 pid=3339
comm="/usr/sbin/console-kit-daemon --no-daemon ")
Sep 6 15:37:45 shadowfax dbus[2250]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.159" (uid=117 pid=11871
comm="gnome-shell --mode=gdm ")
interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" error name="(unset)" requested_reply="0"
destination=":1.1" (uid=0 pid=2451 comm="/usr/sbin/bluetoothd ")
- I can login with lightdm, but there is no suspend button, and
network-manager applet doesn't work (connections are shown, but there is
no way to act on them)
In both case, loginctl list-session and show-session seem normal.
Hope that helps.
--
Clément Hermann (nodens)
On Fri, 5 Sep 2014 16:30:49 -0700 Steve Langasek <vor...@debian.org> wrote:
> I'm not sure, but note that I've just uploaded systemd-shim 7-3 with a
> cherry-picked patch from upstream to fix a race condition, that would
allow
> systemd-shim to respond to a request before processes had actually
been put
> in the cgroup. This problem was diagnosed with lightdm on Ubuntu
Phone, but
> it's quite possible that the same problem is affected xfce.
>
> Could someone please test whether systemd-shim fixes this problem for
them?
> If it does, great! If not, I'll schedule some time to dig into this bug
> further.
- gdm3 doesn't list the users, as gnome-session fails to get the
session-id somehow. greeter.log :
gnome-session[12023]: WARNING: Could not get session id for session.
Check that logind is properly installed and pam_systemd is getting used
at login.
auth.log (debug=yes for pam_systemd.so) :
Sep 6 15:37:44 shadowfax gdm-launch-environment][11829]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
Sep 6 15:37:44 shadowfax gdm-launch-environment][11829]:
pam_systemd(gdm-launch-environment:session): Asking logind to create
session: uid=1000 pid=11829 service=gdm-launch-environment type=x11
class=greeter seat=seat0 vtnr=7 tty= display=:0 remote=no remote_user=
remote_host=
Sep 6 15:37:44 shadowfax gdm-launch-environment][11829]:
pam_systemd(gdm-launch-environment:session): Failed to parse message:
Argument 4 is specified to be of type "string", but is actually of type
"uint32"
Sep 6 15:37:44 shadowfax gdm-launch-environment][11829]:
pam_ck_connector(gdm-launch-environment:session): nox11 mode, ignoring
PAM_TTY :0
Sep 6 15:37:45 shadowfax dbus[2250]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.159" (uid=117 pid=11871
comm="gnome-shell --mode=gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.53" (uid=0 pid=3339
comm="/usr/sbin/console-kit-daemon --no-daemon ")
Sep 6 15:37:45 shadowfax dbus[2250]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.159" (uid=117 pid=11871
comm="gnome-shell --mode=gdm ")
interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" error name="(unset)" requested_reply="0"
destination=":1.1" (uid=0 pid=2451 comm="/usr/sbin/bluetoothd ")
- I can login with lightdm, but there is no suspend button, and
network-manager applet doesn't work (connections are shown, but there is
no way to act on them)
In both case, loginctl list-session and show-session seem normal.
Hope that helps.
--
Clément Hermann (nodens)
Julian Gilbey
Sep 6, 2014, 6:10:02 PM9/6/14
to
On Fri, Sep 05, 2014 at 04:30:49PM -0700, Steve Langasek wrote:
> > > > On mar., 2014-09-02 at 15:21 +0100, Julian Gilbey wrote:
> > > > > Having recently updated testing, I discover that I can no longer mount
> > > > > a USB drive by double-clicking on it in the panel. (If this should be
> > > > > reassigned to xfce4-panel or elsewhere, please do so!) I am running
> > > > > with a SysV init system, not systemd, so I wonder whether this bug is
> > > > > similar to that described in
> > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557
>
> > > > > The error message which pops up says "Failed to mount "drive name" -
> > > > > Not authorized to perform operation".
> [...]
> > > > On mar., 2014-09-02 at 15:21 +0100, Julian Gilbey wrote:
> > > > > Having recently updated testing, I discover that I can no longer mount
> > > > > a USB drive by double-clicking on it in the panel. (If this should be
> > > > > reassigned to xfce4-panel or elsewhere, please do so!) I am running
> > > > > with a SysV init system, not systemd, so I wonder whether this bug is
> > > > > similar to that described in
> > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557
>
> > > > > The error message which pops up says "Failed to mount "drive name" -
> > > > > Not authorized to perform operation".
> I'm not sure, but note that I've just uploaded systemd-shim 7-3 with a
> cherry-picked patch from upstream to fix a race condition, that would allow
> systemd-shim to respond to a request before processes had actually been put
> in the cgroup. This problem was diagnosed with lightdm on Ubuntu Phone, but
> it's quite possible that the same problem is affected xfce.
>
> Could someone please test whether systemd-shim fixes this problem for them?
> If it does, great! If not, I'll schedule some time to dig into this bug
> further.
I just tried it. It sadly doesn't fix this problem. It also doesn't
> cherry-picked patch from upstream to fix a race condition, that would allow
> systemd-shim to respond to a request before processes had actually been put
> in the cgroup. This problem was diagnosed with lightdm on Ubuntu Phone, but
> it's quite possible that the same problem is affected xfce.
>
> Could someone please test whether systemd-shim fixes this problem for them?
> If it does, great! If not, I'll schedule some time to dig into this bug
> further.
fix the probably-unrelated problem of bug #758557. :-(
Thanks, Steve!
0 new messages