On Wednesday 04 June 2008, Arjan van de Ven wrote: > Frans Pop wrote: > > On Wednesday 04 June 2008, Arjan van de Ven wrote: > >> Any user needs to be in a GUI for the popup "ask permission" window > >> to come up. However, this can be asynchronous. In "ASK" mode the > >> daemon just holds on to the oopses until the GUI application starts. > >> The application will then notify the daemon it's there and some > >> communication will happen. At that point the window should then pop > >> up asking for permission. > > > > Hmm. Then I do still wonder why I've not been asked. I have a KDE > > desktop environment, but I thought that was supported. Although I'm > > not sure that KDE supports /etc/xdg/autostart. Starting > > kerneloops-applet manually works, but does not result in anything. > > > > Any checks/tests I can do to see what's missing? > > dbus-monitor --system > > should record the kerneloops traffic between the daemon and the GUI... > would be interesting to see what's communicated.
OK, more info on this. Today I had one of those known "sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists" warnings, so I thought that would be a good test. The kerneloops daemon was already running, the client was not. So first I tried just 'kerneloops-applet &' in a KDE konsole shell. Same nothing as previously. Then I tried the same with sudo, and at last something happens: - I get *two* icons in the KDE applet panel: small tux and larger tux. - Does the larger tux mean there is something active to be done (like report the parport warning)? - Neither icon seems to "do" anything on click, right click etc. - I do not get a pop-up asking me if I want to submit the warning - I get the following processes: 15845 pts/2 S 0:00 kerneloops-applet 15846 pts/2 S 0:00 kerneloops-applet 15850 pts/2 S 0:00 dbus-launch --autolaunch 496e4345abd6e71a433b7ccb68a03100 --binary-syntax --close-stderr 15851 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session - I probably should have killed 15845 (regular users) before starting 15846 (sudo)... :-( - Does the fact that I only get the dbus-launch and dbus-daemon fork when I use sudo mean that it is needed or that there is some problem in the kerneloops packaging? - Or, how should I be starting the applet for it to work correctly? Should it be run as root or as "user logged on to X"? - Killing 15845 makes the small tux go away. - Remaining larger tux still not responsive. - In the end I killed everything. Hope this helps. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
