Blind test: famous quotations

I am getting the "A stop job is running for User Manager for UID 1000" situation on Trisquel 11 from time to time, so I am currently doing random searches on that topic. Unfortunately, that respected Member of systemd suddenly retreated from that thread, so we may never know who ate Cthulhu's children. He was teleported by his handlers to more than a year later, tasked with posting this deeply philosophical comment: "Not sure why people think it's useful to keep posting on an old bug", followed by a long and convoluted discussion of that very same old bug.

It appears that any userspace service (managed by systemd --user) could cause the system to hang. Some users have reported wpa_supplicant as the source of the hanging job, others the Transmission daemon, others Audacious or pulseaudio, others still some Gnome service, etc.

No luck yet with journalctl --no-pager -b -1 > journal.log.

There's a lot of killing children and dying and lost children in that thread.

>"It appears that any userspace service (managed by systemd --user) could cause the system to hang."

It's why we love systemd.

I don't recall if Trisquel has an /etc/tlp.conf, but if it does, you could try blacklisting USB autosuspend for your wifi card:

1. run the command 'lsusb'. Look for the "Bus 003 blah blah blah..." line for your wifi device. In that line, it should say something like 'ID 2100:02c0' or something in the form of 'xxxx:xxxx'. That's your USB ID number for that device.

2. edit tlp.conf with your favorite editor, like 'sudo mousepad /etc/tlp.conf'

3. scroll down, look for the line that says '#USB_BLACKLIST="1111:2222 3333:4444". It's on about line 330 for my tlp.conf file.

4. uncomment by removing the '#', and put your wifi card USB ID in the list, so it looks like 'USB_BLACKLIST="1111:2222 3333:4444 2100:02c0' or whatever your wifi's USB ID is.

5. Save, and you might need to reboot. Now your wifi card shouldn't do it's auto-sleep thing and mess up. I end up having to make this edit on every computer for some reason. And some computers I use a USB ethernet dongle, and I have to blacklist the auto-suspend on that one too.

Might help. Or it might not - it might cause more of your child processes to get killed and eaten. But then you would have a good bug to chat with Lennart about.

That thread is pure Troll Lounge gold. Let us use it sparingly.

I am currently suspecting my sound card, based on a vague recollection of a suggestion I posted some time ago to comment out the module-suspend-on-idle in /etc/pulse/default.pa, for a completely different reason. My past self helped my memory, and the "Please wait until I am allowed to kill my own children" situation is yet to happen again. This is also suppressing the annoying buzzing sound of the sound card going into suspend mode, in addition to saving the children.

The problem with that message is that it always seems to happen randomly, probably depending on the state of that lazy worker at shutdown time. So checking any potential solution may take a while. I thought I may try your suggestion next, but on second thought maybe not: I am using no USB wifi. This is happening on the grand laptop, with full Trisquel 11 for regular sized people and royal ath9k wifi. There is in fact a folder named /etc/tlp.d with a unique file in it: 10-usb-autosuspend.conf. There it triumphantly says: "USB_AUTOSUSPEND=0".

" I see, carts might be convenient to carry drunks. I thought it would be a good painting. The title: Better drunks who are carrying collapsed drunks." -- MSs the Frozen.