Re: logging no longer standard?
On 8/7/23 07:50, Henning Follmann wrote:
On Sat, Aug 05, 2023 at 03:12:39PM -0400, Greg Wooledge wrote:
On Sat, Aug 05, 2023 at 08:03:27PM +0100, Joe wrote:
On Sat, 5 Aug 2023 15:09:41 +0000
Andy Smith <andy@strugglers.net> wrote:
[...]
In some cases, the release notes actually do tell you how to get back
to normal.
err,
"how to get back."
Normal is the new systemd
And the new logging is journal.d or some such. And I so far have not
been able to detect from reading its tail equ, what port of which card
is WHICH PHYSICAL DRIVE? Logging is IMO incomplete until I can easily
locate the drive plugged into sata 4 or 5, starting at base 0, of the
2nd sata controller plugged into my machine. If its there, but I can't
see it, explain to ME how to make that connection. The log is full of
info but gives virtually zero clues for stuff that's locking this
machine up tight, so tight it takes 2 minutes to register that the front
panels reset button has been pressed. A digiKam AppImage cannot open and
write an output file to my raid10 /home partitian. However the database
can write its files A Cura AppImage waits for around 2 minutes to open
an output file requestor, presumably because the default path is into my
raid10. If in my impatience, I click save to disk a second time, Its a
50-50 bet I'll wind up using a root session of htop to kill it and start
all over again.
Absolutely none of that makes it to the log I can read with sudo.
This causes me to ask about any new ACL's bookworm might have put in
place, but questions about that have so far been totally ignored. I
according to an ls -lR, own that raid10 lock, stock and barrel, so why
can't apps running as me, write to it without the 2 minute wait? And
why is there no d------ clue in the logs root can read, showing why this
is happening.
All most of you can do is give Gene more hell, he broke it again. W/o
telling me what I actually did wrong. The 4 main apps I use, 3 of them
are AppImages because they are under constant development, and the
version supplied is old & slow. OpenSCAD is 2+ years old in the repo's,
the current AppImage is now around 8 releases newer, quite a bit more
complete AND at least 10x faster. Same for cura, yours is many versions
out of date. 4.13 vs 5.4.0. And I've checked, the repo version also has
this same blockage. Why? What log can I look at that might actually TELL
me something?
All I can see in journalctl's log is gigabytes spewed by plasmashell,
and which I can't find what its REAL name is as I generally use konsole
for a terminal screen. Sample:
ug 07 09:11:07 coyote plasmashell[2385]: Could not find the Plasmoid for
Plasma::FrameSvgItem(0x559c2dbc5990) QQmlContext(0x559c29de8860)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Aug 07 09:13:55 coyote kwin_x11[2346]: kwin_core: XCB error: 3
(BadWindow), sequence: 15618, resource id: 32931609, major code: 129
(SHAPE), minor code: 6 (Input)
Aug 07 09:13:55 coyote kwin_x11[2346]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 15619, resource id: 32931609, major
code: 2 (ChangeWindowAttributes), minor code: 0
Aug 07 09:20:03 coyote plasmashell[2385]: Could not find the Plasmoid
for Plasma::FrameSvgItem(0x559c2da12130) QQmlContext(0x559c29de8860)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Aug 07 09:20:03 coyote plasmashell[2385]: Could not find the Plasmoid
for Plasma::FrameSvgItem(0x559c2da12130) QQmlContext(0x559c29de8860)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Aug 07 09:20:08 coyote kwin_x11[2346]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 61182, resource id: 44044366, major
code: 15 (QueryTree), minor code: 0
Aug 07 09:26:11 coyote plasmashell[2385]: Could not find the Plasmoid
for Plasma::FrameSvgItem(0x559c2d983bd0) QQmlContext(0x559c29de8860)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Aug 07 09:26:11 coyote plasmashell[2385]: Could not find the Plasmoid
for Plasma::FrameSvgItem(0x559c2d983bd0) QQmlContext(0x559c29de8860)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Aug 07 09:29:13 coyote plasmashell[2385]: Could not find the Plasmoid
for Plasma::FrameSvgItem(0x559c2da372e0) QQmlContext(0x559c29de8860)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Aug 07 09:29:13 coyote plasmashell[2385]: Could not find the Plasmoid
for Plasma::FrameSvgItem(0x559c2da372e0) QQmlContext(0x559c29de8860)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Aug 07 09:34:31 coyote kwin_x11[2346]: kwin_core: XCB error: 3
(BadWindow), sequence: 28339, resource id: 32949194, major code: 129
(SHAPE), minor code: 6 (Input)
Aug 07 09:34:31 coyote kwin_x11[2346]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 28340, resource id: 32949194, major
code: 2 (ChangeWindowAttributes), minor code: 0
Aug 07 09:34:37 coyote ksmserver[2926]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 15362, resource id: 16780529, major
code: 18 (ChangeProperty), minor code: 0
Aug 07 09:34:37 coyote ksmserver[2926]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 15363, resource id: 16780529, major
code: 18 (ChangeProperty), minor code: 0
Aug 07 09:34:49 coyote kwin_x11[2346]: kwin_core: XCB error: 3
(BadWindow), sequence: 32066, resource id: 32949507, major code: 129
(SHAPE), minor code: 6 (Input)
Aug 07 09:34:49 coyote kwin_x11[2346]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 32067, resource id: 32949507, major
code: 2 (ChangeWindowAttributes), minor code: 0
Aug 07 09:35:11 coyote plasmashell[2385]: Could not find the Plasmoid
for Plasma::FrameSvgItem(0x559c2daae510) QQmlContext(0x559c29de8860)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Aug 07 09:35:11 coyote plasmashell[2385]: Could not find the Plasmoid
for Plasma::FrameSvgItem(0x559c2daae510) QQmlContext(0x559c29de8860)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Aug 07 09:35:15 coyote kwin_x11[2346]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 38526, resource id: 44044419, major
code: 15 (QueryTree), minor code: 0
Aug 07 09:38:38 coyote kwin_x11[2346]: kwin_core: XCB error: 3
(BadWindow), sequence: 59056, resource id: 32952602, major code: 129
(SHAPE), minor code: 6 (Input)
Aug 07 09:38:38 coyote kwin_x11[2346]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 59057, resource id: 32952602, major
code: 2 (ChangeWindowAttributes), minor code: 0
Aug 07 09:38:39 coyote ksmserver[2926]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 19938, resource id: 16780546, major
code: 18 (ChangeProperty), minor code: 0
Aug 07 09:38:39 coyote ksmserver[2926]: qt.qpa.xc
What for instance, do I install to stop this crap so I might see a real
message?
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>
Reply to: