After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 404133 - crash in CD/DVD Creator: It happened immediately ...
crash in CD/DVD Creator: It happened immediately ...
Status: RESOLVED DUPLICATE of bug 362942
Product: gnome-system-tools
Classification: Deprecated
Component: general
2.15.x
Other All
: High critical
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
: 404134 437302 437323 437327 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-04 00:22 UTC by thehowlingfantods
Modified: 2007-06-22 11:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16

Attachments
output from sudo hald --daemon=no --verbose=yes > hald.output 2&>1 (323.72 KB, text/plain)
2007-05-10 16:54 UTC, philip.schlesinger 		Details

Description thehowlingfantods 2007-02-04 00:22:30 UTC 
What were you doing when the application crashed?
It happened immediately on restarting, right after login.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 26349568 vsize: 0 resident: 26349568 share: 0 rss: 9125888 rss_rlim: 0
CPU usage: start_time: 1170548484 rtime: 0 utime: 9 stime: 0 cutime:8 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226720608 (LWP 5234)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 107807

Thread 1 (Thread -1226720608 (LWP 5234))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 _dbus_abort
    at dbus-sysdeps.c line 84
  • #8 _dbus_warn_check_failed
  • #9 dbus_connection_add_filter
    at dbus-connection.c line 4955
  • #10 oobs_object_commit
    from /usr/lib/liboobs-1.so.2
  • #11 IA__g_object_newv
    at gobject.c line 697
  • #12 IA__g_object_new_valist
    at gobject.c line 1022
  • #13 IA__g_object_new
    at gobject.c line 795
  • #14 oobs_smb_config_get
    from /usr/lib/liboobs-1.so.2
  • #15 nautilus_shares_register_type
    from /usr/lib/nautilus/extensions-1.0/libnautilus-gst-shares.so
  • #16 IA__g_type_create_instance
    at gtype.c line 1569
  • #17 g_object_constructor
    at gobject.c line 1041
  • #18 IA__g_object_newv
    at gobject.c line 937
  • #19 IA__g_object_new_valist
    at gobject.c line 981
  • #20 IA__g_object_new
    at gobject.c line 795
  • #21 nautilus_marshal_BOOLEAN__POINTER
  • #22 nautilus_marshal_BOOLEAN__POINTER
  • #23 POA_Nautilus_MetafileMonitor__init
  • #24 POA_Nautilus_MetafileMonitor__init
  • #25 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #26 ??
  • #0 __kernel_vsyscall 






Comment 1


palfrey





          2007-02-04 22:18:31 UTC
        



*** Bug 404134 has been marked as a duplicate of this bug. ***






Comment 2


André Klapper





          2007-02-06 00:09:52 UTC
        



can you please also install the packages liboobs-1-2-dbg and gnome-system-tools-dbgsym, try to reproduce the crash, and provide the stacktrace here?







Comment 3


Pedro Villavicencio





          2007-05-09 23:29:56 UTC
        



*** Bug 437302 has been marked as a duplicate of this bug. ***






Comment 4


Pedro Villavicencio





          2007-05-10 01:54:34 UTC
        



*** Bug 437327 has been marked as a duplicate of this bug. ***






Comment 5


Pedro Villavicencio





          2007-05-10 02:01:11 UTC
        



*** Bug 437323 has been marked as a duplicate of this bug. ***






Comment 6


philip.schlesinger





          2007-05-10 16:46:48 UTC
        



I'm using Ubuntu 6.10.  

I have a unable to initialize HAL error when starting up.  It seems to be related to dbus:

<snip>
$ sudo /etc/init.d/dbus restart
 * Stopping System Tools Backends system-tools-backends                  [ ok ] 
 * Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon                       [fail] 
 * Stopping Hardware abstraction layer hald                              [ ok ] 
 * Stopping system message bus dbus                                      [ ok ] 
 * Starting system message bus dbus                                      [ ok ] 
 * Starting Hardware abstraction layer hald                                     run-parts: /etc/dbus-1/event.d/20hal exited with return code 1
 * Starting System Tools Backends system-tools-backends                  [ ok ] 
$
</snip> 

I cannot use the update manager or user and groups manager.

I cannot lock the screen (nothing happens both when I click the lock screen icon directly and when I click the red power icon in my toolbar and then click the lock screen button).

I can't seem to quit the X server (ctrl-alt-backspace just brings me back to a login screen, and when I hit the key combo again, it just brings me to a generic gnome login screen).

I've installed liboobs-1-2-dbg, but gnome-system-tools-dbgsym does not appear to be a valid package.

Your help would be greatly appreciated.






Comment 7


philip.schlesinger





          2007-05-10 16:50:53 UTC
        



btw I tried removing and reinstalling the hal and haldaemon users as well as the hal package per: https://launchpad.net/ubuntu/+source/dbus/+bug/31517/

with no luck either.






Comment 8


philip.schlesinger





          2007-05-10 16:54:21 UTC
        



Created attachment 87972 [details]
output from sudo hald --daemon=no --verbose=yes > hald.output 2&>1

Tried this per https://launchpad.net/ubuntu/+source/dbus/+bug/19577






Comment 9


philip.schlesinger





          2007-05-15 22:55:48 UTC
        



=== BUMP ===
Anybody there?






Comment 10


André Klapper





          2007-06-22 11:27:20 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to ask UBuntu for a software upgrade.


*** This bug has been marked as a duplicate of 362942 ***