[kdeplasma-addons] [Bug 476161] Ability to use the new Cube effect as animation when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=476161 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465608] Widgets move to the left each time Plasma restarts
https://bugs.kde.org/show_bug.cgi?id=465608 --- Comment #1 from Alexander Kernozhitsky --- The bug is present only after updating to 5.26.90. Before that, the widgets might move to the left sometimes, but it happened at most one and whey didn't move anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465608] Widgets move to the left each time Plasma restarts
https://bugs.kde.org/show_bug.cgi?id=465608 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465608] New: Widgets move to the left each time Plasma restarts
https://bugs.kde.org/show_bug.cgi?id=465608 Bug ID: 465608 Summary: Widgets move to the left each time Plasma restarts Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: sh200...@mail.ru CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY Suppose you have a panel in the left of the screen and some plasmoids on the desktop. Then, after each restart of Plasma, the widgets will move a bit left. After many restarts, they will move steadily to the left edge of the screen. STEPS TO REPRODUCE 1. Place panel to the left 2. Place some plasmoids on desktop 3. Restart Plasma many times OBSERVED RESULT The widgets move left on each restart EXPECTED RESULT The widgets remain on the same position as before the restart SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION See also https://bugs.kde.org/show_bug.cgi?id=458038#c19. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397388] Kdevelop crash everytime I click in one specific option.
https://bugs.kde.org/show_bug.cgi?id=397388 Alexander Kernozhitsky changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #16 from Alexander Kernozhitsky --- The issue is still reproducible. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461301] Cannot paste from Scintilla GTK widget to KDE apps
https://bugs.kde.org/show_bug.cgi?id=461301 --- Comment #2 from Alexander Kernozhitsky --- The bug seems to be on the Scintilla side, see https://sourceforge.net/p/scintilla/bugs/2361/#ec34 for more details. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461301] Cannot paste from Scintilla GTK widget to KDE apps
https://bugs.kde.org/show_bug.cgi?id=461301 --- Comment #1 from Alexander Kernozhitsky --- Another observation is that the text copied from Scintilla is not shown in Klipper history. Still, it can be pasted successfully into GTK apps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461301] Cannot paste from Scintilla GTK widget to KDE apps
https://bugs.kde.org/show_bug.cgi?id=461301 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461301] New: Cannot paste from Scintilla GTK widget to KDE apps
https://bugs.kde.org/show_bug.cgi?id=461301 Bug ID: 461301 Summary: Cannot paste from Scintilla GTK widget to KDE apps Classification: Plasma Product: kwin Version: 5.26.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: sh200...@mail.ru Target Milestone: --- SUMMARY If I try to copy some text from Scintilla widget and paste it into a KDE app, then nothing is pasted. Though, pasting into XWayland or GTK apps works fine. The bug is reproducible both with Geany 1.38 ( https://github.com/geany/geany/issues/3320 ) and SciTE 5.3.1. See also: https://sourceforge.net/p/scintilla/bugs/2361/. Quoting a Scintilla maintainer, > Copying the path with the File | Copy Path command does copy to Kate. That is > using the simpler gtk_clipboard_set_text API instead of > gtk_clipboard_set_with_data which is called in Scintilla to allow multiple > formats and asynchronous access. Its likely that the current KDE > implementation on Wayland has a problem with this API or its use. Since it > works with GTK applications on Debian + Wayland and also with KDE > applications on Ubuntu + Wayland, I'd hope that it gets fixed with updates to > KDE's Wayland support. STEPS TO REPRODUCE 1. Open Plasma Wayland session 2. Open a Scintilla-based editor (SciTE or Geany) 3. Enter some text and copy it to the clipboard 4. Paste into a KDE app (e.g. Kate) OBSERVED RESULT No text is pasted. EXPECTED RESULT Copied test must be pasted into the KDE app. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 455513] Small icons no longer respect the "Small Icon" size configurable in the Icons KCM
https://bugs.kde.org/show_bug.cgi?id=455513 --- Comment #15 from Alexander Kernozhitsky --- > I guess to fix this in Breeze, we would need to: > 1. look at the small size value set in system settings > 2. map it to a KIconLoader icon size constant (e.g. small, smallMedium, etc) > 3. figure out the next largest KIconLoader icon size from that > 4. when in Tablet Mode, use that larger value I created a merge request that does exactly what you described :) -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 438206] Fails to build against Python 3.10
https://bugs.kde.org/show_bug.cgi?id=438206 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 455513] Small icons no longer respect the "Small Icon" size configurable in the Icons KCM
https://bugs.kde.org/show_bug.cgi?id=455513 --- Comment #12 from Alexander Kernozhitsky --- > The code assumes that a small icon is always 16, probably because the author > didn't know or forgot that the small icon size is configurable in the Icons > KCM. The code is also Breeze-specific, meaning that if I switch the application theme to something else, then it will use the icon size configured in the KCM (which resides in SmallIcons section in ~/.config/kdeglobals). Also, magic hard-coded values in the source code are usually bad. I don't really know how Tablet mode is made, but I assume that this fix should go to System settings or whatever sets the icon sizes. If the Tablet mode is Breeze-specific itself, then making the icons one step bigger is also a good solution. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 455513] Small icons no longer respect the "Small Icon" size configurable in the Icons KCM
https://bugs.kde.org/show_bug.cgi?id=455513 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API
https://bugs.kde.org/show_bug.cgi?id=438883 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430882] New: Please make icon sizes (or at least row count) configurable
https://bugs.kde.org/show_bug.cgi?id=430882 Bug ID: 430882 Summary: Please make icon sizes (or at least row count) configurable Product: plasmashell Version: 5.20.4 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: sh200...@mail.ru CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY I am using Plasma with vertical panel layout. The system tray icon size is now hard-coded to smallMedium (which is 24px), and is too small for me. Fortunately, Plasma 5.20 adds a feature to fit the icon sizes to panel width. But in vertical panel case (which has ~80px width for me), the icons become too large. So, it would be nice to have an option to configure icon sizes in system tray. An alternative option would be to allow setting the number of rows for system tray icons. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.9.0-5-amd64 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 430881] New: Icon title consumes too much space (at least in Russian translation)
https://bugs.kde.org/show_bug.cgi?id=430881 Bug ID: 430881 Summary: Icon title consumes too much space (at least in Russian translation) Product: Plasma Vault Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: sh200...@mail.ru Target Milestone: --- Created attachment 134357 --> https://bugs.kde.org/attachment.cgi?id=134357&action=edit Screenshot of Plasma Vault in Russian i18n SUMMARY After upgrading to Plasma 5.20.4, I noticed that the unlock icon near the folder name now has a title. But the title is too long, so I can't see the encrypted folder name. See the screenshot for details. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.9.0-5-amd64 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430705] New: Split position changes after disabling and enabling the split mode
https://bugs.kde.org/show_bug.cgi?id=430705 Bug ID: 430705 Summary: Split position changes after disabling and enabling the split mode Product: dolphin Version: 20.12.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: split view Assignee: dolphin-bugs-n...@kde.org Reporter: sh200...@mail.ru CC: kfm-de...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Turn the split mode on and change the split position 2. Turn the split mode off 3. Turn the split mode on again OBSERVED RESULT The split positions at steps 1 and 3 are different. EXPECTED RESULT The split positions at steps 1 and 3 are must be the same. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.2 Kernel Version: 5.9.0-5-amd64 OS Type: 64-bit ADDITIONAL INFORMATION This is a regression since Dolphin 20.08. I notice the bug often enough, as I disable the split mode and re-enable it again to make the contents of both panels the same. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 334733] Okular txt backend chokes on unicode text
https://bugs.kde.org/show_bug.cgi?id=334733 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru --- Comment #6 from Alexander Kernozhitsky --- Just tried on Okular 20.12.0, the bug is still reproducible for me. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 430538] Markdown files opened as plain text
https://bugs.kde.org/show_bug.cgi?id=430538 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397388] Kdevelop crash everytime I click in one specific option.
https://bugs.kde.org/show_bug.cgi?id=397388 Alexander Kernozhitsky changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #13 from Alexander Kernozhitsky --- I can confirm that the crash is still present on KDevelop 5.6.1. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 430396] New: Runs many programs when executable confirmation settings are changed
https://bugs.kde.org/show_bug.cgi?id=430396 Bug ID: 430396 Summary: Runs many programs when executable confirmation settings are changed Product: frameworks-kio Version: 5.75.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: sh200...@mail.ru CC: kdelibs-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE Use Dolphin (version 20.12.0 or higher is required) 1. Go to "Configure Dolphin > General > Confirmations" and set "When opening executable file" to "Open in application". 2. Find any binary executable (for example, /usr/bin/kate) and click many times to open it 3. Go to "Configure Dolphin > General > Confirmations" and set "When opening executable file" to "Always ask". 4. Click to /usr/bin/kate to open it again, choose "Execute" in the opened dialog OBSERVED RESULT Kate is opened many times. EXPECTED RESULT Kate is opened exactly once. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426341] Dolphin doesn't show number of items in symlinked folder
https://bugs.kde.org/show_bug.cgi?id=426341 --- Comment #2 from Alexander Kernozhitsky --- Noticing the same problem on Debian GNU/Linux testing since 20.08. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426341] Dolphin doesn't show number of items in symlinked folder
https://bugs.kde.org/show_bug.cgi?id=426341 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395532] Dolphin hangs while transferring files via KDE Connect
https://bugs.kde.org/show_bug.cgi?id=395532 --- Comment #2 from Alexander Kernozhitsky --- > Alexander can you please retest on a recent version, thanks. Tested on Dolphin 20.04.3, there is no hang while transferring a file between devices. By the way, the UI is still slow and some freezes are notable while I navigate between folders on KDE Connect. Though, this issue needs a separate bug report. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 408296] KDEInit could not launch /usr/bin/kile
https://bugs.kde.org/show_bug.cgi?id=408296 --- Comment #4 from Alexander Kernozhitsky --- On the recent Debian testing, it seems that I am not able to reproduce this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417787] sshfs key exchange methods deprecated
https://bugs.kde.org/show_bug.cgi?id=417787 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 418597] New: Incorrect plot on function (x-0.7)^2+3*(x-0.7)
https://bugs.kde.org/show_bug.cgi?id=418597 Bug ID: 418597 Summary: Incorrect plot on function (x-0.7)^2+3*(x-0.7) Product: kalgebra Version: 19.12 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: sh200...@mail.ru Target Milestone: --- STEPS TO REPRODUCE 1. Make a plot with the function "(x-0.7)^2+3*(x-0.7)" OBSERVED RESULT The function never passes through zero. EXPECTED RESULT The function must pass through zero when x = 0.7. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 409472] Wrong result coming from calculator and plotter
https://bugs.kde.org/show_bug.cgi?id=409472 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru --- Comment #5 from Alexander Kernozhitsky --- It seems to be duplicate of https://bugs.kde.org/show_bug.cgi?id=402637. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415364] Setting to disable when mouse is plugged in is missing
https://bugs.kde.org/show_bug.cgi?id=415364 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 --- Comment #27 from Alexander Kernozhitsky --- Oops, it seems that switching to QFSWatch doesn't fix this problem fully (I still need to refresh the view manually in my ~/Downloads folder) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 --- Comment #26 from Alexander Kernozhitsky --- Finally, after some hours of debugging and reading the logs I reached the reason of this bug. It's triggered when: - KDirWatch uses inotify as a backend - the watched directory contains a symlink as one of its parent. For example, /d is a symlink to /media/data, and our current directory in Dolphin is something like /d/1/2/3 - the directory is added and then removed: $ while true ; do mkdir abc ; sleep 1 ; rmdir abc ; sleep 1 ; done The problem is that inotify_add_watch reuses the file descriptor if the directory is already watched. When the directory and the another path to it with a symlink (e. g. /d/1/2/3 and /media/data/1/2/3) are watched, inotify API still reuses the file descriptor. But KDirWatch intrinsically considers these path different, so uses different entries for them. The mapping between file descriptors and names is kept in QHash m_inotify_wd_to_entry, so the previous entry here is overwritten. Moreover, when one of these path stops being watched, the file descriptor is freed and the map entry is removed, so the other path doesn't receive events. I don't know how to fix this in a simple way (maybe use canonical paths inside KDirWatch?) Also note that it's the only one scenario in which the file system updates are not delivered, there may be other ways to break it and the separate reasons why this happens. Any missing update in KDirWatch can be the reason. As I stated in the previous message, KDirWatch can use other methods as default (FAM, inotify, QFSWatch and Stat). FAM seems to affect performance. Stat will poll the filesystem each 0.5 seconds, which is not the most efficient way. I don't know anything about QFSWatch and why it's not use as a default. Some comments in the code suggest that it lacks some functionality. As I workaround, I set the environment variable: KDIRWATCH_METHOD=QFSWatch -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 --- Comment #25 from Alexander Kernozhitsky --- I also encountered this bug and tried some more advanced ways to get some info. The best way to reproduce it was while true ; do mkdir abc ; sleep 1 ; rmdir abc ; sleep 1 ; done the extra conditions are: - Details mode - Split View - the directory is on the separate partition (also called /media/data :) ) - when it's reference by symlink The conditions are not necessary, though; I saw it also on files and on non-symlinked directory. Also I noted that it's possible to play with KDirWatch's preferred method using the environment variable, KDIRWATCH_METHOD. Of the four methods available (Fam, inotify, QFSWatch, Stat), I could reproduce the bug only on inotify. Also I was trying to get some more advanced info to detect whether something is wrong with interpreting inotify's data. To do this, I set s_verboseDebug to true in kdirwatch.cpp. I got the following in the log after creating/deleting directory "abc": kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/day4" sub_entry: 0x0 kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/day2" sub_entry: 0x0 kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/trial" sub_entry: 0x0 kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/day1" sub_entry: 0x0 kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/day3" sub_entry: 0x0 kf5.kcoreaddons.kdirwatch: Added Dir "/media/data/Tasks/ptz2020/abc" for "" ["KDirWatch-6"] kf5.kcoreaddons.kdirwatch: inotify successfully used for monitoring "/media/data/Tasks/ptz2020/abc" wd= 82 kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020/abc" (now 2 clients) "[KDirWatch-4]" kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020/day1" (now 2 clients) "[KDirWatch-4]" kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020/day2" (now 2 clients) "[KDirWatch-4]" kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020/day3" (now 2 clients) "[KDirWatch-4]" kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020/day4" (now 2 clients) "[KDirWatch-4]" kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020/trial" (now 2 clients) "[KDirWatch-4]" kf5.kcoreaddons.kdirwatch: got event 0x400 for "/media/data/Tasks/ptz2020/abc" kf5.kcoreaddons.kdirwatch: -->got deleteself signal for "/media/data/Tasks/ptz2020/abc" kf5.kcoreaddons.kdirwatch: 4 "/media/data/Tasks/ptz2020/abc" 2 clients kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020" (for "/media/data/Tasks/ptz2020/abc" ) kf5.kcoreaddons.kdirwatch: "KDirWatch-6" emitting deleted "/media/data/Tasks/ptz2020/abc" kf5.kcoreaddons.kdirwatch: "KDirWatch-4" emitting deleted "/media/data/Tasks/ptz2020/abc" kf5.kcoreaddons.kdirwatch: kf5.kcoreaddons.kdirwatch: scanEntry for "/home/gepardo/.local/share/user-places.xbel" says 0 kf5.kcoreaddons.kdirwatch: "/media/data/Tasks/ptz2020" e->m_ctime= 1580594624 01:03:44 stat_buf.st_ctime= 1580594669 stat_buf.st_mtime= 1580594669 e->m_nlink= 1 stat_buf.st_nlink= 1 e->m_ino= 437305 stat_buf.st_ino= 437305 kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020" says 1 kf5.kcoreaddons.kdirwatch: 1 "/media/data/Tasks/ptz2020" 1 clients kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020/abc" says 0 kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020/day1" says 0 kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020/day2" says 0 kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020/day3" says 0 kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020/day4" says 0 kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020/trial" says 0 kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/abc" sub_entry: 0x0 kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/abc" sub_entry: 0x0 kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020" sub_entry: 0x5622d961b920 kf5.kcoreaddons.kdirwatch: Removed Dir "/media/data/Tasks/ptz2020/abc" for "" ["KDirWatch-4"] During the next creation/deletion rounds, no log entries appeared. I hope this information can be helpful while finding the bug, and I'll try to dig more of it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403484] many classes not resolved by C++ indexer
https://bugs.kde.org/show_bug.cgi?id=403484 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP transfer corrupts all files
https://bugs.kde.org/show_bug.cgi?id=405847 --- Comment #20 from Alexander Kernozhitsky --- Just tested it now, I am unable to reproduce this issue also on 1.12.93. I also had errors like "Unable to transfer file", but they don't appear now. Seems that it's fixed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 409954] KIO FTP: kioclient hangs while copying file over existing file [copy() did not call finished() or error()]
https://bugs.kde.org/show_bug.cgi?id=409954 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 409057] New: Crash on closing the application
https://bugs.kde.org/show_bug.cgi?id=409057 Bug ID: 409057 Summary: Crash on closing the application Product: ksysguard Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: sh200...@mail.ru Target Milestone: --- Application: ksysguard (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-5-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: Sometimes, when I close KSysGuard, it crashes. Stack trace attached. The crash can be reproduced sometimes. -- Backtrace: Application: Системный монитор (ksysguard), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe876a2e940 (LWP 4386))] Thread 4 (Thread 0x7fe86cf12700 (LWP 4392)): #0 0x7fe87c7f500c in futex_wait_cancelable (private=0, expected=0, futex_word=0x556ad525c688) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe87c7f500c in __pthread_cond_wait_common (abstime=0x0, mutex=0x556ad525c638, cond=0x556ad525c660) at pthread_cond_wait.c:502 #2 0x7fe87c7f500c in __pthread_cond_wait (cond=0x556ad525c660, mutex=0x556ad525c638) at pthread_cond_wait.c:655 #3 0x7fe86d518e03 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fe86d518b57 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fe87c7eefa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7fe88233b4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fe86fdf8700 (LWP 4390)): #0 0x7fe882330819 in __GI___poll (fds=0x7fe868004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe87bf91136 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe87bf9125c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe880ab287b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe880a6027b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe8808afec6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe880da8545 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fe8808b9aa7 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe87c7eefa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7fe88233b4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fe876a2a700 (LWP 4388)): #0 0x7fe87c7f500c in futex_wait_cancelable (private=0, expected=0, futex_word=0x7fe880394150) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe87c7f500c in __pthread_cond_wait_common (abstime=0x0, mutex=0x556ad50a7880, cond=0x7fe880394128) at pthread_cond_wait.c:502 #2 0x7fe87c7f500c in __pthread_cond_wait (cond=0x7fe880394128, mutex=0x556ad50a7880) at pthread_cond_wait.c:655 #3 0x7fe8807293bc in std::condition_variable::wait(std::unique_lock&) () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x7fe87f8bf542 in () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #5 0x7fe87f8bf659 in () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #6 0x7fe88072eb2f in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7fe87c7eefa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7fe88233b4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fe876a2e940 (LWP 4386)): [KCrash Handler] #6 0x7fe88092cb16 in operator==(QString const&, QString const&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe88163e7f7 in QLabel::setText(QString const&) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fe882475484 in () at /usr/lib/x86_64-linux-gnu/libkdeinit5_ksysguard.so #9 0x7fe8820e4dc9 in KSGRD::SensorAgent::processAnswer(char const*, int) () at /usr/lib/x86_64-linux-gnu/libksgrd.so.7 #10 0x7fe8820ec17e in () at /usr/lib/x86_64-linux-gnu/libksgrd.so.7 #11 0x7fe880a8aa43 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fe8809f77ea in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fe8809fdc8d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fe8809fe0d0 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fe880a8a906 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fe880a95fc9 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fe880a96311 in QSocketNotifier::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/lib
[kdeconnect] [Bug 405847] SFTP transfer corrupts all files
https://bugs.kde.org/show_bug.cgi?id=405847 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[klickety] [Bug 408432] Game can be finished twice
https://bugs.kde.org/show_bug.cgi?id=408432 --- Comment #1 from Alexander Kernozhitsky --- Created attachment 120676 --> https://bugs.kde.org/attachment.cgi?id=120676&action=edit Game finished (after falling) -- You are receiving this mail because: You are watching all bug changes.
[klickety] [Bug 408432] Game can be finished twice
https://bugs.kde.org/show_bug.cgi?id=408432 Alexander Kernozhitsky changed: What|Removed |Added Platform|Other |Debian testing -- You are receiving this mail because: You are watching all bug changes.
[klickety] [Bug 408432] New: Game can be finished twice
https://bugs.kde.org/show_bug.cgi?id=408432 Bug ID: 408432 Summary: Game can be finished twice Product: klickety Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: shuizhuyuan...@hotmail.com Reporter: sh200...@mail.ru CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 120675 --> https://bugs.kde.org/attachment.cgi?id=120675&action=edit Game finished SUMMARY The program can show that the game is finished while the blocks are falling. When the blocks finish falling, you sometimes can continue playing the game. So, it can be finished twice. See the screenshots attached (after I enter my name into the high score table, the game continues) -- You are receiving this mail because: You are watching all bug changes.
[knavalbattle] [Bug 408430] New: Network player cannot shot twice after hit
https://bugs.kde.org/show_bug.cgi?id=408430 Bug ID: 408430 Summary: Network player cannot shot twice after hit Product: knavalbattle Version: 2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: roney...@gmail.com Reporter: sh200...@mail.ru CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY On a network game, when a player hits a ship, the next move is performed by his opponent. In normal battleship game, the player is allowed to shot once more after a successful shot. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[knavalbattle] [Bug 408429] New: Borders are not visible and not added
https://bugs.kde.org/show_bug.cgi?id=408429 Bug ID: 408429 Summary: Borders are not visible and not added Product: knavalbattle Version: 2.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: roney...@gmail.com Reporter: sh200...@mail.ru CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 120666 --> https://bugs.kde.org/attachment.cgi?id=120666&action=edit KDE3 feature screenshot SUMMARY In adjacent ships mode, when a player hits a ship, he is still able to shot the adjacent cells, though it would be good to forbid it. STEPS TO REPRODUCE 1. Enable adjacent ship mode 2. Start new game 3. Beat an opponent's ship 4. Try to shot a cell adjacent to ship OBSERVED RESULT The shot happens EXPECTED RESULT After the ship's death, border cells must prevent the user from shoting on them. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION This feature is present in KDE3 version (see the attachment), but current version by some reason lacks this. Also, when playing by network with a program from KDE3, the borders seem to be present, but they are not shown. -- You are receiving this mail because: You are watching all bug changes.
[kregexpeditor] [Bug 408425] New: Pressing Enter on every widget navigates to outdated docs.kde.org
https://bugs.kde.org/show_bug.cgi?id=408425 Bug ID: 408425 Summary: Pressing Enter on every widget navigates to outdated docs.kde.org Product: kregexpeditor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: blac...@kde.org Reporter: sh200...@mail.ru Target Milestone: --- STEPS TO REPRODUCE 1. Enter some regexp (like /[kde]*/) 2. Press on "One of the following characters" widget 3. Press Enter OBSERVED RESULT https://docs.kde.org/index.php?branch=stable5&language=ru_RU&application=kregexpeditor&path=/kregexpeditor/index.html is opened. The page says that "The application kregexpeditor could not be found." EXPECTED RESULT Nothing happens, or, at least, the link to the valid docs is opened. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION This is especially annoying when pressing "Enter" on text fields. -- You are receiving this mail because: You are watching all bug changes.
[kregexpeditor] [Bug 91686] POSIX [:space:] character class not detected.
https://bugs.kde.org/show_bug.cgi?id=91686 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru --- Comment #3 from Alexander Kernozhitsky --- > Could you help us out and re-test if the bug is valid in the latest version? Yes, the bug is still valid. -- You are receiving this mail because: You are watching all bug changes.
[kregexpeditor] [Bug 408424] New: Crash when built in debug mode
https://bugs.kde.org/show_bug.cgi?id=408424
Bug ID: 408424
Summary: Crash when built in debug mode
Product: kregexpeditor
Version: unspecified
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: blac...@kde.org
Reporter: sh200...@mail.ru
Target Milestone: ---
SUMMARY
STEPS TO REPRODUCE
1. Put a text field
2. Choose "Alternative" tool button
3. Press on a text field ("plus" cursor is shown)
OBSERVED RESULT
When build in Debug mode, I get the following:
ASSERT: "dynamic_cast(_children.at(0))" in file
/home/gepardo/tmp/kregexpeditor/src/concwidget.cpp, line 99
In release mode it just behaves weirdly and the changes are not reflected in
the ASCII syntax.
EXPECTED RESULT
Nothing should happen (or the Alternative added outside of the text field)
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
ADDITIONAL INFORMATION
I am using the latest git snapshot.
--
You are receiving this mail because:
You are watching all bug changes.
[kile] [Bug 408297] New: \end{gathered} not highligted correctly
https://bugs.kde.org/show_bug.cgi?id=408297
Bug ID: 408297
Summary: \end{gathered} not highligted correctly
Product: kile
Version: 2.9.92
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: editor
Assignee: michel.lud...@kdemail.net
Reporter: sh200...@mail.ru
Target Milestone: ---
Created attachment 120567
--> https://bugs.kde.org/attachment.cgi?id=120567&action=edit
Highlighting bug
SUMMARY
See the screenshot attached. On line 21, \end{gathered} is highlighted with two
different colors.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
--
You are receiving this mail because:
You are watching all bug changes.
[kile] [Bug 408296] New: KDEInit could not launch /usr/bin/kile
https://bugs.kde.org/show_bug.cgi?id=408296 Bug ID: 408296 Summary: KDEInit could not launch /usr/bin/kile Product: kile Version: 2.9.92 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: sh200...@mail.ru Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open Kile 2. Open any TeX document from Dolphin (Kile must be associated with TeX files) OBSERVED RESULT You will see a dialog saying smth like "KDEInit could not launch /usr/bin/kile" (my locale is not English, so the translation of the message may be not precise). The document is opened. EXPECTED RESULT No such dialog appears. The document is opened. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361606] GTK theme is buggy ,icons are overlapped and some time there is no text to display
https://bugs.kde.org/show_bug.cgi?id=361606 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru --- Comment #3 from Alexander Kernozhitsky --- Is the bug still valid? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 358005] gtk3-engines-breeze: script-not-executable
https://bugs.kde.org/show_bug.cgi?id=358005 Alexander Kernozhitsky changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||sh200...@mail.ru Version Fixed In||5.15.0 --- Comment #2 from Alexander Kernozhitsky --- render_assets.sh script is not installed now, and at least since 5.15 there's not such file. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 377568] Please install all the gtk-3.* themes
https://bugs.kde.org/show_bug.cgi?id=377568 Alexander Kernozhitsky changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||sh200...@mail.ru Resolution|--- |WAITINGFORINFO --- Comment #1 from Alexander Kernozhitsky --- The theme has changed much since 5.15 and it seems that this bug is fixed there (both gtk-3.18 and gtk-3.20 are installed). Can you please check if the bug is still valid? -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 201515] "Create -> Implicit Plot" freezes application
https://bugs.kde.org/show_bug.cgi?id=201515 Alexander Kernozhitsky changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Version|unspecified |1.3.0 Status|RESOLVED|REOPENED CC||sh200...@mail.ru --- Comment #4 from Alexander Kernozhitsky --- The bug is still valid :) I think it's better to use another function as a default, or use different default functions for different scale. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 331539] All messages disappear after deleting one
https://bugs.kde.org/show_bug.cgi?id=331539 Alexander Kernozhitsky changed: What|Removed |Added CC|sh200...@mail.ru| -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 391182] kmail --composer return an error and doesn't open
https://bugs.kde.org/show_bug.cgi?id=391182 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 331539] All messages disappear after deleting one
https://bugs.kde.org/show_bug.cgi?id=331539 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405081] Windows contents are not fully rendered when moving to corner
https://bugs.kde.org/show_bug.cgi?id=405081 --- Comment #2 from Alexander Kernozhitsky --- (In reply to David Edmundson from comment #1) > And this happens reliably with other windows too? Could reproduce it with Kile and System Settings (other windows have a smaller minimum size). Other people in KDE Russian Telegram channel could reproduce it with other applications, like Octopi. > Please include output of: > qdbus org.kde.KWin /KWin supportInformation https://paste.ubuntu.com/p/CHMzSwXYCR/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405081] New: Windows contents are not fully rendered when moving to corner
https://bugs.kde.org/show_bug.cgi?id=405081 Bug ID: 405081 Summary: Windows contents are not fully rendered when moving to corner Product: kwin Version: 5.14.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: sh200...@mail.ru Target Milestone: --- Created attachment 118544 --> https://bugs.kde.org/attachment.cgi?id=118544&action=edit Screenshot illustrating the bug STEPS TO REPRODUCE 1. Choose a window which minimum allowed size is more than 1/2 width and 1/2 height of the screen (e.g. systemsettings5) 2. Move it to the corner to stretch it to 25% of the screen (best reproducible when moving to the top left corner) 3. Resize it very slightly OBSERVED RESULT The window contents are not fully rendered (see the screenshot) EXPECTED RESULT The window contents are fully rendered SOFTWARE/OS VERSIONS KDE Plasma Version: 5.14.5 (also reproducible on 5.15.2) KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 403108] No visible indication of active tab in Chromium using dark GTK3 theme
https://bugs.kde.org/show_bug.cgi?id=403108 --- Comment #3 from Alexander Kernozhitsky --- Created attachment 117483 --> https://bugs.kde.org/attachment.cgi?id=117483&action=edit Chromium on different color schemes I just did some experimenting to see how Chromium looks on other GTK themes. I used Breeze in different variants (also with a custom color scheme which uses different colors for different elements), also tried Numix and Adwaita. It seems that breeze theme takes the same color for the background and tabs, despite of the color scheme used. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 402653] Crash while choosing the application menu icon on Debian
https://bugs.kde.org/show_bug.cgi?id=402653 --- Comment #1 from Alexander Kernozhitsky --- More detailed crash dump: (gdb) backtrace #0 0x75bd641e in QString::mid(int, int) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7739f1b9 in sortByFileName (path1=..., path2=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qchar.h:88 #2 0x773a2aa1 in __gnu_cxx::__ops::_Val_comp_iter::operator()::iterator> (this=, __it=..., __val=...) at /usr/include/c++/8/bits/predefined_ops.h:214 #3 std::__unguarded_linear_insert::iterator, __gnu_cxx::__ops::_Val_comp_iter > (__last=..., __comp=__comp@entry=...) at /usr/include/c++/8/bits/stl_algo.h:1828 #4 0x773a12fc in std::__unguarded_insertion_sort::iterator, __gnu_cxx::__ops::_Iter_comp_iter > (__first=..., __comp=..., __last=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:239 #5 std::__final_insertion_sort::iterator, __gnu_cxx::__ops::_Iter_comp_iter > (__comp=..., __last=..., __first=...) at /usr/include/c++/8/bits/stl_algo.h:1886 #6 std::__sort::iterator, __gnu_cxx::__ops::_Iter_comp_iter > ( __comp=..., __last=..., __first=...) at /usr/include/c++/8/bits/stl_algo.h:1971 #7 std::sort::iterator, bool (*)(QString const&, QString const&)> (__first=..., __last=..., __comp= 0x7739f140 ) at /usr/include/c++/8/bits/stl_algo.h:4866 #8 KIconDialog::KIconDialogPrivate::showIcons (this=0x55f0ecc0) at ./src/kicondialog.cpp:447 #9 0x75d3728b in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7680d9e1 in QComboBox::activated(int) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7680fa6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x768114aa in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7681751d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x75d3728b in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7680dc92 in QComboBoxPrivateContainer::itemSelected(QModelIndex const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7680e251 in QComboBoxPrivateContainer::eventFilter(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x75d0dd4b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x76716481 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7671dd18 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x75d0e039 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7671d019 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7676f6c3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x76771e8e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 402653] Crash while choosing the application menu icon on Debian
https://bugs.kde.org/show_bug.cgi?id=402653 Alexander Kernozhitsky changed: What|Removed |Added Component|general |general Product|plasmashell |frameworks-kiconthemes Version|5.14.3 |5.51.0 Assignee|k...@davidedmundson.co.uk|cf...@kde.org Platform|Debian stable |Debian testing Target Milestone|1.0 |--- CC||kdelibs-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402653] New: Crash while choosing the application menu icon on Debian
https://bugs.kde.org/show_bug.cgi?id=402653 Bug ID: 402653 Summary: Crash while choosing the application menu icon on Debian Product: plasmashell Version: 5.14.3 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sh200...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.3) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.19.0-1-amd64 x86_64 Distribution: Debian GNU/Linux buster/sid -- Information about the crash: Hello, I was trying to configure the icon for the application menu. I went to application menu confguration and got to the icon chooser dialog. But it crashes if I try to select any icon category other than Applications. I am using Papirus icon theme, and this bug is not reproducible with Breeze icons. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fec79b896c0 (LWP 1051))] Thread 15 (Thread 0x7fec40ff9700 (LWP 1425)): #0 0x7fec80537804 in __GI___libc_read (nbytes=16, buf=0x7fec40ff8b20, fd=63) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7fec80537804 in __GI___libc_read (fd=63, buf=0x7fec40ff8b20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fec7e089180 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fec7e04391f in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fec7e043df0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fec7e043f6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fec80a4dd2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fec809fad0b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fec8084a0c6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fec82165385 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fec80853c97 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fec7f57cfa3 in start_thread (arg=) at pthread_create.c:486 #12 0x7fec8054688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7fec417fa700 (LWP 1416)): #0 0x7fec7f582fec in futex_wait_cancelable (private=0, expected=0, futex_word=0x564e02f3f274) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fec7f582fec in __pthread_cond_wait_common (abstime=0x0, mutex=0x564e02f3f220, cond=0x564e02f3f248) at pthread_cond_wait.c:502 #2 0x7fec7f582fec in __pthread_cond_wait (cond=0x564e02f3f248, mutex=0x564e02f3f220) at pthread_cond_wait.c:655 #3 0x7fec8085444b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fec5f93bd30 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fec5f93fae8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fec5f93ae3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fec5f93fb42 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fec5f93ae3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fec5f93fb42 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fec5f93ae3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fec5f93fb42 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7fec5f93ae3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7fec5f93dbb9 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7fec80853c97 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fec7f57cfa3 in start_thread (arg=) at pthread_create.c:486 #16 0x7fec8054688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7fec41ffb700 (LWP 1415)): #0 0x7fec7f582fec in futex_wait_cancelable (private=0, expected=0, futex_word=0x564e02f3f274) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fec7f582fec in __pthread_cond_wait_common (abstime=0x0, mutex=0x564e02f3f220, cond=0x564e02f3f248) at pthread_cond_wait.c:502 #2 0x7fec7f582fec in __pthread_cond_wait (cond=0x564e02f3f248, mutex=0x564e02f3
[kalgebra] [Bug 402637] KAlgebra produces wrong output on functions like root(x, 3) or x^(1/3)
https://bugs.kde.org/show_bug.cgi?id=402637 --- Comment #1 from Alexander Kernozhitsky --- So, basically, there are two issues: 1) If qalculate returns complex number, KAlgebra uses only its real part, which produces wrong answer 2) root(-8;3) = -2 in qalculate, but seems that root(x;y) is implemented via x^(1/y) in KAlgrebra, so the same bug here. -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 402637] New: KAlgebra produces wrong output on functions like root(x, 3) or x^(1/3)
https://bugs.kde.org/show_bug.cgi?id=402637 Bug ID: 402637 Summary: KAlgebra produces wrong output on functions like root(x, 3) or x^(1/3) Product: kalgebra Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: sh200...@mail.ru Target Milestone: --- Created attachment 117143 --> https://bugs.kde.org/attachment.cgi?id=117143&action=edit Screenshot SUMMARY STEPS TO REPRODUCE Try to make plots for functions like x^(1/3) or root(x, 3) in KAlgebra. Also (-8)^(1/3) gives 1, not -2. OBSERVED RESULT See the screenshot attached. EXPECTED RESULT The function plot looks properly, and (-8)^(1/3) gives -2 as a result. ADDITIONAL INFORMATION This seems to be a bug in Qalculate, which is used by KAlgebra, because qalc gives the following as a result: $ qalc > (-8)^(1/3) (-8)^(1 / 3) = approx. 1 + 1,7320508i -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397388] Kdevelop crash everytime I click in one specific option.
https://bugs.kde.org/show_bug.cgi?id=397388 --- Comment #11 from Alexander Kernozhitsky --- By the way, I use Debian Testing. Maybe this bug is distro-specific. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397388] Kdevelop crash everytime I click in one specific option.
https://bugs.kde.org/show_bug.cgi?id=397388 Alexander Kernozhitsky changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397388] Kdevelop crash everytime I click in one specific option.
https://bugs.kde.org/show_bug.cgi?id=397388 --- Comment #9 from Alexander Kernozhitsky --- Created attachment 116334 --> https://bugs.kde.org/attachment.cgi?id=116334&action=edit New crash information added by DrKonqi kdevelop (5.2.4) using Qt 5.11.2 The crash is still reproducible. I have both heaptrack and heaptrack_gui installed. -- Backtrace (Reduced): #6 0x in () [...] #8 0x7f44431bfcc9 in KJob::finished(KJob*, KJob::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #9 0x7f44431c0418 in KJob::~KJob() () at /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #10 0x7f440e9ab049 in Heaptrack::Job::~Job() (this=0x556864164b30, __in_chrg=) at ./plugins/heaptrack/job.cpp:108 #11 0x7f444233625b in QObjectPrivate::deleteChildren() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397388] Kdevelop crash everytime I click in one specific option.
https://bugs.kde.org/show_bug.cgi?id=397388 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 397086] kdeconnect freezes plasmashell during move operation
https://bugs.kde.org/show_bug.cgi?id=397086 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru --- Comment #1 from Alexander Kernozhitsky --- Getting the same issue, but there are not too much log entries from kdeconnect. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 389709] LibreOffice (gtk3) page scrollbars broken with breeze-gtk ('regular'; Breeze-Dark works fine)
https://bugs.kde.org/show_bug.cgi?id=389709 --- Comment #6 from Alexander Kernozhitsky --- > Can you submit the patch to phabricator? Otherwise, I think it might take > longer until breeze developers merge it. Done. Created https://phabricator.kde.org/D15110. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 389709] LibreOffice (gtk3) page scrollbars broken with breeze-gtk ('regular'; Breeze-Dark works fine)
https://bugs.kde.org/show_bug.cgi?id=389709 --- Comment #4 from Alexander Kernozhitsky --- BTW, the sizes of scrollbar button are OK in breeze-dark, so the issue is not reproducible there. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 389709] LibreOffice (gtk3) page scrollbars broken with breeze-gtk ('regular'; Breeze-Dark works fine)
https://bugs.kde.org/show_bug.cgi?id=389709
Alexander Kernozhitsky changed:
What|Removed |Added
CC||sh200...@mail.ru
--- Comment #3 from Alexander Kernozhitsky ---
As for me, the following patch fixed the issue:
--- gtk.css.old 2018-07-31 15:32:44.0 +0300
+++ gtk.css 2018-08-27 18:19:33.273586541 +0300
@@ -3189,8 +3189,8 @@
border-color: @theme_bg_color;
margin: 0px; }
scrollbar button {
-min-width: 5px;
-min-height: 5px;
+min-width: 14px;
+min-height: 14px;
margin: 0px;
padding: 0px 0px;
border: none;
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 395532] New: Dolphin hangs while transferring files via KDE Connect
https://bugs.kde.org/show_bug.cgi?id=395532 Bug ID: 395532 Summary: Dolphin hangs while transferring files via KDE Connect Product: dolphin Version: 18.04.0 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sh200...@mail.ru CC: elvis.angelac...@kde.org Target Milestone: --- When I transfer files via KDE Connect, I can't do any other things in Dolphin: the UI hangs until the copying is finished. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 395527] Ark crash when trying to open RAR archives.
https://bugs.kde.org/show_bug.cgi?id=395527 --- Comment #1 from Alexander Kernozhitsky --- Removing unrar-free prevents ark from crashing. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 395527] New: Ark crash when trying to open RAR archives.
https://bugs.kde.org/show_bug.cgi?id=395527 Bug ID: 395527 Summary: Ark crash when trying to open RAR archives. Product: ark Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: sh200...@mail.ru CC: rthoms...@gmail.com Target Milestone: --- Application: ark (18.4.1) Qt Version: 5.10.1 Frameworks Version: 5.46.0 Operating System: Linux 4.16.0-2-amd64 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: I tried to open a RAR achive with Ark and it crashed. Using Debian, with unrar-free and unar installed. Before crash, it printed the following line to the terminal many times: "ark.clirar: Failed to detect UNRAR output." The crash can be reproduced every time. -- Backtrace: Application: Ark (ark), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f40922edd80 (LWP 9416))] Thread 3 (Thread 0x7f4072620700 (LWP 9418)): #0 0x7f408e3fc5d9 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f40887a3439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f40887a354c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f408ed3c1bb in QEventDispatcherGlib::processEvents (this=0x7f406c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f408ecdfb6a in QEventLoop::exec (this=this@entry=0x7f407261fd70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f408eaf57ea in QThread::exec (this=) at thread/qthread.cpp:522 #6 0x7f408c0eadf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f408eafab4f in QThreadPrivate::start (arg=0x7f408c35dd60) at thread/qthread_unix.cpp:376 #8 0x7f408a4ff5aa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f408e406cbf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f407f989700 (LWP 9417)): #0 0x7f408e3fc5d9 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f40879720f7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f4087973d1a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f4082739b19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f408eafab4f in QThreadPrivate::start (arg=0x55740249ac00) at thread/qthread_unix.cpp:376 #5 0x7f408a4ff5aa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f408e406cbf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f40922edd80 (LWP 9416)): [KCrash Handler] #6 0x7f408ec67bf1 in QIODevicePrivate::QRingBufferRef::isEmpty (this=0x5574028c1f78) at ../../include/QtCore/5.10.1/QtCore/private/../../../../../src/corelib/io/qiodevice_p.h:105 #7 (anonymous namespace)::QProcessPoller::QProcessPoller (proc=..., this=0x7fff970ef240) at io/qprocess_unix.cpp:175 #8 QProcessPrivate::waitForFinished (this=this@entry=0x5574028c1ee0, msecs=msecs@entry=5) at io/qprocess_unix.cpp:838 #9 0x7f408ec5d50b in QProcess::waitForFinished (this=, msecs=msecs@entry=5) at io/qprocess.cpp:1920 #10 0x7f4091eda157 in Kerfuffle::CliInterface::killProcess (this=this@entry=0x557402897870, emitFinished=emitFinished@entry=true) at ./kerfuffle/cliinterface.cpp:697 #11 0x7f4091edf03d in Kerfuffle::CliInterface::readStdout (this=0x557402897870, handleAll=) at ./kerfuffle/cliinterface.cpp:804 #12 0x7f408ed112af in QtPrivate::QSlotObjectBase::call (a=0x7fff970ef4c0, r=0x557402897870, this=0x557402ae9430) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378 #13 QMetaObject::activate (sender=sender@entry=0x557402ae3790, signalOffset=, local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7fff970ef4c0) at kernel/qobject.cpp:3750 #14 0x7f408ed11867 in QMetaObject::activate (sender=sender@entry=0x557402ae3790, m=m@entry=0x7f408f140e80 , local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7fff970ef4c0) at kernel/qobject.cpp:3629 #15 0x7f408ec5bdda in QProcess::readyReadStandardOutput (this=this@entry=0x557402ae3790, _t1=...) at .moc/moc_qprocess.cpp:362 #16 0x7f408ec62979 in QProcessPrivate::tryReadFromChannel (this=this@entry=0x5574028c1ee0, channel=channel@entry=0x5574028c2008) at io/qprocess.cpp:1070 #17 0x7f408ec62a8c in QProcessPrivate::_q_canReadStandardOutput (this=this@entry=0x5574028c1ee0) at io/qprocess.cpp:1081 #18 0x7f408ec67da8 in QProcessPrivate::waitForFinished (this=this@entry=0x5574028c1ee0, msecs=msecs@entry=5) at io/qprocess_unix.cpp:859 #19 0x7f408ec5d50b in QProcess::waitForFinished (this=, msecs=msecs@entry=5) at io/qprocess.cpp:1920 #20 0x7f4091eda157 in Kerfuffle::CliInterface::killProces
