[dolphin] [Bug 487919] Open tabs close to home on reboot / logoff
https://bugs.kde.org/show_bug.cgi?id=487919 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 464225] copy/move symbolic link moves link destination instead
https://bugs.kde.org/show_bug.cgi?id=464225 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 466552] New: Kclock stays alive after closing it, without a way to shut it down.
https://bugs.kde.org/show_bug.cgi?id=466552 Bug ID: 466552 Summary: Kclock stays alive after closing it, without a way to shut it down. Classification: Applications Product: KClock Version: 23.01.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: espi...@gmail.com Reporter: eridanired...@yahoo.com.mx CC: hanyo...@protonmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Install Kclock (I did from Flathub) 2. Start it and create a timer. 3. Close the app. OBSERVED RESULT 1. Launch ´top´ in konsole to see that ´kclock´, ´kclockd´ and related processes are still running in the background, but there would be no visual indicator about this, nor a way to terminate the application from the graphic interface. 2. Opening the program again will spawn duplicated processes instead of reusing those that are still alive. EXPECTED RESULT 1. The program should terminate cleanly without leaving any lingering background process. 2. There should be a configurable preference to keep it running in the background for tasks that may benefit from it, such as programmed alarms; optionally, this status should be indicated by an interactive icon in the system tray. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-32-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358231] desktop locks up when moving lots of files
https://bugs.kde.org/show_bug.cgi?id=358231 --- Comment #44 from Eridani Rodríguez --- Copying an 8 Gigabyte file across any devices that do NOT hold the system does not trigger the freeze for me. However, copying it to the physical device THAT HOLDS the system installation, does cause panels and dolphin to become sluggish; if I continue trying to do stuff, like opening other dolphin views or emptying the trash, it would eventually become non responsive unless the transfer is cancelled or completed. This does not happen at all if cp in a terminal is used for the operation. The problem may be less noticeable in faster devices, so if you are not being able to reproduce it, try with files that are way larger than the speed of the device where your system is installed. Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-32-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz Memory: 31.3 GiB of RAM File system: BTRFS System's storage device: SATA 3 SSD -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466011] New: vulkaninfo package missing from Neon User repos
https://bugs.kde.org/show_bug.cgi?id=466011 Bug ID: 466011 Summary: vulkaninfo package missing from Neon User repos Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: eridanired...@yahoo.com.mx CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** kinfocenter has a new page to see Vulkan information inside the Graphics section, but when I navigate to it displays a message saying that “The vulkaninfo tool is required to display this page but could not be found” suggesting the user to search and install it using the package manager. However, such search returns no results. *** OBSERVED RESULT No vulkaninfo package in Neon user repos. EXPECTED RESULT vulkaninfo should be available. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 446797] In search results, when text doesn't fit in the window: implement a way to read the full string (e.g. in a tooltip) on demand.
https://bugs.kde.org/show_bug.cgi?id=446797 Eridani Rodríguez changed: What|Removed |Added Ever confirmed|1 |0 Status|CONFIRMED |REPORTED --- Comment #4 from Eridani Rodríguez --- I think this is no longer a problem! Can anyone confirm and close the report? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 465723] New: Search should be diacritic insensitive while results should prefer them when available.
https://bugs.kde.org/show_bug.cgi?id=465723 Bug ID: 465723 Summary: Search should be diacritic insensitive while results should prefer them when available. Classification: Plasma Product: krunner Version: 5.27.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: eridanired...@yahoo.com.mx CC: alexander.loh...@gmx.de Target Milestone: --- SUMMARY 1. It is usual for search engines (from Google to Discover app search) to not care if people typed a word with its diacritic signs or without them, returning equal results no matter how the word was written. This is not the case for Krunner, as it returns different results. As an example, in Spanish, the correct way to spell “Japan” in a written text would be “Japón” but typing it correctly involves pressing a [modifier key] + [accent key] + [O] key to obtain “ó”. That is quite complex for a quick search, so people usually just presses the “O” key to type “japon”, not caring even for caps, leaving the rest to the search engines. 2. However, in some cases diacritics change the meaning of a word by 180º, so if people have typed them, the results should prefer matches with them, while still showing the results that do not have them because it is common to mistype them in some cases. As an example, in Spanish “inglés” (English) can't be more distinct from “ingles” (groins), the difference residing only in the accent on top of the letter “e”. STEPS TO REPRODUCE 1. Launch KRunner using Spanish locale*** and search for: A) “hora japon” B) “hora japón” OBSERVED RESULT Case (A) returns nothing, while case (B) properly returns Japan's date and time. EXPECTED RESULT Both searches should return the matches from case (A). Additionally, search (B) should also return its own matches and show them on top. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 5.15.0-60-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION *** I use Plasma in Spanish, hence is the case I can talk about, but there is a related bug for Arabic already open, so I can imagine how this may apply to other languages as well. https://bugs.kde.org/show_bug.cgi?id=465333 Is this even a Krunner bug?, there are many components affected with a similar issue, see: https://bugs.kde.org/show_bug.cgi?id=250345 https://bugs.kde.org/show_bug.cgi?id=274933 https://bugs.kde.org/show_bug.cgi?id=429448 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes
https://bugs.kde.org/show_bug.cgi?id=395023 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462845] The default button changed to Cancel at permanent delete
https://bugs.kde.org/show_bug.cgi?id=462845 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436627] Mouse gestures don't work in Wayland
https://bugs.kde.org/show_bug.cgi?id=436627 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 353886] SystemSettings - shortcuts and gestures
https://bugs.kde.org/show_bug.cgi?id=353886 Eridani Rodríguez changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Eridani Rodríguez --- Can still be reproduced following the steps in the previously attached video https://bugs.kde.org/attachment.cgi?id=133861 Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-52-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z87-HD3 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 417895] Pull current track/artist name from radio stream
https://bugs.kde.org/show_bug.cgi?id=417895 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458844] New: "Shade" button disappears from tittle bar when returning from full screen.
https://bugs.kde.org/show_bug.cgi?id=458844 Bug ID: 458844 Summary: "Shade" button disappears from tittle bar when returning from full screen. Product: kwin Version: 5.25.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- SUMMARY *** When having the Shade window button on the tittle bar, and going full screen then exiting said state, the Shade button will disappear from the tittle bar until the tittle bar is forced to be redrawn, e.g. making the windows borderless and bordered again. *** STEPS TO REPRODUCE 1. From Window Decorations settings, place the “Shade” button in the tittle bar. 2. Open any application and go full screen, (Firefox or Dolphin, for example). 3. Exit full screen. OBSERVED RESULT The application have lost the Shade button. EXPECTED RESULT The Shade button should be there along with the rest. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.15.0-46-generic (64-bit) Graphics Platform: X11 Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 ADDITIONAL INFORMATION Possibly duplicate of https://bugs.kde.org/show_bug.cgi?id=453282 , but if not, at least it should be related. In that bug report only the rightmost button disappear, but in this one, rightmost button is fine, all buttons are fine, except for the “Shade” button, doesn't matter where it is placed, left, right, leftmost, rightmost, it always and only the “Shade” button disappears. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458842] New: Can no longer activate shaded windows from desktop grid
https://bugs.kde.org/show_bug.cgi?id=458842 Bug ID: 458842 Summary: Can no longer activate shaded windows from desktop grid Product: kwin Version: 5.25.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- SUMMARY *** If a window is shaded, and then the desktop grid effect invoked, although the tittle bar appears, it is impossible to click on it. *** STEPS TO REPRODUCE 1. Shade any window (via the option when right-clicking its tittle bar, or by enabling the button in Window Decorations settings) 2. Use the dektop grid effect (e.g. via Present Window or Desktop Grid) 3. Try selecting the app you shaded before. OBSERVED RESULT Desktop Grid will exit, as if you had clicking on empty space. EXPECTED RESULT The selected window's tittle bar should be brought to the front as an active window. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.15.0-46-generic (64-bit) Graphics Platform: X11 Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455280] New: While arranging a single window, all windows in the same workspace move along together.
https://bugs.kde.org/show_bug.cgi?id=455280 Bug ID: 455280 Summary: While arranging a single window, all windows in the same workspace move along together. Product: kwin Version: 5.25.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- SUMMARY *** It used to be able to move a window from one desktop to another by dragging via the desktop grid effect, additionally, it was possible to rearrange all windows in a specific virtual desktop by dragging from the wallpaper instead of a window. After update to 25.0, the first feature seems to be lost, allowing only to rearrange whole groups of windows. Furthermore, dragging now requires two clicks to activate the action. See online clips in Dropbox posted below. *** STEPS TO REPRODUCE 1. Update Neon to 25.0 2. Open multiple windows in various workspaces, open a few per workspace. 3. Fire desktop grid effect from a hot corner 4. Try moving a window from one desktop to another. OBSERVED RESULT All windows in the same desktop move along while trying to move only one, see: - https://www.dropbox.com/s/11e3o1x49gmrt88/vokoscreen-2022-06-14_11-50-04.mkv?dl=0 EXPECTED RESULT Only the chosen window will be draged. See how it used to work: - https://www.dropbox.com/s/59ufkg3x8cxin1o/vokoscreen-2022-06-14_15-35-32.mkv?dl=0 SOFTWARE/OS VERSIONS - Operating System: KDE neon 5.25 - KDE Plasma Version: 5.25.0 - KDE Frameworks Version: 5.95.0 - Qt Version: 5.15.4 - Kernel Version: 5.13.0-48-generic (64-bit) - Graphics Platform: X11 - Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz - Memory: 15.6 GiB of RAM - Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 ADDITIONAL INFORMATION These are the specs of the same system with the version that works well: - Operating System: KDE neon 5.24 - KDE Plasma Version: 5.24.5 - KDE Frameworks Version: 5.94.0 - Qt Version: 5.15.4 - Kernel Version: 5.13.0-44-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358231] desktop locks up when moving lots of files
https://bugs.kde.org/show_bug.cgi?id=358231 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 387455] Column view in Dolphin
https://bugs.kde.org/show_bug.cgi?id=387455 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453638] Starting Wayland session loops back to user selection screen and blocks starting any further session
https://bugs.kde.org/show_bug.cgi?id=453638 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453638] Starting Wayland session loops back to user selection screen and blocks starting any further session
https://bugs.kde.org/show_bug.cgi?id=453638 --- Comment #1 from Eridani Rodríguez --- Created attachment 148720 --> https://bugs.kde.org/attachment.cgi?id=148720&action=edit Output of `coredumpctl dump kwin_wayland` after reboot ADDITIONAL INFORMATION Attached the output of `coredumpctl dump kwin_wayland` as suggested by this tread in KDE's subreddit: https://old.reddit.com/r/kde/comments/um14wt/trying_to_start_a_wayland_session_loops_back_to/ Had to compress as 7z because it was too big otherwise. Here is the first part of the output that was displayed in Konsole: ~$ coredumpctl dump kwin_wayland PID: 593064 (kwin_wayland) UID: 1000 (eridani) GID: 1000 (eridani) Signal: 11 (SEGV) Timestamp: Tue 2022-05-10 14:14:15 CDT (19min ago) Command Line: /usr/bin/kwin_wayland --wayland-fd 5 --socket wayland-0 --xwayland-fd 7 --xwayland-fd 8 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_PKLmut --xwayland Executable: /usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/session-325.scope Unit: session-325.scope Slice: user-1000.slice Session: 325 Owner UID: 1000 (eridani) Boot ID: e2dbbc468a854738b0afae8032175360 Machine ID: 40718d4cc0cb4ce7bb811319c1acac35 Hostname: pronyma Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.e2dbbc468a854738b0afae8032175360.593064.1652210055.lz4 Message: Process 593064 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 593064: #0 0x7f4633599ef8 _ZN4KWin10GbmSurface17swapBuffersForDrmEv (KWinWaylandDrmBackend.so + 0x57ef8) #1 0x7f4633596323 _ZN4KWin13EglGbmBackend18endFrameWithBufferEPNS_14AbstractOutputERK7QRegion (KWinWaylandDrmBackend.so + 0x54323) #2 0x7f46335965fb _ZN4KWin13EglGbmBackend15renderTestFrameEPNS_17DrmAbstractOutputE (KWinWaylandDrmBackend.so + 0x545fb) #3 0x7f4633587064 _ZN4KWin11DrmPipeline15checkTestBufferEv (KWinWaylandDrmBackend.so + 0x45064) #4 0x7f46335893be _ZN4KWin11DrmPipeline21commitPipelinesAtomicERK7QVectorIPS0_ENS0_10CommitModeERKS1_IPNS_9DrmObjectEE (KWinWaylandDrmBackend.so + 0x473be) #5 0x7f463357f916 _ZN4KWin6DrmGpu13testPipelinesEv (KWinWaylandDrmBackend.so + 0x3d916) #6 0x7f463357fad0 _ZN4KWin6DrmGpu19checkCrtcAssignmentE7QVectorIPNS_12DrmConnectorEES1_IPNS_7DrmCrtcEE (KWinWaylandDrmBackend.so + 0x3dad0) #7 0x7f463357fee1 _ZN4KWin6DrmGpu19checkCrtcAssignmentE7QVectorIPNS_12DrmConnectorEES1_IPNS_7DrmCrtcEE (KWinWaylandDrmBackend.so + 0x3dee1) #8 0x7f4633580708 operator() (KWinWaylandDrmBackend.so + 0x3e708) #9 0x7f4633581c7f _ZN4KWin6DrmGpu13updateOutputsEv (KWinWaylandDrmBackend.so + 0x3fc7f) #10 0x7f463355dd34 _ZN4KWin10DrmBackend13updateOutputsEv (KWinWaylandDrmBackend.so + 0x1bd34) #11 0x7f4639cbcdfe n/a (libQt5Core.so.5 + 0x2ebdfe) #12 0x7f463bfd027e _ZN4KWin10Compositor10setupStartEv (libkwin.so.5 + 0x13f27e) #13 0x7f463bfd1895 _ZN4KWin17WaylandCompositor5startEv (libkwin.so.5 + 0x140895) #14 0x7f4639cb3959 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e2959) #15 0x7f463a7dcdc3 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x16ddc3) #16 0x7f463a7e5bd8 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x176bd8) #17 0x7f4639c85d7a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b4d7a) #18 0x7f4639c88681 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b7681) #19 0x7f4639cdd9de _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c9de) #20 0x560a7fe2c521 _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (kwin_wayland + 0x17b521) #21 0x7f4639c8487b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b387b) #22 0x7f4639c8ca24 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2bba24) #23 0x560a7fd0cfcc main (kwin_wayland + 0x5bfcc) #24 0x7f46392430b3 __libc_start_main (libc.so.6 + 0x240b3) #25 0x560a7fd0ecfe _start (kwin_wayland + 0x5dcfe) Stack trace of thread 593066: #0 0x7f46393319cf __GI___poll (libc.so.6 + 0x1129cf) #1 0x7f463791b36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f463791b4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x
[kwin] [Bug 453638] New: Starting Wayland session loops back to user selection screen and blocks starting any further session
https://bugs.kde.org/show_bug.cgi?id=453638 Bug ID: 453638 Summary: Starting Wayland session loops back to user selection screen and blocks starting any further session Product: kwin Version: 5.24.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- SUMMARY *** In the user selection screen, if I pick Wayland, it won't start, it will instead proceed to a black screen and show the cursor before going back to the user selection screen after a minute or so. Then, after trying to start a Wayland session, it is no longer possible to start any kind of graphic session any more, since the x11 session starts showing the same loopy behaviour until rebooting. I tested with my regular session and with 2 newly created users (regular and administration types), without any appreciable difference between the 3. *** STEPS TO REPRODUCE 1. Get to the login screen 2. Select Wayland session 3. Try to log in. OBSERVED RESULT Session won't start, and the user selection screen will be shown again after a few moments. EXPECTED RESULT It should properly login. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-40-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 442510] I can't see avif images, kimageformat-plugins package updated to 5.86 with support for avif file
https://bugs.kde.org/show_bug.cgi?id=442510 --- Comment #7 from Eridani Rodríguez --- Not OP, but can confirm that adding qt-avif-image-plugin.xml and running update-mime-database enabled Gwenview to open avif images and Dolphin to generate thumbnails. Tested in daily driver KDE Neon with: KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 And neondocker:latest: KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 As a side note, this workaround was unneeded for Open SUSE Tumbleweed, as it properly opened avif images after installing kimageformats-5.93.0-248.3. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 442510] I can't see avif images, kimageformat-plugins package updated to 5.86 with support for avif file
https://bugs.kde.org/show_bug.cgi?id=442510 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 433804] zfs support in ksysguard / system monitor widgets?
https://bugs.kde.org/show_bug.cgi?id=433804 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 446797] In search results, when text doesn't fit in the window: implement a way to read the full string (e.g. in a tooltip) on demand.
https://bugs.kde.org/show_bug.cgi?id=446797 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 446797] In search results, when text doesn't fit in the window: implement a way to read the full string (e.g. in a tooltip) on demand.
https://bugs.kde.org/show_bug.cgi?id=446797 --- Comment #1 from Eridani Rodríguez --- Created attachment 144438 --> https://bugs.kde.org/attachment.cgi?id=144438&action=edit Screenshot showing results for time search. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 446797] New: In search results, when text doesn't fit in the window: implement a way to read the full string (e.g. in a tooltip) on demand.
https://bugs.kde.org/show_bug.cgi?id=446797 Bug ID: 446797 Summary: In search results, when text doesn't fit in the window: implement a way to read the full string (e.g. in a tooltip) on demand. Product: krunner Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: eridanired...@yahoo.com.mx CC: plasma-b...@kde.org Target Milestone: --- Created attachment 144437 --> https://bugs.kde.org/attachment.cgi?id=144437&action=edit Screenshot showing similar looking borwser bookmarks as search results. Currently, if a search result text is a too long sentence that doesn't fit in the window it is cut by the middle with tree dots “…” which is expected, but there is no way to read the full text if the necessity arises. The full text is necessary to distinguish a useful result from the rest when there are multiple similar items in the list, and whose sole differentiating factor is not at the start or the end of the string. Showing a tooltip with the full text on mouse over or displaying it in a sort of *marquee* fashion with the text scrolling on mouse over would be two possible solutions. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 434308] Bluetooth headset broken in multi user environment
https://bugs.kde.org/show_bug.cgi?id=434308 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 438391] HWE kernel missing
https://bugs.kde.org/show_bug.cgi?id=438391 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 438390] Regression: Installation fails on BTRFS
https://bugs.kde.org/show_bug.cgi?id=438390 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 429406] Gmail auth token is not remembered across restarts
https://bugs.kde.org/show_bug.cgi?id=429406 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 353886] SystemSettings - shortcuts and gestures
https://bugs.kde.org/show_bug.cgi?id=353886 --- Comment #6 from Eridani Rodríguez --- Created attachment 133862 --> https://bugs.kde.org/attachment.cgi?id=133862&action=edit valgrind log -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 353886] SystemSettings - shortcuts and gestures
https://bugs.kde.org/show_bug.cgi?id=353886 Eridani Rodríguez changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Eridani Rodríguez --- Changing this back to reported as suggested before. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 353886] SystemSettings - shortcuts and gestures
https://bugs.kde.org/show_bug.cgi?id=353886 --- Comment #4 from Eridani Rodríguez --- Created attachment 133861 --> https://bugs.kde.org/attachment.cgi?id=133861&action=edit gdb log + small video to reproduce Can confirm that this erratic behaviour is still present in Plasma 5.20.3. I've attached a gdb log (hope I did it correctly) and a small video showing the steps needed to reproduce it. Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.4.0-54-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 1060 3GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 366238] KMail does not fetch mails from imap.kabelmail.de
https://bugs.kde.org/show_bug.cgi?id=366238 --- Comment #23 from Eridani Rodríguez --- Forgot my system info: Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.4.0-54-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 1060 3GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 366238] KMail does not fetch mails from imap.kabelmail.de
https://bugs.kde.org/show_bug.cgi?id=366238 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx --- Comment #22 from Eridani Rodríguez --- Created attachment 133704 --> https://bugs.kde.org/attachment.cgi?id=133704&action=edit akonadi console kimap logs I'm experiencing this problem with an account from my local ISP, akonadi can see the IMAP folder, how many messages are on them, see the discrepancy between message count on the server and local copies, tries to fetch them but won't fetch a thing at the end, no feedback either, other mail accounts from popular services (google, yahoo, etc.) work well by the way. This problematic account can be synced in Thunderbird but not on Kmail (Trojita failed too), I've attached the kimap.log files from my test conducted as explained a few comments above. As after reading the logs it doesn't seem to be any specially helpful info on them at least to my untrained eye, I'll be able to conduct more testing if guided. Also, can provide login credentials for this account if needed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402154] Baloo reindexes everything after every reboot
https://bugs.kde.org/show_bug.cgi?id=402154 --- Comment #8 from Eridani Rodríguez --- My system seems to be affected too, in my case / is BTRFS while /home/MyUser/Desktop or /home/MyUser/Music (and all other user folders) are on separated ZFS datasets, none of them are encrypted, but both use compression among other features. Baloo will reindex all /home/MyUser/ZFSMonutedDirectories on reboot. I'll leave some additional specs of another system (mine) in hopes that it could be helpful: Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 Kernel Version: 5.4.0-52-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 1060 3GB/PCIe/SSE2 btrfs-progs v5.4.1 zfs-0.8.3-1ubuntu12.4 zfs-kmod-0.8.3-1ubuntu12.4 ZFS INFO for an affected dataset zfs get all Link/Home/Music NAME PROPERTY VALUE SOURCE Link/Home/Music type filesystem - Link/Home/Music creation sáb jun 6 16:13 2020 - Link/Home/Music used 20.8G - Link/Home/Music available 655G- Link/Home/Music referenced 20.8G - Link/Home/Music compressratio 1.01x - Link/Home/Music mountedyes - Link/Home/Music quota nonedefault Link/Home/Music reservationnonedefault Link/Home/Music recordsize 128Kdefault Link/Home/Music mountpoint /home/MyUser/Music local Link/Home/Music sharenfs off default Link/Home/Music checksum on default Link/Home/Music compressionon inherited Link/Home/Music atime on default Link/Home/Music deviceson default Link/Home/Music exec on default Link/Home/Music setuid on default Link/Home/Music readonly off default Link/Home/Music zoned off default Link/Home/Music snapdirhidden default Link/Home/Music aclinherit restricted default Link/Home/Music createtxg 261 - Link/Home/Music canmount on default Link/Home/Music xattr on default Link/Home/Music copies 1 default Link/Home/Music version5 - Link/Home/Music utf8only off - Link/Home/Music normalization none- Link/Home/Music casesensitivitysensitive - Link/Home/Music vscan off default Link/Home/Music nbmand off default Link/Home/Music sharesmb off default Link/Home/Music refquota nonedefault Link/Home/Music refreservation nonedefault Link/Home/Music guid 14467266995499749484- Link/Home/Music primarycache all default Link/Home/Music secondarycache all default Link/Home/Music usedbysnapshots51.8M - Link/Home/Music usedbydataset 20.8G - Link/Home/Music usedbychildren 0B - Link/Home/Music usedbyrefreservation 0B - Link/Home/Music logbiaslatency default Link/Home/Music objsetid 167 - Link/Home/Music dedup off default Link/Home/Music mlslabel nonedefault Link/Home/Music sync standarddefault Link/Home/Music dnodesize legacy default Link/Home/Music refcompressratio 1.01x - Link/Home/Music written0 - Link/Home/Music logicalused21.1G - Link/Home/Music logicalreferenced 21.0G - Link/Home/Music volmodedefault default Link/Home/Music filesystem_limit nonedefault Link/Home/Music snapshot_limit nonedefault Link/Home/Music filesystem_count nonedefault Link/Home/Music snapshot_count nonedefault Link/Home/Music sn
[kwin] [Bug 422548] Cursors do not respect scale factor on X11
https://bugs.kde.org/show_bug.cgi?id=422548 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 427650] New: kactivitymanagerd crashes with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=427650 Bug ID: 427650 Summary: kactivitymanagerd crashes with segmentation fault Product: kactivitymanagerd Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: eridanired...@yahoo.com.mx CC: plasma-b...@kde.org Target Milestone: --- Created attachment 132329 --> https://bugs.kde.org/attachment.cgi?id=132329&action=edit Backtrace 01 SUMMARY Upon starting Plasma, kactivitymanagerd crashes then crashes again when using Dolphin or System settings. STEPS TO REPRODUCE 1. Reboot and wait for Plasma 2. Crash OBSERVED RESULT kactivitymanagerd crashes rendering impossible to use Activities. EXPECTED RESULT It should not crash. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 Kernel Version: 5.4.0-48-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 1060 3GB/PCIe/SSE2 ADDITIONAL INFORMATION Specific VERSION with this problem is 5.20.0-0xneon+20.04+focal+build10 downgrading to 5.19.5-0xneon+20.04+focal+build9 is a workaround to maintain activities working with no noticeable drawback. Also, https://bugs.kde.org/show_bug.cgi?id=426963 Talks about a crash on version 5.20, but I don't know if its related or not. Their trace back is not a segmentation fault, so opted for opening this ticket. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402154] Baloo reindexes everything after every reboot
https://bugs.kde.org/show_bug.cgi?id=402154 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421392] plasmashell crashes when opening the thermal monitor widget settings
https://bugs.kde.org/show_bug.cgi?id=421392 --- Comment #9 from Eridani Rodríguez --- Created attachment 128666 --> https://bugs.kde.org/attachment.cgi?id=128666&action=edit dpkg log of updated software for when bug started [Neon 5.18.5] Can confirm this is a recent issue, whatever update Neon User Edition had for plasma the week before last (highly suspect update around 2020-05-07) is what triggered this behaviour. I'm confident that widget worked fine before May. Sadly I don't know the exact date for when this started but I've attached my dpkg log, hope is of use. Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-53-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz Memory: 15.6 GiB -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366485] Plasma crash while update
https://bugs.kde.org/show_bug.cgi?id=366485 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421392] plasmashell crashes when opening the thermal monitor widget settings
https://bugs.kde.org/show_bug.cgi?id=421392 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 269367] There is no way to search in hidden folders now.
https://bugs.kde.org/show_bug.cgi?id=269367 --- Comment #24 from Eridani Rodríguez --- Can confirm that it is STILL IMPOSSIBLE to search in hidden folders from folders on higher hierarchy than the hidden folder in 19.12.3, this means that: - You can search from `/regularF/.hiddenF/` and find `/regularF/.hiddenF/myFile` - But if you search from `/regularF/` Dolphin won't find `/regularF/.hiddenF/myFile`, ever. Unless you explicitly tell Baloo to index either all hidden paths or that specific hidden folder. But that may not be what most people want, hidden folders are hidden because people want them out of their way most of the time. Being "most of the time" the keyword here, you some times need to search in hidden folders, and your file manager should give you an option to do it, even if this option meant using an external program for conducting the task. (For those wondering, installing KFind doesn't make a difference, although you at least get a handy button to launch KFind.) System info: --- Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 5.3.0-40-generic KDE Applications Version: 19.12.3 Dolphin Version: 19.12.3 --- This bug was marked as SOLVED because of bug https://bugs.kde.org/show_bug.cgi?id=391252 which talks about how is intentional behaviour for Baloo to not index hidden folders by default. While I agree with the thing about Baloo's scope, I don't agree with this bug being a duplicate of that Baloo bug. If KFind integration* is the only plausible solution at this time because Baloo is pretty much unmaintained or because it is out of Baloo's design scope (as noted on the thread cited above); then some steps should be taken to make it a flawless integration. Currently the folder to search from is passed to KFind as "file:///yourFolder/childFolder" and KFind doesn't understand that, it understands however "/yourFolder/childFolder", same for the actual string to search for e.g. "strawberries", KFind needs it to be "*strawberries*" to find something unless you meant an exact name match which most of the times you don't (no idea about blank spaces or weird characters in the search string, but probably need to use some special stuff to handle those cases too). Nothing useful is passed from Dolphin to Catfish either by the way. Currently we have a crippled search in a file manager that allows you to navigate hidden folders but won't let you search in them. In my opinion, this integration should be addressed or Baloo scope should be addressed or in the worst scenario, Dolphin allowing you to view hidden files should be addressed before this bug could be marked as solved. * When I say "KFind integration" is because it was mentioned above and is almost done from my point of view, but I'm just an user and have no idea of the internals that would need to be moved around for it to be a flawless integration. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416476] New: Add a close window button on Desktop Grid view
https://bugs.kde.org/show_bug.cgi?id=416476 Bug ID: 416476 Summary: Add a close window button on Desktop Grid view Product: plasmashell Version: master Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Pager Assignee: h...@kde.org Reporter: eridanired...@yahoo.com.mx CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When Present Windows view is invoked, all windows have an (X) button on the corner for closing the window directly from the Present Windows view, it would be awesome if this was the case for the Desktop Grid view too. STEPS TO REPRODUCE 1. Try closing a window from Desktop View OBSERVED RESULT You can't EXPECTED RESULT You should be able to SOFTWARE/OS VERSIONS Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 Kernel Version: 5.3.0-26-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz Memory: 15.6 GiB -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416476] Add a close window button on Desktop Grid view
https://bugs.kde.org/show_bug.cgi?id=416476 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 401383] Elisa crash after deleting Music forlder from library.
https://bugs.kde.org/show_bug.cgi?id=401383 --- Comment #4 from Eridani Rodríguez --- Elisa 19.12.1 from Neon repos, not crashing any more! But you can't actually remove all directories from the library (leave the list empty); as removing the last item automatically replaces it instead for /home/user_name/Music (or whatever route the user has configured for it's system's music folder). Is this the intended behaviour? -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 411339] zanshin fails to run on neon
https://bugs.kde.org/show_bug.cgi?id=411339 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 390797] Feature request: macOS-like titlebar proxy icon
https://bugs.kde.org/show_bug.cgi?id=390797 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405035] Provide "Switch to next/previous activity" actions
https://bugs.kde.org/show_bug.cgi?id=405035 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 405033] Manual sorting of activities
https://bugs.kde.org/show_bug.cgi?id=405033 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368421] With menubar hidden, the "Control" toolbar button is unalterable, unlike all other toolbar buttons
https://bugs.kde.org/show_bug.cgi?id=368421 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kunitconversion] [Bug 409077] Unit Converter to comma-separate large values
https://bugs.kde.org/show_bug.cgi?id=409077 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx --- Comment #1 from Eridani Rodríguez --- That may work on the USA, but the rest of the world mostly use comma on the line [,] to separate from decimal units so the notation may become messy if not handled with care; below a copy pasta from ISO 8601 E norm: "If a decimal fraction is included, lower order components (if any) shall be omitted and the decimal fraction shall be divided from the integer part by the decimal sign specified in ISO 31-0: i.e. the comma [,] or full stop [.]. Of these, the comma is the preferred sign." But there are also some weird notations on certain countries (e.g. México), where while using the SI they use full stop [.] to separate decimal units (like USA). Therefore, it is recommended to just use space [ ] to separate groups of 3 numbers for better readability on a numeric notation and never use comma [,] or full stop [.] as these are reserved for decimal units. For example, one million (100) may be written as 1 000 000 for better readability. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kjobwidgets] [Bug 408795] New: Progress window should appear on top of current window instead of behind it.
https://bugs.kde.org/show_bug.cgi?id=408795 Bug ID: 408795 Summary: Progress window should appear on top of current window instead of behind it. Product: frameworks-kjobwidgets Version: 5.59.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- Created attachment 120922 --> https://bugs.kde.org/attachment.cgi?id=120922&action=edit Video showing the steps to reproduce. SUMMARY With Plasma 5.16 update, task progress feedback (move, copy, delete, etc.) was moved from the notification area to a floating independent window. This window currently appears behind the window that fired the action which causes that the user could miss it easily, this may provoke the user to invoke the action many times until he finally realizes that the process was already running but he just missed it. STEPS TO REPRODUCE 1. Go to Dolphin file manager 2. Pick some large file 3. Right click it and select "Copy" 4. Navigate to some other folder 5. "Paste" the file. OBSERVED RESULT 1. Progress window will appear behind the current Dolphin window. 2. This erratic behaviour may become unnoticed if you paste the file on the same folder that you copied it from; because then a dialog to rename the file will be displayed, this dialog changes the "z-index" of the child (Progress) window, placing it either in front of Dolphin's window or in the centre of the screen. EXPECTED RESULT Progress window should be easily noticeable by the user, either sticking it to the front or temporarily rising it to the front. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.15.0-51-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz Memory: 15.6 GiB ADDITIONAL INFORMATION I suspect that this affects also the Compression progress window (Ark & Dolphin) but may not be easily noticeable because you have to pick a name in most cases. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 408716] Subsequent "Get New" things in System Settings display items from the first search.
https://bugs.kde.org/show_bug.cgi?id=408716 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408716] New: Subsequent "Get New" things in System Settings display items from the first search.
https://bugs.kde.org/show_bug.cgi?id=408716 Bug ID: 408716 Summary: Subsequent "Get New" things in System Settings display items from the first search. Product: systemsettings Version: 5.16.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- SUMMARY When wanting to install customizations trough System Settings "Get New ..." buttons. The window to download stuff always shows the items from the first category you opened the "Download New ..." for. (Free translation as my system isn't in english) STEPS TO REPRODUCE 1. Open System Settings and navigate to Color schemes section, hit "Get new ..." button. 2. Close the "Download new ..." window 3. Navigate to Workspace themes and hit the "Get new ..." button OBSERVED RESULT 1. The window will display the search for color schemes 2. Same happen the other way around and with other sections combinations (Icons & Cursors, Cursors & Colors, etc.), it always shows the first thing you searched for. 3. Desktop Effects, SDDM and Start Up themes doesn't seem to be affected. EXPECTED RESULT It should show the results for the current category. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.15.0-51-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz Memory: 15.6 GiB ADDITIONAL INFORMATION I think this bug was introduced with the recent update to Plasma 5.16 because I don't recall experiencing it in 5.15. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408627] New: System Settings crash when trying to navigate to Touchpad configuration.
https://bugs.kde.org/show_bug.cgi?id=408627 Bug ID: 408627 Summary: System Settings crash when trying to navigate to Touchpad configuration. Product: systemsettings Version: 5.16.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- Application: systemsettings5 (5.16.0) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.15.0-51-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Tried to open touchpad settings panel on system settings but it crashed inmediately when clicking said entry. The crash can be reproduced every time. -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdfdefaf680 (LWP 25393))] Thread 9 (Thread 0x7fdfa0ac8700 (LWP 25416)): #0 0x7fdfd594fed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fdfa0ac7ba0, expected=0, futex_word=0x5625802080c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fdfa0ac7c60, mutex=0x562580208070, cond=0x562580208098) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x562580208098, mutex=0x562580208070, abstime=0x7fdfa0ac7c60) at pthread_cond_wait.c:667 #3 0x7fdfdac3ed36 in QWaitConditionPrivate::wait_relative (this=0x562580208070, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x562580208070) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=, mutex=0x5625801562a0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7fdfdac3f096 in QWaitCondition::wait (this=this@entry=0x562580207fe0, mutex=mutex@entry=0x5625801562a0, time=) at thread/qwaitcondition_unix.cpp:209 #7 0x7fdfdac3c740 in QThreadPoolThread::run (this=0x562580207fd0) at thread/qthreadpool.cpp:139 #8 0x7fdfdac37c72 in QThreadPrivate::start (arg=0x562580207fd0) at thread/qthread_unix.cpp:361 #9 0x7fdfd59496db in start_thread (arg=0x7fdfa0ac8700) at pthread_create.c:463 #10 0x7fdfda53788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fdfa12c9700 (LWP 25415)): #0 0x7fdfd594fed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fdfa12c8ba0, expected=0, futex_word=0x562580207f54) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fdfa12c8c60, mutex=0x562580207f00, cond=0x562580207f28) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x562580207f28, mutex=0x562580207f00, abstime=0x7fdfa12c8c60) at pthread_cond_wait.c:667 #3 0x7fdfdac3ed36 in QWaitConditionPrivate::wait_relative (this=0x562580207f00, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x562580207f00) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=, mutex=0x5625801562a0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7fdfdac3f096 in QWaitCondition::wait (this=this@entry=0x562580207e70, mutex=mutex@entry=0x5625801562a0, time=) at thread/qwaitcondition_unix.cpp:209 #7 0x7fdfdac3c740 in QThreadPoolThread::run (this=0x562580207e60) at thread/qthreadpool.cpp:139 #8 0x7fdfdac37c72 in QThreadPrivate::start (arg=0x562580207e60) at thread/qthread_unix.cpp:361 #9 0x7fdfd59496db in start_thread (arg=0x7fdfa12c9700) at pthread_create.c:463 #10 0x7fdfda53788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fdfa1aca700 (LWP 25414)): #0 0x7fdfd594fed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fdfa1ac9ba0, expected=0, futex_word=0x562580207c84) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fdfa1ac9c60, mutex=0x562580207c30, cond=0x562580207c58) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x562580207c58, mutex=0x562580207c30, abstime=0x7fdfa1ac9c60) at pthread_cond_wait.c:667 #3 0x7fdfdac3ed36 in QWaitConditionPrivate::wait_relative (this=0x562580207c30, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x562580207c30) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=, mutex=0x5625801562a0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7fdfdac3f096 in QWaitCondition::wait (this=this@entry=0x562580207ba0, mutex=mutex@entry=0x5625801562a0, time=) at thread/qwaitcondition_unix.cpp:209 #7 0x7fdfdac3c740 in QThreadPoolThread::run (this=0x562580207b90) at thread/qthreadpool.cpp:139 #8
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401987] Some notifications become not interactive once in the history widget.
https://bugs.kde.org/show_bug.cgi?id=401987 --- Comment #2 from Eridani Rodríguez --- But some other notifications like when you take a screenshot with Spectacle, maintain their interactive behaviour even in the history. Why is there a difference? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 401987] Some notifications become not interactive once in the history widget.
https://bugs.kde.org/show_bug.cgi?id=401987 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 401987] New: Some notifications become not interactive once in the history widget.
https://bugs.kde.org/show_bug.cgi?id=401987 Bug ID: 401987 Summary: Some notifications become not interactive once in the history widget. Product: frameworks-knotifications Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: eridanired...@yahoo.com.mx CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Some notifications (like those from websites opened in Firefox) are interactive only when they popup, and lose their "interactiveness" if you don't click on them at that time, once they are in the notification history they doesn't fire any action if you click on them. STEPS TO REPRODUCE 1. Open http://www.bennish.net/web-notifications.html in Firefox 2. Click "Show in 5s" 3. Open a Dolphin window or anything, just navigate away from that browser tab OBSERVED RESULT 4. The notification will appear in 5 seconds, if you click it it will take you to the website above. 5. If you don't click it it will disappear in a few seconds, now try clicking it in the Notifications history, it won't do anything. EXPECTED RESULT It should still take you to the website even if you click it in the notification history widget. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.14 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION May be related to https://bugs.kde.org/show_bug.cgi?id=364798 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 364798] knotifications processes clicks wrong
https://bugs.kde.org/show_bug.cgi?id=364798 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401552] Dolphin crash when renaming a file
https://bugs.kde.org/show_bug.cgi?id=401552 Eridani Rodríguez changed: What|Removed |Added Summary|Isolated Dolphin crash when |Dolphin crash when renaming |renaming a file |a file -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401552] Isolated Dolphin crash when renaming a file
https://bugs.kde.org/show_bug.cgi?id=401552 --- Comment #1 from Eridani Rodríguez --- Created attachment 116576 --> https://bugs.kde.org/attachment.cgi?id=116576&action=edit New crash information added by DrKonqi dolphin (18.08.3) using Qt 5.11.2 - What I was doing when the application crashed: Was renaming more folders, adding underscore at the end of the folder like this: MyFolder_ -- Backtrace (Reduced): #6 std::__atomic_base::operator++ (this=0x1) at /usr/include/c++/7/bits/atomic_base.h:296 #7 QAtomicOps::ref (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:265 [...] #9 QUrl::QUrl (this=0x7ffe5d27bdb8, other=...) at io/qurl.cpp:1876 #10 0x7ff5be0f8ee5 in KFileItem::url (this=this@entry=0x7ffe5d27bda8) at ./src/core/kfileitem.cpp:1387 #11 0x7ff5be1a9473 in KCoreDirListerCache::renameDir (this=this@entry=0x7ff5be417280 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, oldUrl=..., newUrl=...) at ./src/core/kcoredirlister.cpp:1579 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401552] Isolated Dolphin crash when renaming a file
https://bugs.kde.org/show_bug.cgi?id=401552 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401552] New: Isolated Dolphin crash when renaming a file
https://bugs.kde.org/show_bug.cgi?id=401552 Bug ID: 401552 Summary: Isolated Dolphin crash when renaming a file Product: dolphin Version: 18.08.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: eridanired...@yahoo.com.mx CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.08.3) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.15.0-39-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: I had a Dolphin window with 4 tabs open with diferent directories when I tried to rename a directory insde a tab Dolphin crashed, this folder wasn't opened on any of those tabs. Tried to reproduce the crash even with the same folders, but couldn't. The crash does not seem to be reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f24db633800 (LWP 3216))] Thread 3 (Thread 0x7f24b0da3700 (LWP 3290)): #0 0x7f24daebdbf9 in __GI___poll (fds=0x7f24ac0049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f24cd709539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f24cd70964c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f24d50a004b in QEventDispatcherGlib::processEvents (this=0x7f24ac000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f24d504430a in QEventLoop::exec (this=this@entry=0x7f24b0da2da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f24d4e6fbba in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f24d4e7aadb in QThreadPrivate::start (arg=0x55c71ae670e0) at thread/qthread_unix.cpp:367 #7 0x7f24cfaf16db in start_thread (arg=0x7f24b0da3700) at pthread_create.c:463 #8 0x7f24daeca88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f24c090e700 (LWP 3230)): #0 0x7f24daeb90b4 in __GI___libc_read (fd=7, buf=0x7f24c090db60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f24cd74dcd0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f24cd709027 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f24cd7094e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f24cd70964c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f24d50a004b in QEventDispatcherGlib::processEvents (this=0x7f24b4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f24d504430a in QEventLoop::exec (this=this@entry=0x7f24c090dd70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #7 0x7f24d4e6fbba in QThread::exec (this=) at thread/qthread.cpp:525 #8 0x7f24d54e6e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f24d4e7aadb in QThreadPrivate::start (arg=0x7f24d575ed60) at thread/qthread_unix.cpp:367 #10 0x7f24cfaf16db in start_thread (arg=0x7f24c090e700) at pthread_create.c:463 #11 0x7f24daeca88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f24db633800 (LWP 3216)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x81) at /usr/include/c++/7/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x81) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 #9 QtPrivate::RefCount::ref (this=0x81) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55 #10 QString::QString (other=..., this=0x7ffe4edc7700) at ../../include/QtCore/../../src/corelib/tools/qstring.h:953 #11 QUrlPrivate::appendPath (this=0x55c71aff0bc0, appendTo=..., options=..., appendingTo=QUrlPrivate::Path) at io/qurl.cpp:960 #12 0x7f24d4f99d58 in QUrl::path (this=this@entry=0x7ffe4edc7898, options=...) at io/qurl.cpp:2615 #13 0x7f24d4f99da4 in QUrl::fileName (this=this@entry=0x7ffe4edc7898, options=..., options@entry=...) at io/qurl.cpp:2678 #14 0x7f24d9670490 in KCoreDirListerCache::renameDir (this=this@entry=0x7f24d98de280 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, oldUrl=..., newUrl=...) at ./src/core/kcoredirlister.cpp:1581 #15 0x7f24d967243f in KCoreDirListerCache::slotFileRenamed (this=0x7f24d98de280 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, _src=..., _dst=..., dstPath=...) at ./src/core/kcoredirlister.cpp:969 #16 0x7f24d507518f in QtPrivate::QSlotObjectBase::call (a=0x7ffe4edc7b20, r=0x7f24d98de280 <(anonymo
[ksmserver] [Bug 401447] New: ksmserver-logout-greeter crash after graphics driver update
https://bugs.kde.org/show_bug.cgi?id=401447 Bug ID: 401447 Summary: ksmserver-logout-greeter crash after graphics driver update Product: ksmserver Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: ui Assignee: unassigned-b...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- SUMMARY After updating graphic drivers when trying to reboot the PC the logout dialog crashed. STEPS TO REPRODUCE 1. Updated nVidia driver 410 2. Tried to logout to reboot PC 3. Couldn't because the screen with logout options crashed. EXPECTED RESULT Would be possible to reboot using the regular GUI method SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.14 Kernel: 4.15.0-39-generic KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 nVidia driver: 410.73 BACKTRACE Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe62caabd80 (LWP 9878))] Thread 3 (Thread 0x7fe60e424700 (LWP 9881)): #0 0x7fe6282dfbf9 in __GI___poll (fds=0x7fe604004a00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe620e76539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe620e7664c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe628c1a04b in QEventDispatcherGlib::processEvents (this=0x7fe604000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fe628bbe30a in QEventLoop::exec (this=this@entry=0x7fe60e423d40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7fe6289e9bba in QThread::exec (this=this@entry=0x563a12a61a50) at thread/qthread.cpp:525 #6 0x7fe62ac364f5 in QQmlThreadPrivate::run (this=0x563a12a61a50) at qml/ftw/qqmlthread.cpp:148 #7 0x7fe6289f4adb in QThreadPrivate::start (arg=0x563a12a61a50) at thread/qthread_unix.cpp:367 #8 0x7fe622e086db in start_thread (arg=0x7fe60e424700) at pthread_create.c:463 #9 0x7fe6282ec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fe614f2a700 (LWP 9880)): #0 0x7fe6282db0b4 in __GI___libc_read (fd=7, buf=0x7fe614f29b20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fe620ebacd0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe620e76027 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe620e764e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe620e7664c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe628c1a04b in QEventDispatcherGlib::processEvents (this=0x7fe608000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fe628bbe30a in QEventLoop::exec (this=this@entry=0x7fe614f29d30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #7 0x7fe6289e9bba in QThread::exec (this=) at thread/qthread.cpp:525 #8 0x7fe629807e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7fe6289f4adb in QThreadPrivate::start (arg=0x7fe629a7fd60) at thread/qthread_unix.cpp:367 #10 0x7fe622e086db in start_thread (arg=0x7fe614f2a700) at pthread_create.c:463 #11 0x7fe6282ec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fe62caabd80 (LWP 9878)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7fe62820b801 in __GI_abort () at abort.c:79 #8 0x7fe6289c55db in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1842 #9 QMessageLogger::fatal (this=this@entry=0x7ffde1ac50f0, msg=msg@entry=0x7fe62b5337d6 "%s") at global/qlogging.cpp:880 #10 0x7fe62b34220d in QSGRenderLoop::handleContextCreationFailure (this=this@entry=0x563a12a78cb0, window=0x563a12a61c50, isEs=) at scenegraph/qsgrenderloop.cpp:274 #11 0x7fe62b342ffd in QSGGuiThreadRenderLoop::renderWindow (this=this@entry=0x563a12a78cb0, window=) at scenegraph/qsgrenderloop.cpp:375 #12 0x7fe62b343d9a in QSGGuiThreadRenderLoop::exposureChanged (this=0x563a12a78cb0, window=) at scenegraph/qsgrenderloop.cpp:481 #13 0x7fe62915c745 in QWindow::event (this=this@entry=0x563a12a61c50, ev=ev@entry=0x7ffde1ac55a0) at kernel/qwindow.cpp:2334 #14 0x7fe62b3bd1a5 in QQuickWindow::event (this=0x563a12a61c50, e=0x7ffde1ac55a0) at items/qquickwindow.cpp:1634 #15 0x563a126b5f91 in KSMShutdownDlg::event (this=0x563a12a61c50, e=0x7ffde1ac55a0) at ./ksmserver/logout-greeter/shutdowndlg.cpp:223 #16 0x7fe629de0e1c in QApplicationPrivate::notify_helper (this=this@entry=0x563a129f9c70, receiver=receiver@entry=0x563a12a61c50, e=e@entry=0x7ffde1ac55a0) at kernel/qapplication.cpp:3727 #17 0x7fe629de83ef in QApplication::noti
[elisa] [Bug 401383] New: Elisa crash after deleting Music forlder from library.
https://bugs.kde.org/show_bug.cgi?id=401383 Bug ID: 401383 Summary: Elisa crash after deleting Music forlder from library. Product: elisa Version: 0.3.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: eridanired...@yahoo.com.mx Target Milestone: --- Application: elisa (0.3.0) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.15.0-39-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: 1. Set Music forlder for Elisa 2. Wait for the library to update 3. Added Pictures folder too 4. Deleted Music folder from the list as I wanted a way to purge the database 5. Nothing was purged so I scrolled down to see if maybe the bottom items where being deleted. 6. Couldn't scroll too much as Elisa crashed. The crash can be reproduced every time. -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fca9d9b6800 (LWP 16528))] Thread 12 (Thread 0x7f8a2bfff700 (LWP 16764)): #0 0x7fca9a4420b4 in __GI___libc_read (fd=59, buf=0x7f8a2bffeb70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fca940e8cd0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fca940a4027 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fca940a44e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fca940a464c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fca9ad8104b in QEventDispatcherGlib::processEvents (this=0x7f8a2b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fca9ad2530a in QEventLoop::exec (this=this@entry=0x7f8a2bffed80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #7 0x7fca9ab50bba in QThread::exec (this=this@entry=0x556dbdc72670) at thread/qthread.cpp:525 #8 0x7fca9c6f14f5 in QQmlThreadPrivate::run (this=0x556dbdc72670) at qml/ftw/qqmlthread.cpp:148 #9 0x7fca9ab5badb in QThreadPrivate::start (arg=0x556dbdc72670) at thread/qthread_unix.cpp:367 #10 0x7fca963906db in start_thread (arg=0x7f8a2bfff700) at pthread_create.c:463 #11 0x7fca9a45388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f8a3141c700 (LWP 16634)): #0 0x7fca96396ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f8a3141bc30, expected=0, futex_word=0x556dbc25bc80) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f8a3141bd00, mutex=0x556dbc25bc30, cond=0x556dbc25bc58) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x556dbc25bc58, mutex=0x556dbc25bc30, abstime=0x7f8a3141bd00) at pthread_cond_wait.c:667 #3 0x7fca9ab5c880 in QWaitConditionPrivate::wait_relative (time=3, this=0x556dbc25bc30) at thread/qwaitcondition_unix.cpp:133 #4 QWaitConditionPrivate::wait (time=3, this=0x556dbc25bc30) at thread/qwaitcondition_unix.cpp:141 #5 QWaitCondition::wait (this=this@entry=0x7fca7801be60, mutex=mutex@entry=0x556dbbdbf080, time=3) at thread/qwaitcondition_unix.cpp:215 #6 0x7fca9ab5328d in QThreadPoolThread::run (this=0x7fca7801be50) at thread/qthreadpool.cpp:146 #7 0x7fca9ab5badb in QThreadPrivate::start (arg=0x7fca7801be50) at thread/qthread_unix.cpp:367 #8 0x7fca963906db in start_thread (arg=0x7f8a3141c700) at pthread_create.c:463 #9 0x7fca9a45388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fca41ecb700 (LWP 16633)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x40c96400) at /usr/include/c++/7/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x40c96400) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 #9 QtPrivate::RefCount::ref (this=0x40c96400) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55 #10 QString::QString (other=..., this=) at ../../include/QtCore/../../src/corelib/tools/qstring.h:953 #11 QFontEngineMulti::fallbackFamilyAt (at=, this=0x7fca38154cc0) at ../../include/QtGui/5.11.2/QtGui/private/../../../../../src/gui/text/qfontengine_p.h:484 #12 QFontEngineMulti::loadEngine (this=0x7fca38154cc0, at=) at text/qfontengine.cpp:1845 #13 0x7fca9b61290d in QFontEngineMulti::ensureEngineAt (this=this@entry=0x7fca38154cc0, at=at@entry=207) at text/qfontengine.cpp:1832 #14 0x7fca9b6457f2 in QTextLine::glyphRuns (this=this@entry=0x7fca41ec85c0, from=from@entry=0, length=) at text/qtextlayout.cpp:2355 #15 0x7
[elisa] [Bug 401383] Elisa crash after deleting Music forlder from library.
https://bugs.kde.org/show_bug.cgi?id=401383 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 400438] Akonadi IMAP resource crashes periodically: Segmentation fault (11)
https://bugs.kde.org/show_bug.cgi?id=400438 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 400438] New: Akonadi IMAP resource crashes periodically: Segmentation fault (11)
https://bugs.kde.org/show_bug.cgi?id=400438 Bug ID: 400438 Summary: Akonadi IMAP resource crashes periodically: Segmentation fault (11) Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- Created attachment 115958 --> https://bugs.kde.org/attachment.cgi?id=115958&action=edit Traceback: akonadi_imap_resource crash Segmentation fault (11) SUMMARY Some times when I'm doing my stuff akonadi_imap_resource crashes, I don't notice until I see my notifications history, there I found it crashed. I still get new mails automatically though, so I assume that it relaunches itself after having crashed? Have 2 accounts configured on KMail, Gmail and Yahoo. Problem started after upgrading KDE Neon from Xenial based to Bionic based. STEPS TO REPRODUCE 1. No idea 2. Probably when KMail is auto checking for new IMAP messages since everything goes OK when manually refreshing. OBSERVED RESULT Got a notification about it having crashed, otherwise I wouldn't even notice. SOFTWARE VERSIONS KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51..0 Qt Version: 5.11.2 Kernel: 4.15.0-38-generic akonadiserver: 5.9.2 libkf5imap5 Version: 18.08.2-0xneon+18.04+bionic+build11 akonadi-server: 4:18.08.2-0xneon+18.04+bionic+build13 ADDITIONAL INFORMATION Trace back log attached. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400431] Discover complains about Appstream possibly not being properly set up.
https://bugs.kde.org/show_bug.cgi?id=400431 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400431] New: Discover complains about Appstream possibly not being properly set up.
https://bugs.kde.org/show_bug.cgi?id=400431 Bug ID: 400431 Summary: Discover complains about Appstream possibly not being properly set up. Product: Discover Version: 5.14.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- Created attachment 115952 --> https://bugs.kde.org/attachment.cgi?id=115952&action=edit initial debug output from "appstreamcli status --verbose" SUMMARY Upon launching Discover, a notification is shown with the following text: "Please make sure that Appstream is properly set up in your system" (Free translation) SOFTWARE VERSIONS KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 OS: KDE neon 5.14 Kernel: 4.15.0-38-generic AppStream version: 0.12.2 ADDITIONAL INFORMATION - When updating or upgrading packages from apt or Synaptic, no error is found. - Attached file with initial debug output from "appstreamcli status --verbose" -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 399643] Can't open vaults stored outside default path anymore
https://bugs.kde.org/show_bug.cgi?id=399643 --- Comment #4 from Eridani Rodríguez --- Awesome, thanks Ivan! -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 399643] Can't open vaults stored outside default path anymore
https://bugs.kde.org/show_bug.cgi?id=399643 Eridani Rodríguez changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Eridani Rodríguez --- EncFS 1.9.1-4+16.04+xenial+build4 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 399643] Can't open vaults stored outside default path anymore
https://bugs.kde.org/show_bug.cgi?id=399643 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 399643] New: Can't open vaults stored outside default path anymore
https://bugs.kde.org/show_bug.cgi?id=399643 Bug ID: 399643 Summary: Can't open vaults stored outside default path anymore Product: Plasma Vault Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- SUMMARY After upgrading from Plasma 5.13 to 5.14 on KDE Neon 5.13 (still Xenial based), accessing Plasma Vaults stored outside "~/.local/share/plasma-vault" became impossible. I keep my Vaults stored on an external HDD so I can use them at home and work. I used to just symlink the data to the default directory on both systems but today updated my home PC and couldn't access them any more. Even modifying "~/.config/plasmavaultrc" with the real paths doesn't work. STEPS TO REPRODUCE 1. Create a Vault 2. Move it outside "~/.local/share/plasma-vault" lets say, to your desktop. 3. Symlink it back so it keep appearing in the plasmoid lists next login 4. Log out and log back in 5. Try mounting it OBSERVED RESULT Vault fails to mount (without giving any feedback btw) EXPECTED RESULT Vault should be mounted normally SOFTWARE VERSIONS KDE Plasma Version: 5.14.0 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395676] Discover crash calligra_stencil.knsrc All categories are missing
https://bugs.kde.org/show_bug.cgi?id=395676 --- Comment #1 from Eridani Rodríguez --- Probably related to https://bugs.kde.org/show_bug.cgi?id=390922 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395676] New: Discover crash calligra_stencil.knsrc All categories are missing
https://bugs.kde.org/show_bug.cgi?id=395676 Bug ID: 395676 Summary: Discover crash calligra_stencil.knsrc All categories are missing Product: Discover Version: 5.13.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- Application: plasma-discover (5.13.1) Qt Version: 5.11.0 Frameworks Version: 5.47.0 Operating System: Linux 4.15.0-15-lowlatency x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: - Install Calligra - Launch Discover again - Pick an item from the left pane - Crash - Custom settings of the application: Flatpak and snap integration ennabled The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5c7ff2c900 (LWP 2614))] Thread 16 (Thread 0x7f5c02136700 (LWP 2693)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f5c75dbacfa in g_cond_wait_until () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5c75d4a999 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5c75d4afbb in g_async_queue_timeout_pop () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5c75d9d60a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f5c75d9cbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f5c77ca46ba in start_thread (arg=0x7f5c02136700) at pthread_create.c:333 #7 0x7f5c7b20641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f5c1e9fd700 (LWP 2637)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f5c7bc0355f in QWaitConditionPrivate::wait_relative (time=3, this=0x3af8390) at thread/qwaitcondition_unix.cpp:133 #2 QWaitConditionPrivate::wait (time=3, this=0x3af8390) at thread/qwaitcondition_unix.cpp:141 #3 QWaitCondition::wait (this=this@entry=0x3af7c70, mutex=mutex@entry=0x26c7ef0, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7f5c7bbf8e8a in QThreadPoolThread::run (this=0x3af7c60) at thread/qthreadpool.cpp:146 #5 0x7f5c7bc02727 in QThreadPrivate::start (arg=0x3af7c60) at thread/qthread_unix.cpp:367 #6 0x7f5c77ca46ba in start_thread (arg=0x7f5c1e9fd700) at pthread_create.c:333 #7 0x7f5c7b20641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7f5c1f1fe700 (LWP 2636)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f5c7bc0355f in QWaitConditionPrivate::wait_relative (time=3, this=0x3af73c0) at thread/qwaitcondition_unix.cpp:133 #2 QWaitConditionPrivate::wait (time=3, this=0x3af73c0) at thread/qwaitcondition_unix.cpp:141 #3 QWaitCondition::wait (this=this@entry=0x294a9b0, mutex=mutex@entry=0x26c7ef0, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7f5c7bbf8e8a in QThreadPoolThread::run (this=0x294a9a0) at thread/qthreadpool.cpp:146 #5 0x7f5c7bc02727 in QThreadPrivate::start (arg=0x294a9a0) at thread/qthread_unix.cpp:367 #6 0x7f5c77ca46ba in start_thread (arg=0x7f5c1f1fe700) at pthread_create.c:333 #7 0x7f5c7b20641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f5c2d1fe700 (LWP 2634)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5c7bc035cb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x37a14f0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x3715528, mutex=mutex@entry=0x3715520, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f5c7f0bfafd in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x3715518) at scenegraph/qsgthreadedrenderloop.cpp:245 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x37154a0) at scenegraph/qsgthreadedrenderloop.cpp:709 #5 0x7f5c7f0bff81 in QSGRenderThread::run (this=0x37154a0) at scenegraph/qsgthreadedrenderloop.cpp:738 #6 0x7f5c7bc02727 in QThreadPrivate::start (arg=0x37154a0) at thread/qthread_unix.cpp:367 #7 0x7f5c77ca46ba in start_thread (arg=0x7f5c2d1fe700) at pthread_create.c:333 #8 0x7f5c7b20641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f5c2ddde700 (LWP 2633)): #0 0x7f5c7b1fa74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f5c75d7638c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5c75d7649c in g_main_context_iteration ()
[Discover] [Bug 395676] Discover crash calligra_stencil.knsrc All categories are missing
https://bugs.kde.org/show_bug.cgi?id=395676 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 395617] Plasmoids scrollbars not work with Wacom Pen
https://bugs.kde.org/show_bug.cgi?id=395617 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx --- Comment #1 from Eridani Rodríguez --- Can confirm this erratic behavior being present on my system with the same Wacom model as OP. 2 more users with different hardware in the KDE Neon Telegram support group said to be affected too: https://t.me/kdeneon/55101 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 395500] Broken IMAP syncing when retrieving corrupted email
https://bugs.kde.org/show_bug.cgi?id=395500 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 395500] New: Broken IMAP syncing when retrieving corrupted email
https://bugs.kde.org/show_bug.cgi?id=395500 Bug ID: 395500 Summary: Broken IMAP syncing when retrieving corrupted email Product: Akonadi Version: 5.8.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- Created attachment 113383 --> https://bugs.kde.org/attachment.cgi?id=113383&action=edit Akonadi Debugger log + Yahoo web interface html headers and screenshot. Overview: When synchronizing an IMAP folder from Yahoo Mail the process is interrupted if a corrupted e-mail is currently in the server making it impossible to continue receiving further messages from said folder. It is still possible to respond and manage all previously synced mails but no further mail is received. (After a few hours of manually moving my mails on Yahoo's web interface I found the culprit and isolated it, but can't send it or do anything else with it aside from moving it from folder to folder or delete it.) Steps to Reproduce: 1) Configure an IMAP account and start syncing. 2) Be unlucky enough to have a corrupted message. Actual Results: Sync is interrupted and no further messages are retrieved from server, unless the faulty message is manually identified and removed from server. Expected Results: Should be possible to keep sync going even if skipping the faulty mail. Build Date & Platform: Unsure & KDE neon 5.13 Additional Information: akonadictl 5.8.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 269367] There is no way to search in hidden folders now.
https://bugs.kde.org/show_bug.cgi?id=269367 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394772] Some GTK apps temporarily lose scroll focus while desktop notification are shown
https://bugs.kde.org/show_bug.cgi?id=394772 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394772] New: Some GTK apps temporarily lose scroll focus while desktop notification are shown
https://bugs.kde.org/show_bug.cgi?id=394772 Bug ID: 394772 Summary: Some GTK apps temporarily lose scroll focus while desktop notification are shown Product: plasmashell Version: 5.12.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: eridanired...@yahoo.com.mx CC: plasma-b...@kde.org Target Milestone: 1.0 Overview: Some GTK applications lose focus when a desktop notification is displayed Tested and affected: - File-roller 3.16.5-0 - Synaptic 0.83 - Snapper GUI (master) - Meld 3.14.2 - Remarkable 1.87 Tested and not affected: - Gmusicbrowser - PlayOnLinux - Shotwell - GIMP Steps to Reproduce: 1) Play some music. 2) Open any of the listed programs and navigate to a window with enough content to get a scrollbar. 3) Scroll up and down while waiting for the track change notification. Actual Results: Focus is lost while the notification stays visible. Expected Results: Should be possible to keep scrolling like in most other programs. Build Date & Platform: Unsure & KDE neon 5.12 Additional Information: KDE Frameworks 5.46.0 Plasma 5.12.5 Qt 5.10.0 X Server 1.19.5 Proprietary nVidia drivers 390.59 GeForce GTX 1060 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 353886] SystemSettings - shortcuts and gestures
https://bugs.kde.org/show_bug.cgi?id=353886 --- Comment #2 from Eridani Rodríguez --- Comment on attachment 112491 --> https://bugs.kde.org/attachment.cgi?id=112491 New crash information added by DrKonqi >Application: systemsettings5 (5.12.5) > >Qt Version: 5.10.0 >Frameworks Version: 5.45.0 >Operating System: Linux 4.15.0-15-lowlatency x86_64 >Distribution: KDE neon User Edition 5.12 > >-- Information about the crash: >- Unusual behavior I noticed: > >systemsettings5 crashes when editing a previously saved custom shortcut. >Reproduce by: Creating a new custom group, add a few conditions and save it. >Then go back, edit the conditions and try saving it again to have it crash. > > >The crash can be reproduced every time. > >-- Backtrace: >Application: Preferencias del sistema (systemsettings5), signal: Segmentation >fault >Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". >[Current thread is 1 (Thread 0x7efe76c65900 (LWP 20612))] > >Thread 4 (Thread 0x7efe455af700 (LWP 20618)): >#0 0x7efe7277574d in poll () at ../sysdeps/unix/syscall-template.S:84 >#1 0x7efe6c61838c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >#2 0x7efe6c61849c in g_main_context_iteration () from >/lib/x86_64-linux-gnu/libglib-2.0.so.0 >#3 0x7efe730a85cb in QEventDispatcherGlib::processEvents >(this=0x7efe48c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 >#4 0x7efe7304f64a in QEventLoop::exec (this=this@entry=0x7efe455aeca0, >flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 >#5 0x7efe72e6f554 in QThread::exec (this=) at >thread/qthread.cpp:522 >#6 0x7efe709ada35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 >#7 0x7efe72e746eb in QThreadPrivate::start (arg=0x11d17e0) at >thread/qthread_unix.cpp:376 >#8 0x7efe6ebfe6ba in start_thread (arg=0x7efe455af700) at >pthread_create.c:333 >#9 0x7efe7278141d in clone () at >../sysdeps/unix/sysv/linux/x86_64/clone.S:109 > >Thread 3 (Thread 0x7efe4e11a700 (LWP 20617)): >#0 0x7efe6c65ca79 in g_mutex_lock () from >/lib/x86_64-linux-gnu/libglib-2.0.so.0 >#1 0x7efe6c617929 in g_main_context_prepare () from >/lib/x86_64-linux-gnu/libglib-2.0.so.0 >#2 0x7efe6c6182bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >#3 0x7efe6c61849c in g_main_context_iteration () from >/lib/x86_64-linux-gnu/libglib-2.0.so.0 >#4 0x7efe730a85cb in QEventDispatcherGlib::processEvents >(this=0x7efe480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 >#5 0x7efe7304f64a in QEventLoop::exec (this=this@entry=0x7efe4e119ca0, >flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 >#6 0x7efe72e6f554 in QThread::exec (this=) at >thread/qthread.cpp:522 >#7 0x7efe709ada35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 >#8 0x7efe72e746eb in QThreadPrivate::start (arg=0xe664a0) at >thread/qthread_unix.cpp:376 >#9 0x7efe6ebfe6ba in start_thread (arg=0x7efe4e11a700) at >pthread_create.c:333 >#10 0x7efe7278141d in clone () at >../sysdeps/unix/sysv/linux/x86_64/clone.S:109 > >Thread 2 (Thread 0x7efe593bc700 (LWP 20615)): >#0 0x7efe7277127d in read () at ../sysdeps/unix/syscall-template.S:84 >#1 0x7efe6c65b6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >#2 0x7efe6c617e74 in g_main_context_check () from >/lib/x86_64-linux-gnu/libglib-2.0.so.0 >#3 0x7efe6c618330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >#4 0x7efe6c61849c in g_main_context_iteration () from >/lib/x86_64-linux-gnu/libglib-2.0.so.0 >#5 0x7efe730a85cb in QEventDispatcherGlib::processEvents >(this=0x7efe540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 >#6 0x7efe7304f64a in QEventLoop::exec (this=this@entry=0x7efe593bbc90, >flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 >#7 0x7efe72e6f554 in QThread::exec (this=) at >thread/qthread.cpp:522 >#8 0x7efe749882c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 >#9 0x7efe72e746eb in QThreadPrivate::start (arg=0x7efe74bfcd60) at >thread/qthread_unix.cpp:376 >#10 0x7efe6ebfe6ba in start_thread (arg=0x7efe593bc700) at >pthread_create.c:333 >#11 0x7efe7278141d in clone () at >../sysdeps/unix/sysv/linux/x86_64/clone.S:109 > >Thread 1 (Thread 0x7efe76c65900 (LWP 20612)): >[KCrash Handler] >#6 0x0021 in ?? () >#7 0x7efe3c6adafe in >qDeleteAll::const_iterator> (end=..., begin=...) >at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:320 >#8 qDeleteAll (c=...) at >/usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:328 >#9 ConditionsWidget::copyToObject (this=0x26d2410) at >/workspace/build/k
[systemsettings] [Bug 353886] SystemSettings - shortcuts and gestures
https://bugs.kde.org/show_bug.cgi?id=353886 --- Comment #1 from Eridani Rodríguez --- Created attachment 112491 --> https://bugs.kde.org/attachment.cgi?id=112491&action=edit New crash information added by DrKonqi systemsettings5 (5.12.5) using Qt 5.10.0 - Unusual behavior I noticed: systemsettings5 crashes when editing a previously saved custom shortcut. -- Backtrace (Reduced): #7 0x7efe3c6adafe in qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:320 #8 qDeleteAll (c=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:328 #9 ConditionsWidget::copyToObject (this=0x26d2410) at /workspace/build/kcm_hotkeys/conditions/conditions_widget.cpp:177 #10 0x7efe3c6b11fd in HotkeysWidgetBase::apply (this=0x26d9880) at /workspace/build/kcm_hotkeys/hotkeys_widget_base.cpp:46 #11 0x7efe3c695b63 in KCMHotkeysPrivate::save (this=0x26b9cc0) at /workspace/build/kcm_hotkeys/kcm_hotkeys.cpp:397 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 353886] SystemSettings - shortcuts and gestures
https://bugs.kde.org/show_bug.cgi?id=353886 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
