Fedora 20 64 bit XFCE
When logging out from gui I get:
"Received error while trying to log out Session manager must be in idle state when requesting a shutdown."
Each time I reboot a number of windows/tabs are loaded, I go through and close them all.
However there is garbage running when I look at ctrl-alt-F1 and XFCE is in ctrl-alt-F2.
There must be a command to kill everything but I haven't found it.
Need help please,
Bob
On 09/02/14 13:23, Bob Goodwin - Zuni, Virginia, USA wrote:
Fedora 20 64 bit XFCE
When logging out from gui I get:
"Received error while trying to log out Session manager must be in idle state when requesting a shutdown."
Each time I reboot a number of windows/tabs are loaded, I go through and close them all.
However there is garbage running when I look at ctrl-alt-F1 and XFCE is in ctrl-alt-F2.
There must be a command to kill everything but I haven't found it.
Need help please,
Bob
I worked around the problem by creating a new user, that will have to do!
Bob
On 2/9/2014 8:21 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
On 09/02/14 13:23, Bob Goodwin - Zuni, Virginia, USA wrote:
Fedora 20 64 bit XFCE
When logging out from gui I get:
"Received error while trying to log out Session manager must be in idle state when requesting a shutdown."
Each time I reboot a number of windows/tabs are loaded, I go through and close them all.
However there is garbage running when I look at ctrl-alt-F1 and XFCE is in ctrl-alt-F2.
There must be a command to kill everything but I haven't found it.
Need help please,
Bob
I worked around the problem by creating a new user, that will have to do!
Bob
Most users here use KDE or Gnome so I doubt they can help you with a Xfce problem.
When I offer advice here I am usually ignored. I have offered you advice before with similar results. I know how to solve this but I choose not to give you the information.
But? Want a suggestion? A good one? Ask on the Xfce list. Either the Fedora one (second choice but not a bad one) or the real Xfce list (first choice and a better choice IMO).
On 10.02.2014 02:21, Bob Goodwin - Zuni, Virginia, USA wrote:
On 09/02/14 13:23, Bob Goodwin - Zuni, Virginia, USA wrote:
Fedora 20 64 bit XFCE
When logging out from gui I get:
"Received error while trying to log out Session manager must be in idle state when requesting a shutdown."
Each time I reboot a number of windows/tabs are loaded, I go through and close them all.
However there is garbage running when I look at ctrl-alt-F1 and XFCE is in ctrl-alt-F2.
There must be a command to kill everything but I haven't found it.
Need help please,
Bob
I worked around the problem by creating a new user, that will have to do!
Bob
That is always a valid choice, however 'xfce4-session-settings', http://docs.xfce.org/xfce/xfce4-session/preferences#session ;)
If that doesn't help, man 1 loginctl
poma
On 09/02/14 21:06, David wrote:
When I offer advice here I am usually ignored. I have offered you advice before with similar results. I know how to solve this but I choose not to give you the information.
My apologies David, I try to acknowledge everyone. I also feel this accusation is unjust without specifics ...
Ask on the Xfce list.
I am aware of, and have at times subscribed to, the xfce list. I may do that.
Thank you,
Bob
On Sun, 09 Feb 2014 21:06:24 -0500 David dgboles@gmail.com wrote:
Most users here use KDE or Gnome so I doubt they can help you with a Xfce problem.
I use Xfce.
There are also Fedora lists for Gnome and KDE,
this is a Fedora user list, not specific to DE X
<snipped>
But? Want a suggestion? A good one? Ask on the Xfce list. Either the Fedora one (second choice but not a bad one) or the real Xfce list (first choice and a better choice IMO).
Myabe Bob, has more than one DE installed, it might be some other churn. I havn't looked into it. I use Xfce exclusively and don't' have this problem.
I wouldn't ever ask on an upstream list, unless knowing for certain in was a bug in their code. You can get the "worksforme" answer quite easily, with most upstream whether, Xfce, KDE, Calibre etc..
___ Regards Frank frankly3d.com
On Sun, 09 Feb 2014 20:21:28 -0500 "Bob Goodwin - Zuni, Virginia, USA" bobgoodwin@wildblue.net wrote:
I worked around the problem by creating a new user, that will have to do!
Bob
That was using a sledgehammer for toilet paper. In Xfce > Application Menu > Settings > Session and Startup > Session > "Clear Saved Session"
If you do not want any programs started except those that are in Application Autostart: As above but: > Session and Startup > uncheck Logout Settings "Automatically save session on Logout"
___ Regards Frank frankly3d.com
On 10/02/14 04:43, Frank Murphy wrote:
That was using a sledgehammer for toilet paper. In Xfce > Application Menu > Settings > Session and Startup > Session > "Clear Saved Session"
If you do not want any programs started except those that are in Application Autostart: As above but: > Session and Startup > uncheck Logout Settings "Automatically save session on Logout"
Regards Frank frankly3d.com
I've done those things early this morning.
Clear Saved Session got rid of the stuff it insisted on running after start up but xfce4 is still running in the second console while the first console is displaying junk. I can try entering stuff in console F1 but it has no effect or at least ignores commands. Stopping/killing that first console is what it needs/ My attempts with "logctl" have not been successful either, Got to feed horses, be back shortly,
Bob
On 09/02/14 21:22, poma wrote:
I worked around the problem by creating a new user, that will have to do!
Bob
That is always a valid choice, however 'xfce4-session-settings', http://docs.xfce.org/xfce/xfce4-session/preferences#session ;)
If that doesn't help, man 1 loginctl
poma
That helped although I did not expect it to since nothing showed up under "Sessions?" That was blank, however after I clicked
"Clear Saved Session" and rebooted xfce stopped bringing up all those pages as it had been ...
Xfce is still coming up on console 2. I need to stop whatever causes console 1 to be active. It appears to be happening when xfce4 starts since it sits displaying a small progress circle until something "times-out" and then switches to the usual larger circle before running?
Nothing I did with loginctl worked, it showed only USER bobg 1000 Seat0, nothing else unless I ssh'd in from this computer. Nothing I did appeared to have any effect on or even recognize what was going on on console 1.
But the sledgehammer [bobG, new user] works!
Bob
On Mon, 10 Feb 2014 08:17:07 -0500 "Bob Goodwin - Zuni, Virginia, USA" bobgoodwin@wildblue.net wrote:
Xfce is still coming up on console 2. I need to stop whatever causes console 1 to be active. It appears to be happening when xfce4 starts since it sits displaying a small progress circle until something "times-out" and then switches to the usual larger circle before running?
Remove rhgb and quite from the kernel line during bootup. See if you can spot something.
If not wait till you login and: journalctl -b | grep timeout # or whatever is the correct "time-out" you see.
___ Regards Frank frankly3d.com
On 10/02/14 08:22, Frank Murphy wrote:
Xfce is still coming up on console 2. I need to stop whatever causes console 1 to be active. It appears to be happening when xfce4 starts since it sits displaying a small progress circle until something "times-out" and then switches to the usual larger circle before running?
Remove rhgb and quite from the kernel line during bootup.
Done, that is one of the first things I do after installation of system.
See if you can spot something.
If not wait till you login and: journalctl -b | grep timeout # or whatever is the correct "time-out" you see.
Not sure how to implement "time-out" but this is the data after 08:33:30 and startxfce4 > the small progress circle was displayed:
Feb 10 08:33:26 box7 systemd[1]: Started Stop Read-Ahead Data Collection. Feb 10 08:33:30 box7 kernel: mei_me 0000:00:03.0: reset: connect/disconnect timeout. Feb 10 08:33:30 box7 kernel: mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING Feb 10 08:33:32 box7 fprintd[968]: ** Message: No devices in use, exit Feb 10 08:33:36 box7 kernel: mei_me 0000:00:03.0: reset: connect/disconnect timeout. Feb 10 08:33:36 box7 kernel: mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING Feb 10 08:33:42 box7 kernel: mei_me 0000:00:03.0: reset: connect/disconnect timeout. Feb 10 08:33:42 box7 kernel: mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING Feb 10 08:33:48 box7 kernel: mei_me 0000:00:03.0: reset: connect/disconnect timeout. Feb 10 08:33:48 box7 kernel: mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING Feb 10 08:33:54 box7 kernel: mei_me 0000:00:03.0: reset: connect/disconnect timeout. Feb 10 08:33:54 box7 kernel: mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING Feb 10 08:33:54 box7 polkitd[669]: Registered Authentication Agent for unix-session:1 (system bus name :1.23 [/usr/libexec/polkit-gnome-authen Feb 10 08:33:54 box7 systemd[1]: Starting CUPS Printing Service... Feb 10 08:33:54 box7 systemd[1]: Started CUPS Printing Service. Feb 10 08:33:54 box7 dbus-daemon[424]: dbus[424]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-dae Feb 10 08:33:54 box7 dbus[424]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' Feb 10 08:33:54 box7 systemd[1]: Starting RealtimeKit Scheduling Policy Service... Feb 10 08:33:55 box7 dbus-daemon[424]: dbus[424]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1' Feb 10 08:33:55 box7 dbus[424]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1' Feb 10 08:33:55 box7 systemd[1]: Started RealtimeKit Scheduling Policy Service. Feb 10 08:33:55 box7 rtkit-daemon[1063]: Successfully called chroot. Feb 10 08:33:55 box7 rtkit-daemon[1063]: Successfully dropped privileges. Feb 10 08:33:55 box7 rtkit-daemon[1063]: Successfully limited resources. Feb 10 08:33:55 box7 rtkit-daemon[1063]: Running. Feb 10 08:33:55 box7 rtkit-daemon[1063]: Canary thread running. Feb 10 08:33:55 box7 rtkit-daemon[1063]: Watchdog thread running. Feb 10 08:33:55 box7 rtkit-daemon[1063]: Successfully made thread 1062 of process 1062 (/usr/bin/pulseaudio) owned by '1000' high priority at Feb 10 08:33:55 box7 rtkit-daemon[1063]: Supervising 1 threads of 1 processes of 1 users. Feb 10 08:33:55 box7 pulseaudio[1062]: [pulseaudio] core-util.c: Home directory not accessible: Permission denied Feb 10 08:33:55 box7 kernel: fuse init (API version 7.22) Feb 10 08:33:55 box7 systemd[1]: Mounting FUSE Control File System... Feb 10 08:33:55 box7 systemd[1]: Mounted FUSE Control File System. Feb 10 08:33:55 box7 kernel: SELinux: initialized (dev fusectl, type fusectl), uses genfs_contexts Feb 10 08:33:55 box7 kernel: SELinux: initialized (dev fuse, type fuse), uses genfs_contexts Feb 10 08:33:56 box7 dbus-daemon[424]: dbus[424]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' Feb 10 08:33:56 box7 dbus[424]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' Feb 10 08:33:56 box7 systemd[1]: Starting Daemon for power management... Feb 10 08:33:56 box7 dbus-daemon[424]: dbus[424]: [system] Successfully activated service 'org.freedesktop.UPower' Feb 10 08:33:56 box7 dbus[424]: [system] Successfully activated service 'org.freedesktop.UPower' Feb 10 08:33:56 box7 systemd[1]: Started Daemon for power management. Feb 10 08:33:57 box7 dbus-daemon[424]: dbus[424]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.servic Feb 10 08:33:57 box7 dbus[424]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' Feb 10 08:33:57 box7 systemd[1]: Starting Disk Manager... Feb 10 08:33:57 box7 udisksd[1382]: udisks daemon version 2.1.2 starting Feb 10 08:33:57 box7 dbus-daemon[424]: dbus[424]: [system] Successfully activated service 'org.freedesktop.UDisks2' Feb 10 08:33:57 box7 dbus[424]: [system] Successfully activated service 'org.freedesktop.UDisks2' Feb 10 08:33:57 box7 udisksd[1382]: Acquired the name org.freedesktop.UDisks2 on the system message bus Feb 10 08:33:57 box7 systemd[1]: Started Disk Manager. Feb 10 08:33:59 box7 goa[1439]: goa-daemon version 3.10.2 starting [main.c:117, main()] Feb 10 08:33:59 box7 goa[1439]: GoaKerberosIdentityManager: Using polling for change notification for credential cache type 'KEYRING' [goakerb Feb 10 08:34:00 box7 kernel: mei_me 0000:00:03.0: reset: connect/disconnect timeout. Feb 10 08:34:00 box7 kernel: mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING Feb 10 08:34:06 box7 kernel: mei_me 0000:00:03.0: reset: connect/disconnect timeout. Feb 10 08:34:06 box7 kernel: mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING Feb 10 08:34:11 box7 chronyd[403]: Selected source 50.23.135.154 Feb 10 08:34:12 box7 kernel: mei_me 0000:00:03.0: reset: connect/disconnect timeout. Feb 10 08:34:12 box7 kernel: mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING Feb 10 08:34:18 box7 kernel: mei_me 0000:00:03.0: reset: connect/disconnect timeout. Feb 10 08:34:18 box7 kernel: mei_me 0000:00:03.0: unexpected reset: dev_state = RESETTING Feb 10 08:34:20 box7 sshd[1474]: Accepted password for bobg from 192.168.1.10 port 39820 ssh2 Feb 10 08:34:20 box7 systemd-logind[423]: New session 2 of user bobg. Feb 10 08:34:20 box7 systemd[1]: Starting Session 2 of user bobg. Feb 10 08:34:20 box7 systemd[1]: Started Session 2 of user bobg. Feb 10 08:34:20 box7 sshd[1474]: pam_unix(sshd:session): session opened for user bobg by (uid=0)
At the end you can see my ssh access to view this.
I think the "unexpected reset: dev_state = RESETTING" is at least part off what I am seeing in console 1.
If you can deduce anything from that I would like to know ...
Bob
Regards Frank frankly3d.com
On Mon, 10 Feb 2014 08:46:30 -0500 "Bob Goodwin - Zuni, Virginia, USA" bobgoodwin@wildblue.net wrote:
Feb 10 08:33:30 box7 kernel: mei_me 0000:00:03.0: reset: connect/disconnect timeout.
What kernel are you using on that box? https://bugzilla.redhat.com/show_bug.cgi?id=917081
also check: https://bbs.archlinux.org/viewtopic.php?id=168403 in case it's Intel having a bad-hair day.
___ Regards Frank frankly3d.com
On 10/02/14 09:00, Frank Murphy wrote:
On Mon, 10 Feb 2014 08:46:30 -0500 "Bob Goodwin - Zuni, Virginia, USA" bobgoodwin@wildblue.net wrote:
Feb 10 08:33:30 box7 kernel: mei_me 0000:00:03.0: reset: connect/disconnect timeout.
What kernel are you using on that box?
[bobg@box7 ~]$ uname -a Linux box7 3.12.9-301.fc20.x86_64 #1 SMP Wed Jan 29 15:56:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
on a Dell Optiplex 755 desktop system.
So as in the bug report I did:
[root@box7 bobg]# echo -e "blacklist mei\ninstall mei /bin/true" > /etc/modprobe.d/mei.conf [root@box7 bobg]# dracut --force [root@box7 bobg]# exit
And for the first time in many months the "garbage" I have been seeing at boot, which I normally ignore since it did not seem to do anyhing except clutter the display, the log in is nice and clear but console-1 is still busy and xfce is on console-2?
Ther is a difference though in that it console-1 now shows at the prompt:
xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on x server :0.0
I don't know what to do about that but I'll bet if I did things would improve?
also check: https://bbs.archlinux.org/viewtopic.php?id=168403 in case it's Intel having a bad-hair day. ___ Regards Frank frankly3d.com Bob
On Mon, 10 Feb 2014 09:29:35 -0500 "Bob Goodwin - Zuni, Virginia, USA" bobgoodwin@wildblue.net wrote:
xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on x server :0.0
You have a borked X &| Xfce try: https://bbs.archlinux.org/viewtopic.php?id=129274
___ Regards Frank frankly3d.com
On 10.02.2014 14:17, Bob Goodwin - Zuni, Virginia, USA wrote: …
But the sledgehammer [bobG, new user] works!
Bob
http://www.youtube.com/embed/cQl6r0fqRAI?rel=0&border=0&autoplay=1 :)
poma
On 02/12/2014 02:56 AM, poma wrote:
On 10.02.2014 14:17, Bob Goodwin - Zuni, Virginia, USA wrote: …
But the sledgehammer [bobG, new user] works!
Bob
http://www.youtube.com/embed/cQl6r0fqRAI?rel=0&border=0&autoplay=1 :)
great series. lmao nearly every time i watched it.