[plasmashell] [Bug 480112] PlasmaCore.DataSource "executable" engine arbitrary code execution via any QML file in backdoored wallpaper plugins, themes, etc. distributed via store.kde.org
https://bugs.kde.org/show_bug.cgi?id=480112 --- Comment #6 from Amin Vakil --- What do you think about adding a warning, so users pay more attention installing plugins and check its sources? Just like you say, at the end of the day this concern is valid for any application which you install from everywhere, but here users (including myself) does not think that it may contain a executable as it's only a wallpaper plugin. Also I didn't understand whether installing a wallpaper could have a code execution capability or this only applies to plugins? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480112] PlasmaCore.DataSource "executable" engine arbitrary code execution via any QML file in backdoored wallpaper plugins, themes, etc. distributed via store.kde.org
https://bugs.kde.org/show_bug.cgi?id=480112 Amin Vakil changed: What|Removed |Added CC||i...@aminvakil.com --- Comment #2 from Amin Vakil --- (In reply to David Edmundson from comment #1) > Same as installing any program. Yeah, but it seems safe as it's only downloading a jpg file, not that it can also execute code . -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 Amin Ya changed: What|Removed |Added CC||aminyahyaabad...@gmail.com --- Comment #163 from Amin Ya --- I had the same issue on KDE Neon 5.27.5. After hours of trying, I finally tried a set of commands and a certain version of Nvidia that fixed the issue. I have put them on my GitHub here: https://github.com/aminya/AcuteLinux/blob/master/src/setup/setup-nvidia.bash This uses the latest Nvidia graphics. I could only make this work on X11, and XWayland was very buggy and sluggish. ``` #!/usr/bin/bash # -*- coding: utf-8 -*- set -e set -o pipefail sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt update sudo apt install -y nvidia-driver-535 # select nvidia sudo prime-select nvidia # set high-performance profile sudo nvidia-smi -pm 1 echo "Please reboot your system and enroll the MOK key, then reboot again." ``` -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 Amin Vakil changed: What|Removed |Added CC||i...@aminvakil.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457588] Deleted widgets return after a reboot
https://bugs.kde.org/show_bug.cgi?id=457588 --- Comment #10 from Mohammad Amin Chitgarha --- Good! Thanks for your time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457588] Deleted widgets return after a reboot
https://bugs.kde.org/show_bug.cgi?id=457588 --- Comment #8 from Mohammad Amin Chitgarha --- Oops, sorry; and thanks for clarification. The problem is gone when I explicitly close the notification. Not sure about waiting for the notification to go away (i.e. implicit close), because I don't remember just before submitting the bug whether it happened or not. However, I just tried once, and it seems it works. In other words, I have to close the notification, either explicitly or otherwise. Is it the intended behavior? If yes, it's confusing, at least for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457588] Deleted widgets return after a reboot
https://bugs.kde.org/show_bug.cgi?id=457588 Mohammad Amin Chitgarha changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457588] Deleted widgets return after a reboot
https://bugs.kde.org/show_bug.cgi?id=457588 Mohammad Amin Chitgarha changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Mohammad Amin Chitgarha --- @NateGraham, yes. However, note that because of no notification widget being present in the reproducable example I added recently, when removing something I don't get a notification. BTW, I've tested with cases giving me notifications and I close them, but after a session restart, the removed widgets are still there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457588] Plasma customizations not preserved
https://bugs.kde.org/show_bug.cgi?id=457588 --- Comment #4 from Mohammad Amin Chitgarha --- So I added an attachment for better reproducing the bug. First, get it and put it in your `.config` (make sure to backup your existing file before overriding it). Then, log in with the new configuration. The configuration consists of an empty panel at the bottom. Enter edit mode, remove the panel, exit edit mode and log out. Now log back in. The panel should be there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457588] Plasma customizations not preserved
https://bugs.kde.org/show_bug.cgi?id=457588 --- Comment #3 from Mohammad Amin Chitgarha --- Created attachment 151168 --> https://bugs.kde.org/attachment.cgi?id=151168=edit Reproducable plasma-org.kde.plasma.desktop-appletsrc file -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457588] Plasma customizations not preserved
https://bugs.kde.org/show_bug.cgi?id=457588 --- Comment #2 from Mohammad Amin Chitgarha --- The problem is actually the file `plasma-org.kde.plasma.desktop-appletsrc` is edited in a wrong way: The removed applet only gets dropped from `AppletOrder` in `General` category, and the actual widget data doesn't get removed from the file. This behavior is simply wrong. As a workaround, I had to manually remove the entries to get rid of the widgets entirely, by looking at the file before and after the change to find out the widget numbers. Maybe this is due to an applet creating an invalid configuration entry? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457588] Plasma customizations not preserved
https://bugs.kde.org/show_bug.cgi?id=457588 --- Comment #1 from Mohammad Amin Chitgarha --- I just tested it again, and it seems to happen only with widget removal, meaning removing does not persist. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457588] New: Plasma customizations not preserved
https://bugs.kde.org/show_bug.cgi?id=457588 Bug ID: 457588 Summary: Plasma customizations not preserved Product: plasmashell Version: 5.25.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: machitga...@outlook.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY When I make changes to anything in plasma, say adding/removing a widget to/from a panel, the changes are not preserved after a logout/reboot. Used both X11 and Wayland sessions, the problem is available on both. STEPS TO REPRODUCE 1. Remove an existing widget from a panel. 2. Logout and log back in. OBSERVED RESULT The widget is still there. EXPECTED RESULT The widget must be gone. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442398] non-latin symbols inside PDF-forms not displayed in view-mode and non-printable
https://bugs.kde.org/show_bug.cgi?id=442398 --- Comment #1 from Amin --- P.S. In firefox all symbols from PDF-forms fields displayed correctly; -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442398] New: non-latin symbols inside PDF-forms not displayed in view-mode and non-printable
https://bugs.kde.org/show_bug.cgi?id=442398 Bug ID: 442398 Summary: non-latin symbols inside PDF-forms not displayed in view-mode and non-printable Product: okular Version: 21.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: ami...@tuta.io Target Milestone: --- Created attachment 141525 --> https://bugs.kde.org/attachment.cgi?id=141525=edit PDF for test displaying non-latin / ex-latin / math / cyrillic symbols in FORMS SUMMARY When PDF with forms filled, non-latin chars displayed only in edit-mode; In view / print_preview mode non-latin or extended latin chars not displayed; This chars also not printed; STEPS TO REPRODUCE 1. Open PDF with filled form from attach in okular 2. Press button "Show forms" and compare data strings in edit- and display- modes. 3. Try print filled form to printer (ex cups-pdf) and discover that only basic latin characters printed. OBSERVED RESULT Extended-Latin (extension A-E in kCharSelect), cyrillic and math-symbols inside PDF-forms not displayed in view-mode and not printing. EXPECTED RESULT All symbols visible and printable in PDF-forms fields. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 / KDE @ X11 KDE Plasma Version: 5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 412884] Excessive precision in I/O graphs; usability;
https://bugs.kde.org/show_bug.cgi?id=412884 Amin changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Amin --- fixed in 5.22.0 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 405414] Header name and colors options don't saved for [Partition usage] --> [Table (listview)]
https://bugs.kde.org/show_bug.cgi?id=405414 --- Comment #4 from Amin --- Fedora 34, ksysguard 5.22.0 - color options for disk usage table still non-working; -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 405414] Header name and colors options don't saved for [Partition usage] --> [Table (listview)]
https://bugs.kde.org/show_bug.cgi?id=405414 Amin changed: What|Removed |Added Version|5.17.5 |5.22.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430036] konsole no-toolbar setting missing or forgotten
https://bugs.kde.org/show_bug.cgi?id=430036 Amin Vakil changed: What|Removed |Added CC||i...@aminvakil.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436192] Feature Request: Sort Unknown Faces (ungrouped)
https://bugs.kde.org/show_bug.cgi?id=436192 Amin Husni changed: What|Removed |Added Version|unspecified |7.4.0 OS|Other |Microsoft Windows Platform|Other |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436192] New: Feature Request: Sort Unknown Faces (ungrouped)
https://bugs.kde.org/show_bug.cgi?id=436192 Bug ID: 436192 Summary: Feature Request: Sort Unknown Faces (ungrouped) Product: digikam Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Faces-Recognition Assignee: digikam-bugs-n...@kde.org Reporter: aminhu...@gmail.com Target Milestone: --- Wondering if it is possible to have a feature where you can sort the faces in the unknown group in an incremental manner according to similarity/alignments? This is possible with other program called FaceSwap by using openCV. (Note: Different program on the link to demonstrate example of such feature) https://github.com/deepfakes/faceswap/issues/252 https://forum.faceswap.dev/viewtopic.php?t=27#sort I believe this could further enhance the speed of managing faces where we can just batch tag a row of faces that has been sorted. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 432474] baloo_file core dump on every system boot
https://bugs.kde.org/show_bug.cgi?id=432474 --- Comment #4 from Amin Vakil --- It's happening again. It got fixed with `balooctl purge` again. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 432474] baloo_file core dump on every system boot
https://bugs.kde.org/show_bug.cgi?id=432474 --- Comment #2 from Amin Vakil --- I asked this on archlinux irc channels and someone replied me: "known issue, it's fixed in 5.78 but you need to regenerate the index balooctl purge" And it got fixed for me. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 432960] New: BUG: Youtube livestreams and Twitch VODs & Livestreams
https://bugs.kde.org/show_bug.cgi?id=432960 Bug ID: 432960 Summary: BUG: Youtube livestreams and Twitch VODs & Livestreams Product: Falkon Version: 3.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: ariam...@student.ltu.se Target Milestone: --- SUMMARY Livestreams on Youtube cannot be loaded/played, and on Twitch neither livestreams nor VODs work. STEPS TO REPRODUCE 1. Install Falkon 3.1 on Windows 10 2. Open a livestream on Youtube or a livestream or VOD on Twitch OBSERVED RESULT Error observed on both Twitch and Youtube. EXPECTED RESULT Expected it to start streaming. SOFTWARE/OS VERSIONS Windows: Windows 10 Falkon Version: 3.1.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 432474] baloo_file core dump on every system boot
https://bugs.kde.org/show_bug.cgi?id=432474 Amin Vakil changed: What|Removed |Added CC||i...@aminvakil.com -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 405414] Header name and colors options don't saved for [Partition usage] --> [Table (listview)]
https://bugs.kde.org/show_bug.cgi?id=405414 Amin changed: What|Removed |Added Version|5.15.5 |5.17.5 --- Comment #3 from Amin --- FC31 , ksysguard 5.17.5 (fedora 31) - bug still active -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 412884] Excessive precision in I/O graphs; usability;
https://bugs.kde.org/show_bug.cgi?id=412884 Amin changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 412884] New: Excessive precision in I/O graphs; usability;
https://bugs.kde.org/show_bug.cgi?id=412884 Bug ID: 412884 Summary: Excessive precision in I/O graphs; usability; Product: ksysguard Version: 5.15.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: ami...@tuta.io Target Milestone: --- Created attachment 123166 --> https://bugs.kde.org/attachment.cgi?id=123166=edit excessive 6 digits after dot in ksysguard when I/O meter SUMMARY When monitoring I/O activity, current values of data from sensors like disk/sd*/Rate/rblk or disk/sd*/Rate/wblk show with unreal precision - 6 digits after dot. STEPS TO REPRODUCE 1. Add new tab and graph with disk/sd*/Rate/rblk sensor 2. Watch current values with 6 digitls after dot. OBSERVED RESULT Too excessive precision for current values of this data. EXPECTED RESULT Smart round of values. If we have 125800.569226 Kb/sec of read data, last 6 digits absolutely trash. 125.8 Mb/sec more comfortable for read value. But for very small values (floppy ?) (for example less 15 Kb/sec) all digits can be showed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 30 KDE Plasma Version: KDE Frameworks 5.59.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION This not "bug", this interface usability idea. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 320733] A privacy option that controlled output to logs (and elsewhere) would be nice
https://bugs.kde.org/show_bug.cgi?id=320733 Amin changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=411152 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 411152] New: KTorrent generate too many logs in xsession* Loglevel option not work
https://bugs.kde.org/show_bug.cgi?id=411152 Bug ID: 411152 Summary: KTorrent generate too many logs in xsession* Loglevel option not work Product: ktorrent Version: 5.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: usability Severity: wishlist Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: ami...@tuta.io Target Milestone: --- SUMMARY When active seeding ktorrent write too many logs to ~/.xsession_errors or in case of inaccesibity .xsession_erros - - to /tmp/xses-username. log file. For two days size of log can increase up to some gigabytes. I try change loglevel in ktorrent options - Journals - set all levels to none, but no changes in ktorrent behavior STEPS TO REPRODUCE 1. Start ktorrent with seeding popular torrent 2. Watch to files ~/.xsession_errors and/or /tmp/xses-$username.* 3. See relatively fast increase this logs with detail about each torrent connections 4. Try to disable logs in ktorrent log option and watch log files again OBSERVED RESULT - Logs writed to xsession_errors / xses-* and grow such fast - log level can't be tweaked EXPECTED RESULT - Logs writed only in ~/.local/share/ktorrent/logs (subdir for logs will be nice idea) - Log level options will work for this logs. Some similiar bugs: 320733 + 329671 In case of small partitions ktorrent logs can eat all free space; 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.
[ktorrent] [Bug 329671] Ktorrent should allow disabling logging to disk
https://bugs.kde.org/show_bug.cgi?id=329671 Amin changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=411152 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 405414] Header name and colors options don't saved for [Partition usage] --> [Table (listview)]
https://bugs.kde.org/show_bug.cgi?id=405414 Amin changed: What|Removed |Added Ever confirmed|0 |1 Version|5.14.5 |5.15.5 Alias||5.15.5, @, fc30, -, bug, ||present Status|REPORTED|CONFIRMED --- Comment #2 from Amin --- ksysguard 5.15.5 at fedora 30 - bug still active in this version; I see that dev-version 5.16.* exist - who can test partition usage element for color / title saving ? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 405414] New: Header name and colors options don't saved for [Partition usage] --> [Table (listview)]
https://bugs.kde.org/show_bug.cgi?id=405414
Bug ID: 405414
Summary: Header name and colors options don't saved for
[Partition usage] --> [Table (listview)]
Product: ksysguard
Version: 5.14.5
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: ksysguard
Assignee: ksysguard-b...@kde.org
Reporter: ami...@tuta.io
Target Milestone: ---
Created attachment 118762
--> https://bugs.kde.org/attachment.cgi?id=118762=edit
strace ksysguard with strange EACCES calls
SUMMARY
In ksysguard, for element [Partition usage] --> [Table (listview)]
options don't saved.
STEPS TO REPRODUCE
1. Add new tab in ksysguard, add table of partition usage to this tab
2. Use right click - properties, and try change colors or title name
3. See bug - header name stay empty, all three colors stay black.
OBSERVED RESULT
Title name stay empty and colors stay black
EXPECTED RESULT
Title name and colors must be saved and applied.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 29 full updated at 2019-03-13
KDE Frameworks 5.55.0,
Qt 5.11.3 (build with version 5.11.3),
window system xcb.
ADDITIONAL INFORMATION
- try remove tab/table and add again - no effect
- try run from konsole - no error messages in shell
- found in strace some strange info about access to config:
access("/home/Amin/.config/ksysguardrc", X_OK) = -1 EACCES (denied)
But access rights for ksysguardrc and *.sgrd files stay correct -
placed tabs and items remain at tuned positions.
- try deactivate selinux - also no effect
* 4 small wishlist - display units / round bytes to Gb can be option =)
--
You are receiving this mail because:
You are watching all bug changes.
[ksysguard] [Bug 278974] KSysGuard show incorrect Total Size for big (~2.7 Tb) partition
https://bugs.kde.org/show_bug.cgi?id=278974 Amin changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 278974] KSysGuard show incorrect Total Size for big (~2.7 Tb) partition
https://bugs.kde.org/show_bug.cgi?id=278974 Amin changed: What|Removed |Added CC||ami...@tuta.io -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 278974] KSysGuard show incorrect Total Size for big (~2.7 Tb) partition
https://bugs.kde.org/show_bug.cgi?id=278974 --- Comment #3 from Amin --- Fixed in 5.14.5 - 3 Tb HDD info display correctly. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 325280] Internal viewer kills krusader after view of any xml documents
https://bugs.kde.org/show_bug.cgi?id=325280 Amin changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||ami...@tuta.io Resolution|--- |FIXED --- Comment #6 from Amin --- Fixed in 2.7.1 - xml files view correctly in all modes. Small and medium size (60 Mb) view correctly -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 405410] New: krviewer crash krusader at try zip-archive view by F3 button
https://bugs.kde.org/show_bug.cgi?id=405410 Bug ID: 405410 Summary: krviewer crash krusader at try zip-archive view by F3 button Product: krusader Version: 2.7.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: krviewer Assignee: krusader-bugs-n...@kde.org Reporter: ami...@tuta.io CC: krusader-bugs-n...@kde.org Target Milestone: --- Created attachment 118761 --> https://bugs.kde.org/attachment.cgi?id=118761=edit Crash info for developers from send-report dialog SUMMARY When try view zip-archive by press F3 button krviewer crashed and krusader crashed too after this. STEPS TO REPRODUCE 1. Open krusader, find zip-archive, select this and press F3 button 2. Watch crashed viewer and crashed krusader too OBSERVED RESULT - krviewer crashed, and main application krusader crashed too - Send bug dialog appear, with detailed exception info (i send this). EXPECTED RESULT - view index of archive (list dirs/files) or some metadata about archive or something like hexdump (depends of installed packages / settings ?) - main app krusader must continue work undependent from krviewer SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 29 full updated at 2019-03-13 KDE Frameworks 5.55.0, Qt 5.11.3 (build with version 5.11.3), window system xcb. ADDITIONAL INFORMATION - This bug like to #396387 and #325280 , but appear on another file type - I can go inside archive by Enter button and view packed internal files from zip archives by F3, but can't view original zip-file by F3 button (ex. midnight commander show ascii-table with packed files and compressio data) - try edit by F4 work correctly - i see binary data and utf-8 info-warning. - Segmentation fault (11) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396297] New: Kwin crashes
https://bugs.kde.org/show_bug.cgi?id=396297 Bug ID: 396297 Summary: Kwin crashes Product: kwin Version: 5.13.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: arivana...@gmail.com Target Milestone: --- Application: kwin_x11 (5.13.2) Qt Version: 5.11.0 Frameworks Version: 5.47.0 Operating System: Linux 4.13.0-45-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: Kwin sometimes crashes when switching virtual desktops no other applications where opened It doesn't matter what app is open or being used it crashes sometimes the crash is not so frequent it happens about once in 15 virtual desktop switching kwin closes unexpectly then recovers and restarts The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbcce754940 (LWP 9856))] Thread 6 (Thread 0x7fbc90ed6700 (LWP 9870)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbcca3f7e04 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fbcca3f7e49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fbcc710a6ba in start_thread (arg=0x7fbc90ed6700) at pthread_create.c:333 #4 0x7fbcce15a41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fbc91fd9700 (LWP 9868)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbc9743170b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7fbc97431427 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7fbcc710a6ba in start_thread (arg=0x7fbc91fd9700) at pthread_create.c:333 #4 0x7fbcce15a41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fbc927da700 (LWP 9867)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbc9743170b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7fbc97431427 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7fbcc710a6ba in start_thread (arg=0x7fbc927da700) at pthread_create.c:333 #4 0x7fbcce15a41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fbcaa142700 (LWP 9865)): #0 0x7fff425f6974 in ?? () #1 0x7fff425f6cb8 in clock_gettime () #2 0x7fbcce168876 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7fbcaa141a90) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7fbccb4e1501 in qt_clock_gettime (ts=0x7fbcaa141a90, clock=) at kernel/qelapsedtimer_unix.cpp:111 #4 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #5 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #6 0x7fbccb4dfcf9 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fbc98000980) at kernel/qtimerinfo_unix.cpp:91 #7 0x7fbccb4e0265 in QTimerInfoList::timerWait (this=this@entry=0x7fbc98000980, tm=...) at kernel/qtimerinfo_unix.cpp:388 #8 0x7fbccb4defd4 in QEventDispatcherUNIX::processEvents (this=0x7fbc980008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:485 #9 0x7fbccb4891ca in QEventLoop::exec (this=this@entry=0x7fbcaa141c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #10 0x7fbccb2be5e4 in QThread::exec (this=) at thread/qthread.cpp:522 #11 0x7fbcc5d8bcf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7fbccb2c9727 in QThreadPrivate::start (arg=0xf7ac80) at thread/qthread_unix.cpp:367 #13 0x7fbcc710a6ba in start_thread (arg=0x7fbcaa142700) at pthread_create.c:333 #14 0x7fbcce15a41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fbcb0bca700 (LWP 9861)): #0 0x7fbcce14e811 in __GI_ppoll (fds=fds@entry=0x7fbca400f468, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7fbccb4dd651 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fbca400f468) at kernel/qcore_unix.cpp:112 #3 qt_safe_poll (fds=0x7fbca400f468, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:133 #4 0x7fbccb4dece2 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7fbccb4891ca in QEventLoop::exec (this=this@entry=0x7fbcb0bc9c40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7fbccb2be5e4 in QThread::exec (this=) at thread/qthread.cpp:522 #7 0x7fbcc4c90f35 in ?? () from
[ksysguard] [Bug 278974] KSysGuard show incorrect Total Size for big (~2.7 Tb) partition
https://bugs.kde.org/show_bug.cgi?id=278974 Amin <a...@nm.ru> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366513] kwin crashed (SEGFAULT)
https://bugs.kde.org/show_bug.cgi?id=366513 --- Comment #2 from Amin <a...@weba.ru> --- OK, i switch to vesa temporarily, it's acceptable. I try install debug symbols and report to nouveau-developers. Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366513] New: kwin crashed (SEGFAULT)
https://bugs.kde.org/show_bug.cgi?id=366513 Bug ID: 366513 Summary: kwin crashed (SEGFAULT) Product: kwin Version: 5.7.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: a...@weba.ru Application: kwin_x11 (5.7.3) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux 4.6.4-301.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Update Fedora 23 to Fedora 24 with dnf upgrade plugin; Try login to Plasma Encvironment; Some times later try update Fedora 24 to latest stable packets, including plasma*. Try to login in Plasma-environment. - Unusual behavior I noticed: Message-box about "kwin crashed (Segfault)" appear; Start-menu, Quick-Launch, Taskbar and application tray NOT appear; But X-server live, i can run applications with Alt-F1 and switch between appications with Alt-Tab. Graphical desktop (Icons, widgets) not appear; The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff430f58940 (LWP 4505))] Thread 4 (Thread 0x7ff40e188700 (LWP 4517)): #0 0x7ff44405cbd0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff449a8bbc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7ff449a8bc09 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7ff4440575ca in start_thread () from /lib64/libpthread.so.0 #4 0x7ff4411d0ead in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7ff40f705700 (LWP 4516)): #0 0x7ff4411c7103 in select () from /lib64/libc.so.6 #1 0x7ff441fc76df in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7ff441fc8dd4 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /lib64/libQt5Core.so.5 #3 0x7ff441fc930a in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7ff441f7a5ea in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7ff441dd9343 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7ff448cda8f5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7ff441ddd99a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7ff4440575ca in start_thread () from /lib64/libpthread.so.0 #9 0x7ff4411d0ead in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7ff423fff700 (LWP 4512)): #0 0x7ff4411c7103 in select () from /lib64/libc.so.6 #1 0x7ff441fc76df in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7ff441fc8dd4 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /lib64/libQt5Core.so.5 #3 0x7ff441fc930a in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7ff441f7a5ea in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7ff441dd9343 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7ff443b9 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7ff441ddd99a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7ff4440575ca in start_thread () from /lib64/libpthread.so.0 #9 0x7ff4411d0ead in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff430f58940 (LWP 4505)): [KCrash Handler] #6 0x7ff41369b2f5 in nv30_fp_state_bind () from /usr/lib64/dri/nouveau_dri.so #7 0x7ff41351d0ce in cso_delete_fragment_shader () from /usr/lib64/dri/nouveau_dri.so #8 0x7ff4133d32e1 in destroy_program_variants () from /usr/lib64/dri/nouveau_dri.so #9 0x7ff4133d33c4 in destroy_shader_program_variants_cb () from /usr/lib64/dri/nouveau_dri.so #10 0x7ff4132e4c3d in _mesa_HashWalk () from /usr/lib64/dri/nouveau_dri.so #11 0x7ff4133a0731 in st_destroy_context () from /usr/lib64/dri/nouveau_dri.so #12 0x7ff4135122dd in dri_destroy_context () from /usr/lib64/dri/nouveau_dri.so #13 0x7ff4135114c3 in driDestroyContext () from /usr/lib64/dri/nouveau_dri.so #14 0x7ff43f3343af in dri2_destroy_context () from /lib64/libGL.so.1 #15 0x7ff43f3078d9 in glXDestroyContext () from /lib64/libGL.so.1 #16 0x7ff44ab9f401 in QGLXContext::~QGLXContext() () from /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #17 0x7ff44ab9f429 in QGLXContext::~QGLXContext() () from /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #18 0x7ff4422f0a0b in QOpenGLContext::destroy() () from /lib64/libQt5Gui.so.5 #19 0x7ff4422f0fe7 in QOpenGLContext::~QOpenGLContext() () from
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #50 from Omar Amin <omar.moh.a...@gmail.com> --- Sure. I'll max tomorrow send you a list of screenshots with the colors for feedback, I've found a side effect from my patch and i'm working on it and will get back to you soon. Omar -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 Omar Amin <omar.moh.a...@gmail.com> changed: What|Removed |Added Attachment #98977|0 |1 is obsolete|| --- Comment #47 from Omar Amin <omar.moh.a...@gmail.com> --- Created attachment 99002 --> https://bugs.kde.org/attachment.cgi?id=99002=edit group border fitting, different background colors for grouped images. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #42 from Omar Amin <omar.moh.a...@gmail.com> --- Created attachment 98977 --> https://bugs.kde.org/attachment.cgi?id=98977=edit Not final patch, just a trial for feedback -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #39 from Omar Amin <omar.moh.a...@gmail.com> --- Dear Mr Gilles, I've attached three images for the three problems i'm currently addressing: 1- Group border was transparent so when the theme is changed to black background, the border is visible, but i think it can be better, please let me know your opinion. 2- The Image to be totally included inside the thumbnail, i'm still solving this, what i'm trying to do is to limit the image thumbnail size (the space in which the image and its border to be drawn within) to make sure that the image and its border doesn't go outside the thumbnail also, they doesn't overlay the group indicator 3- the grouped images background color while expanded as requested by Mr Jens. What i'm trying to do: 1- to add to each theme two more appropriate colors one for the grouped images background color while expanded, the other to choose the border color depending on the theme, the current setting is suitable when the background is white, but it doesn't look good when using any other background color. 2- resize the image thumbnail to fit within a max width and max height that are a function of the slider value in the buttom right so as to the grouped border fit within the image thumbnail as requested, but i didn't manage to do it yet. If there're other requests please let me know what are they, and i'll finish within the next couple of days. I'm expecting to finish these suggestions max by tomorrow(Friday) or by Saturday. I'm sorry for the long delay, it won't happen again Thank you, Omar -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #38 from Omar Amin <omar.moh.a...@gmail.com> --- Created attachment 98939 --> https://bugs.kde.org/attachment.cgi?id=98939=edit Group images highlighted when group is expanded -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #37 from Omar Amin <omar.moh.a...@gmail.com> --- Created attachment 98938 --> https://bugs.kde.org/attachment.cgi?id=98938=edit progress in ensure the image border doesn't go outside the thumbnail border, temp solution -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #36 from Omar Amin <omar.moh.a...@gmail.com> --- Created attachment 98937 --> https://bugs.kde.org/attachment.cgi?id=98937=edit Black background theme, group bordered is filled -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #32 from Omar Amin <omar.moh.a...@gmail.com> --- if we need to use the rotated borders, we can adjust the border for each image at different thumbnail sizes differently that will make us able to fit the rotated borders at different thumbnail sizes entirely inside the image rectangle, the only withdraw for this approach would be it'll show less number of images per row in the album grid. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #31 from Omar Amin <omar.moh.a...@gmail.com> --- Dear Mr Gilles and Mr Jens, I made this simple stack just for confirming if that's what we need or not?, i made it on a separate project to make the compilation quicker, that's why not all digKam image info is shown nor the borders, it's just for confirming the view and if that's what's required or not. I'll still make the turned corner, or did i misunderstood the requirements? I didn't fully understand what you mean by: - "I think that we must to render a smallest thumb with a largest border in case of grouped items" do you mean that the border will be of different size for different images? and "Just try to make the grouped border frame better, to render it inside the thumbnails, not outside" how can the rotated frames fit inside the thumbnail? if you can clarify more that would be perfect. sorry for inconvenience. Regards, Omar -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #30 from Omar Amin <omar.moh.a...@gmail.com> --- Created attachment 98715 --> https://bugs.kde.org/attachment.cgi?id=98715=edit stack proposal -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #26 from Omar Amin <omar.moh.a...@gmail.com> --- (In reply to caulier.gilles from comment #25) > Note : LightRoom groupped items is called "Image Stacked". It's explained > here : > > http://valeriegoettsch.com/lightroom-grid-view-icons/ > > Excepted the icon+number of items in the stack, no specify frames is draw. > > Gilles Thanks for the feedback. to start working i just want to make sure that i understood what's required. In the following image http://valeriegoettsch.com/wp-content/uploads/badges-diagram.jpg I'll imitate the following features: - Stack (stating 1 of 2 -- where 2 is the group images count) - the virtual copy (do i need to draw the turned corner to indicate visually that this is a group ?) in the following image https://bugs.kde.org/attachment.cgi?id=98577=edit What about the icon in the bottom right on which the number of grouped images is written ? should it be removed? Thank you, Omar -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #22 from Omar Amin <omar.moh.a...@gmail.com> --- Dear Mr Gilles, I'm sorry for being late, attached the new patch containing the modifications needed for centring the thumbnail inside the group borders, If we have time I can work on the other needed modifications (grouped images different background colour and the darker group border) and get back to you as soon as I finish them. Omar -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 Omar Amin <omar.moh.a...@gmail.com> changed: What|Removed |Added Attachment #98455|0 |1 is obsolete|| --- Comment #21 from Omar Amin <omar.moh.a...@gmail.com> --- Created attachment 98630 --> https://bugs.kde.org/attachment.cgi?id=98630=edit Group border modification patch v2 Contains code for centring thumbnail inside new group borders -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #17 from Omar Amin <omar.moh.a...@gmail.com> --- Hello, I've fixed the centring issue for the thumbnail and have attached a sample for 3 different groups, please let me know if you think they're still not symmetrical. Regarding the large thumbnail support, I've tried to reproduce this issue on my PC but couldn't I tried the following >From Settings->Configure-digiKam --> Album View : I checked the option --> use large thumbnail size for high screen resolution and restart digiKam for this option to take effect, but nothing happened Also from Tools-> Maintenance : I checked the rebuild thumbnails and restarted digiKam but nothing happened. Do I need to have an HD screen for this option to take effect? I'll still search for the code responsible for handling this issue and get back to you with the patch once i finish it. Thank you :) Omar -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 Omar Amin <omar.moh.a...@gmail.com> changed: What|Removed |Added Attachment #98456|0 |1 is obsolete|| --- Comment #16 from Omar Amin <omar.moh.a...@gmail.com> --- Created attachment 98577 --> https://bugs.kde.org/attachment.cgi?id=98577=edit Thumbnail centred -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #15 from Omar Amin <omar.moh.a...@gmail.com> --- Dear Mr Gilles, I'm sorry for being late, I'll start today on it, and also tomorrow will be working on it the whole day, and will send a patch tomorrow max. Mr Jens, yes for sure i can, I'll also try to do the grouped background color and get back to you :) Regards, Omar -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #10 from Omar Amin <omar.moh.a...@gmail.com> --- Created attachment 98456 --> https://bugs.kde.org/attachment.cgi?id=98456=edit Screenshot of the new grouped images border -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #9 from Omar Amin <omar.moh.a...@gmail.com> --- Created attachment 98455 --> https://bugs.kde.org/attachment.cgi?id=98455=edit Group border modification patch This patch is for grouped images border new background -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #7 from Omar Amin <omar.moh.a...@gmail.com> --- Hi Mr Gilles, I'll look into it during this week, and will finish it by next Friday, Please let me know if you need it finished earlier. Regards, Omar -- You are receiving this mail because: You are watching all bug changes.
