| Summary: | gnome-base/gnome-volume-manager-2.15.0 does not starts | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Victor Yegorov <vyegorov> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | aj, dsd, michal |
| Priority: | Normal | ||
| Version: | 2006.1 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
strace output for gvm
patch to fix bug 154675 ebuild for g-v-m-2.15.0_p1, fixes bug 154675 patch for g-v-m-2.15.0_p1 ebuild, fixes bug 154675 |
||
|
Description
Victor Yegorov
2006-11-10 06:49:22 UTC
Are you starting a session bus ? if not, add eval "/usr/bin/dbus-launch --sh-syntax --exit-with-session" in your .xinitrc As I mntioned, I don't have .xinitrc System default startup script is used, it is /etc/X11/Sessions/Gnome (based on my config). In this script, all xinitrc.d/ scripts are sourced, including the one for dbus, which starts session bus (see /etc/X11/xinit/xinitrc.d/30-dbus). So yes, I'm running session bus (set | grep DBUS reports DBUS_SESSION_BUS_ADDRESS). do you use pam_console or do you have a file under /var/run/console/${USER} ?
IIRC I think it's needed for g-v-m
Hm, not sure.
But as I have no such file /var/run/console/${USER}, then I assume that pam_consolde is used. Actually, no files under /var/run/console at all.
Do you mean this file is needed?.. If yes, what would be the proper way to setup system to create/use this file?
IIRC, pam_console is not needed for g-v-m (it used to be required for networkmanager though). Could you try rebuilding g-v-m with your CFLAGS set to "-O2 -pipe" ? Thanks Rebuilt. All the same sympthoms, going back to 1.5.15-r3 pam_console *is* needed for g-v-m, at least here. g-v-m silently exits if on_console fails. @dang: gvm works fine here without it (running in the background, waiting for me to plug my usb keys). Maybe it checks for it at build time and dlopen()s it when you run it. @Victor: could try and figure out if gvm either segfaults or quits with an error? I suggest you do a wrapper script like this one to see what's going on : (rename /usr/bin/gnome-volume-manager as gnome-volume-manager.orig and create/chmod this script as gnome-volume-manager) ------------- #!/bin/bash /usr/bin/strace /usr/bin/gnome-volume-manager.orig $@ &> /tmp/gvm.txt ------------- Created attachment 102380 [details]
strace output for gvm
Note: I've already installed pam_console, strace done after the pam_console was installed and Gnome restarted.
sys-libs/pam-0.99.6.3-r1
sys-auth/pam_console-0.99.6.2.3.6
gnome-base/gnome-volume-manager-2.15.0
I filed a bug upstream on this a while back. http://bugzilla.gnome.org/show_bug.cgi?id=359443 Apparently it has been fixed in cvs, and there is a link in the upstream bug to a patch. Perhaps that patch could be applied here? Installing gvm 2.17.0 (which is not in official portage yet) fixed the problem. Confirmed, can 2.17.0 go into portage or should I backport the fix? Created attachment 104342 [details, diff] patch to fix bug 154675 patch to g-v-m 2.15.0 to fix the startx session bug which is caused by gvm_local_user, where ut_line is returned as ttyN rather than :0. (In reply to comment #13) > Created an attachment (id=104342) [edit] > patch to fix bug 154675 > > patch to g-v-m 2.15.0 to fix the startx session bug which is caused by > gvm_local_user, where ut_line is returned as ttyN rather than :0. > Note: I take no credit for the above attachment, I simply pinched it (http://cvs.gnome.org/viewcvs/gnome-volume-manager/src/manager.c?r1=1.152&r2=1.153) and added it to this bugzilla so it's easier for people to see. I'm going to create a local ebuild in my overlay tommorow (currently remote to my gnome gentoo machine) and will post more details then. Comment on attachment 104342 [details, diff] patch to fix bug 154675 broken, still working on it sorry! Created attachment 104430 [details] ebuild for g-v-m-2.15.0_p1, fixes bug 154675 Got my act together and wrote the ebuild to fix the bug we're experiencing Created attachment 104431 [details, diff] patch for g-v-m-2.15.0_p1 ebuild, fixes bug 154675 This is the accompanying patch for my previous ebuild attachment this works here fine... i started out by upgrading to 2.17.0 then found this bug and it resolves the issue... you need to get this in portage since this has been broken for too long Fixed in CVS, thanks everyone :) |
