Description of problem: Lately I've noticed that apps that I set to autostart at login (in Session and Startup/Application Autostart) stopped working. Specifically, the apps that I'm trying to run are keepassx and bluedevil-monolithic. When logging out then back in, apps are started -- but not after first boot/login.
Is this under xfce4-session-4.10.1-3?
yes
Is there anything related to those apps in ~/.xsession-errors ?
No
also, looks like these apps are running in the system, but there's no sign of them in the systray...
Is this by any chance specific to these applications? I have guake and dropbox (dropbox not installed using rpm) in the startup and they start fine.
No idea; if only one of them wasn't showing up, I would've filed a bug against it.. but since it's more than one, it's likely something they have in common. BTW, I have yum btrfs snapshots going back to May 7 -- looks like that one doesn't start these apps, either..
I use keepassx here and it autostarts for me just fine. ;( Can you perhaps attach your ~/.cache/sessions/xfce4-session-* files? and make sure you have it set to save session on logout, or that you save session now from the sessions and startup applet?
There are no files in that directory.. I got used to not saving sessions because of a years old bug that would make startup very slow when reading from a session. No idea if it ever got fixed, but I'm pretty happy without sessions... Are you saying that using sessions would fix this bug? Or.. don't tell me -- I need to create a new user profile to fix this crap?? Just an idea -- since the apps show as running in process list but not in the systray.. is it possible they start up too early while systray is not initialized yet?
(In reply to Konstantin Svist from comment #9) > There are no files in that directory.. > I got used to not saving sessions because of a years old bug that would make > startup very slow when reading from a session. No idea if it ever got fixed, > but I'm pretty happy without sessions... If you mean the bug that caused it to start a bunch of duplicate applications, then yeah, it was fixed a while back. > Are you saying that using sessions would fix this bug? > Or.. don't tell me -- I need to create a new user profile to fix this crap?? No. I was just trying to figure out your configuration so I could isolate where the bug was. No need to get upset. > Just an idea -- since the apps show as running in process list but not in > the systray.. is it possible they start up too early while systray is not > initialized yet? It is... we have been seeing this with xfce4-power-manager as well of late. If you login, don't see them, kill those processes and restart them, they show up in the systray?
(In reply to Kevin Fenzi from comment #10) > If you mean the bug that caused it to start a bunch of duplicate > applications, then yeah, it was fixed a while back. Don't remember duplicates, but remember slow login process :) > No. I was just trying to figure out your configuration so I could isolate > where the bug was. No need to get upset. Ok, no problem, I can try it. > It is... we have been seeing this with xfce4-power-manager as well of late. > > If you login, don't see them, kill those processes and restart them, they > show up in the systray? That's exactly what I see, yes
Just found this in .xsession-errors, sounds like it's related QSystemTrayIcon::setVisible: No Icon set No systemtrayicon available No systemtrayicon available libpager-Message: Setting the pager rows returned false. Maybe the setting is not applied. No systemtrayicon available
Yeah, it has to be some ordering issue on startup where it's not starting the systray before things that need it. Would you like to file this upstream? Or would you like me to do so?
Please file it upstream
Done. https://bugzilla.xfce.org/show_bug.cgi?id=11019 Thanks for the report.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Issue still present
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.