docky crashes after some time after startup

Bug #647072 reported by Trekkele
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Docky
Fix Released
Medium
Robert Dyer

Bug Description

Description:
Docky crashes unexpectedly after some time, leaving mouse cursor totally "paralyzed" until Docky is restarted (keyboard is ok).

Affects:
- Archlinux
- Ubuntu 10.04

Computer:
Dell Inspiron 15

Hardware:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)
0c:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100

GNOME: 2.30.2 (Archlinux only)

Mono: 2.6.7-1 (Archlinux only)

Revision history for this message
Robert Dyer (psybers) wrote :

We absolutely have to get a stack trace from the crash, or there is *nothing* we can do for you.

Also, when reporting crashing about a program it is quite prudent to report the version of the program (that crashed).

Are there steps to reproduce this crash consistently? If so, what are they?

To get a stack trace, run docky from a terminal as 'docky -d' and then copy/paste the log output here. If you can not consistently reproduce it, the stack trace might already be in your ~/.xsession-errors file - if this is the case please TRIM the file to just the relevant parts and post it here.

Changed in docky:
status: New → Incomplete
importance: Undecided → Medium
assignee: nobody → Jason Smith (jassmith)
Revision history for this message
Trekkele (trekkele) wrote :

Docky version: 2.0.6-1 (Archlinux only)

Unfortunately there seems to be no way to reproduce the bug, it *just happens*.
The only thing I have noticed is it tends to happen when wireless networks are detected or when network manager connects to one of the wireless networks available.

I have created a personalized launcher by myself, which forces docky to wait 5 seconds after login before starting up, in order to let network manager connect, but it's nothing more than a workaraound.

Docky is mentioned only once in my current .xsession-errors file, here comes the code:

** Message: pygobject_register_sinkfunc is deprecated (GtkWindow)
** Message: pygobject_register_sinkfunc is deprecated (GtkInvisible)
** Message: pygobject_register_sinkfunc is deprecated (GtkObject)
[Info 18:12:50.618] Docky version: 2.0.6 Release
[Info 18:12:50.731] Kernel version: 2.6.35.0
[Info 18:12:50.733] CLR version: 2.0.50727.1433

I hope these few lines of code can help you!

Revision history for this message
Robert Dyer (psybers) wrote :

No, we need a stack trace. For all we know this is a duplicate of another bug or possibly a bug that is already fixed in 2.1.0.

Revision history for this message
Trekkele (trekkele) wrote :
Download full text (3.4 KiB)

Update:

I just started ubuntu and the bug showed up again. As usual, as soon as NM detects a network, docky goes down.

This is the code from .xsession-errors:

** (nm-applet:5648): WARNING **: applet-device-wifi.c.1597 (get_secrets_dialog_response_cb): canceled
** (nm-applet:5648): DEBUG: old state indicates that this was not a disconnect 9
[Info 09:43:20.242] [DrawingService] Could not find 'gajim', using fallback of 'extension'.
[Debug 09:43:20.332] [AbstractWeatherSource] Weather Channel: reload success
[Warn 09:43:20.486] [DrawingService] Error loading icon from file '/usr/share/pithos/media/icon.svg': Apertura del file «/usr/share/pithos/media/icon.svg» non riuscita: Nessun file o directory
[Debug 09:43:20.490] [DrawingService] at Gdk.Pixbuf..ctor (System.String filename, Int32 width, Int32 height, Boolean preserve_aspect_ratio) [0x00000]
  at Docky.Services.DrawingService.IconFromFile (System.String name, Int32 width, Int32 height) [0x0005a] in /build/buildd/docky-2.1.0~bzr1641/Docky.Services/Docky.Services/DrawingService.cs:329
[Info 09:43:20.490] [DrawingService] Could not find '/usr/share/pithos/media/icon.svg', using fallback of 'extension'.
Exception in Gtk# callback delegate
  Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception.
System.ArgumentOutOfRangeException: Alpha must be between 0 and 1
Parameter name: Alpha
  at Cairo.Color_Extensions.SetAlpha (Color self, Double alpha) [0x0001e] in /build/buildd/docky-2.1.0~bzr1641/Docky.CairoHelper/Cairo/Color_Extensions.cs:71
  at Docky.Interface.DockWindow.DrawActiveIndicator (Docky.CairoHelper.DockySurface surface, Rectangle area, Color color, Double opacity) [0x00121] in /build/buildd/docky-2.1.0~bzr1641/Docky/Docky/Interface/DockWindow.cs:2475
  at Docky.Interface.DockWindow.DrawItem (Docky.CairoHelper.DockySurface surface, Rectangle dockArea, Docky.Items.AbstractDockItem item) [0x00780] in /build/buildd/docky-2.1.0~bzr1641/Docky/Docky/Interface/DockWindow.cs:2422
  at Docky.Interface.DockWindow.DrawDock (Docky.CairoHelper.DockySurface surface) [0x00141] in /build/buildd/docky-2.1.0~bzr1641/Docky/Docky/Interface/DockWindow.cs:2127
  at Docky.Interface.DockWindow.OnExposeEvent (Gdk.EventExpose evnt) [0x000c3] in /build/buildd/docky-2.1.0~bzr1641/Docky/Docky/Interface/DockWindow.cs:2690
  at Gtk.Widget.exposeevent_cb (IntPtr widget, IntPtr evnt) [0x00000]
   at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal)
   at Gtk.Widget.exposeevent_cb(IntPtr widget, IntPtr evnt)
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at Docky.Docky.Main(System.String[] args) in /build/buildd/docky-2.1.0~bzr1641/Docky/Docky/Docky.cs:line 95
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
** (nm-applet:5648): DEBUG: going for offline with icon: notification-network-wireless-disconnected

(gnome-termi...

Read more...

Revision history for this message
Robert Dyer (psybers) wrote :

Fixed in rev 1646.

Changed in docky:
assignee: Jason Smith (jassmith) → Robert Dyer (psybers)
status: Incomplete → Fix Committed
milestone: none → 2.0.7
Changed in docky:
status: Fix Committed → Fix Released
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.