Package: disk-manager
Version: 1.1.1-1
Followup-For: Bug #640133
(See below if you are looking for quick fix as normal use.)
Let's assume that no sane X desktop user runs X under root, then this
bug is real. All other X configuration tools which require
administrative right are configured to be started via something like
gksu. This is not the case for disk-manager provided as Debian package.
(This is not upstream bug as I describe below.)
I just installed this. Both menu (Gnome one via desktop file and Debian
tradition menu) does not work when started from normal user. This is a
bug which has a major effect on the usability of a package, without
rendering it completely unusable to everyone who dare to run X under X.
==> IMPORTANT BUG
disk-manager code checks its administrative right upon its execution and
exit as "insufficient right".
| if not os.getuid() == 0 :
| dialog("warning", _("Insufficient rights"), \
| _("You need administrative rights to start this application."))
| return
== FIX FOR MAINTAINER ==
SHORT ANSWER:
This maintainer needs to add dependency to gksu for installed package
and make desktop file to execute: "gksu disk-manager" instead.
LONGER ANSWER:
This can be done by replacing contents of
/usr/share/applications/disk-manager.desktop
from
Exec= /usr/sbin/disk-manager
to
Exec=gksu disk-manager
in package build script debian/rules. Of course this is a short cut.
Upstream has fancy build script configure.ac as:
| # su handler
| AC_CHECK_PROGS([SUHANDLER], [su-to-root gksu kdesudo kdesu])
|
| if test ${SUHANDLER} = "su-to-root"; then
| SUHANDLER="su-to-root -X -c"
| fi
Since you did not install gksu in build environment, autotools did not
detect it and skipped it in desktop file. Some tweaking in build script
should fix this.
See data/disk-manager.desktop.in and data/disk-manager.desktop.in.in how
this affected the maintainer's build result.
This bug may be regression of 1.1-1 for the following action.
"Point menu to disk-manager, instead of disk-manager-root"
The above is for gnome/KDE menu. For Debian menu, you need to use gksu
too.
=== QUICK FIX FOR NORMAL USER ==
For people got hit by this silly bug, here is a work around for
your Gnome Desktop.
* Right click top left corner debian swirl icon to "Edit menu".
* Click to open item: System -> Administration
* Right click "Disk Manager" to open Properties.
* Replace command with "gksu disk-manager" (No quotation marks needed)
* Close and Close
Now we are ready to use this package as normal user :-)
(You can configure gksu to use su or sudo behavior via gconf-editor
under /apps/gksu . Normally This is sudo mode these days.)
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages disk-manager depends on:
ii menu 2.1.45
ii python 2.6.7-3
ii python-glade2 2.24.0-2
ii python-gtk2 2.24.0-2
ii python-support 1.0.14
Versions of packages disk-manager recommends:
ii dmsetup 2:1.02.65-1
disk-manager suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
