On kde certain kde aps do not launch from docky icon.

Bug #712877 reported by JC
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Docky
New
Low
Unassigned

Bug Description

Kopete and Konsole do not launch from their docked Docky icons. When opened from the menu, they can be managed in docky but do not start from the icon shortcut.

With debug enabled:
john@john-Satellite-A505:~/Documents$ docky --d
[Info 21:04:06.110] Docky version: 2.0.11 Release
[Info 21:04:06.117] Kernel version: 2.6.35.26
[Info 21:04:06.118] CLR version: 2.0.50727.1433
[Info 21:04:06.227] [Gtk] Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
[Debug 21:04:06.305] [SystemService] Using org.freedesktop.UPower for battery information
[Info 21:04:06.357] [Gtk] (for origin information, set GTK_DEBUG): failed to retrieve property `gtk-enable-event-sounds' of type `gboolean' from rc file value "((GString*) 0x12827a0)" of type `gboolean'
[Info 21:04:06.357] [Gtk] (for origin information, set GTK_DEBUG): failed to retrieve property `gtk-enable-input-feedback-sounds' of type `gboolean' from rc file value "((GString*) 0x12829a0)" of type `gboolean'
[Info 21:04:06.427] [DockServices] Dock services initialized.
[Debug 21:04:06.436] [UserArgs] BufferTime = 0
[Debug 21:04:06.436] [UserArgs] MaxSize = 2147483647
[Debug 21:04:06.436] [UserArgs] NetbookMode = False
[Debug 21:04:06.436] [UserArgs] NoPollCursor = False
[Debug 21:04:06.538] [PluginManager] Plugin manager initialized.
[Info 21:04:06.540] [DockController] Setting theme: HUD
[Info 21:04:06.805] [PluginManager] Loaded "Docky.Widgets,1.0".
[Info 21:04:06.806] [PluginManager] Loaded "Docky.Widgets,1.0".
[Info 21:04:06.806] [PluginManager] Loaded "Clock".
[Info 21:04:06.807] [PluginManager] Loaded "Trash".
[Info 21:04:08.360] [Helper] Starting banshee_control.py
[Info 21:04:08.397] [Helper] Starting pidgin_control.py
[Info 21:04:08.402] [Helper] Starting rhythmbox_control.py
[Info 21:04:08.412] [HelperService] Helper added: /usr/local/share/docky/helpers/banshee_control.py
[Info 21:04:08.413] [HelperService] Helper added: /usr/local/share/docky/helpers/deluge_badge.py
[Info 21:04:08.413] [HelperService] Helper added: /usr/local/share/docky/helpers/gajim_badge.py
[Info 21:04:08.413] [HelperService] Helper added: /usr/local/share/docky/helpers/gtg_menus.py
[Info 21:04:08.413] [HelperService] Helper added: /usr/local/share/docky/helpers/liferea_badge.py
[Info 21:04:08.413] [HelperService] Helper added: /usr/local/share/docky/helpers/open_terminal_here.py
[Info 21:04:08.413] [HelperService] Helper added: /usr/local/share/docky/helpers/pidgin_control.py
[Info 21:04:08.413] [HelperService] Helper added: /usr/local/share/docky/helpers/rhythmbox_control.py
[Info 21:04:08.413] [HelperService] Helper added: /usr/local/share/docky/helpers/tomboy_menus.py
[Info 21:04:08.413] [HelperService] Helper added: /usr/local/share/docky/helpers/zeitgeist_docky.py
[Info 21:04:08.417] [HelperService] Helper added: /usr/local/share/docky/helpers/zeitgeist_journal.py
[Info 21:04:08.437] [DrawingService] Could not find 'deluge', using fallback of 'extension'.
[Info 21:04:08.444] [DrawingService] Could not find 'gajim', using fallback of 'extension'.
[Info 21:04:08.462] [DrawingService] Could not find 'gtg', using fallback of 'extension'.
[Info 21:04:08.478] [DrawingService] Could not find 'liferea', using fallback of 'extension'.
[Error 21:04:08.556] [Helper] banshee_control.py :: Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
[Error 21:04:08.707] [Helper] rhythmbox_control.py :: Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
[Fatal 21:04:30.212] [GLib-GIO] g_app_info_launch: assertion `G_IS_APP_INFO (appinfo)' failed
[Fatal 21:04:44.607] [GLib-GIO] g_app_info_launch: assertion `G_IS_APP_INFO (appinfo)' failed
[Fatal 21:05:12.712] [Gtk] gtk_drag_dest_leave: assertion `site != NULL' failed

(Docky:6967): Wnck-WARNING **: Received a timestamp of 0; window activation may not function properly.

(Docky:6967): Wnck-WARNING **: Received a timestamp of 0; window activation may not function properly.

The last two instances were reported after trying to use Kopete and Konsole respectively.
Ubuntu 10.10 x86_64
kubuntu dekstop
kde 4.6
docky 2.0.11

Revision history for this message
JC (nothingness) wrote :

This is also present on the gnome desktop. The programs were downloaded when I downloaded kde 4.6 (kubuntu desktop with kubuntu backports ppa)

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

I'm guessing those GIO fatal errors are the root cause. GIO probably can't figure out how to launch these KDE apps...

Changed in docky:
importance: Undecided → Low
Revision history for this message
JC (nothingness) wrote :

KPackageKit launches from Docky.
Log when launching KPackageKit:
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon

Log for Gnome system monitor:
** (gnome-system-monitor:3941): WARNING **: SELinux was found but is not enabled.

Log for ubuntu software center:
Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `gtk-enable-event-sounds' of type `gboolean' from rc file value "((GString*) 0xff4900)" of type `gboolean'
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `gtk-enable-input-feedback-sounds' of type `gboolean' from rc file value "((GString*) 0xcd0340)" of type `gboolean'
2011-02-04 00:34:32,116 - softwarecenter.fixme - WARNING - logs to the root logger: '('/usr/share/software-center/softwarecenter/view/widgets/mkit_themes.py', 675, 'retrieve')'
2011-02-04 00:34:32,116 - root - WARNING - No styling hints for Bluebird were found... using Human hints.
Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory

It loads though.
In my home folder I edited ".gconf/desktop/gnome/sound/%gconf.xml" and:
<entry name="event_sounds" mtime="1296762120" type="bool" value="false"/>
</gconf>
I changed the initial "true" to "false." That might might be why a lot of the gtk enable-event-sounds might be showing up in my logs.

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

We really dont care about any log messages from other programs, they are completely useless to us.

And the fact it runs other (kde) programs has little bearing. The problem is that GIO (for whatever reason) could not run those 2 specific programs - you can see GIO complain about a lack of GAppInfo. So the question becomes: why can't it find a AppInfo's for those two programs.

And even more interesting (to me) the question is: is this a GIO or a Docky problem. I am leaning towards it being a GIO problem.

Revision history for this message
JC (nothingness) wrote :

I can confirm that on a clean install of kubuntu, the programs all launch correctly. So it's some sort of clash between gnome and kde (when both are present).
The docky trash icon can't load though without gnome's nautilus, though, I don't expect anything different since this is a gnome app. Though it was worth mentioning.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

As Chris Coulson wite on another report:
This definitely isn't a gnome-session bug, and those errors in the linked bug are not a GIO bug either. Those messages are caused by applications using the API incorrectly

Revision history for this message
Ayberk Özgür (equilibriumtr) wrote :

More than 6 years later this bug still exists and I'd like to share what caused this for me. There was a `Path[$e]=` entry in my `.desktop` file. Changing it to `Path=` solved it.

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.