#timjangrumpsoncomputers — Public Fediverse posts

But of course Linux = Debian.
#TimjanGrumpsOnComputers

#TimjanGrumpsOnComputers

One hour later.

"Upgrading system. Do not turn ff your computer. 0% complete"

Wee, I got my main system to hibernate and wake up again...

Except that the network interface didn't come up.

And it doesn't want to poweroff or reboot: it just sits there doing nothing.

#TimjanGrumpsOnComputers

#TimjanGrumpsOnComputers

Yet again, #fedora freezes hard instead of going to sleep.
Any recommendations on how to figure out what is causing this?

Comparing two journalctl printouts, for a successful and unsuccessful sleep respectively, and it appears to fail to reach this stage:

`
Sep 03 09:22:44 <hostname> kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Sep 03 09:22:44 <hostname> kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Sep 03 09:22:44 <hostname> kernel: ata1.00: Entering standby power mode
Sep 03 09:22:44 <hostname> kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache
Sep 03 09:22:44 <hostname> kernel: ata3.00: Entering standby power mode
Sep 03 09:22:44 <hostname> kernel: ata2.00: Entering standby power mode
`

(Forgot to post this after composing...)

XWayland crashes twice during a one hour Skype call.

Someone reported a very similar bug 6 months ago; another half dozen people made "me too" reports.

If someone is working on it, that's not visible from the bug report.

Giving up on Wayland, so trying to log out to switch to Xorg. After clicking on "leave", everything froze. Mouse, keyboard, status bar clock... hard reset, sigh.

#TimjanGrumpsOnComputers

Okay, that's enough of Gentoo for me.

No updates have succeeded for the last month, and I just wasted a full Saturday on trying to coax it to continue.
I'm still stuck on compilation failures:

#timjangrumpsoncomputers

#TimjanGrumpsOnComputers

"No Timjan, you may not delete this folder. To do so, you need permission from Timjan. [Skip] [Cancel]".

Alright, that's it.

Either I'll have to upgrade the desktop, or I'll have to leave Gentoo.

It's been compiling more or less constantly for the last week!
Yes, in many cases, it's had to restart large compilations, because they tend to crash after 5 hours .

#timjangrumpsoncomputers

And the next step was to upgrade the *desktop* from 36 to #Fedora38. (36 was a fresh install).

So far it's stuck in a loop right after 'system-upgrade reboot':
"systemd[1]: looping too fast. Throttling execution a little"

Second image: how far things has progressed after about 9 hours.

The first image is from after I rebooted to let it try again... It doesn't seem to go any further just because the reboot.

#TimjanGrumpsOnComputers
#TooDumbForLinux

#TimjanGrumpsOnComputers
Reminder to self to not use apps that saves data in binary formats.

=====

Apparently I had two versions of app 'foo' installed - an older from the repos, a newer downloaded from the website ("portable").
(Did I do that when the repo version was unavailable / broken a while back?)

#TimjanGrumpsOnComputers

I'm sorry, but I still don't get the #gnome-derived file interaction dialogs that certain applications insist on, despite being in a #KDE environment.

If I don't want to open from/save to the default location that the dialog presents, my mental model of what I'm doing comes crashing down until I rearrange myself.

#TimjanGrumpsOnComputers

What the ... snap?

`snap refresh` ?

It's enough to try to remember which tools use 'update' and which use 'upgrade' - and you come here with 'refresh'?

F*ck, a reboot didn't fix the pam spew.

And now sddm doesn't start properly either. So no graphics beyond one mouse pointer on a black screen.

F*ck.

I don't want to reinstall Gentoo, too.

Well, I guess I really have to get on that fedora reinstallation, then

#TimjanGrumpsOnComputers

That was another episode of #TimjanGrumpsOnComputers

#TimjanGrumpsOnComputers

"Oh, you want to accomplish <blah>? The nice, powerful piece of software FooBaz will do that for you"

$ sudo emerge --ask FooBaz
(FooBaz is installed)
$ FooBaz
bash: FooBaz: command not found
$ foobaz
bash: foobaz: command not found
$ man foobaz
No manual entry for foobaz

$ ddg "foobaz get started"
"Just double click on the icon"

#TimjanGrumpsOnComputers

Trying to wake up desktop from sleep.

Mouse works, keyboard does not. Can't unlock.

Ssh in from phone. Tries to suspend again. Wake up a second time.

Bright white screen, no indication of mouse or keyboard.

Duck this, I'm too tired to deal with this ship.

#TimjanGrumpsOnComputers

Oh, those are USE flags, not packages

/me is too dumb for Gentoo

#TimjanGrumpsOnComputers

Oh, there's a workaround:

don't update the flatbpaks, only the themes

only select ONE theme at a time (else it'll crash)

some will fail for "not finding <some file>"... and crash.

After certain crashes, it'll be unable to start up all way again. I'll probably see it again after the next reboot and/or gentoo reinstallation.

:shrug:

#TimjanGrumpsOnComputers

But I guess I should have known what I should have installed to get the backtrace for the tool to generate the backtrace for what broke in the first place.

#TimjanGrumpsOnComputers

...
Okay, this is repeatable, yadda yadda.
"Fetching backtrace"..
"The debugger has quit unexpectedly".
"The backtrace could not be generated".

Uhm, okay?

"This report does not contain enough information for the developers".

"Finish".

So no report generated, this time either. Good thing I can update anything important through CLI, then.

#TimjanGrumpsOnComputers

#KDE wants to use its tool ("Discover") to update the system. Today, I let it.
It found the flatpaks, and the various themes I've installed.
Okay, let's install them...
First, it takes 5 minutes to "fetch updates" (why not already in the background?)
Installing...
"We're sorry, discover closed unexpectedly", and please report the error. Sure, let's report the bug.
"The assistant will analyze the crash information and guide you..."

...

#TimjanGrumpsOnComputers

Went back to AwesomeWM.
Tried to suspend to disk ('loginctl suspend'); didn't notice until next morning that it didn't do anything.
Tried to suspend again. 4 attempts; some did nothing, some 'suspended' for about 5 seconds after which the system woke up by itself. 5th attempt successful. Or?

Now, trying to wake up the system. Power indicator is on but the system doesn't respond to any inputs. (Keyboard, mouse, ssh).

Hard power cycle, then.

#TimjanGrumpsOnComputers
> The following REQUIRED_USE flag constraints are unsatisfied:
> foo? ( any-of ( bar baz ) )

> no ebuilds to satisfy "bar"
> no ebuilds to satisfy "baz"

Okay, what's next?