kdesu often hang while starting programs

Bug #55053 reported by Christmas
This bug report is a duplicate of:  Bug #50971: kdesu will not start apps. Edit Remove
12
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Confirmed
Medium
Kubuntu Bugs

Bug Description

Binary package hint: adept

Sometimes the Adept Updater or Adept Package Manager fails to start. It won't prompt for the password, only the second or even the third time it starts. I'm using Kubuntu Dapper with all the updates on a P4 2800 MHz with 512 RAM.

Revision history for this message
Dean Sas (dsas) wrote : Re: Adept Fails to Start

Do you get any output if you run adept from a konsole?

Changed in adept:
status: Unconfirmed → Needs Info
assignee: nobody → kubuntu-team
Revision history for this message
Christmas (christmas) wrote :

Yes, I get output. I just tried now and here it is:

christmas@floydian:~$ kdesu adept
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

And after this it does nothing. It won't start. Sometimes it does, sometimes it doesn't. The same with the updater and I also noticed that sometimes even after I enter my password the updater fails to start.

Kenny Duffus (kduffus)
Changed in adept:
importance: Untriaged → Medium
Dean Sas (dsas)
Changed in adept:
status: Needs Info → Unconfirmed
Revision history for this message
d selby (kbmaniac) wrote :

Same with edgy though not as bad as dapper.

Click on adept manager, it starts most of the time but sometimes nothing happens, usually get the kdesu login on the second attempt.

I guess this is a confirmation ?

Revision history for this message
Anton_K (antonk89) wrote :

It seems to be a kdesu problem...

Revision history for this message
Laur Mõtus (vprints) wrote :

Confirming for Edgy AND Feisty.
In both, if I click on adept from the menu or adept updater there is about 50% chance that it won't start. The cursor starts bouncing like it would hae launched, but I have even waited for it (just in case) for 10 minutes and noting still happens. And then I click for the second time and it launches just fine.

Changed in adept:
status: Unconfirmed → Confirmed
Revision history for this message
ivan (ivan.tg) wrote :

hi,
another comfirmation for edgy. It seems quite random. Sometimes it fails several times consecutively.
It really has to do something with kdesu since launching from Konsole (either with "adept" or "sudo adept" never fails)

Revision history for this message
Paul Dufresne (paulduf) wrote :

Yeah, I do lots of kdesu whoami to test kdesu,
and it does it about 1 on 10 times.
I agree with Anton_K that this is a kdesu problem.

Each time kdesu does it to me, it leave in the process
tree it's marks:
ps -eH
...
 5083 ? 00:00:31 konsole
 5120 pts/1 00:00:01 bash
 9249 pts/1 00:00:00 kdesu
 9252 pts/3 00:00:00 kdesu_stub
 9255 pts/5 00:00:00 sudo
(actually I had ask kdesu whoami here)
...
 6656 ? 00:00:00 kdesu_stub
 6663 ? 00:00:00 sh
 6664 ? 00:00:10 kcmshell
(I think when I asked kdesu kcmshell mountconfig)

So I'll move this bug to kdesu, which is in kdebase package.

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.