[kde] [Bug 467806] New: kdenlive 22.12.3 What it is? I spent four days editing the video!!!!
https://bugs.kde.org/show_bug.cgi?id=467806 Bug ID: 467806 Summary: kdenlive 22.12.3 What it is? I spent four days editing the video Classification: I don't know Product: kde Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: a0...@ukr.net Target Milestone: --- Qt: Session management error: None of the authentication protocols specified are supported [mp3float @ 0x7f88085fdbc0] Could not update timestamps for skipped samples. [mp3float @ 0x7f88082d8ac0] Could not update timestamps for skipped samples. qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #path7198 is undefined! qt.svg: link #path7198 is undefined! qt.svg: Invalid path data; path truncated. qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_9_ is undefined! qt.svg: link #SVGID_11_ is undefined! qt.svg: link #SVGID_13_ is undefined! qt.svg: link #SVGID_1_ is undefined! qt.svg: link #SVGID_3_ is undefined! qt.svg: link #SVGID_5_ is undefined! qt.svg: link #SVGID_7_ is undefined! qt.svg: link #SVGID_9_
[okular] [Bug 400287] New: Trim margin tabs
https://bugs.kde.org/show_bug.cgi?id=400287 Bug ID: 400287 Summary: Trim margin tabs Product: okular Version: 1.5.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: forsi...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400287] Trim margin tabs
https://bugs.kde.org/show_bug.cgi?id=400287 Evgenii changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400327] New: Trim Margins does not work properly when applied to files opened in different tabs
https://bugs.kde.org/show_bug.cgi?id=400327 Bug ID: 400327 Summary: Trim Margins does not work properly when applied to files opened in different tabs Product: okular Version: 1.5.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: forsi...@gmail.com Target Milestone: --- SUMMARY Trim Margins does not work properly when applied to pdf-files opened in different tabs STEPS TO REPRODUCE 1. Open multiple pdf-files in tabs (e.g. file1.pdf and file2.pdf) 2. Switch to file1.pdf 3. Select View - Trim View - Trim Margins (or just click on a button on a toolbar) 4. Switch to file2.pdf 5. Select View - Trim View - Trim Margins (or just click on a button on a toolbar) 6. Switch back to file1.pdf 7. Unselect View - Trim View - Trim Margins (or just click on a button on a toolbar) OBSERVED RESULT After step #5 file2.pdf is not trimmed. After step #7 file1.pdf remains trimmed. EXPECTED RESULT After steps #5 and #7 files to be trimmed and untrimmed respectively. SOFTWARE VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.14.2 Qt Version: 5.11.2 KDE Frameworks Version: 5.51.0 Kernel Version: 4.14.78-1-lts OS Type: 64-bit Operating System: Microsoft Windows 10 Home Single Language OS Type: 64-bit Qt Version: 5.11.2 (built against 5.11.2) KDE Frameworks Version: 5.50.0 -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 395363] Touchpad indicator - always shows that Touchpad is enabled
https://bugs.kde.org/show_bug.cgi?id=395363 --- Comment #2 from Evgenii --- Fixed in the package kdeplasma-addons 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 395363] Touchpad indicator - always shows that Touchpad is enabled
https://bugs.kde.org/show_bug.cgi?id=395363 Evgenii changed: What|Removed |Added Version Fixed In||5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 403422] New: Whitespace highlight marker size cannot be changed
https://bugs.kde.org/show_bug.cgi?id=403422 Bug ID: 403422 Summary: Whitespace highlight marker size cannot be changed Product: kate Version: 18.12.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: forsi...@gmail.com Target Milestone: --- SUMMARY Whitespace highlight marker size cannot be changed in settings. STEPS TO REPRODUCE 1. Go to Settings -> Configure Kate -> Editor Component -> Appearance -> General. 2. Try to increase the Highlight marker size. OBSERVED RESULT The slider indicator does not move, the settings window is grabbed instead. EXPECTED RESULT Change the marker size. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.14.5 Qt Version: 5.12.0 KDE Frameworks Version: 5.54.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390265] Multiple windows from the same application sometimes are not grouped
https://bugs.kde.org/show_bug.cgi?id=390265 Evgenii changed: What|Removed |Added CC||forsi...@gmail.com --- Comment #3 from Evgenii --- Created attachment 115594 --> https://bugs.kde.org/attachment.cgi?id=115594&action=edit Ungrouped icons -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390265] Multiple windows from the same application sometimes are not grouped
https://bugs.kde.org/show_bug.cgi?id=390265 --- Comment #4 from Evgenii --- Created attachment 115595 --> https://bugs.kde.org/attachment.cgi?id=115595&action=edit Grouped after all windows are selected individually -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 394318] New: Replacing file without confirmation
https://bugs.kde.org/show_bug.cgi?id=394318 Bug ID: 394318 Summary: Replacing file without confirmation Product: dolphin Version: 18.04.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: forsi...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- While pasting an image from clipboard and giving a name to the file that is going to be created the same as one of the existing files, the existing file is replaced without confirmation. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 394318] Replacing a file without confirmation
https://bugs.kde.org/show_bug.cgi?id=394318 Evgenii changed: What|Removed |Added Summary|Replacing file without |Replacing a file without |confirmation|confirmation -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399049] New: Layout switching set to Alt+Shift breaks Alt+Shift+Tab shortcut for reverse navigation through windows
https://bugs.kde.org/show_bug.cgi?id=399049 Bug ID: 399049 Summary: Layout switching set to Alt+Shift breaks Alt+Shift+Tab shortcut for reverse navigation through windows Product: systemsettings Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: unassigned-b...@kde.org Reporter: forsi...@gmail.com Target Milestone: --- SUMMARY Layout switching set to Alt+Shift breaks Alt+Shift+Tab shortcut for reverse navigation through windows. STEPS TO REPRODUCE 1. Set the Reverse Navigation Through Windows shortcut to Alt+Shift+Tab 2. Select Alt+Shift as a Switching to another layout shortcut 3. Open multiple windows 4. Press Alt+Shift+Tab OBSERVED RESULT 1. If the forward navigation through windows set to Alt+Tab: Alt+Shift+Tab firstly switches the layout right after the combination Alt+Shift is pressed then after the Tab pressed and released(while Alt and Shift are held pressed) KWin switches windows in a forward direction. 2. If the forward navigation through windows is assigned to other combination, e.g. Alt+F12: Alt+Shift+Tab only switches the layout right after Alt+Shift is pressed. EXPECTED RESULT Switching layouts by Alt+Shift and switching windows backwardly. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Probably changing an event type for layout switching from "key pressed" to "key released" could solve the problem. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 395360] New: Keyboard indicator - NumLock is always locked
https://bugs.kde.org/show_bug.cgi?id=395360 Bug ID: 395360 Summary: Keyboard indicator - NumLock is always locked Product: kdeplasma-addons Version: 5.13.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: forsi...@gmail.com Target Milestone: --- With an upgrade to plasma 5.13 Keyboard indicator addon has got installed. When NumLock is activated and after deactivated the plasmoid still shows that Num keys are locked. However, when in the settings only CapsLock option is checked the behavior is correct: both lock and unlock are indicated properly. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 395363] New: Touchpad indicator - always shows that Touchpad is enabled
https://bugs.kde.org/show_bug.cgi?id=395363 Bug ID: 395363 Summary: Touchpad indicator - always shows that Touchpad is enabled Product: Touchpad-KCM Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: plasma-applet Assignee: rajeeshknamb...@gmail.com Reporter: forsi...@gmail.com Target Milestone: --- After upgrade to Plasma 5.13 the touchpad indicator always shows that a touchpad is enabled, even when it is not. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 395363] Touchpad indicator - always shows that Touchpad is enabled
https://bugs.kde.org/show_bug.cgi?id=395363 Evgenii changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] New: Menubar - No text
https://bugs.kde.org/show_bug.cgi?id=395497 Bug ID: 395497 Summary: Menubar - No text Product: okular Version: 1.4.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: forsi...@gmail.com Target Milestone: --- Created attachment 113381 --> https://bugs.kde.org/attachment.cgi?id=113381&action=edit Menubar screenshot After "Show Menubar" button was added to Main Toolbar or the button was triggered (did not notice when exactly) some 1st level items of the menubar are labeled as "No text". -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] Menubar - No text
https://bugs.kde.org/show_bug.cgi?id=395497 --- Comment #1 from Evgenii --- Resetting the toolbar configuration to defaults solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 395360] Keyboard indicator - NumLock is always locked
https://bugs.kde.org/show_bug.cgi?id=395360 --- Comment #2 from Evgenii --- I have just figured out that on my Thinkpad x220, which doesn't have a physical NumLock button, the combination Fn+ScrLk used as a NumLock is generating an output in xev or in showkey when xserver is running just once. On the other laptpop with a physical NumLock the indicator works correctly. So I guess this is not a bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears
https://bugs.kde.org/show_bug.cgi?id=416739 Evgenii Frolov changed: What|Removed |Added CC||frol@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears
https://bugs.kde.org/show_bug.cgi?id=416739 --- Comment #32 from Evgenii Frolov --- (In reply to grego from comment #30) > I started to experience exactly the same issue, hovewer, in my case I found > a way to reproduce it. I commented on that already on Manjaro forum [1] so > here's the copy of my findings: > > >>> > I experienced the same issue today i.e. after a reboot my default panel has > gone and I could not add it back nor any other panel via the context menu, > the desktop wallpaper has reset to the default and my custom key bindings > for the default panel have been gone equally. > > I think I identified it to be related to my dual screen setup. My Lenovo > L570 has a UHD 4K display connected via a mini-DP to DP cable. As I used to > dual boot with Windows 10 I had the laptop lid open during boot and closed > it when the login screen came on. This resulted in a cloned display on both > the laptop and the 4K screen with the same low resolution of the laptop > screen. After logging in the resolution gets adjusted to 4K and scaling of > 150% is applied. > > Today, however, I restarted from Windows 10 with the lid closed and the boot > continued only on the 4K screen. When KDE login screen came up it was in the > native 4K resolution without any scaling applied and after logging in my > desktop was reset, the default panel gone etc. The same remained after > logging out and in again, rebooting and even clearing cache, config files > and applying other reset actions I was able to find. Resetting the theme to > defaults helped bring the default panel back but it didn't persist the log > out/in nor reboot cycle. Very frustrating. > > Finally, I booted up with the laptop lid open and… bang! my panel was there > back again. I repeated the same procedure a few times with the same result: > > - **reboot with the lid open** and the laptop screen on during the boot and > my **desktop and panels persist** > - **reboot with the lid closed** and the laptop screen off during the boot > and my **desktop panels and wallpaper are gone**. > > Looks like connected to screen setup detected by KDE. > > >>> > > [1]: > https://forum.manjaro.org/t/manjaro-kde-taskbar-panel-missing-each-time-i- > log-into-account-after-log-off-or-reboot-event/145960/7 I can confirm that I can reproduce the issue with laptop and additional monitor following these steps. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410149] Make & receive call from PC
https://bugs.kde.org/show_bug.cgi?id=410149 Evgenii Pakhomov changed: What|Removed |Added CC||p1hi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408969] New: KDE Plasma with EglStreams on nvidia 430
https://bugs.kde.org/show_bug.cgi?id=408969 Bug ID: 408969 Summary: KDE Plasma with EglStreams on nvidia 430 Product: plasmashell Version: 5.16.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: z.mozha...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.1) Qt Version: 5.12.4 Frameworks Version: 5.59.0 Operating System: Linux 5.1.12-1-clear x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was closing a window. - Unusual behavior I noticed: I ran kde-wayland-session with eglstreams enabled with gtx 1080 on nvidia dkms 430.26-5. The actual monitor res is 3840x2160, but it got locked somewhere at 800x600 without streching to fullscreen, leaving most of the screen blank, though the cursor does move outside of it and changes shape, probably because of the sddm. nvidia-settings won't launch and display settings in kde settings menu is blank. Kde was installed from arch repositories via plasma, plasma-wayland-session, kde-applications - packages. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f633e017880 (LWP 809))] Thread 18 (Thread 0x7f62ecf4b700 (LWP 2880)): [KCrash Handler] #6 0x7f634292ae94 in wl_proxy_marshal_constructor () at /usr/lib/libwayland-client.so.0 #7 0x7f633dc3b19b in QtWaylandClient::QWaylandWindow::handleUpdate() () at /usr/lib/libQt5WaylandClient.so.5 #8 0x7f633c015d78 in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #9 0x7f6343431142 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/libQt5Gui.so.5 #10 0x7f6344c2682e in () at /usr/lib/libQt5Quick.so.5 #11 0x7f6344c2a6f8 in () at /usr/lib/libQt5Quick.so.5 #12 0x7f6342e4ebf0 in () at /usr/lib/libQt5Core.so.5 #13 0x7f634212c57f in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f6342ae0f13 in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f62d7fff700 (LWP 2865)): #0 0x7f63421323c5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f6342e54cf0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f6342e54de2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f6344c2a4cd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f6344c2a73c in () at /usr/lib/libQt5Quick.so.5 #5 0x7f6342e4ebf0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f634212c57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f6342ae0f13 in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f62ed74c700 (LWP 1023)): #0 0x7f63421323c5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f6342e54cf0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f6342e54de2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f6344c2a4cd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f6344c2a73c in () at /usr/lib/libQt5Quick.so.5 #5 0x7f6342e4ebf0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f634212c57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f6342ae0f13 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f62e700 (LWP 1017)): #0 0x7f6342ad6497 in poll () at /usr/lib/libc.so.6 #1 0x7f63411c17c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f63411c18ae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f634306b27c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f63430123ac in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6342e4d9c5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6342e4ebf0 in () at /usr/lib/libQt5Core.so.5 #7 0x7f634212c57f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6342ae0f13 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f62fcf18700 (LWP 1016)): #0 0x7f6342ad6497 in poll () at /usr/lib/libc.so.6 #1 0x7f63411c17c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f63411c18ae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f634306b27c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f63430123ac in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6342e4d9c5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f62fdade33a in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7f6342e4ebf0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f634212c57f in start_thread () at /
[plasmashell] [Bug 393626] New: Plasma crashes randomly during coding/browsing
https://bugs.kde.org/show_bug.cgi?id=393626 Bug ID: 393626 Summary: Plasma crashes randomly during coding/browsing Product: plasmashell Version: 5.12.4 Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: zheltonozhs...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.4) Qt Version: 5.10.1 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-3-amd64 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: Wring code in CLion and switching to browser (firefox) by Alt-tab. The screen gets black seemingly without connection to what I am doing. - Custom settings of the application: The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff3ad14c6c0 (LWP 1431))] Thread 15 (Thread 0x7ff2b27fc700 (LWP 2131)): #0 0x7ff3a5f7a4ec in futex_wait_cancelable (private=, expected=0, futex_word=0x555a548a7400) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x555a548a73b0, cond=0x555a548a73d8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x555a548a73d8, mutex=0x555a548a73b0) at pthread_cond_wait.c:655 #3 0x7ff3a6dbdfbb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x555a548a73b0) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=, mutex=0x555a5625b9b0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7ff2eb51d99b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x555a53cfb3b0, th=) at ./src/weaver.cpp:594 #6 0x7ff2eb51e745 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x555a53cfb3b0, th=, th@entry=0x7ff2b8004db0, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ./src/weaver.cpp:554 #7 0x7ff2eb522818 in ThreadWeaver::WorkingHardState::applyForWork (this=0x555a56051d50, th=0x7ff2b8004db0, wasBusy=) at ./src/workinghardstate.cpp:66 #8 0x7ff2eb51d8fd in ThreadWeaver::Weaver::applyForWork (this=, th=0x7ff2b8004db0, wasBusy=) at ./src/weaver.cpp:568 #9 0x7ff2eb522872 in ThreadWeaver::WorkingHardState::applyForWork (this=0x555a56051d50, th=0x7ff2b8004db0, wasBusy=) at ./src/workinghardstate.cpp:73 #10 0x7ff2eb51d8fd in ThreadWeaver::Weaver::applyForWork (this=, th=0x7ff2b8004db0, wasBusy=) at ./src/weaver.cpp:568 #11 0x7ff2eb5206db in ThreadWeaver::Thread::run (this=0x7ff2b8004db0) at ./src/thread.cpp:103 #12 0x7ff3a6dbcb4f in QThreadPrivate::start (arg=0x7ff2b8004db0) at thread/qthread_unix.cpp:376 #13 0x7ff3a5f745aa in start_thread (arg=0x7ff2b27fc700) at pthread_create.c:463 #14 0x7ff3a66c4cbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7ff2b2ffd700 (LWP 2130)): #0 0x7ff3a5f7a4ec in futex_wait_cancelable (private=, expected=0, futex_word=0x555a548a7400) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x555a548a73b0, cond=0x555a548a73d8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x555a548a73d8, mutex=0x555a548a73b0) at pthread_cond_wait.c:655 #3 0x7ff3a6dbdfbb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x555a548a73b0) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=, mutex=0x555a5625b9b0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7ff2eb51d99b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x555a53cfb3b0, th=) at ./src/weaver.cpp:594 #6 0x7ff2eb51e745 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x555a53cfb3b0, th=, th@entry=0x555a562bafd0, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ./src/weaver.cpp:554 #7 0x7ff2eb522818 in ThreadWeaver::WorkingHardState::applyForWork (this=0x555a56051d50, th=0x555a562bafd0, wasBusy=) at ./src/workinghardstate.cpp:66 #8 0x7ff2eb51d8fd in ThreadWeaver::Weaver::applyForWork (this=, th=0x555a562bafd0, wasBusy=) at ./src/weaver.cpp:568 #9 0x7ff2eb522872 in ThreadWeaver::WorkingHardState::applyForWork (this=0x555a56051d50, th=0x555a562bafd0, wasBusy=) at ./src/workinghardstate.cpp:73 #10 0x7ff2eb51d8fd in ThreadWeaver::Weaver::applyForWork (this=, th=0x555a562bafd0, wasBusy=) at ./src/weaver.cpp:568 #11 0x7ff2eb5206db in ThreadWeaver::Thr
