[systemsettings] [Bug 476638] If the name of shared library ends with digit from 1 to 9, Plasma recognizes it as manual page, and one can't change it using GUI
https://bugs.kde.org/show_bug.cgi?id=476638 --- Comment #4 from Łukasz Konieczny --- I don't know how, but now, after I have reset both file type associations, this bug is not present. Perhaps I had some old settings (I have fought with this bug earlier). I'm closing this bug report. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476638] If the name of shared library ends with digit from 1 to 9, Plasma recognizes it as manual page, and one can't change it using GUI
https://bugs.kde.org/show_bug.cgi?id=476638 --- Comment #3 from Łukasz Konieczny --- Software versions: Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-10-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: System76 Product Name: Darter Pro System Version: darp7 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476638] If the name of shared library ends with digit from 1 to 9, Plasma recognizes it as manual page, and one can't change it using GUI
https://bugs.kde.org/show_bug.cgi?id=476638 --- Comment #2 from Łukasz Konieczny --- Created attachment 162914 --> https://bugs.kde.org/attachment.cgi?id=162914=edit And example of correctly depicted library -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476638] If the name of shared library ends with digit from 1 to 9, Plasma recognizes it as manual page, and one can't change it using GUI
https://bugs.kde.org/show_bug.cgi?id=476638 --- Comment #1 from Łukasz Konieczny --- Created attachment 162913 --> https://bugs.kde.org/attachment.cgi?id=162913=edit Example of library depicted as manual page -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476638] New: If the name of shared library ends with digit from 1 to 9, Plasma recognizes it as manual page, and one can't change it using GUI
https://bugs.kde.org/show_bug.cgi?id=476638 Bug ID: 476638 Summary: If the name of shared library ends with digit from 1 to 9, Plasma recognizes it as manual page, and one can't change it using GUI Classification: Applications Product: systemsettings Version: 5.27.9 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_filetypes Assignee: plasma-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: fa...@kde.org Target Milestone: --- Created attachment 162911 --> https://bugs.kde.org/attachment.cgi?id=162911=edit Many libraries are depicted as manual pages SUMMARY *** The wrong file association (and icon) of shared libraries which names end with .[1-9] is somewhat hardcoded in Plasma and it is not possible to change it, no matter what you would do in GUI. They are presented as manual pages, despite file command shows they are shared libraries. I have tried: 1. removing pattern *.[1-9] from application/x-troff-man association 2. adding pattern *.so.*.[0-9] to application/x-sharedlib association. It doesn't work. I suspect there is some fundamental problem with kcm_filetypes, which prevents an ordinary user from doing whatever they want with file associations. You can see in attached screenshots what have I done and how still wrongly Dolphin shows shared libraries for example in /usr/lib/x86_64-linux-gnu/ *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 471870] New: Sometimes the NetworkManager applet doesn't appear after resuming from suspend and is not reachable unless suspend and resume again
https://bugs.kde.org/show_bug.cgi?id=471870 Bug ID: 471870 Summary: Sometimes the NetworkManager applet doesn't appear after resuming from suspend and is not reachable unless suspend and resume again Classification: Plasma Product: plasma-nm Version: 5.27.6 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- Created attachment 160044 --> https://bugs.kde.org/attachment.cgi?id=160044=edit NM applet is not visible anywhere after resume SUMMARY There is a problem with NetworkManager applet in tray. It happens frequently (but not always), that this applet doesn't appear after resuming from suspend to RAM. I have attached a screenshot of such situation. As you can see, there is no NM applet either in tray or in the slid-up applet with other tray items. STEPS TO REPRODUCE 1. Suspend system to RAM. 2. Resume from suspend. 3. Do points 1 and 2 until NM applet dies. 4. If it dies, suspend again and resume, NM applet most likely will reappear. OBSERVED RESULT Sometimes NM applet is not reachable after resuming. EXPECTED RESULT NM applet is always visible in the system. SOFTWARE/OS VERSIONS GNU/Linux, KDE Plasma: (available in About System) Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-24-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: System76 Product Name: Darter Pro System Version: darp7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 466106] Don't register MPRIS interface when not doing anything controllable by MPRIS
https://bugs.kde.org/show_bug.cgi?id=466106 Łukasz Konieczny changed: What|Removed |Added Version|22.12.2 |23.04.2 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 466106] Don't register MPRIS interface when not doing anything controllable by MPRIS
https://bugs.kde.org/show_bug.cgi?id=466106 Łukasz Konieczny changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from Łukasz Konieczny --- The bug still exists. The situation happens when i suspend system to RAM with many Gwenview instances opened, and then resume from suspend. It also happens when Plasma shell crashes and relaunches itself while many instances of Gwenview are opened. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468919] Some KDE Apps don't respect KWin window rules even when "ignore requested geometry" is set to "force"
https://bugs.kde.org/show_bug.cgi?id=468919 --- Comment #2 from Łukasz Konieczny --- (In reply to Nate Graham from comment #1) > Can you test the following other KDE apps so we can try to establish a > pattern? > - Dolphin > - Ark > - Konsole > - Discover > - System Settings > - Filelight > - Elisa Dolphin - behaves correctly Ark - behaves correctly Konsole - behaves incorrectly! Discover - behaves correctly System Settings - behaves incorrectly! Filelight - behaves correctly Elisa - behaves correctly Kate - behaves correctly Plasma System Monitor - behaves correctly Gwenview - behaves correctly KGet - behaves correctly Kid3 - behaves correctly Cantor - behaves incorrectly! LabPlot - behaves correctly KDE Marble - behaves correctly Spectacle - behaves correctly KDevelop - behaves correctly KDiskFree - behaves partially incorrectly - it re-launches with proper size, but the last column is stretched and horizontal scrollbar appears! KInfoCenter - behaves correctly Uff! Perhaps it's enough. Moreover, those programs, which behaves incorrectly, often launch not centered, despite I have setting to all windows appear centered. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468919] New: Some KDE Apps don't respect KWin window rules even when "ignore requested geometry" is set to "force"
https://bugs.kde.org/show_bug.cgi?id=468919 Bug ID: 468919 Summary: Some KDE Apps don't respect KWin window rules even when "ignore requested geometry" is set to "force" Classification: I don't know Product: kde Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- SUMMARY Some KDE Apps, notably KWrite and Okular, but probably others, don't launch to their window size being set (when previously their size was manually changed) even when "ignore requested geometry" is set to "force". That means, they stubbornly remember their last window size regardless of "ignore requested geometry" set to "force" and regardless of their window size set to "apply initially". This is annoying bug, not a feature, because perfectionists like me want to set initial sizes of all their applications to some values and have freedom to dynamically change that size, and have their apps again in their initial size after re-launching. STEPS TO REPRODUCE 1. Set some window size for particular program. 2. Set "ignore requested geometry" to "force". 3. Launch program. 4. Change its size by dragging border. 5. Close app. 6. Open it again. OBSERVED RESULT App has size you changed by dragging. EXPECTED RESULT App has size NOT you changed by dragging, but its initial size set by you. SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-20-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: System76 Product Name: Darter Pro System Version: darp7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 439470] KFontView is unable to open or install a font on Wayland
https://bugs.kde.org/show_bug.cgi?id=439470 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467518] KWrite doesn't respect initial window size setting set in System Settings
https://bugs.kde.org/show_bug.cgi?id=467518 Łukasz Konieczny changed: What|Removed |Added Platform|Other |Kubuntu -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467518] New: KWrite doesn't respect initial window size setting set in System Settings
https://bugs.kde.org/show_bug.cgi?id=467518 Bug ID: 467518 Summary: KWrite doesn't respect initial window size setting set in System Settings Classification: Applications Product: kate Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- SUMMARY KWrite doesn't respect initial window size setting set in System Settings, that means when I set, that KWrite should appear after launching in such way that it has for example size of 400 px x 500 px, when I resize manually KWrite window, close KWrite and then launch it, it doesn't have size of 400 px x 500 px. STEPS TO REPRODUCE 1. Set initial size of KWrite window in System Settings or by clicking KWrite's icon in top-left corner of the window, set even rejecting window geometry demanding to "yes". 2. Launch KWrite. Resize its window manually. Close KWrite. 3. Launch KWrite. Observe, that KWrite's window doesn't have size of initial size set. OBSERVED RESULT KWrite doesn't respect window rules settings. EXPECTED RESULT KWrite fully respects window rules settings. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: System76 Product Name: Darter Pro System Version: darp7 ADDITIONAL INFORMATION Kubuntu Backports PPA enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466106] Allow to exclude some applications from registering in media player applet in preferences of this applet
https://bugs.kde.org/show_bug.cgi?id=466106 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466106] New: Allow to exclude some applications from registering in media player applet in preferences of this applet
https://bugs.kde.org/show_bug.cgi?id=466106 Bug ID: 466106 Summary: Allow to exclude some applications from registering in media player applet in preferences of this applet Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Media Player Assignee: plasma-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 156513 --> https://bugs.kde.org/attachment.cgi?id=156513=edit Screenshot of media player applet, when 36 windows of Gwenview are opened SUMMARY A problem specific to me, but perhaps somebody has the same problem. I'm listening to music, using some audio player (for example Strawberry). In the same time I have 36 windows of Gwenview opened, in every window is a photo of my friends. I love those photos, so I want them to be opened simultaneously in 36 windows, one window per photo. All of those Gwenview windows register themselves as media player and the top of media player applet is littered by Gwenview icons, which even don't fit in the space in top of the applet. If I want to stop playing music in Strawberry and play something in Firefox, and then switch back to Strawberry, I can't, because I'm even not able to point to icon of Strawberry in the top of the applet. I have attached screenshot, to show you the problem. I would like to have an option to exclude particular programs from registering themselves as media player in this applet. Then I would exclude Gwenview, because I don't need to command Gwenview from this applet. STEPS TO REPRODUCE 1. Open way more windows of, for example, Gwenview, than you think you can, for example 40 windows of Gwenview, and observe, that each Gwenview window registers itself as media player in applet. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.6 Kernel Version: 6.0.12-76060006-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: System76 Product Name: Darter Pro System Version: darp7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 453669] Muon asks for root password on system with sudo when trying to launch software-properties-kde, so one can't launch this utility
https://bugs.kde.org/show_bug.cgi?id=453669 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 453669] New: Muon asks for root password on system with sudo when trying to launch software-properties-kde, so one can't launch this utility
https://bugs.kde.org/show_bug.cgi?id=453669 Bug ID: 453669 Summary: Muon asks for root password on system with sudo when trying to launch software-properties-kde, so one can't launch this utility Product: muon Version: 5.8.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: muon Assignee: unassigned-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: echidna...@kubuntu.org, silh...@gmail.com Target Milestone: --- SUMMARY Muon asks for root password on system with sudo when trying to launch software-properties-kde, so one can't launch this utility. It does that even when root account is locked. STEPS TO REPRODUCE 1. Launch Muon 2. Go to settings -> Configure software sources 3. Observe that Muon launches KDE su. When I try to provide my own password (because root account is locked and I have sudo configured), I can't launch software-properties-kde OBSERVED RESULT One can't launch software-properties-kde from Muon EXPECTED RESULT One can launch software-properties-kde from Muon SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.16.19-76051619-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION Kubuntu backports PPA enabled -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413499] The sorting method and placement of desktop icons get reset after changing sorting method to Manual from anything else
https://bugs.kde.org/show_bug.cgi?id=413499 --- Comment #8 from Łukasz Konieczny --- Unfortunately, the bug still exists in Plasma 5.24.5. Icons are moved from their positions when bottom panel appears after login. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 --- Comment #10 from Łukasz Konieczny --- It seems like this bug can be overcome by editing bottom panel, for example I have changed application launcher from Kickoff to old Kickoff variant downloaded via Get Hot New Stuff. Now I have tried to logout and login several times and sometimes icons move to the top but immediately return to their position. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 444490] "Login" column doesn't show usernames
https://bugs.kde.org/show_bug.cgi?id=90 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 444490] New: "Login" column doesn't show usernames
https://bugs.kde.org/show_bug.cgi?id=90 Bug ID: 90 Summary: "Login" column doesn't show usernames Product: plasma-systemmonitor Version: 5.23.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 142941 --> https://bugs.kde.org/attachment.cgi?id=142941=edit Screenshot of Plasma Systemmonitor SUMMARY If enabled, "login" column shows no usernames of owners of processess. STEPS TO REPRODUCE 1. Enable "login" column in Plasma Systemmonitor. 2. Observe the effect. OBSERVED RESULT No usernames on this column. EXPECTED RESULT "Login" column contains usernames corresponding to UIDs of processess. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-7619-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION Kubuntu backports PPA enabled -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 --- Comment #8 from Łukasz Konieczny --- (In reply to Nate Graham from comment #6) > But "Manual" is supposed to be the default setting. What did you change it > from? I have also changed "place icons in rows" to "place icons in columns", because rows is default setting in Kubuntu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 Łukasz Konieczny changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #7 from Łukasz Konieczny --- (In reply to Nate Graham from comment #6) > But "Manual" is supposed to be the default setting. What did you change it > from? At least in Kubuntu sorting desktop icons by name (directories first) is default. I have just checked it on new account. So I changed that and also changed icons size from fourth position on slider to third. I have also disabled icons preview of content. I did those things after installation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 Łukasz Konieczny changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Łukasz Konieczny --- (In reply to Nate Graham from comment #4) > Is there any chance you--at any time--changed the sorting method to > something other than "Manual" and then changed it back? If so, this may have > the same root cause as Bug 413499. I have only changed to "manual" after installation of OS, when I was adjusting settings of desktop. Since then I haven't changed anything. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 --- Comment #3 from Łukasz Konieczny --- Created attachment 142836 --> https://bugs.kde.org/attachment.cgi?id=142836=edit This is what happended after login -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 --- Comment #2 from Łukasz Konieczny --- Created attachment 142835 --> https://bugs.kde.org/attachment.cgi?id=142835=edit My desktop settings part 2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 --- Comment #1 from Łukasz Konieczny --- Created attachment 142834 --> https://bugs.kde.org/attachment.cgi?id=142834=edit My desktop settings part 1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] New: Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345
Bug ID: 444345
Summary: Frequently, but not always, files on the desktop move
to the top after login
Product: plasmashell
Version: 5.23.1
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Desktop Containment
Assignee: notm...@gmail.com
Reporter: ftefrjbhfvas...@o2.pl
CC: plasma-b...@kde.org
Target Milestone: 1.0
Created attachment 142833
--> https://bugs.kde.org/attachment.cgi?id=142833=edit
My desktop with icons placed as I want
SUMMARY
I have some files in the ~/Desktop/ (in polish version in the ~/Pulpit/)
directory. Those files are shown on my desktop. I want them to be in place
specified by me. But many times after I login into my account, they initially
are in those places, but when bottom panel appears, they move to the top. They
change their place. My bottom panel has height of 38. In desktop settings
("Icons" section) I have those options enabled (I have polish language version,
so this is my own translation to english): "place icons in columns", "align to
the left", "arrange manually", "icons size": third from the left on slider,
"width of label": medium, "number of text lines": 2. This problem has existed
for a long time (couple of years). My screen resolution is 1920x1080, I have
only bottom panel. Screenshots of my desktop are in attachments.
STEPS TO REPRODUCE
1. Login into account in system.
2. Many times you will observe that icons move to the top after login.
OBSERVED RESULT
Icons change their place. I don't want that. I want them to be in exactly this
place I have placed them.
EXPECTED RESULT
Icons on the desktop don't change their place.
SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.10
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-7619-generic (64-bit)
Graphics Platform: X11
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
ADDITIONAL INFORMATION
Kubuntu backports PPA enabled.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 443742] Kickoff doesn't respect order of programs set in KMenuEdit
https://bugs.kde.org/show_bug.cgi?id=443742 --- Comment #6 from Łukasz Konieczny --- (In reply to Noah Davis from comment #5) > > Weirdly, only programs in Multimedia category behave as I expect. > > I have a theory for why this may be. Please confirm that you have no > subcategories in the Multimedia category with items in them. > > My theory is that Kickoff is supposed to respect the "Always sort > applications alphabetically" setting, but it falls back to alphabetical > sorting whenever a category has subcategories with items in them. If that is > the case, we'll need to change the behavior of the Kicker models, which are > used by Kickoff. Yes, I don't have any subcategories (nested folders) in Multimedia category. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443742] Kickoff doesn't respect order of programs set in KMenuEdit
https://bugs.kde.org/show_bug.cgi?id=443742 --- Comment #4 from Łukasz Konieczny --- (In reply to Nate Graham from comment #3) > For apps like those, maybe you could put them all in a big top-level "Junk" > folder. Yes, I could do so, but those utilities come from various categories, so, again, nested folders could be very helpful. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443742] Kickoff doesn't respect order of programs set in KMenuEdit
https://bugs.kde.org/show_bug.cgi?id=443742 --- Comment #2 from Łukasz Konieczny --- (In reply to Nate Graham from comment #1) > Not showing the nesting is intentional; we got user complaints that showing > the nesting required unnecessarily fiddly navigation. If you're the kind of > person who likes it, then Kicker (Application Menu) may be better for you. > > Showing apps in alphabetical order is likewise intentional, though you may > have a point. We can use the bug to track that. I think there could be apropriate configuration options in Kickoff configuration window. Nesting folders is very useful, for example one user (like myself) has many "junk" applications, which aren't "big" programs, but rather small utilities, like Bluetooth assistant, KColorChooser, KRuler, vprerex, UXTerm, ImageMagick, which register their entries in menu, but user never launches them from menu. For some reasons though the user doesn't want to remove those entries of small utilities from menu, but wants to store them in folder "Others" nested in apropriate category. The user can then hide those utilities from "big" applications, like OBS Studio, Strawberry, LibreOffice Writer or Kid3. Listing applications in order specified by user instead of alphabetical order is also useful when user wants some programs to be on top. For example I like to order programs of similar purpose near each other. In Multimedia category for example my order of applications is as follows: Strawberry -> Yarock -> Elisa -> Kid3 -> VLC media player -> mpv -> Subtitle Composer -> OBS Studio -> vokoscreenNG -> Handbrake -> K3b. As you can see, this order resembles closely such groups of programs: audio players -> tag editors -> multimedia players -> subtitle editors -> recording software -> multimedia converters -> disk burning software. That's the reason the user wouldn't want their programs be listed in alphabetical order. Conclusion. Please make configuration options for various types of users instead of hard-coding particular behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443742] Kickoff doesn't respect order of programs set in KMenuEdit and doesn't show nested folders of programs
https://bugs.kde.org/show_bug.cgi?id=443742 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443742] New: Kickoff doesn't respect order of programs set in KMenuEdit and doesn't show nested folders of programs
https://bugs.kde.org/show_bug.cgi?id=443742 Bug ID: 443742 Summary: Kickoff doesn't respect order of programs set in KMenuEdit and doesn't show nested folders of programs Product: plasmashell Version: 5.23.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: ftefrjbhfvas...@o2.pl CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I have set order of programs in every category using KMenuEdit and Kickoff doesn't repsect that. Instead it shows programs in every category in alphabetical order. I have had unchecked showing programs in alphabetical order in kickoff settings from the beginning. Weirdly, only programs in Multimedia category behave as I expect. Changing order of programs in KMenuEdit doesn't work. Moreover, I have folders for less important programs nested in every category. Kickoff doesn't show those folders. STEPS TO REPRODUCE Update Plasma to 5.23 OBSERVED RESULT As described above EXPECTED RESULT Nested folders are shown and I can go to them. Kickoff obeys order of programs set in KMenuEdit. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-7614-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION Kubuntu Backports PPA enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442475] Plasma crashed after unplugging USB memory stick
https://bugs.kde.org/show_bug.cgi?id=442475 --- Comment #1 from Łukasz Konieczny --- Created attachment 141797 --> https://bugs.kde.org/attachment.cgi?id=141797=edit New crash information added by DrKonqi plasmashell (5.22.5) using Qt 5.15.2 - What I was doing when the application crashed: I unplugged pendrive from computer using external drives applet. -- Backtrace (Reduced): #6 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=) at /usr/include/c++/10/bits/atomic_base.h:741 #7 std::atomic::load(std::memory_order) const (__m=std::memory_order_relaxed, this=) at /usr/include/c++/10/atomic:523 #8 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239 #9 QBasicAtomicPointer::loadRelaxed() const (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:248 #10 QQmlNotifierEndpoint::connect(QObject*, int, QQmlEngine*, bool) (this=this@entry=0x56544ba586e0, source=0x56544d0618e0, sourceSignal=46, engine=0x0, doNotify=doNotify@entry=true) at qml/qqmlnotifier.cpp:122 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442475] Plasma crashed after unplugging USB memory stick
https://bugs.kde.org/show_bug.cgi?id=442475 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440424] Placing icon in lower-right-most position causes it to shift down a row when plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=440424 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl --- Comment #7 from Łukasz Konieczny --- I want to extend this bug report. I have manual placement of icons on the desktop (and, because I had to choose one from two options, I have placement of icons in columns and to the left side of the screen, but they are in reality placed manually on various places on the desktop). Plasma sometimes doesn't remember my placement of icons on the desktop after i log out and log in (or reboot). Especially it always doesn't remember my manual placement of icons, when I choose to place them to the right side of the screen, Plasma then stretches workspace beyond right side of the screen and horizontal scrollbar appears. Plasma has a HUGE problem with remembering custom position of icons on the desktop. My specification: Operating System: Kubuntu 21.04 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-7620-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics My screen resolution: 1920x1080 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #17 from Łukasz Konieczny --- (In reply to Nate Graham from comment #15) > Can't reproduce, FWIW. In both cases, the restored window moves to the > correct place. I did find one related problem while testing, however: Bug > 434116. > > I will try to fix that soon. I have to add, that in icon view I have icons of size 80 px. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #16 from Łukasz Konieczny --- (In reply to Nate Graham from comment #15) > Can't reproduce, FWIW. In both cases, the restored window moves to the > correct place. I did find one related problem while testing, however: Bug > 434116. > > I will try to fix that soon. Perhaps the initial size of window matters? Please try to shrink your Dolphin window so that you have four columns of files/directories in icon view. I have such setup and in this case I can reproduce the problem every time. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #14 from Łukasz Konieczny --- (In reply to Nate Graham from comment #13) > That's not related to this, but if you're sure it is, you can test again by > removing the "Location Bar" item from Dolphin's toolbar. I have already tested this on new account in system (in order to eliminate other factors). When location bar is in the toolbar (default since Dolphin 20.12), Dolphin behaves correctly. When location bar is not in the toolbar, but under the toolbar (that's my setting, because I like that), Dolphin doesn't return to the desired size of window. So it must be caused by placement of location bar. Or by something connected to the placement of this element of interface. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 Łukasz Konieczny changed: What|Removed |Added Resolution|WORKSFORME |--- Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #12 from Łukasz Konieczny --- Finally, I have found, what is causing problem. In recent version of Dolphin you have moved URL navigator into the toolbar. Please, remove the URL navigator (breadcrumbs) from the toolbar, then it will appear under the toolbar. You will see, that Dolphin doesn't return into the window size set by you, when you return from maximize state. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #11 from Łukasz Konieczny --- Because of the remainder about bug closing due to inactivity, I have posted another video, which shows this problem. Still doesn't work for me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #10 from Łukasz Konieczny --- Created attachment 136437 --> https://bugs.kde.org/attachment.cgi?id=136437=edit The second video showing this behavior of Dolphin in version 20.12.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #8 from Łukasz Konieczny --- (In reply to Nate Graham from comment #7) > FWIW if your goal is to always position all windows in the center, there's a > much easier solution than using Window Rules: > > 1. Go to System Settings > Window Management > Window Behavior > Advanced > 2. Change "Window Placement" to "Centered" > 3. Uncheck "Allow apps to remember the positions of their own windows, if > they support it > > Voila! That's what I did. I was talking about that exactly. I have separate window rules, but only the ones that control size of the windows of particular programs. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 Łukasz Konieczny changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Łukasz Konieczny --- (In reply to Nate Graham from comment #4) > Hmm, seems kind of like Bug 432661, but that was fixed in Frameworks 5.79 > and yo have that. > > If you remove your window rule entirely, does Dolphin restore to the correct > position? Position is OK. I have setting to place every window in the center of the screen. But size of the window is incorrect, regardless if I have a window rule or not. So no, if I remove this rule, Dolphin still restores to incorrect size of window. But I have noticed that if size of unmaximized Dolphin window is larger, more or less larger, this problem doesn't occur. But in my case (784x616) it occurs. > If not, does it do so if you temporarily move aside your ~/.config/dolphinrc > file, restart Dolphin, and try a maximize+restore cycle again? No, it doesn't help. It only makes Dolphin loss my settings, unless I restore that file into its place. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #3 from Łukasz Konieczny --- Perhaps this problem depends on size of window. My size of Dolphin window is 784x616. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #2 from Łukasz Konieczny --- (In reply to Nate Graham from comment #1) > You can remove that window rule because Dolphin now always remembers its > window size automatically. :) I made this window rule in case I would like to temporarily change Dolphin's window size, because I want Dolphin to have the same size every time I launch it. > If you don't want to remove the window rule, you need to make use of the > window rule setting to override the app's own window geometry by also adding > an "Ignore Requested Geometry: Yes" property to your window rule. This is > made clearer in Plasma 5.21 when you create a window rule with with Size: > property. I checked if it is true, and no. I removed the window rule and yes, Dolphin remembers its size, unless I maximize its window. When I maximize and return from maximization, Dolphin sets window size to this size, which I have shown in video. I have tried everything, also setting "Ignore Requested Geometry: Yes", and it doesn't work. Dolphin is still stubborn and after returning from maximization it sets its size to this fixed value, which I don't want. I think there is either problem with Dolphin respecting Plasma's settings, or someone hard-coded this unwanted window size into Dolphin. Or some another problem, which I don't know. And still there is problem with "Places" panel on the left side of the window, which changes width after returning from maximization. I don't want this behavior either. Older version of Dolphin (20.08) didn't have those problems. Thank you in advance for your help! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] New: Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 Bug ID: 433230 Summary: Dolphin window doesn't return to size set by user after returning from maximize state Product: dolphin Version: 20.12.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: kfm-de...@kde.org Target Milestone: --- Created attachment 135893 --> https://bugs.kde.org/attachment.cgi?id=135893=edit Video showing strange behavior of Dolphin after returning from maximization of window SUMMARY I have set size of Dolphin window in window rules in order to have Dolphin window of the same size every time I create a window of this program. But when I maximize the window of Dolphin and return from maximization, Dolphin sets window size to its own size and doesn't respect my own settings. Moreover, "places" pane on the left is shrunk. This behavior is shown in attached video made using vokoscreenNG. Other KDE programs behave correctly, only Dolphin behaves this way. STEPS TO REPRODUCE 1. Set window size of Dolphin in System Settings and set it to be applied when new window is created. 2. Launch Dolphin. 3. Maximize its window. 4. Return from maximization. OBSERVED RESULT Dolphin doesn't respect user settings. EXPECTED RESULT Dolphin window has the same size as it has before maximization. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430197] KWin crashed when I used hot corner to present all windows in virtual desktop
https://bugs.kde.org/show_bug.cgi?id=430197 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430197] New: KWin crashed when I used hot corner to present all windows in virtual desktop
https://bugs.kde.org/show_bug.cgi?id=430197 Bug ID: 430197 Summary: KWin crashed when I used hot corner to present all windows in virtual desktop Product: kwin Version: 5.19.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- Application: kwin_x11 (5.19.5) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-31-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: - What I was doing when the application crashed: I used top-right hot corner to present all 34 windows in one of my four virtual desktops, then I again used this hot corner to switch off all windows view and KWin crashed (but reopened immediately). All of those windows were Gwenview instances. Just when I was writing this bug report, I did the same thing and it happened again. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 0x7f16d7ee34ee in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) (this=0x5607635d2970, e=0x7f16c80473f0) at /usr/include/c++/10/bits/stl_algobase.h:1975 #7 0x7f16d6b5b4ef in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=, eventType=..., message=message@entry=0x7f16c80473f0, result=result@entry=0x7ffd5ab17648) at kernel/qabstracteventdispatcher.cpp:488 #8 0x7f16d0634505 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0x5607634c4770, event=event@entry=0x7f16c80473f0) at qxcbnativeinterface.h:101 #9 0x7f16d0635a46 in QXcbConnection::processXcbEvents(QFlags) (this=0x5607634c4770, flags=...) at qxcbconnection.cpp:1029 #10 0x7f16d0658740 in QXcbUnixEventDispatcher::processEvents(QFlags) (this=0x5607635143f0, flags=...) at qxcbeventdispatcher.cpp:61 #11 0x7f16d6b5ca4b in QEventLoop::exec(QFlags) (this=this@entry=0x7ffd5ab17790, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #12 0x7f16d6b64fc6 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #13 0x560762d25a6d in main(int, char**) (argc=, argv=0x7ffd5ab17a18) at ./main_x11.cpp:479 [Inferior 1 (process 1242) detached] Possible duplicates by query: bug 430180, bug 430028, bug 429938, bug 429202, bug 428975. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 428611] Cantor crashes after closing tab with working Sage
https://bugs.kde.org/show_bug.cgi?id=428611 --- Comment #5 from Łukasz Konieczny --- (In reply to Nikita Sirgienko from comment #4) > About crashing problem - I don't know, how to fix it, because crash appears > in Qt code, and I even don't know why it goes there in first place. > But there is a good news - crash will apears only, when Cantor can't use > Sage. So, for example, the problem don't appears with Sage 9.1, because > Cantor works with this version. > And after script fix - the problems will gone for Sage 9.2 too. > So, this problem is on low priority, and because it appears very rarely and > depends from another bug - i will set status as LATER. OK. Thank you very much for help and explanation. Regards. Łukasz Konieczny -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428535] Dolphin crashes when I choose to empty trash
https://bugs.kde.org/show_bug.cgi?id=428535 --- Comment #6 from Łukasz Konieczny --- Perhaps the problem is caused by tree view mode. I wrote that problem occurs no matter which view mode I choose. But I had initially tree view mode. When I set view to icon view mode and threw those files to trash, they were not duplicated. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428535] Dolphin crashes when I choose to empty trash
https://bugs.kde.org/show_bug.cgi?id=428535 --- Comment #5 from Łukasz Konieczny --- I have thrown 7.4 GiB of data into trash. Dolphin duplicates files in trash and crashes even when I go back from trash to earlier directory. @Christoph Feck [[[Duplicate entries where also seen by other reporters; might be caused by the Tree view mode. Do you use this?]]] No matter which view mode I use, Dolphin shows duplicated files in trash. I have thrown 3 files, Dolphin shows 6. @Méven Car [[[Is there double files in ~/.local/share/Trash/info/ as well compared to the trash "real" content in "~/.local/share/Trash/files" ?]]] In both directories mentioned by you I have now 3 files. There is everything OK. Dolphin only erratically shows 6 files in trash:/ Moreover, Dolphin doesn't show duplicated files every time. It only shows duplicated files every time I move to trash some large files. Now I have thrown to trash three files which are 7.4 GiB in total. Dolphin showed them duplicated, then crashed when I went back to earlier directory. When I launched Dolphin once again, those files in trash were not duplicated. I could then empty the trash successfully. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428535] Dolphin crashes when I choose to empty trash
https://bugs.kde.org/show_bug.cgi?id=428535 --- Comment #2 from Łukasz Konieczny --- I don't have any idea. Perhaps Dolphin has problems if there are too large files in trash? I had some large files then and total amount of used space in trash was around 400 MiB. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 428611] Cantor crashes after closing tab with working Sage
https://bugs.kde.org/show_bug.cgi?id=428611 --- Comment #2 from Łukasz Konieczny --- Looks like only Sage tabs crash on closing. I have tried Maxima and it works fine. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 428611] Cantor crashes after closing tab with working Sage
https://bugs.kde.org/show_bug.cgi?id=428611 Łukasz Konieczny changed: What|Removed |Added Version|unspecified |20.08 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 428611] Cantor crashes after closing tab with working Sage
https://bugs.kde.org/show_bug.cgi?id=428611 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 428611] New: Cantor crashes after closing tab with working Sage
https://bugs.kde.org/show_bug.cgi?id=428611 Bug ID: 428611 Summary: Cantor crashes after closing tab with working Sage Product: cantor Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: cantor-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- Application: cantor (20.08.2) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-26-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: - What I was doing when the application crashed: I tried to use Sage 9.2 installed in /opt/SageMath/ and symlinked in /usr/bin/. Sage doesn't work in Cantor after all (but works in terminal), but the biggest problem is that Cantor crashes when I click to close tab with worksheet. It happens every time. - Custom settings of the application: I have manually installed Sage in /opt/ (vanilla version downloaded from Sage website). The crash can be reproduced every time. -- Backtrace: Application: Cantor (cantor), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 0x in ?? () #7 0x7fa3fb7732e6 in QtPrivate::QSlotObjectBase::call (a=0x7ffd9a19d250, r=0x55b9698c8db0, this=0x55b969a58f70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x55b9698e6110, signal_index=7, argv=0x7ffd9a19d250) at kernel/qobject.cpp:3870 #9 0x7fa3fb7732e6 in QtPrivate::QSlotObjectBase::call (a=0x7ffd9a19d390, r=0x55b96a0d2790, this=0x55b96a2aafb0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x55b96989d350, signal_index=8, argv=argv@entry=0x7ffd9a19d390) at kernel/qobject.cpp:3870 #11 0x7fa3fb76d068 in QMetaObject::activate (sender=sender@entry=0x55b96989d350, m=m@entry=0x7fa3fcdb42c0 , local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7ffd9a19d390) at kernel/qobject.cpp:3930 #12 0x7fa3fcd77cf5 in Cantor::Expression::statusChanged (this=this@entry=0x55b96989d350, _t1=, _t1@entry=Cantor::Expression::Interrupted) at ./obj-x86_64-linux-gnu/src/lib/cantorlibs_autogen/EWIEGA46WW/moc_expression.cpp:249 #13 0x7fa3fcd7db8c in Cantor::Expression::setStatus (this=0x55b96989d350, status=Cantor::Expression::Interrupted) at ./src/lib/expression.cpp:206 #14 0x7fa3f009ece5 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/backends/cantor_sagebackend.so #15 0x7fa3f009f149 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/backends/cantor_sagebackend.so #16 0x7fa3deafded0 in Worksheet::~Worksheet (this=0x55b9698e6110, __in_chrg=) at ./src/worksheet.cpp:119 #17 0x7fa3deafe08d in Worksheet::~Worksheet (this=0x55b9698e6110, __in_chrg=) at ./src/worksheet.cpp:107 #18 0x7fa3fb76718e in QObjectPrivate::deleteChildren (this=this@entry=0x55b9696d4c00) at kernel/qobject.cpp:2123 #19 0x7fa3fc22fa66 in QWidget::~QWidget (this=0x55b9699460d0, __in_chrg=) at kernel/qwidget.cpp:1530 #20 0x7fa3fc22fdbd in QWidget::~QWidget (this=0x55b9699460d0, __in_chrg=) at kernel/qwidget.cpp:1408 #21 0x7fa3fcd118b7 in KParts::Part::~Part (this=0x55b9698c8db0, __vtt_parm=0x7fa3deb77638 , __in_chrg=) at /usr/include/c++/10/bits/atomic_base.h:420 #22 0x7fa3deae5a82 in CantorPart::~CantorPart (this=0x55b9698c8db0, __in_chrg=, __vtt_parm=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qpointer.h:53 #23 0x7fa3deae5acd in CantorPart::~CantorPart (this=0x55b9698c8db0, __in_chrg=, __vtt_parm=) at ./src/cantor_part.cpp:400 #24 0x55b967a7c6d0 in CantorShell::closeTab (this=0x55b96967cb30, index=) at ./src/cantor.cpp:483 #25 0x7fa3fb773320 in doActivate (sender=0x55b9697f0650, signal_index=8, argv=argv@entry=0x7ffd9a19d7b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #26 0x7fa3fb76d068 in QMetaObject::activate (sender=, m=m@entry=0x7fa3fc7075e0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffd9a19d7b0) at kernel/qobject.cpp:3930 #27 0x7fa3fc3c23e5 in QTabWidget::tabCloseRequested (this=, _t1=) at .moc/moc_qtabwidget.cpp:333 #28 0x7fa3fb773320 in doActivate (sender=0x55b969749a30, signal_index=8, argv=argv@entry=0x7ffd9a19d8d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #29 0x7fa3fb76d068 in QMetaObject::activate (sender=, m=m@entry=0x7fa3fc706040 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffd9a19d8d0) at kernel/qobject.cpp:3930 #30 0x7fa3fc3a1ff5 in QTabBar::tabCloseRequested (this=, _t1=) at .moc/moc_qtabbar.cpp:345 #31 0x7fa3fb773320 in doActivate (sender=0x55b9698d0990, signal_index=9, argv=argv@entry=0x7ffd9a19d9f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #32 0x7fa3fb76d068 in
[dolphin] [Bug 428535] Dolphin crashes when I choose to empty trash
https://bugs.kde.org/show_bug.cgi?id=428535 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428535] New: Dolphin crashes when I choose to empty trash
https://bugs.kde.org/show_bug.cgi?id=428535 Bug ID: 428535 Summary: Dolphin crashes when I choose to empty trash Product: dolphin Version: 20.08.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.08.2) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-26-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: - What I was doing when the application crashed: I went to Trash where I had about 400 MiB of data and attempted to empty the Trash. Every item in Trash was duplicated, which I thought was strange. When I hit "Empty Trash" button, Dolphin crashed. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 QSharedDataPointer::~QSharedDataPointer (this=0x55e2e539e650, __in_chrg=) at /usr/include/c++/10/bits/atomic_base.h:333 #7 0x7fa7e91e18be in KFileItemModel::ItemData::~ItemData (this=0x55e2e539e650, __in_chrg=) at ./src/kitemviews/kfileitemmodel.h:298 #8 qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:320 #9 qDeleteAll > (c=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:328 #10 KFileItemModel::slotClear (this=0x55e2e563cb90) at ./src/kitemviews/kfileitemmodel.cpp:1155 #11 0x7fa7e73e42e6 in QtPrivate::QSlotObjectBase::call (a=0x7ffc7b51a620, r=0x55e2e563cb90, this=0x55e2e4b27040) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x55e2e55fc290, signal_index=10, argv=0x7ffc7b51a620, argv@entry=0x0) at kernel/qobject.cpp:3870 #13 0x7fa7e73de068 in QMetaObject::activate (sender=sender@entry=0x55e2e55fc290, m=m@entry=0x7fa7e8d65100 , local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #14 0x7fa7e8cea547 in KCoreDirLister::clear (this=this@entry=0x55e2e55fc290) at ./obj-x86_64-linux-gnu/src/core/KF5KIOCore_autogen/include/moc_kcoredirlister.cpp:460 #15 0x7fa7e8cfcb3e in KCoreDirListerCache::forgetDirs (this=this@entry=0x7fa7e8d684e0 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, lister=0x55e2e55fc290) at ./src/core/kcoredirlister.cpp:490 #16 0x7fa7e8cfd31a in KCoreDirListerCache::listDir (this=0x7fa7e8d684e0 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, lister=, _u=..., _keep=, _reload=) at ./src/core/kcoredirlister.cpp:125 #17 0x7fa7e91ec382 in KFileItemModel::refreshDirectory (this=0x55e2e563cb90, url=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:118 #18 0x7fa7e9243dcf in DolphinView::reload (this=0x55e2e537d4d0) at ./src/views/dolphinview.cpp:463 #19 0x7fa7e94e68f1 in DolphinViewContainer::reload (this=0x55e2e53dfcc0) at ./src/dolphinviewcontainer.cpp:456 #20 0x7fa7e94d1662 in DolphinMainWindow::reloadView (this=0x55e2e44ccdc0) at ./src/dolphinmainwindow.cpp:805 #21 0x7fa7e73e42e6 in QtPrivate::QSlotObjectBase::call (a=0x7ffc7b51a9f0, r=0x55e2e44ccdc0, this=0x55e2e4550b70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #22 doActivate (sender=0x55e2e453e520, signal_index=4, argv=argv@entry=0x7ffc7b51a9f0) at kernel/qobject.cpp:3870 #23 0x7fa7e73de068 in QMetaObject::activate (sender=sender@entry=0x55e2e453e520, m=m@entry=0x7fa7e8427f00 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc7b51a9f0) at kernel/qobject.cpp:3930 #24 0x7fa7e7f1f826 in QAction::triggered (this=this@entry=0x55e2e453e520, _t1=) at .moc/moc_qaction.cpp:381 #25 0x7fa7e7f22111 in QAction::activate (this=0x55e2e453e520, event=) at kernel/qaction.cpp:1161 #26 0x7fa7e8017202 in QAbstractButtonPrivate::click (this=this@entry=0x55e2e46e34f0) at widgets/qabstractbutton.cpp:909 #27 0x7fa7e8017325 in QAbstractButton::mouseReleaseEvent (this=0x55e2e470c050, e=0x7ffc7b51afc0) at widgets/qabstractbutton.cpp:1012 #28 0x7fa7e810959e in QToolButton::mouseReleaseEvent (this=, e=) at widgets/qtoolbutton.cpp:622 #29 0x7fa7e7f6730e in QWidget::event (this=0x55e2e470c050, event=0x7ffc7b51afc0) at kernel/qwidget.cpp:9033 #30 0x7fa7e7f26013 in QApplicationPrivate::notify_helper (this=, receiver=0x55e2e470c050, e=0x7ffc7b51afc0) at kernel/qapplication.cpp:3685 #31 0x7fa7e7f2b841 in QApplication::notify(QObject*, QEvent*) () at kernel/qapplication.cpp:3129 #32 0x7fa7e73ae1ca in QCoreApplication::notifyInternal2 (receiver=0x55e2e470c050, event=0x7ffc7b51afc0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 #33 0x7fa7e7f2a73a in
[kcharselect] [Bug 428523] New: Make KCharSelect cover all scripts in Unicode
https://bugs.kde.org/show_bug.cgi?id=428523 Bug ID: 428523 Summary: Make KCharSelect cover all scripts in Unicode Product: kcharselect Version: 20.08 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: cf...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- SUMMARY KCharSelect doesn't allow to use all scripts, for example egyptian hieroglyphs or vietnamese Chu Nom and many other scripts. Please make this program covering all scripts (all signs) in Unicode. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-26-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414913] Connect Deamon closed unexpectedly in Slideshow remote menu
https://bugs.kde.org/show_bug.cgi?id=414913 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411242] New: System Settings: choosing default mail client doesn't work
https://bugs.kde.org/show_bug.cgi?id=411242 Bug ID: 411242 Summary: System Settings: choosing default mail client doesn't work Product: systemsettings Version: 5.16.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_componentchooser Assignee: unassigned-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- SUMMARY System Settings: choosing default mail client doesn't work STEPS TO REPRODUCE 1. Go to: applications -> default applications -> email client -> use a different email client 2. Click button with three dots. 3. Choose program from categories. OBSERVED RESULT Nothing happens after clicking apply. EXPECTED RESULT Default program changes to chosen one. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20190820 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Kernel Version: 5.2.8-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15,6 GiB ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411242] System Settings: choosing default mail client doesn't work
https://bugs.kde.org/show_bug.cgi?id=411242 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383127] KTorrent crash while closing
https://bugs.kde.org/show_bug.cgi?id=383127 --- Comment #41 from Łukasz Konieczny --- Created attachment 121845 --> https://bugs.kde.org/attachment.cgi?id=121845=edit New crash information added by DrKonqi ktorrent (5.1.1) using Qt 5.13.0 - What I was doing when the application crashed: I had several torrents opened and I quited KTorrent. Then CPU usage peaked to 90% and KTorrent crashed. -- Backtrace (Reduced): #7 0x7ffacf7a5749 in memcpy (__len=65524, __src=, __dest=) at /usr/include/bits/string_fortified.h:34 #8 QString::reallocData (this=0x7ffdb5308b90, alloc=, grow=) at tools/qstring.cpp:2382 [...] #10 QString::replace (this=this@entry=0x7ffdb5308b90, before=before@entry=..., after=after@entry=..., cs=cs@entry=Qt::CaseSensitive) at tools/qstring.cpp:3282 #11 0x7ffad05a4667 in QAbstractItemDelegatePrivate::textForRole (this=, role=role@entry=Qt::DisplayRole, value=..., locale=..., precision=precision@entry=6) at ../../include/QtCore/../../src/corelib/tools/qchar.h:88 #12 0x7ffad05abc20 in QStyledItemDelegate::displayText (this=, value=..., locale=...) at itemviews/qstyleditemdelegate.h:99 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383127] KTorrent crash while closing
https://bugs.kde.org/show_bug.cgi?id=383127 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409223] KWin crashed when I used hot corner (top right in my configuration) to present all windows in virtual desktop
https://bugs.kde.org/show_bug.cgi?id=409223 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409223] New: KWin crashed when I used hot corner (top right in my configuration) to present all windows in virtual desktop
https://bugs.kde.org/show_bug.cgi?id=409223 Bug ID: 409223 Summary: KWin crashed when I used hot corner (top right in my configuration) to present all windows in virtual desktop Product: kwin Version: 5.16.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- Application: kwin_x11 (5.16.1) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 5.1.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I used hot corner to present all windows in virtual dekstop - 34 windows of Gwenview with various photos. The crash does not seem to be reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcb671eb940 (LWP 13862))] Thread 6 (Thread 0x7fcb5edee700 (LWP 22752)): #0 0x7fcb6afd284e in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #1 0x7fcb6affb4af in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #2 0x7fcb6afa6bdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7fcb6ade8751 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #4 0x7fcb69ae4065 in () at /usr/lib64/libQt5Qml.so.5 #5 0x7fcb6ade98d2 in () at /usr/lib64/libQt5Core.so.5 #6 0x7fcb6a35bfaa in start_thread () at /lib64/libpthread.so.0 #7 0x7fcb6c51471f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fcb4e538700 (LWP 13973)): #0 0x7fcb6a361e05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcb6a8731da in () at /usr/lib64/libQt5Script.so.5 #2 0x7fcb6a8731fb in () at /usr/lib64/libQt5Script.so.5 #3 0x7fcb6a35bfaa in start_thread () at /lib64/libpthread.so.0 #4 0x7fcb6c51471f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fcb4f53a700 (LWP 13970)): #0 0x7fcb6a361e05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcb4f78b043 in () at /usr/lib64/dri/i965_dri.so #2 0x7fcb4f78ad97 in () at /usr/lib64/dri/i965_dri.so #3 0x7fcb6a35bfaa in start_thread () at /lib64/libpthread.so.0 #4 0x7fcb6c51471f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fcb5e225700 (LWP 13968)): #0 0x7fcb6c509d96 in ppoll () at /lib64/libc.so.6 #1 0x7fcb6aff9ec9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fcb6affb3a4 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7fcb6afa6bdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcb6ade8751 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7fcb69ae4065 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7fcb6ade98d2 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fcb6a35bfaa in start_thread () at /lib64/libpthread.so.0 #8 0x7fcb6c51471f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fcb5700 (LWP 13883)): #0 0x7fcb6c509d96 in ppoll () at /lib64/libc.so.6 #1 0x7fcb6aff9ec9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fcb6affb3a4 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7fcb6afa6bdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcb6ade8751 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7fcb6950e4e6 in () at /usr/lib64/libQt5DBus.so.5 #6 0x7fcb6ade98d2 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fcb6a35bfaa in start_thread () at /lib64/libpthread.so.0 #8 0x7fcb6c51471f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fcb671eb940 (LWP 13862)): [KCrash Handler] #6 0x7fcb6c20dcd4 in std::__find_if >(int const*, int const*, __gnu_cxx::__ops::_Iter_equals_val, std::random_access_iterator_tag) (__pred=..., __last=0x15bbe90be2a94, __first=0x15bbe8d693d10) at /usr/include/c++/9/bits/predefined_ops.h:240 #7 0x7fcb6c20dcd4 in std::__find_if >(int const*, int const*, __gnu_cxx::__ops::_Iter_equals_val) (__pred=..., __last=0x15bbe90be2a94, __first=) at /usr/include/c++/9/bits/stl_algo.h:161 #8 0x7fcb6c20dcd4 in std::find(int const*, int const*, int const&) (__val=@0x7ffcc6f19a68: 6, __last=0x15bbe90be2a94, __first=) at /usr/include/c++/9/bits/stl_algo.h:3889 #9 0x7fcb6c20dcd4 in QVector::contains(int const&) const (t=t@entry=@0x7ffcc6f19a68: 6, this=) at /usr/include/qt5/QtCore/qvector.h:937 #10 0x7fcb6c2120cf in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) (this=0x55808c8757c0, e=0x7fcb600374a0) at
[kamoso] [Bug 404456] Opening the Effects Gallery drawer when no images have been taken yet renders the whole system unresponsive
https://bugs.kde.org/show_bug.cgi?id=404456 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl --- Comment #9 from Łukasz Konieczny --- I think my bug (bug405190) is related. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 405190] Kamoso crashes when clicking hamburger button in the bottom-left corner
https://bugs.kde.org/show_bug.cgi?id=405190 --- Comment #1 from Łukasz Konieczny --- I think that this bug is related: bug404456 -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 405190] Kamoso crashes when clicking hamburger button in the bottom-left corner
https://bugs.kde.org/show_bug.cgi?id=405190 Łukasz Konieczny changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 405190] Kamoso crashes when clicking hamburger button in the bottom-left corner
https://bugs.kde.org/show_bug.cgi?id=405190 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 405190] New: Kamoso crashes when clicking hamburger button in the bottom-left corner
https://bugs.kde.org/show_bug.cgi?id=405190 Bug ID: 405190 Summary: Kamoso crashes when clicking hamburger button in the bottom-left corner Product: kamoso Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- Created attachment 118633 --> https://bugs.kde.org/attachment.cgi?id=118633=edit gdb output SUMMARY Kamoso consumes several GiB of memory and crashes when clicking on hamburger button in the bottom-left corner of the application. STEPS TO REPRODUCE 1. Click on this button. OBSERVED RESULT Large amount of probably leaked memory. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: openSUSE Tumbleweed 20190305 KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.20.13-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15,6 GiB ADDITIONAL INFORMATION I couldn't use DrKonqi because it crashed every time I wanted to submit bug report using it. So I used gdb. -- You are receiving this mail because: You are watching all bug changes.
