[???] black screen of death

Everything about X, Gnome, KDE, ... and everything running on it

Re: [SOLVED] GTK requires systemd-sysv, (black screen of dea

Postby GarryRicketson » 2019-05-15 02:13

Since you give Zero details, such as the version of the package, and the version of Debian , Who can guess ? Not me,... but a quick search , does show some bugs listed for this package, if it is the unstable verison
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=gpgsm;dist=unstable
I did not look at the other Debian versions, nor check the bug reports on them, since it is rather futile, not knowing the version you are using:
https://packages.debian.org/sid/gpgsm
You can look at them your self though.
User avatar
GarryRicketson
 
Posts: 5596
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: [SOLVED] GTK requires systemd-sysv, (black screen of dea

Postby sickpig » 2019-05-15 04:50

GarryRicketson wrote:Since you give Zero details, such as the version of the package, and the version of Debian , Who can guess ?


he has already provided every pertinent detail if only you can comprehend

@Soul Singin' big fan of your 'how to package' 'how to' thread, thank you. Am sure other stalwarts who have already posted to this thread know what they are talking about and will be able to help you.
User avatar
sickpig
 
Posts: 129
Joined: 2019-01-23 10:34

Re: [SOLVED] GTK requires systemd-sysv, (black screen of dea

Postby GarryRicketson » 2019-05-15 11:53

Oh no, I really do feel bad, and need to apologize, last night it was late, and I did not notice this was the second page, so what I saw was interpreted as the first post,...
Now I do see everything is on the previous page:
http://forums.debian.net/viewtopic.php?f=6&t=138293#p678714
My sincere apology, hope it is accepted
User avatar
GarryRicketson
 
Posts: 5596
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: [SOLVED] GTK requires systemd-sysv, (black screen of dea

Postby GarryRicketson » 2019-05-15 11:59

Again, my apology, yes the details are in the very first post.
Soul Singin' wrote:EDIT:. The original post wrongly diagnoses the problem. The real issue is that GTK requires systemd to be the init system. Violations are punishable by black screen of death.

UPDATE:. This nasty bug reappeared after installing gpgsm. Removing the package removed the bug.

---------

I recently upgraded from Wheezy to Stretch (making a very brief visit to Jessie along the way). After the upgrade, I began experiencing black screens of death at seemingly random times. The crashes would render the keyboard and mouse useless. And I could not login through SSH either. Lacking an alternative, I had to cycle the power.

I searched through the log files (many times), but I could never find any trace of the error that cause that catastrophic crash. (Perhaps I was not looking in the right location??)

The only clue to diagnosis was that the crashes would occur more often after editing my GTK configurations with LXAppearance (and on one occasion while editing them with LXAppearance). Removing the ".gtkrc" files stopped the crashing, so I did what any good Debian user would do: I created them with LXAppearance one more time ... and got a black screen of death.

In frustration, I finally did what any sane human being would do. I ran:
Code: Select all
rm -rf ~/.gtkrc-2.0 ~/.config/gtk-3.0/  ~/.config/lx*  ~/.config/libfm/  ~/.config/pcmanfm/

And for good measure, I also ran:
Code: Select all
apt-get purge --autoremove $(dpkg -l lx* | grep ^ii | awk '{print $2}')

Since then, I have not experienced any black screens of death.

Nonetheless, I would be curious to know what GTK configuration was causing those crashes. And I wonder if the inability to login via SSH provides a clue: The GTK crash would cause the Network Manager applet to crash, which would prevent me from connecting over the network.

Below are two of the ".gtkrc" files that LXAppearance generated. The crashes occurred regardless of which theme, icons or cursors was selected.

~/.config/gtk-3.0/settings.ini
Code: Select all
[Settings]
gtk-font-name=Sans 10
gtk-theme-name=Clearlooks-Phenix
gtk-icon-theme-name=default.kde4
gtk-fallback-icon-theme=Tango
gtk-toolbar-style=GTK_TOOLBAR_BOTH_HORIZ
gtk-menu-images=1
gtk-button-images=1
gtk-cursor-theme-size=18
gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
gtk-enable-event-sounds=1
gtk-enable-input-feedback-sounds=1
gtk-xft-antialias=1
gtk-xft-hinting=1
gtk-xft-hintstyle=hintslight
gtk-xft-rgba=rgb
gtk-cursor-theme-name=oxy-obsidian


~/.gtkrc-2.0
Code: Select all
# DO NOT EDIT! This file will be overwritten by LXAppearance.
# Any customization should be done in ~/.gtkrc-2.0.mine instead.

include "/home/soul/.gtkrc-2.0.mine"
gtk-theme-name="Clearlooks-Phenix"
gtk-icon-theme-name="default.kde4"
gtk-font-name="Sans 10"
gtk-cursor-theme-name="oxy-obsidian"
gtk-cursor-theme-size=18
gtk-toolbar-style=GTK_TOOLBAR_BOTH_HORIZ
gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
gtk-button-images=1
gtk-menu-images=1
gtk-enable-event-sounds=1
gtk-enable-input-feedback-sounds=1
gtk-xft-antialias=1
gtk-xft-hinting=1
gtk-xft-hintstyle="hintslight"
gtk-xft-rgba="rgb"


Please leave a reply if you have experienced a similar issue. I would like to know what caused all of those crashes.

Thanks in advance,
- Soul Singin'
.
User avatar
GarryRicketson
 
Posts: 5596
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: [SOLVED] GTK requires systemd-sysv, (black screen of dea

Postby Soul Singin' » 2019-05-15 12:20

GarryRicketson wrote:Oh no, I really do feel bad, and need to apologize,
GarryRicketson wrote:My sincere apology, hope it is accepted

Apology accepted, but none was necessary. I laughed at myself. (I really did). You put a big smile on my face this morning. . :D

sickpig wrote:@Soul Singin' big fan of your 'how to package' 'how to' thread, thank you.

Thank you! I'm happy to help. I'm glad you found it useful.

The date of that HowTo just surpised me: 9 May 2009. Ten years ago! . :shock:

sickpig wrote:every pertinent detail

In terms of software, this all happened in Debian Stretch, but what may be more relevant is the fact that this computer is almost as old as that HowTo. Back when I installed Debian Lenny on it, a computer with 8GB of RAM was a beast of a machine. Today, that's standard.

Low-level software that's relatively new (like systemd) was designed with newer hardware in mind. When it was in development, it was tested on newer hardware.

But I still love this machine! . :D
.
User avatar
Soul Singin'
 
Posts: 1498
Joined: 2008-12-21 07:02

Re: [SOLVED] GTK requires systemd-sysv, (black screen of dea

Postby Head_on_a_Stick » 2019-05-15 14:24

Soul Singin' wrote:But why would gpgsm cause systemd to crash?
.

So you are now running with systemd as PID1?

Do you still have any packages on the box that were build with the no-systemd sources?

Please post the output of
Code: Select all
loginctl session-status --no-p
User avatar
Head_on_a_Stick
 
Posts: 9693
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: [SOLVED] GTK requires systemd-sysv, (black screen of dea

Postby Soul Singin' » 2019-05-15 17:21

Head_on_a_Stick wrote:So you are now running with systemd as PID1?

Yes.

Head_on_a_Stick wrote:Do you still have any packages on the box that were build with the no-systemd sources?

None.

Head_on_a_Stick wrote:Please post the output of
Code: Select all
loginctl session-status --no-p

Thank you for taking a look. Here it is:

Code: Select all
2 - eryk (1000)
           Since: Tue 2019-05-14 18:23:49 EDT; 19h ago
          Leader: 1349 (lightdm)
            Seat: seat0; vc7
         Display: :0
         Service: lightdm; type x11; class user
         Desktop: lightdm-xsession
           State: active
            Unit: session-2.scope
                  ├─ 1349 lightdm --session-child 14 23
                  ├─ 1358 x-session-manager
                  ├─ 1414 /usr/bin/dbus-launch --exit-with-session --sh-syntax
                  ├─ 1415 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
                  ├─ 1433 /usr/bin/ssh-agent x-session-manager
                  ├─ 1434 icewmbg
                  ├─ 1435 icewm --notify
                  ├─ 1436 icewmtray --notify
                  ├─ 1443 xeyes
                  ├─ 1445 nm-applet
                  ├─ 1448 /usr/lib/at-spi2-core/at-spi-bus-launcher
                  ├─ 1453 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
                  ├─ 1455 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
                  ├─ 1461 clipit
                  ├─ 1467 pnmixer
                  ├─ 1472 /usr/bin/pulseaudio --start --log-target=syslog
                  ├─ 1477 cbatticon
                  ├─ 1515 kdeinit4: kdeinit4 Running...
                  ├─ 1518 kdeinit4: klauncher [kdeinit] --fd=
                  ├─ 1520 kdeinit4: kded4 [kdeinit]
                  ├─ 2862 /usr/bin/kuiserver
                  ├─ 6817 /usr/bin/knotify4
                  ├─17161 /usr/lib/dconf/dconf-service
                  ├─24090 /usr/lib/x86_64-linux-gnu/gconf/gconfd-2
                  ├─28260 dolphin4
                  ├─28280 /usr/bin/firefox-esr
                  ├─28331 /usr/lib/firefox-esr/firefox-esr -contentproc -childID 1 -isForBrowser -intPrefs 235:3| -boolPrefs 36:1|1…ab
                  ├─28396 /usr/bin/expressvpn-browser-helper /home/eryk/.mozilla/native-messaging-hosts/com.expressvpn.helper.json …om
                  ├─28423 /usr/lib/firefox-esr/firefox-esr -contentproc -childID 2 -isForBrowser -intPrefs 235:3| -boolPrefs 36:1|1…ab
                  ├─28624 konsole
                  ├─28627 /bin/bash
                  └─28654 loginctl session-status --no-p

Edit: . After posting, I went back and experimented by installing gpgsm, sending an email with mutt (to trigger usage of gpgsm) and then compared the output of the loginctl command.

The only difference was the PID of the loginctl command.
.
Last edited by Soul Singin' on 2019-05-16 00:42, edited 1 time in total.
User avatar
Soul Singin'
 
Posts: 1498
Joined: 2008-12-21 07:02

Re: [???] GTK requires systemd-sysv, (black screen of death)

Postby Soul Singin' » 2019-05-16 00:40

summary:
  • The machine is an old Dell Inspiron with an Intel Quad Core i3 CPU and 8 GB of RAM, running Debian Stretch.
  • When systemd-sysv is NOT installed, the machine experiences random crashes.
  • When systemd-sysv and gpgsm are both installed, the machine also experiences random crashes.
  • When gpgsm is NOT installed (and systemd-sysv is installed), the machine runs perfectly.
observations:
  • Since the crashes occur when systemd-sysv is not installed, it cannot be systemd-sysv that is causing the crashes. Something else must be creating trouble for the init system.
  • gpgsm creates that trouble for the init system even though systemd-sysv is installed.

What is causing those crashes?
.
User avatar
Soul Singin'
 
Posts: 1498
Joined: 2008-12-21 07:02

Re: [???] GTK requires systemd-sysv, (black screen of death)

Postby sickpig » 2019-05-16 03:24

can u get gpgsm to do a delayed start?
it will help in identifying if the issue is with init or with the startup of gpgsm
let me know if this approach seems right?
User avatar
sickpig
 
Posts: 129
Joined: 2019-01-23 10:34

Re: [???] GTK requires systemd-sysv, (black screen of death)

Postby Soul Singin' » 2019-05-16 11:22

sickpig wrote:can u get gpgsm to do a delayed start?
it will help in identifying if the issue is with init or with the startup of gpgsm
let me know if this approach seems right?

The approach is correct. I just cannot find a way to implement it.

For example, when I ran the loginctl command, first I ran it on the machine without gpgsm installed and stored the output. Then, I installed the gpgsm package and sent an email with mutt to trigger the gpgsm binary. Finally, I ran the loginctl command again and stored the output.

When I compared the output, the only difference was the PID of the loginctl command -- as you would expect. Or at least, that's what you would expect if no other processes had been started or stopped. . mutt sent the email and so gpgsm had finished too, so those processes had stopped and nothing else was started.

So it's like "nothing" is running, but that "nothing" crashed my machine a short time later.
.
User avatar
Soul Singin'
 
Posts: 1498
Joined: 2008-12-21 07:02

Re: [???] GTK requires systemd-sysv, (black screen of death)

Postby Head_on_a_Stick » 2019-05-16 20:16

Soul Singin' wrote:gpgsm creates that trouble for the init system

What makes you think that PID1 is involved in this problem?

You seem to have a correct login session so my theory was wrong.

Try the gpgsm version from stretch-backports.

Or perhaps install and enable the haveged package to help generate some (fake) entropy.

The systemd-coredump package will store any coredumps for future analysis, see coredumpctl(1).
User avatar
Head_on_a_Stick
 
Posts: 9693
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: [???] GTK requires systemd-sysv, (black screen of death)

Postby Soul Singin' » 2019-05-17 13:48

Head_on_a_Stick wrote:What makes you think that PID1 is involved in this problem?

The fact that the crash is so catastrophic that it disables everything and does not leave a trace. Not even a log file. I could be mistaken, but it seems to me that the problem is affecting the system at a very deep level.

This morning, I reinstalled gpgsm and sent a bunch of emails with mutt, so I'm waiting for the crash as I write to you.

Update: . It crashed. I removed gpgsm, then it crashed again.

So the problem cannot be in systemd-sysv and cannot be in gpgsm. It must be somewhere else. So what else might I have done to trigger the crash?

While thinking about the issue, I looked at my ~/.muttrc file and noticed this old line:
Code: Select all
set editor="qemacs"

The qemacs-nox package was removed from Debian ages ago, but I still had it installed on my system and mutt was using it to send emails. I played with it and the computer crashed.

So I removed qemacs-nox and now I'm waiting for another crash. I'll keep you posted.

In the meantime, thank you for your help.

Sincerely,
- Soul
.
User avatar
Soul Singin'
 
Posts: 1498
Joined: 2008-12-21 07:02

Re: [???] GTK requires systemd-sysv, (black screen of death)

Postby Head_on_a_Stick » 2019-05-17 15:08

If you are shutting down the computer after these freezes then try enabling persistent logging:
Code: Select all
# mkdir -p /var/log/journal # delete the directory to return to non-persistent logging

Then use the systemd journal to check the last boot:
Code: Select all
journalctl -r -b -1

The coredumpctl command can also be very useful in situations like this.
User avatar
Head_on_a_Stick
 
Posts: 9693
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: [???] GTK requires systemd-sysv, (black screen of death)

Postby Soul Singin' » 2019-05-17 15:59

Head_on_a_Stick wrote:try enabling persistent logging:

There's a good idea. Thank you! I just enabled it.

And in general, thank you for your help! . :D

This time, I think I've identified the real issue and I think it was qemacs-nox. My system has been crash free since I removed that package.

I have not tried sending any emails yet, but I will. First, I want to test this configuration a little bit. If it runs smoothly, then I will try sending some emails. And if the system is still crash-free after that, then we should be able to confidently say that the problem was qemacs-nox.

Keep your fingers crossed for me!

Thanks,
- Soul
.
User avatar
Soul Singin'
 
Posts: 1498
Joined: 2008-12-21 07:02

Re: [???] GTK requires systemd-sysv, (black screen of death)

Postby Soul Singin' » 2019-05-17 19:01

Soul Singin' wrote:This time, I think I've identified the real issue

I was wrong. It crashed again.

Here is the relevant section from the journal log:
Code: Select all
-- Logs begin at Fri 2019-05-17 10:02:26 EDT, end at Fri 2019-05-17 15:43:19 EDT. --
May 17 15:37:20 inspiron kernel: perf: interrupt took too long (5197 > 4963), lowering kernel.perf_event_max_sample_rate to 38250

What does that mean?
.
User avatar
Soul Singin'
 
Posts: 1498
Joined: 2008-12-21 07:02

PreviousNext

Return to Desktop & Multimedia

Who is online

Users browsing this forum: No registered users and 12 guests

fashionable