[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2023-05-27 Thread Alex
https://bugs.kde.org/show_bug.cgi?id=461316

Alex  changed:

   What|Removed |Added

 CC||leon.expr...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2023-01-19 Thread Andreas
https://bugs.kde.org/show_bug.cgi?id=461316

Andreas  changed:

   What|Removed |Added

 CC||ads-kde-b...@wars-nicht.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2023-01-11 Thread eris23
https://bugs.kde.org/show_bug.cgi?id=461316

eris23  changed:

   What|Removed |Added

 CC||jdkat...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-12-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=461316

valdi...@gmail.com changed:

   What|Removed |Added

 CC||valdi...@gmail.com

--- Comment #57 from valdi...@gmail.com ---
*** Bug 463231 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-12-17 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=461316

Vlad Zahorodnii  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=461132

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-12-14 Thread Sam James
https://bugs.kde.org/show_bug.cgi?id=461316

Sam James  changed:

   What|Removed |Added

 CC||s...@gentoo.org

--- Comment #56 from Sam James  ---
(In reply to Vassilis Virvilis from comment #55)
> Out of curiosity,
> 
> I have no experience with opengl/mesa so the question may be invalid.
> 
> The main culprit that is being reversed is a patch that was adjusting
> reference counting of ... something (opengl context? not sure).
> 

Anything to do with resource management is tricky :)

> The question is: Are we sure that the patch being reversed is buggy? We know
> for sure that it caused a regression and kwin crashes. However, isn't it
> possible that this is a failure of Qt/KDE/Plasma/kwin to handle the new
> "correct" behavior that the patch introduced?
> 

I'm sure that the Mesa folks wouldn't have reverted it unless they thought
it looked like an issue on their end.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-30 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #55 from Vassilis Virvilis  ---
Out of curiosity,

I have no experience with opengl/mesa so the question may be invalid.

The main culprit that is being reversed is a patch that was adjusting reference
counting of ... something (opengl context? not sure).

The question is: Are we sure that the patch being reversed is buggy? We know
for sure that it caused a regression and kwin crashes. However, isn't it
possible that this is a failure of Qt/KDE/Plasma/kwin to handle the new
"correct" behavior that the patch introduced?

Don't get me wrong I am thrilled and grateful that you guys found it and have
the mesa guys reverting it but I am just curious...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-27 Thread Karl Q
https://bugs.kde.org/show_bug.cgi?id=461316

Karl Q  changed:

   What|Removed |Added

 CC||bugs.kde.org@karlquinsland.
   ||com

--- Comment #54 from Karl Q  ---
(In reply to xxmlud from comment #53)
> Hello, in which version of Mesa is the problem solved?

The URL @ the top of the ticket points to
[this](https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19972) issue
which is part of the `22.3` release which looks to be _almost_ ready to ship.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-27 Thread xxmlud
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #53 from xxmlud  ---
Hello, in which version of Mesa is the problem solved?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-25 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=461316

Vlad Zahorodnii  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
URL||https://gitlab.freedesktop.
   ||org/mesa/mesa/-/merge_reque
   ||sts/19972

--- Comment #52 from Vlad Zahorodnii  ---
Fixed in Mesa.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-23 Thread João Vidal da Silva
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #51 from João Vidal da Silva  ---
Following the last comment by CapsAdmin: it happened to me during the process
of opening +/- 20 files at once in LibreOffice Writer, using Dolphin.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-23 Thread CapsAdmin
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #50 from CapsAdmin  ---
So it might be finally solved?

I made a duplicate issue, but having read the comments here I can add that it
seems/feels to happen when:

- launching an application that creates an opengl context or something that
triggers the desktop turning off the compositor (for example me developing an
opengl application)
- screen lock due to inactivity. (not sure if happens on lock out or logging
back in though)
- abnormally high gpu usage (ie running something very gpu intensive by mistake
when programming)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-23 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=461316

Zamundaaa  changed:

   What|Removed |Added

 CC||eliashogstv...@gmail.com

--- Comment #49 from Zamundaaa  ---
*** Bug 462143 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-23 Thread Sebastian Weisgerber
https://bugs.kde.org/show_bug.cgi?id=461316

Sebastian Weisgerber  changed:

   What|Removed |Added

 CC||sebastian@dystopianfuture.d
   ||e

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-23 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=461316

Vlad Zahorodnii  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #48 from Vlad Zahorodnii  ---
I can reproduce the issue with the attached test app. Thank you, Oleg, for
providing it and also bisecting mesa. :)

kwin 5.26 didn't have any significant X11 changes besides one fix to prevent
frozen windows due to xcb_generate_id() returning a bad id, however this bug is
reproducible even after reverting those changes, so I think that we can rule
out kwin.

One peculiar thing about this bug is that if compositing is disabled,
reproducer v3 can "hang" xorg. That's it, at some point, notification windows
will stop popping up and other X11 connections will hang in general. Restarting
plasmashell helps to fix that.

kwin gets killed when it repaints the screen, specifically binds the window
texture

Thread 1 "kwin_x11" received signal SIGTERM, Terminated.
0x7fc511503120 in ?? () from /usr/lib/libqaccessibilityclient-qt5.so.0
(gdb) bt
#0  0x7fc511503120 in  () at /usr/lib/libqaccessibilityclient-qt5.so.0
#1  0x7fc51168eaae in  () at /lib64/ld-linux-x86-64.so.2
#2  0x7fc50de53fa5 in  () at /usr/lib/libc.so.6
#3  0x7fc50de54120 in  () at /usr/lib/libc.so.6
#4  0x7fc50ec05be6 in _XDefaultIOError () at /usr/lib/libX11.so.6
#5  0x7fc50ec08eb3 in _XIOError () at /usr/lib/libX11.so.6
#6  0x7fc50ec0c5c9 in _XFlush () at /usr/lib/libX11.so.6
#7  0x7fc50ec0c85e in _XGetRequest () at /usr/lib/libX11.so.6
#8  0x7fc50ec010ee in XSync () at /usr/lib/libX11.so.6
#9  0x7fc5082e00cd in  () at /usr/lib/libGLX_mesa.so.0
#10 0x5577ad004ec4 in KWin::GlxPixmapTexturePrivate::onDamage()
(this=0x5577af38c5d0)
at
/home/vlad/Workspace/kwin/src/backends/x11/standalone/x11_standalone_glx_backend.cpp:921
#11 0x7fc50efb0b29 in KWin::GLTexture::bind() (this=) at
/home/vlad/Workspace/kwin/src/libkwineffects/kwingltexture.cpp:454
#12 0x7fc511235a78 in KWin::SceneOpenGL::render(KWin::Item*, int, QRegion
const&, KWin::WindowPaintData const&)

so if plasmashell manages to "break" xorg, it sort of explains why kwin_x11
gets killed

I built mesa 22.1.7 and the issue is not reproducible there. I didn't bisect
mesa changes, but the ones mentioned in
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674 look like good
candidates.

It looks like glXMakeCurrent(Display, Window, GLXContext) got broken in Mesa
22.2. It's worth noting that Qt uses glXMakeCurrent(Display, Window,
GLXContext) rather than glXMakeCurrent(Display, GLXWindow, GLXContext). I made
a quick and dirty patch to test that theory
https://invent.kde.org/-/snippets/2423. I ran reproducer v3 a couple of times,
the bug doesn't seem to occur.

Regardless, glXMakeCurrent(Display, Window, GLXContext) is still a valid case
and it must work.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-22 Thread Aleš Svoboda
https://bugs.kde.org/show_bug.cgi?id=461316

Aleš Svoboda  changed:

   What|Removed |Added

 CC||svo...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-21 Thread xxmlud
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #47 from xxmlud  ---
Hi, kde-bugs-io-drs...@spamfilter.de. Is there any way we users can help?

I have disabled notifications for several days and have not had any crashes.

Regards

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-19 Thread João Vidal da Silva
https://bugs.kde.org/show_bug.cgi?id=461316

João Vidal da Silva  changed:

   What|Removed |Added

 CC||joao.vidal.si...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=461316

kde-bugs-io-drs...@spamfilter.de changed:

   What|Removed |Added

 CC||kde-bugs-io-drsf32@spamfilt
   ||er.de

--- Comment #46 from kde-bugs-io-drs...@spamfilter.de ---
I keep having this for weeks now and can confirm the last line before X goes
down always is the BadDamage one.
I think it started like 6-8 weeks ago. Once it starts to happen, restarting
kwin_x11 mostly won't help for any longer period of time. In the best cases it
lasts long enough to allow for a controlled Desktop shutdown, package update
and reboot - sometimes not even that. After reboot it keeps going for another
24 to 48 hours before kwin crashes start again. I 

I don't think notifications are the one culprit. Yes, notifications sometimes
seem to trigger the problem (notably causing latte dock to hang until killed),
but not always. Sometimes a mere desktop switch apparently is enough to get it
down again. In the worst cases just coming back to the x11 VT (remapping the
desktop) did end it. I'll keep re-starting and updating until it gets better
since I get it there is a promising patch now. But the general instability
really is getting to me :-) 
If you want logs of anything you don't already have, drop me a line.
Thanks for looking into this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-17 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #45 from Oleg Solovyov  ---
(In reply to xxmlud from comment #44)
> So far since I disabled notifications in my application, I haven't had any
> crashes. Are you sure it's a Mesa bug?

Retry with hardware acceleration disabled.
It crashes after updating Mesa 22.1 -> 22.2 branch

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-17 Thread xxmlud
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #44 from xxmlud  ---
Hello,

So far since I disabled notifications in my application, I haven't had any
crashes. Are you sure it's a Mesa bug?

I will report next Tuesday if I had any new crashes.

Regards

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-16 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #43 from Oleg Solovyov  ---
(In reply to xxmlud from comment #42)
> Could it be related to some bug in "(org.kde.plasma.notifications)"?
> Can you check if it appears in the same situation?

No, it is a Mesa bug, which has been bisected and tested with reproducer (see
attachments)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-16 Thread xxmlud
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #42 from xxmlud  ---
Hello,

In my case, the "crash" comes after a notification comes up.

Could it be related to some bug in "(org.kde.plasma.notifications)"?
Can you check if it appears in the same situation?

For the moment I have disabled notifications in the application that gives me
more notifications on the screen.

Regards

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-16 Thread xxmlud
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #41 from xxmlud  ---
*** Bug 461333 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-16 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #40 from Oleg Solovyov  ---
(In reply to Silvan Calarco from comment #34)
> I also used to have the problems reported by Daniel but in my case it seems
> they stopped happening since Qt update to 5.15.7 (with KDE patches applied
> to qtbase and qtdeclarative modules).

It didn't help for me

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-16 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #39 from Vlad Zahorodnii  ---
It looks like
https://invent.kde.org/plasma/kwin/-/commit/7eca5f44dbc2b094468e7430f784ff1e7f372989
was not backported to 5.26. I backported it just now, hopefully it's going to
reduce the amount of BadDamage errors.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-16 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #38 from Vlad Zahorodnii  ---
Do you know what tends to cause

kwin_core: XCB error: 152 (BadDamage), sequence: 48054, resource id: 69786721,
major code: 143 (DAMAGE), minor code: 3 (Subtract)

e.g. did you close some window?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-15 Thread xxmlud
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #37 from xxmlud  ---
Hello,

These are the versions that I use.

KDE Plasma: 5.26.3
KDE Frameworks: 5.99.0
QT Version: 5.15.7

Is there any way to put kwin_x11 in debug mode? I have seen that in Wayland it
is possible, but in X11 I have not found anything.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-15 Thread Daniel Schulte
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #36 from Daniel Schulte  ---
(In reply to Silvan Calarco from comment #34)
> I also used to have the problems reported by Daniel but in my case it seems
> they stopped happening since Qt update to 5.15.7 (with KDE patches applied
> to qtbase and qtdeclarative modules).
> Currently I didn't have any issues at all in the last 5 days on two
> computers (with Intel and AMD/ATI chipsets) where they happened once every
> 1-2 days. I also run many times Oleg's reproducer without any issue. It may
> just be a coincidence, BTW I also updated Mesa to 22.2.3 and KDE Plasma to
> 5.26.3, are you all using such releases?
I'm running these version except that all the Qt Packages have the KDE patches,
as that is what ArchLinux ships at the moment.

For me the v3 reproducer works. I'm, thinking of putting a check in there to
see if KWin is still alive before sending the next notification and quit if
not. Maybe it's somewhat consistent how many notifications it takes for KWin to
crash.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-15 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #35 from Oleg Solovyov  ---
(In reply to Silvan Calarco from comment #34)
> I also used to have the problems reported by Daniel but in my case it seems
> they stopped happening since Qt update to 5.15.7 (with KDE patches applied
> to qtbase and qtdeclarative modules).
> I also run many times Oleg's reproducer without any issue. It may
> just be a coincidence, BTW I also updated Mesa to 22.2.3 and KDE Plasma to
> 5.26.3, are you all using such releases?

All the same, except Qt release (5.15.6)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-15 Thread Silvan Calarco
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #34 from Silvan Calarco  ---
I also used to have the problems reported by Daniel but in my case it seems
they stopped happening since Qt update to 5.15.7 (with KDE patches applied to
qtbase and qtdeclarative modules).
Currently I didn't have any issues at all in the last 5 days on two computers
(with Intel and AMD/ATI chipsets) where they happened once every 1-2 days. I
also run many times Oleg's reproducer without any issue. It may just be a
coincidence, BTW I also updated Mesa to 22.2.3 and KDE Plasma to 5.26.3, are
you all using such releases?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-15 Thread Daniel Schulte
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #33 from Daniel Schulte  ---
Not sure how much of this is just a coincidence or if it is actually related:
Before I had the "KWin just quits" issue I had problems where KWin sometimes
just "forgot to update a window", meaning a window starts flickering between
some old window states instead of rendering new ones. The issue was "fixable"
by toggling compositing off and on again (using Ctrl+Shift+F12 by default I
think). I had that issue for a few years but never really investigated as just
pressing the keys was an easy work around for me. How often this happened
varied from once every few days to multiple times an hour, though subjectively
it was occurring more often lately than a year ago.

At the beginning of November I changed my default browser from Chrome to
Firefox and that issue didn't happen anymore for a few days so I thought maybe
it was a wired interaction between Chrome and KWin. Then this issue started
happening.

What both issues/behaviors have in common is that I noticed that usually there
are notifications being shown when it happens. The "old issue" with stuck
rendering showed the notifications just fine and also still updated a small
(maybe 30 px?) region around the notification popup. With this issue I saw a
notification pop up appear as a black rectangle and then KWin crashing (and
sometimes also Plasmashell hanging after the KWin restart).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-15 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #32 from Oleg Solovyov  ---
(In reply to Vassilis Virvilis from comment #30)
> (In reply to Oleg Solovyov from comment #27)
> > Older version would spam notifications so hard it could have killed any
> > version of Mesa
> 
> 
> But but... a client shouldn't be able to crash a library... My world
> shutters...
> 
> 
> Seriously though. If I try to open thousands or million of files I wouldn't
> expect a crash in libc or in the kernel. I would expect an error "out of
> resources" but then I guess my program would crash because I wouldn't have
> been checking for errors. Is something like that goes on here?

I suspect something happens with rendering process

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-14 Thread xxmlud
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #31 from xxmlud  ---
I do work with two monitors, and I wanted to find some relation.
 When kwin breaks and I have the Konsole in focus I restart the service
"display-manager", otherwise I connect with alt+f2. The truth is that the logs
are not enlightening. I am lost with this issue

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-14 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #30 from Vassilis Virvilis  ---
(In reply to Oleg Solovyov from comment #27)
> Older version would spam notifications so hard it could have killed any
> version of Mesa


But but... a client shouldn't be able to crash a library... My world
shutters...


Seriously though. If I try to open thousands or million of files I wouldn't
expect a crash in libc or in the kernel. I would expect an error "out of
resources" but then I guess my program would crash because I wouldn't have been
checking for errors. Is something like that goes on here?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-14 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #29 from Vassilis Virvilis  ---
(In reply to xxmlud from comment #28)
> Hello, Vassilis Virvilis, I am in the same situation as you. But I don't
> know how to provide some logs that can help with this problem.
> One question, do you have two monitors?

No. I have one monitor per machine. But I have work and home computer. Some
times I use xpra to access the work machine.

Sometimes I got a local crash. Sometimes I got a remote crash. Sometimes I have
keyboard other I have mouse. Sometimes the keyboard input is borked like a
modifier (like Ctrl or Alt) is pressed. The borked modifier is probably a
remote thing only but I am not 100% sure. It's all over the place really.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-14 Thread xxmlud
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #28 from xxmlud  ---
Hello, Vassilis Virvilis, I am in the same situation as you. But I don't know
how to provide some logs that can help with this problem.
One question, do you have two monitors?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-14 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #27 from Oleg Solovyov  ---
(In reply to Vassilis Virvilis from comment #26)
> I am not sure I am helping anyone with these awfully incomplete reports. I
> will try my best to run the reproducer. Maybe I would be able to report
> something more useful.

Older version would spam notifications so hard it could have killed any version
of Mesa

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-14 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #26 from Vassilis Virvilis  ---
Thanks for looking so hard at this. Much appreciated.

Yesterday I had another instance of this (or another bug). This time kwin
wasn't killed (windows have their titles) but kwin was unresponsive. However I
had keyboard and I was able to run 'kwin --replace' and then everything got ok.

I don't remember how I got to the terminal though. Either I was already there
(konsole had focus) or Alt-Tab worked which strikes me as somewhat weird.

Unfortunately no logs for this new one.

I am not sure I am helping anyone with these awfully incomplete reports. I will
try my best to run the reproducer. Maybe I would be able to report something
more useful.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-14 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #25 from Oleg Solovyov  ---
(In reply to Oleg Solovyov from comment #24)
> Created attachment 153678 [details]
> reproducer v3
> 
> Better reproducer, gave 31b04e420b0eb080084c6323066ea0b83929d59e on Mesa

nd 768238fd should be reverted too.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-11 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

Oleg Solovyov  changed:

   What|Removed |Added

 Attachment #153667|0   |1
is obsolete||

--- Comment #24 from Oleg Solovyov  ---
Created attachment 153678
  --> https://bugs.kde.org/attachment.cgi?id=153678&action=edit
reproducer v3

Better reproducer, gave 31b04e420b0eb080084c6323066ea0b83929d59e on Mesa

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-11 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #23 from Oleg Solovyov  ---
(In reply to Vassilis Virvilis from comment #22)
> This is probably another bug. I looked around but can't anything. Probable
> bad keywords. (no keyboard input)

Unfortunately, if it is, it makes difficult to bisect the original one.

> *** Do you happen to know what process I need to restart to gain keyboard
> again?. I had to reboot. and I lost a lot of state.

Dunno, sorry. Just making tests to figure out what happens and why

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-11 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #22 from Vassilis Virvilis  ---
This is probably another bug. I looked around but can't anything. Probable bad
keywords. (no keyboard input)

This time my desktop hanged. (Not sure if I had mouse pointer). Certainly not
keyboard. Windows decorations were there.

I switch to console and back to X. Now I have mouse pointer but no click. No
keyboard.

Now I can't Ctrl-Alt-F2. I ssh and do sudo chvt 2

I restart kwin from console (DISPLAY=:0 kwin --replace)

Now I have mouse pointer + click but still no keyboard.

I restarted plasmashell. Kate crashed as per:
https://bugs.kde.org/show_bug.cgi?id=461318

Still no keyboard input.

*** Do you happen to know what process I need to restart to gain keyboard
again?. I had to reboot. and I lost a lot of state.

In the meantime as I promised I straced both kwin and plasmashell. Everything
looks ok. They are waiting for input:

kwin:
futex(0x56164c8eaec4, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
FUTEX_BITSET_MATCH_ANY

plasmashell:
futex(0x55796b5c3f14, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
FUTEX_BITSET_MATCH_ANY

This bug is more severe and more difficult / rare to trigger. If somebody has a
pointer for this bug  I will post there. Otherwise I will open a new bug later
today.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #21 from Vassilis Virvilis  ---
Aa a reproducer. Thanks for that.

I will try it at home and report back.

I hope that you are onto something. If memory serves  a lot of the crashes are
related with virtual dekstop switches - not sure if that is a Knotification
though...

We 'll see. Much appreciated anyway...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #20 from Oleg Solovyov  ---
Created attachment 153667
  --> https://bugs.kde.org/attachment.cgi?id=153667&action=edit
how to crash

Additionally, put

[Notifications]
PopupTimeout=100

into ~/.config/plasmanotifyrc and relogin

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread xxmlud
https://bugs.kde.org/show_bug.cgi?id=461316

xxmlud  changed:

   What|Removed |Added

 CC||xxm...@gmail.com

--- Comment #19 from xxmlud  ---
Hi, this same thing happens to me, Kwin dies randomly, what I do to get back to
normal I run alt+f2 and type "systemctl restart display-manager".

I have a bug created, but this one seems more extensive. My graphics card is an
Intel

Traducido con DeepL
(https://www.deepl.com/app/?utm_source=ios&utm_medium=app&utm_campaign=share-translation

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #18 from Oleg Solovyov  ---
(In reply to Silvan Calarco from comment #17)
> As you may have noticed an upstream bug has been opened here:
> https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674

It's mine

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Silvan Calarco
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #17 from Silvan Calarco  ---
(In reply to Oleg Solovyov from comment #16)
> (In reply to Silvan Calarco from comment #15)
> > Hello, I'm facing this problem too.
> > If I understand the problem might be resolved by reverting commit
> > 768238fdc06eed3dce36da3baf811cb70db42b5c, is that correct? Or the two last
> > comments state something different? Thanks!
> 
> 7682 is bad, not sure if it's the same about 151a

Ok, I'm testing now Mesa 22.2.3 with 7682 reverted.
In my case the problem happens seldomly usually upon the creation of a
notification box which is rendered black and it may take some days before I may
say that the issue is fixed.
As you may have noticed an upstream bug has been opened here:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #16 from Oleg Solovyov  ---
(In reply to Silvan Calarco from comment #15)
> Hello, I'm facing this problem too.
> If I understand the problem might be resolved by reverting commit
> 768238fdc06eed3dce36da3baf811cb70db42b5c, is that correct? Or the two last
> comments state something different? Thanks!

7682 is bad, not sure if it's the same about 151a

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Silvan Calarco
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #15 from Silvan Calarco  ---
(In reply to Oleg Solovyov from comment #14)
> (In reply to Oleg Solovyov from comment #13)
> > (In reply to Oleg Solovyov from comment #12)
> > > (In reply to Vassilis Virvilis from comment #11)
> > > > This one?
> > > > https://gitlab.freedesktop.org/mesa/mesa/-/commit/
> > > > 768238fdc06eed3dce36da3baf811cb70db42b5c
> > > 
> > > Yes. Before this commit kwin never exited for me (not a crash)
> > 
> > just exited on commit 768238fdc06eed3dce36da3baf811cb70db42b5c
> 
> commit 151aa19c21575ba498a19c48e84474107a4eb304*

Hello, I'm facing this problem too.
If I understand the problem might be resolved by reverting commit
768238fdc06eed3dce36da3baf811cb70db42b5c, is that correct? Or the two last
comments state something different? Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #14 from Oleg Solovyov  ---
(In reply to Oleg Solovyov from comment #13)
> (In reply to Oleg Solovyov from comment #12)
> > (In reply to Vassilis Virvilis from comment #11)
> > > This one?
> > > https://gitlab.freedesktop.org/mesa/mesa/-/commit/
> > > 768238fdc06eed3dce36da3baf811cb70db42b5c
> > 
> > Yes. Before this commit kwin never exited for me (not a crash)
> 
> just exited on commit 768238fdc06eed3dce36da3baf811cb70db42b5c

commit 151aa19c21575ba498a19c48e84474107a4eb304*

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Silvan Calarco
https://bugs.kde.org/show_bug.cgi?id=461316

Silvan Calarco  changed:

   What|Removed |Added

 CC||silvan.cala...@mambasoft.it

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #13 from Oleg Solovyov  ---
(In reply to Oleg Solovyov from comment #12)
> (In reply to Vassilis Virvilis from comment #11)
> > This one?
> > https://gitlab.freedesktop.org/mesa/mesa/-/commit/
> > 768238fdc06eed3dce36da3baf811cb70db42b5c
> 
> Yes. Before this commit kwin never exited for me (not a crash)

just exited on commit 768238fdc06eed3dce36da3baf811cb70db42b5c

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #12 from Oleg Solovyov  ---
(In reply to Vassilis Virvilis from comment #11)
> This one?
> https://gitlab.freedesktop.org/mesa/mesa/-/commit/
> 768238fdc06eed3dce36da3baf811cb70db42b5c

Yes. Before this commit kwin never exited for me (not a crash)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #11 from Vassilis Virvilis  ---
This one?
https://gitlab.freedesktop.org/mesa/mesa/-/commit/768238fdc06eed3dce36da3baf811cb70db42b5c

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=461316

Oleg Solovyov  changed:

   What|Removed |Added

 CC||mcp...@altlinux.org

--- Comment #10 from Oleg Solovyov  ---
Try reverting Mesa commit 768238fd

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-10 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #9 from Vassilis Virvilis  ---
In my home. I upgraded to 5.26.3 (debian unstable) and was hit again by this .
Not sure which error code though, because it was the first kwin instance and
not one that I run from terminal so I didn't have stderr output.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=461316

mira...@mirandastreeter.com changed:

   What|Removed |Added

 CC||mira...@mirandastreeter.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-08 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #8 from Vassilis Virvilis  ---
I also got the 'error 2: No such file or directory' error:

The X11 connection broke: I/O error (code 1)
XIO:  fatal IO error 2 (No such file or directory) on X server ":0"
  after 5589828 requests (5589828 known processed) with 0 events remaining.

kwin killed so no strace.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=461316

hexclo...@outlook.com changed:

   What|Removed |Added

 CC||hexclo...@outlook.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-05 Thread Daniel Schulte
https://bugs.kde.org/show_bug.cgi?id=461316

Daniel Schulte  changed:

   What|Removed |Added

 CC||trilader+kdeb...@gmail.com

--- Comment #7 from Daniel Schulte  ---
I also have encountered this (quite a lot) in the last days (since I updated to
5.26.x). Sometimes I need to `kwin_x11 --replace` multiple times a day -
sometimes I also then need to `pkill plasmashell && kstart5 plasmashell` as it
becomes non-responsive.

Messages I've seen so far:
The X11 connection broke: I/O error (code 1) X connection to :0 broken
(explicit kill or server shutdown)
The X11 connection broke: I/O error (code 1) XIO:  fatal IO error 22 (Invalid
argument) on X server ":0" after 171015 requests (171015 known processed) with
0 events remaining.
The X11 connection broke: I/O error (code 1) XIO:  fatal IO error 2 (No such
file or directory) on X server ":0" after 78026 requests (78026 known
processed) with 0 events remaining.

There are more which I don't have anything saved for as they are from
re-running kwin_x11 from a terminal.
There isn't anything interesting in dmesg or Xorg.0.log.

System information:
Operating System: Arch Linux
KDE Plasma Version: 5.26.2
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.7
Kernel Version: 6.0.6-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Xeon® CPU E3-1245 v5 @ 3.50GHz
Memory: 31,1 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series
Manufacturer: Supermicro
Product Name: Super Server
System Version: 0123456789

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-04 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #6 from Vassilis Virvilis  ---
So far the X errors are:

1. Local: The X11 connection broke: I/O error (code 1) X connection to :0
broken (explicit kill or server shutdown). --> kwin killed
2. Local: The X11 connection broke: I/O error (code 1) XIO:  fatal IO error 0
(Success) on X server ":0" --> kwin killed
3. Remote:  The X11 connection broke: I/O error (code 1) XIO:  fatal IO error
22 (Invalid argument) on X server ":0" after 6963214 requests (6963214 known
processed) with 0 events remaining. --> kwin killed

I will keep updating the list.

Note: It looks like the hung case is much rarer. Maybe it happens when the
plasmashell is busted and it is actually a different bug. When kwin dies user
input are dying too so I can't be really sure that plasmashell is actually
alive before I restart kwin.

Maybe all 3 above are different bugs. I certainly hope that this isn't the case
though because it looks terribly difficult to diagnose this without a backtrace
let alone 3 of them.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-04 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #5 from Vassilis Virvilis  ---
It did it a again this on (remote with xpra) unlock time with error code 22.
I am posting only a few lines of intermixed output (plasmashell & kwin) just in
case somebody may spot something.

qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 16004, resource
id: 60817412, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 16008, resource
id: 60817421, major code: 18 (ChangeProperty), minor code: 0
QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0
Could not find the Plasmoid for Plasma::FrameSvgItem(0x563937d58010)
QQmlContext(0x563934b35570)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Could not find the Plasmoid for Plasma::FrameSvgItem(0x563937d58010)
QQmlContext(0x563934b35570)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:248:21:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:248:21:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:248:21:
QML SelectableLabel: Binding loop detected for property "implicitHeight"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/SelectableLabel.qml:40:5:
QML TextArea: Binding loop detected for property "implicitHeight"
The X11 connection broke: I/O error (code 1)
XIO:  fatal IO error 22 (Invalid argument) on X server ":0"
  after 6963214 requests (6963214 known processed) with 0 events remaining.
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 32106, resource
id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 32107,
resource id: 29364601, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 32108,
resource id: 29364601, major code: 72 (PutImage), minor code: 0

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=461316

jed-bugs.kde@uma.litech.org changed:

   What|Removed |Added

 CC||jed-bugs.kde.org@uma.litech
   ||.org

--- Comment #4 from jed-bugs.kde@uma.litech.org ---
This has been happening to me as well. Today, it got so bad that kwin was
crashing every few minutes. Interestingly, things stablized after I killed and
restarted plasmashell.

Operating System: Arch Linux
KDE Plasma Version: 5.26.2
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.7
Kernel Version: 5.15.76-1-lts (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: LENOVO
Product Name: 20UBCTO1WW
System Version: ThinkPad X1 Yoga Gen 5

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-03 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #3 from Vassilis Virvilis  ---
ok it did it again. Same error but different message. kwin got killed so no
backtrace.

The X11 connection broke: I/O error (code 1)
XIO:  fatal IO error 0 (Success) on X server ":0"

Here is the combined output in the console from kwin and plasmashell.

I don't want to spam this bug so I won't post any more of these outputs unless
somebody finds them useful.

caching records from 6725 to 6925
Export in 0 msecs
kwin_core: XCB error: 152 (BadDamage), sequence: 48054, resource id: 69786721,
major code: 143 (DAMAGE), minor code: 3 (Subtract)
kwin_core: XCB error: 152 (BadDamage), sequence: 50025, resource id: 69786857,
major code: 143 (DAMAGE), minor code: 3 (Subtract)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 60404, resource
id: 69787609, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 60405,
resource id: 69787609, major code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 60408, resource
id: 69787609, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 60409,
resource id: 69787609, major code: 14 (GetGeometry), minor code: 0
kwin_core: XCB error: 152 (BadDamage), sequence: 1323, resource id: 69788124,
major code: 143 (DAMAGE), minor code: 3 (Subtract)
libkcups: Renew-Subscription last error: 0 successful-ok
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 10656, resource
id: 94371894, major code: 18 (ChangeProperty), minor code: 0
kwin_core: XCB error: 3 (BadWindow), sequence: 13117, resource id: 69781020,
major code: 129 (SHAPE), minor code: 6 (Input)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 13118, resource
id: 69781020, major code: 2 (ChangeWindowAttributes), minor code: 0
QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0
kwin_core: XCB error: 3 (BadWindow), sequence: 27544, resource id: 69789767,
major code: 129 (SHAPE), minor code: 6 (Input)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 27545, resource
id: 69789767, major code: 2 (ChangeWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 29605, resource
id: 29362200, major code: 18 (ChangeProperty), minor code: 0
kwin_core: XCB error: 3 (BadWindow), sequence: 31735, resource id: 69791250,
major code: 129 (SHAPE), minor code: 6 (Input)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31736, resource
id: 69791250, major code: 2 (ChangeWindowAttributes), minor code: 0
kwin_core: XCB error: 3 (BadWindow), sequence: 36739, resource id: 69791729,
major code: 129 (SHAPE), minor code: 6 (Input)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36740, resource
id: 69791729, major code: 2 (ChangeWindowAttributes), minor code: 0
kwin_core: XCB error: 3 (BadWindow), sequence: 28091, resource id: 69792410,
major code: 129 (SHAPE), minor code: 6 (Input)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28092, resource
id: 69792410, major code: 2 (ChangeWindowAttributes), minor code: 0
kwin_core: XCB error: 152 (BadDamage), sequence: 46384, resource id: 69816448,
major code: 143 (DAMAGE), minor code: 3 (Subtract)
kwin_core: XCB error: 152 (BadDamage), sequence: 6396, resource id: 69819312,
major code: 143 (DAMAGE), minor code: 3 (Subtract)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7456, resource
id: 71303652, major code: 19 (DeleteProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7467, resource
id: 71303652, major code: 19 (DeleteProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7468, resource
id: 71303652, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7469, resource
id: 71303652, major code: 19 (DeleteProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7470, resource
id: 71303652, major code: 19 (DeleteProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7471, resource
id: 71303652, major code: 19 (DeleteProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7472, resource
id: 71303652, major code: 7 (ReparentWindow), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7473, resource
id: 71303652, major code: 6 (ChangeSaveSet), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7474, resource
id: 71303652, major code: 2 (ChangeWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7475, resource
id: 71303652, major code: 10 (UnmapWindow), minor code: 0
kwin_core: XCB error: 3 (BadWindow), sequence: 8525, resource id: 71303784,
major code: 129 (SHAPE), mino

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-03 Thread Grzegorz
https://bugs.kde.org/show_bug.cgi?id=461316

Grzegorz  changed:

   What|Removed |Added

 CC||grzegorz.alibo...@gmail.com

--- Comment #2 from Grzegorz  ---
I have the same problem

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))

2022-11-02 Thread Vassilis Virvilis
https://bugs.kde.org/show_bug.cgi?id=461316

--- Comment #1 from Vassilis Virvilis  ---
Now I saw the about system:

Operating System: Debian GNU/Linux
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 6.0.0-2-amd64 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz
Memory: 31.3 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000
Manufacturer: Gigabyte Technology Co., Ltd.

-- 
You are receiving this mail because:
You are watching all bug changes.