[kwin] [Bug 372015] kwin_x11 crashes when logging in
https://bugs.kde.org/show_bug.cgi?id=372015 --- Comment #8 from Gregory M. Turner <g...@be-evil.net> --- (In reply to Martin Gräßlin from comment #7) > @Gregory: you are hitting the standard Aurorae/QML crash. Use breeze window > decoration. Ah, good. Sorry for the noise, I'll give it a shot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372015] kwin_x11 crashes when logging in
https://bugs.kde.org/show_bug.cgi?id=372015 --- Comment #5 from Gregory M. Turner <g...@be-evil.net> --- Ok, got it. However I'm not sure if this is the same as OP's crash or not anymore. Anyhow I'll let the experts judge. If you guys want more details I'd be happy to provide them. My box is not terribly interesting, but neither is it totally standard. In addition to the usual Gentoo rice, my system is shockingly ancient -- much older than my hardware -- and somewhat cavalierly maintained. Either way, I seem to have established my issueis not fully reproducible but close enough that I can probably reproduce the problem on demand by just rebooting a few times. -- Application: kwin_x11 (5.8.3) Qt Version: 5.6.2 Frameworks Version: 5.28.0 Operating System: Linux 4.8.9-gentoo-gmt-00 x86_64 Distribution: "Gentoo Base System release 2.3" -- Information about the crash: The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f9c3faf5840 (LWP 3112))] Thread 11 (Thread 0x7f9b9f7fe700 (LWP 3356)): #0 0x7f9c3f58b853 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x0030f1084fff in qt_safe_select (nfds=17, fdread=fdread@entry=0x7f9b9a58, fdwrite=fdwrite@entry=0x7f9b9ce8, fdexcept=fdexcept@entry=0x7f9b9f78, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:65 #2 0x0030f10863e9 in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7f9b9f78, writefds=0x7f9b9ce8, readfds=0x7f9b9a58, nfds=, this=0x7f9b9013d6a0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f9b98c0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x0030f10868ea in QEventDispatcherUNIX::processEvents (this=0x7f9b9013d6a0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x0030f103a71a in QEventLoop::exec (this=this@entry=0x7f9b9f7fdd60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #6 0x0030f0ea01e4 in QThread::exec (this=this@entry=0x7a09a0) at thread/qthread.cpp:500 #7 0x0031024be115 in QQmlThreadPrivate::run (this=0x7a09a0) at qml/ftw/qqmlthread.cpp:141 #8 0x0030f0ea459b in QThreadPrivate::start (arg=0x7a09a0) at thread/qthread_unix.cpp:365 #9 0x7f9c3c004362 in start_thread (arg=0x7f9b9f7fe700) at pthread_create.c:333 #10 0x7f9c3f59296d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f9b967fc700 (LWP 3332)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9b9d800b43 in cnd_wait (mtx=0xb41168, cond=0xb41190) at /usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x8362c0) at /usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/src/gallium/auxiliary/util/u_queue.c:76 #3 0x7f9b9d8009a7 in impl_thrd_routine (p=) at /usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/include/c11/threads_posix.h:87 #4 0x7f9c3c004362 in start_thread (arg=0x7f9b967fc700) at pthread_create.c:333 #5 0x7f9c3f59296d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f9b96ffd700 (LWP 3331)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9b9d800b43 in cnd_wait (mtx=0xb41168, cond=0xb41190) at /usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x8cbcf0) at /usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/src/gallium/auxiliary/util/u_queue.c:76 #3 0x7f9b9d8009a7 in impl_thrd_routine (p=) at /usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/include/c11/threads_posix.h:87 #4 0x7f9c3c004362 in start_thread (arg=0x7f9b96ffd700) at pthread_create.c:333 #5 0x7f9c3f59296d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f9b977fe700 (LWP 3329)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9b9d800b43 in cnd_wait (mtx=0xb41168, cond=0xb41190) at /usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x8d0130) at /usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/src/gallium/auxiliary/util/u_queue.c:76 #3 0x7f9b9d8009a7 in impl_thrd_routine (p=) at /usr/src/debug/media-libs/mesa-13.0.1/mesa-13.0.1/include/c11/threads_posix.h:87 #4 0x7f9c3c004362 in start_thread (arg=0x7f9b977fe700) at pthread_create.c:333 #5 0x7f9c3f59296d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f9b97fff700 (LWP 3328)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00
[kwin] [Bug 372015] kwin_x11 crashes when logging in
https://bugs.kde.org/show_bug.cgi?id=372015 --- Comment #4 from Gregory M. Turner <g...@be-evil.net> --- hm, wierd. now, after logging in, no crash. Pretty sure the only thing I changed was to add this to konsole: >From e434862050abe2ec48a0c506faf8e2a5f0fe99a9 Mon Sep 17 00:00:00 2001 From: "Martin T. H. Sandsmark" <martin.sandsm...@kde.org> Date: Sun, 4 Sep 2016 14:12:02 +0200 Subject: [PATCH] Make the config of file filters and url filters separate REVIEW: 128828 BUG: 368234 Which I haven't carefully looked at. If it recurs I'll do my best to grab a trace. In the meanwhile I'll try to look into whats up with my coredumpctl. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372015] kwin_x11 crashes when logging in
https://bugs.kde.org/show_bug.cgi?id=372015 --- Comment #3 from Gregory M. Turner <g...@be-evil.net> --- P.S.: I have gentoo ~amd64 not Arch. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372015] kwin_x11 crashes when logging in
https://bugs.kde.org/show_bug.cgi?id=372015 Gregory M. Turner <g...@be-evil.net> changed: What|Removed |Added CC||g...@be-evil.net --- Comment #2 from Gregory M. Turner <g...@be-evil.net> --- Looks damn familiar to me. Every time I log in, decorations are zapped and replaced, and I get what sure looks to me like OP's trace. Unfortunately, drkonqui likes to crash and/or lock up soon afterwards. Are they stored somewhere? Even somewhere temporary that would persist after a drkonqui segfault? I seem to have disabled coredumpctl too for some stupid reason :(. I have lots and lots of symbols for you if I can just manage not to fumble ball one time. So long as kwin successfully respawns, which it does about 90% of the time, everything is more-or-less fine after this. If I had to pick a likely culprit I'd tend to suspect it's something to do with some fancy xrandr footwork I allow to race with my sddm login. I guess, it's taken me several recurrences to learn that (a) it's not some sort of transient thing that will magically go away, and (b) drkonqi is never going to work his usual magic and I'll need to do something other than ask him to automate my telemetry. Pretty sure this only started as of 5.8.2 or 5.8.3. I didn't have any 5.8.x for long, so, in truth, I could have missed earlier incidents or presumptively attributed crashes to other stuff. Anyhow, I'm quite sure the drkonqi report was not happening two weeks ago. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 363245] Fails to compile due to FFMPEG API change [kf5 branch]
https://bugs.kde.org/show_bug.cgi?id=363245 Gregory M. Turner <g...@be-evil.net> changed: What|Removed |Added CC||g...@be-evil.net --- Comment #2 from Gregory M. Turner <g...@be-evil.net> --- That may be one problem; another might be that maintainers, early adopters, and eventually amarok's own developers will need to independently track down and test: https://build.opensuse.org/package/view_file/openSUSE:Factory/amarok/amarok-ffmpeg3.0.patch?rev=99, after they came here to try to determine if a reasonable solution had been identified, yet, by the kf5 amarok community. Thankfully, both problems have the same solution. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358343] Konsole's tabbar completely obscures/hides mouse cursor
https://bugs.kde.org/show_bug.cgi?id=358343 --- Comment #3 from Gregory M. Turner <g...@be-evil.net> --- dup: #357937 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 357937] Cursor turns invisible when hovering tab
https://bugs.kde.org/show_bug.cgi?id=357937 Gregory M. Turner <g...@be-evil.net> changed: What|Removed |Added CC||g...@be-evil.net --- Comment #2 from Gregory M. Turner <g...@be-evil.net> --- dup: #358483 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358343] Konsole's tabbar completely obscures/hides mouse cursor
https://bugs.kde.org/show_bug.cgi?id=358343 Gregory M. Turner <g...@be-evil.net> changed: What|Removed |Added CC||g...@be-evil.net --- Comment #2 from Gregory M. Turner <g...@be-evil.net> --- (In reply to nsane457 from comment #1) > I have this problem on Gentoo Linux as well. > For me, it occurs after I pull up the search bar. > > The following is a video clip demonstrating the problem: > > https://www.youtube.com/watch?v=3snx18IjnvA > > Konsole Version 15.08.0 > Using: > KDE Frameworks 5.18.0 > Qt 5.5.1 (built against 5.5.1) > The xcb windowing system > > output of `uname -a`: > > Linux Home-PC 4.3.3-gentoo #2 SMP Fri Jan 22 01:31:59 EST 2016 x86_64 > Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz GenuineIntel GNU/Linux likewise here (also gentoo). I use the hardware-accelerated xorg cursors on the radeon foss driver. In 5.4.x I could "futz" with the mouse and the cursor would eventually appear. Apparently that was a bug as 5.5.x fixed it :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 219121] if holding mouse mid button, perform scroll instead zoom
https://bugs.kde.org/show_bug.cgi?id=219121 --- Comment #17 from Gregory M. Turner <g...@be-evil.net> --- Maybe it's to do with the particulars of my box but the patch from this bug never quite worked correctly on my Gentoo box, Yichao (although I used it for many months and eventually decided to just stop using Okular. It /almost/ worked. But certain actions -- I can't remember /exactly/ what, but maybe it was something to do with scrolling past a page boundary? -- would cause the display to go blank. Under the hood everything was fine; if you used the "normal" scrolling techniques then the document would appear again, but it was as though okular did not realize that certain parts of the page needed to be repainted. Sorry I can't remember more precisely what the exact way to trigger these problems were. But I just wanted to mention it for the record, so that if someone is looking into these patches with an eye toward refactoring or merging them in some way, they should be mindful that there may be some bug in there. -- You are receiving this mail because: You are watching all bug changes.
