Your message dated Mon, 02 Mar 2015 01:23:34 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#730102: dbus: unable to mount
usb devices and shutdown the system
has caused the Debian Bug report #730102,
regarding dbus: unable to mount usb devices and shutdown the system
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
730102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730102
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dbus
Version: 1.6.18-1
Severity: normal
Dear Maintainer,
There is a problem with dbus in sid.
When I login as a normal user and insert an USB pendrive i can not mount
this device and if I try to shutdown the system the dialog form doesn't
enable the options "shudown", "hybernate" and "suspend", only enables
the option "exit".
In a fresh sid that works rigth when I login as a normal user, when I
logout and login again as root (in the X enviroment) an then I go back
to login as a normal user again the problem appears.
This is the error message at .xsession-errors :
"session: X session started for manolo at mié nov 20 21:07:01 CET 2013
localuser:manolo being added to access control list
/usr/bin/startxfce4: X server already running on display :0
xrdb: "Xft.hinting" on line 8 overrides entry on line 5
xrdb: "Xft.hintstyle" on line 10 overrides entry on line 6
xfce4-session-Message: ssh-agent is already running; starting gpg-agent
without ssh support
Then I try to mount an USB pendrive the dbus-monitor reports:
method call sender=:1.4 -> dest=:1.7 serial=69
path=/org/gtk/Private/RemoteVolumeMonitor;
interface=org.gtk.Private.RemoteVolumeMonitor; member=VolumeMount
string "0x1faddb0"
string ""
uint32 0
string "31764:2"
error sender=:1.7 -> dest=:1.4
error_name=org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code0
reply_serial=69
string "Not authorized to perform operation"
And the problem stays forever
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dbus depends on:
ii adduser 3.113+nmu3
ii libc6 2.17-96
ii libdbus-1-3 1.6.18-1
ii libexpat1 2.1.0-4
ii libselinux1 2.2.1-1
ii libsystemd-login0 204-5
ii lsb-base 4.1+Debian12
dbus recommends no packages.
Versions of packages dbus suggests:
ii dbus-x11 1.6.18-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 02.03.2015 um 00:37 schrieb Трезвый Дворник:
> Thank you for reply. I am sorry for wrong bug-report placing, just found
> "error_name=org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code0"
>
> here, and stopped looking for better location.
>
> While I was writing the answer below, i found that i am not right.
> It looks like #703016, when i start
> /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
> i can pkexec and mount.
>
> I am sorry for my haste.
That's not a bug in policykit-1 then either. You should file a bug
report against your desktop environment of choice. It should make sure
to pull in a polkit authentication agent via appropriate package
dependencies.
> Best regards,
> Dmitri
>
>
> -------My fail here------
>> What groups is your user account in? ("groups" command)
>
> ➜ ~ groups
> noroot disk audio dip video plugdev netdev vboxusers storage
>
> Same as in new jessie installation (where it appears a gui promt asking
> root password)
>
>> Does the system think your login session is active? (See below)
>
> Yes, it does
>
> Id=2
> Name=noroot
> Timestamp=Sun 2015-03-01 23:50:18 EET
> TimestampMonotonic=435710523
> VTNr=7
> Display=:0
> Remote=no
> Service=lightdm
> Scope=session-2.scope
> Leader=17397
> Audit=2
> Type=x11
> Class=user
> Active=yes
> State=active
> IdleHint=no
> IdleSinceHint=0
> IdleSinceHintMonotonic=0
>
>
>> What type of disk contains the partitions you are trying to manipulate?
>> Does the system think it is a removable disk? (See below)
>
> It is an internal hdd, and i fugured, that i can mount partitions with
>
> ➜ ~ /usr/bin/udisksctl mount -b /dev/sda5
> ==== AUTHENTICATING FOR org.freedesktop.udisks2.filesystem-mount-system ===
> Authentication is required to mount WDC WD10EZEX-08M2NA0 (/dev/sda5)
> Authenticating as: root
> Password:
>
> (udisksctl mount:24101): GLib-WARNING **: GChildWatchSource: Exit status of
> a child process was requested but ECHILD was received by waitpid(). Most
> likely the process is ignoring SIGCHLD, or some other thread is invoking
> waitpid() with a nonpositive first argument; either behavior can break
> applications that use g_child_watch_add()/g_spawn_sync() either directly or
> indirectly.
> ==== AUTHENTICATION COMPLETE ===
> Mounted /dev/sda5 at /media/noroot/data.
>
> and i cat umount it from thunar
>
>> ---- PolicyKit policy ----
>
>> /usr/share/polkit-1/actions/org.freedesktop.udisks2.policy says that
>> by default you can mount filesystems on removable devices if you either
>> authenticate as an administrative user or are in an active desktop session,
>> and you can only mount filesystems on non-removable devices
>> or described in /etc/fstab if you authenticate as an administrative user.
>
> Yep, chagint section to
> <defaults>
> <allow_any>yes</allow_any>
> <allow_inactive>yes</allow_inactive>
> <allow_active>yes</allow_active>
> </defaults>
>
> made the trick, and fs are mounting w/o asking password
>
> So, it is a problem just with gui part, because i can not also run
> gparted-pkexec.desktop, and had to swap pkexec with gksu, while running
> pkexec in terminal asks the root password in cli.
>
>
>
>
> There are the packages versions i have in my system
> aptitude search ~ipolicykit ~ipolkit ~idbus ~iudisk -F "%v %p"
> 1.9.12-1
> dbus
> 1.9.12-1
> dbus-x11
> 2.1.3-5
> gir1.2-udisks-2.0
> 1.9.12-1
> libdbus-1-3
> 1.9.12-1
> libdbus-1-3:i386
> 1.9.12-1
> libdbus-1-dev
> 0.102-1
> libdbus-glib-1-2
> 0.6.0-1
> libdbus-glib2.0-cil
> 0.8.1-1
> libdbus2.0-cil
> 12.10.2-1
> libdbusmenu-glib4
> 12.10.2-1
> libdbusmenu-gtk4
> 0.4.1-4
> libndesk-dbus-glib1.0-cil
> 0.6.0-6
> libndesk-dbus1.0-cil
> 1.0.0-2+b2
> libnet-dbus-perl
> 1.0.3-4.3
> libnih-dbus1
> 0.112-4
> libpolkit-agent-1-0
> 0.105-8
> libpolkit-backend-1-0
> 0.112-4
> libpolkit-gobject-1-0
> 0.103.0-1
> libpolkit-qt-1-1
> 4:4.8.6+git64-
> libqt4-dbus
> 4:4.8.6+git64-
> libqt4-dbus:i386
> 5.3.2+dfsg-4+b
> libqt5dbus5
> 4:4.8.6+git64-
> libqtdbus4
> 4:4.8.6+git64-
> libqtdbus4:i386
> 2.1.3-5
> libudisks2-0
> 0.112-4
> policykit-1
> 0.105-2
> policykit-1-gnome
> 1.2.0-2+b3
> python-dbus
> 1.2.0-2
> python-dbus-dev
> 4:4.8.6+git64-
> qdbus
> 2.1.4-1
> udisks2
>
>
> Versions of packages policykit-1 depends on:
> ii adduser 3.113+nmu3
> ii dbus 1.9.12-1
> ii libc6 2.19-15
> ii libexpat1 2.1.0-6+b3
> ii libglib2.0-0 2.42.1-1
> ii libmozjs-17.0-0 17.0.0-2
> ii libpam-systemd 219-4
> ii libpam0g 1.1.8-3.1
> ii libpolkit-agent-1-0 0.112-4
> ii libpolkit-gobject-1-0 0.112-4
> ii libsystemd0 219-4
>
> 2015-03-01 18:55 GMT+02:00 Simon McVittie <[email protected]>:
>
>> Control: reassign 730102 policykit-1
>> Control: tags 730102 + moreinfo
>>
>> This does not look like a bug in D-Bus: D-Bus is only a message-passing
>> system, and I don't see any indication that it is passing the messages
>> incorrectly (analogy: if you buy an office chair on eBay, and the
>> seller sends you a bobcat instead <http://xkcd.com/325/>, this is not
>> the courier's fault).
>>
>> I'm reassigning this to policykit for now in the hope that the PK
>> maintainers will know more about how to debug this than I do, but
>> you would probably get better results from a user support forum
>> such as the debian-user mailing list.
>>
>> The fact that the default "out of the box" configuration does not do
>> what you expect might be a bug in some component (perhaps udisks2 or
>> policykit-1), but you will need to provide more information / do more
>> research before anyone can determine what is wrong.
>>
>> On Thu, 21 Nov 2013 at 12:57:30 +0100, Manuel J. Martin wrote:
>>> xrdb: "Xft.hinting" on line 8 overrides entry on line 5
>>> xrdb: "Xft.hintstyle" on line 10 overrides entry on line 6
>>> xfce4-session-Message: ssh-agent is already running; starting gpg-agent
>>> without ssh support
>>
>> These don't look relevant.
>>
>>> method call sender=:1.4 -> dest=:1.7 serial=69
>>> path=/org/gtk/Private/RemoteVolumeMonitor;
>>> interface=org.gtk.Private.RemoteVolumeMonitor; member=VolumeMount
>>> string "0x1faddb0"
>>> string ""
>>> uint32 0
>>> string "31764:2"
>>> error sender=:1.7 -> dest=:1.4
>>>
>> error_name=org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code0
>>> reply_serial=69
>>> string "Not authorized to perform operation"
>>
>> This is not an error generated by libdbus or dbus-daemon. :1.4 (whatever
>> process that is) is sending a request, and :1.7 (looks like part of gvfs)
>> replies with the error G_IO_ERROR_FAILED "Not authorized to perform
>> operation".
>>
>> From searching source code, I suspect may be because :1.4 (gvfs?) is
>> sending a request to udisks2 and receiving the error
>> POLKIT_ERROR_NOT_AUTHORIZED "Not authorized to perform operation".
>>
>> On Sun, 01 Mar 2015 at 05:07:27 +0200, Трезвый Дворник wrote:
>>> I tried some udisk2/policykit rules, but without any success (anyway, it
>>> must
>>> be something relevant to out-of-box problem, not user-configuration part)
>>
>> What groups is your user account in? ("groups" command)
>>
>> Does the system think your login session is active? (See below)
>>
>> What type of disk contains the partitions you are trying to manipulate?
>> Does the system think it is a removable disk? (See below)
>>
>> ---- PolicyKit policy ----
>>
>> /usr/share/polkit-1/actions/org.freedesktop.udisks2.policy says that
>> by default you can mount filesystems on removable devices if you either
>> authenticate as an administrative user or are in an active desktop session,
>> and you can only mount filesystems on non-removable devices
>> or described in /etc/fstab if you authenticate as an administrative user.
>>
>> ---- Whether your login session is active ----
>>
>> In Debian wheezy, an "active desktop session" is one that ConsoleKit
>> thinks is active. Use the ck-list-sessions command to check that
>> ConsoleKit thinks your session is active.
>>
>> In Debian jessie/sid, an "active desktop session" is one that
>> systemd-logind thinks is active. Use the "loginctl list-sessions"
>> command to find your session ID, then something like "loginctl
>> show-session 1"
>> (if your session ID is 1) to check that systemd-logind thinks your
>> session is active.
>>
>> ---- Whether you are an administrative user ----
>>
>> An "administrative user" is a user in the sudo group. I don't know whether
>> root gets an exception from this check: in any case, using the GUI as root
>> is not recommended. You should create a non-root user account and add it
>> to the sudo group.
>>
>> ---- Whether your disk is removable ----
>>
>> Run "cat /sys/class/block/sda/removable" replacing sda with the name of
>> the disk device (e.g. /dev/sda). You should get 0 for an internal disk
>> or 1 for a disk with removable media. USB sticks usually show up as
>> "removable" even though they aren't really.
>>
>> Run "udisksctl dump" to see everything udisks knows about your disks
>> and partitions. Removable disks should have HintSystem: false,
>> HintIgnore: false; internal system disks should have HintSystem: true.
>>
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
