wm-logout or :Quit end into nirwana

[gapan]

For the resolution, install hwinfo and run:

Code: Select all

hwinfo --framebuffer

you should get a list of resolutions. Pick the one you want and you should edit the corresponding vga=... line in the lilo.conf file. That should fix your resolution.

About your logout problem, fluxbox probably doesn't shut down properly because of something that is blocking it. This is not the default behaviour in a fresh system which works fine. You should start by trying to identify what that is and then forcing it to stop when logging out.

You seem to have mixed problems. You're saying that it wasn't working properly with slim before, but at least it was working partially. Now it doesn't work at all. Neither is acceptable and has been the result of something you did. Nobody else could have any idea what that was though...

[jsfarinet]

For the resolution, install hwinfo and run:

Code: Select all

hwinfo --framebuffer

you should get a list of resolutions. Pick the one you want and you should edit the corresponding vga=... line in the lilo.conf file. That should fix your resolution

That command gives no output at all.

About your logout problem, fluxbox probably doesn't shut down properly because of something that is blocking it. This is not the default behaviour in a fresh system which works fine. You should start by trying to identify what that is and then forcing it to stop when logging out.

You seem to have mixed problems. You're saying that it wasn't working properly with slim before, but at least it was working partially. Now it doesn't work at all. Neither is acceptable and has been the result of something you did. Nobody else could have any idea what that was though...

Just to made it clear: When you advised to better use gdm, i turned back to it and all was working fine. With slim, the switch user did not work (obviously because in the default fluxbox configuration it relays on gdmflexiserver). But at least i could switch the user, logging out of the Xsession and getting to a new login (not so elegant but that would have worked).

In my humble mind i thought the same. I am pretty sure that the culprit is the fglrx driver. After i installed that, the problems showed up. Now, there is the unconfortable alternative of

a) a system having at least suspend and a somehow reasonable powermanagement keeping the cpu temperatur at reasonable levels but with the problems of logout (i on my own very likely will be unable to solve).

or

b) a system with the default radeon driver which does not have suspend correctly working suspend (with this cpu, obviously)and which is getting crazily hot (toward 90° even with only average cpu use; many installations crashed underway because the machine was overheating and shut itself down consequentely). This pm problems were ongoing long time with any kernel after 3.2. Before the machine got still hot, but not that much, and suspend (suspend on close_lid too) worked fine.

A bit clueless at this point ...

[gapan]

If you get nothing about vga setting, look in lilo.conf. There are already some examples in there. Pick one.

OK, so lets investigate what might stay running when you try to log out. Log out, switch to a console with ctrl-alt-f2 and run:

Code: Select all

ps -A > PSA

Then paste the contents of the PSA file here.

[jsfarinet]

Thanks a lot for your patience. Here comes the output of PSA

Code: Select all

  PID TTY          TIME CMD
13506 tty2     00:00:00 ps

[jsfarinet]

Since this one of the most important remaining problems a tried to experiment around it. I deleted Slim completely (i think it might be safe too remove any slim statement from /etc/rc.d/rc4 (?).

Moreover i "cleaned" lilo a bit, I always got a warning "lba32 addressing assumed" and to clear that i put a lba32 statement into lilo.

Now, the situation about logout, console access etc. is this:

Switch User (=gdmflexiserver) works.

Ctrl-Alt-F1 thru F3 work
Ctrl-Alt-F7 reassumes desktop
Ctr-Alt-F4 thru F6 bring to a dead screen, but i can use Ctr-Alt-F7 from there to reassume the desktop

wm-logout > logout brings to a "nirwana" where nothing helps not even the magic linux keys (sys req based)
Same goes for Ctrl-Alt-Del (which i presume is the equivalent to the fluxbox internal :Quit command).
In this both cases only a hard reboot helps.

Ah, and PSA now looks like this:

Code: Select all

  PID TTY          TIME CMD
 5638 pts/1    00:00:00 ps

[gapan]

That ps -A output looks too weird. It's as if nothing else is running on your system, which is impossible.

Anyway, can you determine that it's really the graphics card drivers that is causing this? Can you uninstall, try it without, see what happens and reinstall?

[jsfarinet]

That ps -A output looks too weird. It's as if nothing else is running on your system, which is impossible.

Anyway, can you determine that it's really the graphics card drivers that is causing this? Can you uninstall, try it without, see what happens and reinstall?

Thanks for answering. Since it's a bit critical, i need some time.Tomorrow, i'll do like you advised and see what happens (praying that reboot after uninstalling fglrx will work ).

Stop, stop: I did it newly. Now it looks like this:

Code: Select all

  PID TTY          TIME CMD
    1 ?        00:00:00 init
    2 ?        00:00:00 kthreadd
    3 ?        00:00:00 ksoftirqd/0
    4 ?        00:00:01 kworker/0:0
    5 ?        00:00:00 kworker/0:0H
    6 ?        00:00:00 kworker/u8:0
    7 ?        00:00:02 migration/0
    8 ?        00:00:00 rcu_bh
    9 ?        00:00:00 rcu_sched
   10 ?        00:00:00 migration/1
   11 ?        00:00:00 ksoftirqd/1
   13 ?        00:00:00 kworker/1:0H
   14 ?        00:00:00 khelper
   15 ?        00:00:00 kdevtmpfs
   16 ?        00:00:00 netns
   17 ?        00:00:00 writeback
   18 ?        00:00:00 bioset
   19 ?        00:00:00 kblockd
   20 ?        00:00:00 ata_sff
   21 ?        00:00:00 khubd
   22 ?        00:00:00 md
   23 ?        00:00:00 devfreq_wq
   24 ?        00:00:01 kworker/1:1
   25 ?        00:00:00 rpciod
   26 ?        00:00:00 kworker/0:1
   60 ?        00:00:00 khungtaskd
   61 ?        00:00:00 kswapd0
   62 ?        00:00:00 khugepaged
   63 ?        00:00:00 fsnotify_mark
   64 ?        00:00:00 nfsiod
   65 ?        00:00:00 jfsIO
   66 ?        00:00:00 jfsCommit
   67 ?        00:00:00 jfsCommit
   68 ?        00:00:00 jfsSync
   69 ?        00:00:00 xfsalloc
   70 ?        00:00:00 xfs_mru_cache
   71 ?        00:00:00 xfslogd
   72 ?        00:00:00 ocfs2_wq
   73 ?        00:00:00 user_dlm
   74 ?        00:00:00 bioset
   75 ?        00:00:00 crypto
  118 ?        00:00:00 kthrotld
  120 ?        00:00:00 cciss_scan
  121 ?        00:00:00 fc_exch_workque
  122 ?        00:00:00 fc_rport_eq
  123 ?        00:00:00 fcoethread/0
  124 ?        00:00:00 fcoethread/1
  125 ?        00:00:00 fnic_event_wq
  126 ?        00:00:00 scsi_eh_0
  127 ?        00:00:00 scsi_eh_1
  128 ?        00:00:00 scsi_eh_2
  129 ?        00:00:00 scsi_eh_3
  133 ?        00:00:00 kworker/u8:5
  134 ?        00:00:00 scsi_eh_4
  137 ?        00:00:00 scsi_eh_5
  138 ?        00:00:00 exec-osm
  139 ?        00:00:00 block-osm
  140 ?        00:00:00 speakup
  142 ?        00:00:00 kworker/1:1H
  143 ?        00:00:00 deferwq
  145 ?        00:00:00 kworker/0:1H
  146 ?        00:00:00 jbd2/sda1-8
  147 ?        00:00:00 ext4-dio-unwrit
  179 ?        00:00:00 udevd
  265 ?        00:00:00 kpsmoused
  298 ?        00:00:00 cfg80211
  299 ?        00:00:00 hd-audio0
  302 ?        00:00:00 hd-audio1
  305 ?        00:00:00 kvm-irqfd-clean
  312 ?        00:00:00 led_workqueue
  319 ?        00:00:00 kworker/u9:0
  321 ?        00:00:00 hci0
  322 ?        00:00:00 hci0
  325 ?        00:00:00 kworker/u9:1
  423 ?        00:00:00 kworker/1:2
  429 ?        00:00:00 jbd2/sda2-8
  430 ?        00:00:00 ext4-dio-unwrit
  470 ?        00:00:00 syslogd
  474 ?        00:00:00 klogd
  532 ?        00:00:00 udevd
  533 ?        00:00:00 udevd
  645 ?        00:00:00 acpid
  655 ?        00:00:00 dbus-daemon
  658 ?        00:00:00 console-kit-dae
  723 ?        00:00:00 bluetoothd
  728 ?        00:00:00 polkitd
  735 ?        00:00:00 ntpd
  746 ?        00:00:00 krfcommd
  753 ?        00:00:00 cupsd
  757 ?        00:00:02 wicd
  760 ?        00:00:00 crond
  762 ?        00:00:00 atd
  765 ?        00:00:00 wicd-monitor
  889 ?        00:00:09 privoxy
  924 ?        00:00:07 tor
 1386 tty1     00:00:00 agetty
 1387 tty2     00:00:00 agetty
 1388 tty3     00:00:00 agetty
 1389 ?        00:00:00 gdm-binary
 1433 ?        00:00:00 gdm-binary
 1435 tty7     00:01:56 X
 1440 ?        00:00:00 firegl
 1441 ?        00:00:00 firegl
 1442 ?        00:00:00 firegl
 1473 ?        00:00:00 wpa_supplicant
 1513 ?        00:00:13 clamd
 1517 ?        00:00:04 freshclam
 1526 ?        00:00:02 fluxbox
 1557 ?        00:00:00 ssh-agent
 1561 ?        00:00:00 dbus-daemon
 1589 ?        00:00:00 dhcpcd
 1599 ?        00:00:04 SpiderOak
 1600 ?        00:00:00 thunar
 1601 ?        00:00:00 blueman-applet
 1602 ?        00:00:13 thunderbird
 1603 ?        00:00:00 applet.py
 1604 ?        00:00:00 salix-update-no
 1606 ?        00:00:00 salix-update-no
 1607 ?        00:00:00 xscreensaver
 1609 ?        00:00:00 conky
 1610 ?        00:00:00 volumeicon
 1611 ?        00:00:02 clipit
 1612 ?        00:00:00 keepassx
 1615 ?        00:00:05 conky
 1650 ?        00:00:05 compton
 1652 ?        00:00:00 xfconfd
 1698 ?        00:00:00 gvfsd
 1707 ?        00:00:00 obex-data-serve
 1710 ?        00:00:00 gvfsd-fuse
 1711 ?        00:00:09 SpiderOak
 1802 ?        00:00:00 inotify_dir_wat
 1904 ?        00:00:00 gconfd-2
 1925 ?        00:00:00 bash
 1926 ?        00:00:00 xterm
 1927 ?        00:00:01 kdocker
 1929 pts/0    00:00:16 arm
 1979 ?        00:02:30 firefox
 2000 ?        00:00:00 at-spi-bus-laun
 2736 ?        00:00:00 sleep
 2737 ?        00:00:00 sleep
 3226 ?        00:00:00 xterm
 3228 pts/1    00:00:00 bash
 3246 pts/1    00:00:00 ps

Looks more reasonable to you?

[gapan]

Yes, this looks normal, but it shows a lot of apps are running, like firefox and thunderbird. I was suggesting you try to logout and then run this so we could see if something stays on and is blocking it. From what I read from your comments though that may not be possible, since you say that everything hangs and you can't do anything as soon as you logout?

Anyway, see if it's an actual video driver problem, so we might be able to troubleshoot it then.

[jsfarinet]

Yes, this looks normal, but it shows a lot of apps are running, like firefox and thunderbird. I was suggesting you try to logout and then run this so we could see if something stays on and is blocking it. From what I read from your comments though that may not be possible, since you say that everything hangs and you can't do anything as soon as you logout?

Anyway, see if it's an actual video driver problem, so we might be able to troubleshoot it then.

As for the apps running could i shoot them down manually? (Thunderbird in my setup is started by fluxbox startup as well as many others; Thunar i start as a daemon to have it come up faster when calling etc.). SwitchUser (gdmflexiserver) works. May be i should create another user ... Or is there a trick to login as root?

[gapan]

Don't login as root. Are you trying to logout while having all those apps running?

Things to try are:
- Create a new user, reboot the system and log in with that user. See if logout hangs.
- Uninstall the proprietary drivers you installed. Reboot and check if logout hangs.