[latte-dock] [Bug 400539] Option to disable unread count
https://bugs.kde.org/show_bug.cgi?id=400539 --- Comment #1 from Michail Vourlakos --- Tasks -> Show progress information for tasks -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 400531] Latte only shows an error and does not start properly
https://bugs.kde.org/show_bug.cgi?id=400531 --- Comment #1 from Michail Vourlakos --- How did you install Latte? -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 400531] Latte only shows an error and does not start properly
https://bugs.kde.org/show_bug.cgi?id=400531 --- Comment #2 from Michail Vourlakos --- How did you install Latte? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400436] Crash when saving jpeg files with metadata
https://bugs.kde.org/show_bug.cgi?id=400436 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||6.0.0 Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400540] New: KDE Partition Manager taking an extremely long time to start
https://bugs.kde.org/show_bug.cgi?id=400540 Bug ID: 400540 Summary: KDE Partition Manager taking an extremely long time to start Product: partitionmanager Version: 3.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: dal.delmon...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1.Turn off NFS server. 2.Place entries for NFS shares in /etc/fstab (using systemd automount options) on NFS client computer. 3.Start KDE Partition Manager program on NFS client computer. OBSERVED RESULT The program remains in the disk scanning phase for up to 30 minutes. The main program does not start until many cycles of attempting to mount the missing NFS shares is complete. If the NFS server is up, or the NFS entries are removed from /etc/fstab the program starts normally. EXPECTED RESULT The program should only be in the initial disk scanning phase for a very brief period, and then the program should quickly start. SOFTWARE VERSIONS (available in About System) KDE Plasma Version:5.14.2 KDE Frameworks Version:5.51.0 Qt Version:5.11.2 ADDITIONAL INFORMATION I started running journalctl -f just before starting KDE Partition Manager. It became quickly apparent why the program was not starting as attempt after attempt was being made to mount the missing shares on the NFS server that was down. I only posted this issue hours ago on the Manjaro forum and I already had another very competent user confirm exactly the same symptoms and result. Link to Manjaro forum thread: https://forum.manjaro.org/t/kde-partition-manager-long-start-time-confirmed-bug/63698 Journal output from the time KDE Partition Manager was started: $ journalctl -f -- Logs begin at Sun 2018-10-28 07:25:33 MST. -- Oct 31 15:37:58 htpc1 systemd[643]: Starting Mark boot as successful... Oct 31 15:37:58 htpc1 systemd[643]: Started Mark boot as successful. Oct 31 15:42:29 htpc1 plasmashell[811]: trying to show an empty dialog Oct 31 15:42:29 htpc1 plasmashell[811]: org.kde.plasmaquick: Applet "Application Menu" loaded after 0 msec Oct 31 15:42:29 htpc1 plasmashell[811]: org.kde.plasmaquick: Increasing score for "Application Menu" to 97 Oct 31 15:42:29 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread Oct 31 15:42:29 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread Oct 31 15:42:32 htpc1 plasmashell[811]: trying to show an empty dialog Oct 31 15:42:32 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread Oct 31 15:42:32 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread Oct 31 15:42:34 htpc1 kwin_x11[805]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 35494, resource id: 33554565, major code: 18 (ChangeProperty), minor code: 0 Oct 31 15:42:34 htpc1 kdesu[1366]: qt.core.logging: Ignoring malformed logging rule: '’*=false’' Oct 31 15:42:35 htpc1 kdesud[1370]: qt.core.logging: Ignoring malformed logging rule: '’*=false’' Oct 31 15:42:35 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread Oct 31 15:42:37 htpc1 plasmashell[811]: KActivitiesStats( 0x55e9ae5db4a0 ) ResultModelPrivate::onResultScoreUpdated result added: "applications:org.kde.partitionmanager.desktop" score: 13.2286 last: 1541025754 first: 1538808294 Oct 31 15:42:50 htpc1 su[1375]: (to root) htpc on pts/5 Oct 31 15:42:50 htpc1 su[1375]: pam_unix(su:session): session opened for user root by (uid=1000) Oct 31 15:42:50 htpc1 su[1375]: pam_unix(su:session): session closed for user root Oct 31 15:42:50 htpc1 kwin_x11[805]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 38305, resource id: 65011729, major code: 18 (ChangeProperty), minor code: 0 Oct 31 15:42:50 htpc1 su[1378]: (to root) htpc on pts/5 Oct 31 15:42:50 htpc1 su[1378]: pam_unix(su:session): session opened for user root by (uid=1000) Oct 31 15:42:51 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner) Oct 31 15:42:51 htpc1 systemd[1]: Mounting /media/nfs/3tb... Oct 31 15:42:51 htpc1 kernel: FS-Cache: Loaded Oct 31 15:42:51 htpc1 kernel: FS-Cache: Netfs 'nfs' registered for caching Oct 31 15:42:51 htpc1 kernel: Key type dns_resolver registered Oct 31 15:42:52 htpc1 kernel: NFS: Registering the id_resolver key type Oct 31 15:42:52 htpc1 kernel: Key type id_resolver registered Oct 31 15:42:52 htpc1 kernel: Key type id_legacy registered Oct 31 15:42:55 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 4833, resource id: 54525969, major code: 142 (Unknown), minor code: 3 Oct 31 15:42:55 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue),
[konsole] [Bug 399291] Don't include trailing colons in URLs for the purpose of double-click selection
https://bugs.kde.org/show_bug.cgi?id=399291 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Nate Graham --- Well anyway, here's a patch: https://phabricator.kde.org/D16578 Let's see what Kurt thinks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400436] Crash when saving jpeg files with metadata
https://bugs.kde.org/show_bug.cgi?id=400436 --- Comment #11 from Patrick Roye --- The new installer did successfully fix the crash for me. I have retested changing tags, exporting JPEG files, and opening the metadata editor on the pictures in my collection. Everything is working correctly now. Thank you so much for your diligence in fixing this bug! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377253] Show option to format USB drive in context menu
https://bugs.kde.org/show_bug.cgi?id=377253 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374575] "Shortcut for switching to this activity" has no effect
https://bugs.kde.org/show_bug.cgi?id=374575 Nate Graham changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #12 from Nate Graham --- Darn. Can you do as Ivan asked? > If it does not, try the following steps: > > - stop kactivitymanagerd and kglobalaccel5 > - edit the kglobalshortcutsrc and remove the section for activity manager > - restart kactivitymanagerd and kglobalaccel5 > > Set the shortcuts via System Settings -> Shortcuts -> Global Shortcuts -> > Activity Manager > > The issue that remains is that setting the shortcut via the activities kcm > is broken. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 400539] Option to disable unread count
https://bugs.kde.org/show_bug.cgi?id=400539 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 400539] New: Option to disable unread count
https://bugs.kde.org/show_bug.cgi?id=400539 Bug ID: 400539 Summary: Option to disable unread count Product: latte-dock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: benjamindai...@gmail.com Target Milestone: --- Created attachment 116017 --> https://bugs.kde.org/attachment.cgi?id=116017=edit email unread notification Large unread counts with small icons creates an unsightly cutoff. I have a lot of unread emails, and no intentions of changing that so the unread count is pretty useless anyway. It would be nice to be able to turn it off. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400538] New: vex amd64->IR: unhandled instruction bytes: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2 0xCC 0x90 0x55
https://bugs.kde.org/show_bug.cgi?id=400538 Bug ID: 400538 Summary: vex amd64->IR: unhandled instruction bytes: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2 0xCC 0x90 0x55 Product: valgrind Version: 3.14 SVN Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: alexhenri...@gmail.com Target Milestone: --- When I try to use Valgrind to debug any 64-bit Windows program, I get the following error: vex amd64->IR: unhandled instruction bytes: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2 0xCC 0x90 0x55 vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 vex amd64->IR: unhandled instruction bytes: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2 0xCC 0x90 0x55 vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 This is easily reproducible by running `valgrind --trace-children=yes wine notepad`. For what it's worth, I run Arch Linux and all packages are up-to-date. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 381629] add arrow's option to annotation tools
https://bugs.kde.org/show_bug.cgi?id=381629 azzamsa changed: What|Removed |Added CC||oktinast...@gmail.com --- Comment #1 from azzamsa --- Come here for requesting this feature too. Hope it will be implemented soon. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 400537] New: Vertical white bars on desktop after suspend
https://bugs.kde.org/show_bug.cgi?id=400537 Bug ID: 400537 Summary: Vertical white bars on desktop after suspend Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- Created attachment 116016 --> https://bugs.kde.org/attachment.cgi?id=116016=edit bars SUMMARY I see vertical bars on desktop and sometimes on other applications when I suspend to RAM and then wake system up. STEPS TO REPRODUCE 1. Suspend to RAM 2. Wake System OBSERVED RESULT Desktop and windows will have white bars EXPECTED RESULT Clean rendered desktop and windows SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.12.6 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION Linux Kubuntu 18.04 LTS -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 398577] closing a message subwindow crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=398577 Christoph Feck changed: What|Removed |Added CC||paul.nod...@outlook.com --- Comment #4 from Christoph Feck --- *** Bug 36 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 399996] Kmail sometimes crashes when a message window is open
https://bugs.kde.org/show_bug.cgi?id=36 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 398577 *** -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 400536] New: Extract attribute docstrings according to PEP258
https://bugs.kde.org/show_bug.cgi?id=400536 Bug ID: 400536 Summary: Extract attribute docstrings according to PEP258 Product: kdev-python Version: 5.2.4 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: m...@svenbrauch.de Reporter: nicolas.alva...@gmail.com CC: m...@svenbrauch.de Target Milestone: --- Python doesn't "officially" have attribute docstrings, in the sense that nothing will automatically fill the __doc__ of an attribute. However, PEP 258 (https://www.python.org/dev/peps/pep-0258/#attribute-docstrings) defines a convention for external documentation-extracting tools, where a string literal immediately following a simple assignment is interpreted as documentation for the thing being assigned. KDevelop doesn't support this. It seems to extract the string literal *before* an assignment. This is worse than extracting nothing, because if docstrings are written according to the PEP so that docutils extracts them properly, KDevelop's tooltip will show the wrong thing. Here's an example from the PEP. g = 'module attribute (module-global variable)' """This is g's docstring.""" class AClass: c = 'class attribute' """This is AClass.c's docstring.""" In KDevelop, "This is g's docstring" appears in the tooltip for 'c' instead. Another example: class Obj: """Obj's docstring, extracted correctly""" foo=1 """this should be foo's docstring""" bar=2 """this should be bar's docstring""" In this example, "foo" shows no documentation in the tooltip, and "bar" shows the docstring for "foo" instead. -- You are receiving this mail because: You are watching all bug changes.
[kdf] [Bug 400003] Opening KDiskFree freezes and crashes dolphin
https://bugs.kde.org/show_bug.cgi?id=43 --- Comment #4 from Christoph Feck --- The (wrong?) entry in the kdf.desktop does not need a fix? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 310490] kpat crashes when slecting New Game
https://bugs.kde.org/show_bug.cgi?id=310490 --- Comment #7 from Christoph Feck --- You can get a backtrace with 'gdb'. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 334164] building ktorrent from the repository fails: undefined reference to `bt::qHash(bt::SHA1Hash const&)'
https://bugs.kde.org/show_bug.cgi?id=334164 --- Comment #12 from George R. Goffe --- Let's close this one. George... -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 328778] Downloaded files location is updated even if the move fails.
https://bugs.kde.org/show_bug.cgi?id=328778 --- Comment #2 from George R. Goffe --- If the developer doesn't care about this one then why should we? I stopped reporting AND using Ktorrent some time ago. Let's close this one. George... -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 346226] Unexpected condition popup
https://bugs.kde.org/show_bug.cgi?id=346226 --- Comment #2 from George R. Goffe --- Let's close this one. George... -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 328867] Ktorrent (dev) crash at startup
https://bugs.kde.org/show_bug.cgi?id=328867 --- Comment #4 from George R. Goffe --- Let's close this one. George... -- You are receiving this mail because: You are watching all bug changes.
[kpackagekit] [Bug 270321] software system windows ussualy crashed (
https://bugs.kde.org/show_bug.cgi?id=270321 --- Comment #5 from George R. Goffe --- Andrew, Thanks for your help. I would point to this bug as evidence to the wast of time statement. Again, bugs with NO activity for N years should go through an automatic closure process... i.e., contact the user and/or the developer and/or maintainer and give them one more chance to avoid the closure. In any event... Best regards, George... -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 324812] Random Segfault
https://bugs.kde.org/show_bug.cgi?id=324812 --- Comment #11 from Tom Hardy --- I re-enabled weather 6.5 hours ago. No problems so far. I just enabled more features (wind speed and such). Tomorrow I'll go to US customary units. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 400535] New: Plasma-nm applet does not reflect airplane mode properly after I turn on it twice
https://bugs.kde.org/show_bug.cgi?id=400535 Bug ID: 400535 Summary: Plasma-nm applet does not reflect airplane mode properly after I turn on it twice Product: plasma-pa Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 116015 --> https://bugs.kde.org/attachment.cgi?id=116015=edit demonstration SUMMARY My wi-fi connection is stabilished automatically after I start plasma. My settings: hidden network non-encrypted password Watch the screencast please. I click the checkbox to enable the airplaine mode, it works as expected: all wi-fi connections are disabled, wi-fi checkbox is also disabled, wi-fi icon changes to a greyed out icon with a diagonal red line. Now uncheck the airplane mode checkbox: all wi-fi connections are listed again, as expected. Enable airplane mode again. Now wi-fi icon is incorrect, the checkbox to enable the wi-fi adapter is enabled and plasma-nm has no icon in the system tray. Now click the checkbox to enable the wi-fi adapter: plasma-nm applet lists all wi-fi connections active/available and wi-fi icon reappears in the system tray despite both icons and both checkboxes in the header of the applet indicate that the airplane mode is enabled. Operating System: openSUSE Tumbleweed 20181029 KDE Plasma Version: 5.14.80 Qt Version: 5.11.2 KDE Frameworks Version: 5.52.0 Kernel Version: 4.18.15-1-default networkmanager 1.14.0-1.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400397] Plasma 5 Cursor Size reverts to "Resolution Dependent" when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=400397 Kyle Ferriter changed: What|Removed |Added CC||krferri...@protonmail.com --- Comment #1 from Kyle Ferriter --- I would like to add that this also happens for me even when using one 3840x2160 (4K) monitor. Steps to reproduce: 1. Open Cursor Theme settings dialog. 2. Set to 48 3. Click Apply, cursor size is correctly adjusted to 48. 4. Close Cursor Theme dialog. 5. Open Cursor Theme dialog. 6. Size setting in dialog is automatically reverted back to "Resolution Dependent" despite no other user interaction taking place. Actual cursor size is also reverted back to previous size (on my system defaults to 36) despite not clicking "Apply" or "Ok", this happens just by opening the Cursor Theme dialog. Current Plasma version: 5.14.2 but has also been a longstanding issue in previous versions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400534] New: Flash in Firefox in fullscreen mode breaks plasmashell/KWin
https://bugs.kde.org/show_bug.cgi?id=400534 Bug ID: 400534 Summary: Flash in Firefox in fullscreen mode breaks plasmashell/KWin Product: plasmashell Version: 5.14.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: paulo76.alga...@hotmail.com Target Milestone: 1.0 SUMMARY Flash in Firefox in full screen breaks plasmashell/Kwin, every time I put a flash video stream in full screen mode the plasmashell crashes (but no crash report is generated by the system). In order to get things working again I have to close the Firefox tab that has the flash video and run the commands: killall plasmashell && kwin && plasmashell & STEPS TO REPRODUCE 1. In Firefox browser go to a website that has a flash video, in example: https://student.testmasters.com/portal/online/Test.aspx 2. When the video starts, put it in fullscreen mode. 3. Plasmashell/KWin should crash right away OBSERVED RESULT plasmashell/Kwin crashing EXPECTED RESULT plasmashell/Kwin not to crash SOFTWARE VERSIONS System:Host: pemartins-X55U Kernel: 4.15.0-38-generic x86_64 bits: 64 Desktop: KDE Plasma 5.14.2 Distro: KDE neon User Edition 5.14 Machine: Device: laptop System: ASUSTeK product: X55U v: 1.0 serial: N/A Mobo: ASUSTeK model: X55U v: 1.0 serial: N/A UEFI: American Megatrends v: X55U.423 date: 08/06/2013 CPU: Dual core AMD E2-1800 APU with Radeon HD Graphics (-MCP-) cache: 512 KB clock speeds: max: 1700 MHz 1: 871 MHz 2: 872 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Wrestler [Radeon HD 7340] Display Server: x11 (X.Org 1.19.6 ) drivers: ati,radeon (unloaded: modesetting,fbdev,vesa) Resolution: 1366x768@60.01hz OpenGL: renderer: AMD PALM (DRM 2.50.0 / 4.15.0-38-generic, LLVM 6.0.0) version: 3.3 Mesa 18.0.5 Audio: Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller driver: snd_hda_intel Card-2 Advanced Micro Devices [AMD/ATI] Wrestler HDMI Audio driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k4.15.0-38-generic Network: Card-1: Ralink RT5390 Wireless 802.11n 1T/1R PCIe driver: rt2800pci IF: wlp1s0 state: up mac: Card-2: Qualcomm Atheros AR8161 Gigabit Ethernet driver: alx IF: enp2s0 state: down mac: Drives:HDD Total Size: 500.1GB (8.5% used) ID-1: /dev/sda model: ST500LM012_HN size: 500.1GB Partition: ID-1: / size: 97G used: 37G (40%) fs: ext4 dev: /dev/sda5 ID-2: swap-1 size: 3.85GB used: 0.00GB (0%) fs: swap dev: /dev/sda6 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 59.0C mobo: N/A gpu: 59.0 Fan Speeds (in rpm): cpu: 3100 Info: Processes: 164 Uptime: 35 min Memory: 1310.0/3528.9MB Client: Shell (xterm) inxi: 2.3.56 ADDITIONAL INFORMATION I'm using the latest Firefox version Firefox Quantum 63.0 (64-bit). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399778] Special Application/Window Settings not applying
https://bugs.kde.org/show_bug.cgi?id=399778 --- Comment #23 from Vlad Zagorodniy --- (In reply to David Edmundson from comment #22) > config doesn't go out of scope so doesn't implicitly sync. I had the same thought. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 383961] Searches don't show compressed files that Baloo has indexed and can find
https://bugs.kde.org/show_bug.cgi?id=383961 --- Comment #11 from Stefan Brüns --- Yes, works for me. Also try "type:archive" as a search term. Gives a bunch of zip files for me. Another possible check: qdbus-qt5 --session org.kde.krunner /App org.kde.krunner.App.querySingleRunner baloosearch type:archive Archives are "Type::Archive == 1", e.g. have a "T1" term from baloos point of view (as shown with "balooshow -x ..."). Note, I have plasma-workspace 5.14.2 here. -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 323801] Unexpected Policy Kit crash
https://bugs.kde.org/show_bug.cgi?id=323801 Peter C. Trenholme changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #3 from Peter C. Trenholme --- Sorry, I don't have that drive anymore, and it was reported more as a FYI than a bug needing fixing. It's five years old now, and not worth keeping. Changed status to Resolved, Unmaintained. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 383961] Searches don't show compressed files that Baloo has indexed and can find
https://bugs.kde.org/show_bug.cgi?id=383961 --- Comment #10 from Nate Graham --- (In reply to Stefan Brüns from comment #9) > Should be fixed since https://phabricator.kde.org/D10624 (5.12.2, 5.13.0) Than I guess that patch didn't work, since this is still broken for me on 5.12.7 and git master. Does it work for you? Can you find archives with KRunner that baloosearch sees? I can't. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 395192] rust-qt-binding-generator: unable to compile multi-dimensional list
https://bugs.kde.org/show_bug.cgi?id=395192 --- Comment #3 from carl --- Sorry for not giving any sign of live. I read your O.2 announcement and remembered that I posted this bug report a long time ago. I read you answers and I found your solution a bit 'hacky'. Is where at some point something in rust, cpp or qt that could forbid to use multidimensional list. I already saw that the new version don't need #[derive(clone)] anymore and with for example the new `impl trait` syntax in rust. Can't we not implement multidimensional list in this binding generator? I not yet very experimented with the model-view architecture, so maybe I forget something important. I'm looking at your code right now, and I will try to implement something. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 385993] Error in investment interest (Jahresrendite)
https://bugs.kde.org/show_bug.cgi?id=385993
--- Comment #4 from Ralf Habacker ---
Class CashFlowList has a dumpAll() method, which shows
"2005-09-22" "-347257/100"
"2009-03-18" "151284/25"
"1989-11-01" "0/1"
"2017-08-11" "0/1"
Adding this values to an additional QueryTableTest method as:
void QueryTableTest::testCashFlowAnalysis2()
{
CashFlowList list;
list += CashFlowListItem(QDate(2005, 9, 22), MyMoneyMoney(-3472.57));
list += CashFlowListItem(QDate(2009, 3, 18), MyMoneyMoney(6051.36));
list += CashFlowListItem(QDate(1998, 11, 1), MyMoneyMoney(0.0));
list += CashFlowListItem(QDate(2017, 8, 11), MyMoneyMoney(0.0));
MyMoneyMoney IRR(list.IRR(), 1000);
QCOMPARE(IRR.toDouble(), MyMoneyMoney(173, 1000).toDouble());
}
returns:
FAIL! : QueryTableTest::testCashFlowAnalysis2() Compared doubles are not the
same (fuzzy compare)
Actual (IRR.toDouble()): -0.928
Expected (MyMoneyMoney(173, 1000).toDouble()): 0.173
Loc: [/home/ralf/src/kmymoney-4.8/kmymoney/reports/querytabletest.cpp(365)]
Removing the ling
list += CashFlowListItem(QDate(2017, 8, 11), MyMoneyMoney(0.0));
let the test be successful.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 400492] Rotation does not work
https://bugs.kde.org/show_bug.cgi?id=400492 --- Comment #9 from Milan Knížek --- The thing is, the flag for thumbnail does not rotate - it stays as it was originally (from camera) and the thumbnail rotates physically. Try show the exif metadata in the right hand pane, filter for orientation flag and rotate the image. In other words, originally both flags might be "rotated right", but when I rotate the image, then the image flag gets set to 'normal', while the thumbnail flag remains 'rotated right'. In order to get the thumbnail displayed correctly (in Digikam), digiKam must actually physically rotate it, too. The trouble is, that the above behaviour unsyncs the flags and the thumbnail is not shown properly anymore (in Samsung Gallery app). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399778] Special Application/Window Settings not applying
https://bugs.kde.org/show_bug.cgi?id=399778 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #22 from David Edmundson --- Good work, config doesn't go out of scope so doesn't implicitly sync. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 400495] no timeline resize or get a white background
https://bugs.kde.org/show_bug.cgi?id=400495 --- Comment #1 from frank --- settings -> themes -> breeze-dark will fix the problems but i have to do it every time i run kdenlive, it does not remember. this should be changed to minor in importance. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400533] New: Plasma crash when dragging folder on desktop
https://bugs.kde.org/show_bug.cgi?id=400533 Bug ID: 400533 Summary: Plasma crash when dragging folder on desktop Product: plasmashell Version: 5.14.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: j...@ristioja.ee CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.2) (Compiled from sources) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.19.0-gentoo x86_64 Distribution: "Gentoo Base System release 2.4.1" -- Information about the crash: - What I was doing when the application crashed: Started dragging a folder (didn't drop) on the desktop which shows the desktop folder on top of the background picture. - Custom settings of the application: It seems like the desktop is configured as a folder view to show the Desktop folder of the user. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f28f198e800 (LWP 2799))] Thread 5 (Thread 0x7f28a8832700 (LWP 3036)): #0 0x7f28eac03ea0 in __GI___libc_read (fd=27, buf=buf@entry=0x7f28a8831b20, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f28e4ed85c0 in read (__nbytes=16, __buf=0x7f28a8831b20, __fd=) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7f28b4003d80) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gwakeup.c:210 #3 0x7f28e4e8927b in g_main_context_check (context=context@entry=0x7f28a4000bf0, max_priority=2147483647, fds=fds@entry=0x7f28a4006450, n_fds=n_fds@entry=1) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3750 #4 0x7f28e4e89740 in g_main_context_iterate (context=context@entry=0x7f28a4000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3969 #5 0x7f28e4e898dc in g_main_context_iteration (context=0x7f28a4000bf0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4033 #6 0x7f28eb5cdc5b in QEventDispatcherGlib::processEvents (this=0x7f28a4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x7f28eb5662bb in QEventLoop::exec (this=this@entry=0x7f28a8831d60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #8 0x7f28eb38579a in QThread::exec (this=this@entry=0x56527e3d0360) at thread/qthread.cpp:525 #9 0x7f28a9cbfbf7 in KCupsConnection::run (this=0x56527e3d0360) at /var/tmp/portage/kde-apps/print-manager-18.08.2/work/print-manager-18.08.2/libkcups/KCupsConnection.cpp:304 #10 0x7f28eb393896 in QThreadPrivate::start (arg=0x56527e3d0360) at thread/qthread_unix.cpp:367 #11 0x7f28e7df49aa in start_thread (arg=0x7f28a8832700) at pthread_create.c:463 #12 0x7f28eac142ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f28c7fff700 (LWP 2970)): #0 0x7f28e7dfb55c in futex_wait_cancelable (private=, expected=0, futex_word=0x56527b518d44) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56527b518cf0, cond=0x56527b518d18) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56527b518d18, mutex=0x56527b518cf0) at pthread_cond_wait.c:655 #3 0x7f28d088398b in cnd_wait (mtx=0x56527b518cf0, cond=0x56527b518d18) at /var/tmp/portage/media-libs/mesa-18.1.9/work/mesa-18.1.9/include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x56527b3bafa0) at /var/tmp/portage/media-libs/mesa-18.1.9/work/mesa-18.1.9/src/util/u_queue.c:255 #5 0x7f28d0883617 in impl_thrd_routine (p=) at /var/tmp/portage/media-libs/mesa-18.1.9/work/mesa-18.1.9/include/c11/threads_posix.h:87 #6 0x7f28e7df49aa in start_thread (arg=0x7f28c7fff700) at pthread_create.c:463 #7 0x7f28eac142ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f28d37c9700 (LWP 2880)): #0 __libc_disable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:96 #1 0x7f28eac087d7 in __GI___poll (fds=, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #2 0x7f28e4e89799 in g_main_context_poll (priority=, n_fds=1, fds=0x7f28c8004a00, timeout=, context=0x7f28c8000bf0) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4271 #3 g_main_context_iterate (context=context@entry=0x7f28c8000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3967 #4 0x7f28e4e898dc in g_main_context_iteration (context=0x7f28c8000bf0, may_block=may_block@entry=1) at
[klinkstatus] [Bug 352062] Konqueror crashed in KLinkStatusPart view
https://bugs.kde.org/show_bug.cgi?id=352062 andrew brewster changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from andrew brewster --- Sorry, I'm unwilling to do that. KLinkStatus is a KDE4 component I think, and since I reported it, I'veupdgraded to Mageia 6 where its at v16.12.3, with dependencies on the whole KDE ecosystem at that same version. The software installer is telling me that to install it I will have to uninstall all of KDE at v17.12.2, which is a deal breaker for me. Its part of kdewebdev, but it doesn't seems to have been ported to KF5, as there's no docs for it at https://docs.kde.org/stable/en/kdewebdev/klinkstatus/index.html If KLinkStatus ever gets ported to KF5 I would certainly try it out. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 400532] New: Copy to clipboard on host terminates session
https://bugs.kde.org/show_bug.cgi?id=400532 Bug ID: 400532 Summary: Copy to clipboard on host terminates session Product: krdc Version: 18.08 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: RDP Assignee: uwol...@kde.org Reporter: k...@mockies.de Target Milestone: --- Copying text to clipboard (Ctrl+c or Ctrl+x) on the host will terminate the active RDP session. The text is not actually placed into the clipboard (which could lead to data loss in case Ctrl+x was used and the text field does not support "undo"). Copying text on the client into clipbaord is available on the host as expected. Clipboard text copied before the session gets opened will be available in a newly opened session. STEPS TO REPRODUCE 1. open a RDP session (to Windows 7 in my case) 2. copy text to clipbaord on the host OBSERVED RESULT The RDP session gets terminated. Text is not copied to clipboard at all. EXPECTED RESULT Text should be available in the clipboard of the host as well as in the client session. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION I'm using Plasma clipboard applet, after copying text and the remote session terminates the applet will show an empty entry. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 400531] New: Latte only shows an error and does not start properly
https://bugs.kde.org/show_bug.cgi?id=400531 Bug ID: 400531 Summary: Latte only shows an error and does not start properly Product: latte-dock Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: timesarehard4dream...@gmail.com Target Milestone: --- Created attachment 116014 --> https://bugs.kde.org/attachment.cgi?id=116014=edit screenshot SUMMARY STEPS TO REPRODUCE 1. Run latte dock OBSERVED RESULT a blank panel appears with this error along it: Error loading QML file: file:///usr/share/plasma/plasmoids/org.kde.latte.containment/contents/ui/main.qml:1830:26: ColorizerManager is not a type EXPECTED RESULT it should run... SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 400530] New: Cursor theme of Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=400530 Bug ID: 400530 Summary: Cursor theme of Breeze Dark Product: Breeze Version: unspecified Platform: Other OS: All Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gusta...@gmail.com Target Milestone: --- SUMMARY Shouldn't the dark variant of Breeze use the Breeze Snow cursor theme by default? It's easier to find due the contrast difference, while with defaults happens the opposite. STEPS TO REPRODUCE 1. Use the default "Breeze Dark" Look and Feel OBSERVED RESULT The cursor is dark, similar to the other components EXPECTED RESULT The cursor should be differentiated from the other components using a higher contrast. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390411] Sqlite opening broken
https://bugs.kde.org/show_bug.cgi?id=390411 --- Comment #16 from Thomas Baumgart --- What is the exact version number of 'Kmymoney from Neon repo' you mention in comment 14? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400529] New: Ship multiple CSS files for markdown backend
https://bugs.kde.org/show_bug.cgi?id=400529 Bug ID: 400529 Summary: Ship multiple CSS files for markdown backend Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kleinmeier.bened...@gmail.com Target Milestone: --- It would be nice if the Markdown backend would ship multiple CSS files so that the user can change the style how the Markdown code is rendered. The style should be changed via "Settings -> Configure Backends -> Markdown". A lot of Markdown editors (e.g. Haroopad) already ship different CSS styles (e.g. "Solarized Light/Dark" and so on). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399778] Special Application/Window Settings not applying
https://bugs.kde.org/show_bug.cgi?id=399778 --- Comment #21 from Vlad Zagorodniy --- After bisecting it looks like a02797ca0608a302f466897d5bb5cd5cf4b9d13f introduced this bug. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 353900] Marble crashed while setting route points
https://bugs.kde.org/show_bug.cgi?id=353900 Germano Massullo changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Germano Massullo --- Sorry, I don't have a kmz available for the test. Feel free to close the bugreport -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 340248] K3b when copying DVDs on-the-fly hangs
https://bugs.kde.org/show_bug.cgi?id=340248 Felix Miata changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Felix Miata --- K3B 18.08.2 (openSUSE TW 20181029; dvd+rw-tools-7.1-61.6; cdrdao-1.2.3-15.3; cdrecord-3.02~a10-5.1) worked as expected using DVD+R media source on PATA and DVD+R media on SATA target. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #21 from Sergey ---
xrandr shell script seems to work good.
Bug I just rewrote it based on this
https://askubuntu.com/questions/183516/how-do-i-detect-when-my-system-wakes-up-from-suspend-via-dbus-or-similar-in-a-py
def handle_sleep_callback(sleeping):
if not sleeping:
os.system("sleep 5; xrandr --output LVDS-1 --primary --auto --left-of
HDMI-2")
If I notice any issues I'll report back.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 377181] Support for termcap/terminfo te@/ti@ sequences.
https://bugs.kde.org/show_bug.cgi?id=377181 Marcos Dione changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |INTENTIONAL --- Comment #6 from Marcos Dione --- > On a side note, turning these off is a broken idea by design. Sure it's more > convenient to be able to scroll back using the emulator's scrollbar, but the > moment you start using screen's features like detaching and re-attaching, it > no longer carries the scrollback contents. Or if you switch between multiple > windows inside screen, they'll have a common scrollback. This is how I got used to work with screen, using the emulator's scrollback was enough for me in many situations (and you can alwas resort to call screen's copy mode and use it's scrollback). I'll try those tips you mention, for the moment, yes, by all means, elt's close this bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400511] Crash when trying to highlight/underline a text
https://bugs.kde.org/show_bug.cgi?id=400511 Albert Astals Cid changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Albert Astals Cid --- https://cgit.freedesktop.org/poppler/poppler/commit/?id=aeb2c1798ef39b5d3a167f4531e9f09dcb18e88d -- You are receiving this mail because: You are watching all bug changes.
[kdf] [Bug 400003] Opening KDiskFree freezes and crashes dolphin
https://bugs.kde.org/show_bug.cgi?id=43 mthw0 changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 400528] New: Context browser does not show function name until opened for the first time
https://bugs.kde.org/show_bug.cgi?id=400528 Bug ID: 400528 Summary: Context browser does not show function name until opened for the first time Product: kdevelop Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: k...@opensource.sf-tec.de Target Milestone: --- The context browser does not show the current function name when navigating through the code by clicking or scrolling. Once I click into the edit field so the function list shows up everything works fine. One does not have to jump to a function, just click into the field and back into the code window. This is no (recent) regression, I see the same behavior also with 5.2.4. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400492] Rotation does not work
https://bugs.kde.org/show_bug.cgi?id=400492 --- Comment #8 from Maik Qualmann --- In your case, so it works with the Samsung Gallery app, I would only rotate the indicator. Maik -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400527] New: Flatpak backend shows incorrect size of updates
https://bugs.kde.org/show_bug.cgi?id=400527 Bug ID: 400527 Summary: Flatpak backend shows incorrect size of updates Product: Discover Version: 5.14.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: aleix...@kde.org Reporter: nibg...@gmail.com CC: jgrul...@redhat.com Target Milestone: --- Created attachment 116013 --> https://bugs.kde.org/attachment.cgi?id=116013=edit Size of updates: Discover v/s "$ flatpak update" SUMMARY Flatpak backend of Discover does not differentiate between the installation size and the update size of the Flatpak packages (installation size always shown). For example, in the attached image, the "io.atom.Atom" package update is 35.3MB, but Discover shows that the update is 133.3MB. This is most noticeable in the Flatpak Runtime updates, where Discover shows updates of more than 700MB, when sometimes the download does not exceed 30MB. This may be a problem for users who have an Internet connection with a traffic limit (mobile connections), since some users may refrain from updating their system when they see the big size of the updates in Discover, in Flatpak packages. STEPS TO REPRODUCE When there is an update of some Flatpak package, run "$ flatpak update" and compare the size of the update with the one that shows Discover. OBSERVED RESULT In the updates, Discover shows the installation size of the Flatpak packages, not the update size. The user is informed of an incorrect update download size (much bigger than the real one) EXPECTED RESULT Discover shows the real size to download in Flatpak package updates. SOFTWARE VERSIONS Discover: 5.14.2 KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 Operating System: KDE Neon 5.14, Ubuntu 18.04 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400492] Rotation does not work
https://bugs.kde.org/show_bug.cgi?id=400492 --- Comment #7 from Maik Qualmann --- I do not see a mistake here. Only very few cameras have Exif.Thumbnail.Orientation, yes Samsumg is one. If you only rotate the indicator, digiKam also updates Exif.Thumbnail.Orientation. If you rotate the image lossless, only the main image is rotated, the preview image is not. I do not know if LibJpeg can also rotate the embedded preview image lossless, I do not think so. This is of course different with the image editor, as it always generates new image data and also generates a new preview image. Maik -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 351705] KRDC crashed when remote Mac closed connection
https://bugs.kde.org/show_bug.cgi?id=351705 mike0...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 398577] closing a message subwindow crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=398577 Andrew Crouthamel changed: What|Removed |Added Ever confirmed|0 |1 CC||andrew.crouthamel@kdemail.n ||et Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 344302] kmix close on startup
https://bugs.kde.org/show_bug.cgi?id=344302 Andrew Crouthamel changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME CC||andrew.crouthamel@kdemail.n ||et Status|NEEDSINFO |RESOLVED --- Comment #3 from Andrew Crouthamel --- Thanks for the update! -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 324995] Generating video previews crashes "kioslave.EXE"
https://bugs.kde.org/show_bug.cgi?id=324995 Andrew Crouthamel changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME CC||andrew.crouthamel@kdemail.n ||et Status|NEEDSINFO |RESOLVED --- Comment #3 from Andrew Crouthamel --- Thanks for the update! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 377414] Bookmark should also store tab name
https://bugs.kde.org/show_bug.cgi?id=377414 --- Comment #2 from Ovidiu-Florin BOGDAN --- You are right. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359214] Wallpaper on second monitor overlaps first monitor and does not rotate
https://bugs.kde.org/show_bug.cgi?id=359214 Ovidiu-Florin BOGDAN changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #6 from Ovidiu-Florin BOGDAN --- Sorry for the late reply, I didn't get an email until now about this bug. I cannot reproduce this anymore. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400492] Rotation does not work
https://bugs.kde.org/show_bug.cgi?id=400492 --- Comment #6 from Milan Knížek --- One app is confused with out of sync orientation flag - the default Gallery app in Samsung S7. It displays the embedded thumbnail as per Exif.Image.Orientation and ignores Exif.Thumbnail.Orientation. It is probably Samsung's bug, but anyway, wouldn't it be safer to have the image and embedded thumbnail orientation in sync? -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 324995] Generating video previews crashes "kioslave.EXE"
https://bugs.kde.org/show_bug.cgi?id=324995 Julian Groß changed: What|Removed |Added Version|4.10|unspecified --- Comment #2 from Julian Groß --- (In reply to Andrew Crouthamel from comment #1) > Dear Bug Submitter, > > This bug has been stagnant for a long time. Could you help us out and > re-test if the bug is valid in the latest version? I am setting the status > to NEEDSINFO pending your response, please change the Status back to > REPORTED when you respond. > > Thank you for helping us make KDE software even better for everyone! I cannot find a fitting installer anymore, and I don't really have the time to get into the project and figure out how to compile konqueror and the videopreview stuff. Nice to see that someone is taking care of the bugtracker though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400526] New: device notifier pretends it cannot mount usb device while actually mounting it
https://bugs.kde.org/show_bug.cgi?id=400526 Bug ID: 400526 Summary: device notifier pretends it cannot mount usb device while actually mounting it Product: plasmashell Version: 5.12.6 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Device Notifier Assignee: plasma-b...@kde.org Reporter: dorpmuel...@hotmail.com Target Milestone: 1.0 I am wondering that https://bugs.kde.org/show_bug.cgi?id=370975 is not going into a bugfix for the current Kubuntu Bionic LTS. The patch is available and it should be easy to apply or backport it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it
https://bugs.kde.org/show_bug.cgi?id=370975 dorpm changed: What|Removed |Added CC||dorpmuel...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 400293] REGRESSION: NFS root folder not writable with 18.08.2 because NFS ioslave claims root item isn't writable
https://bugs.kde.org/show_bug.cgi?id=400293 Nate Graham changed: What|Removed |Added Keywords||regression Summary|NFS root folder not |REGRESSION: NFS root folder |writable with 18.08.2 - |not writable with 18.08.2 |works with 18.08.1 |because NFS ioslave claims ||root item isn't writable -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 330066] Konsole crashed while double clicking when columns > 1024
https://bugs.kde.org/show_bug.cgi?id=330066 --- Comment #10 from Kurt Hindenburg --- OK that was duh! moment on my part. Konsole does have issues w/ this many columns. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 400293] NFS root folder not writable with 18.08.2 - works with 18.08.1
https://bugs.kde.org/show_bug.cgi?id=400293 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org --- Comment #2 from Nate Graham --- Yep, that makes perfect sense, Elvis. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400525] New: Plasma Crashes while WiFi is obtaining IP address
https://bugs.kde.org/show_bug.cgi?id=400525 Bug ID: 400525 Summary: Plasma Crashes while WiFi is obtaining IP address Product: plasmashell Version: 5.12.6 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: david_...@live.co.uk CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.6) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.22-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: I'd just logged in after switching from anXFCE seesion to KDE(Wayland), and Plasma crashed while WiFi was logging on. After the crash, Plasma restarted OK and WiFi connected successfully. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f95d9c671c0 (LWP 23617))] Thread 12 (Thread 0x7f94f7feb700 (LWP 23802)): #0 0x7f95d28d6c4d in __lll_lock_wait () from /lib64/libpthread.so.0 #1 0x7f95d28cff13 in pthread_mutex_lock () from /lib64/libpthread.so.0 #2 0x7f95b8ec4de5 in eglSwapInterval () from /usr/lib64/libEGL_mesa.so.0 #3 0x7f95b97b5dae in ?? () from /usr/lib64/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #4 0x7f95d3ef59c2 in QOpenGLContext::swapBuffers(QSurface*) () from /usr/lib64/libQt5Gui.so.5 #5 0x7f95d748dab0 in ?? () from /usr/lib64/libQt5Quick.so.5 #6 0x7f95d7492788 in ?? () from /usr/lib64/libQt5Quick.so.5 #7 0x7f95d371f0ce in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f95d28cd559 in start_thread () from /lib64/libpthread.so.0 #9 0x7f95d301e81f in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7f94d7fff700 (LWP 23800)): #0 0x7f95d28d389d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f95d37203eb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f95d7492398 in ?? () from /usr/lib64/libQt5Quick.so.5 #3 0x7f95d74927ca in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7f95d371f0ce in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f95d28cd559 in start_thread () from /lib64/libpthread.so.0 #6 0x7f95d301e81f in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7f94d77fe700 (LWP 23770)): #0 0x7f95d28d389d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f95d37203eb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f95d7492398 in ?? () from /usr/lib64/libQt5Quick.so.5 #3 0x7f95d74927ca in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7f95d371f0ce in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f95d28cd559 in start_thread () from /lib64/libpthread.so.0 #6 0x7f95d301e81f in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f9509880700 (LWP 23742)): #0 0x7f95d301407b in poll () from /lib64/libc.so.6 #1 0x7f95d1f13b29 in ?? () from /usr/lib64/libwayland-client.so.0 #2 0x7f95d1f1516c in wl_display_dispatch_queue () from /usr/lib64/libwayland-client.so.0 #3 0x7f95b8ed2d73 in ?? () from /usr/lib64/libEGL_mesa.so.0 #4 0x7f95b8ec4d3e in eglSwapBuffers () from /usr/lib64/libEGL_mesa.so.0 #5 0x7f95b97b5dbc in ?? () from /usr/lib64/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #6 0x7f95d3ef59c2 in QOpenGLContext::swapBuffers(QSurface*) () from /usr/lib64/libQt5Gui.so.5 #7 0x7f95d748dab0 in ?? () from /usr/lib64/libQt5Quick.so.5 #8 0x7f95d7492788 in ?? () from /usr/lib64/libQt5Quick.so.5 #9 0x7f95d371f0ce in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7f95d28cd559 in start_thread () from /lib64/libpthread.so.0 #11 0x7f95d301e81f in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f95109cf700 (LWP 23709)): #0 0x7f95d300fb68 in read () from /lib64/libc.so.6 #1 0x7f95cd948420 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f95cd903bf7 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f95cd9040b0 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f95cd90421c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f95d3942c0b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f95d38eb09a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f95d371a4da in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f951329bf67 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #9 0x7f95d371f0ce in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7f95d28cd559 in start_thread () from /lib64/libpthread.so.0 #11 0x7f95d301e81f
[Breeze] [Bug 396091] Scrollbar appearance inconsistent in between Breeze themes
https://bugs.kde.org/show_bug.cgi?id=396091 Nate Graham changed: What|Removed |Added Version Fixed In||5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 396091] Scrollbar appearance inconsistent in between Breeze themes
https://bugs.kde.org/show_bug.cgi?id=396091 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/bre ||eze-gtk/6ec73bf0693821ffda1 ||ea262e8b7c162242dc495 Status|CONFIRMED |RESOLVED --- Comment #5 from Nate Graham --- Git commit 6ec73bf0693821ffda1ea262e8b7c162242dc495 by Nate Graham, on behalf of Matthias Groß. Committed on 31/10/2018 at 18:39. Pushed by ngraham into branch 'master'. share common values for both Breeze and Breeze-dark GTK themes Summary: As described in bug #396091, the Breeze-dark theme is often neglected in updates. This patch fixes #396091 and some additional, related inconsistencies, enables sharing the basic stuff like shape, size, style, etc. of components in a common single css file while keeping the colour definitions separated from that in different files for both the light and dark theme. This allows easier changes, easier maintenance because of less LOC, less duplicate code as well as easier extensibility for potential additional colour schemes like [[ https://hig.kde.org/style/color/light.html | light ]] or [[ https://hig.kde.org/style/color/high.html | high-contrast ]]. I only did this for GTK 3.20 for now. If you like the effort, it could (and maybe should) get extended to other versions. Further potential steps in the same direction of saving code would be going back to SASS, which is used by many other popular GTK themes and was used by Breeze-gtk as well in the past. The only downside of that is that the SASS source files would have to be "compiled" to CSS prior to packaging. Test Plan: I don't know of any automated test suites comparing UI components. I have already posted screenshots in the original bug report and can post additional ones of the new state for comparison. Apart from that, my manual sparse testing makes me feel the dark GTK theme looks and feels much more consistent to Breeze now. Reviewers: jackg, #breeze, #plasma, ngraham Reviewed By: #breeze, ngraham Subscribers: grmat, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D16365 M +60 -3707 Breeze-dark-gtk/gtk-3.20/gtk.css C +0-122 Breeze-gtk/gtk-3.20/common.css [from: Breeze-gtk/gtk-3.20/gtk.css - 097% similarity] M +1-3692 Breeze-gtk/gtk-3.20/gtk.css https://commits.kde.org/breeze-gtk/6ec73bf0693821ffda1ea262e8b7c162242dc495 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 400522] Menu editor crashes when changing icon source for submenu
https://bugs.kde.org/show_bug.cgi?id=400522 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 398766 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 398766] Desktop crash while changing application launchers icon.
https://bugs.kde.org/show_bug.cgi?id=398766 Patrick Silva changed: What|Removed |Added CC||m...@emilharder.dk --- Comment #24 from Patrick Silva --- *** Bug 400522 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400492] Rotation does not work
https://bugs.kde.org/show_bug.cgi?id=400492 --- Comment #5 from Milan Knížek --- This one works again. However, I am still wondering if it is a problem that even after rotation (which sets the Orientation Flag to "Normal"), the flag for thumbnail is still reported as "rotated" (even after rebuilding the thumbnails): $ exiv2 -pa z2.jpg | grep -a rientat Exif.Image.Orientation Short 1 top, left Exif.Thumbnail.Orientation Short 1 right, top Xmp.tiff.Orientation XmpText 1 top, left It does not seem to cause problem in digiKam Preview view, in EOG, in Geeqie - all show the thumbnail properly. The Exif.Thumbnail.Orientation flag is removed when the image is edited in digiKam's editor and saved. Shouldn't it be either synced with the image orientation or removed also within Rotation actions in digiKam? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372441] Konsole Desktop file missing StartupWMClass
https://bugs.kde.org/show_bug.cgi?id=372441 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400524] New: Baloo crashed for no reason
https://bugs.kde.org/show_bug.cgi?id=400524 Bug ID: 400524 Summary: Baloo crashed for no reason Product: frameworks-baloo Version: 5.45.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: reinhardau...@gmx.at Target Milestone: --- Application: baloo_file (5.45.0) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.22-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: I had open Google Chrome (facebook) and amarok, nothing else. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f09f1b5c100 (LWP 2148))] Thread 3 (Thread 0x7f09e65ea700 (LWP 18208)): [KCrash Handler] #6 0x7f09ef58b130 in __memcpy_ssse3 () from /lib64/libc.so.6 #7 0x7f09f0b4da93 in memcpy (__len=2067, __src=, __dest=) at /usr/include/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7f09e65e98f7, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42 #9 0x7f09f0b3ef64 in Baloo::PostingDB::get (this=this@entry=0x7f09e65e99e0, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100 #10 0x7f09f0b4b180 in Baloo::WriteTransaction::commit (this=0x7ec9d8004dd0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259 #11 0x7f09f0b444c2 in Baloo::Transaction::commit (this=this@entry=0x7f09e65e9af0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262 #12 0x55a357502577 in Baloo::ModifiedFileIndexer::run (this=0x55a358ddbd60) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/modifiedfileindexer.cpp:103 #13 0x7f09effa6372 in QThreadPoolThread::run (this=0x55a358dc68a0) at thread/qthreadpool.cpp:99 #14 0x7f09effa90ce in QThreadPrivate::start (arg=0x55a358dc68a0) at thread/qthread_unix.cpp:368 #15 0x7f09ee592559 in start_thread () from /lib64/libpthread.so.0 #16 0x7f09ef54b81f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f09e7132700 (LWP 2206)): #0 0x7f09ef53cb68 in read () from /lib64/libc.so.6 #1 0x7f09ebc2d420 in read (__nbytes=16, __buf=0x7f09e7131aa0, __fd=) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x55a358d5e1c0) at gwakeup.c:210 #3 0x7f09ebbe8bf7 in g_main_context_check (context=context@entry=0x7f09ebe0, max_priority=2147483647, fds=fds@entry=0x7f09e0002de0, n_fds=n_fds@entry=3) at gmain.c:3646 #4 0x7f09ebbe90b0 in g_main_context_iterate (context=context@entry=0x7f09ebe0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3865 #5 0x7f09ebbe921c in g_main_context_iteration (context=0x7f09ebe0, may_block=may_block@entry=1) at gmain.c:3929 #6 0x7f09f01ccbef in QEventDispatcherGlib::processEvents (this=0x7f09eb10, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #7 0x7f09f017509a in QEventLoop::exec (this=this@entry=0x7f09e7131ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #8 0x7f09effa44da in QThread::exec (this=this@entry=0x7f09f1671d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:515 #9 0x7f09f1401985 in QDBusConnectionManager::run (this=0x7f09f1671d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #10 0x7f09effa90ce in QThreadPrivate::start (arg=0x7f09f1671d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #11 0x7f09ee592559 in start_thread () from /lib64/libpthread.so.0 #12 0x7f09ef54b81f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f09f1b5c100 (LWP 2148)): #0 0x7f09ef54107b in poll () from /lib64/libc.so.6 #1 0x7f09ebbe9109 in g_main_context_poll (priority=, n_fds=1, fds=0x55a358d6b160, timeout=, context=0x55a358d5e260) at gmain.c:4169 #2 g_main_context_iterate (context=context@entry=0x55a358d5e260, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3863 #3 0x7f09ebbe921c in g_main_context_iteration (context=0x55a358d5e260, may_block=may_block@entry=1) at gmain.c:3929 #4 0x7f09f01ccc0b in QEventDispatcherGlib::processEvents (this=0x55a358d5d8d0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f09f017509a in QEventLoop::exec (this=this@entry=0x7ffd4f3e2060, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f09f017d9e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1289 #7 0x55a3574f821c in main (argc=, argv=) at
[frameworks-baloo] [Bug 390975] KRunner crashes when typing "4." (without quotes)
https://bugs.kde.org/show_bug.cgi?id=390975 Stefan Brüns changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Stefan Brüns --- File search (baloo) is run out-of-process (krunner) now. Several bugs in baloo have been fixed. In case the issue persists, please reopen. When reopening, please run the offending query with baloosearch, e.g. "baloosearch 4.". -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 Shawn Sörbom changed: What|Removed |Added CC||sh...@sorbom.com --- Comment #8 from Shawn Sörbom --- Same issue on KDE Neon 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400248] kwin vanishes from shortcut config when changing number of workspaces
https://bugs.kde.org/show_bug.cgi?id=400248 --- Comment #7 from Martin Flöser --- (In reply to David Edmundson from comment #6) > There's a rule about new strings in backports. > > This has a new i18n'd string "KWin". > I probably could ask for an exception, but the bug seemed quite minor. We could backport without i18n: KWin is hardly a translatable string. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case
https://bugs.kde.org/show_bug.cgi?id=222878 Till Schäfer changed: What|Removed |Added Version|5.4.0 |5.9.2 --- Comment #39 from Till Schäfer --- still valid on 5.9.2 with frameworks 5.51.0 and qt 5.11.2 in the meanwhile for everybody frustrated to type killall kontact every few hours: here is a script to detect and kill hanging kmail instances. I have just added it to my kontact.desktop file, such that kontact just starts and does not wait for the hanging instance. #!/bin/bash pid=$(pidof kontact) if [[ $pid != "" ]]; then echo "Running KMail instance found: $pid" windowsofpid=$(xdotool search --pid $pid) if [[ $windowsofpid == "" ]]; then echo "Hanging KMail instance found. Killing..." kdialog --passivepopup "Hanging KMail instance found: $pid. Killing ..." 5 --title "Kill Hanging Kontact Script" kill $pid fi fi -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 330066] Konsole crashed while double clicking when columns > 1024
https://bugs.kde.org/show_bug.cgi?id=330066 --- Comment #9 from Alexander Potashev --- You just 1. drag the window to a side of the screen and 2. then resize it by dragging the edge 3. repeat -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 352710] baloo stops indexing after few file
https://bugs.kde.org/show_bug.cgi?id=352710 Stefan Brüns changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||stefan.bruens@rwth-aachen.d ||e --- Comment #14 from Stefan Brüns --- Lack of progress is likely due to a crashed indexer process. Should be fixed with https://phabricator.kde.org/D16266 Content indexing can be disabled in System-Settings or using "balooctl config" -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 344302] kmix close on startup
https://bugs.kde.org/show_bug.cgi?id=344302 --- Comment #2 from Kuba --- (In reply to Andrew Crouthamel from comment #1) > Dear Bug Submitter, > > This bug has been stagnant for a long time. Could you help us out and > re-test if the bug is valid in the latest version? I am setting the status > to NEEDSINFO pending your response, please change the Status back to > REPORTED when you respond. > > Thank you for helping us make KDE software even better for everyone! Dear Andrew, I'm sorry it was so long ago that I can't even remember details. Currenty, I run latest stable revision and problem doesn't occur. I think you can close the case. BR, Kuba -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 367646] Ballo file extractor 100%CPU for hours then crashes
https://bugs.kde.org/show_bug.cgi?id=367646 Stefan Brüns changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||stefan.bruens@rwth-aachen.d ||e Resolution|--- |BACKTRACE --- Comment #1 from Stefan Brüns --- The backtrace is incomplete, information is insufficent to take any action. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400508] Search bar -- filter the list of packages to update instead of highlighting matches
https://bugs.kde.org/show_bug.cgi?id=400508 --- Comment #2 from Jonathan Verner --- > This was done because if we're filtering then it's unclear what will happen > when you press update. Do we only update what's being seen? or everything? Oh, I see... :-) I agree that would be confusing > I agree it feels weird, but I'd prefer to drop the search altogether in this > view. Hmm, I still think a way to search the list would be useful (e.g. when there is a long list of updates and I am interested if a particular app with a vulnerability is being updated). Anyway, I am not sure how it would work UI-wise. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 358548] baloo_file_extractor high CPU and memory usage
https://bugs.kde.org/show_bug.cgi?id=358548 Stefan Brüns changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #13 from Stefan Brüns --- Infinnite loops are fixed with https://phabricator.kde.org/D12335 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 377715] Krunner consumes a lot of CPU since I start typing
https://bugs.kde.org/show_bug.cgi?id=377715 Stefan Brüns changed: What|Removed |Added CC||stefan.bruens@rwth-aachen.d ||e Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Stefan Brüns --- File search is run out-of-process since https://phabricator.kde.org/D7404 If krunner is still consuming 100% CPU, this is no filesearch issue. If the baloorunner helper is consuming 100% CPU, it is as filesearch/baloo issue. In this case, please reopen and move to component frameworks-baloo. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 330066] Konsole crashed while double clicking when columns > 1024
https://bugs.kde.org/show_bug.cgi?id=330066 Kurt Hindenburg changed: What|Removed |Added Summary|Konsole crashed while |Konsole crashed while |double clicking on a|double clicking when |colored git hash in tig.|columns > 1024 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 330066] Konsole crashed while double clicking on a colored git hash in tig.
https://bugs.kde.org/show_bug.cgi?id=330066 --- Comment #8 from Kurt Hindenburg --- Thanks for the info; the most I can get on my system is around 600 columns. Comment #3 does make sense; though not sure how to test it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400509] Duplicate header
https://bugs.kde.org/show_bug.cgi?id=400509 --- Comment #2 from Jonathan Verner --- Created attachment 116012 --> https://bugs.kde.org/attachment.cgi?id=116012=edit Screenshot showing the duplication -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 373236] baloo_file_extractor eats up a whole thread (25% CPU) on login
https://bugs.kde.org/show_bug.cgi?id=373236 Stefan Brüns changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||stefan.bruens@rwth-aachen.d ||e Resolution|--- |WAITINGFORINFO --- Comment #2 from Stefan Brüns --- This bug report is too unspecific to take any action. In case the issue persists and you can provide more information, please reopen. Required information: - Are both baloo_file and baloo_file_extractor alive? - Whats the last file baloo_file_extractor was processing? - output of "balooctl monitor", output of "cat /proc//fd" -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 259164] After completing burn of a Video DVD Project; Clear Project will cause k3b to hang - 100% cpu
https://bugs.kde.org/show_bug.cgi?id=259164 --- Comment #6 from Ken Taylor --- I booted the computer from the Kubuntu 18.04 image in preparation to install. It occurred to me that K3b was probably already in the image. I selected "Try Kubuntu" and ran K3b 17.12.3 from the live image. I ran the same steps described in the Ubuntu Mate test. Upon clearing the Video DVD project I found that K3b had become unresponsive and top showed K3b utilizing 100% CPU. I can install and test further if that would help. However, it seems the underlying issue is present on the live image. Please let me know if I can do anything more to assist. Ken -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 343645] Treat archive files (.zip, .rar, ...) full of images in the same way as CBR and CBZ files
https://bugs.kde.org/show_bug.cgi?id=343645 Sabarish changed: What|Removed |Added CC||sabarishsbr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kplayer] [Bug 350005] KPlayer startup crash
https://bugs.kde.org/show_bug.cgi?id=350005 Andrew Crouthamel changed: What|Removed |Added CC||andrew.crouthamel@kdemail.n ||et Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Andrew Crouthamel --- Thanks for the update! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 343346] kbuildsycoca5 crash in VFolderMenu::excludeItems() with custom applications.menu file
https://bugs.kde.org/show_bug.cgi?id=343346 Andrew Crouthamel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||andrew.crouthamel@kdemail.n ||et Resolution|--- |WORKSFORME --- Comment #6 from Andrew Crouthamel --- Thanks for the update! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 370963] baloo_file_extractor stalls searching while still consuming 100% CPU
https://bugs.kde.org/show_bug.cgi?id=370963 Stefan Brüns changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||stefan.bruens@rwth-aachen.d ||e --- Comment #1 from Stefan Brüns --- Running baloo_file_extractor on its own is pointless as it receives the list of files via pipe from its parent process. Lack of progress hints at a crashed indexer process, which has been fixed: https://phabricator.kde.org/D16266 -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 327855] KDE Deamon crashes during wake up in a VirtualBox guest
https://bugs.kde.org/show_bug.cgi?id=327855 Andrew Crouthamel changed: What|Removed |Added Resolution|--- |WORKSFORME CC||andrew.crouthamel@kdemail.n ||et Status|REPORTED|RESOLVED --- Comment #5 from Andrew Crouthamel --- Thanks for the update! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 341785] Application: K3b
https://bugs.kde.org/show_bug.cgi?id=341785 Andrew Crouthamel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||andrew.crouthamel@kdemail.n ||et Resolution|--- |WORKSFORME --- Comment #3 from Andrew Crouthamel --- Thanks for the update! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 334377] KDevelop crashes when project folder gets renamed on disk.
https://bugs.kde.org/show_bug.cgi?id=334377 Andrew Crouthamel changed: What|Removed |Added Resolution|--- |WORKSFORME CC||andrew.crouthamel@kdemail.n ||et Status|REPORTED|RESOLVED --- Comment #4 from Andrew Crouthamel --- Thanks for the update! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 384023] IncidenceEditor sometimes clings to last remaining category
https://bugs.kde.org/show_bug.cgi?id=384023 Denis Kurz changed: What|Removed |Added Version|5.6.0 |5.9.2 --- Comment #2 from Denis Kurz --- Still valid in 18.08.2. -- You are receiving this mail because: You are watching all bug changes.
