doesnt open in edgy

Bug #55782 reported by John Vivirito
86
Affects Status Importance Assigned to Milestone
kxdocker (Ubuntu)
Invalid
Medium
Unassigned
Nominated for Edgy by Emmet Hikory
Nominated for Feisty by Emmet Hikory

Bug Description

Binary package hint: kxdocker

when i try to open it from terminal i get:
gnomefreak@EdgyEft:~$ kxdocker
Error: KXDocker cannot find Composite Extensions
X Error: BadDevice, invalid or uninitialized input device 154
  Major opcode: 143
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 154
  Major opcode: 143
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kxdocker: WARNING: Cannot find updated resources: you may need to update or reinstall KXDocker resources, checkout http://www.xiaprojects.com/www/prodotti/kxdocker/main.php?action=download#resources
kxdocker: WARNING: loading xml...
kxdocker: WARNING: Warning user kxdocker_conf.xml may be corrupt: loading last backup!
kxdocker: WARNING: Warning user, and backup configurations are corrupt! I'm going to load system kxdocker_conf.xml !!!
kxdocker: WARNING: Warning user, backup, system configurations are corrupt! please install right kxdocker_conf.xml
ERROR: Communication problem with kxdocker, it probably crashed.

im gonna attach a strace

Tags: patch
Revision history for this message
John Vivirito (gnomefreak) wrote :
Revision history for this message
John Vivirito (gnomefreak) wrote :

I dont seem to have this issuse after re-installing kxdocker.

Changed in kxdocker:
status: Unconfirmed → Rejected
Revision history for this message
John Anderson (john-e-anderson) wrote :

I am seeing this bug, installed Edgy beta and it won't start. it's a pretty similar error.

KXDocker Will use Composite Extensions!
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kxdocker: WARNING: Cannot find updated resources: you may need to update or reinstall KXDocker resources, checkout http://www.xiaprojects.com/www/prodotti/kxdocker/main.php?action=download#resources
kxdocker: WARNING: loading xml...
kxdocker: WARNING: Warning user kxdocker_conf.xml may be corrupt: loading last backup!
kxdocker: WARNING: Warning user, and backup configurations are corrupt! I'm going to load system kxdocker_conf.xml !!!
kxdocker: WARNING: Warning user, backup, system configurations are corrupt! please install right kxdocker_conf.xml
ERROR: Communication problem with kxdocker, it probably crashed.

Revision history for this message
Steveire (steveire) wrote :

I get the same output when I run kxdocker from the terminal. I'm using edgy beta too.

Revision history for this message
Lorenzo J. Lucchini (ljl) wrote :

I can confirm this. It still happens after the recommended package "kxdocker-data" is installed.

Revision history for this message
Lorenzo J. Lucchini (ljl) wrote :

I do still have the issue, even after reinstalling after a purge.

Changed in kxdocker:
status: Rejected → Confirmed
Revision history for this message
Hagbarddenstore (hagbarddenstore) wrote : Edgy Eft.

It's broken for me too. Think I'm gonna make a new package for it.

Revision history for this message
Brian Pitts (bpitts) wrote :
Download full text (15.2 KiB)

It doesn't crash for me, but no icon appears in kicker's tray and the dock itself never appears.

dpkg --purge kxdocker-data
dpkg --purge kxdocker
apt-get install kxdocker kxdocker-data
kxdocker

KXDocker Will use Composite Extensions!
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kxdocker: WARNING: Cannot find updated resources: you may need to update or reinstall KXDocker resources, checkout http://www.xiaprojects.com/www/prodotti/kxdocker/main.php?action=download#resources
kxdocker: WARNING: loading xml...
kxdocker: WARNING: saving xml configuration to backup configuration...
kxdocker: WARNING: loading plugins...
/usr/share/apps/kxdocker/plugins/libxRoot.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxRoot.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/liblibxRoot.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxRoot.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxRoot.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/liblibxRoot.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxRoot.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxRoot.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/liblibxRoot.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxEvents.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxEvents.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/liblibxEvents.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxEvents.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxEvents.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/liblibxEvents.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxEvents.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxEvents.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/liblibxEvents.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxDocker.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxDocker.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/liblibxDocker.so: cannot open shared object file: No such file or directory
/usr/share/apps/kxdocker/plugins/libxDocker.so: cannot open shared object file: No such file or director...

Revision history for this message
Paulo (pauloerweber) wrote :

We had two bugs heres.
1- There are missing config files: /usr/share/apps/kxdocker/kxdocker_conf_default.xml and /usr/share/apps/kxdocker/kxdocker_conf.xml. Actually the files exist, but they are empty! :|
2- The package kxdocker-data don't contain all the plugins necessary to kxdocker work. So even if the config files of a older version kxdocker will not load the plugins, like Brian said it above.
All this problems are caused by the packaging. Some one send a email to the package maintainer?

Revision history for this message
wouf (woufmail) wrote :

Same bug here.
Kubuntu Edgy Eft :

KXDocker Will use Composite Extensions!
kxdocker: WARNING: Cannot find updated resources: you may need to update or reinstall KXDocker resources, checkout http://www.xiaprojects.com/www/prodotti/kxdocker/main.php?action=download#resources
kxdocker: WARNING: loading xml...
kxdocker: WARNING: Warning user kxdocker_conf.xml may be corrupt: loading last backup!
kxdocker: WARNING: Warning user, and backup configurations are corrupt! I'm going to load system kxdocker_conf.xml !!!
kxdocker: WARNING: Warning user, backup, system configurations are corrupt! please install right kxdocker_conf.xml
ERROR: Communication problem with kxdocker, it probably crashed.

Revision history for this message
Viegas (viegas-dev) wrote :

I also have the same error after upgrading from dapper to edgy... kxdocker worked fine before.
Anyone have a workarround instead of compiling from source a new package?
Basically it seams we're just missing a bunch of files. Can't we get them somewhere?

Revision history for this message
Viegas (viegas-dev) wrote :

One more thing... this happens in the final version of edgy and not just on the beta.

Revision history for this message
Viegas (viegas-dev) wrote :

Been trying to set it up by hand without breaking the future upgrade process but is simply too much to copy and build.
Can we get an estimated time to release an update of the package?
I've managed to get it running but with the configurator, and a minimal plugins... not so fancy looking like it's supposed to and have to configure all by hand on the XML file! :-(

Revision history for this message
Vítor E. Silva Souza (vitorsouza) wrote :

There is a workaround to continue using kxdocker until they fix it, although in an much earlier version: installing DEB packages from Debian Testing repository.

See: http://www.ubuntuforums.org/showthread.php?t=294418

ville palo (vi64pa)
Changed in kxdocker:
assignee: nobody → vi64pa
Revision history for this message
ville palo (vi64pa) wrote :

Here' s a SRU for this bug #74862
It doesn't fix the -data package though

Revision history for this message
ville palo (vi64pa) wrote :

And here's a fix for feisty

Changed in kxdocker:
assignee: vi64pa → motureviewers
Changed in kxdocker:
assignee: motureviewers → nobody
Revision history for this message
Viegas (viegas-dev) wrote :

Don't understand how the debdiff is suposed to be used in order to fix the problem.
Can anybody help?
Also, this does not solve the problem with the missing plugins and other resources like the configurator, right?
I have build a sample and working xml configuration file witch apparently is the only thing this patch does right? Please give instructions on how to use this and if this is the fix or just a temp workarround.
5 months have passed, when is an updated package be released? The kxdocker is fine the only problem is the package, please repackage and distribute in the apt-get stream.

Revision history for this message
elakug (elakug) wrote :

this is still not working. who's assigned to this bug?
its a great app. i really miss it.

plerk

Revision history for this message
ville palo (vi64pa) wrote :

kxdocker.debdiff only fixes the xml files. It could be better to report a new bug for kxdocker-package about the other issue.

Changed in kxdocker:
assignee: nobody → vi64pa
importance: Undecided → Medium
Revision history for this message
ville palo (vi64pa) wrote :

This will be fixed in edgy when/if sru request bug #74862 is accepted.

ville palo (vi64pa)
Changed in kxdocker:
status: Confirmed → In Progress
Revision history for this message
John Vivirito (gnomefreak) wrote :

This is a problem in feisty as well

Revision history for this message
ville palo (vi64pa) wrote :

Fixed kxdocker package (1.1.4a-0ubuntu2.1~proposed1) is now in edgy proposed, please test it and if it works add a comment to SRU request bug #74862

Thank you.

Revision history for this message
eppy 1 (choppy121212) wrote :

Can you fix the kxdocker in Feisty (now since released) as well?

I've seen Bug 105423 and Bug 89747 as dupes as this but for Feisty.

Revision history for this message
Ateo (amoeba-x) wrote :

I downloaded kxdocker-resources, just like it said, and it didn't install anything after installing it.

The tarball contains a plugin, theme and sound folder. The plugin folder has the same content found in kxdocker-data. In other words, it does not supply the libs it's looking for.

this appears to be an upstream bug. kxdocker (this version) should be yanked from the repositories until resolved.

Additionally, kxdocker appears dead. As of April 23, 2007, the project is now XQDE...

http://www.xiaprojects.com/www/prodotti/kxdocker/main.php?action=download

I have found that version kxdocker_0.35-2.2+b1_i386.deb of kxdocker works adequately.

Revision history for this message
Emmet Hikory (persia) wrote :

Thank you for the extended effort in attempting to resolve this issue. My apologies that the patch has not recieved revew. I've unassigned it, and set "Confirmed" instead of "In Progress", just because there hasn't been progress in a while, and at this point it needs to be fixed in gutsy before it can be fixed in feisty or edgy. I've added the patch tag in case someone else wants to respin the debdiff for gutsy. I've unsubscribed ubuntu-universe-sponsors, as the current debdiffs cannot be uploaded until it is fixed in the current development version (and may need adjustment, given the time, and possible changes in policy). Please resubscribe when a gutsy debdiff is generated to request sponsorship of the upload.

Changed in kxdocker:
assignee: vi64pa → nobody
status: In Progress → Confirmed
Revision history for this message
John Vivirito (gnomefreak) wrote :

I took this to build in patch for feisty.
I think it would be a good idea to remove this from gutsy and replace with new package XQDE. I will file a bug on it and if someone want sto do it go for it.

Changed in kxdocker:
assignee: nobody → gnomefreak
status: Confirmed → In Progress
Revision history for this message
John Vivirito (gnomefreak) wrote :

After looking it over i have decided to not fix this for feisty as the fix would have to be in gutsy first. there have been no upstream fixes since edgy. Please see bug #119702 for more info. Once its replaced in gutsy I will see about asking if i can backport it to feisty but one step at a time.

Changed in kxdocker:
assignee: gnomefreak → nobody
status: In Progress → Rejected
Revision history for this message
Martin Pitt (pitti) wrote :

Nobody tested the -proposed upload and gave feedback here for more than 10 months, and I guess nobody cares about edgy universe any more, so I removed the edgy-proposed package.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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