https://bugs.kde.org/show_bug.cgi?id=365678
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #20 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=365678
Justin Zobel changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=365678
supaiku changed:
What|Removed |Added
CC||supa...@protonmail.ch
--- Comment #18 from supaiku -
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #17 from Jan-Marek Glogowski ---
Not sure if this helps. Searching for CS just shows the old lines, but now the
previous lines list (almost) the same amount of warnings:
[warning] plasmashell (unknown:0) - QXcbConnection: XCB error: 2 (BadV
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #16 from Jan-Marek Glogowski ---
Created attachment 100430
--> https://bugs.kde.org/attachment.cgi?id=100430&action=edit
xsession-errors with extended error messages via QT_MESSAGE_PATTERN
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #15 from Martin Gräßlin ---
> What's the preferred way to set a different QT_MESSAGE_PATTERN? Edit startkde?
startkde is an option, though maybe overkill. Another possibility is to edit
any environment file, e.g. /etc/environment or the loc
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #14 from Jan-Marek Glogowski ---
So this time I can confirm, that "Alt + Shift + F12" stops the compositing and
the flickering.
Guess I hit the wrong key combo last time, or I had a different problem, but
xsession-errors and dmesg show almos
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #13 from Martin Gräßlin ---
Can you change the Qt debug message pattern to get the application included? I
would like to know whether the message with the invalid command stream is from
KWin.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #12 from Jan-Marek Glogowski ---
I had some more of these problems, but it's still not reproducible. My feeling
is it's always at the end of the day, which might suggest leaking resources in
the radeon driver. I don't really know, how to deb
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #11 from Jan-Marek Glogowski ---
Created attachment 100401
--> https://bugs.kde.org/attachment.cgi?id=100401&action=edit
xsession errors from a flickering desktop
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #10 from Jan-Marek Glogowski ---
Created attachment 100400
--> https://bugs.kde.org/attachment.cgi?id=100400&action=edit
Even more broken snapshot
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #9 from Martin Gräßlin ---
oh my the looks horrible. What surprises me most is that you are able to
snapshot it with ksnapshot. Quite often such problems won't show in that case.
What's interesting is the kernel log giving us radeon errors.
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #8 from Jan-Marek Glogowski ---
Sorry that I didn't reply earlier. I tried to reproduce the problem, but failed
until today (well I didn't try to actively reproduce it, but continued my
LibreOffice (LO) development with Plasma 2 WM).
The fr
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #7 from Jan-Marek Glogowski ---
Created attachment 100208
--> https://bugs.kde.org/attachment.cgi?id=100208&action=edit
xsession-errors from my working session
It's not from the broken session, but still has a lot of troublesome looking
m
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #6 from Jan-Marek Glogowski ---
Created attachment 100206
--> https://bugs.kde.org/attachment.cgi?id=100206&action=edit
Flickering / broken desktop from ksnapshot
This time the effect was even more extreme. Last time I had to do some
inte
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #5 from Jan-Marek Glogowski ---
Created attachment 100205
--> https://bugs.kde.org/attachment.cgi?id=100205&action=edit
Linux kernel log (dmesg)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #4 from Jan-Marek Glogowski ---
Created attachment 100204
--> https://bugs.kde.org/attachment.cgi?id=100204&action=edit
KWin support information
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #2 from Martin Gräßlin ---
Might it be that LO needs glx and that's disabled in Xorg now?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #3 from Martin Gräßlin ---
any interesting output in /var/log/Xorg.0.log when it happens?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365678
Martin Gräßlin changed:
What|Removed |Added
CC||mgraess...@kde.org
--- Comment #1 from Martin
21 matches
Mail list logo
