Hide Forgot
Created attachment 502788 [details] startx.log Description of problem: There are lxpolkit errors on LXDE startup. Version-Release number of selected component (if applicable): lxpolkit.i686 0.1.0-0.2.20100402git5087383.fc15 @koji-override-0/$releasever How reproducible: Start LXDE in text mode. $ alias alias startx='/usr/bin/startx -- -nolisten tcp > ~/.startx.log 2>&1' Steps to Reproduce: 1. $ startx 2. 3. Actual results: See startx.log attachment. Expected results: No errors. Additional info:
What error are you referring to extactly? What is the consequence of that error, I mean, what exactly does not work?
(In reply to comment #1) > What error are you referring to extactly? What is the consequence of that > error, I mean, what exactly does not work? See attachment: ... ** (lxpolkit:20948): CRITICAL **: polkit_agent_listener_register: assertion `POLKIT_IS_SUBJECT (subject)' failed (lxpolkit:20948): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ... They are, I assume, errors from autostarted LXPolKit configured in Preferences - Desktop Session Settings. These are critical errors ! Assertions usually mean program errors as a result of run-time invalid data. Why issue them and pollute logs if they are of no consequence ? JB
Ask the developer, not the package maintainer. These warnings indicate a problem with the code: An assumption the developer made was invalidated. But if this does not affect the runtime of the program and there is no abnormal behavior of the application, there is nothing we need to track in Fedora's issue tracker. Note that I am not the developer of the code, I am just the maintainer for Fedora. The problems are in the code and not specific to Fedora. If you want the code to be fixed, please file a bug in LXDE's issue tracker and provide it as upstream reference to this bug. You can use the URL field for that. Once the bug in LXDE's tracker is fixed, I'm happy to provide an update for Fedora.
(In reply to comment #3) > Ask the developer, not the package maintainer. > > These warnings indicate a problem with the code: An assumption the developer > made was invalidated. But if this does not affect the runtime of the program > and there is no abnormal behavior of the application, there is nothing we need > to track in Fedora's issue tracker. > > Note that I am not the developer of the code, I am just the maintainer for > Fedora. The problems are in the code and not specific to Fedora. If you want > the code to be fixed, please file a bug in LXDE's issue tracker and provide it > as upstream reference to this bug. You can use the URL field for that. > > Once the bug in LXDE's tracker is fixed, I'm happy to provide an update for > Fedora. OK, so we are on the same page now. You see, there are different schools about who should we report the bugs to and who should pass the bugs to upstream maintainer. Many think that the package maintainer should do it, as this would allow her to keep track of the state of the package and be in contact with the upstream crew, which would be beneficial to her. That's why I filed it here and I assumed that you would pass it upstream. OK. So will do it. JB
Did you do it in the meantime? Please don't forget to add a link to the upstream bug report. TIA!
(In reply to comment #5) > Did you do it in the meantime? Please don't forget to add a link to the > upstream bug report. TIA! Added URL.
Thanks Jurek! I am monitoring the upstream bug and will issue an update for Fedora as soon as there is a fix in the upstream bug report. From now on we'll track this issue @ sourceforge, so I'm going to close this bug.