[kscreenlocker] [Bug 372459] New: screen locker uses layout of the last active window instead of default layout with "Application" switching policy
https://bugs.kde.org/show_bug.cgi?id=372459 Bug ID: 372459 Summary: screen locker uses layout of the last active window instead of default layout with "Application" switching policy Product: kscreenlocker Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sho...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- 1. Go to the Hardware, Input Devices settings, to the layout tab and choose Application switching policy. Also set your first layout to US and your second layout to RU 2. Open some application and switch to RU layout 3. Lock your screen and see the current locale. It will be RU, but should be US. Having password in Latin character set and entering password to unlock screen always requires you too look at the current layout because else you could enter something totally different. PS. Switching policy "Windows" works fine KDE Plasma version: 5.8.3 KDE Frameworks version: 5.27.0 Qt Version: 5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370220] No keyboard layout indicator on lock-screen after updating plasma to 5.8
https://bugs.kde.org/show_bug.cgi?id=370220 Dmitry changed: What|Removed |Added CC||sho...@gmail.com --- Comment #4 from Dmitry --- Somehow it was easier to find this bug, than to see the locale :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454616] On Wayland, cursor never changes when hovering over anything drawn by Plasma
https://bugs.kde.org/show_bug.cgi?id=454616 Dmitry changed: What|Removed |Added CC||nrn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 350521] [RFE] [OpenVPN] kdeplasma-applets-plasma-nm does not support OTP Tokens for OpenVPN connections
https://bugs.kde.org/show_bug.cgi?id=350521 Dmitry changed: What|Removed |Added CC||nrn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455341] [plasma 5.25 / latte v0.10.x] moving an application makes it unclickable
https://bugs.kde.org/show_bug.cgi?id=455341 Dmitry changed: What|Removed |Added CC||kuteyni...@gmail.com --- Comment #8 from Dmitry --- Faced this issue today in Plasma 5.25.5-3 with Latte-Dock 0.10.8-1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459797] New: Layer blocker does not work for Ctrl+V
https://bugs.kde.org/show_bug.cgi?id=459797 Bug ID: 459797 Summary: Layer blocker does not work for Ctrl+V Classification: Applications Product: krita Version: 5.1.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: zalimann...@mail.ru Target Milestone: --- SUMMARY When inserting an object on a blocked layer, the insertion is successful STEPS TO REPRODUCE 1. Create the first layer. 2. Block the first layer. 3. Create a second layer. 4. Insert the object on the second layer. For example, a line. 5. Select this object and press Ctrl+X. 6. Select the first layer. 7. Press Ctrl+V. OBSERVED RESULT The object was successfully inserted on the blocked layer EXPECTED RESULT Nothing happened SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.11-zen1-1-zen (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 468945] New: When open a playlist file (.m3u) outside of the program, the player opens without the contents of the playlist.
https://bugs.kde.org/show_bug.cgi?id=468945 Bug ID: 468945 Summary: When open a playlist file (.m3u) outside of the program, the player opens without the contents of the playlist. Classification: Applications Product: Haruna Version: 0.10.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: dmitry.leb...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Save the playlist (for example, as a file named playlist.m3u) 2. Close the Haruna video player 3. In the file manager, open the playlist file with Haruna video player OBSERVED RESULT Haruna video player opened, but playlist is empty EXPECTED RESULT Haruna video player opened with the contents of the playlist SOFTWARE/OS VERSIONS Linux: Linux Mint 21.1 Cinnamon Cinnamon Version: 5.6.8 Repository: Flathub Flatpak Version: 1.12.7 ADDITIONAL INFORMATION At first I thought that the program lacked access rights to the folder where the playlist and video files are located. However, there is nothing wrong with that. Inside the program, the playlist file is opened, as it should be, in any way, whether via the "open file" (ctrl+o) or "open playlist" buttons, or by simply dragging the file into the program window. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 469165] New: IPv6 routes with metric 0 are silently dropped
https://bugs.kde.org/show_bug.cgi?id=469165 Bug ID: 469165 Summary: IPv6 routes with metric 0 are silently dropped Classification: Frameworks and Libraries Product: frameworks-networkmanager-qt Version: 5.102.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dmitriyval...@gmail.com CC: lamar...@kde.org, lukas.ti...@merlin.cz Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Add IPv6 route with metric 0 to nm-connection (i.e. via text editor) 2. Open the connection in plasma-nm 3. Observe no such route displayed 4. Close the window and get warned about changes OBSERVED RESULT Route is dropped from nm-connection EXPECTED RESULT Route is not silently lost SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.x (available in About System) KDE Plasma Version: 5.x KDE Frameworks Version: 5.x Qt Version: 5.x ADDITIONAL INFORMATION Cause: https://invent.kde.org/frameworks/networkmanager-qt/-/blob/master/src/settings/ipv6setting.cpp#L454 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460551] New: The corner is highlighted when it shouldn't
https://bugs.kde.org/show_bug.cgi?id=460551 Bug ID: 460551 Summary: The corner is highlighted when it shouldn't Classification: Applications Product: systemsettings Version: 5.26.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: zalimann...@mail.ru Target Milestone: --- Created attachment 152909 --> https://bugs.kde.org/attachment.cgi?id=152909&action=edit The corner is highlighted when it shouldn't SUMMARY If the option "Changing the desktop when moving the mouse over the edge of the screen" is in the "Always" mode, the edges of the screen are always highlighted when the mouse approaches. Even if there is only one desktop and the function for the edge of the screen is not assigned. This happens only for corners STEPS TO REPRODUCE Set the parameters as in the screenshot OBSERVED RESULT The corners are highlighted EXPECTED RESULT Nothing happens SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.1-zen2-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460788] New: The restriction of frequently used layouts does not work
https://bugs.kde.org/show_bug.cgi?id=460788 Bug ID: 460788 Summary: The restriction of frequently used layouts does not work Classification: Applications Product: systemsettings Version: 5.26.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: zalimann...@mail.ru Target Milestone: --- SUMMARY I had 2 layouts: English and Russian. Now I have added my custom ones for my Ergodox, now I have 4 layouts. I want the new switch to work by keyboard shortcut and it works. But on a regular keyboard, only 2 main ones are needed. Setting the limit to 2 or 3 has no effect. STEPS TO REPRODUCE 1. Add more than 2 layouts to the desktop environment 2. Set a limit for the number of main layouts OBSERVED RESULT Nothing EXPECTED RESULT The restriction was set SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 282297] support for spice protocol
https://bugs.kde.org/show_bug.cgi?id=282297 Dmitry changed: What|Removed |Added CC||nrn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 486277] Artifacts systemmonitor
https://bugs.kde.org/show_bug.cgi?id=486277 --- Comment #2 from Dmitry --- (In reply to Arjen Hiemstra from comment #1) > This is a GPU driver bug and you should report it to your GPU driver's > author. I thought the problem was only observed in the system monitor. It is he who is to blame, not the driver. Let me add that there are no such or similar problems anywhere else. But I understand you, I will solve the problem through the driver. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 486277] New: Artifacts systemmonitor
https://bugs.kde.org/show_bug.cgi?id=486277 Bug ID: 486277 Summary: Artifacts systemmonitor Classification: Applications Product: plasma-systemmonitor Version: 6.0.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: knyazev...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 168988 --> https://bugs.kde.org/attachment.cgi?id=168988&action=edit Artifacts Artifacts appear almost immediately after startup, sometimes after startup the system freezes completely -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 445866] New: No JP2 and WEBP support
https://bugs.kde.org/show_bug.cgi?id=445866 Bug ID: 445866 Summary: No JP2 and WEBP support Product: gwenview Version: 21.08.3 Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: dmitry.ashka...@gmail.com Target Milestone: --- SUMMARY I was really surprised that snap packet of gwenview does not support WEBP and JP2 at all. It only supports JPG. STEPS TO REPRODUCE 1. Install gwenview from snap 2. Try to open jp2 or webp image OBSERVED RESULT Format is not supported EXPECTED RESULT Image is opened, e.g. in openSuSE 15.3 gwenview rpm supports both formats. SOFTWARE/OS VERSIONS Linux: snap in Ubuntu 21.10 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453839] New: File thumbnails not showing on mounted NTFS drive on SSD
https://bugs.kde.org/show_bug.cgi?id=453839 Bug ID: 453839 Summary: File thumbnails not showing on mounted NTFS drive on SSD Product: dolphin Version: 22.04.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: doctor.wot...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. I open a directory on the NTFS mounted partition of my SSD with graphics and other files. 2. At the same time, the option to show thumbnails is enabled in the Dolphin settings. OBSERVED RESULT Thumbnails in this case do not appear... EXPECTED RESULT I expect to see thumbnails of these files. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I noticed this problem recently, although about two months ago it was all right. Another thing to say is that in Gwenwiew, thumbnails are displayed normally in this case... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452559] New: Cannot delete Global Menu widget from the dock
https://bugs.kde.org/show_bug.cgi?id=452559 Bug ID: 452559 Summary: Cannot delete Global Menu widget from the dock Product: lattedock Version: 0.10.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: kuteyni...@gmail.com Target Milestone: --- SUMMARY Global Menu widget cannot be removed. Due to the fact that Latte dock itself and it's settings don't have any global menus, the menu widget becomes invisible when I start editing the dock. To remove the widget I need to click on it, but it's impossible because it's hidden. STEPS TO REPRODUCE 1. Add Global Menu widget to Latte dock 2. Edit the dock 3. Global Menu becomes hidden and it's impossible to locate it. Thus, it cannot be removed. OBSERVED RESULT Outside of the editing mode, right clicking on the Global Menu widget doesn't bring option to remove it. At the same time, editing Latte Dock doesn't help, because this widget becomes hidden during editing. EXPECTED RESULT I need some way to remove the Global Menu widget. SOFTWARE/OS VERSIONS Linux: EndeavourOS, X11 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452559] Cannot delete Global Menu widget from the dock
https://bugs.kde.org/show_bug.cgi?id=452559 --- Comment #2 from Dmitry --- (In reply to Michail Vourlakos from comment #1) > This is problem of Global menu not Latte... You could try to have an > application open that provides a menu in order to be able to remove it. This workaround doesn't help. Yes, Konsole, for example, supports Global Menu. When I switch to Konsole, Global Menu becomes visible. Then I right click on it. A context menu appears, but it has no option to remove the widget from the dock. The only option is to "Edit Dock..." but when I choose it, the editor appears which doesn't support Global Menu, so the menu becomes hidden again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452559] Cannot delete Global Menu widget from the dock
https://bugs.kde.org/show_bug.cgi?id=452559 --- Comment #4 from Dmitry --- (In reply to Michail Vourlakos from comment #3) > After Edit Dock, choose Rearrange and configure your widgets, it should give > you the minimum length at global menu in order to remove it Thanks, it helped. The solution wasn't obvious, though. By the way, after removing the Global Menu widget I need to restart Konsole for changes to take effect, otherwise it keeps staying without any menu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452559] Cannot delete Global Menu widget from the dock
https://bugs.kde.org/show_bug.cgi?id=452559 --- Comment #5 from Dmitry --- In my opinion, it would be great just to have a "Remove" option in the context menu after right-clicking on the widget. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 453157] New: Corrupted fonts in Latte Dock settings when scrolling
https://bugs.kde.org/show_bug.cgi?id=453157 Bug ID: 453157 Summary: Corrupted fonts in Latte Dock settings when scrolling Product: lattedock Version: 0.10.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: kuteyni...@gmail.com Target Milestone: --- Created attachment 148438 --> https://bugs.kde.org/attachment.cgi?id=148438&action=edit Latte Dock settings with distorted letters SUMMARY Scrolling the content of the settings window of Latte Dock corrupts the text display. It happens on some of scrolling positions (on others it becomes normal again). If I stop scrolling at the moment when the letters are uneven, they keep staying distorted. STEPS TO REPRODUCE 1. Right click on Latte Dock -> Edit dock 2. Slowly scroll the content of the settings window 3. You will see fonts becoming corrupted at some scrolling positions. OBSERVED RESULT Letters look distorted. EXPECTED RESULT Smooth scrolling. Or, at least, the fonts should stabilize after the scrolling ends. SOFTWARE/OS VERSIONS Linux: EndeavourOS (Arch) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Graphics Platform: X11 Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 453158] New: Customization of intensity of the highlight effect on mouse hover
https://bugs.kde.org/show_bug.cgi?id=453158 Bug ID: 453158 Summary: Customization of intensity of the highlight effect on mouse hover Product: lattedock Version: 0.10.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: kuteyni...@gmail.com Target Milestone: --- SUMMARY Latte Dock provides comprehensive configuration abilities, but only one setting I haven't found: It would be great to have ability to customize the intensity of the highlight effect on mouse hover over the icons in the dock. SOFTWARE/OS VERSIONS Linux: EndeavourOS (Arch) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Graphics Platform: X11 Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 457746] The deleted file is detected as an album with one song.
https://bugs.kde.org/show_bug.cgi?id=457746 --- Comment #2 from Dmitry --- (In reply to Nate Graham from comment #1) > I have a few questions: > 1. what does `baloosearch Helena` in a terminal window show? > 2. If you're using the default "fast native file indexer" setting in the > settings window, can you try the "filesystem indexer" and then refresh the > music collection from the hamburger menu and see if that helps? 1. I entered this line. I deleted the Steam folder from the results, it occupied 50+ lines. $ baloosearch Helena /home/zalimannard/.wine/system.reg /home/zalimannard/Music/Eurobeat/SEB Vol. 041 [1994]/05. Helena - With You.mp3 /home/zalimannard/.cache/yay/completion.cache /home/zalimannard/.cache/vlc/art/artistalbum/Helena /home/zalimannard/.config/chromium/ZxcvbnData/1/female_names.txt /home/zalimannard/.oh-my-zsh/plugins/emoji/emoji-char-definitions.zsh /home/zalimannard/.oh-my-zsh/plugins/emoji/emoji-data.txt /home/zalimannard/.local/share/TelegramDesktop/tdata/dictionaries/en_US/en_US.dic /home/zalimannard/Music/Eurobeat/SEB Vol. 024 [1992]/02. Helena - Just an Illusion.mp3 Maybe you will need it for the deleted file as well: $ baloosearch Silver /home/zalimannard/.cache/vlc/art/artistalbum/Silver /home/zalimannard/Music/Eurobeat/SEB Vol. 043 [1994] /home/zalimannard/.local/opt/tor-browser/app/Browser/TorBrowser/Data/Tor/cached-microdesc-consensus /home/zalimannard/.cache/yay/completion.cache /home/zalimannard/.config/chromium/ZxcvbnData/1/english_wikipedia.txt /home/zalimannard/.config/chromium/ZxcvbnData/1/passwords.txt /home/zalimannard/.config/chromium/ZxcvbnData/1/surnames.txt /home/zalimannard/.config/chromium/ZxcvbnData/1/us_tv_and_film.txt /home/zalimannard/.arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/3.0.4-gcc10.3-1757bed/share/man/man1/xtensa-lx106-elf-g++.1 /home/zalimannard/.arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/3.0.4-gcc10.3-1757bed/share/man/man1/xtensa-lx106-elf-gcc.1 /home/zalimannard/.arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/3.0.4-gcc10.3-1757bed/share/info/gcc.info /home/zalimannard/.oh-my-zsh/plugins/fzf/README.md /home/zalimannard/.oh-my-zsh/plugins/ag/README.md /home/zalimannard/.cache/yay/proton-ge-custom-bin/changelog.md /home/zalimannard/.local/share/TelegramDesktop/tdata/dictionaries/en_US/en_US.dic /home/zalimannard/.config/falkon/profiles/default/adblock/easylist.txt /home/zalimannard/.cache/yay/android-ndk/src/android-ndk-r25/toolchains/llvm/prebuilt/linux-x86_64/python3/lib/python3.9/site-packages/pip/_vendor/certifi/cacert.pem /home/zalimannard/Music/Eurobeat/SEB Vol. 044 [1994]/03. Silver - On My Own.mp3 2. Yes, it really works. That file disappeared from the list. But another problem appears: to update the list, you need to restart Elisa, because it says "Nothing found". After restarting, all files are displayed correctly. After returning to the "fast native file indexer", the problem from the bug report returns. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 457746] The deleted file is detected as an album with one song.
https://bugs.kde.org/show_bug.cgi?id=457746 --- Comment #3 from Dmitry --- Created attachment 151275 --> https://bugs.kde.org/attachment.cgi?id=151275&action=edit Properties appeared out of nowhere -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 457746] The deleted file is detected as an album with one song.
https://bugs.kde.org/show_bug.cgi?id=457746 --- Comment #4 from Dmitry --- I found something else Initially, the folder was normal, but in the ~/Music folder it had properties, as if it were a music file. Attached a screenshot to the report to show what I mean. The file was opened only through Elisa. After I renamed the folder, the properties of the music file disappeared. Then I returned the old name and everything remained correct. No additional album appears. In the output of `baloosearch Helena`, the mention of this folder is also missing. Now this problem is no longer there, but clearly something was wrong. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 448068] Moving the seek bar for a paused track does not update the current play time
https://bugs.kde.org/show_bug.cgi?id=448068 Dmitry changed: What|Removed |Added CC||zalimann...@mail.ru --- Comment #5 from Dmitry --- (In reply to Jack Hill from comment #4) > Using 22.04.2, I also can't reproduce it any more. I switched to Fedora a > few days ago, so maybe the bug isn't present on Fedora (36). Yes, most likely, the bug disappeared due to the transition to Fedora. On Archlinux, the problem is still relevant -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 448068] Moving the seek bar for a paused track does not update the current play time
https://bugs.kde.org/show_bug.cgi?id=448068 --- Comment #9 from Dmitry --- (In reply to Jack Hill from comment #8) No, I definitely use 5.15.5 on Archlinux -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442390] New: Rendered video in Webm looks like crap
https://bugs.kde.org/show_bug.cgi?id=442390 Bug ID: 442390 Summary: Rendered video in Webm looks like crap Product: kdenlive Version: 21.08.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: dkis...@gmail.com Target Milestone: --- SUMMARY render in webm looks like 144p STEPS TO REPRODUCE 1. select video rendering to webm 2. set render quality to maximum 3. start render OBSERVED RESULT rendered video looks like crap EXPECTED RESULT rendered video looks not so bad as render in MP4 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445315] New: Plasma crashed after exiting standby
https://bugs.kde.org/show_bug.cgi?id=445315 Bug ID: 445315 Summary: Plasma crashed after exiting standby Product: plasmashell Version: 5.23.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: nedimo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.23.3) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.11.0-40-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.3 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Plasma crashed after exiting standby. 2 monitors are connected, some windows have moved from the second screen to the first The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 3044] [New LWP 3135] [New LWP 3259] [New LWP 3384] [New LWP 3385] [New LWP 3387] [New LWP 3405] [New LWP 3408] [New LWP 5958] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f54519ebaff in __GI___poll (fds=0x7ffc16262fb8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f544db409c0 (LWP 3025))] Thread 10 (Thread 0x7f54231ee700 (LWP 5958)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55a8990a9d60) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a8990a9d10, cond=0x55a8990a9d38) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55a8990a9d38, mutex=0x55a8990a9d10) at pthread_cond_wait.c:638 #3 0x7f5451d805cb in QWaitConditionPrivate::wait (deadline=..., this=0x55a8990a9d10) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=this@entry=0x55a8984b1598, mutex=mutex@entry=0x55a8984b1590, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f54539e9c24 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x55a8984b1588) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x55a8984b14f0) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7f54539ea099 in QSGRenderThread::run (this=0x55a8984b14f0) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7f5451d7a45c in QThreadPrivate::start (arg=0x55a8984b14f0) at thread/qthread_unix.cpp:329 #9 0x7f5450cc9609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f54519f8293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f53f220e700 (LWP 3408)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55a898133590) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a898133540, cond=0x55a898133568) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55a898133568, mutex=0x55a898133540) at pthread_cond_wait.c:638 #3 0x7f5451d805cb in QWaitConditionPrivate::wait (deadline=..., this=0x55a898133540) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=this@entry=0x55a897f51d98, mutex=mutex@entry=0x55a897f51d90, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f54539e9c24 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x55a897f51d88) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x55a897f51cf0) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7f54539ea099 in QSGRenderThread::run (this=0x55a897f51cf0) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7f5451d7a45c in QThreadPrivate::start (arg=0x55a897f51cf0) at thread/qthread_unix.cpp:329 #9 0x7f5450cc9609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f54519f8293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f54109e9700 (LWP 3405)): #0 0x7f54519ebaff in __GI___poll (fds=0x7f53ec0071b0, nfds=1, timeout=2143159) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f545029736e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f54502974a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5451fbb61b in QEventDispatcherGlib::processEvents (this=0x7f53ec045210, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5451f5f8ab in QEventLoop::exec (this=this@entry=0x7f54109e8ba0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f5451d792c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f542036b07c in KCupsConnection::run() () from /usr/lib/x86_6
[Elisa] [Bug 457746] New: The deleted file is detected as an album with one song.
https://bugs.kde.org/show_bug.cgi?id=457746 Bug ID: 457746 Summary: The deleted file is detected as an album with one song. Product: Elisa Version: 22.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: baloo Assignee: matthieu_gall...@yahoo.fr Reporter: zalimann...@mail.ru Target Milestone: --- Created attachment 151242 --> https://bugs.kde.org/attachment.cgi?id=151242&action=edit I show that the file has not disappeared SUMMARY *** I do not know what led to the error. After deleting the song, it did not disappear in Elisa. If I click on "Show Location", then it will point to another folder. Not the one where this song was. I am sure that this file no longer exists. Restarting and updating the music list does not help. This song is not playing and I do not know how to remove it from here. This has never happened before, so I don't know how to reproduce the error *** STEPS TO REPRODUCE 1. Delete a file from your computer ＼(〇_ｏ)／ 2. Look at the list of albums. The song will be there OBSERVED RESULT The file was deleted from the computer, but remained in Elisa as an album and is not deleted EXPECTED RESULT The file was deleted and after reindexing it is not visible SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.16-zen1-1-zen (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 414771] "skip backwards" action always goes to the previous song, never to the beginning of the current song
https://bugs.kde.org/show_bug.cgi?id=414771 Dmitry changed: What|Removed |Added CC||zalimann...@mail.ru --- Comment #4 from Dmitry --- It seems to me that such a function is unnecessary. The button means "Previous Track", not "Previous track, but if more than 5 seconds have passed, then repeat the song". If you need to go back to the beginning of the track after it ends, then there is a "Repeat playback" button. The current function is misleading. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 Dmitry changed: What|Removed |Added CC||nrn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 427004] New: Problem with dual displays
https://bugs.kde.org/show_bug.cgi?id=427004 Bug ID: 427004 Summary: Problem with dual displays Product: frameworks-plasma Version: 5.20.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: zerg...@mail.ru CC: plasma-b...@kde.org Target Milestone: --- Created attachment 131952 --> https://bugs.kde.org/attachment.cgi?id=131952&action=edit problem with dual displays SUMMARY I apologize if I wrote in the wrong place. I have a strange problem with displaying desktops. They are reversed. In this case, the resolution of the screens is in order STEPS TO REPRODUCE 1. install arch 2. install KDE 3. Reboot OBSERVED RESULT Reinstalled the system. Railing problem on newly installed. If you change the monitor parameters, then the gap goes away. After reboot, come back EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.8.10-arch1-1 GNU/Linux / KDE 5.20 and 5.19 try -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376683] System suspends from time to time when works with laptop lid closed and external display connected
https://bugs.kde.org/show_bug.cgi?id=376683 Dmitry changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #8 from Dmitry --- It is not reproducible for me anymore (Plasma 5.18.5) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442645] Plasma freezes on receiving call from KDE Connect
https://bugs.kde.org/show_bug.cgi?id=442645 Dmitry changed: What|Removed |Added CC||nrn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 472200] New: Password not saved for VPN + OpenConnect
https://bugs.kde.org/show_bug.cgi?id=472200 Bug ID: 472200 Summary: Password not saved for VPN + OpenConnect Classification: Plasma Product: plasma-nm Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dosi...@yandex.ru Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open System Settings 2. Go to Connections 3. Press Plus sign and pick Cisco AnyConnnect Compatible VPN(open connect) 4. Fill Gateway and press save and close settings windoe 5. Open Networks, find the connection, press Connect button 6. Check Store passwords checkbox 7. Fill username and password and press Login button 8. Open Networks and press Disconnect for the connection 9. Open Networks and press Connect for the connection OBSERVED RESULT ask password EXPECTED RESULT connection works automatically SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-10-amd64 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION openconnect/stable,now 9.01-3 amd64 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438496] Keyboard layout switching shortcut stops working after a period of inactivity
https://bugs.kde.org/show_bug.cgi?id=438496 Dmitry changed: What|Removed |Added CC||dmitry.a.kuzme...@gmail.com --- Comment #22 from Dmitry --- ArchLinux, Plasma 5.26.4. Main shortcut: Caps Lock The same issue starting from the middle of this year. Just one difference is that in my case layout switching stops to work when the indicator disappears. Switching the policy between window/application level helps. Please let me know how I can help to investigate it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] On X11, widgets still inappropriately move after login
https://bugs.kde.org/show_bug.cgi?id=458038 Dmitry changed: What|Removed |Added Ever confirmed|1 |0 Status|CONFIRMED |REPORTED CC||d.motre...@mail.ru --- Comment #16 from Dmitry --- I have an issue with desktop with right side panel. Widgets change position during panel init, they move left. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] On X11, widgets still inappropriately move after login
https://bugs.kde.org/show_bug.cgi?id=458038 --- Comment #17 from Dmitry --- https://pic.li/9rgd(In reply to Dmitry from comment #16) > I have an issue with desktop with right side panel. Widgets change position > during panel init, they move left. screenshot https://pic.li/9rgd -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 463286] New: Add "kdm" category to bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=463286 Bug ID: 463286 Summary: Add "kdm" category to bugs.kde.org Classification: Websites Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: product/component changes Assignee: sysad...@kde.org Reporter: kuteyni...@gmail.com CC: christo...@krop.fr Target Milestone: --- I wanted to submit a bug of kdm (KDE display manager) on this website, but couldn't find "kdm" product category -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 463286] Add "kdm" category to bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=463286 --- Comment #2 from Dmitry --- Haha, that was my fault :P I woke up and realized that things changed a lot since my last time on KDE: I was surprised that there is no KDM anymore and it's already SDDM under the hood :D -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460788] The restriction of frequently used layouts does not work
https://bugs.kde.org/show_bug.cgi?id=460788 Dmitry changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Dmitry --- When I press Alt+Shift, the layouts change in this order: us -> ru -> custom us -> custom ru -> us -> ru -> ... It seems to me that limiting the main layouts to 2 means the following switching ring: us -> ru -> us -> ru -> us -> ru -> ... custom layouts should not be affected, because they have numbers 3 and 4. But this does not happen, the layouts are switched as in the first example. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460788] The restriction of frequently used layouts does not work
https://bugs.kde.org/show_bug.cgi?id=460788 --- Comment #3 from Dmitry --- Created attachment 153092 --> https://bugs.kde.org/attachment.cgi?id=153092&action=edit My current layout suttings I think that graying additionally means that these layouts should not be available by Alt+Shift. But they are in the switching ring -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 420535] after blocking the computer, it hangs in an attempt to log in after such an action as "switch user"
https://bugs.kde.org/show_bug.cgi?id=420535 Dmitry changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #7 from Dmitry --- I can confirm that today the situation is still the same, I'm using Plasma 5.26.2 on openSUSE Tumbleweed... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 420535] after blocking the computer, it hangs in an attempt to log in after such an action as "switch user"
https://bugs.kde.org/show_bug.cgi?id=420535 Dmitry changed: What|Removed |Added Platform|Manjaro |OpenSUSE -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 420535] after blocking the computer, it hangs in an attempt to log in after such an action as "switch user"
https://bugs.kde.org/show_bug.cgi?id=420535 --- Comment #9 from Dmitry --- One person has the same problem https://bugs.kde.org/show_bug.cgi?id=426194 and he has already filed a bug report https://github.com/sddm/sddm/issues/1609 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464373] Desktop widgets placed next to panel move further and further away each login
https://bugs.kde.org/show_bug.cgi?id=464373 Dmitry changed: What|Removed |Added CC||d.motre...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431581] New: Had very much lag!
https://bugs.kde.org/show_bug.cgi?id=431581 Bug ID: 431581 Summary: Had very much lag! Product: krita Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: thelom...@gmail.com Target Milestone: --- Krita very much lags it is not possible to draw, the brush twitches, freezes, the computer is quite powerful, in other heavy programs it goes smoothly, and in Krita everything lags -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422780] KDE Plasma crash on 5.19 after trying to change widgets
https://bugs.kde.org/show_bug.cgi?id=422780 --- Comment #3 from Dmitry --- I will add more information on the situation today. I have four widgets on my desktop: Clock, Weather, CPU Usage, Network Usage. CPU Usage widget (line chart) does not work correctly, namely, after turning on the PC, only the initial state of the widget is displayed and it is static, but if I only make Log out and then Log in again, this widget starts working properly. I have Operating System: openSUSE Tumbleweed 20200627 KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 Kernel Version: 5.7.5-1-default -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423958] New: error store themes
https://bugs.kde.org/show_bug.cgi?id=423958 Bug ID: 423958 Summary: error store themes Product: systemsettings Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: satanin.dmitry.2...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.5) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.7.6-201.fc32.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 32 (Thirty Two)" -- Information about the crash: - I am installing new themes from store on setting and then crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Параметры системы (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1e1e181f80 (LWP 3961))] Thread 14 (Thread 0x7f1db2f82700 (LWP 4140)): #0 0x7f1e2259cb6f in poll () from /lib64/libc.so.6 #1 0x7f1e208e9ace in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7f1e208e9c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f1e22b06b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f1e22ab991b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f1e22925427 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f1e22926690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f1e21265432 in start_thread () from /lib64/libpthread.so.0 #8 0x7f1e225a79d3 in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f1dbefe6700 (LWP 4134)): #0 0x7f1e2259cb6f in poll () from /lib64/libc.so.6 #1 0x7f1e208e9ace in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7f1e208e9c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f1e22b06b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f1e22ab991b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f1e22925427 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f1e22926690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f1e21265432 in start_thread () from /lib64/libpthread.so.0 #8 0x7f1e225a79d3 in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7f1dcb078700 (LWP 4131)): #0 0x7f1e208e790f in g_source_iter_next () from /lib64/libglib-2.0.so.0 #1 0x7f1e208e8f03 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f1e208e99fb in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #3 0x7f1e208e9c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f1e22b06b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f1e22ab991b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f1e22925427 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f1e22926690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f1e21265432 in start_thread () from /lib64/libpthread.so.0 #9 0x7f1e225a79d3 in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7f1dcbfff700 (LWP 3980)): #0 0x7f1e2126be92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1e093f52ab in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f1e093f4d7b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f1e21265432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f1e225a79d3 in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7f1df4c96700 (LWP 3976)): #0 0x7f1e2126be92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1e093f52ab in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f1e093f4d7b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f1e21265432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f1e225a79d3 in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f1df7fff700 (LWP 3973)): #0 0x7f1e2126be92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1e093f52ab in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f1e093f4d7b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f1e21265432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f1e225a79d3 in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f1dfca94700 (LWP 3972)): #0 0x7f1e2126be92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1e093f52ab in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f1e093f4d7b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f1e212
[kmail2] [Bug 425604] New: kmail crashes when using kvantum theme engine
https://bugs.kde.org/show_bug.cgi?id=425604 Bug ID: 425604 Summary: kmail crashes when using kvantum theme engine Product: kmail2 Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: distsele...@gmail.com Target Milestone: --- Application: kmail (5.15.0 (20.08.0)) Qt Version: 5.14.2 Frameworks Version: 5.73.0 Operating System: Linux 5.7.16-xanmod2 x86_64 Windowing system: X11 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: After upgrading to KDE Apps 20.08 kmail began crashing every time I opened it from tray icon. It successfully starts and sits in a tray unless I open it. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7f4c31e225c6 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x7f4c31de203f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x7f4c31347b62 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4c31e225e4 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f4c30c1aa8b in KMainWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #9 0x7f4c30c64a17 in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #10 0x7f4c31de203f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f4c31347b62 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f4c31dec7b7 in QApplication::setActiveWindow(QWidget*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f4c31dec9cb in QApplicationPrivate::notifyActiveWindowChange(QWindow*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f4c3170ba05 in QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7f4c316e5bfb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7f4c20fd3b6a in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #17 0x7f4c2a8b65fd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f4c2a8b6880 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f4c2a8b690f in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f4c3139d2ff in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f4c313464db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f4c3134e782 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x559d7c9114be in main (argc=, argv=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qcoreapplication.h:116 [Inferior 1 (process 227542) detached] Possible duplicates by query: bug 425532, bug 425508, bug 425334, bug 425209, bug 425205. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 425604] kmail crashes when using kvantum theme engine
https://bugs.kde.org/show_bug.cgi?id=425604 --- Comment #1 from Dmitry --- When I start kmail with QT_STYLE_OVERRIDE=breeze everything is OK. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 425604] kmail crashes when using kvantum theme engine
https://bugs.kde.org/show_bug.cgi?id=425604 Dmitry changed: What|Removed |Added Version|unspecified |5.15.0 Platform|Debian stable |Debian testing -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410800] Device in Bookmark will show docker mount point when docker container opened
https://bugs.kde.org/show_bug.cgi?id=410800 Dmitry changed: What|Removed |Added CC||dima...@gmail.com --- Comment #5 from Dmitry --- Issue for Docker https://github.com/docker/for-linux/issues/1096 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 435770] Crash when loging out
https://bugs.kde.org/show_bug.cgi?id=435770 --- Comment #2 from Dmitry --- Created attachment 138565 --> https://bugs.kde.org/attachment.cgi?id=138565&action=edit New crash information added by DrKonqi krunner (5.19.5) using Qt 5.14.2 - What I was doing when the application crashed: Just pressed CTRL+space. Also, if i am running "krunner" from terminal, this is caues same error. -- Backtrace (Reduced): #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7f8814497864 in __GI_abort () at abort.c:79 #6 0x7f88148caba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f881642dade in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 [...] #10 0x7f8814ec67c5 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 435770] Crash when loging out
https://bugs.kde.org/show_bug.cgi?id=435770 Dmitry changed: What|Removed |Added CC||dimonleono...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 420535] after blocking the computer, it hangs in an attempt to log in after such an action as "switch user"
https://bugs.kde.org/show_bug.cgi?id=420535 Dmitry changed: What|Removed |Added Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 Resolution|UPSTREAM|--- -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 491278] New: Logout UI regressions in 6.1
https://bugs.kde.org/show_bug.cgi?id=491278 Bug ID: 491278 Summary: Logout UI regressions in 6.1 Classification: Plasma Product: Breeze Version: 6.1.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dmitriyval...@gmail.com CC: uhh...@gmail.com Target Milestone: --- SUMMARY Logout UI simplifications made for 478022 made logout options less accessible from Application Dashboard and Lock/Logout plasmoid. STEPS TO REPRODUCE 1. Add Application Dashboard 2. Add Lock/Logout plasmoid 3. Try to enter sleep/hibernation from either OBSERVED RESULT 1. There's no quickly accessible options to sleep or hibernate in Application Dashboard. They are one click further away behind Power/Session submenu. 2. Now for Lock/Logout user is forced to enable separate buttons for all the required options, witch takes a panel space. EXPECTED RESULT As in Plasma 5/6.0, ability to access logout options easier. As per the commit title, add options that would invoke the logout screen without a specific option and add this option to all the relevant plasmoids. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 6.1.x ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433705] New: bad_a
https://bugs.kde.org/show_bug.cgi?id=433705 Bug ID: 433705 Summary: bad_a Product: plasmashell Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: satanin.dmitry.2...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.14.2 Frameworks Version: 5.75.0 Operating System: Linux 5.10.18-100.fc32.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 32 (Thirty Two)" -- Information about the crash: - What I was doing when the application crashed: - Custom settings of the application: i have critical hardware errors: on the laptop it seems that the processor's thermal paste has spread and touches the contacts. also I have not established why it sometimes restarts. it is possible that something is malfunctioning due to a certain bend of the case and the motherboard. the system was just started. maybe not all services and daemons had time to start I opened the telegram application through a shortcut on the desktop. I have several telegrams but only one can run. I don't remember which one, maybe the link does not lead anywhere -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa4d2947280 (LWP 2020))] Thread 27 (Thread 0x7fa445c36700 (LWP 2542)): #0 0x7fa4d5d73e92 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa4d6907d9b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7fa485bcade8 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fa485bcedcc in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fa485bca066 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fa485bcee29 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fa485bca066 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7fa485bcc778 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #8 0x7fa4d6902680 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7fa4d5d6d432 in start_thread () at /lib64/libpthread.so.0 #10 0x7fa4d65816d3 in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7fa446437700 (LWP 2541)): #0 0x7fa4d5d73e92 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa4d6907d9b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7fa485bcade8 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fa485bcedcc in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fa485bca066 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fa485bcee29 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fa485bca066 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7fa485bcc778 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #8 0x7fa4d6902680 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7fa4d5d6d432 in start_thread () at /lib64/libpthread.so.0 #10 0x7fa4d65816d3 in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fa446c38700 (LWP 2540)): #0 0x7fa4d5d73e92 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa4d6907d9b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7fa485bcade8 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fa485bcedcc in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fa485bca066 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fa485bcc778 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fa4d6902680 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7fa4d5d6d432 in start_thread () at /lib64/libpthread.so.0 #8 0x7fa4d65816d3 in clone () at /lib64/libc.so.6 Thr
[dolphin] [Bug 407979] New: Keyboard input focus lost after closing terminal panel
https://bugs.kde.org/show_bug.cgi?id=407979 Bug ID: 407979 Summary: Keyboard input focus lost after closing terminal panel Product: dolphin Version: 19.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: dmitry.a.kuzme...@gmail.com Target Milestone: --- SUMMARY After leaving terminal with Ctrl-D or exit commands the input focus isn't set back to the folder view. So not Tab nor Arrow keys allow to navigate. You need to click to the folder view with mouse to continue work with the folder. STEPS TO REPRODUCE 1. Open Dolphin 2. Press F4 to open the terminal panel 3. Type exit or pres Ctrl-D OBSERVED RESULT Pressing Tab, arrow keys, typing file/folder name results to nothing. EXPECTED RESULT Focus should return to the folder view so you can navigate with arrows. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION Dolphin version 19.04.1 (the bug exists in previous versions) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407979] Keyboard input focus lost after closing terminal panel
https://bugs.kde.org/show_bug.cgi?id=407979 Dmitry changed: What|Removed |Added CC||dmitry.a.kuzme...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408661] New: Appmenu plasmoid prevents on-window menu work when hidden
https://bugs.kde.org/show_bug.cgi?id=408661 Bug ID: 408661 Summary: Appmenu plasmoid prevents on-window menu work when hidden Product: plasmashell Version: 5.16.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: dmitriyval...@gmail.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When appmenu plasmoid is added exclusively to an unplugged display, neither menu is accessible nor appmenu plasmoid could be deleted via GUI. Editing ~/.config/plasma-org.kde.plasma.desktop-appletsrc is the only option. This could be crucial for some portable devices like laptops. STEPS TO REPRODUCE 1. Plug in the second display 2. Add appmenu plasmoid e.g. as "Application menu bar" panel to both primary and secondary displays 3. Unplug the display 4. (Optional) reboot/restart DE/computer/forger about the display entirely 5. Delete any existing appmenu plasmoids available from the primary display. 6. Restart Plasma session 7. Launch any application known to work with appmenu OBSERVED RESULT Menu is not accessible at all. EXPECTED RESULT Ideally appmenu is disabled since plasmoids are not loaded. Possibly some explicit setting is avaliable to disable appmenu plasmoids (like pre-5.12) OR to delete all existing instances of an appmenu plasmoid. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (latest 2019.06.13), presumably distro-unrelated KDE Plasma Version: KDE 5.15.*/5.16 from extra -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 Dmitry changed: What|Removed |Added CC||dmitry-kog...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 413211] New: Wired connection default settings are misleading
https://bugs.kde.org/show_bug.cgi?id=413211
Bug ID: 413211
Summary: Wired connection default settings are misleading
Product: plasma-nm
Version: master
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: editor
Assignee: jgrul...@redhat.com
Reporter: dmitriyval...@gmail.com
Target Milestone: ---
SUMMARY
Settings editor applet shows and saves hardcoded default ethernet settings for
connections without negotioation/speed/duplex explicitly saved. It leads to
saving connections with implicit (autonegotiation => auto 1Gb/s Full) as
explicit (no auto negotiation 100Mb/s Half).
STEPS TO REPRODUCE
1. Stop NetworkManager
2. Remove all wired connections in /etc/NetowrkManager/system-connections
(replicates clear distribution installation
3. Start NetowrkManager
4. Ensure you have a wired connections
5. Check connection settings via ethtool
6. Edit anything (e.g. DNS/VPN) in the newly created connection settings
7. Save settings
8. Disconnect and reconnect ethernet (via UI/CLI/physically)
OBSERVED RESULT
Connection become 100 Mb/s Half duplex no auto negotiation
EXPECTED RESULT
Connection stay whatever it was (presumably autonegotiation => auto 1Gb/s Full)
SOFTWARE/OS VERSIONS
Linux: 4.15+ (presumably any)
Distribution: OpenSUSE, Arch, Fedora (presumably any)
KDE Plasma Version: 5.16/5.17 (presumably any)
NetworkManager: 1.18/1.20
Hardware: r8169/e1000e NIC (including qemu and virtualbox) (presumably any)
ADDITIONAL INFORMATION
Bug comes from interpreting {speed: 0, duplex: UnknownDuplex} at
libs/editor/settings/wiredconnectionwidget.cpp:63
(WiredConnectionWidget::loadConfig) as HalfDuplex 100 Mb/s from hardcoded
defaults.
SEVERITY
Note, that ANY change of ANY implicitly created wired connection on ANY stock
system leads to switching from default ethernet settings to rare and unexpected
mode for virtually no reason. This behaviour is obscure and may turn regular
users ot from using Linux/KDE due to slower "Internet"
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-nm] [Bug 413211] Wired connection default settings are misleading
https://bugs.kde.org/show_bug.cgi?id=413211 Dmitry changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #2 from Dmitry --- Proposed fix does not fix the issue itself, just mitigates the most extreme case. Behaviour is still broken due to: 1. Configuration is still changes implicitly: * before editing: NetworkManager does not set ethernet mode * after editing: NetworkManager sets 100 Mb/s FullDuples 2. In some cases (1) leads to UX regression * it makes connection over gigabit link slower * it makes connection over 100 HD link no longer working 3. In some rare cases it leads to faulty condition * in case of (https://bugzilla.kernel.org/show_bug.cgi?id=205067) it's impossible to configure/preserve via GUI a persistently working gigabit connection. The only fix I hae ideas about is implementing this as a separate mode of a connection like it works in XFCE, where not only "Manual" and "Auto" modes are present, but also "Ignored", which essentially is the described above mode. Implementing this fix may require adding come code into networkmanager-qt as plasma-nm uses it to interact with NetworkManager. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 413211] Wired connection default settings are misleading
https://bugs.kde.org/show_bug.cgi?id=413211 --- Comment #4 from Dmitry --- (In reply to Jan Grulich from comment #3) > I just checked nm-connection-editor and they indeed have additional option, > which is "Ignore", but in the code it doesn't make any difference. If the > link negotiation is set to "Ignore" or "Automatic", it sets speed to 0 and > duplex to unknown type, which is the same what we do in plasma-nm. So, my bad, I've made wrong assumptions from networkmanager-qt code. However, the case is when no value is explicitly set in the connection beforehands, plasma-nm will apply UI defaults for speed/dulpex when user saves any other parameter e.g. DNS servers. Described above case is present on the video: https://youtu.be/8UOu76c-fNk Test was performed on a clear Plasma, Arch Linux (latest stable to 2019.10.22 morning) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410331] When I try to save any Krita file as a jpg or Krita file, I keep getting an error message -- 'cannot save / access is denied'
https://bugs.kde.org/show_bug.cgi?id=410331 Dmitry changed: What|Removed |Added CC||dmitry.make...@gmail.com Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #5 from Dmitry --- Hello, new Krita user here, Windows 10 x64. I've also seen this error. And numerous forum posts about this error, and everywhere people suggest it's a permission issue. Well, I'm a system administrator and I'm pretty sure I have enough permissions on my working folders. I've done some testing and (helped by reports that files can't be saved in folders that are in root) found out that Krita can't save a file in D:\test11, but can save in D:\test11\test22, even though folder permissions are the same. Then I've run procmon to see what exactly Krita tries to do. I'm not that great at understanding Windows file API calls, but I've seen this: D:\test11.nKanRR.kraPRIVILEGE NOT HELD and later when successfully saving to D:\test11\test22\test.kra D:\test11\test22.aZmNdf.kra SUCCESS (multiple operations). I believe the issue is Krita's trying to create a temp file not in the folder it's saving to, but in the parent folder, probably because the last slash in the filename (or path) is lost (or replaced with "."). Thus when saving in D:\test11 it tries to create temp file in D:\, and that usually requires additional privileges. BTW, only the temp file name is affected. Later it copies temp file (if it saved succesfully) to the intended file name, and that goes as expected: ReadFileD:\test11\test22.aZmNdf.kra SUCCESS Offset: 0, Length: 101 629, Priority: Normal WriteFile D:\test11\test22\test.kra SUCCESS Offset: 0, Length: 101 629, Priority: Normal (among other things). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412198] New: Plasma crashes when you click the left mouse button on the icon "Classic application menu"
https://bugs.kde.org/show_bug.cgi?id=412198 Bug ID: 412198 Summary: Plasma crashes when you click the left mouse button on the icon "Classic application menu" Product: plasmashell Version: 5.16.2 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: hunk...@yandex.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.2) Qt Version: 5.12.2 Frameworks Version: 5.59.0 Operating System: FreeBSD 12.0-RELEASE-p10 amd64 Distribution (Platform): FreeBSD Ports -- Information about the crash: - What I was doing when the application crashed: Plasma crashes when you click the left mouse button on the icon "Classic application menu" and try to select any category. Parallel launched - firefox, pycharm, okular, fbreader. -- Backtrace: Application: Plasma (plasmashell), signal: Bus error (lldb) process attach --pid 1448 Process 1448 stopped Executable module set to "/usr/local/bin/plasmashell". Architecture set to: x86_64--freebsd12.0. (lldb) set term-width 200 (lldb) thread info thread #1: tid = 100779, 0x000802f5a84a libc.so.7`__sys_nanosleep + 10, name = 'plasmashell' (lldb) bt all * thread #1, name = 'plasmashell' * frame #0: 0x000802f5a84a libc.so.7`__sys_nanosleep + 10 frame #1: 0x00080338017c libthr.so.3`___lldb_unnamed_symbol36$$libthr.so.3 + 44 frame #2: 0x000802ec0e0b libc.so.7`_sleep + 59 frame #3: 0x00080143e51a libKF5Crash.so.5`___lldb_unnamed_symbol6$$libKF5Crash.so.5 + 1450 frame #4: 0x00080143dc2c libKF5Crash.so.5`KCrash::defaultCrashHandler(int) + 1484 frame #5: 0x0008033834b6 libthr.so.3`___lldb_unnamed_symbol101$$libthr.so.3 + 214 frame #6: 0x000803382a22 libthr.so.3`___lldb_unnamed_symbol82$$libthr.so.3 + 322 frame #7: 0x7003 frame #8: 0x000802c72154 libQt5Core.so.5`QMetaObject::activate(QObject*, int, void**) + 36 frame #9: 0x000800dc6d31 libQt5Qml.so.5`___lldb_unnamed_symbol203$$libQt5Qml.so.5 + 1233 frame #10: 0x00080108efab libQt5Qml.so.5`QQmlDelegateModel::_q_itemsChanged(int, int, QVector const&) + 107 frame #11: 0x000801099d81 libQt5Qml.so.5`___lldb_unnamed_symbol6124$$libQt5Qml.so.5 + 2305 frame #12: 0x000801099eba libQt5Qml.so.5`QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) + 122 frame #13: 0x000802c71826 libQt5Core.so.5`QMetaObject::activate(QObject*, int, int, void**) + 1814 frame #14: 0x000802bf5ead libQt5Core.so.5`QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const, QVector const&) + 61 frame #15: 0x00080f944321 libkickerplugin.so`___lldb_unnamed_symbol585$$libkickerplugin.so + 833 frame #16: 0x00080f91b477 libkickerplugin.so`___lldb_unnamed_symbol41$$libkickerplugin.so + 71 frame #17: 0x000800facbd8 libQt5Qml.so.5`QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlContextData*, QFlags) + 1160 frame #18: 0x000800ed2087 libQt5Qml.so.5`QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) + 3415 frame #19: 0x000800ed32e4 libQt5Qml.so.5`QV4::QObjectWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::PropertyKey*) + 452 frame #20: 0x000800f73e2a libQt5Qml.so.5`QV4::Runtime::method_storeProperty(QV4::ExecutionEngine*, QV4::Value const&, int, QV4::Value const) + 234 frame #21: 0x00081e150756 frame #22: 0x000800eed700 libQt5Qml.so.5`___lldb_unnamed_symbol2432$$libQt5Qml.so.5 + 224 frame #23: 0x000800e92d66 libQt5Qml.so.5`QV4::Function::call(QV4::Value const*, QV4::Value const, int, QV4::ExecutionContext const*) + 694 frame #24: 0x00080101a4ba libQt5Qml.so.5`QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) + 570 frame #25: 0x000800fbb9f4 libQt5Qml.so.5`QQmlBoundSignalExpression::evaluate(void**) + 1140 frame #26: 0x000800fbc0de libQt5Qml.so.5`___lldb_unnamed_symbol4291$$libQt5Qml.so.5 + 446 frame #27: 0x000800ee libQt5Qml.so.5`QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) + 686 frame #28: 0x000802c71195 libQt5Core.so.5`QMetaObject::activate(QObject*, int, int, void**) + 133 frame #29: 0x000800b4dfbf libQt5Quick.so.5`___lldb_unnamed_symbol5752$$libQt5Quick.so.5 + 799 frame #30: 0x000800b590b7 libQt5Quick.so.5`QQuickItemView::qt_metacall(QMetaObject::Call, int, void**) + 71 frame #31: 0x000800b68d48 libQt5Quick.so.5`QQuickListView::qt_metacall(QMetaObject::Call, int, void**) + 24 frame #32: 0x000800ed21e2 libQt5Qml.so.5`QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) + 3762 frame #33: 0x000
[kwin] [Bug 405103] New: KWin fails to bring window to foreground
https://bugs.kde.org/show_bug.cgi?id=405103 Bug ID: 405103 Summary: KWin fails to bring window to foreground Product: kwin Version: 5.12.6 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kuteyni...@gmail.com Target Milestone: --- SUMMARY Window switching not working. STEPS TO REPRODUCE 1. Open Konsole, Android Studio, Kate, two Firefox windows, YakYak, Dolphin, Telegram Desktop. 2. Switch between windows using mouse. 3. Sometimes I cannot bring inactive window to foreground. OBSERVED RESULT The activity's button in task panel was clicked, but no window appeared. Only Alt-Tab helps in such situation. EXPECTED RESULT Restore window from background to foreground. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Leap 15.0 KDE Plasma Version: 5.12.6 KDE Frameworks Version: 5.45.0 Qt Version: 5.9.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405103] KWin fails to bring window to foreground
https://bugs.kde.org/show_bug.cgi?id=405103 --- Comment #1 from Dmitry --- I think the problem is in the way how AndroidStudio and KDE interact with each other. Not sure if other apps have such problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405103] KWin fails to bring window to foreground
https://bugs.kde.org/show_bug.cgi?id=405103 --- Comment #3 from Dmitry --- Yes, looks like it is a problem with AndroidStudio working within kwin. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405103] KWin fails to bring window to foreground
https://bugs.kde.org/show_bug.cgi?id=405103 --- Comment #5 from Dmitry --- Created attachment 118902 --> https://bugs.kde.org/attachment.cgi?id=118902&action=edit xprop output for AndroidStudio window Here it is (see the attachment). Also I've found exact steps how to reproduce: just put AndroidStudio into foreground, then click on it's button inside the task manager (window will minimize), and than again click the button to unminimize. You will see AndroidStudio coming out but not into the top-level - other windows will stay on top of it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405103] KWin fails to bring window to foreground
https://bugs.kde.org/show_bug.cgi?id=405103 --- Comment #6 from Dmitry --- Created attachment 118903 --> https://bugs.kde.org/attachment.cgi?id=118903&action=edit xprop root with sleep -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405103] KWin fails to bring window to foreground
https://bugs.kde.org/show_bug.cgi?id=405103 --- Comment #7 from Dmitry --- Also I noticed the similar problem with notifications: When I receive a message notification from WhatsApp Web running inside my Firefox (I keep two windows of Firefox opened), I click on the notification and KDE instead of bringing to foreground one of the Firefox windows (that contains WhatsApp Web) opens another app's window (Telegram). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422780] KDE Plasma crash on 5.19 after trying to change widgets
https://bugs.kde.org/show_bug.cgi?id=422780 Dmitry changed: What|Removed |Added CC||doctor.wot...@gmail.com --- Comment #2 from Dmitry --- My Plasma also crashed after trying to configure Widgets, and Widgets were empty, such as using CPU and Network speed, tried to add other Widgets, such as Disk Usage and Hard Disk Activity, they were empty too, tried to change themes - it didn’t help, it’s on OpenSUSE Tumbleweed with the updated Plasma 5.19. Update: today a system update has arrived, and some Widgets display has started working, but not all styles work correctly, and Plasma also crashes sometimes when trying to configure them ... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422913] New: I can’t assign hotkeys for some applications
https://bugs.kde.org/show_bug.cgi?id=422913 Bug ID: 422913 Summary: I can’t assign hotkeys for some applications Product: systemsettings Version: 5.19.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: doctor.wot...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I have a keyboard with multimedia and some other keys. I wanted to assign them to launch applications such as VLC player and KCalc. And I would also like to be able to launch other applications such as LibreOffice Writer or others with hot keys. STEPS TO REPRODUCE 1. I open the System parameters, Hot keys, then click button Add application, select KCalc, then I click the Add custom shortcut button. I click the button Calculator on the keyboard, the inscription inside the button changes, then I click Apply. 2. In another case, I do the same for the VLС player and the corresponding button on the keyboard. 3. And in another case, I do the same for LibreOffice Writer and the keyboard shortcut Meta+W. OBSERVED RESULT Nothing happens, hot keys in all cases do not start the application. EXPECTED RESULT Hotkeys must launch their applications ... SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSUSE Tumbleweed/5.19.0 (available in About System) KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420535] New: after blocking the computer, it hangs in an attempt to log in after such an action as "switch user"
https://bugs.kde.org/show_bug.cgi?id=420535 Bug ID: 420535 Summary: after blocking the computer, it hangs in an attempt to log in after such an action as "switch user" Product: plasmashell Version: 5.18.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Lock/logout Assignee: plasma-b...@kde.org Reporter: doctor.wot...@gmail.com Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. I press "Meta + L" to lock the screen 2. I click "Switch user" 3. Then I try to unlock the screen, enter the password, press Enter OBSERVED RESULT Regardless of how many users in the system, one or several, can’t log in, the system freezes, only Reset saves EXPECTED RESULT The idea is to log in to the system SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.18.4 (openSUSE Tumbleweed) (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417109] New: KWin crash with Nvidia 435 proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=417109 Bug ID: 417109 Summary: KWin crash with Nvidia 435 proprietary drivers Product: kwin Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: dmitry.s.lisov...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.5) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-29-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: Crash happened after I resumed laptop, previously suspended. - Unusual behavior I noticed: Some UI elements were corrupted (desktop icons labels, system tray icons). - Custom settings of the application: This started to happen after I installed Nvidia 435 proprietary drivers. -- 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 0x7f4b75be9d00 (LWP 1979))] Thread 7 (Thread 0x7f4b5d782700 (LWP 17775)): #0 0x7f4b7a8e42c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x5560f1952a34) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f4b7a8e42c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5560f19529e0, cond=0x5560f1952a08) at pthread_cond_wait.c:508 #2 0x7f4b7a8e42c6 in __pthread_cond_wait (cond=0x5560f1952a08, mutex=0x5560f19529e0) at pthread_cond_wait.c:638 #3 0x7f4b7b375def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4b7b375ee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4b7a40a7b9 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f4b7a40aa1a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f4b7b36fcc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4b7a8dd669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f4b7cad6323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f4b6edee700 (LWP 17429)): #0 0x7f4b7cac9d26 in __GI_ppoll (fds=0x7f4b60002978, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f4b7b58a5f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f4b7b58bb64 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f4b7b53563b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4b7b36ea75 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4b7b36fcc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4b7a8dd669 in start_thread (arg=) at pthread_create.c:479 #7 0x7f4b7cad6323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f4b6cf05700 (LWP 2259)): #0 0x7f4b7a8e42c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f4b7aef2fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f4b7a8e42c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f4b7aef2f68, cond=0x7f4b7aef2f90) at pthread_cond_wait.c:508 #2 0x7f4b7a8e42c6 in __pthread_cond_wait (cond=0x7f4b7aef2f90, mutex=0x7f4b7aef2f68) at pthread_cond_wait.c:638 #3 0x7f4b7adfc08a in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f4b7adfc0af in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f4b7a8dd669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f4b7cad6323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f4b6e175700 (LWP 2196)): #0 0x7f4b7cac9d26 in __GI_ppoll (fds=0x7f4b64000d68, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f4b7b58a5f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f4b7b58bb64 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f4b7b53563b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4b7b36ea75 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4b7a07c319 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f4b7b36fcc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4b7a8dd669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f4b7cad6323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f4b6700 (LWP 2019)): #0 0x7f4b7cac9d26 in __GI_ppoll (fds=0x7f4b6800e9e8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1
[plasmashell] [Bug 417536] New: Plasma crashed after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=417536 Bug ID: 417536 Summary: Plasma crashed after resume from suspend Product: plasmashell Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: s...@mailfence.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-29-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: Resumed laptop from suspend. The laptop was suspended while connected to Thunderbolt3 hub via USB-C, and resumed not connected. -- 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 0x7fce9dad3880 (LWP 8074))] Thread 20 (Thread 0x7fce1e4df700 (LWP 18540)): #0 0x7fcea07e72c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x561d61de6dd4) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fcea07e72c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561d61de6d80, cond=0x561d61de6da8) at pthread_cond_wait.c:508 #2 0x7fcea07e72c6 in __pthread_cond_wait (cond=0x561d61de6da8, mutex=0x561d61de6d80) at pthread_cond_wait.c:638 #3 0x7fcea1363dbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcea1363eb1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcea317c7b9 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fcea317ca1a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fcea135dc92 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fcea07e0669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fcea0fe2323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fce3d400700 (LWP 21984)): #0 0x7fcea07e72c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x561d61e526f4) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fcea07e72c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561d61e526a0, cond=0x561d61e526c8) at pthread_cond_wait.c:508 #2 0x7fcea07e72c6 in __pthread_cond_wait (cond=0x561d61e526c8, mutex=0x561d61e526a0) at pthread_cond_wait.c:638 #3 0x7fcea1363dbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcea1363eb1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcea317c7b9 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fcea317ca1a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fcea135dc92 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fcea07e0669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fcea0fe2323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fce1700 (LWP 21947)): #0 0x7fcea0fd12ac in __GI___libc_read (nbytes=10, buf=0x7fce1fffeb5e, fd=25) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7fcea0fd12ac in __GI___libc_read (fd=25, buf=0x7fce1fffeb5e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fce7101b955 in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.0.so #3 0x7fce710a3406 in pa_mainloop_prepare () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fce710a3ea4 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fce710a3f60 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fce710b210d in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7fce7104a37c in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.0.so #8 0x7fcea07e0669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fcea0fe2323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fce3f7fe700 (LWP 21878)): #0 0x7fcea07e72c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x561d61b422a4) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fcea07e72c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561d61b42250, cond=0x561d61b42278) at pthread_cond_wait.c:508 #2 0x7fcea07e72c6 in __pthread_cond_wait (cond=0x561d61b42278, mutex=0x561d61b42250) at pthread_cond_wait.c:638 #3 0x7fcea1363dbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcea1363eb1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcea317c7b9 in () at /usr/lib
[plasmashell] [Bug 417536] Plasma crashed after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=417536 --- Comment #1 from Dmitry --- Additional info: Laptop Dell precision 5520, Nvidia proprietary drivers 435.21 installed. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 --- Comment #22 from Dmitry --- As for me, I was able to start Akonadi with: rm -r ~/.config/akonadi rm -r ~/.local/share/akonadi sudo apt update sudo apt install akonadi* --reinstall sudo reboot now But I had to recreate the imap accounts in Kmail after it. -- You are receiving this mail because: You are watching all bug changes.
[calligragemini] [Bug 421776] New: Calligra Gemini crashed after opening or creating document
https://bugs.kde.org/show_bug.cgi?id=421776 Bug ID: 421776 Summary: Calligra Gemini crashed after opening or creating document Product: calligragemini Version: 3.1.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: dmitry.leb...@gmail.com Target Milestone: --- Application: calligragemini (3.1.0) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-31-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04 LTS -- Information about the crash: - What I was doing when the application crashed: I tried to open or create a document. The program tried to do something and then crashed. The crash can be reproduced every time. -- Backtrace: Application: Calligra Gemini (calligragemini), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f29a9303dc0 (LWP 8419))] Thread 12 (Thread 0x7f29777fe700 (LWP 8430)): #0 0x7f29ad541e60 in QMutex::lock() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f29ad761c89 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f29ab72dbe1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f29ab72e152 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f29ab72e2e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f29ad761583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f29ad7084db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f29ad540785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f29aec7ae1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f29ad5419d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f29abf77609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f29ad1d0103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f2977fff700 (LWP 8429)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f2977ffec90, clockid=, expected=0, futex_word=0x56022528a9d0) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f2977ffec90, clockid=, mutex=0x56022528a980, cond=0x56022528a9a8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x56022528a9a8, mutex=0x56022528a980, abstime=0x7f2977ffec90) at pthread_cond_wait.c:656 #3 0x7f29ad547a7c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f29ad547bcb in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f29ad545171 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f29ad5419d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f29abf77609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f29ad1d0103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f297ceab700 (LWP 8428)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f297ceaac90, clockid=, expected=0, futex_word=0x5602252a4a30) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f297ceaac90, clockid=, mutex=0x5602252a49e0, cond=0x5602252a4a08) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x5602252a4a08, mutex=0x5602252a49e0, abstime=0x7f297ceaac90) at pthread_cond_wait.c:656 #3 0x7f29ad547a7c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f29ad547bcb in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f29ad545171 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f29ad5419d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f29abf77609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f29ad1d0103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f297d6d4700 (LWP 8427)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x560224f2dce8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560224f2dc98, cond=0x560224f2dcc0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x560224f2dcc0, mutex=0x560224f2dc98) at pthread_cond_wait.c:638 #3 0x7f2982ffc3db in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f2982ffbfeb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f29abf77609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f29ad1d0103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f29756d4700 (LWP 8426)): #0 futex_wait_cancelable (
[krita] [Bug 410331] When I try to save any Krita file as a jpg or Krita file, I keep getting an error message -- 'cannot save / access is denied'
https://bugs.kde.org/show_bug.cgi?id=410331 --- Comment #8 from Dmitry --- As I understand you changed it to use system temp directory instead. Is it always a good idea? What if a project is HUUGE, but the temp dir is on a small SSD for example? Or a limited size tmpfs? Saving temporary file in the directory where the save is directed to seems like a good idea. Could have been a 1 character commit. :) -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 400929] kwallet-pam errors when logging into Plasma from lightdm
https://bugs.kde.org/show_bug.cgi?id=400929 Dmitry changed: What|Removed |Added CC||sho...@gmail.com --- Comment #1 from Dmitry --- I think I have the same error. It's happening for quite some time already after I changed my user password and of course I changed also kwallet password to be the same. I'm not sure it was the cause, maybe I updated packages at the same time and this is just a coincidence. After logging into plasma after opening Chromium or when wi-fi is trying to connect, dialog box pops up asking for my password. If enter the same password and kwallet unlocks. Plasma 5.14.3, but I believe it happened with previous versions as well. lightdm 1.28.0-1. Arch linux. ноя 23 08:39:34 stone0495 systemd[1]: session-c1.scope: Killing process 780 (lightdm) with signal SIGTERM. ноя 23 08:39:34 stone0495 systemd[1]: session-c1.scope: Killing process 791 (lightdm-webkit2) with signal SIGTERM. ноя 23 08:39:34 stone0495 systemd[1]: session-c1.scope: Killing process 811 (WebKitNetworkPr) with signal SIGTERM. ноя 23 08:39:34 stone0495 systemd[1]: session-c1.scope: Killing process 813 (WebKitWebProces) with signal SIGTERM. ноя 23 08:39:34 stone0495 systemd[1]: Stopping Session c1 of user lightdm. ноя 23 08:39:34 stone0495 lightdm[780]: pam_unix(lightdm-greeter:session): session closed for user lightdm ноя 23 08:39:34 stone0495 lightdm[983]: pam_kwallet5(lightdm:setcred): pam_kwallet5: pam_sm_setcred ноя 23 08:39:34 stone0495 lightdm[983]: pam_unix(lightdm:session): session opened for user shohov by (uid=0) ноя 23 08:39:34 stone0495 kernel: audit: type=1006 audit(1542955174.763:126): pid=983 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=4 res=1 ноя 23 08:39:34 stone0495 systemd-logind[393]: New session 4 of user shohov. ноя 23 08:39:34 stone0495 systemd[1]: Started Session 4 of user shohov. ноя 23 08:39:34 stone0495 lightdm[983]: pam_kwallet5(lightdm:session): pam_kwallet5: pam_sm_open_session ноя 23 08:39:34 stone0495 lightdm[989]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket ноя 23 08:39:34 stone0495 lightdm[989]: pam_kwallet5-kwalletd: Couldn't listen in socket ноя 23 08:39:34 stone0495 systemd[1]: Stopped Session c1 of user lightdm. ноя 23 08:39:34 stone0495 lightdm[983]: pam_kwallet5(lightdm:session): pam_kwallet5: Couldn't fork to execv kwalletd ноя 23 08:39:34 stone0495 systemd-logind[393]: Removed session c1. ноя 23 08:39:34 stone0495 systemd[948]: Started D-Bus User Message Bus. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395931] Bad rendering of bold fonts
https://bugs.kde.org/show_bug.cgi?id=395931 --- Comment #2 from Dmitry --- Installed in the VirtualBox default fonts: https://yadi.sk/i/r7sWKzwo3YZcM7 font settings: https://yadi.sk/i/4mmsVmZL3YZcLo System Information: https://yadi.sk/i/l3XG4jJ-3YZcLB -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 396270] New: End of a break notification does not work until "Skip Break" button is pressed
https://bugs.kde.org/show_bug.cgi?id=396270 Bug ID: 396270 Summary: End of a break notification does not work until "Skip Break" button is pressed Product: rsibreak Version: 0.12.8 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aa...@kde.org Reporter: dmitry.s.lisov...@gmail.com Target Milestone: --- I have enabled notifications for "End of long break" and "End of short break", so they play a sound and show popup. But they work only if "Skip Break" button is pressed during a break. Otherwise, when the break is over, they don't play any sound and don't show any popup. I need this functionality to hear the sound when the break is over, so I can return to the computer. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 396270] End of a break notification does not work until "Skip Break" button is pressed
https://bugs.kde.org/show_bug.cgi?id=396270 Dmitry changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395931] Bad rendering of bold fonts
https://bugs.kde.org/show_bug.cgi?id=395931 --- Comment #5 from Dmitry --- However, for some fonts "hinting" is used, but for other fonts (bold) "hinting" it is not applied. example: https://yadi.sk/i/CE7oAi2U3ZaRVB example 2: https://yadi.sk/i/DUFjz28o3ZaRew example settings: https://yadi.sk/i/6dWgaa9w3ZaRfZ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395931] Bad rendering of bold fonts
https://bugs.kde.org/show_bug.cgi?id=395931 --- Comment #7 from Dmitry --- Created attachment 114146 --> https://bugs.kde.org/attachment.cgi?id=114146&action=edit bed hinting -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395931] Bad rendering of bold fonts
https://bugs.kde.org/show_bug.cgi?id=395931 --- Comment #8 from Dmitry --- Created attachment 114147 --> https://bugs.kde.org/attachment.cgi?id=114147&action=edit In one window, hinting is not applied to all fonts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395931] Bad rendering of bold fonts
https://bugs.kde.org/show_bug.cgi?id=395931 --- Comment #9 from Dmitry --- Created attachment 114148 --> https://bugs.kde.org/attachment.cgi?id=114148&action=edit SMPlayer too. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383127] KTorrent crash while closing
https://bugs.kde.org/show_bug.cgi?id=383127 --- Comment #23 from Dmitry --- Created attachment 114174 --> https://bugs.kde.org/attachment.cgi?id=114174&action=edit New crash information added by DrKonqi ktorrent (5.1.0) using Qt 5.10.1 - What I was doing when the application crashed: I was closeing Ktorrent from system Plasma tray -- Backtrace (Reduced): #6 0x7f3901601d93 in findChar(QChar const*, int, QChar, int, Qt::CaseSensitivity) () from /lib64/libQt5Core.so.5 #7 0x7f39016065da in QString::replace(QChar, QChar, Qt::CaseSensitivity) () from /lib64/libQt5Core.so.5 #8 0x7f390227b029 in QAbstractItemDelegatePrivate::textForRole(Qt::ItemDataRole, QVariant const&, QLocale const&, int) const () from /lib64/libQt5Widgets.so.5 #9 0x7f39022822b3 in QStyledItemDelegate::displayText(QVariant const&, QLocale const&) const () from /lib64/libQt5Widgets.so.5 #10 0x7f3902283c6e in QStyledItemDelegate::initStyleOption(QStyleOptionViewItem*, QModelIndex const&) const () from /lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383127] KTorrent crash while closing
https://bugs.kde.org/show_bug.cgi?id=383127 Dmitry changed: What|Removed |Added CC||bm_...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391995] New: Inhibition handling is illogical
https://bugs.kde.org/show_bug.cgi?id=391995 Bug ID: 391995 Summary: Inhibition handling is illogical Product: Powerdevil Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dmitriyval...@gmail.com Target Milestone: --- Inhibition from org.freedesktop.PowerManagement.Inhibit and org.freedesktop.ScreenSaver are handled pretty much the same way with preventing both sleep/suspend and screen power saving/screen locking. But that's absolutely illogical as far as powerdevil supports differentiation between these two types of wakelocks (e.g. on laptop lid close when external monitor is present). So intentions for developers using these inhibitions are absolutely clear, just take a look at chromium (chromium/services/device/wake_lock/power_save_blocker/power_save_blocker_x11.cc:282) or ktorrent (ktorrent/ktorrent/pref/generalpref.ui, ktorrent/ktorrent/core.cpp:972) sources. This behaviour makes system keep screen on when no one app really needs it, like chromium/vavaldi/other forks playing audio (not video) or ktorrent downloading something. It appears at least in KDE Neon, Fedora 26 and OpenSUSE Tumbleweed with 5.10 up to latest Plasma versions. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 393388] Font vertical alignment problem in Global Menu with Latte Dock
https://bugs.kde.org/show_bug.cgi?id=393388 Dmitry changed: What|Removed |Added CC||dmitriyval...@gmail.com --- Comment #2 from Dmitry --- Created attachment 112175 --> https://bugs.kde.org/attachment.cgi?id=112175&action=edit regular panel with global menu, 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 393388] Font vertical alignment problem in Global Menu with Latte Dock
https://bugs.kde.org/show_bug.cgi?id=393388 --- Comment #3 from Dmitry --- Created attachment 112176 --> https://bugs.kde.org/attachment.cgi?id=112176&action=edit regular panel with global menu, 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 393388] Font vertical alignment problem in Global Menu with Latte Dock
https://bugs.kde.org/show_bug.cgi?id=393388 --- Comment #4 from Dmitry --- (In reply to Michail Vourlakos from comment #1) > sounds more Latte issue, but I cant replicate with master version I found the way to reproduce this issue on Plasma 5.12.4 with regular plasma pannel (not latte). There are a few steps with default layout: 1) Add 'Application Menu Bar' pannel 2) Add Digital Clock widget to the pannel 3) Add date to Digital Clock widget 4) Make this pannel so thin that both date and time will be on the one line Also see this issue in openSUSE Tumbleweed -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 387972] New: Power management suppressing prevents screen from locking
https://bugs.kde.org/show_bug.cgi?id=387972 Bug ID: 387972 Summary: Power management suppressing prevents screen from locking Product: kscreenlocker Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dmitriyval...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- Created attachment 109419 --> https://bugs.kde.org/attachment.cgi?id=109419&action=edit WebRTC in Chromium suppressing power management KDE ignores lockscreen timeout when power management is suppressed (e.g. by Chromium playing audio or showing some websites like Aliexpress). It may be a critical security issue for someone eho rely on auto locking screen Behavour is the same on: Latest unstable/developer Neon, Latest OpenSUSE Tumbleweed, Fedora 26, and, I'm sure, on some other distributions -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 392608] New: Software central crash
https://bugs.kde.org/show_bug.cgi?id=392608 Bug ID: 392608 Summary: Software central crash Product: Discover Version: 5.12.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: my3dwork2...@yandex.ru Target Milestone: --- Application: plasma-discover (5.12.3) Qt Version: 5.10.0 Frameworks Version: 5.44.0 Operating System: Linux 4.13.0-37-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: Im install drivers in konsole sudo ubuntu-drivers autoinstall after that i launch Software central and it crash every time a try start it The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f02867e3900 (LWP 15622))] Thread 9 (Thread 0x7f0237bea700 (LWP 15633)): #0 0x7f0281c2027d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f027ae43073 in ?? () from /usr/lib/nvidia-384/tls/libnvidia-tls.so.384.111 #2 0x7f027c64b6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f027c607e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f027c608330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f027c60849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f02828605cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f028280764a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0282627554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f028262c6eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f027e7cf6ba in start_thread (arg=0x7f0237bea700) at pthread_create.c:333 #11 0x7f0281c3041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f024d647700 (LWP 15631)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f028262d67b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0282625fbb in QSemaphore::acquire(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f02828366c6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f027faecec8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7f027fbac09d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #6 0x7f0282836489 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f027fab46ab in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7f027fab4f0d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #9 0x7f0282836489 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f027fba6477 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f027fba35db in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7f027fba3ff6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #13 0x7f027fb879e1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #14 0x7f0282836489 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f027fb55773 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #16 0x7f027fb5582c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #17 0x7f027fb660e1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #18 0x7f0283e0eacc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f0283e16417 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f02828093c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f028286122d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f027c608197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f027c6083f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f027c60849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f02828605cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f028280764a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f0282627554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
[kdenlive] [Bug 380055] Configuration file is invalid
https://bugs.kde.org/show_bug.cgi?id=380055 Dmitry changed: What|Removed |Added CC||lubsanov.dmi...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380055] Configuration file is invalid
https://bugs.kde.org/show_bug.cgi?id=380055 Dmitry changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
