[krita] [Bug 388531] Brush Rotation broken with Wacom Art Pen
https://bugs.kde.org/show_bug.cgi?id=388531 --- Comment #11 from Dmitry Kazakov --- I have tested ArtPen with Ubuntu 16.04 and it works perfectly normal :( # list of relevant wacom packages: libwacom-bin/xenial-updates,now 0.22-1~ubuntu16.04.1 amd64 [installed,automatic] libwacom-common/xenial-updates,xenial-updates,now 0.22-1~ubuntu16.04.1 all [installed,automatic] libwacom2/xenial-updates,now 0.22-1~ubuntu16.04.1 amd64 [installed,automatic] xserver-xorg-input-wacom/xenial,now 1:0.32.0-0ubuntu3 amd64 [installed,automatic] # Qt info Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.4.0 20160609) on "xcb" OS: Ubuntu 16.04.3 LTS [linux version 4.4.0-109-generic] -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391136] Edges of strokes are extremely pixelated
https://bugs.kde.org/show_bug.cgi?id=391136 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt --- Sorry, this is a bug tracker, not a help forum, and this is not a bug report but a help request. Check out the sharpness parameter for the brush engines (see the https://docs.krita.org). Also, make sure you understand the difference between various brush engines In your example: * the first stroke is antialiased. It's likely the bristle brush engine, which gives this effect. * the second stroke and the dot look like the ordinary round brush with sharpness dialed all the way up or fading all the way down * the brush after that is nicely anti-aliased, it looks a bit weird but that's because your canvas is really small * then the small brush is anti-aliased. It looks like your pen has some trouble sending proper tablet events, hence the stuttering * and the final line looks like the 1px brush, which does not do anti-aliasing. And do update to a more recent version of Krita than 3.1.4; if that is really the version you're using. And if you're really using Linux, specify where your packages come from, next time you have a real bug to report. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 352052] Dolphin startup fails when having hiragana (japanese) text in klipper history
https://bugs.kde.org/show_bug.cgi?id=352052 --- Comment #12 from William --- Problem seems to have gone away. Thanks -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 391148] New: Unhandled AVX instruction vmovq %xmm9,%xmm1
https://bugs.kde.org/show_bug.cgi?id=391148
Bug ID: 391148
Summary: Unhandled AVX instruction vmovq %xmm9,%xmm1
Product: valgrind
Version: 3.13.0
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: vex
Assignee: jsew...@acm.org
Reporter: taku...@schaft-inc.com
Target Milestone: ---
I ran valgrind 3.13.0 with my AVX program and it died with this message.
vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xC9 0xC4 0xE3 0x7D
0x18 0xC1 0x1
vex amd64->IR: REX=0 REX.W=0 REX.R=1 REX.X=0 REX.B=0
vex amd64->IR: VEX=1 VEX.L=0 VEX.n=0x0 ESC=0F
vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0
==17131== valgrind: Unrecognised instruction at address 0xe888c95.
I found the instruction was vmovq between xmm.
=> 0x0e888c95 <+213>: vmovq %xmm9,%xmm1
I can reproduce this problem by this code:
int main() {
asm("vmovq %xmm9, %xmm1");
return 0;
}
And found that "%xmm8, %xmm0" and "%xmm15, %xmm7" killed valgrind with similar
message but "%xmm15, %xmm8" didn't.
I also tried "%xmm0, %xmm8" and "%xmm8, %xmm9" and valgrind worked with them.
It seems valgrind cannot handle vmovq from xmm8-15 to xmm0-7.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 391147] New: Location Bar crashes Dolphin when dragging contents from folder panel into desired location
https://bugs.kde.org/show_bug.cgi?id=391147 Bug ID: 391147 Summary: Location Bar crashes Dolphin when dragging contents from folder panel into desired location Product: dolphin Version: 16.08.3 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: gmpin...@gmail.com Target Milestone: --- Intermittently, when dragging items from the folder panel into the location bar immediately above, where the directory hierarchy is displayed in a drop-down list, Dolphin crashes. This also happens in tabbed windows. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 391057] fit via context menu of curve does not always work
https://bugs.kde.org/show_bug.cgi?id=391057 Alexander Semke changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 391146] New: fix crash when some external APIs fail
https://bugs.kde.org/show_bug.cgi?id=391146 Bug ID: 391146 Summary: fix crash when some external APIs fail Product: amarok Version: 2.8.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Services/MP3tunes Assignee: amarok-bugs-d...@kde.org Reporter: jiazhouyan...@gmail.com CC: unnamedramb...@gmail.com Target Milestone: 2.9 Created attachment 111040 --> https://bugs.kde.org/attachment.cgi?id=111040&action=edit patch of reported bugs Hi, I'm a PhD student. I analyzed Amarok source code and found some potential API bugs that may cause crashes: 1. In src/services/mp3tunes/libmp3tunes/locker.c:1501:5, if "curl_easy_perform" failed, there would be unexcepted results. 2. In src/services/mp3tunes/libmp3tunes/locker.c:1479:14, if "fopen" failed, "hd_src" might cause a crash. I think it's unsafe to assume the library function would be correct. It would be better if we could handle the error properly. Attached please find the patch against version 2.8.0. Hopefully, it can solve these potential bugs. Best, Zhouyang -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391139] Powerdevil very slow in paging user about power states
https://bugs.kde.org/show_bug.cgi?id=391139 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- Can you monitor DBus to see what takes so long? If UPower takes a while to notify us there's nothing we could do. Is this just about the notification or does the battery icon also take a while to update? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362522] Cursor becomes "hand grab cursor" stuck after using "Set horizontal mirror mode"
https://bugs.kde.org/show_bug.cgi?id=362522 --- Comment #6 from dr.rosh...@gmail.com --- (In reply to John Di Pasquale from comment #0) > Every time I use the "Set Horizontal Mirror Mode". It gets stuck in "Hand > Grab Cursor Symbol". > > Reproducible: Always This also happens to me, on the vertical mirror tool. It causes my cursor to lag too. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362522] Cursor becomes "hand grab cursor" stuck after using "Set horizontal mirror mode"
https://bugs.kde.org/show_bug.cgi?id=362522 dr.rosh...@gmail.com changed: What|Removed |Added CC||dr.rosh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391145] Window list (as a desktop widget) shows a pin icon on the top right corner
https://bugs.kde.org/show_bug.cgi?id=391145 Yuze Jiang changed: What|Removed |Added CC||fortissi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379551] Sudden huge memory leaks when using KDevelop for an extended amount of time
https://bugs.kde.org/show_bug.cgi?id=379551 ddz changed: What|Removed |Added Attachment #110818|0 |1 is obsolete|| Attachment #110819|0 |1 is obsolete|| Attachment #110870|0 |1 is obsolete|| Attachment #110871|0 |1 is obsolete|| Attachment #110872|0 |1 is obsolete|| --- Comment #21 from ddz --- Created attachment 111039 --> https://bugs.kde.org/attachment.cgi?id=111039&action=edit kdevelop log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391145] New: Window list (as a desktop widget) shows a pin icon on the top right corner
https://bugs.kde.org/show_bug.cgi?id=391145 Bug ID: 391145 Summary: Window list (as a desktop widget) shows a pin icon on the top right corner Product: plasmashell Version: 5.12.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Window List Assignee: plasma-b...@kde.org Reporter: fortissi...@gmail.com Target Milestone: 1.0 Drag a window list widget onto the desktop, stretch it a bit and there's a pin icon on the top right corner. Clicking it takes no effect. This should only appear when the window list is a popup list. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379551] Sudden huge memory leaks when using KDevelop for an extended amount of time
https://bugs.kde.org/show_bug.cgi?id=379551 --- Comment #20 from ddz --- Hi, I don't see any "crash" keywords in terminal. Also, I found if I did the "clear cache" when launch kdevelop. Even run 10+ hours, the max memory usage VIRT 8922M, RES 3493M, SHR 32440 At least, my computer don't freeze. I can put the log file here. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379551] Sudden huge memory leaks when using KDevelop for an extended amount of time
https://bugs.kde.org/show_bug.cgi?id=379551 --- Comment #19 from ddz --- Hi, I don't see any "crash" keywords in terminal. Also, I found if I did the "clear cache" when launch kdevelop. Even run 10+ hours, the max memory usage VIRT 8922M, RES 3493M, SHR 32440 At least, my computer don't freeze. I can put the log file here. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 390507] No properties dialog for message widgets
https://bugs.kde.org/show_bug.cgi?id=390507 --- Comment #1 from Ralf Habacker --- Git commit a5b5a46a52c36ca45288e3d3272470eac3545daa by Ralf Habacker. Committed on 27/02/2018 at 05:24. Pushed by habacker into branch 'master'. Move operation properties dialog related setup and applying code into class SelectOperationDialog Dialog setup from widget/umlobject and applying to them was implemented in client code (class FloatingTextWidget) instead of the related dialog class, which makes it hard to reuse the operation properties dialog from other locations. M +70 -2umbrello/dialogs/selectoperationdialog.cpp M +7-1umbrello/dialogs/selectoperationdialog.h M +3-52 umbrello/umlwidgets/floatingtextwidget.cpp https://commits.kde.org/umbrello/a5b5a46a52c36ca45288e3d3272470eac3545daa -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391135] After window resizing, touch maximize button using a touch screen does not maximize the window
https://bugs.kde.org/show_bug.cgi?id=391135 Martin Flöser changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391144] New: Discover's sort menu inappropriately uses checkboxes instead of radio buttons
https://bugs.kde.org/show_bug.cgi?id=391144 Bug ID: 391144 Summary: Discover's sort menu inappropriately uses checkboxes instead of radio buttons Product: Discover Version: 5.12.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: n...@kde.org Target Milestone: --- Discover's new sort menu inappropriately uses checkboxes instead of radio buttons. This results in a really awkward interaction paradigm where you need to uncheck the existing sort order before you can check the other one. It's also just wrong: checkboxes are uses when multiple selection is allowed; when the items are mutually exclusive, the correct control is a set of ratio buttons. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 391141] Various basic notifications present on major operating systems are not available on KDE
https://bugs.kde.org/show_bug.cgi?id=391141 --- Comment #1 from Zakhar --- Also include to the list airplane mode notification. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 391143] Device information is not updating when navigating using arrow keys
https://bugs.kde.org/show_bug.cgi?id=391143 --- Comment #2 from Yuze Jiang --- Just found it's a duplicate, sorry about that. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 391143] Device information is not updating when navigating using arrow keys
https://bugs.kde.org/show_bug.cgi?id=391143 Yuze Jiang changed: What|Removed |Added Status|RESOLVED|VERIFIED -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 391143] Device information is not updating when navigating using arrow keys
https://bugs.kde.org/show_bug.cgi?id=391143 Yuze Jiang changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Yuze Jiang --- *** This bug has been marked as a duplicate of bug 300265 *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 300265] keyboard navigation doesn't update the device info on the right
https://bugs.kde.org/show_bug.cgi?id=300265 Yuze Jiang changed: What|Removed |Added CC||fortissi...@gmail.com --- Comment #2 from Yuze Jiang --- *** Bug 391143 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 391143] New: Device information is not updating when navigating using arrow keys
https://bugs.kde.org/show_bug.cgi?id=391143 Bug ID: 391143 Summary: Device information is not updating when navigating using arrow keys Product: kinfocenter Version: 5.12.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Device Viewer Assignee: hubn...@gmail.com Reporter: fortissi...@gmail.com Target Milestone: --- Steps to reproduce: - Open info center and go to Device Viewer - Unfold processors and storage drives - Navigate items using up and down key, device information on the right hand side does not update -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391142] New: "Unmet dependencies" passiveNotifications while browsing
https://bugs.kde.org/show_bug.cgi?id=391142 Bug ID: 391142 Summary: "Unmet dependencies" passiveNotifications while browsing Product: Discover Version: 5.12.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: n...@kde.org Target Milestone: --- Created attachment 111038 --> https://bugs.kde.org/attachment.cgi?id=111038&action=edit Unmet dependency errors while browsing Recently Discover has started to emit passiveNotifications about unmet dependencies while browsing app lists. There are several problems here: 1. This is not appropriate or something the user needs to be burdened with while browsing. At most, Discover should show an error message during installation of the broken app, not anywhere else. 2. PassiveNotifications should be safely ignorable, e.g. for status updates. These errors are not ignorable; they block installation and must be dealt with. It is not appropriate to use a passiveNotification for these errors. Solution: - While browsing, don't show passiveNotifications about unmet dependencies - When trying to install an app with broken dependencies, show a real modal error pop-up with the full detailed message, so ensure that the user sees it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391063] Memory Leak in Plasmashell
https://bugs.kde.org/show_bug.cgi?id=391063 boonhead.nl changed: What|Removed |Added CC||bugs.kde@boonhead.nl --- Comment #1 from boonhead.nl --- Hello my follow bug reporter :) We might be experiencing the same issue. I have had an issue with plasmashell after upgrading from KDE Neon 5.8 LTS to 5.12 LTS, but I didn't report it yet as I did not have the skill set to investigate deeper and make a bug report with more detail. Lucky for us, it might be that some smart people are already on it => https://bugs.kde.org/show_bug.cgi?id=368838 As I was searching similar bug reports I came across yours and thought your problem might be the same. Could you check if your problem goes away if you run the following line in the terminal? pkill plasmashell; QSG_RENDER_LOOP=threaded kstart plasmashell It will kill the current plasmashell process, and then restart it using the QSG_RENDER_LOOP set to "threaded". Upon conclusion, you might want to mark this bug a duplicate of 368838. Thanx in advance, as your findings will be very helpful. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390436] Component "plasmashell", took too much memory
https://bugs.kde.org/show_bug.cgi?id=390436 boonhead.nl changed: What|Removed |Added CC||bugs.kde@boonhead.nl --- Comment #1 from boonhead.nl --- Hey glewik, my follow bug reporter :) We might be experiencing the same issue. I have had an issue with plasmashell after upgrading from KDE Neon 5.8 LTS to 5.12 LTS, but I didn't report it yet as I did not have the skill set to investigate deeper and make a bug report with more detail. Lucky for us, it might be that some smart people are already on it => https://bugs.kde.org/show_bug.cgi?id=368838 As I was searching similar bug reports I came across yours and thought your problem might be the same. Could you check if your problem goes away if you run the following line in the terminal? pkill plasmashell; QSG_RENDER_LOOP=threaded kstart plasmashell It will kill the current plasmashell process, and then restart it using the QSG_RENDER_LOOP set to "threaded". Upon conclusion, you might want to mark this bug a duplicate of 368838. Thanx in advance, as your findings will be very helpful. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 386893] kmymoney language setting
https://bugs.kde.org/show_bug.cgi?id=386893 --- Comment #10 from lajoie --- I will check as soon as possible. on the other hand under Mga6 and Mga7 the date format is / mm / dd how to change to dd / mm / ? thank you -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 386893] kmymoney language setting
https://bugs.kde.org/show_bug.cgi?id=386893 --- Comment #9 from lajoie --- I will check as soon as possible. on the other hand under Mga6 and Mga7 the date format is / mm / dd how to change to dd / mm / ? thank you Le 25/02/2018 à 13:38, Ralf Habacker a écrit : > https://bugs.kde.org/show_bug.cgi?id=386893 > > Ralf Habacker changed: > > What|Removed |Added > > Resolution|--- |WORKSFORME > Status|UNCONFIRMED |RESOLVED > > --- Comment #8 from Ralf Habacker --- > KDE4 apps saves there language settings into ~/.kde4/share/config/kmymoneyrc > By chaning the following entry, or adding if not present > > [Locale] > Language=fr > > kmymoney should have french gui. > -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391139] Powerdevil very slow in paging user about power states
https://bugs.kde.org/show_bug.cgi?id=391139 Zakhar changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 391138] Ark becomes slow when working with large archives
https://bugs.kde.org/show_bug.cgi?id=391138 Zakhar changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 391141] Various basic notifications present on major operating systems are not available on KDE
https://bugs.kde.org/show_bug.cgi?id=391141 Zakhar changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 391141] Various basic notifications present on major operating systems are not available on KDE
https://bugs.kde.org/show_bug.cgi?id=391141 Zakhar changed: What|Removed |Added Version|unspecified |5.43.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 391141] New: Various basic notifications present on major operating systems are not available on KDE
https://bugs.kde.org/show_bug.cgi?id=391141 Bug ID: 391141 Summary: Various basic notifications present on major operating systems are not available on KDE Product: frameworks-knotifications Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: zakhar.nasi...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- It would be ideal if KDE would provide notification events for: attached USB devices attached HDMI/VGA devices RJ45 jack connection uplink wireless connection established SDcard reader card inserted detection powerbutton pressed notification those are basic notifications absent from KDE which would be a great compliment to the system. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 391140] New: [Feature request] Display right click menu when right clicking on the results.
https://bugs.kde.org/show_bug.cgi?id=391140 Bug ID: 391140 Summary: [Feature request] Display right click menu when right clicking on the results. Product: krunner Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: filesearch Assignee: baloo-bugs-n...@kde.org Reporter: idmresettr...@gmail.com Target Milestone: --- Like when right clicking on a file in Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391139] Powerdevil very slow in paging user about power states
https://bugs.kde.org/show_bug.cgi?id=391139 --- Comment #1 from Zakhar --- After further testing I verified connecting PC to AC yields notifications far quicker than disconnecting. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 384122] KOrganizer - No invitation sent when selecting multiple attendees + no email address autocompletion
https://bugs.kde.org/show_bug.cgi?id=384122 Jochen Trumpf changed: What|Removed |Added CC||jochen.tru...@anu.edu.au --- Comment #8 from Jochen Trumpf --- I have the same issue in version 5.6.3. I rarely use this functionality so I am unsure how long the bug has been there. Starting from a console gives (edited for privacy): Input: "Jochen Trumpf , a@b" Error: "The email address you have entered is not valid because it contains an unexpected comma." This is with mixed address types but the same happens with a single type. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391139] New: Powerdevil very slow in paging user about power states
https://bugs.kde.org/show_bug.cgi?id=391139 Bug ID: 391139 Summary: Powerdevil very slow in paging user about power states Product: Powerdevil Version: 5.12.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: zakhar.nasi...@gmail.com Target Milestone: --- Laptop connected to AC then disconnected powerdevil issues a page to user stating PC has been disconnected, however it takes over 3-4 seconds to do so. Same goes for attaching laptop to AC also yields same slowness. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 391138] New: Ark becomes slow when working with large archives
https://bugs.kde.org/show_bug.cgi?id=391138 Bug ID: 391138 Summary: Ark becomes slow when working with large archives Product: ark Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: zakhar.nasi...@gmail.com CC: rthoms...@gmail.com Target Milestone: --- The app ark being a capable necessary component of KDE becomes utterly useless when opening and working with archives over 80MBs with many files in it. What happens when opening an archive it has to sit there and scan thru it for no good reason, no other archive manager does this. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 390911] While updating, app/package list should sort by completion percentage
https://bugs.kde.org/show_bug.cgi?id=390911 --- Comment #5 from Nate Graham --- Created attachment 111037 --> https://bugs.kde.org/attachment.cgi?id=111037&action=edit Not quite Did a big update with Discover built from git master (after merging Plasma 5.12), and it's still not what I'm looking for here. See attached screenshot. Sorting by completion percentage would ensure that you're always looking at something that's happening and you can tell that there's progress. We still don't quite have that here. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391130] Sometimes an arrow appears before screenshot loading is completed
https://bugs.kde.org/show_bug.cgi?id=391130 --- Comment #2 from Dr. Chapatin --- Hi Nate A menu with sorting options is opened. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391130] Sometimes an arrow appears before screenshot loading is completed
https://bugs.kde.org/show_bug.cgi?id=391130 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Nate Graham --- Unrelatedly, what happens if you click on the "Sort" button that's visible in your screenshot? Something, or nothing? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391084] Unclickable dead zone to the left of the application menu button (regularly impeding user).
https://bugs.kde.org/show_bug.cgi?id=391084 --- Comment #3 from Nate Graham --- It's no problem at all. In fact, more duplicates may help convince the KWin maintainer that this is a serious problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391084] Unclickable dead zone to the left of the application menu button (regularly impeding user).
https://bugs.kde.org/show_bug.cgi?id=391084 --- Comment #2 from boonhead.nl --- Thank you Nate. This worked for me. Sorry for posting duplicate. I did not find similar bugs using the words I used. Cheers! -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 391116] kaffeine doesn't find some transponders on Astr 19.2E
https://bugs.kde.org/show_bug.cgi?id=391116 --- Comment #1 from Mauro Carvalho Chehab --- (In reply to peter from comment #0) > Created attachment 111025 [details] > Debug info presented ba caffeine in the diagnostic window > > kaffeine finds only some transponders on Astra 19.3E. For example the > stations on 10744 Mhz (Phoenix, arte, tagesschau24, all SD) are omitted. > Many other channels are ok. The DVB-Card /Skystar2) is ok, runs in an > Windows environment in same machine. Manual entry of the channels isn't > possible, because the Audio-PID-field is not editable. Same Problem with > version 2.0.14. > > The diagnostic window of kaffeine is in the appeded file Did you try to enable "Other NIT" options at Kaffeine scan popup window? It takes more time to parse channels, but it should find the other channels. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Brett Keller changed: What|Removed |Added CC||blkel...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391137] Lock icon (system-lock-screen) doesn't retain its line-art appearance at large sizes with Plasma Breeze theme
https://bugs.kde.org/show_bug.cgi?id=391137 --- Comment #2 from Nate Graham --- Created attachment 111036 --> https://bugs.kde.org/attachment.cgi?id=111036&action=edit Icon looks wrong at units.iconSizes.large size -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391137] Lock icon (system-lock-screen) doesn't retain its line-art appearance at large sizes with Plasma Breeze theme
https://bugs.kde.org/show_bug.cgi?id=391137 --- Comment #1 from Nate Graham --- Created attachment 111035 --> https://bugs.kde.org/attachment.cgi?id=111035&action=edit Icon looks fine at units.iconSizes.medium size -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391137] New: Lock icon (system-lock-screen) doesn't retain its line-art appearance at large sizes with Plasma Breeze theme
https://bugs.kde.org/show_bug.cgi?id=391137 Bug ID: 391137 Summary: Lock icon (system-lock-screen) doesn't retain its line-art appearance at large sizes with Plasma Breeze theme Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: n...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 The system-lock-screen icon loses its line-art appearance with the Plasma theme when rendered at units.iconSizes.large size. Instead, it looks like a screen with a lock in it. It looks fine when its size is units.iconSizes.medium. See attached screenshots. The problem does not reproduce with the Oxygen theme. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 390744] Parenthesis 2 error
https://bugs.kde.org/show_bug.cgi?id=390744 --- Comment #2 from Robby Stephenson --- Git commit 74cd5ca785e1ea5ca746098fce3efc99858eb7d7 by Robby Stephenson. Committed on 27/02/2018 at 02:31. Pushed by rstephenson into branch '3.1'. Add a unit test to expose crashing bug when reading XMP data BlueSquare.jpg is a test file from the exiv library. Linking to EXEMPI causes a crash, no matter whether XMPHandler is initialized or not M +4-0src/tests/CMakeLists.txt A +---src/tests/data/BlueSquare.jpg M +29 -1src/tests/filelistingtest.cpp M +1-0src/tests/filelistingtest.h https://commits.kde.org/tellico/74cd5ca785e1ea5ca746098fce3efc99858eb7d7 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 362890] Very slow to load folders from NTFS drive
https://bugs.kde.org/show_bug.cgi?id=362890 --- Comment #3 from northon_patri...@yahoo.ca --- It still happen on Fedora with the official package (fully up to date at this time). It doesn't happen on Ubuntu. Is it compiled differently on Fedora? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390864] Notifications have cropped images
https://bugs.kde.org/show_bug.cgi?id=390864 Scott Harvey changed: What|Removed |Added CC||bund...@gmail.com --- Comment #6 from Scott Harvey --- I'll take a look at dynamically sizing the notification popup and/or image area based on the size of the capture. I personally feel that the whole image should be shown; otherwise it gives the impression that the screengrab was inaccurate or incomplete. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391136] New: Edges of strokes are extremely pixelated
https://bugs.kde.org/show_bug.cgi?id=391136 Bug ID: 391136 Summary: Edges of strokes are extremely pixelated Product: krita Version: 3.1.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: aporrino2...@queensinquiry.com Target Milestone: --- Created attachment 111034 --> https://bugs.kde.org/attachment.cgi?id=111034&action=edit Several brushstrokes with different brushes, illustrating the problem. I don't know why, but one day I opened up Krita and all the brush strokes rendered like the attachment. I checked on another program to make sure it wasn't a problem with my pen, and that came out fine. I really do like this program, and would want to continue to use it, but I can't if the strokes continue being like this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365696] Brush lag and cursor wont appear on screen when drawing
https://bugs.kde.org/show_bug.cgi?id=365696 mninja...@gmail.com changed: What|Removed |Added CC||mninja...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #57 from Matt Whitlock --- (In reply to Marco Martin from comment #50) > can this be tried again with a more recent Qt? either the latest 5.9 or 5.10 > making sure both of these patches are in: > > https://codereview.qt-project.org/#/c/200715/ > https://codereview.qt-project.org/#/c/202781/ The second patch set (202781) is a reversion of the first patch set (200715) plus one extra line [sgrc->endSync();]. I confirm that the dev-qt/qtdeclarative-5.9.4 that is built on my Gentoo system does contain that added line. (In reply to Alexander Schlarb from comment #48) > 2. Memory usage of the offending process will be accounted correctly with > running it with `LIBGL_ALWAYS_SOFTWARE=true`, but the leaking issue will > persist I tried this and do confirm that the leak persists and is accounted to the plasmashell process. In this case, radeontop shows unchanging VRAM usage, which is not surprising, given that the rendering is happening all in software. (The transitions between wallpaper images are a lot jerkier, and CPU usage is through the roof.) It's worth noting that triggering this bug is not always so simple as starting up a plasmashell and running a slideshow. For me, it can take many minutes of running an aggressive slideshow before plasmashell starts to leak memory. Maybe this suggests that a race condition is the initial triggering event that leads into the state in which plasmashell leaks textures. Also, I'm not sure if this is a placebo effect, but it may be that mousing over the launcher icons and task manager buttons in the panel (to cause the sliding tooltips effect) may increase the likelihood of starting the memory leak. Once it starts leaking, it's dramatic and fast when you're running a slideshow wallpaper with a 1-second interval. (In reply to gertlink_nospam from comment #51) > QSG_RENDER_LOOP=threaded solves the problem here. After about 10 minutes of trying, I have been unable to trigger the leak when running plasmashell with the threaded render loop. I'll leave the slideshow wallpaper enabled (with a less aggressive, 29-minute interval), using this threaded render loop, and I'll continue to monitor for excessive VRAM usage. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 325653] MIGRATION : database conversion is very slow
https://bugs.kde.org/show_bug.cgi?id=325653 Michał Karwowski changed: What|Removed |Added CC||pro...@gmail.com --- Comment #6 from Michał Karwowski --- I'm confirming, that in DigiKam 5.8.0 - migration from MySQL to SQLite is very slow. To speed up, I have created RAM disk to store SQLite database, but still, it takes ages. I notice, that during migration .jurnal file is created and deleted over and over again. That's why I think it might be related to single insert transaction commits. According to http://www.sqlite.org/faq.html#q19 --- Transaction speed is limited by disk drive speed because (by default) SQLite actually waits until the data really is safely stored on the disk surface before the transaction is complete. That way, if you suddenly lose power or if your OS crashes, your data is still safe. For details, read about atomic commit in SQLite.. By default, each INSERT statement is its own transaction. But if you surround multiple INSERT statements with BEGIN...COMMIT then all the inserts are grouped into a single transaction. The time needed to commit the transaction is amortized over all the enclosed insert statements and so the time per insert statement is greatly reduced. -- Thus probably it would be a good idea to wrap inserts by some transaction. Moreover, we could try to do some tweaks to improve performance. We can ask SQLite not to delete and recreate file over and over again for each insert, by using PRAGMA JOURNAL_MODE. With value eg. 'TRUNCATE', we can keep journal file, but it will be cleared. If we can accept loose of imported data on eg power failure, we can use some pragmas to speed up. See: https://blog.devart.com/increasing-sqlite-performance.html See: https://stackoverflow.com/questions/1711631/improve-insert-per-second-performance-of-sqlite -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375666] Please add option to adjust output RGB range
https://bugs.kde.org/show_bug.cgi?id=375666 grouchomarx...@gmail.com changed: What|Removed |Added CC||grouchomarx...@gmail.com --- Comment #4 from grouchomarx...@gmail.com --- I strongly agree. Plasma on Wayland is shaping up nicely, but the picture is washed out on my hdmi monitors due to this issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391135] New: After window resizing, touch maximize button using a touch screen does not maximize the window
https://bugs.kde.org/show_bug.cgi?id=391135 Bug ID: 391135 Summary: After window resizing, touch maximize button using a touch screen does not maximize the window Product: kwin Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- I use a laptop with touch screen, neon dev unstable. Reproducible only using apps running natively under Wayland. open okular or konsole resize the window dragging some border touch maximize button in window decoration Result: window is not maximized. Depending on how the window was resized, sometimes the window changes its position on screen quickly and back to original position or sometimes the window remains in the new position. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 391134] Don't have an icon for num lock key
https://bugs.kde.org/show_bug.cgi?id=391134 --- Comment #1 from Aleix Pol --- Git commit e2c9a044e51220cf4488bd449c2e963c68c88df1 by Aleix Pol. Committed on 27/02/2018 at 00:18. Pushed by apol into branch 'master'. At least show an awkward overlay for numlock At least until we have a proper icon M +8-1applets/keyboardindicator/contents/ui/main.qml https://commits.kde.org/kdeplasma-addons/e2c9a044e51220cf4488bd449c2e963c68c88df1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391115] Very slow search, full text search (FTS) proposition for huge speedup.
https://bugs.kde.org/show_bug.cgi?id=391115 --- Comment #5 from Michał Karwowski --- (In reply to Michał Karwowski from comment #4) > Thanks for 'DebugView' - I didn't know such tool exists. > > I made more detail research on the problem. > > > To be precise, my total media count from DigiKam database stats is about > 108012. > (I didn't add all folders to DigiKam) > > When I run the application I see in a log: > [8144] digikam.database: Search result: 1512168 > > But: "1 512 168" is much more than "108 012"! > Strange.. what does it mean? > > > == > == > Text filter (available on the right) > == > == > > The problem with speed appears to be related to "Text filter" which I use. > Filtering pictures with that filter takes from 20 seconds to 3 minutes. > > DebugView doesn't show logs for database on "text filter". > Thus now, I believe that's it's not related to database engine, > but rather internal filtering system. > > Filter query: 'tajlandia' took 2 minutes 31 seconds (to display results - > 8586 items). > Filter query: 'żaba' took 1 minute 25 seconds (to display results - 1862 > items). > etc. > Clearing filter also takes lots of time. > > I did tests with offline and online albums. > By term offline I mean disconnected USB drive with albums. > By term online I mean connected USB drive with albums. > Measurements I have don after the inilial digikam scan. > > > == > == > Search (available on the left) > == > == > When I use search I see digikam.database logs on DebugView. > This suggests that for searching database query is made in contrast to > filtering. > > To be clear I use: digiKam 5.8.0 with mariadb 10.2.10 winx64 > > > Query for: "gosia" (164794 results?) > > 1448 21:55:15[10424] digikam.general: keywords changed to ' > "gosia" ' > 1449 21:55:15[10424] digikam.geoiface: > 1450 21:55:15[10424] digikam.geoiface: > 1451 21:55:15[10424] digikam.geoiface: > 1452 21:55:15[10424] digikam.general: Using 8 CPU core to > run threads > 1453 21:55:15[10424] digikam.general: Action Thread run 1 > new jobs > 1454 21:55:15[10424] digikam.database: " ( ( > (Albums.relativePath LIKE > ?) OR (Images.name LIKE ?) OR (Images.id IN(SELECT imageid FROM > ImageTags WHERE tagid IN(SELECT id FROM Tags WHERE name LIKE ?))) OR > (Albums.caption LIKE ?) OR (Albums.collection LIKE ?) OR (Images.id IN > (SELECT imageid FROM ImageComments WHERE type=? AND comment LIKE ?)) OR > (Images.id IN (SELECT imageid FROM ImageComments WHERE type=? AND comment > LIKE ?)) ) ) " > 1455 21:55:15[10424] digikam.database: Search query: > 1458 21:55:16[10424] digikam.database: Search result: 164794 > # Result is ready but not visible > > 1459 21:55:19[10424] digikam.general: Cancel Main Thread > 1507 21:55:22[10424] digikam.general: One job is done > 1508 21:55:24[10424] digikam.general: Cancel Main Thread > 1509 21:55:45[10424] digikam.geoiface: > 1512 21:55:50[10424] digikam.general: keywords changed to ' > "gosia" ' > 1513 21:55:50[10424] digikam.general: same keywords as > before, > ignoring... > 1514 21:55:58[10424] digikam.general: keywords changed to ' > "ekp" ' > # application is responsive again > > > > > Query for: "ekp" (394240 results?) > > > 1514 21:55:58[10424] digikam.general: keywords changed to ' > "ekp" ' > 1515 21:55:58[10424] digikam.geoiface: > 1516 21:55:58[10424] digikam.geoiface: > 1517 21:55:58[10424] digikam.geoiface: > 1518 21:55:58[10424] digikam.general: Using 8 CPU core to > run threads > 1519 21:55:58[10424] digikam.general: Action Thread run 1 > new jobs > 1520 21:55:58[10424] digikam.database: " ( ( > (Albums.relativePath LIKE > ?) OR (Images.name LIKE ?) OR (Images.id IN(SELECT imageid FROM > ImageTags WHERE tagid IN(SELECT id FROM Tags WHERE name LIKE ?))) OR > (Albums.caption LIKE ?) OR (Albums.collection LIKE ?) OR (Images.id IN > (SELECT imageid FROM ImageComments WHERE type=? AND comment LIKE ?)) OR > (Images.id IN (SELECT imageid FROM ImageComments WHERE type=? AND comment > LIKE ?)) ) ) " > 1521 21:55:58[10424] digikam.database: Search query: > 1524 21:56:00[10424] digikam.database: Search result:
[trojita] [Bug 358680] sort order not saved when not threaded
https://bugs.kde.org/show_bug.cgi?id=358680 Brandon Watkins changed: What|Removed |Added CC||bwa...@gmail.com --- Comment #4 from Brandon Watkins --- This is a pretty huge usability issue (seriously, no one wants to sort new mails to the bottom) if your mail server does not support threading (in which case there's no workaround by enabling threading, your sorting settings are always reset no matter what). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 391134] New: Don't have an icon for num lock key
https://bugs.kde.org/show_bug.cgi?id=391134 Bug ID: 391134 Summary: Don't have an icon for num lock key Product: Breeze Version: 5.12.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: aleix...@kde.org CC: kain...@gmail.com Target Milestone: --- I'm implementing a plasmoid that would show which lock keys are currently locked. For Caps Lock we have "input-caps-on", it would be interesting to have an icon for the "Num Lock". Thanks!! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391115] Very slow search, full text search (FTS) proposition for huge speedup.
https://bugs.kde.org/show_bug.cgi?id=391115 --- Comment #4 from Michał Karwowski --- Thanks for 'DebugView' - I didn't know such tool exists. I made more detail research on the problem. To be precise, my total media count from DigiKam database stats is about 108012. (I didn't add all folders to DigiKam) When I run the application I see in a log: [8144] digikam.database: Search result: 1512168 But: "1 512 168" is much more than "108 012"! Strange.. what does it mean? == == Text filter (available on the right) == == The problem with speed appears to be related to "Text filter" which I use. Filtering pictures with that filter takes from 20 seconds to 3 minutes. DebugView doesn't show logs for database on "text filter". Thus now, I believe that's it's not related to database engine, but rather internal filtering system. Filter query: 'tajlandia' took 2 minutes 31 seconds (to display results - 8586 items). Filter query: 'żaba' took 1 minute 25 seconds (to display results - 1862 items). etc. Clearing filter also takes lots of time. I did tests with offline and online albums. By term offline I mean disconnected USB drive with albums. By term online I mean connected USB drive with albums. Measurements I have don after the inilial digikam scan. == == Search (available on the left) == == When I use search I see digikam.database logs on DebugView. This suggests that for searching database query is made in contrast to filtering. To be clear I use: digiKam 5.8.0 with mariadb 10.2.10 winx64 Query for: "gosia" (164794 results?) 144821:55:15[10424] digikam.general: keywords changed to ' "gosia" ' 144921:55:15[10424] digikam.geoiface: 145021:55:15[10424] digikam.geoiface: 145121:55:15[10424] digikam.geoiface: 145221:55:15[10424] digikam.general: Using 8 CPU core to run threads 145321:55:15[10424] digikam.general: Action Thread run 1 new jobs 145421:55:15[10424] digikam.database: " ( ( (Albums.relativePath LIKE ?) OR (Images.name LIKE ?) OR (Images.id IN (SELECT imageid FROM ImageTags WHERE tagid IN(SELECT id FROM Tags WHERE name LIKE ?))) OR (Albums.caption LIKE ?) OR (Albums.collection LIKE ?) OR (Images.id IN (SELECT imageid FROM ImageComments WHERE type=? AND comment LIKE ?)) OR (Images.id IN (SELECT imageid FROM ImageComments WHERE type=? AND comment LIKE ?)) ) ) " 145521:55:15[10424] digikam.database: Search query: 145821:55:16[10424] digikam.database: Search result: 164794 # Result is ready but not visible 145921:55:19[10424] digikam.general: Cancel Main Thread 150721:55:22[10424] digikam.general: One job is done 150821:55:24[10424] digikam.general: Cancel Main Thread 150921:55:45[10424] digikam.geoiface: 151221:55:50[10424] digikam.general: keywords changed to ' "gosia" ' 151321:55:50[10424] digikam.general: same keywords as before, ignoring... 151421:55:58[10424] digikam.general: keywords changed to ' "ekp" ' # application is responsive again Query for: "ekp" (394240 results?) 151421:55:58[10424] digikam.general: keywords changed to ' "ekp" ' 151521:55:58[10424] digikam.geoiface: 151621:55:58[10424] digikam.geoiface: 151721:55:58[10424] digikam.geoiface: 151821:55:58[10424] digikam.general: Using 8 CPU core to run threads 151921:55:58[10424] digikam.general: Action Thread run 1 new jobs 152021:55:58[10424] digikam.database: " ( ( (Albums.relativePath LIKE ?) OR (Images.name LIKE ?) OR (Images.id IN (SELECT imageid FROM ImageTags WHERE tagid IN(SELECT id FROM Tags WHERE name LIKE ?))) OR (Albums.caption LIKE ?) OR (Albums.collection LIKE ?) OR (Images.id IN (SELECT imageid FROM ImageComments WHERE type=? AND comment LIKE ?)) OR (Images.id IN (SELECT imageid FROM ImageComments WHERE type=? AND comment LIKE ?)) ) ) " 152121:55:58[10424] digikam.database: Search query: 152421:56:00[10424] digikam.database: Search result: 394240 152521:56:08[10424] digikam.general: Cancel Main Thread 152621:56:18[10424] digikam.general: One job is done 157521:56:23[10424] digikam.geoiface:
[muon] [Bug 382538] Muon has generic Wayland icon
https://bugs.kde.org/show_bug.cgi?id=382538 --- Comment #1 from Dr. Chapatin --- Icon from window decoration is still wrong. Muon 5.7, neon dev unstable. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389852] Impossible to install muon package manager (unmet dependencies)
https://bugs.kde.org/show_bug.cgi?id=389852 Dr. Chapatin changed: What|Removed |Added Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389852] Impossible to install muon package manager (unmet dependencies)
https://bugs.kde.org/show_bug.cgi?id=389852 Dr. Chapatin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Dr. Chapatin --- Today I reinstalled neon because other issues. Muon is now installed. -- You are receiving this mail because: You are watching all bug changes.
[kalzium] [Bug 391133] New: Can't fetch molecules
https://bugs.kde.org/show_bug.cgi?id=391133 Bug ID: 391133 Summary: Can't fetch molecules Product: kalzium Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kalz...@kde.org Reporter: leewilkerso...@gmail.com Target Milestone: --- Created attachment 111033 --> https://bugs.kde.org/attachment.cgi?id=111033&action=edit Error in file fetch Error attempting to obtain file: http://data.kstuff.org/cgi-bin/hotstuff-provider?site=kalzium -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350944] Clicking on systray icon yields unpredictable result
https://bugs.kde.org/show_bug.cgi?id=350944 --- Comment #7 from Thomas Tanghus --- (In reply to Alexander Mentyu from comment #6) > Although results in my previous comment may be due to Focus stealing > prevention setting set to 'Medium' Setting Focus stealing prevention to High does indeed bring Clementine to the foreground, but it still doesn't hide again when clicked on systray, and it prevents the Plasma Launcher from showing. Isn't it application specific, since it happens differently on different apps? I haven't coded Qt/Plasma for years, so I have no idea on how to implement window rules. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 391132] kmail crashes when trying to select akonadi agents in kmail settings
https://bugs.kde.org/show_bug.cgi?id=391132 --- Comment #1 from o...@eclipso.eu --- Created attachment 111032 --> https://bugs.kde.org/attachment.cgi?id=111032&action=edit Screenshot akonadi agents -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 391083] Allow user to 'press' keys that aren't on Android keyboard
https://bugs.kde.org/show_bug.cgi?id=391083 --- Comment #1 from Albert Vaca --- You can download a keyboard with special keys, like Hacker's Keyboard, if you need them. Google Play: https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard&hl=en FDroid: https://f-droid.org/en/packages/org.pocketworkstation.pckeyboard/ -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 391132] New: kmail crashes when trying to select akonadi agents in kmail settings
https://bugs.kde.org/show_bug.cgi?id=391132 Bug ID: 391132 Summary: kmail crashes when trying to select akonadi agents in kmail settings Product: kontact Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: o...@eclipso.eu Target Milestone: --- Application: kontact (5.5.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.114-42-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: trying to activate akonadi agents - Unusual behavior I noticed: the first three akonadi agents didn't show any text. Selecting one of them and hitting "apply" makes kmail crash. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7778b4c780 (LWP 1593))] Thread 26 (Thread 0x7f763b7fe700 (LWP 1646)): #0 0x7f77715310ff in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7768d3a5d9 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f7768d3ad9d in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f7768d3b5c0 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f7768d3831e in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f777152c724 in start_thread () from /lib64/libpthread.so.0 #6 0x7f777558ee8d in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7f76414bf700 (LWP 1641)): #0 0x7f77708ef2a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f77708ef42c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #2 0x7f77760a91ab in QEventDispatcherGlib::processEvents (this=0x7f763c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #3 0x7f7776056bfb in QEventLoop::exec (this=this@entry=0x7f76414bee50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #4 0x7f7775e91f5a in QThread::exec (this=) at thread/qthread.cpp:500 #5 0x7f7775e96a29 in QThreadPrivate::start (arg=0x262b610) at thread/qthread_unix.cpp:365 #6 0x7f777152c724 in start_thread () from /lib64/libpthread.so.0 #7 0x7f777558ee8d in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f76537fe700 (LWP 1626)): #0 0x7f777558630d in poll () from /lib64/libc.so.6 #1 0x7f77708ef314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f77708ef42c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f77760a91ab in QEventDispatcherGlib::processEvents (this=0x7f76440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f7776056bfb in QEventLoop::exec (this=this@entry=0x7f76537fde50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #5 0x7f7775e91f5a in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7f7775e96a29 in QThreadPrivate::start (arg=0x1f9c810) at thread/qthread_unix.cpp:365 #7 0x7f777152c724 in start_thread () from /lib64/libpthread.so.0 #8 0x7f777558ee8d in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f7653fff700 (LWP 1625)): #0 0x7f7770930899 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f77708eeef6 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #2 0x7f77708ef388 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f77708ef42c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f77760a91ab in QEventDispatcherGlib::processEvents (this=0x7f764c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f7776056bfb in QEventLoop::exec (this=this@entry=0x7f7653ffee50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #6 0x7f7775e91f5a in QThread::exec (this=) at thread/qthread.cpp:500 #7 0x7f7775e96a29 in QThreadPrivate::start (arg=0x1ff2ce0) at thread/qthread_unix.cpp:365 #8 0x7f777152c724 in start_thread () from /lib64/libpthread.so.0 #9 0x7f777558ee8d in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f765962f700 (LWP 1624)): #0 0x7f777558630d in poll () from /lib64/libc.so.6 #1 0x7f77708ef314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f77708ef42c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f77760a91ab in QEventDispatcherGlib::processEvents (this=0x7f76540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f7776056bfb in QEventLoop::exec (this=this@entry=0x7f765962ee50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #5 0x7f7775e91f5a in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7f7775e96a29 in QThreadPrivate::start (arg=0x2024620) at thread/qthread_unix.cpp:365 #7 0x7f777152c724 in start_thread () from /lib64/libpt
[plasmashell] [Bug 391013] Icon of an app already present in favorites list is duplicated when such app is configured as default in system settings
https://bugs.kde.org/show_bug.cgi?id=391013 --- Comment #2 from Dr. Chapatin --- Ok, update the default web browser icon is correct. But I think that the second icon should be removed. Two icons of the same app in the same place does no sense. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391013] Icon of an app already present in favorites list is duplicated when such app is configured as default in system settings
https://bugs.kde.org/show_bug.cgi?id=391013 Eike Hein changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Eike Hein --- The default web browser favorite is magic and updates with the default browser - intentionally. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390134] Why clicking on a link has a delay before it opens the page?
https://bugs.kde.org/show_bug.cgi?id=390134 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com --- Comment #7 from Rex Dieter --- I can confirm unchecking "in an application based on the contents" makes links open (more) immediately in a webbrowser. Downside, of course, is that they will always open in a webbrowser, even if the default applications for the given file type is something else. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 391131] New: Dragon player crash playing mp4
https://bugs.kde.org/show_bug.cgi?id=391131 Bug ID: 391131 Summary: Dragon player crash playing mp4 Product: dragonplayer Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: sit...@kde.org Reporter: argona...@gmail.com CC: myr...@kde.org Target Milestone: --- Application: dragon (17.04.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.114-42-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: playing a mp4 file copied from my samsung phone to my Harddrive (NTFS) The crash can be reproduced sometimes. -- Backtrace: Application: Dragon Player (dragon), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5ec2469900 (LWP 22661))] Thread 2 (Thread 0x7f5ea69f2700 (LWP 22663)): #0 0x7f5ebd7cf30d in poll () at /lib64/libc.so.6 #1 0x7f5eb9f5f314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5eb9f5f42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5ebe3e51ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f5ebe392bfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5ebe1cdf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f5ebe7fa295 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f5ebe1d2a29 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f5ebaf1b724 in start_thread () at /lib64/libpthread.so.0 #9 0x7f5ebd7d7e8d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f5ec2469900 (LWP 22661)): [KCrash Handler] #6 0x7f5ebd71ff67 in raise () at /lib64/libc.so.6 #7 0x7f5ebd72133a in abort () at /lib64/libc.so.6 #8 0x7f5eb65f229d in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #9 0x7f5eb65f2ca3 in pa_fdsem_after_poll () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #10 0x7f5eb660a86d in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #11 0x7f5eba47cba7 in () at /usr/lib64/libpulse-mainloop-glib.so.0 #12 0x7f5eb9f5f134 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #13 0x7f5eb9f5f388 in () at /usr/lib64/libglib-2.0.so.0 #14 0x7f5eb9f5f42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #15 0x7f5ebe3e518c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #16 0x7f5ebe392bfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #17 0x7f5ebe39aae6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #18 0x0041c091 in () #19 0x7f5ebd70b725 in __libc_start_main () at /lib64/libc.so.6 #20 0x0041c1c9 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350944] Clicking on systray icon yields unpredictable result
https://bugs.kde.org/show_bug.cgi?id=350944 --- Comment #6 from Alexander Mentyu --- Although results in my previous comment may be due to Focus stealing prevention setting set to 'Medium' -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 390020] Latte dock crash when closing settings (Wayland)
https://bugs.kde.org/show_bug.cgi?id=390020 --- Comment #4 from Michail Vourlakos --- I just checked this... In my system I dont get any crash when closing config windows... I get a crash when closing Latte from Quit button is that the case? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 390017] [wayland] - Latte panel on top edge shows a centered transparent box after login
https://bugs.kde.org/show_bug.cgi?id=390017 --- Comment #6 from Michail Vourlakos --- can you still reproduce this? I tested in wayland and I dont have such issue... -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391130] New: Sometimes an arrow appears before screenshot loading is completed
https://bugs.kde.org/show_bug.cgi?id=391130 Bug ID: 391130 Summary: Sometimes an arrow appears before screenshot loading is completed Product: Discover Version: 5.12.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 111031 --> https://bugs.kde.org/attachment.cgi?id=111031&action=edit demonstration See screenshot taken on neon dev unstable. Mainly flatpak apps are affected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #56 from Alexander Schlarb --- That's a typo, the actual command had been issued with `QSG_RENDER_LOOP=basic`. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 381028] Missing path separator when backing up from scanned directory
https://bugs.kde.org/show_bug.cgi?id=381028 Elvis Angelaccio changed: What|Removed |Added Latest Commit|https://commits.kde.org/fil |https://cgit.kde.org/fileli |elight/4f8d281aad8e8390fb8e |ght.git/commit/?id=c353bb21 |6044da6a8bb0abb0195c|f2b5d56692ddafb673a66a5f49b ||b272c -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 381028] Missing path separator when backing up from scanned directory
https://bugs.kde.org/show_bug.cgi?id=381028 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/fil ||elight/4f8d281aad8e8390fb8e ||6044da6a8bb0abb0195c CC||elvis.angelac...@kde.org Version Fixed In||17.12.3 --- Comment #6 from Elvis Angelaccio --- Should be fixed by https://commits.kde.org/filelight/4f8d281aad8e8390fb8e6044da6a8bb0abb0195c -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 308351] Cannot run MountMan from menu
https://bugs.kde.org/show_bug.cgi?id=308351 Martin Kostolný changed: What|Removed |Added Assignee|m...@fork.pl |clearmar...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 308351] Cannot run MountMan from menu
https://bugs.kde.org/show_bug.cgi?id=308351 Martin Kostolný changed: What|Removed |Added CC||clearmar...@zoho.com --- Comment #2 from Martin Kostolný --- I like Nikita's proposal. This seems easy, I can do that. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391109] Powerdevil crash on wakup from suspend to ram in dock with wayland
https://bugs.kde.org/show_bug.cgi?id=391109 Christoph Feck changed: What|Removed |Added Product|kde |Powerdevil Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391129] Network Manager hides VPN connections on each suspend/wakeup
https://bugs.kde.org/show_bug.cgi?id=391129 --- Comment #1 from Dan Duris --- Importance is minor, basically a UX glitch, I am not sure why it switched to normal. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391109] Powerdevil crash on wakup from suspend to ram in dock with wayland
https://bugs.kde.org/show_bug.cgi?id=391109 Christoph Feck changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391102] KDE crashes after laptop suspend
https://bugs.kde.org/show_bug.cgi?id=391102 Christoph Feck changed: What|Removed |Added Component|general |general Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Product|kde |Powerdevil -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 391129] New: Network Manager hides VPN connections on each suspend/wakeup
https://bugs.kde.org/show_bug.cgi?id=391129 Bug ID: 391129 Summary: Network Manager hides VPN connections on each suspend/wakeup Product: plasma-nm Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: kdeb...@staznosti.sk Target Milestone: --- Regularly used VPN connections used to be easily accessbile via left-click on the applet and scrolling down. Now they are being hidden on each computer wakeup and one has to right click -> Configure network connection and connect using that popup dialog. One I connect through this dialog, I can close it and VPN connections are suddenly shown in the available connections in the applet among wifi and bluetooth networks. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391102] KDE crashes after laptop suspend
https://bugs.kde.org/show_bug.cgi?id=391102 Christoph Feck changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366284] Compositor crashes after using dashboard until icon in systray is closed
https://bugs.kde.org/show_bug.cgi?id=366284 Alexander Mentyu changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Alexander Mentyu --- No, thanks for your feedback -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391082] Menu Bar is landing on the wrong monitor. Primary monitor not defined.
https://bugs.kde.org/show_bug.cgi?id=391082 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391084] Unclickable dead zone to the left of the application menu button (regularly impeding user).
https://bugs.kde.org/show_bug.cgi?id=391084 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- Turn off your KWin left touch screen edge, which is causing this. See the duplicate big for details. *** This bug has been marked as a duplicate of bug 387775 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387775] KWin touch screen edge creates a 1 pixel dead zone on that edge that doesn't accept mouse clicks outside of full-screen mode
https://bugs.kde.org/show_bug.cgi?id=387775 Nate Graham changed: What|Removed |Added CC||bugs.kde@boonhead.nl --- Comment #13 from Nate Graham --- *** Bug 391084 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kjobwidgets] [Bug 353462] Dolphin crashes trying to rename a file with iso15 filename
https://bugs.kde.org/show_bug.cgi?id=353462 Elvis Angelaccio changed: What|Removed |Added CC||luca.tagliaco...@gmail.com --- Comment #26 from Elvis Angelaccio --- *** Bug 391096 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391099] Memory leak with NVIDIA 390.25
https://bugs.kde.org/show_bug.cgi?id=391099 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391096] When connecting to a Samba share Dolphin crashes
https://bugs.kde.org/show_bug.cgi?id=391096 Elvis Angelaccio changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Elvis Angelaccio --- *** This bug has been marked as a duplicate of bug 353462 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366284] Compositor crashes after using dashboard until icon in systray is closed
https://bugs.kde.org/show_bug.cgi?id=366284 --- Comment #8 from Hugo Rens --- (In reply to Alexander Mentyu from comment #7) > @Hugo Rens is this bug still relevant for you after updates? Sorry for my lack of feedback, I didn't actually encountered the bug after a few updates (as far as I can remember) and I'm afraid I can't tell you exactly what update solved the issue. So no, the bug isn't relevant for me anymore. Can I (and should I) do something to close/delete the issue ? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391126] Dscover does not list apps from flathub in settings
https://bugs.kde.org/show_bug.cgi?id=391126 Nate Graham changed: What|Removed |Added CC||n...@kde.org Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Nate Graham --- Yep, this recently regressed for me too in git master. I kept forgetting to report it, so thanks, Dr Chapatin! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391128] New: Process name change isn’t reflected in tabbar after using exec
https://bugs.kde.org/show_bug.cgi?id=391128 Bug ID: 391128 Summary: Process name change isn’t reflected in tabbar after using exec Product: konsole Version: 17.12.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: pe...@hack-libre.org Target Milestone: --- When using exec in current shell, the last process name is still reflected in the tabbar. For example, I use a `~/.bashrc` with `exec fish` so that launching Bash in interactive mode is replaced with fish (because fish as a default shell breaks e.g. Plasma). In this case, Konsole reports `bash` as the current process. Note that when launching e.g. htop, it reports correctly the current process name, but when returning to the shell it still displays the wrong name (bash in my case). -- You are receiving this mail because: You are watching all bug changes.
