https://bugs.kde.org/show_bug.cgi?id=343803
Michael Marley changed:
What|Removed |Added
CC|mich...@michaelmarley.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #103 from sheep...@gmail.com ---
Reported: 2015-02-05 06:56 UTC by DMT
It's now 2020-11-05 and I believe the problem is fixed! yay!
I have not seen the issue occur for some time.
Close it; but let us try REALLY hard not to let a
https://bugs.kde.org/show_bug.cgi?id=343803
Justin Zobel changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #101 from Patrick Shanahan ---
I have not seen this happen for quite some time.
konsole-20.08.2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
Daniel Eckl changed:
What|Removed |Added
CC|daniel.e...@gmx.de |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=343803
Justin Zobel changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #99 from Datenfalke ---
*** Bug 369059 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
Datenfalke changed:
What|Removed |Added
CC||f...@datenfalke.de
---
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #97 from Zbigniew Rebacz ---
I forgot to add that currently I use 5.11.5. And on this version KDE posses
less bugs.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #96 from Zbigniew Rebacz ---
Thank you for your response. Meanwhile I whip out my Kubuntu 16.04 distribution
with stable Plasma and replace it with latest KDE Neon and the bug doesn't
reproduce there. I also install
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #95 from Christoph Feck ---
Developers care, but are not able to debug problems with NVIDIA binary drivers.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
Zbigniew Rebacz changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #93 from Sergio ---
Unfortunately running things under strace just to get rid of some timing race
is a bit expensive in terms of wasted resources.
>From the strace manual:
A traced process runs slowly.
This is
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #92 from stackfaulterror ---
This had been gone for me for a long time with Plasma 5.8 on Linux Mint 18,
with the Nvidia 384.90 driver. However, at some point, the issue has returned.
This issue is therefore
https://bugs.kde.org/show_bug.cgi?id=343803
antonio.guadag...@gmail.com changed:
What|Removed |Added
CC||antonio.guadag...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #90 from Fran ---
A reflection, offtopic.
After a few years kubuntu 14.04 was relatively stable, now it is without
support and we have to use 16.04 very unstable, within 3 years, when it is
stable we will again have
https://bugs.kde.org/show_bug.cgi?id=343803
Kurt Hindenburg changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #89 from Fran ---
I've tried:
OpenGL 2 and 3.
XRender
KWin
TWIN (trinity)
Compiz
Without any composite.
Without any window manager.
And the error is always produced.
As I see that no one is trying to solve this
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #88 from Nick ---
This is very strange. I experienced this problem on Kubuntu 15.10 but then
after upgrading to 16.04 it disappeared, but now after upgrading to 16.10 it
came back! I would have to agree that this is some
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #87 from Sergio ---
Reported to the Qt bug tracker
https://bugreports.qt.io/browse/QTBUG-56766
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #86 from Daniel Eckl ---
I absolutely have this issue, too, using Kubuntu 16.10 Yakkety Yak and
nvidia-340.98.
After I tried to reproduce my (supposedly unrelated) konsole crash issue I
closed every konsole window.
https://bugs.kde.org/show_bug.cgi?id=343803
Nicolas Frattaroli changed:
What|Removed |Added
CC|kdeb...@fratti.ch |
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #85 from Sergio ---
So, we have users who saw this bug with xenial and then the bug go away with
yakkety, but there are also users (at least me) who did not see the bug with
xenial and see it with yakkety. Then
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #84 from Daniel Eckl ---
You are right, my issue does not match the topic, but crashes have been
discussed here, too. I will reconsider and search for other bugs on this
tracker. Thank you for pointing this out.
--
You
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #83 from iraklis ---
(In reply to Daniel Eckl from comment #82)
> I have quite the opposite result, my issues began with the update to
> Yakkety. I'm using nvidia-340.98 with disabled compositor. My konsole
> sessions
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #82 from Daniel Eckl ---
I have quite the opposite result, my issues began with the update to Yakkety.
I'm using nvidia-340.98 with disabled compositor. My konsole sessions were
crashing so fast (and always took all
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #81 from iraklis ---
For the past weeks I messed around with this one and found out that if I open
two different konsole instances, I could close them both without the cpu
drainage. This might explain the complicated
https://bugs.kde.org/show_bug.cgi?id=343803
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--
You
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #80 from Sergio ---
Note that a comment in the bug thread on the nvidia bug tracker states: "From
what I've seen it may not be the nVidia driver which is at fault. There seems
to be a complicated threading issue
https://bugs.kde.org/show_bug.cgi?id=343803
Sergio changed:
What|Removed |Added
CC||sergio.calleg...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #78 from Hans-J. Ullrich ---
Yes, I can confirm, the bug is still existent. As I cannot change my nvidia
drivers (as I need legacy drivers), they are still installed. So on my system
KDE changed, but not the drivers.
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #77 from sheep...@gmail.com ---
Just checked a konsole session this morning...the problem is still present.
Bummer.
Hans - you were correct! Wishful thinking on my part that 'they' fixed it.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #76 from sheep...@gmail.com ---
Herr Ullrich,
I don't know for sure but your input may have finally helped solve this
years-long issue.
Vielen Dank!!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #75 from sheep...@gmail.com ---
Just tried the latest version (16.08.1). The problem seems to have been
resolved...FINALLY! HOORAH FOR THE 'KDE FOLKS'!! Thanks...I think.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=343803
iraklis changed:
What|Removed |Added
CC||irts...@hotmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #73 from Fran ---
Another workaround.
The failure (at least in my case) occurs when the last instance of konsole
closes. Then the solution is that there is always an instance of konsole in the
session.
Add to the
https://bugs.kde.org/show_bug.cgi?id=343803
fanisatt changed:
What|Removed |Added
CC||fanis...@yahoo.gr
--- Comment
https://bugs.kde.org/show_bug.cgi?id=343803
gwar...@gmail.com changed:
What|Removed |Added
CC||gwar...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #71 from Rex Dieter ---
*** Bug 368998 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #70 from Rex Dieter ---
*** Bug 361790 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #69 from Fran ---
For 9600GT. install nvidia-experimental-340 solve this for my
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
Fran changed:
What|Removed |Added
CC||phegoru...@throwam.com
---
https://bugs.kde.org/show_bug.cgi?id=343803
sheep...@gmail.com changed:
What|Removed |Added
CC||sheep...@gmail.com
--- Comment #67 from
https://bugs.kde.org/show_bug.cgi?id=343803
Valdas changed:
What|Removed |Added
CC||zmo...@hotmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=343803
jeremy9...@gmail.com changed:
What|Removed |Added
CC|jeremy9...@gmail.com|
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=343803
Rex Dieter changed:
What|Removed |Added
CC|rdie...@math.unl.edu|
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=343803
Fabrizio Ruggeri changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=343803
stackfaulterror changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=343803
sverre@gmail.com changed:
What|Removed |Added
CC||sverre@gmail.com
--- Comment #64
https://bugs.kde.org/show_bug.cgi?id=343803
Simon Andric changed:
What|Removed |Added
CC||simonandr...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #62 from Fuchs ---
Mike: My guess would be that it depends on whether you use the glvnd library or
not.
Could you try installing the driver with it and see if the problem persists?
I can't reproduce it when using
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #63 from Mike ---
It appears your hypothesis is correct, when I reinstalled the driver with:
NVIDIA-Linux-x86_64-361.28.run -s --dkms --install-libglvnd --glvnd-glx-client
I am not able to reproduce the bug. I
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #61 from lnx...@westlot.net ---
I can't duplicate this Mike. I've tried a dozen or so konsoles, and not one of
them hung. Before, I wasn't able to open and close more than twice before one
hung up.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #60 from Mike ---
This needs to be re-opened due to the fact that 361.28 has a regression that
causes this bug to reappear. Unfortunately this is the new LONG-LIVED driver.
:(
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=343803
maboro...@mail.ru changed:
What|Removed |Added
CC||maboro...@mail.ru
--- Comment #59 from
https://bugs.kde.org/show_bug.cgi?id=343803
Mohammad Reza Hajianpour changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #57 from Rex Dieter ---
I don't know, sorry
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #56 from chepioq ---
Hi Rex.
Just one question.
I am on fedora, Is the 361.18 driver is expected soon in rpmfusion?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
Rex Dieter changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=343803
Rex Dieter changed:
What|Removed |Added
CC||xwaang1...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #51 from lnx...@westlot.net ---
Just installed 361.18 now that it made it into the ppa. All seems well after
several Konsole sessions.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
Marc González Majoral changed:
What|Removed |Added
CC||gons...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #50 from deabru ---
# for I in $(seq -w 1 100); do konsole -e sleep 2s; done
It seems konsole doesn't keep running in background after that. Not one single
process, so looking good so far.
# cat
https://bugs.kde.org/show_bug.cgi?id=343803
Fuchs changed:
What|Removed |Added
CC||deve...@fuchsnet.ch
--- Comment
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #49 from Mike ---
A little off-topic, but I tested the issue I had with it crashing when
restoring/backing-up games and it did not crash now with 361.16 on Fedora 23.
I also have not experienced a konsole cpu lockup
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #48 from lnx...@westlot.net ---
(In reply to Fuchs from comment #47)
> This appears to be fixed in 361.18, can someone still reproduce it with this
> version?
>
> (They fixed a different Qt triggered bug in that release, might have been a
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #41 from Jonathan Ringstad ---
I had a look and found a bit of additional information:
- The hang occurs when the libc exit handler cleans up the shared libraries of
the program, so when the process starts to hang, no
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #42 from Jonathan Ringstad ---
I had a look and found a bit of additional information:
- The hang occurs when the libc exit handler cleans up the shared libraries of
the program, so when the process starts to hang, no
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #44 from Kevin Kofler ---
Though actually, QT_XCB_FORCE_SOFTWARE_OPENGL is probably also ineffective
because the proprietary driver replaces the system libGL with its own version
that probably does not support
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #43 from Kevin Kofler ---
> As a workaround it might be possible to make Qt not interact with GLX (if
> that's possible)
It is:
export QT_XCB_FORCE_SOFTWARE_OPENGL=1
but you folks should really use a working OpenGL
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #45 from Jonathan Ringstad ---
That does indeed not fix the issue, as the issue is not with OpenGL but with
GLX. The GLX calls are made all the same.
You can force software rendering through mesas llvm-pipe by
https://bugs.kde.org/show_bug.cgi?id=343803
Adam Batkin changed:
What|Removed |Added
CC||a...@batkin.net
--
You are
https://bugs.kde.org/show_bug.cgi?id=343803
an999 changed:
What|Removed |Added
CC||arminn...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #38 from jeremy9...@gmail.com ---
OK so that won't be fixed anytime soon I guess.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
Gilboa Davara changed:
What|Removed |Added
CC||gilb...@gmail.com
--
You
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #37 from jeremy9...@gmail.com ---
(In reply to Jonathan Ringstad from comment #31)
> I believe I observed the breakpoint being triggered many times, but I'm not
> sure how thoroughly I actually investigated that. I can collect more data
>
https://bugs.kde.org/show_bug.cgi?id=343803
Rex Dieter changed:
What|Removed |Added
CC||slug...@live.co.uk
---
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #33 from jeremy9...@gmail.com ---
These seems to be duplicates :
bug 350475, bug 354965, bug 351587
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #32 from jeremy9...@gmail.com ---
> I can collect more data later today to (hopefully) answer the question
> definitely.
> I can try to make a debug-build of konsole to isolate the driver<->konsole
> transitioning site
That's sound very
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #26 from Rex Dieter ---
It's (virtually) impossible to debug nvidia's libs, no debuginfo or source
code.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #25 from SinClaus ---
Why Deepin Terminal don't have any problems with Nvidia?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #23 from Rex Dieter ---
re: comment #22
No reason to say "I really don't know", we do know. It's hanging inside one of
nvidia's libraries. that makes it pretty clear where the problem is.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #27 from jeremy9...@gmail.com ---
(In reply to Rex Dieter from comment #26)
> It's (virtually) impossible to debug nvidia's libs, no debuginfo or source
> code.
As you can see, the problem has been reported to Nvidia without success for
https://bugs.kde.org/show_bug.cgi?id=343803
Elvis Angelaccio changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #31 from Jonathan Ringstad ---
I believe I observed the breakpoint being triggered many times, but I'm not
sure how thoroughly I actually investigated that. I can collect more data later
today to (hopefully) answer the
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #28 from Jonathan Ringstad ---
We really don't know anything about where the issue is. All we know is that a
function from the nvidia driver is getting called repeatedly, and that's where
CPU time is going. I can
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #17 from kailed ---
Here it happens only sometimes.
But 2 things:
starting Konsole from a xterm:
QCoreApplication::arguments: Please instantiate the QApplication object first
QDBusConnection: session D-Bus connection
https://bugs.kde.org/show_bug.cgi?id=343803
Bo Jin changed:
What|Removed |Added
CC||b...@suse.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=343803
deabru changed:
What|Removed |Added
CC||deabruf...@gmail.com
--
You
https://bugs.kde.org/show_bug.cgi?id=343803
kailed changed:
What|Removed |Added
CC||kai...@kailed.net
--- Comment #14
https://bugs.kde.org/show_bug.cgi?id=343803
Alexander changed:
What|Removed |Added
CC||ober...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=343803
SinClaus changed:
What|Removed |Added
CC|
92 matches
Mail list logo