Version: (using 3.5.8, Kubuntu (gutsy) 4:3.5.8-0ubuntu3.1) Compiler: Target: x86_64-linux-gnu OS: Linux (x86_64) release 2.6.22-14-generic When clicking on adept_notifier, it askes for passphrase and gives launch-feedback, but adept does not start. Same when starting adept directly over k-menu. There are no error-messages in console when starting adept_manager from there. Although after the Window of Adept is drawn I get some "Error: "/var/tmp/kdecache-k" is owned by uid 1000 instead of uid 0." Dont know if this is important. karl
When starting it with option checked "start in terminal" same problem: Asking for passphrase in the terminal but nothing is started. I want to make clear, that starting adept_manager via "sudo adept_manager" adept is started. Please tell me how I can get a useful debugging output
Good question, I have no idea.... Can you maybe check .xsession-errors maybe in your $HOME?
here what I think may be important for tracking the error. ~/.xsession-errors ----------------------------------------------------------- X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x32000c3 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x14015f9 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x14015f9 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x14015f9 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x14015f9 passprompt Xlib: connection to ":0.0" refused by server Xlib: No protocol specified adept_updater: cannot connect to X server :0.0
when trying to switch to SU-Mode in SystemSettings, same error: ------------------------- X Error: BadWindow (invalid Window parameter) 3 Major opcode: 6 Minor opcode: 0 Resource id: 0x3c0098a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 12 Minor opcode: 0 Resource id: 0x3c0098a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 12 Minor opcode: 0 Resource id: 0x3c0098a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 8 Minor opcode: 0 Resource id: 0x3c0098a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 12 Minor opcode: 0 Resource id: 0x3c0098a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 12 Minor opcode: 0 Resource id: 0x3c0098a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 25 Minor opcode: 0 Resource id: 0x3c0098a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 25 Minor opcode: 0 Resource id: 0x3c0098a Xlib: connection to ":0.0" refused by server Xlib: No protocol specified kcmshell: cannot connect to X server :0.0
This is then a problem with your X server permissions -- and maybe how kdesu works. I cannot give you much better hint than trying to ask in some support forum, about your kdesu issue. You can try playing with xhost and see if that helps, but opening up your server fully (xhost +) is at best a temporary solution. You will need to find out what's going on in kdesu, I suppose. Nevertheless, this is not an Adept problem, so I'll close this report. If you have enough information, you might want to open a new report againts kdesu (if it turns out to be a bug there, as opposed to misconfiguration somwhere on your system). Also, sorry for the delays...