Kubuntu - All gnome apps fail (different ways)

Bug #274224 reported by ro9u3b46
4
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome

Loaded Kubuntu 8.04.1 from CDROM - loaded updates - everything worked!

Loaded Ubuntu Firefox - did not work
- start from GUI > some hard drive activity then nothing
- start from terminal > "bus error"
Loaded Aisleriot (gnome-games) - did not work
- Start at GUI > only - border shows - nothing inside the border - not populated
Loaded Blackjack - did not work
- Start at GUI > only - border shows - nothing inside the border - not populated
Downloaded Firefox 3.0.2 from Mozilla - did not work
- Start from GUI > some hard drive activity then nothing
- Start from terminal > "bus error"
- Start gThumb from GUI - border shows - nothing inside the border - not populated
- Start gthumb from terminal > mousepointer freezes on newline

- Start Fspot from GUI > Error "An unhandled exception was thrown: F-Spot cannot find the Dbus session bus. Make sure dbus is configured properly or start a new session for f-spot using "dbus-launch f-spot"
- dbus started at boot and running

Sounds almost like a Xulrunner 1.9.??? problem but other things are happening - using Xulrunner 1.9.0.1. I do not have Keytouch installed.

All KDE stuff works just fine

Using 3.5.10 - current files

p.s. I tried to load Kubuntu 8.04.1 with gnome apps on another computer. It took me more than 5 installs to get everything working. The failures included Xulrunner, Network Manager, and KeyTouch. This is the most troublesome install of Kubuntu that I have ever run into. This install onto my wife's computer is trouble also!

Revision history for this message
ro9u3b46 (ro9u3b46) wrote :

Today, 25 September 2008, I downloaded bugfixes to Xulrunner & security update to Firefox via Adept.

The problems still exist.
I tried checking the checksums with debsums -s but nothing showed.

fyi . . .

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

It simply sounds like the session bus is not running?

Revision history for this message
ro9u3b46 (ro9u3b46) wrote :
Download full text (4.9 KiB)

Tried

?@TheMacHine:~$ sudo /etc/init.d/dbus start
[sudo] password for ?:
 * system message bus already started; not starting.
?@TheMacHine:~$

?@TheMacHine:~$ sudo dbus-launch f-spot
(/usr/lib/f-spot/f-spot.exe:6767): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.16.4/gobject/gtype.c:2248: initialization assertion failed, use IA__g_type_init() prior to this function

(/usr/lib/f-spot/f-spot.exe:6767): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed

(/usr/lib/f-spot/f-spot.exe:6767): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
Stacktrace:

  at (wrapper managed-to-native) GConf.Client.gconf_client_get_default () <0x00004>
  at (wrapper managed-to-native) GConf.Client.gconf_client_get_default () <0xffffffff>
  at GConf.Client..ctor () <0x0003b>
  at FSpot.GConfPreferenceBackend.get_Client () <0x0001f>
  at FSpot.GConfPreferenceBackend.AddNotify (string,FSpot.NotifyChangedHandler) <0x00033>
  at FSpot.Preferences.get_Backend () <0x000ea>
  at FSpot.Preferences.Get (string) <0x00074>
  at FSpot.Driver.Main (string[]) <0x00144>
  at (wrapper runtime-invoke) FSpot.Driver.runtime_invoke_int_string[] (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

        f-spot [0x816b1fa]
        f-spot [0x807de81]
        [0xb7fbb440]
        /usr/lib/libgconf-2.so.4(gconf_client_get_default+0xa9) [0xb6caf9f9]
        [0xb7820de0]
        [0xb782087c]
        [0xb7820818]
        [0xb7820764]
        [0xb7820633]
        [0xb782017d]
        [0xb781c93d]
        [0xb781c1c4]
        f-spot(mono_runtime_exec_main+0x10e) [0x809c68e]
        f-spot(mono_runtime_run_main+0x173) [0x809c933]
        f-spot(mono_main+0x6a9) [0x805acd9]
        f-spot [0x805a122]
        /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d69450]
        f-spot [0x805a091]

Debug info from gdb:

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7d11940 (LWP 6767)]
[New Thread 0xb7294b90 (LWP 6773)]
[New Thread 0xb7fa7b90 (LWP 6772)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7fbb410 in __kernel_vsyscall ()
  3 Thread 0xb7fa7b90 (LWP 6772) 0xb7fbb410 in __kernel_vsyscall ()
  2 Thread 0xb7294b90 (LWP 6773) 0xb7fbb410 in __kernel_vsyscall ()
  1 Thread 0xb7d11940 (LWP 6767) 0xb7fbb410 in __kernel_vsyscall ()

Thread 3 (Thread 0xb7fa7b90 (LWP 6772)):
#0 0xb7fbb410 in __kernel_vsyscall ()
#1 0xb7ed4196 in nanosleep () from /lib/tls/i686/cmov/libpthread.so.0
#2 0x08105c91 in ?? ()
#3 0xb7ecc4fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#4 0xb7e29e5e in clone () from /lib/tls/i686/cmov/libc.so.6

...

Read more...

Revision history for this message
Harald Sitter (apachelogger) wrote :

Moving to fspot since this bug will never get fixed if it is marked to affect kdebase, while it doesn't seem to be related to KDE at all.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Changed in f-spot:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Changed in f-spot:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.