[systemsettings] [Bug 489202] Get additional touchpad settings. Installing some package, can't remember. Was it a drivers package?
https://bugs.kde.org/show_bug.cgi?id=489202 --- Comment #4 from Mina <842m...@gmail.com> --- Okay. Thanks for letting me know. Nice meeting you here every now and then :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 489202] Get additional touchpad settings. Installing some package, can't remember. Was it a drivers package?
https://bugs.kde.org/show_bug.cgi?id=489202 --- Comment #2 from Mina <842m...@gmail.com> --- Can I install something from Synaptics to make it work though? I also want to note that I think I've got something from Synaptics already installed on my machine by the way. ``` $ apt-cache policy xserver-xorg-input-synaptics xserver-xorg-input-synaptics: Installed: 1.9.1-1ubuntu3 Candidate: 1.9.1-1ubuntu3 Version table: *** 1.9.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status ``` -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 489202] New: Get additional touchpad settings. Installing some package, can't remember. Was it a drivers package?
https://bugs.kde.org/show_bug.cgi?id=489202 Bug ID: 489202 Summary: Get additional touchpad settings. Installing some package, can't remember. Was it a drivers package? Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: 842m...@gmail.com CC: carlosdema...@gmail.com, j...@jriddell.org, neon-b...@kde.org Target Milestone: --- Created attachment 170979 --> https://bugs.kde.org/attachment.cgi?id=170979&action=edit Comparison of two touchpad settings. Not sure if it's a bug exactly, but here's a bug report anyway. Please see the attached image. I've got the touchpad settings on the left. My older laptop has got the touchpad settings on the right, which are more advanced, and have got something I would like to edit. I want to get the touchpad settings on the right of the attached image. I remember that I got it once before. I think I had to install some software package, and then the available settings changed from the settings on the left to the settings on the right. STEPS TO REPRODUCE 1. Go to settings, Mouse & Touchpad, Touchpad. OBSERVED RESULT One finds only a limited set of settings. EXPECTED RESULT One should find a larger set of settings. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.0.4 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488380] Show desktop grid not working on KDE neon anymore (thinking because of upgrade to Wayland).
https://bugs.kde.org/show_bug.cgi?id=488380 Mina <842m...@gmail.com> changed: What|Removed |Added Summary|Show desktop grid not |Show desktop grid not |working on KDE neon anymore |working on KDE neon anymore |(thinking because of the|(thinking because of |upgrade to Wayland).|upgrade to Wayland). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488380] Show desktop grid not working on KDE neon anymore (thinking because of the upgrade to Wayland).
https://bugs.kde.org/show_bug.cgi?id=488380 Mina <842m...@gmail.com> changed: What|Removed |Added Summary|Show desktop grid not |Show desktop grid not |working on KDE neon anymore |working on KDE neon anymore |(thinking it's because of |(thinking because of the |the upgrade to Wayland).|upgrade to Wayland). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488380] New: Show desktop grid not working on KDE neon anymore (thinking it's because of the upgrade to Wayland).
https://bugs.kde.org/show_bug.cgi?id=488380 Bug ID: 488380 Summary: Show desktop grid not working on KDE neon anymore (thinking it's because of the upgrade to Wayland). Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: 842m...@gmail.com CC: carlosdema...@gmail.com, j...@jriddell.org, neon-b...@kde.org Target Milestone: --- SUMMARY https://imgur.com/a/PbPkGMy (not sure if link works). Show desktop grid not working anymore. Settings > Keyboard > Shortcuts > KWin > Show Desktop Grid. Default shortcut should appear to be Meta+F8 I think. STEPS TO REPRODUCE 1. Press the assigned shortcut to show desktop grid. 2. 3. OBSERVED RESULT Nothing occurs. EXPECTED RESULT There's a zoom out, and all virtual desktops or workspaces appear on screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.5.0-35-generic (64-bit) (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438348] Plasmashell crashes in QOpenGLFunctions::glGetString() after waking up from suspend
https://bugs.kde.org/show_bug.cgi?id=438348 --- Comment #3 from Mina <842m...@gmail.com> --- Nvidia's proprietary drivers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438348] New: Plasmashell crash after waking up from suspend.
https://bugs.kde.org/show_bug.cgi?id=438348 Bug ID: 438348 Summary: Plasmashell crash after waking up from suspend. Product: plasmashell Version: 5.21.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: 842m...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.21.3) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.4.0-70-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.3 Distribution: KDE neon User Edition 5.21 -- Information about the crash: - What I was doing when the application crashed: I found an error message saying that plasmashell crashed. The laptop was suspended, and I found it after I woke the laptop up. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f8926a478c0 (LWP 2000))] [New LWP 2016] [New LWP 2019] [New LWP 5147] [New LWP 5584] [New LWP 6125] [New LWP 6130] [New LWP 6240] [New LWP 6241] [New LWP 6242] [New LWP 6243] [New LWP 6244] [New LWP 6245] [New LWP 6246] [New LWP 6247] [New LWP 112009] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f892a800aff in __GI___poll (fds=fds@entry=0x7ffeb6eeac68, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 Thread 16 (Thread 0x7f88e9831700 (LWP 112009)): #0 __GI___libc_read (nbytes=16, buf=0x7f88e9830ad0, fd=65) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=65, buf=0x7f88e9830ad0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f89290bbb2f in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8929072ebe in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8929073312 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f89290734a3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f892adcdffb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f88c8002e90, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f892ad721eb in QEventLoop::exec(QFlags) (this=this@entry=0x7f88e9830ce0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7f892ab8ca52 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x7f892ab8dbec in QThreadPrivate::start(void*) (arg=0x562112866f80) at thread/qthread_unix.cpp:329 #10 0x7f8929be4609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f892a80d293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f88ea320700 (LWP 6247)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56210f204d94) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56210f204d40, cond=0x56210f204d68) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56210f204d68, mutex=0x56210f204d40) at pthread_cond_wait.c:638 #3 0x7f892ab93d5b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x56210f204d40) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x56210e04f530, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f8910451f40 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f8910455c1e in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f8910451102 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f8910453b93 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f892ab8dbec in QThreadPrivate::start(void*) (arg=0x56210d522d10) at thread/qthread_unix.cpp:329 #10 0x7f8929be4609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f892a80d293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f88eab21700 (LWP 6246)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56210f204d94) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56210f204d40, cond=0x56210f204d68) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56210f204d68, mutex=0x56210f204d40) at pthread_cond_wait.c:638 #3 0x7f892ab93d5b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x56210f204d40) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (th
[Spectacle] [Bug 435324] Screenshot not being saved anymore. And the dialogue doesn't appear.
https://bugs.kde.org/show_bug.cgi?id=435324 --- Comment #4 from Mina <842m...@gmail.com> --- Yea I guess so. I don't think it happened again. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 435324] Screenshot not being saved anymore. And the dialogue doesn't appear.
https://bugs.kde.org/show_bug.cgi?id=435324 --- Comment #1 from Mina <842m...@gmail.com> --- Strange. I did `killall spectacle` and now this doesn't happen anymore. Sorry for the ping. One thing to note is that this issue happened after an update. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 435324] New: Screenshot not being saved anymore. And the dialogue doesn't appear.
https://bugs.kde.org/show_bug.cgi?id=435324 Bug ID: 435324 Summary: Screenshot not being saved anymore. And the dialogue doesn't appear. Product: Spectacle Version: 20.12.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: 842m...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Spectacle not taking screenshots anymore. And also it's not showing the dialogue that it used to show. I use the dialogue to either save the screenshot or copy the screenshot if I want to. How can I (obviously) make it save the screenshots? And how can I make it show the dialogue? Or alternatively, how do I copy the screenshot? STEPS TO REPRODUCE 1. Press the prt sc button 2. Drag a box 3. Hit enter OBSERVED RESULT I don't find the screenshot in the Pictures folder. EXPECTED RESULT I should find the screenshot in the pictures folder. STEPS TO REPRODUCE 1. Press the prt sc button OBSERVED RESULT No dialogue appears. It prompts me to drag a box right away. EXPECTED RESULT A dialogue used to appear. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.21 (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435119] Search doesn't work.
https://bugs.kde.org/show_bug.cgi?id=435119 --- Comment #7 from Mina <842m...@gmail.com> --- > It may also be that things work differently if you've been running Neon for a > while and started with a far older version and upgraded. Yeah my neon is with me since 18.04 and I upgraded it to 20.04. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435119] Search doesn't work.
https://bugs.kde.org/show_bug.cgi?id=435119 --- Comment #6 from Mina <842m...@gmail.com> --- > is Baloo running or not? Yes it should be running. I have this: $ pgrep baloo 1427814 1430114 > when you do a Ctrl-F you'll see... I see something like this https://bugsfiles.kde.org/attachment.cgi?id=137169 which has "any type" & "any date" & "any rating". Therefore baloo should be running. > Try creating a test file in your Documents folder... Okay, but I used "~/Documents/TestBaloo" instead, because my Documents folder is quite messy. $ echo "Hello Penguin" > test-file.txt And now if I go to that folder and Ctrl + F and search "test" or "Penguin" I get no results. $ balooctl status It stays blank and I have to hit Ctrl + C to exit. $ balooshow -x test-file.txt test-file.txt: No index information found ...so there's no index. Okay. mono@gask:~/Documents/TestBaloo$ baloosearch test /home/mono/Sachen/Documents Library/Thesis/template/lstpatch.sty It returns things from another directory. This is not a full list. And test-file.txt is not in the list. $ baloosearch Penguin Elapsed: 15.2315 msecs Returns nothing. Now for balooctl monitor in one window and balooctl purge in another window. The first one: $ balooctl monitor Press ctrl+c to stop monitoring File indexer is running Idle The second one: $ balooctl purge Stopping the File Indexer ... - failed to stop! Not sure if you can see the output correctly, but it's just lots of dots and "failed to stop" in the end. > In System Settings "Search", you should see "Enable File Search" checked and > your home directory "indexed"... Yes it's checked, and home is indexed, and also "Also index file content" is checked. Hope any of this makes sense. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435119] New: Search doesn't work.
https://bugs.kde.org/show_bug.cgi?id=435119 Bug ID: 435119 Summary: Search doesn't work. Product: dolphin Version: 20.12.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: 842m...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Searching in dolphin doesn't return anything. STEPS TO REPRODUCE 1. Open Dolphin. 2. Ctrl + F. 3. Type a search term. OBSERVED RESULT No results after waiting for long. EXPECTED RESULT Get results. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.21 (available in About System) KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434359] Kwin crash after suspend.
https://bugs.kde.org/show_bug.cgi?id=434359 --- Comment #1 from Mina <842m...@gmail.com> --- Might very well be related to this. https://bugs.kde.org/show_bug.cgi?id=428603 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434359] New: Kwin crash after suspend.
https://bugs.kde.org/show_bug.cgi?id=434359 Bug ID: 434359 Summary: Kwin crash after suspend. Product: kwin Version: 5.21.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- Application: kwin_x11 (5.21.1) Qt Version: 5.15.2 Frameworks Version: 5.79.0 Operating System: Linux 5.4.0-66-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.1 Distribution: KDE neon User Edition 5.21 -- Information about the crash: - What I was doing when the application crashed: I leave the laptop to suspend, and when I come back I find the compositor disabled. I get around it by re-enabling opengl detection and changing the rendering backend between the opengl versions. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fcd918f98c0 (LWP 754258))] [New LWP 754261] [New LWP 754263] [New LWP 754346] [New LWP 779678] [New LWP 779701] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __lll_lock_wait (futex=futex@entry=0x7fcd6f3efae0, private=0) at lowlevellock.c:52 Thread 6 (Thread 0x7fcd65769700 (LWP 779701)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7fcd9721afd8 ) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7fcd9721af88 , cond=0x7fcd9721afb0 ) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7fcd9721afb0 , mutex=0x7fcd9721af88 ) at pthread_cond_wait.c:638 #3 0x7fcd9711d63a in QTWTF::TCMalloc_PageHeap::scavengerThread() (this=0x7fcd9720cee0 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #4 0x7fcd9711d65f in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #5 0x7fcd96a34609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fcd974d2293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fcd89437700 (LWP 779678)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7fcd973d5859 in __GI_abort () at abort.c:79 #8 0x7fcd973d5729 in __assert_fail_base (fmt=0x7fcd9756b588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7fcd95b82717 "!xcb_xlib_unknown_seq_number", file=0x7fcd95b826c3 "../../src/xcb_io.c", line=145, function=) at assert.c:92 #9 0x7fcd973e6f36 in __GI___assert_fail (assertion=0x7fcd95b82717 "!xcb_xlib_unknown_seq_number", file=0x7fcd95b826c3 "../../src/xcb_io.c", line=145, function=0x7fcd95b82af0 "append_pending_request") at assert.c:101 #10 0x7fcd95b0e25f in () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #11 0x7fcd95b0ecda in _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #12 0x7fcd95b04b8a in XQueryExtension () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #13 0x7fcd95af81c7 in XInitExtension () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #14 0x7fcd91d8d3f1 in XextAddDisplay (extinfo=0x7fcd8c02bbb0, dpy=0x562b78ac2c40, ext_name=0x7fcd7822b37b "GLX", hooks=0x7fcd78459b40, nevents=17, data=0x0) at ../../src/extutil.c:110 #15 0x7fcd781c32ae in () at /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #16 0x7fcd781c3d7b in () at /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #17 0x7fcd781c9d4e in () at /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #18 0x7fcd96a335a1 in __nptl_deallocate_tsd () at pthread_create.c:301 #19 0x7fcd96a3462a in __nptl_deallocate_tsd () at pthread_create.c:256 #20 start_thread (arg=) at pthread_create.c:488 #21 0x7fcd974d2293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fcd7b7fe700 (LWP 754346)): #0 0x7fcd97a8f713 in QListData::end() const (this=) at ../../include/QtCore/../../src/corelib/tools/qlist.h:118 #1 QList::constEnd() const (this=) at ../../include/QtCore/../../src/corelib/tools/qlist.h:345 #2 QTimerInfoList::timerWait(timespec&) (this=this@entry=0x7fcd68000c08, tm=...) at kernel/qtimerinfo_unix.cpp:393 #3 0x7fcd97a8e774 in QEventDispatcherUNIX::processEvents(QFlags) (this=0x7fcd68000b60, flags=...) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:102 #4 0x7fcd97a351ab in QEventLoop::exec(QFlags) (this=this@entry=0x7fcd7b7fdcc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7fcd9784fa12 in QThread::exec() (this=this@entry=0x562b7827ce70) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7fcd962c4fa9 in QQmlThreadPrivate::run() (this=0x562b7827ce70) at qml/ftw/qqmlthread.cpp:155 #7 0x7fcd97850bac in QThreadPrivate::start(voi
[kdenlive] [Bug 433356] Kdenlive crashes when editing a title clip and clicking both mouse buttons at the same time.
https://bugs.kde.org/show_bug.cgi?id=433356 --- Comment #3 from Mina <842m...@gmail.com> --- Okay. I've tested it kinda quickly. It's not crashing when I click both mouse buttons. ...guess it's fixed :D -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 433456] Crash after clicking the zoom button, then clicking the generated pdf
https://bugs.kde.org/show_bug.cgi?id=433456 --- Comment #1 from Mina <842m...@gmail.com> --- Created attachment 136065 --> https://bugs.kde.org/attachment.cgi?id=136065&action=edit New crash information added by DrKonqi kile (2.9.93) using Qt 5.15.2 - What I was doing when the application crashed: I only clicked the zoom button. Then Kile crashed. One thing that might be related is that the generated pdf is already zoomed in a bit. But I'm not very sure if that's related. -- Backtrace (Reduced): #8 0x7fba664ff6be in QtPrivate::QSlotObjectBase::call (a=0x7ffc954eaf50, r=0x564c2f228580, this=0x564c2f1233f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate (sender=0x564c2f1b0320, signal_index=7, argv=0x7ffc954eaf50) at kernel/qobject.cpp:3886 [...] #11 0x7fba66f9b946 in QAction::toggled (this=this@entry=0x564c2f1b0320, _t1=, _t1@entry=false) at .moc/moc_qaction.cpp:389 #12 0x7fba66f9deb7 in QAction::setChecked (this=0x564c2f1b0320, b=) at kernel/qaction.cpp:976 #13 0x7fba66f9f25d in QActionGroupPrivate::_q_actionChanged (this=0x564c2f1b0180) at /usr/include/c++/9/bits/atomic_base.h:413 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 433456] Crash after clicking the zoom button, then clicking the generated pdf
https://bugs.kde.org/show_bug.cgi?id=433456 Mina <842m...@gmail.com> changed: What|Removed |Added CC||842m...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 433456] New: Crash after clicking the zoom button, then clicking the generated pdf
https://bugs.kde.org/show_bug.cgi?id=433456 Bug ID: 433456 Summary: Crash after clicking the zoom button, then clicking the generated pdf Product: kile Version: 2.9.93 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: 842m...@gmail.com Target Milestone: --- Application: kile (2.9.93) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.4.0-58-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: The title is all I know. Kile crashed after I clicked the zoom button, then I clicked the generated pdf. -- Backtrace: Application: Kile (kile), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [New LWP 665149] [New LWP 665150] [New LWP 665152] [New LWP 665153] [New LWP 673300] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f4691640aff in __GI___poll (fds=fds@entry=0x7ffd959a8e68, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f4689081080 (LWP 665146))] Thread 6 (Thread 0x7f466f0dc700 (LWP 673300)): #0 __GI___libc_read (nbytes=10, buf=0x7f466f0dbb1e, fd=29) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=29, buf=0x7f466f0dbb1e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f4689c5e975 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f468bef0416 in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f468bef0eb4 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f468bef0f70 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f468beff11d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f4689c8d72c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #8 0x7f468e470609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f469164d293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f468563b700 (LWP 665153)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55ae51b37e24) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ae51b37dd0, cond=0x55ae51b37df8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55ae51b37df8, mutex=0x55ae51b37dd0) at pthread_cond_wait.c:638 #3 0x7f468e759d1b in QWaitConditionPrivate::wait (deadline=..., this=0x55ae51b37dd0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55ae51bc75d0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f468e759de1 in QWaitCondition::wait (this=0x55ae51bc75d8, mutex=0x55ae51bc75d0, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #6 0x7f46919df6c6 in ?? () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kile.so #7 0x7f468e753bac in QThreadPrivate::start (arg=0x55ae51bc75a0) at thread/qthread_unix.cpp:329 #8 0x7f468e470609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f469164d293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f4685e3c700 (LWP 665152)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55ae519b83d4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ae519b8380, cond=0x55ae519b83a8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55ae519b83a8, mutex=0x55ae519b8380) at pthread_cond_wait.c:638 #3 0x7f468e759d1b in QWaitConditionPrivate::wait (deadline=..., this=0x55ae519b8380) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55ae51b503a0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f468e759de1 in QWaitCondition::wait (this=0x55ae51b503a8, mutex=0x55ae51b503a0, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #6 0x7f46919df6c6 in ?? () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kile.so #7 0x7f468e753bac in QThreadPrivate::start (arg=0x55ae51b50370) at thread/qthread_unix.cpp:329 #8 0x7f468e470609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f469164d293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f468705d700 (LWP 665150)): #0 0x7f468c03909d in g_source_ref () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f468c039168 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f468c03a66b in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f468c03b0db in ?? () from /usr/
[dolphin] [Bug 433357] Dolphin Crashed. Only backtrace is available.
https://bugs.kde.org/show_bug.cgi?id=433357 Mina <842m...@gmail.com> changed: What|Removed |Added Platform|Other |Neon Packages --- Comment #1 from Mina <842m...@gmail.com> --- SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.20 (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433357] New: Dolphin Crashed. Only backtrace is available.
https://bugs.kde.org/show_bug.cgi?id=433357 Bug ID: 433357 Summary: Dolphin Crashed. Only backtrace is available. Product: dolphin Version: 20.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: 842m...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- I don't have information about how to reproduce the bug. But I just have the backtrace. Application: dolphin (20.12.0) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.4.0-58-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Backtrace: Application: Dolphin (dolphin), signal: Aborted Content of s_kcrashErrorMessage: (null) [New LWP 9973] [New LWP 9974] [New LWP 9979] [New LWP 16700] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f160f039aff in __GI___poll (fds=fds@entry=0x7ffcc66ddae8, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f16080ec8c0 (LWP 9972))] Thread 5 (Thread 0x7f15eec47700 (LWP 16700)): #0 __GI___libc_read (nbytes=10, buf=0x7f15eec46b1e, fd=26) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=26, buf=0x7f15eec46b1e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f160a672975 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f160b46c416 in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f160b46ceb4 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f160b46cf70 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f160b47b11d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f160a6a172c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #8 0x7f160b4bf609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f160f046293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f15ef7fe700 (LWP 9979)): #0 0x7f160f039aff in __GI___poll (fds=0x7f15e4005240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f160aaf01ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f160aaf02e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f160cd80fbb in QEventDispatcherGlib::processEvents (this=0x7f15e4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f160cd251ab in QEventLoop::exec (this=this@entry=0x7f15ef7fdce0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f160cb3fa12 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f160cb40bac in QThreadPrivate::start (arg=0x55750078df20) at thread/qthread_unix.cpp:329 #7 0x7f160b4bf609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f160f046293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f16066c9700 (LWP 9974)): #0 0x7f160f039aff in __GI___poll (fds=0x7f15f8015390, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f160aaf01ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f160aaf02e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f160cd80fbb in QEventDispatcherGlib::processEvents (this=0x7f15f8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f160cd251ab in QEventLoop::exec (this=this@entry=0x7f16066c8cb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f160cb3fa12 in QThread::exec (this=this@entry=0x7f160de5ad80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f160ddd6f4b in QDBusConnectionManager::run (this=0x7f160de5ad80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179 #7 0x7f160cb40bac in QThreadPrivate::start (arg=0x7f160de5ad80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:329 #8 0x7f160b4bf609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f160f046293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f160748f700 (LWP 9973)): #0 0x7f160f039aff in __GI___poll (fds=0x7f160748ebe8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f160b4f5c1a in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f160b4f790a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f16079add58 in QXcbEventQueue::run (this=0x5575004d3ad0) at qxcbeventqueue.cp
[kdenlive] [Bug 433356] Kdenlive crashes when editing a title clip and clicking both mouse buttons at the same time.
https://bugs.kde.org/show_bug.cgi?id=433356 --- Comment #1 from Mina <842m...@gmail.com> --- Application: Kdenlive (kdenlive), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [New LWP 22467] [New LWP 22470] [New LWP 22472] [New LWP 22473] [New LWP 22474] [New LWP 22475] [New LWP 22476] [New LWP 22477] [New LWP 22485] [New LWP 22486] [New LWP 22487] [New LWP 22488] [New LWP 22515] [New LWP 22520] [New LWP 47341] [New LWP 53391] [New LWP 53392] [New LWP 53393] [New LWP 53394] [New LWP 53395] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f09b2405aff in __GI___poll (fds=fds@entry=0x7ffdcbbfeb68, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f09ae8008c0 (LWP 22463))] Thread 21 (Thread 0x7f08e3fff700 (LWP 53395)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564f8acff734) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564f8acff6e0, cond=0x564f8acff708) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564f8acff708, mutex=0x564f8acff6e0) at pthread_cond_wait.c:638 #3 0x7f09961cde7d in () at /usr/lib/x86_64-linux-gnu/mlt/libmltsdl2.so #4 0x7f09b18e8609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f09b2412293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f095f7bc700 (LWP 53394)): #0 getpid () at ../sysdeps/unix/syscall-template.S:60 #1 0x7f09b0c24f50 in pa_detect_fork () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #2 0x7f09b193946c in pa_stream_writable_size () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f0998e2bacd in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #4 0x7f0998d7d6be in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #5 0x7f0998dcd720 in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #6 0x7f0998e4613d in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #7 0x7f09b18e8609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f09b2412293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f095e761700 (LWP 53393)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564f89972768) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564f89972718, cond=0x564f89972740) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564f89972740, mutex=0x564f89972718) at pthread_cond_wait.c:638 #3 0x7f09b444fe79 in () at /usr/lib/x86_64-linux-gnu/libmlt.so.6 #4 0x564f855c91f1 in RenderThread::run() (this=0x7f0934101900) at ./src/monitor/glwidget.cpp:1443 #5 0x7f09b28fabac in QThreadPrivate::start(void*) (arg=0x7f0934101900) at thread/qthread_unix.cpp:329 #6 0x7f09b18e8609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f09b2412293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f095efbb700 (LWP 53392)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564f8acff768) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564f8acff770, cond=0x564f8acff740) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564f8acff740, mutex=0x564f8acff770) at pthread_cond_wait.c:638 #3 0x7f09961cea73 in () at /usr/lib/x86_64-linux-gnu/mlt/libmltsdl2.so #4 0x7f09b18e8609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f09b2412293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f0978b82700 (LWP 53391)): #0 __GI___libc_read (fd=18, buf=0x7f0978b81cae, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:25 #1 0x7f09b0c35975 in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #2 0x7f09b1930416 in pa_mainloop_prepare () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f09b1930eb4 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f09b1930f70 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f0998e2bcb3 in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #6 0x7f0998dcd720 in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #7 0x7f0998e4613d in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #8 0x7f09b18e8609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f09b2412293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f09295ff700 (LWP 47341)): #0 __GI___libc_read (nbytes=10, buf=0x7f09295feb1e, fd=65) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=65, buf=0x7f09295feb1e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f09b0c35975 in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f09b1930416 in pa_mainloop_prepare () at /usr/lib/
[kdenlive] [Bug 433356] New: Kdenlive crashes when editing a title clip and clicking both mouse buttons at the same time.
https://bugs.kde.org/show_bug.cgi?id=433356 Bug ID: 433356 Summary: Kdenlive crashes when editing a title clip and clicking both mouse buttons at the same time. Product: kdenlive Version: 20.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: 842m...@gmail.com Target Milestone: --- The bug reporter is not able to report the bug on its own. Here's what it produced. Let me know if you need more information. The bug is very easily reproducible. I attach multiple reports. Application: kdenlive (20.12.0) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.4.0-58-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: I am editing a title clip. I clicked both mouse buttons at the same time. I think right before left. -- Backtrace: Application: Kdenlive (kdenlive), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [New LWP 7917] [New LWP 7919] [New LWP 7920] [New LWP 7921] [New LWP 7922] [New LWP 7923] [New LWP 7924] [New LWP 7925] [New LWP 7929] [New LWP 7930] [New LWP 7931] [New LWP 7932] [New LWP 9941] [New LWP 14279] [New LWP 14280] [New LWP 14281] [New LWP 14282] [New LWP 14286] [New LWP 14287] [New LWP 17168] [New LWP 17169] [New LWP 17170] [New LWP 17171] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f51caa67aff in __GI___poll (fds=fds@entry=0x7ffd0e48be68, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f51c6e628c0 (LWP 7915))] Thread 24 (Thread 0x7f5156ffd700 (LWP 17171)): #0 getpid () at ../sysdeps/unix/syscall-template.S:60 #1 0x7f51c9286f50 in pa_detect_fork () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #2 0x7f51c9f9b46c in pa_stream_writable_size () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f51b14a8acd in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #4 0x7f51b13fa6be in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #5 0x7f51b144a720 in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #6 0x7f51b14c313d in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #7 0x7f51c9f4a609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f51caa74293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f516a489700 (LWP 17170)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55aeffed891c) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55aeffed88c8, cond=0x55aeffed88f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55aeffed88f0, mutex=0x55aeffed88c8) at pthread_cond_wait.c:638 #3 0x7f51ccab1e79 in () at /usr/lib/x86_64-linux-gnu/libmlt.so.6 #4 0x55aef6a5a1f1 in RenderThread::run() (this=0x7f5128000a20) at ./src/monitor/glwidget.cpp:1443 #5 0x7f51caf5cbac in QThreadPrivate::start(void*) (arg=0x7f5128000a20) at thread/qthread_unix.cpp:329 #6 0x7f51c9f4a609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f51caa74293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f51911b6700 (LWP 17169)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55af00e10258) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55af00e10260, cond=0x55af00e10230) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55af00e10230, mutex=0x55af00e10260) at pthread_cond_wait.c:638 #3 0x7f51ae84ba73 in () at /usr/lib/x86_64-linux-gnu/mlt/libmltsdl2.so #4 0x7f51c9f4a609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f51caa74293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f51911f7700 (LWP 17168)): #0 __GI___libc_read (nbytes=10, buf=0x7f51911f6cae, fd=31) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=31, buf=0x7f51911f6cae, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f51c9297975 in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f51c9f92416 in pa_mainloop_prepare () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f51c9f92eb4 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f51c9f92f70 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f51b14a8cb3 in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #7 0x7f51b144a720 in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #8 0x7f51b14c313d in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #9 0x7f51c9f4a609 in start_thread (arg=) at pthrea
[Bluedevil] [Bug 429830] Crackling or choppy sound when scanning for a device.
https://bugs.kde.org/show_bug.cgi?id=429830 --- Comment #3 from Mina <842m...@gmail.com> --- I did `bluetoothctl` then `scan on` and the crackling or choppiness happened. This is just to confirm that the issue happens when scanning specifically. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 429830] Crackling or choppy sound when scanning for a device.
https://bugs.kde.org/show_bug.cgi?id=429830 --- Comment #2 from Mina <842m...@gmail.com> --- Thanks for responding. I think it's not reproducible on your machine in this case. It should be clear enough. Sometimes, the first moment you click the button, the sound just stops for some milliseconds, then it resumes with choppiness or crackling. This should be clear. I thought I'd make a screen recording and try to capture this issue. When I'm recording the screen I can experience the issue, but when I check the video I've recorded, it doesn't have the issue. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 429830] New: Crackling or choppy sound when scanning for a device.
https://bugs.kde.org/show_bug.cgi?id=429830 Bug ID: 429830 Summary: Crackling or choppy sound when scanning for a device. Product: Bluedevil Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: 842m...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The sound coming through the bluetooth headphones had some crackling or was kind of choppy. I figured out that the reason was the "scanning" dialogue. When I closed the dialogue, the sound returned back to normal. This isn't expected behavior, right? I think this is some sort of signal interference. I'm thinking this might not be a Bluedevil issue. It might be the underlying software. STEPS TO REPRODUCE 1. Connect bluetooth headphones. Play some music. It should be playing fine in the headphones through bluetooth. 2. Click the bluetooth icon in the taskbar. The bluetooth dialogue should appear (containing connected devices and available devices and so on...) 3. Click the plus button. The "bluetooth device wizard" should appear. It says "Select a device" and it scans for devices. 4. You should hear crackling sounds in the music. It should sound choppy. Listen carefully. It might not be very obvious. OBSERVED RESULT Music is choppy or has crackling sounds. I think this is interference EXPECTED RESULT Music should be clear. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.20 (available in About System) KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428603] Desktop effects are disabled after suspend. Can't set rendering backend to opengl.
https://bugs.kde.org/show_bug.cgi?id=428603 Mina <842m...@gmail.com> changed: What|Removed |Added Attachment #133345|0 |1 is obsolete|| --- Comment #5 from Mina <842m...@gmail.com> --- Created attachment 133696 --> https://bugs.kde.org/attachment.cgi?id=133696&action=edit Better trace (after installing libepoxy0-dbgsym) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 429197] New: Pinch to zoom is broken. It moves the pdf away from the point where I'm zooming.
https://bugs.kde.org/show_bug.cgi?id=429197 Bug ID: 429197 Summary: Pinch to zoom is broken. It moves the pdf away from the point where I'm zooming. Product: okular Version: 1.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- SUMMARY After an upgrade to Okular, pinch to zoom (using the touch screen) doesn't work correctly. It moves the pdf away from the point where I'm zooming. It moves it relative to the top left I believe. This wasn't broken in previous versions of Okular. I don't have the exact version numbers, but this started happening after I did the rebase upgrade of my KDE neon from 18.04 to 20.04. So in 18.04 neon, this didn't happen. In 20.04 neon this happens. STEPS TO REPRODUCE 1. Pinch to zoom in any pdf. 2. 3. OBSERVED RESULT Zooming pans the pdf away from the point where I'm zooming. EXPECTED RESULT Zooming should work and doesn't pan the pdf while zooming SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.20 (available in About System) KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428603] Desktop effects are disabled after suspend. Can't set rendering backend to opengl.
https://bugs.kde.org/show_bug.cgi?id=428603 --- Comment #3 from Mina <842m...@gmail.com> --- Created attachment 133345 --> https://bugs.kde.org/attachment.cgi?id=133345&action=edit Trace (generated with the help of #kde-bugs on irc) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391226] Dolphin crash. Was closing a tab.
https://bugs.kde.org/show_bug.cgi?id=391226 --- Comment #5 from Mina <842m...@gmail.com> --- Okay. Sure thing. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391226] Dolphin crash. Was closing a tab.
https://bugs.kde.org/show_bug.cgi?id=391226 --- Comment #3 from Mina <842m...@gmail.com> --- Hi. Sorry for the delayed reply. This issue happened just once. I reported it when it happened, but I can't reproduce it anymore. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 428943] New: baloo file extractor crash on startup.
https://bugs.kde.org/show_bug.cgi?id=428943 Bug ID: 428943 Summary: baloo file extractor crash on startup. Product: frameworks-baloo Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: 842m...@gmail.com Target Milestone: --- SUMMARY On startup, I get a message saying "baloo file extractor has crashed". In the dialog, the "report bug" button is grayed out. I'm using kde neon. up to date. STEPS TO REPRODUCE 1. Startup the laptop 2. 3. OBSERVED RESULT An error message appears. EXPECTED RESULT No error message should appear. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.20.1 (available in About System) KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION The bug reporting message, in the "Developer information" tab, shows the following: Application: baloo_file_extractor (baloo_file_extractor), signal: Aborted Content of s_kcrashErrorMessage: (null) [New LWP 14647] [New LWP 14648] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f136a955aff in __GI___poll (fds=fds@entry=0x7fff51da77a8, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f1367349400 (LWP 14646))] Thread 3 (Thread 0x7f1365bc4700 (LWP 14648)): #0 0x7f136a955aff in __GI___poll (fds=0x7f135801b270, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f13699591ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f13699592e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f136af1deab in QEventDispatcherGlib::processEvents (this=0x7f1358000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f136aec21bb in QEventLoop::exec (this=this@entry=0x7f1365bc3d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f136ace0082 in QThread::exec (this=this@entry=0x7f136b92ad80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f136b8a7f2b in QDBusConnectionManager::run (this=0x7f136b92ad80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179 #7 0x7f136ace120c in QThreadPrivate::start (arg=0x7f136b92ad80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:342 #8 0x7f136a2bd609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f136a962293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f136662b700 (LWP 14647)): #0 0x7f136a955aff in __GI___poll (fds=0x7f136662aca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f13698dcc1a in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f13698de90a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f1366c09978 in QXcbEventQueue::run (this=0x55f137039460) at qxcbeventqueue.cpp:228 #4 0x7f136ace120c in QThreadPrivate::start (arg=0x55f137039460) at thread/qthread_unix.cpp:342 #5 0x7f136a2bd609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f136a962293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f1367349400 (LWP 14646)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7f136a865859 in __GI_abort () at abort.c:79 #8 0x7f136a482a83 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #9 0x7f136a4776d5 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #10 0x7f136a478966 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #11 0x7f136a478ba3 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #12 0x7f136a47a7ec in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #13 0x7f136a47ea0f in mdb_cursor_del () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #14 0x7f136a4802e3 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #15 0x7f136b9548c9 in Baloo::DocumentDB::del (this=this@entry=0x7fff51da90b0, docId=, docId@entry=47865237260470279) at ./src/engine/documentdb.cpp:105 #16 0x7f136b9851d9 in Baloo::WriteTransaction::removeDocument (this=0x55f13710fb20, id=id@entry=47865237260470279) at ./src/engine/writetransaction.cpp:115 #17 0x7f136b977f37 in Baloo::Transaction::removeDocument (this=this@entry=0x55f137102180, id=id@entry=47865237260470279) at ./src/engine/transaction.cpp:235 #18 0x55f135a9aa75 in Baloo::App::index (this=this@entry=0x7fff51da9940, tr=0x55f137102180, url=..., id=id@entry=47865237260470279) at ./src/file/extractor/app.cpp:209 #19 0x55f135a9b97d in Balo
[kwin] [Bug 428603] Desktop effects are disabled after suspend. Can't set rendering backend to opengl.
https://bugs.kde.org/show_bug.cgi?id=428603 --- Comment #2 from Mina <842m...@gmail.com> --- Thank you for the reply. There's a popup that I sometimes get that tries to collect the backtrace I think, but it fails. One thing that it fails to do is to install "debug symbols". How else can I collect the backtrace? Please tell me what I need to do and I'll follow the steps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428603] New: Desktop effects are disabled after suspend. Can't set rendering backend to opengl.
https://bugs.kde.org/show_bug.cgi?id=428603 Bug ID: 428603 Summary: Desktop effects are disabled after suspend. Can't set rendering backend to opengl. Product: kwin Version: 5.20.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- SUMMARY Desktop effects are disabled with opengl after suspend, and cannot be re-enabled. Sometimes this workaround fixes it. Go to compositor. Click the "re-enable opengl detection" button. Switch rendering backend to opengl. This is what happens when the workaround doesn't work. After I switch rendering backend to opengl, kwin crashes again, and is reopened but desktop effects are still disabled. It seems to be an Nvida driver issue. I have the latest Nvidia driver installed. My laptop is an HP envy x360. STEPS TO REPRODUCE 1. Suspend laptop 2. Wake it up from suspend OBSERVED RESULT Desktop effects are disabled and cannot be re-enabled with opengl as the rendering backend. EXPECTED RESULT Desktop effects are enabled. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.20 (available in About System) KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 415764] New: Cannot use microphone with bluetooth headphones and mic
https://bugs.kde.org/show_bug.cgi?id=415764 Bug ID: 415764 Summary: Cannot use microphone with bluetooth headphones and mic Product: Bluedevil Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: 842m...@gmail.com Target Milestone: --- I have a Bose QC35 II. It's a headphone and it includes a microphone. It works over bluetooth (or wired). When I connect it I only get headphones. I can't use the mic. I'm using an HP envy x360 laptop. I'm using kde neon. STEPS TO REPRODUCE 1. Pair the device normally. Headphone speakers work fine. 2. Do a facebook voice call. OBSERVED RESULT Mic used is internal mic of the laptop. EXPECTED RESULT Using the mic in the headphones to perform the call. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406639] New: Disabling Full Screen -> crash
https://bugs.kde.org/show_bug.cgi?id=406639 Bug ID: 406639 Summary: Disabling Full Screen -> crash Product: kwin Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: saleebm...@aol.com Target Milestone: --- Application: kwin_x11 (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-17-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: I have VMware openning in full screen automatically. It was open, then I ran my VM in full screen, closes the VM successfully, then on the VMware workstation itself, I used their option to disable full screen. Then it crashed. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3a15734840 (LWP 5242))] Thread 7 (Thread 0x7f3a0e653700 (LWP 20179)): #0 0x7f3a1fd1f7d6 in __GI_ppoll (fds=0x7f3a3568, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3a1e8c0141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3a1e8c15b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f3a1e87116b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3a1e6c00b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3a1cd2b1f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f3a1e6c9c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3a1d4fa164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f3a1fd2bdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f39efb3f700 (LWP 16881)): #0 0x7f3a1fd1f7d6 in __GI_ppoll (fds=0x7f39640383f8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3a1e8c0141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3a1e8c15b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f3a1e87116b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3a1e6c00b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3a1cd2b1f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f3a1e6c9c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3a1d4fa164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f3a1fd2bdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f3a0d8b9700 (LWP 11984)): #0 0x7f3a1fd1f7d6 in __GI_ppoll (fds=0x7f3a04003298, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3a1e8c0141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3a1e8c15b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f3a1e87116b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3a1e6c00b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3a1e6c9c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3a1d4fa164 in start_thread (arg=) at pthread_create.c:486 #7 0x7f3a1fd2bdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f39f5207700 (LWP 5293)): #0 0x7f3a1d5002eb in futex_wait_cancelable (private=, expected=0, futex_word=0x7f3a1e2ddfb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f3a1d5002eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f3a1e2ddf68, cond=0x7f3a1e2ddf90) at pthread_cond_wait.c:502 #2 0x7f3a1d5002eb in __pthread_cond_wait (cond=0x7f3a1e2ddf90, mutex=0x7f3a1e2ddf68) at pthread_cond_wait.c:655 #3 0x7f3a1e1e6e2a in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f3a1e1e6e49 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f3a1d4fa164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f3a1fd2bdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f39fc973700 (LWP 5287)): #0 0x7f3a1fd1f7d6 in __GI_ppoll (fds=0x7f39f8000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3a1e8c0141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3a1e8c15b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x00
[frameworks-baloo] [Bug 405871] New: Baloo crashes after restart
https://bugs.kde.org/show_bug.cgi?id=405871 Bug ID: 405871 Summary: Baloo crashes after restart Product: frameworks-baloo Version: 5.56.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- Application: baloo_file_extractor (5.56.0) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: I'm on neon. This error message appears right after restart. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffa25653c80 (LWP 3533))] Thread 3 (Thread 0x7ff9ff0c8700 (LWP 3541)): #0 0x7ffa221660b4 in __GI___libc_read (fd=8, buf=0x7ff9ff0c7b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7ffa1e87bcd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffa1e837027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa1e8374e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffa1e83764c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ffa22aad15b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7ff9f8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7ffa22a4e64a in QEventLoop::exec(QFlags) (this=this@entry=0x7ff9ff0c7d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7ffa2287641a in QThread::exec() (this=this@entry=0x7ffa246b9d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:531 #8 0x7ffa24442015 in QDBusConnectionManager::run() (this=0x7ffa246b9d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #9 0x7ffa22877bc2 in QThreadPrivate::start(void*) (arg=0x7ffa246b9d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #10 0x7ffa209d36db in start_thread (arg=0x7ff9ff0c8700) at pthread_create.c:463 #11 0x7ffa2217788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7ffa18987700 (LWP 3534)): #0 0x7ffa2216abf9 in __GI___poll (fds=0x7ffa18986cb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ffa1e3c6747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ffa1e3c836a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7ffa19f0232a in QXcbEventQueue::run() (this=0x55a659c5ccd0) at qxcbeventqueue.cpp:225 #4 0x7ffa22877bc2 in QThreadPrivate::start(void*) (arg=0x55a659c5ccd0) at thread/qthread_unix.cpp:361 #5 0x7ffa209d36db in start_thread (arg=0x7ffa18987700) at pthread_create.c:463 #6 0x7ffa2217788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ffa25653c80 (LWP 3533)): [KCrash Handler] #6 0x7ffa22094e97 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7ffa22096801 in __GI_abort () at abort.c:79 #8 0x7ffa21382932 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #9 0x7ffa213777b5 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #10 0x7ffa213789bb in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #11 0x7ffa21378c29 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #12 0x7ffa2137a854 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #13 0x7ffa2137ea7a in mdb_cursor_del () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #14 0x7ffa2138029c in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #15 0x7ffa24adaf2e in Baloo::DocumentDB::del(unsigned long long) () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #16 0x7ffa24af431a in Baloo::WriteTransaction::removeDocument(unsigned long long) () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #17 0x55a657a4c37c in () #18 0x55a657a4cb9e in () #19 0x7ffa22a8cd04 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffce85365a0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #20 0x7ffa22a8cd04 in QSingleShotTimer::timerEvent(QTimerEvent*) (this=0x55a659ca80a0) at kernel/qtimer.cpp:318 #21 0x7ffa22a8094b in QObject::event(QEvent*) (this=0x55a659ca80a0, e=) at kernel/qobject.cpp:1271 #22 0x7ffa2384683c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55a659c570f0, receiver=receiver@entry=0x55a659ca80a0, e=e@entry=0x7ffce85368e0) at kernel/qapplication.cpp:3752 #23 0x7ffa2384ddd0 in QApplication::notify(QObject*, QEvent*) (this=0x7ff
[frameworks-baloo] [Bug 405284] New: Balloo crash
https://bugs.kde.org/show_bug.cgi?id=405284 Bug ID: 405284 Summary: Balloo crash Product: frameworks-baloo Version: 5.55.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- Application: baloo_file_extractor (5.55.0) Qt Version: 5.12.0 Frameworks Version: 5.55.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: The crash message appeared right after restarting neon after an update. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcab5d8cc80 (LWP 2777))] Thread 3 (Thread 0x7fca8f8ea700 (LWP 2779)): #0 0x7fcab28a70b4 in __GI___libc_read (fd=8, buf=0x7fca8f8e9b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fcaaefbccd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcaaef78027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcaaef784e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fcaaef7864c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fcab31ee15b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fca88000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fcab318f64a in QEventLoop::exec(QFlags) (this=this@entry=0x7fca8f8e9d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fcab2fb741a in QThread::exec() (this=this@entry=0x7fcab4dfad80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:531 #8 0x7fcab4b83015 in QDBusConnectionManager::run() (this=0x7fcab4dfad80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #9 0x7fcab2fb8bc2 in QThreadPrivate::start(void*) (arg=0x7fcab4dfad80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #10 0x7fcab14b26db in start_thread (arg=0x7fca8f8ea700) at pthread_create.c:463 #11 0x7fcab28b888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fcaa90c8700 (LWP 2778)): #0 0x7fcab28abbf9 in __GI___poll (fds=0x7fcaa90c7cb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fcaaeb07747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fcaaeb0936a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fcaaa64332a in QXcbEventQueue::run() (this=0x55f7ed835cd0) at qxcbeventqueue.cpp:225 #4 0x7fcab2fb8bc2 in QThreadPrivate::start(void*) (arg=0x55f7ed835cd0) at thread/qthread_unix.cpp:361 #5 0x7fcab14b26db in start_thread (arg=0x7fcaa90c8700) at pthread_create.c:463 #6 0x7fcab28b888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fcab5d8cc80 (LWP 2777)): [KCrash Handler] #6 0x7fcab27d5e97 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7fcab27d7801 in __GI_abort () at abort.c:79 #8 0x7fcab1e614d2 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #9 0x7fcab1e565d5 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #10 0x7fcab1e57803 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #11 0x7fcab1e57a79 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #12 0x7fcab1e59764 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #13 0x7fcab1e5daba in mdb_cursor_del () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #14 0x7fcab1e5f0d4 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #15 0x7fcab521be1e in Baloo::DocumentDB::del(unsigned long long) () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #16 0x7fcab523518a in Baloo::WriteTransaction::removeDocument(unsigned long long) () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #17 0x55f7ed4e535c in () #18 0x55f7ed4e5b7e in () #19 0x7fcab31cdd04 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffe09e03f20, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #20 0x7fcab31cdd04 in QSingleShotTimer::timerEvent(QTimerEvent*) (this=0x55f7ed87f860) at kernel/qtimer.cpp:318 #21 0x7fcab31c194b in QObject::event(QEvent*) (this=0x55f7ed87f860, e=) at kernel/qobject.cpp:1271 #22 0x7fcab3f8783c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55f7ed8300f0, receiver=receiver@entry=0x55f7ed87f860, e=e@entry=0x7ffe09e04260) at kernel/qapplication.cpp:3752 #23 0x7fcab3f8edd0 in QApplication::notify(QObject*, QEvent*) (this=0x7ffe09e04540, receiver=0x55f7ed87f860, e=0x7ff
[gwenview] [Bug 403801] New: Feature request, pinch to zoom in and out
https://bugs.kde.org/show_bug.cgi?id=403801 Bug ID: 403801 Summary: Feature request, pinch to zoom in and out Product: gwenview Version: 18.08.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- I'm using KDE neon. I can't pinch to zoom the image. I can only pan. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400078] New: Freezing annotations when double pressing the keyboard shortcut or double tapping the touch screen.
https://bugs.kde.org/show_bug.cgi?id=400078 Bug ID: 400078 Summary: Freezing annotations when double pressing the keyboard shortcut or double tapping the touch screen. Product: okular Version: 1.5.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- Annotation tools can be selected by the keyboard shortcuts [1, 2, 3, ...]. However double pressing any of those keys doesn't freeze the annotation. Also double tapping an annotation tool through the touchscreen doesn't freeze it. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14 KDE Frameworks 5.50.0 Qt 5.11.1 (built against 5.11.1) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400065] Feature for touchscreens: freezing annotations on double-tapping the screen.
https://bugs.kde.org/show_bug.cgi?id=400065 Mina <842m...@gmail.com> changed: What|Removed |Added Summary|Features for touchscreens. |Feature for touchscreens: |Freezing annotations. |freezing annotations on ||double-tapping the screen. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400065] Features for touchscreens. Freezing annotations.
https://bugs.kde.org/show_bug.cgi?id=400065 --- Comment #4 from Mina <842m...@gmail.com> --- Alright. Will do. But I don't know how to edit the description of this thread. Also were the tags correct? I just marked the importance as "wishlist". Is there something else that I need to do? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400065] Features for touchscreens. Freezing annotations.
https://bugs.kde.org/show_bug.cgi?id=400065 --- Comment #2 from Mina <842m...@gmail.com> --- Oops very sorry. I just thought I'd put the feature requests in one thread. I thought they might be related. How should I fix this? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400065] New: Features for touchscreens. Freezing annotations.
https://bugs.kde.org/show_bug.cgi?id=400065 Bug ID: 400065 Summary: Features for touchscreens. Freezing annotations. Product: okular Version: 1.5.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- I use Okular almost daily for studying course material. The annotations work really well with a touchscreen. If I double-click an annotation tool with the mouse it "freezes", which effectively gives me the ability to draw over pdfs like they were printed papers. However there are tiny but really important "tweaks" that can make Okular much more touch-screen friendly. 1. Annotation tools can be selected by the keyboard shortcuts [1, 2, 3, ...]. However double pressing any of those keys doesn't freeze the annotation. 2. Double tapping an annotation tool through the touchscreen doesn't freeze it. 3. Adding a popup note, then typing in the note sometimes causes the pdf to scroll for no apparent reason. 4. Inline note causes the pdf to scroll while typing in order to observe the changes on the pdf itself. I do the pdf positioning myself so I wish I can disable that feature. 5. Many times the pdf is rotated unintentionally while panning. I wish I can at least disable the rotation effect or control it's sensitivity. I would rarely need to rotate the pdf with my hands, and even if I do, I would reach out for the menu bar. The above features are the very most important. They first two would allow the user to control the type of the annotation with one hand (on the keyboard) and draw or pan with the other. Here's more touchscreen wishes below. 6. Pinching the screen to zoom is a bit jittery. 7. Sliding a finger to pan creates no momentum (or acceleration). Meaning, once finger is released, panning stops. My favorite pdf editor! Thanks for all the beautiful work :D SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14 KDE Frameworks 5.50.0 Qt 5.11.1 (built against 5.11.1) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398584] Proxy settings not effective
https://bugs.kde.org/show_bug.cgi?id=398584 --- Comment #3 from Mina <842m...@gmail.com> --- I see. When I was using Ubuntu 16.04 (with unity) it used to set the environment variables. Is there another tool that does this? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398584] Proxy settings not effective
https://bugs.kde.org/show_bug.cgi?id=398584 --- Comment #1 from Mina <842m...@gmail.com> --- Bump! Any updates on this? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398584] New: Proxy settings not effective
https://bugs.kde.org/show_bug.cgi?id=398584 Bug ID: 398584 Summary: Proxy settings not effective Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- The dialog to set the proxy doesn't work. No proxy is being set. I do "env | grep HTTP" and I can't find the environment variables that should be added. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 397271] New: Unattended access settings lost on reboot
https://bugs.kde.org/show_bug.cgi?id=397271 Bug ID: 397271 Summary: Unattended access settings lost on reboot Product: krfb Version: 18.04.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: 842m...@gmail.com Target Milestone: --- version 18.04.3 If I setup an unattended access password, then I reboot the machine it's gone. Using KDE neon, up to date. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395759] New: Monitor Displays refresh rate changes when connecting an HDMI cable.
https://bugs.kde.org/show_bug.cgi?id=395759 Bug ID: 395759 Summary: Monitor Displays refresh rate changes when connecting an HDMI cable. Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- The laptop is an HP envy x360. For this laptop if I set the refresh rate to be 59.93Hz I can't notice any flickering, but for 60.01Hz or 40.01Hz I can notice flickering. On startup the refresh rate is set to "auto", but I don't notice any flickering. Then when I connect an HDMI cable to extend my display to a second monitor I can notice flickering. When I look at the refresh rate, it's set to Auto. So I set it to 59.93 and the flickering goes away. (This doesn't affect the extended monitor in any way). If I disconnect (or also reconnect) the HDMI cable, the refresh rate is changed to auto and I can see flickering. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384695] Configurable horizontal scrolling key (ALT or SHIFT) + WHEEL
https://bugs.kde.org/show_bug.cgi?id=384695 Mina <842m...@gmail.com> changed: What|Removed |Added CC||842m...@gmail.com --- Comment #1 from Mina <842m...@gmail.com> --- Yes this is really bugging me too because I use Alt+scroll to control the opacity of windows (it's configurable through the settings). Shift + scroll is very standard. It's used in google chrome, vs code, most of ubuntu unity and many others. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 99948] "Shift+ScrollWheel" for Horizontal Scrolling
https://bugs.kde.org/show_bug.cgi?id=99948 Mina <842m...@gmail.com> changed: What|Removed |Added CC||842m...@gmail.com --- Comment #2 from Mina <842m...@gmail.com> --- Is it not possible to include a setting to specify the modifier key for horizontal scrolling? :( I have a problem with the Alt key being the modifier, I use it to change the opacity of windows, so when I horizontal scroll the opacity is also affected. This is also the case with kolourpaint. Shift+scroll is used in lots of places like google chrome, many places in ubuntu unity and others. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 392619] New: Segmentation faults with kdeconnect_notifications.so and libKF5KIOCore.so.5.44.0
https://bugs.kde.org/show_bug.cgi?id=392619 Bug ID: 392619 Summary: Segmentation faults with kdeconnect_notifications.so and libKF5KIOCore.so.5.44.0 Product: kdeconnect Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: 842m...@gmail.com Target Milestone: --- [1101981.316412] kdeconnectd[17206]: segfault at 10 ip 7f58a77b599d sp 7ffc40d8cc40 error 4 in kdeconnect_notifications.so[7f58a77af000+18000] [1101982.719294] kdeconnectd[23739]: segfault at 0 ip 7f157b9fe1d2 sp 7fff3664abe0 error 4 in libKF5KIOCore.so.5.44.0[7f157b926000+17e000] [1102607.015090] kdeconnectd[23752]: segfault at 0 ip 7f6945bfa1d2 sp 7ffd7b22d5a0 error 4 in libKF5KIOCore.so.5.44.0[7f6945b22000+17e000] [1102608.443828] kdeconnectd[25028]: segfault at 0 ip 7fc152fb11d2 sp 7fff76aaa270 error 4 in libKF5KIOCore.so.5.44.0[7fc152ed9000+17e000] [1150558.212602] kdeconnectd[25035]: segfault at 0 ip 7fe339bcc1d2 sp 7ffe4ef8dab0 error 4 in libKF5KIOCore.so.5.44.0[7fe339af4000+17e000] I'm on kde neon. Every now and then I see such things in dmesg. I have kdeconnect running on my PC and phone and I'm having it forward my phone's notifications to my pc. It's working fine. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 391857] The logout dialog doesn't run If I switch PRIME profiles in Nvidia X server settings
https://bugs.kde.org/show_bug.cgi?id=391857 --- Comment #2 from Mina <842m...@gmail.com> --- It says "ksmserver-logout-greeter does not provide a bug reporting address" In the "developer information" tab: Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa6d9a59940 (LWP 6849))] Thread 3 (Thread 0x7fa6bb7fe700 (LWP 6853)): #0 0x7fa6d535b74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa6cdf9838c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa6cdf9849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa6d5c8e5cb in QEventDispatcherGlib::processEvents (this=0x7fa6ac0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa6d5c3564a in QEventLoop::exec (this=this@entry=0x7fa6bb7fdc60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fa6d5a4 in QThread::exec (this=) at thread/qthread.cpp:522 #6 0x7fa6d7cb5a35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa6d5a5a6eb in QThreadPrivate::start (arg=0x1983180) at thread/qthread_unix.cpp:376 #8 0x7fa6cff506ba in start_thread (arg=0x7fa6bb7fe700) at pthread_create.c:333 #9 0x7fa6d536741d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fa6bbfff700 (LWP 6852)): #0 __lll_unlock_wake () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:371 #1 0x7fa6cff544ff in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7fa6cf8de950) at pthread_mutex_unlock.c:55 #2 __GI___pthread_mutex_unlock (mutex=0x7fa6cf8de950) at pthread_mutex_unlock.c:314 #3 0x7fa6cf6599e5 in ?? () from /usr/lib/nvidia-390/libGL.so.1 #4 0x7fa6cf65f0bb in ?? () from /usr/lib/nvidia-390/libGL.so.1 #5 0x7fa6cb7050f1 in ?? () from /usr/lib/nvidia-390/tls/libnvidia-tls.so.390.25 #6 0x7fa6cdfdb6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fa6cdf97e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fa6cdf98330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7fa6cdf9849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7fa6d5c8e5cb in QEventDispatcherGlib::processEvents (this=0x7fa6b40008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #11 0x7fa6d5c3564a in QEventLoop::exec (this=this@entry=0x7fa6bbffec50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #12 0x7fa6d5a4 in QThread::exec (this=this@entry=0x7fa6d6aa8d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:522 #13 0x7fa6d68342c5 in QDBusConnectionManager::run (this=0x7fa6d6aa8d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #14 0x7fa6d5a5a6eb in QThreadPrivate::start (arg=0x7fa6d6aa8d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:376 #15 0x7fa6cff506ba in start_thread (arg=0x7fa6bbfff700) at pthread_create.c:333 #16 0x7fa6d536741d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fa6d9a59940 (LWP 6849)): [KCrash Handler] #6 0x7fa6d5295428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fa6d529702a in __GI_abort () at abort.c:89 #8 0x7fa6d5a44311 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1710 #9 QMessageLogger::fatal (this=this@entry=0x7ffd225af1f0, msg=msg@entry=0x7fa6d858a47d "%s") at global/qlogging.cpp:816 #10 0x7fa6d83a1068 in QSGRenderLoop::handleContextCreationFailure (this=this@entry=0x197dea0, window=0x19772a0, isEs=) at scenegraph/qsgrenderloop.cpp:274 #11 0x7fa6d83a22a7 in QSGGuiThreadRenderLoop::renderWindow (this=this@entry=0x197dea0, window=0x19772a0) at scenegraph/qsgrenderloop.cpp:368 #12 0x7fa6d83a2aa5 in QSGGuiThreadRenderLoop::exposureChanged (this=0x197dea0, window=0x19772a0) at scenegraph/qsgrenderloop.cpp:477 #13 0x7fa6d61dc625 in QWindow::event (this=this@entry=0x19772a0, ev=ev@entry=0x7ffd225af6a0) at kernel/qwindow.cpp:2328 #14 0x7fa6d841a8c5 in QQuickWindow::event (this=this@entry=0x19772a0, e=e@entry=0x7ffd225af6a0) at items/qquickwindow.cpp:1627 #15 0x00408f31 in KSMShutdownDlg::event (this=0x19772a0, e=0x7ffd225af6a0) at /workspace/build/ksmserver/shutdowndlg.cpp:234 #16 0x7fa6d6e08acc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fa6d6e10417 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fa6d5c373c8 in QCoreApplication::notifyInternal2 (receiver=receiver@entry=0x19772a0, event=event@entry=0x7ffd225af6a0) at kernel/qcoreapplication.cpp:1044 #19 0x7fa6d61d128d
[ksmserver] [Bug 391857] New: The logout dialog doesn't run If I switch PRIME profiles in Nvidia X server settings
https://bugs.kde.org/show_bug.cgi?id=391857 Bug ID: 391857 Summary: The logout dialog doesn't run If I switch PRIME profiles in Nvidia X server settings Product: ksmserver Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: ui Assignee: l.lu...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- If I open the Nvidia X server settings, then I change PRIME profiles (either from intel to nvidia or the opposite), then I try to logout, the logout dialog can't run. It crashes and shows a notification to report the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391766] Whole desktop freezes when I run a genymotion device, using virtualbox in the repositories.
https://bugs.kde.org/show_bug.cgi?id=391766 --- Comment #2 from Mina <842m...@gmail.com> --- yes the tty doesn't work either. Ctrl + Alt + F1 to F6 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 391774] New: Typing exit in konsole shows a crash
https://bugs.kde.org/show_bug.cgi?id=391774 Bug ID: 391774 Summary: Typing exit in konsole shows a crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- Application: kdeinit5 (17.12.2) Qt Version: 5.10.0 Frameworks Version: 5.43.0 Operating System: Linux 4.13.0-36-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: I just type "exit" in konsole. Most of the time I get a crash message. konsole is just supposed to close. The crash can be reproduced every time. -- Backtrace: Application: Konsole (kdeinit5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fad590fa780 (LWP 22213))] Thread 2 (Thread 0x7fad3b264700 (LWP 22217)): #0 0x7fad571c874d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fad537bd38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fad537bd49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fad577795cb in QEventDispatcherGlib::processEvents (this=0x7fad340008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fad5772064a in QEventLoop::exec (this=this@entry=0x7fad3b263e10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fad57540554 in QThread::exec (this=) at thread/qthread.cpp:522 #6 0x7fad4db972c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fad575456eb in QThreadPrivate::start (arg=0x7fad4de0bd60) at thread/qthread_unix.cpp:376 #8 0x7fad5562f6ba in start_thread (arg=0x7fad3b264700) at pthread_create.c:333 #9 0x7fad571d441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fad590fa780 (LWP 22213)): [KCrash Handler] #6 0x7fad57102428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fad5710402a in __GI_abort () at abort.c:89 #8 0x7fad571447ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fad5725ded8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7fad5714d37a in malloc_printerr (ar_ptr=, ptr=, str=0x7fad5725dfe8 "double free or corruption (out)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7fad5715153c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x7fad5774bb8c in QMetaCallEvent::~QMetaCallEvent (this=0x7fad3c003630, __in_chrg=) at kernel/qobject.cpp:485 #13 0x7fad5774bbe9 in QMetaCallEvent::~QMetaCallEvent (this=0x7fad3c003630, __in_chrg=) at kernel/qobject.cpp:493 #14 0x7fad577256ef in QCoreApplication::removePostedEvents (receiver=0xa89cb0, eventType=eventType@entry=0) at kernel/qcoreapplication.cpp:1796 #15 0x7fad5774ec4a in QObjectPrivate::~QObjectPrivate (this=0xa8a050, __in_chrg=) at kernel/qobject.cpp:252 #16 0x7fad5774edf9 in QObjectPrivate::~QObjectPrivate (this=0xa8a050, __in_chrg=) at kernel/qobject.cpp:263 #17 0x7fad57756edc in QScopedPointerDeleter::cleanup (pointer=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:60 #18 QScopedPointer >::~QScopedPointer (this=0xa89cb8, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107 #19 QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:881 #20 0x7fad457f7489 in QXcbConnection::~QXcbConnection (this=0xa89cb0, __in_chrg=) at qxcbconnection.cpp:678 #21 0x7fad457f8fa6 in qDeleteAll::const_iterator> (end=..., begin=...) at ../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:320 #22 qDeleteAll > (c=...) at ../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:328 #23 QXcbIntegration::~QXcbIntegration (this=0xa5b1d0, __in_chrg=) at qxcbintegration.cpp:224 #24 0x7fad457f90a9 in QXcbIntegration::~QXcbIntegration (this=0xa5b1d0, __in_chrg=) at qxcbintegration.cpp:226 #25 0x7fad57cb1333 in QGuiApplicationPrivate::~QGuiApplicationPrivate (this=0xa37d60, __in_chrg=) at kernel/qguiapplication.cpp:1548 #26 0x7fad55ba03e9 in QApplicationPrivate::~QApplicationPrivate (this=0xa37d60, __in_chrg=) at kernel/qapplication.cpp:189 #27 0x7fad57756edc in QScopedPointerDeleter::cleanup (pointer=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:60 #28 QScopedPointer >::~QScopedPointer (this=0xa39458, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107 #29 QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:881 #30 0x7fad57724802 in QCoreApplication::~QCoreApplication (this=0xa39450, __in_chrg=) at kernel/qcoreapplication.cpp:877 #31 0x7fad55ba22b4 in QApplication::~QApp
[plasmashell] [Bug 391766] New: Whole desktop freezes when I run a genymotion device, using virtualbox in the repositories.
https://bugs.kde.org/show_bug.cgi?id=391766 Bug ID: 391766 Summary: Whole desktop freezes when I run a genymotion device, using virtualbox in the repositories. Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: 842m...@gmail.com Target Milestone: 1.0 I'm trying to run a genymotion device on kde neon. I tried installing the version of virtualbox that's in the repositories. (sudo apt install virtualbox), then when I run a genymotion device the whole computer freezes and I have to restart. Even REISUB doesn't work. I can understand if a genymotion device doesn't run but not freeze the entire desktop. Also note that virtualbox version 5.2 doesn't work either. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391498] Tablet mode for convertibles (laptops with hinge screens)
https://bugs.kde.org/show_bug.cgi?id=391498 --- Comment #3 from Mina <842m...@gmail.com> --- It's enough to get a reply! Thank you :D Actually I just noticed that sometimes when I flip the laptop into a tablet the keyboard and touchpad are disabled correctly! (the keys on the side work but the keyboard & touchpad are disabled) but it's inconsistent. Sometimes it's disabled and sometimes not! I've been searching and asking about the sensors. I can get readings of the gyro and accelerometer (and other sensors) at /sys/bus/iio/devices -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 391503] New: konsole crash
https://bugs.kde.org/show_bug.cgi?id=391503 Bug ID: 391503 Summary: konsole crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- Application: kdeinit5 (17.12.2) Qt Version: 5.10.0 Frameworks Version: 5.43.0 Operating System: Linux 4.13.0-36-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: getting crash messages right after login (after restart). Although there are konsole windows still open and working. -- Backtrace: Application: Konsole (kdeinit5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1f5ca3c780 (LWP 2818))] Thread 2 (Thread 0x7f1f3eb1f700 (LWP 2866)): #0 0x7f1f5ab0a74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1f570ff38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1f570ff49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1f5b0bb5cb in QEventDispatcherGlib::processEvents (this=0x7f1f380008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f1f5b06264a in QEventLoop::exec (this=this@entry=0x7f1f3eb1ee10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f1f5ae82554 in QThread::exec (this=) at thread/qthread.cpp:522 #6 0x7f1f514d92c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f1f5ae876eb in QThreadPrivate::start (arg=0x7f1f5174dd60) at thread/qthread_unix.cpp:376 #8 0x7f1f58f716ba in start_thread (arg=0x7f1f3eb1f700) at pthread_create.c:333 #9 0x7f1f5ab1641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f1f5ca3c780 (LWP 2818)): [KCrash Handler] #6 0x7f1f5aa44428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f1f5aa4602a in __GI_abort () at abort.c:89 #8 0x7f1f5aa867ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f1f5ab9fed8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7f1f5aa8f37a in malloc_printerr (ar_ptr=, ptr=, str=0x7f1f5ab9ffe8 "double free or corruption (out)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7f1f5aa9353c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x7f1f5b08db8c in QMetaCallEvent::~QMetaCallEvent (this=0x7f1f40023cd0, __in_chrg=) at kernel/qobject.cpp:485 #13 0x7f1f5b08dbe9 in QMetaCallEvent::~QMetaCallEvent (this=0x7f1f40023cd0, __in_chrg=) at kernel/qobject.cpp:493 #14 0x7f1f5b0676ef in QCoreApplication::removePostedEvents (receiver=0x1475db0, eventType=eventType@entry=0) at kernel/qcoreapplication.cpp:1796 #15 0x7f1f5b090c4a in QObjectPrivate::~QObjectPrivate (this=0x1476150, __in_chrg=) at kernel/qobject.cpp:252 #16 0x7f1f5b090df9 in QObjectPrivate::~QObjectPrivate (this=0x1476150, __in_chrg=) at kernel/qobject.cpp:263 #17 0x7f1f5b098edc in QScopedPointerDeleter::cleanup (pointer=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:60 #18 QScopedPointer >::~QScopedPointer (this=0x1475db8, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107 #19 QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:881 #20 0x7f1f49139489 in QXcbConnection::~QXcbConnection (this=0x1475db0, __in_chrg=) at qxcbconnection.cpp:678 #21 0x7f1f4913afa6 in qDeleteAll::const_iterator> (end=..., begin=...) at ../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:320 #22 qDeleteAll > (c=...) at ../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:328 #23 QXcbIntegration::~QXcbIntegration (this=0x1446da0, __in_chrg=) at qxcbintegration.cpp:224 #24 0x7f1f4913b0a9 in QXcbIntegration::~QXcbIntegration (this=0x1446da0, __in_chrg=) at qxcbintegration.cpp:226 #25 0x7f1f5b5f in QGuiApplicationPrivate::~QGuiApplicationPrivate (this=0x14241d0, __in_chrg=) at kernel/qguiapplication.cpp:1548 #26 0x7f1f594e23e9 in QApplicationPrivate::~QApplicationPrivate (this=0x14241d0, __in_chrg=) at kernel/qapplication.cpp:189 #27 0x7f1f5b098edc in QScopedPointerDeleter::cleanup (pointer=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:60 #28 QScopedPointer >::~QScopedPointer (this=0x1432a18, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107 #29 QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:881 #30 0x7f1f5b066802 in QCoreApplication::~QCoreApplication (this=0x1432a10, __in_chrg=) at kernel/qcoreapplication.cpp:877 #31 0x7f1f594e42b4 in QApplication::~QApplication (this=0x1432a10, __in_chrg=) at ker
[plasmashell] [Bug 391498] Tablet mode for convertibles (laptops with hinge screens)
https://bugs.kde.org/show_bug.cgi?id=391498 --- Comment #1 from Mina <842m...@gmail.com> --- My laptop's product model: 15-w107ne -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391498] New: Tablet mode for convertibles (laptops with hinge screens)
https://bugs.kde.org/show_bug.cgi?id=391498 Bug ID: 391498 Summary: Tablet mode for convertibles (laptops with hinge screens) Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: 842m...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 My laptop is an HP envy x360 convertible. It's screen can be rotated 360 degrees (so that the back of the screen touches the back of the keyboard and the laptop becomes very much like a tablet). The laptop has windows preinstalled. On windows when I rotate the screen 360 degrees, windows detects this and asks to "switch to tablet mode". In tablet mode: - screen is rotated according to orientation* - keyboard and touchpad are disabled** - an on-screen keyboard pops up for anything that needs a keyboard (the android way) - (not sure of this) a 2-finger click triggers a right-click. This currently works in google chrome. Try it on chrome with a touch screen. *(it seems the laptop has a built-in gsensor) (this can be done using `xrandr -o right` `xrandr -o inverted` `xrandr -o normal`... **There volume up & down buttons and a "meta" button on the side. Those are meant to be used in tablet mode. When I disable the entire keyboard those are disabled too. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391023] Can't draw using the touch screen
https://bugs.kde.org/show_bug.cgi?id=391023 --- Comment #4 from Mina <842m...@gmail.com> --- wow it's fixed. Now I can draw with the touch screen. I didn't do anything. Thanks X) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390435] Plasma crashed, and after rebooting many things aren't working.
https://bugs.kde.org/show_bug.cgi?id=390435 --- Comment #3 from Mina <842m...@gmail.com> --- It should be reproducible but I uninstalled the system. I replaced it with kde neon. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391226] New: Dolphin crash. Was closing a tab.
https://bugs.kde.org/show_bug.cgi?id=391226 Bug ID: 391226 Summary: Dolphin crash. Was closing a tab. Product: dolphin Version: 17.12.2 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: 842m...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.2) Qt Version: 5.10.0 Frameworks Version: 5.43.0 Operating System: Linux 4.13.0-36-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: unmounted a partition and was closing a tab that was in a directory in that partition using the mouse middle click -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6b006d4900 (LWP 14040))] Thread 3 (Thread 0x7f6adca06700 (LWP 14043)): #0 0x7f6b274d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6af2f3238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6af2f3249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6afa25a5cb in QEventDispatcherGlib::processEvents (this=0x7f6ad40008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f6afa20164a in QEventLoop::exec (this=this@entry=0x7f6adca05cc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f6afa021554 in QThread::exec (this=) at thread/qthread.cpp:522 #6 0x7f6afa0266eb in QThreadPrivate::start (arg=0x285eba0) at thread/qthread_unix.cpp:376 #7 0x7f6af53406ba in start_thread (arg=0x7f6adca06700) at pthread_create.c:333 #8 0x7f6be41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f6ae56e3700 (LWP 14042)): #0 0x7f6b274d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6af2f3238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6af2f3249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6afa25a5cb in QEventDispatcherGlib::processEvents (this=0x7f6ad80008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f6afa20164a in QEventLoop::exec (this=this@entry=0x7f6ae56e2c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f6afa021554 in QThread::exec (this=) at thread/qthread.cpp:522 #6 0x7f6afa67d2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f6afa0266eb in QThreadPrivate::start (arg=0x7f6afa8f1d60) at thread/qthread_unix.cpp:376 #8 0x7f6af53406ba in start_thread (arg=0x7f6ae56e3700) at pthread_create.c:333 #9 0x7f6be41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f6b006d4900 (LWP 14040)): [KCrash Handler] #6 0x7f6afa14acbc in QUrl::~QUrl (this=0x2f6b408, __in_chrg=) at io/qurl.cpp:1858 #7 0x7f6aff78f144 in LocationData::~LocationData (this=0x2f6b400, __in_chrg=) at /workspace/build/src/filewidgets/kurlnavigator.cpp:57 #8 QList::node_destruct (this=, to=0x317a0c8, from=0x317a0c8) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:494 #9 QList::dealloc (data=0x317a0b0, this=0x2c16970) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:865 #10 0x7f6aff79014d in QList::~QList (this=0x2c16970, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:827 #11 KUrlNavigator::Private::~Private (this=0x2c16960, __in_chrg=) at /workspace/build/src/filewidgets/kurlnavigator.cpp:66 #12 KUrlNavigator::~KUrlNavigator (this=0x2ac78c0, __in_chrg=) at /workspace/build/src/filewidgets/kurlnavigator.cpp:849 #13 0x7f6aff790169 in KUrlNavigator::~KUrlNavigator (this=0x2ac78c0, __in_chrg=) at /workspace/build/src/filewidgets/kurlnavigator.cpp:850 #14 0x7f6afa22df73 in QObjectPrivate::deleteChildren (this=this@entry=0x2bad030) at kernel/qobject.cpp:1992 #15 0x7f6afb20a6a4 in QWidget::~QWidget (this=0x2aecf10, __in_chrg=) at kernel/qwidget.cpp:1711 #16 0x7f6b00323d11 in DolphinViewContainer::~DolphinViewContainer (this=0x2aecf10, __in_chrg=) at /workspace/build/src/dolphinviewcontainer.cpp:208 #17 DolphinViewContainer::~DolphinViewContainer (this=0x2aecf10, __in_chrg=) at /workspace/build/src/dolphinviewcontainer.cpp:210 #18 0x7f6afa22df73 in QObjectPrivate::deleteChildren (this=this@entry=0x2dc2020) at kernel/qobject.cpp:1992 #19 0x7f6afb20a6a4 in QWidget::~QWidget (this=0x2e3cbb0, __in_chrg=) at kernel/qwidget.cpp:1711 #20 0x7f6afb37cd09 in QSplitter::~QSplitter (this=0x2e3cbb0, __in_chrg=) at widgets/qsplitter.cpp:984 #21 0x7f6afa22df73 in QObjectPrivate::deleteChildren (this=this@entry=0x2527bd0) at kernel/qobject.cpp:1992 #22 0x7f6afb20a6a4 in QWidget::~QWidget (this=0x2b
[kwin] [Bug 391097] Session freezes randomly with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=391097 --- Comment #1 from Mina <842m...@gmail.com> --- Created attachment 111007 --> https://bugs.kde.org/attachment.cgi?id=111007&action=edit dmesg from the tty -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391097] New: Session freezes randomly with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=391097 Bug ID: 391097 Summary: Session freezes randomly with nvidia drivers Product: kwin Version: 5.12.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: scene-opengl Assignee: kwin-bugs-n...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- This is more of an nvidia bug but it didn't use to happen in normal Ubuntu (with unity). I have an nvidia GTX 770 card and I have the proprietary drivers installed (390.25). Frequently kwin crashes. (not sure if specifically kwin). What happens is that plasma just freezes. I can only move the mouse. I can get to the tty. in dmesg I see segmentation fault in libnvidia-glcore.so.390.25 This mostly happens when I activate "show desktop grid". Right now I open a tty and do `sudo systemctl restart sddm` but this is effectively a new session and everything I was doing is lost. Is there some workaround with which I can restore my current session? In the compositor's settings I tried opengl 2 and 3.1 and xrender -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391023] Can't draw using the touch screen
https://bugs.kde.org/show_bug.cgi?id=391023 --- Comment #2 from Mina <842m...@gmail.com> --- Hi! settings > configure krita > General > Tools > Enable Touch Painting this is already enabled but I can't draw. Is this it or there is something else? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391023] New: Can't draw using the touch screen
https://bugs.kde.org/show_bug.cgi?id=391023 Bug ID: 391023 Summary: Can't draw using the touch screen Product: krita Version: 3.3.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- Laptop model is HP envy x360 convertible. I can't draw using the touch screen. I try any of the tools; the freehand brush tool, the line tool, the rectangle... I can only draw using the mouse by clicking. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 390986] can't boot into kde neon. sddm shows black screen
https://bugs.kde.org/show_bug.cgi?id=390986 Mina <842m...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Mina <842m...@gmail.com> --- Okay I connected to the internet using ifconfig, then did sudo apt update and that fixed it. apparently somehow my system had some old qt packages and some new qt packages. I got help on IRC freenode #kde-neon. Thanks -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 390982] Can't start kolourpaint
https://bugs.kde.org/show_bug.cgi?id=390982 Mina <842m...@gmail.com> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 390983] konsole crashes when I right-click it
https://bugs.kde.org/show_bug.cgi?id=390983 Mina <842m...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 390982] Can't start kolourpaint
https://bugs.kde.org/show_bug.cgi?id=390982 --- Comment #2 from Mina <842m...@gmail.com> --- I rebooted after that and now sddm is black https://bugs.kde.org/show_bug.cgi?id=390986 maybe the problem is that I installed kio-extras? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390986] can't boot into kde neon. sddm shows black screen
https://bugs.kde.org/show_bug.cgi?id=390986 --- Comment #1 from Mina <842m...@gmail.com> --- I also need to mention that the laptop now isn't connected to the internet -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390986] New: can't boot into kde neon. sddm shows black screen
https://bugs.kde.org/show_bug.cgi?id=390986 Bug ID: 390986 Summary: can't boot into kde neon. sddm shows black screen Product: plasmashell Version: 5.12.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: 842m...@gmail.com Target Milestone: 1.0 I only get a black screen with the cursor visible in the middle. This happened after those two issues https://bugs.kde.org/show_bug.cgi?id=390983 https://bugs.kde.org/show_bug.cgi?id=390982 What may be the cause is that I installed kio-extras. I purged it from tty and rebooted but it's not fixed. I don't know what else may cause the problem. please help. I need to get moving with my work. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 390983] New: konsole crashes when I right-click it
https://bugs.kde.org/show_bug.cgi?id=390983 Bug ID: 390983 Summary: konsole crashes when I right-click it Product: konsole Version: 17.12.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: copy-paste Assignee: konsole-de...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- I opened a konsole from another konsole, when I right-click this is what I get: $ konsole Empty filename passed to function Cannot mix incompatible Qt library (version 0x50903) with this library (version 0x50a00) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = konsole path = /usr/bin pid = 14146 KCrash: Arguments: /usr/bin/konsole KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 Killed might be somehow related to https://bugs.kde.org/show_bug.cgi?id=390982 both happened at the same time and the error output in the terminal seems the same also I can't open system settings -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 390982] New: Can't start kolourpaint
https://bugs.kde.org/show_bug.cgi?id=390982 Bug ID: 390982 Summary: Can't start kolourpaint Product: kolourpaint Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: 842m...@gmail.com Target Milestone: --- I tried to start it from terminal. This is what I get: $ kolourpaint Empty filename passed to function Cannot mix incompatible Qt library (version 0x50903) with this library (version 0x50a00) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kolourpaint path = /usr/bin pid = 13068 KCrash: Arguments: /usr/bin/kolourpaint KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 Killed I'm using a fresh install of KDE neon. I think this happened after I tried opening an image with kolourpaint directly from dolphin. I right-clicked the image > open with > kolourpaint. kolourpaint version 17.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 390660] New: Konsole crash after installing nvidia proprietary drivers and restart
https://bugs.kde.org/show_bug.cgi?id=390660 Bug ID: 390660 Summary: Konsole crash after installing nvidia proprietary drivers and restart Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- Application: kdeinit5 (17.12.2) Qt Version: 5.9.3 Frameworks Version: 5.43.0 Operating System: Linux 4.13.0-32-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: I installed the nvidia proprietary drivers then restarted. -- Backtrace: Application: Konsole (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe4e509d780 (LWP 1451))] Thread 3 (Thread 0x7fe4c7544700 (LWP 1456)): #0 0x7fe4df9fea94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe4df9b9910 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe4df9ba2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe4df9ba49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe4e36f36cb in QEventDispatcherGlib::processEvents (this=0x7fe4c8e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fe4e369be2a in QEventLoop::exec (this=this@entry=0x7fe4c7543e10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7fe4e34c48f4 in QThread::exec (this=this@entry=0x7fe4da00cd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:515 #7 0x7fe4d9d98315 in QDBusConnectionManager::run (this=0x7fe4da00cd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7fe4e34c9709 in QThreadPrivate::start (arg=0x7fe4da00cd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #9 0x7fe4e15bd6ba in start_thread (arg=0x7fe4c7544700) at pthread_create.c:333 #10 0x7fe4e315a41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fe4ceec1700 (LWP 1453)): #0 0x7fe4e314e74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe4e44fbc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fe4e44fd8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fe4d1a4a1f9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fe4e34c9709 in QThreadPrivate::start (arg=0x23b0900) at thread/qthread_unix.cpp:368 #5 0x7fe4e15bd6ba in start_thread (arg=0x7fe4ceec1700) at pthread_create.c:333 #6 0x7fe4e315a41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fe4e509d780 (LWP 1451)): [KCrash Handler] #6 0x7fe4e34afa17 in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x6) at /usr/include/c++/5/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x6) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:102 #9 QtPrivate::RefCount::deref (this=0x6) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:66 #10 QString::~QString (this=0x7fe4c0010d78, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qstring.h:1084 #11 QList::node_destruct (this=0x7fe4c0010d78, to=0x7fe4c0010d78, from=0x7fe4c0010db0) at ../../include/QtCore/../../src/corelib/tools/qlist.h:496 #12 QList::dealloc (this=0x7fe4c0010d78, data=0x7fe4c0010d70) at ../../include/QtCore/../../src/corelib/tools/qlist.h:865 #13 QList::~QList (this=this@entry=0x7fe4c8c0, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qlist.h:827 #14 0x7fe4e36e4985 in QStringList::~QStringList (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qstringlist.h:101 #15 v_clear (d=0x7fe4c8c0) at ../../include/QtCore/5.9.3/QtCore/private/../../../../../src/corelib/kernel/qvariant_p.h:175 #16 QVariantDestructor<(anonymous namespace)::CoreTypesFilter>::FilteredDestructor::FilteredDestructor (this=, d=0x7fe4c8c0) at ../../include/QtCore/5.9.3/QtCore/private/../../../../../src/corelib/kernel/qvariant_p.h:400 #17 QVariantDestructor<(anonymous namespace)::CoreTypesFilter>::delegate (this=) at ../../include/QtCore/5.9.3/QtCore/private/../../../../../src/corelib/kernel/qvariant_p.h:426 #18 QMetaTypeSwitcher::switcher > (data=0x0, type=, logic=) at ../../include/QtCore/5.9.3/QtCore/private/../../../../../src/corelib/kernel/qmetatypeswitcher_p.h:74 #19 (anonymous namespace)::clear (d=0x7fe4c8c0) at kernel/qvariant.cpp:120 #20 0x7fe4d9d9d3b4 in QL
[plasmashell] [Bug 390435] Plasma crashed, and after rebooting many things aren't working.
https://bugs.kde.org/show_bug.cgi?id=390435 --- Comment #1 from Mina <842m...@gmail.com> --- I think I may have found the cause. Try running kazam, and start a recording. Then try opening a new konsole. That konsole doesn't display correctly and consequently plasma crashes. I'm using Nvidia's proprietary drivers. Card is GTX770. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390435] Plasma crashed, and after rebooting many things aren't working.
https://bugs.kde.org/show_bug.cgi?id=390435 Mina <842m...@gmail.com> changed: What|Removed |Added Version|master |5.10.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390435] New: Plasma crashed, and after rebooting many things aren't working.
https://bugs.kde.org/show_bug.cgi?id=390435 Bug ID: 390435 Summary: Plasma crashed, and after rebooting many things aren't working. Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: 842m...@gmail.com Target Milestone: 1.0 Created attachment 110646 --> https://bugs.kde.org/attachment.cgi?id=110646&action=edit the xsession errors file Plasma5 has gone terribly wrong. I really don't know where the problem is exactly. Plasma effects? The worst thing is that restarting doesn't fix the problems. The system is almost unusable. How this happened; I opened a new konsole then it froze then everything else froze so I rebooted, and since then things are so. Now the hot corners are not working. Desktop grid not working (Probably the problem is with the keyboard shortcut, but whatever I try assigning to it it doesn't work) Present all windows doesn't work (same as above). Some applets aren't being displayed, like the applet for kazam. Effects are not working (like switching between workspaces). I'm on Kubuntu 17.10 It's a fresh install & everything is up to date. What else should I attach? help :( -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 388414] Crash in QQuickItemPrivate::deliverKeyEvent() when typing in System Settings search box
https://bugs.kde.org/show_bug.cgi?id=388414 Mina <842m...@gmail.com> changed: What|Removed |Added CC||842m...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 388414] Crash in QQuickItemPrivate::deliverKeyEvent() when typing in System Settings search box
https://bugs.kde.org/show_bug.cgi?id=388414 --- Comment #21 from Mina <842m...@gmail.com> --- Created attachment 110506 --> https://bugs.kde.org/attachment.cgi?id=110506&action=edit New crash information added by DrKonqi systemsettings5 (5.11.5) using Qt 5.10.0 - What I was doing when the application crashed: I was under system settings and I was typing in the search box. -- Backtrace (Reduced): #5 0x7f8446d67192 in QGuiApplicationPrivate::sendQWindowEventToQPlatformWindow(QWindow*, QEvent*) () from /usr/lib/libQt5Gui.so.5 #6 0x7f84475818dc in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #7 0x7f844595a850 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 [...] #9 0x7f8443ce169d in QQuickItemPrivate::filterKeyEvent(QKeyEvent*, bool) () from /usr/lib/libQt5Quick.so.5 #10 0x7f8443cede76 in QQuickItemPrivate::deliverKeyEvent(QKeyEvent*) () from /usr/lib/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390212] New: System settings crash
https://bugs.kde.org/show_bug.cgi?id=390212 Bug ID: 390212 Summary: System settings crash Product: systemsettings Version: 5.11.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- Application: systemsettings5 (5.11.5) Qt Version: 5.10.0 Frameworks Version: 5.42.0 Operating System: Linux 4.14.15-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was under system settings > keyboard shortcuts > global shortcuts. I clicked something, either an item under the "component" menu or an item under the menu to its left (the shortcuts menu) -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fba39f30c80 (LWP 3527))] Thread 7 (Thread 0x7fb9fa72c700 (LWP 3535)): #0 0x7fba35b0197b in poll () at /usr/lib/libc.so.6 #1 0x7fba2f633ff3 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fba2f63410e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fba3644cd24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fba363eee9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fba361fe78e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fba3426da19 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fba36203b2d in () at /usr/lib/libQt5Core.so.5 #8 0x7fba3185508c in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fba35b0be7f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fba023bb700 (LWP 3534)): #0 0x7fba35b0197b in poll () at /usr/lib/libc.so.6 #1 0x7fba2f633ff3 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fba2f63410e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fba3644cd24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fba363eee9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fba361fe78e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fba3426da19 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fba36203b2d in () at /usr/lib/libQt5Core.so.5 #8 0x7fba3185508c in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fba35b0be7f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fba0a17d700 (LWP 3532)): #0 0x7fba35b0197b in poll () at /usr/lib/libc.so.6 #1 0x7fba2f633ff3 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fba2f63410e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fba3644cd24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fba363eee9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fba361fe78e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fba3426da19 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fba36203b2d in () at /usr/lib/libQt5Core.so.5 #8 0x7fba3185508c in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fba35b0be7f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fba10b19700 (LWP 3530)): #0 0x7fba3185b3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fba15f31fec in () at /usr/lib/dri/nouveau_dri.so #2 0x7fba15f31ef8 in () at /usr/lib/dri/nouveau_dri.so #3 0x7fba3185508c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fba35b0be7f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fba1dbc9700 (LWP 3529)): #0 0x7fba35b0197b in poll () at /usr/lib/libc.so.6 #1 0x7fba2f633ff3 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fba2f63410e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fba3644cd24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fba363eee9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fba361fe78e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fba3686e416 in () at /usr/lib/libQt5DBus.so.5 #7 0x7fba36203b2d in () at /usr/lib/libQt5Core.so.5 #8 0x7fba3185508c in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fba35b0be7f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fba26c10700 (LWP 3528)): #0 0x7fba35b0197b in poll () at /usr/lib/libc.so.6 #1 0x7fba320d88e0 in () at /usr/lib/libxcb.so.1 #2 0x7fba320da679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fba299bd7aa in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fba36203b2d in () at /usr/lib/libQt5Core.so.5 #5 0x7fba3185508c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fba35b0be7f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fba39f30c80 (L
