|
Bugzilla – Full Text Bug Listing |
| Summary: | gnome-mount broken? | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Andreas Hanke <andreas.hanke> |
| Component: | GNOME | Assignee: | Hans Petter Jansson <hpj> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | ||
| Version: | Alpha 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Andreas Hanke
2007-03-19 05:35:48 UTC
G_DEBUG is turned off in the latest gnome-session. I have DVD's mounting ok with that. Mounting works for me now as well, bug ejecting doesn't. There is just a GUI error message: Cannot eject volume Cannot eject the volume 'SU102Alp.001'. Yes, getting that now too, although the item actually gets unmounted for me. I need to look at the code to determine what would cause it. Also probably install latest 10.3 release and try to reproduce it. I have to excuse very much: It is hal's fault, gnome-mount is innocent. hal thinks eject is /usr/bin/eject, but on SUSE it's /bin/eject. This was already fixed in the past, but the patch seems to have been dropped from the hal package. What remains is the assert if hald is not running. Not fixed even in svn trunk, but minor. Filed bug 256270 against hal. Thank you, Andreas. Since I still don't have 10.3 installed, I'd love to see a trace for the assert, if possible. (gdb) run
Starting program: /usr/bin/nautilus
[Thread debugging using libthread_db enabled]
[New Thread -1228867376 (LWP 6697)]
GTK Accessibility Module initialized
Bonobo accessibility support initialized
Initializing nautilus-open-terminal extension
Initializing gnome-mount extension
** (nautilus:6697): WARNING **: Failed to initialize libhal context: (null) : (null)
** (nautilus:6697): WARNING **: Could not initialize hal context
GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
aborting...
Program received signal SIGABRT, Aborted.
[Switching to Thread -1228867376 (LWP 6697)]
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb6c58f20 in raise () from /lib/libc.so.6
#2 0xb6c5a6c1 in abort () from /lib/libc.so.6
#3 0xb6f4df2a in IA__g_logv (log_domain=0xb6fdd35c "GLib-GObject",
log_level=G_LOG_LEVEL_CRITICAL,
format=0xb6f78e3b "%s: assertion `%s' failed",
args1=0xbf87d1bc "\200���\024����r��") at gmessages.c:497
#4 0xb6f4df69 in IA__g_log (log_domain=0xb6fdd35c "GLib-GObject",
log_level=G_LOG_LEVEL_CRITICAL,
format=0xb6f78e3b "%s: assertion `%s' failed") at gmessages.c:517
#5 0xb6f4e04b in IA__g_return_if_fail_warning (
log_domain=0xb6fdd35c "GLib-GObject",
pretty_function=0xb6fdee80 "g_object_new",
expression=0xb6fde814 "G_TYPE_IS_OBJECT (object_type)") at gmessages.c:532
#6 0xb6fbc43c in IA__g_object_new (object_type=0, first_property_name=0x0)
at gobject.c:792
#7 0x081372fa in nautilus_module_add_type (type=0) at nautilus-module.c:253
#8 0x081375d1 in nautilus_module_init () at nautilus-module.c:160
#9 0x08080c27 in nautilus_application_startup (application=0x81f5d38,
kill_shell=0, restart_shell=0, no_default_window=0, no_desktop=0,
do_first_time_druid_check=1, browser_window=0,
startup_id=0x81f88a8 "_TIME1932010232", geometry=0x0, session_to_load=0x0,
urls=0x0) at nautilus-application.c:439
#10 0x08091aad in main (argc=1, argv=0xbf87d674) at nautilus-main.c:533
ok, so with G_DEBUG turned off nautilus won't crash. Warning is appropriate as hal is pretty darn necessary these days, so I think I can close this out. |