[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #48 from Bernd Steinhauser--- (In reply to cherenz from comment #45) > (In reply to Bernd Steinhauser from comment #44) > > This is getting repetitive. The bug is not fixed by Qt 5.6, it's not fixed > > by KF5 5.20 and neither Plasma 5.5.95. > > > > If you don't see, you're lucky (congrats), but the bug is still there, as > > pointed out above. > > However, it is interesting to see that some users seem not to be affected > anymore. Right? Depends. There could be multiple issues. I too noticed, that the panel movement seems to be a bit more stable, but it does still switch them around nevertheless. Especially, I still get the effect that two panels from two different screens end up on exactly the same screen, which in my opinion makes no sense. I could understand if screens are swapped, but this is something else. In the end, there could be a lot of reasons why some people don't see it anymore and others still do. Configuration, screen setup, version of software XY etc. I tried with Qt 5.6 (with those mentioned 3 patches to QtDBus applied), with Plasma 5.6 on KF 5.20 with a clean plasma app config and I can still reproduce it, but as Nakato mentioned, it seems to be *a bit* more stable. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354688] Can't remove file File Association in System Settings
https://bugs.kde.org/show_bug.cgi?id=354688 Storm Engineerchanged: What|Removed |Added CC||hewa...@gmail.com --- Comment #2 from Storm Engineer --- I'm plagued by this bug for a few weeks now (at least) on Arch Linux and KDE 5 - JPG files for whatever reason got associated with Krita and this cannot be changed or removed. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 360755] New: Change of album artist field alone in single mp3 file has no impact
https://bugs.kde.org/show_bug.cgi?id=360755 Bug ID: 360755 Summary: Change of album artist field alone in single mp3 file has no impact Product: amarok Version: 2.8.0 Platform: Ubuntu Packages URL: http://imgur.com/6EBFmmF OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Metadata Editing and Reading Assignee: amarok-bugs-d...@kde.org Reporter: climat...@gmail.com CC: 123k...@gmail.com I use amarok v. 2.8.0 compiled on Sep 25 2013, with Ubuntu 14.04 LTS, in a french environment I have an mp3 version of a chinese album with the metadata below. _ titre/title : 怕 artiste/artist : 陳冠希 - Edison compositeur/composer : empty artiste de l'album/album artist: Edison album: Please steal this album Genre: Pop Année/year: 2004 numéro de la piste/track number: 6 numéro du disque/disc number: 1 battements par minutes/beats per minutes: empty commentaire/comment: 0 track location: /media/ferelden/musique5/gr52/06 怕.mp3 no lyrics/no cover album _ I open the metadata editor for this single file I copy the artist : "陳冠希 - Edison" and replace the field album artist with "陳冠希 - Edison" The "save and close" button becomes available. I click on it. I don't modify any other fields. I see absolutely no change to my playlist ordering by Album, I which I have first 5 tracks for the album artist "Edison", then 10 tracks for the album artist "陳冠希 - Edison". I expect the track to move down and meet the other tracks for the album artist "陳冠希 - Edison". I delete my playlist and my search for the album name. I update collection in tools/"Mettre à jour ma collection" (4th option out of 5) I search again for the album, and drag all my tracks in the empty playlist panel. The track "怕" is still with the first 5 songs that have the album artist "Edison" When I open the metadata editor, no changes were made to the song. The album artist is still "Edison". Workaround: I add a space (" ") at the end of track name and change the album artist field. I click on button"save and close". Hourray : the file is now with the tracks that have the album artist "陳冠希 - Edison" When I open the metadata editor for the file, the field has the wanted value. Don't forget to revert the track name to its initial value. Reproducible: Always Steps to Reproduce: 1. I open the metadata editor for a single file 2. I copy the artist field and replace the field album artist with the artist. I don't modify any other fields. 3. I click on the "save and close" button. 4. Absolutely no change 5. I open the metadata editor: no changes were made to the song. The album artist is still "Edison". Actual Results: The track keeps its previous value for "album artist" Expected Results: The track's album artist should have been changed and saved. The ordering by album should have been updated (because the two albums of the tracklist have the same title and different album artists). All this happens correctly if the title is modified at the same time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #47 from Nakato--- I've pulled qt5.6 down from Arch's testing repo, and it's not fixed, but it's made a big difference on my system. For me the bug is now presenting itself differently. Previously I could always reproduce the bug, now it's only most of the time, sometimes it does the right thing. Though unlike previously I got two segfaults out of about 15 disconnect and reconnects, but I wasn't restarting plasmashell every time this time as it was working. DrKonki ate the dumps though, I dismissed the window quickly expecting the details to go via systemd-coredump. The panel was no-longer always on the wrong screen, sometimes it was on the correct screen but offset by ~ the old monitors horizontal resolution. Additionally full screen apps do not seem to ignore that the panel is there on the screen it lands on, even when halfway hanging off the screen; previously they would overlay under the panel every time. While a different bug, I'll note that with qt5.6 I no-longer lose Konsole and Kate windows on unplug. The apps would remain running, but I could no-longer access them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358885] plasmashell crashed
https://bugs.kde.org/show_bug.cgi?id=358885 --- Comment #10 from Kenneth Burk--- Thanks for you reply. I don't have any technical knowledge and don't know what you mean. On Thursday, March 17, 2016 10:46 AM, Christoph Feck via KDE Bugzilla wrote: https://bugs.kde.org/show_bug.cgi?id=358885 Christoph Feck changed: What |Removed |Added Resolution|BACKTRACE |--- Assignee|l.lu...@kde.org |k...@davidedmundson.co.uk Product|kde |plasmashell Summary|kde crashed |plasmashell crashed Component|clipboard |general Target Milestone|--- |1.0 Status|NEEDSINFO |UNCONFIRMED CC| |bhus...@gmail.com, | |plasma-b...@kde.org Version|unspecified |5.4.2 --- Comment #9 from Christoph Feck --- Thanks for the backtrace. The crash happens in plasmashell. If possible, please try with Qt 5.6, as this crash looks related to QML. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 360639] New: Plasma just crashed after trying to add a Folder widget
https://bugs.kde.org/show_bug.cgi?id=360639 Bug ID: 360639 Summary: Plasma just crashed after trying to add a Folder widget Product: plasma4 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: juan97vic...@hotmail.com Application: plasma-desktop (4.11.20) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-35-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was trying to add the Folder widget on the lower panel, when I unintentionally moved the icon above the activity manager button (I think this is the name). It always crashes when I try to do this, or even when I try to put the widget between the task manager buttons (where stay the buttons for the windows I've opened). Sorry for my bad english (if it is). - Custom settings of the application: When using the default desktop activity on the KDE. -- Backtrace: Application: Shell da área de trabalho do Plasma (plasma-desktop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f575f663780 (LWP 2030))] Thread 8 (Thread 0x7f5731234700 (LWP 2041)): #0 0x7f5759de58e9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f5759da3bca in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5759da3cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f575e2f20de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f575e2c3e6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f575e2c4165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f575e1c10bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f575e2a5783 in () at /usr/lib64/libQtCore.so.4 #8 0x7f575e1c379f in () at /usr/lib64/libQtCore.so.4 #9 0x7f575df2d0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f575cc9900d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f572ae64700 (LWP 2175)): #0 0x7f575df3103f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f57507a48cb in () at /usr/lib64/libQtScript.so.4 #2 0x7f57507a4909 in () at /usr/lib64/libQtScript.so.4 #3 0x7f575df2d0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f575cc9900d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f572b792700 (LWP 9816)): #0 0x7f575df3103f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f575e1c3c86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f574f9fb6fc in () at /usr/lib64/libthreadweaver.so.4 #3 0x7f574f9fe193 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7f574f9fceaf in ThreadWeaver::Thread::run() () at /usr/lib64/libthreadweaver.so.4 #5 0x7f575e1c379f in () at /usr/lib64/libQtCore.so.4 #6 0x7f575df2d0a4 in start_thread () at /lib64/libpthread.so.0 #7 0x7f575cc9900d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f573a5f2700 (LWP 9817)): #0 0x7f575df3103f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f575e1c3c86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f574f9fb6fc in () at /usr/lib64/libthreadweaver.so.4 #3 0x7f574f9fe193 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7f574f9fceaf in ThreadWeaver::Thread::run() () at /usr/lib64/libthreadweaver.so.4 #5 0x7f575e1c379f in () at /usr/lib64/libQtCore.so.4 #6 0x7f575df2d0a4 in start_thread () at /lib64/libpthread.so.0 #7 0x7f575cc9900d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f5739df1700 (LWP 9818)): #0 0x7f575df3103f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f575e1c3c86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f574f9fb6fc in () at /usr/lib64/libthreadweaver.so.4 #3 0x7f574f9fe193 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7f574f9fceaf in ThreadWeaver::Thread::run() () at /usr/lib64/libthreadweaver.so.4 #5 0x7f575e1c379f in () at /usr/lib64/libQtCore.so.4 #6 0x7f575df2d0a4 in start_thread () at /lib64/libpthread.so.0 #7 0x7f575cc9900d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f57395f0700 (LWP 9819)): #0 0x7f575df3103f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f575e1c3c86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f574f9fb6fc in () at /usr/lib64/libthreadweaver.so.4 #3 0x7f574f9fe193 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7f574f9fceaf
[plasmashell] [Bug 357367] Desktop Settings -> Mouse Actions -> Vertical Scroll set to Application Launcher does not work
https://bugs.kde.org/show_bug.cgi?id=357367 Janetchanged: What|Removed |Added CC||bugzi...@kerridis.de --- Comment #3 from Janet --- It also does not work if you asign the application menu to left mouse button (Netrunner 17, Plasma 5.5). I can confirm that it indeed does work mit middle mouse button - but I need the middle mouse button for pasting. And to use the mouse acitons to start the application menu alas is the only way to get the classic menu, as it alas is no alternative for the application menu in the panel anymore :(. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360707] KDevelop crashes during parsing a project when it is compiled with GCC 6.0
https://bugs.kde.org/show_bug.cgi?id=360707 Kevin Funkchanged: What|Removed |Added Keywords||release_blocker Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 360613] New: 15.13.0 git master - when removing a title clip from the Project Bin - and it's also in the timeline - Kdenlive doesn't remove the affine transition
https://bugs.kde.org/show_bug.cgi?id=360613 Bug ID: 360613 Summary: 15.13.0 git master - when removing a title clip from the Project Bin - and it's also in the timeline - Kdenlive doesn't remove the affine transition Product: kdenlive Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jesse.dub...@gmail.com When I remove a title clip from the project bin after it's been inserted into the timeline, the title clip removes from the timeline just fine, but the affine transition under it remains. Reproducible: Always Steps to Reproduce: 1. Create a new title clip 2. Insert it into the timeline 3. Go to the Project Bin, and delete/remove the title clip Actual Results: Affine transition remains in timeline Expected Results: Affine transition should be removed from timeline along with the title clip. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 259678] Partitionmanager should not require root privileges to start.
https://bugs.kde.org/show_bug.cgi?id=259678 --- Comment #10 from Andrius Štikonas--- (In reply to Martin Gräßlin from comment #9) > Please note that running an application as root on X11 means that your > system is potentially instantly owned. I wrote a test case for such a > situation recently, more information at > https://marc.info/?l=kfm-devel=145192452218315=2 > > You can be certain that also partitionmanager can be exploited that way. > Please disallow root access and switch to polkit ASAP. This is not a > wishlish, this is in fact a severe security vulnerability. Dear Martin, I am not sure though whether polkit would fix that exploit path. Kate or Dolphin are usually used as a normal user and don't need root unless something very specific is done. On the other hand, KPM needs root for everything: detection of partitions, ALL write operations, etc... It often needs full write access to block devices as files anyway, so it's not clear whether polkit would be able to attain any finer granularity and prevent that security issue. So that exploit on any write operation with polkit'ed KPM would still be able to take over and delete all partitions... Or do some other nasty stuff. After all, KPM is system software to mess up with hard disks. Clearly we need to move to Wayland ASAP which is getting closer thanks to your effort... Of course polkit would improve some other aspects, like correct fonts and theme but the amount of work required here would be very non-trivial. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360698] Inform user that they must select a display in order to change its settings
https://bugs.kde.org/show_bug.cgi?id=360698 Kai Uwe Broulikchanged: What|Removed |Added CC||k...@privat.broulik.de Flags||Usability? --- Comment #2 from Kai Uwe Broulik --- I think the primary/internal screen should be pre-selected. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 360664] Oxygen5 Icon Theme erroneously inherits Breeze not hicolor
https://bugs.kde.org/show_bug.cgi?id=360664 Christoph Feckchanged: What|Removed |Added Assignee|cf...@kde.org |n...@oxygen-icons.org Component|general |icons Product|frameworks-kiconthemes |Oxygen CC||cf...@kde.org Version|5.19.0 |5.5.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360655] New: Plasma did not start
https://bugs.kde.org/show_bug.cgi?id=360655 Bug ID: 360655 Summary: Plasma did not start Product: plasmashell Version: 5.5.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: g.gumicsi...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Reboot my computer and then I try to login my workspace. Everything is working but Plasma5 is not. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x2b08f0a0c5c0 (LWP 2180))] Thread 8 (Thread 0x2b0907bf0700 (LWP 2185)): #0 0x2b08f7266bbd in poll () at /lib64/libc.so.6 #1 0x2b08f238f422 in () at /usr/lib64/libxcb.so.1 #2 0x2b08f239100f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x2b09050073c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x2b08f686332f in () at /usr/lib64/libQt5Core.so.5 #5 0x2b08f7a3f0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x2b08f726efed in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x2b090f4c6700 (LWP 2192)): #0 0x2b08f685bccf in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5 #1 0x2b08f6a95cc5 in () at /usr/lib64/libQt5Core.so.5 #2 0x2b08faafc4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x2b08faafcd80 in () at /usr/lib64/libglib-2.0.so.0 #4 0x2b08faafcf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x2b08f6a95d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x2b08f6a3cd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x2b08f685e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x2b08f3a66df8 in () at /usr/lib64/libQt5Qml.so.5 #9 0x2b08f686332f in () at /usr/lib64/libQt5Core.so.5 #10 0x2b08f7a3f0a4 in start_thread () at /lib64/libpthread.so.0 #11 0x2b08f726efed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x2b091c60d700 (LWP 2193)): #0 0x2b08f7266bbd in poll () at /lib64/libc.so.6 #1 0x2b08faafce64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x2b08faafcf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x2b08f6a95d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x2b08f6a3cd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x2b08f685e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x2b08f3a66df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x2b08f686332f in () at /usr/lib64/libQt5Core.so.5 #8 0x2b08f7a3f0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x2b08f726efed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x2b091d8c4700 (LWP 2194)): #0 0x2b08faafa1d7 in () at /usr/lib64/libglib-2.0.so.0 #1 0x2b08faafc44b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x2b08faafcd80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x2b08faafcf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x2b08f6a95d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x2b08f6a3cd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x2b08f685e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x2b08f3a66df8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x2b08f686332f in () at /usr/lib64/libQt5Core.so.5 #9 0x2b08f7a3f0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x2b08f726efed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x2b091ec40700 (LWP 2195)): #0 0x2b08f7a4303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x2b08f117c86b in () at /usr/lib64/libQt5Script.so.5 #2 0x2b08f117c899 in () at /usr/lib64/libQt5Script.so.5 #3 0x2b08f7a3f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x2b08f726efed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x2b09a9911700 (LWP 2197)): #0 0x2b08f7262c8d in read () at /lib64/libc.so.6 #1 0x2b08ff0ac073 in () at /usr/lib64/tls/libnvidia-tls.so.361.28 #2 0x2b08fab3db60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x2b08faafc999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x2b08faafcdf8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x2b08faafcf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x2b08f6a95d8b in QEventDispatcherGlib::processEvents(QFlags) () at
[dolphin] [Bug 259382] Make clicking the current folder in places list reset filter bar
https://bugs.kde.org/show_bug.cgi?id=259382 Kai Uwe Broulikchanged: What|Removed |Added Flags||Usability? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360700] New: Disable "Unify outputs" when there is only one display
https://bugs.kde.org/show_bug.cgi?id=360700 Bug ID: 360700 Summary: Disable "Unify outputs" when there is only one display Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: psychon...@nothingisreal.com The "Display Configuration" section of the "Display and Monitor" module contains a button labelled "Unify outputs". This button is always active, but from what I can tell it is effective only when there is more than one display. I suggest that the button should be deactivated whenever there is only one display. I am using System Settings 4.11.20 on KDE 4.14.9 as packaged by openSUSE 13.2. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 345094] [WACOM INTUOS] The eraser preset randomly changes to a brush
https://bugs.kde.org/show_bug.cgi?id=345094 Storm Engineerchanged: What|Removed |Added CC||hewa...@gmail.com --- Comment #5 from Storm Engineer --- I may have this same issue with my Intuos Pen (Arch Linux + KDE): I use the eraser end of the stylus a lot, and sometimes rarely it will have Eraser mode disabled and I have to either press E or click the "reset brush preset" button to fix it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360719] Secondary user actions popup remains visible
https://bugs.kde.org/show_bug.cgi?id=360719 Viorel-Cătălin Răpițeanuchanged: What|Removed |Added CC||rapiteanu.cata...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 360433] konsole crashes when the window is closed
https://bugs.kde.org/show_bug.cgi?id=360433 Torinchanged: What|Removed |Added CC||torin.cben...@googlemail.co ||m --- Comment #1 from Torin --- I am getting the same issue running on Arch Linux 64-bit as a VirtualBox guest. Konsole crashes upon exit, and when I close the crash handler, the crash handler (drkonqi) crashes with the same error. All Qt applications appear to crash in the same way. When I shut the virtual machine down, KDE reports a cascade of similar errors. The issue has also been reported here: https://forum.manjaro.org/index.php?topic=32066.0 A sample backtrace (incomplete - I know) is below. Application: drkonqi (drkonqi), signal: Floating point exception Using host libthread_db library "/usr/lib/libthread_db.so.1". [KCrash Handler] #5 0x7fd92a7fbc19 in pthread_barrier_destroy () from /usr/lib/libpthread.so.0 #6 0x7fd915a2796f in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #7 0x7fd915a33441 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #8 0x7fd9156d254f in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #9 0x7fd9156d25f5 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #10 0x7fd9156d0a2f in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #11 0x7fd929523522 in ?? () from /usr/lib/libGL.so.1 #12 0x7fd9294ff506 in ?? () from /usr/lib/libGL.so.1 #13 0x7fd9294ff589 in ?? () from /usr/lib/libGL.so.1 #14 0x7fd9294ff6de in ?? () from /usr/lib/libGL.so.1 #15 0x7fd92af36c52 in XCloseDisplay () from /usr/lib/libX11.so.6 #16 0x7fd921b36dd6 in QXcbConnection::~QXcbConnection() () from /usr/lib/libQt5XcbQpa.so.5 #17 0x7fd921b37139 in QXcbConnection::~QXcbConnection() () from /usr/lib/libQt5XcbQpa.so.5 #18 0x7fd921b38bd6 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/libQt5XcbQpa.so.5 #19 0x7fd921b38ce9 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/libQt5XcbQpa.so.5 #20 0x7fd92cd6a983 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () from /usr/lib/libQt5Gui.so.5 #21 0x7fd92d321029 in QApplicationPrivate::~QApplicationPrivate() () from /usr/lib/libQt5Widgets.so.5 #22 0x7fd92ca6a408 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5 #23 0x7fd92d322e19 in QApplication::~QApplication() () from /usr/lib/libQt5Widgets.so.5 #24 0x0043a58d in main () -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 360754] New: krunner crash when attempting to start konsole with alt-F2
https://bugs.kde.org/show_bug.cgi?id=360754 Bug ID: 360754 Summary: krunner crash when attempting to start konsole with alt-F2 Product: krunner Version: 5.5.4 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: arthur.ma...@internode.on.net Application: krunner (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.5.0+ x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: when starting KDE plasma for the first time after a reboot, krunner crashed when attempting to start konsole with alt-F2 The crash can be reproduced sometimes. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f29b63b87c0 (LWP 4740))] Thread 12 (Thread 0x7f29b5cf6700 (LWP 4753)): #0 0x0030004dfe4d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00300340a382 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7f29b5cf5d00) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 0x00300340a382 in _xcb_conn_wait (c=c@entry=0x859470, cond=cond@entry=0x8594b0, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:459 #3 0x00300340bff7 in xcb_wait_for_event (c=0x859470) at ../../src/xcb_in.c:693 #4 0x7f29b6155789 in QXcbEventReader::run() (this=0x86c4c0) at qxcbconnection.cpp:1230 #5 0x0030180a57fe in QThreadPrivate::start(void*) (arg=0x86c4c0) at thread/qthread_unix.cpp:331 #6 0x003000c07454 in start_thread (arg=0x7f29b5cf6700) at pthread_create.c:334 #7 0x0030004e8edd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f29acd87700 (LWP 4799)): #0 0x003000c0d04f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f29af9b3c43 in radeon_drm_cs_emit_ioctl (mtx=0x950280, cond=0x9502a8) at ../../../../../../../include/c11/threads_posix.h:159 #2 0x7f29af9b3c43 in radeon_drm_cs_emit_ioctl (sema=0x950280) at ../../../../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 0x7f29af9b3c43 in radeon_drm_cs_emit_ioctl (param=param@entry=0x94ff30) at ../../../../../../../src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:653 #4 0x7f29af9b3397 in impl_thrd_routine (p=) at ../../../../../../../include/c11/threads_posix.h:87 #5 0x003000c07454 in start_thread (arg=0x7f29acd87700) at pthread_create.c:334 #6 0x0030004e8edd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f29ab375700 (LWP 4804)): #0 0x00300448e895 in g_mutex_lock (mutex=mutex@entry=0x7f29a4000990) at /build/glib2.0-2.46.2/./glib/gthread-posix.c:1338 #1 0x003004449981 in g_main_context_query (context=context@entry=0x7f29a4000990, max_priority=2147483647, timeout=timeout@entry=0x7f29ab374cb4, fds=fds@entry=0x7f29a4003070, n_fds=n_fds@entry=1) at /build/glib2.0-2.46.2/./glib/gmain.c:3544 #2 0x00300444a147 in g_main_context_iterate (context=context@entry=0x7f29a4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-2.46.2/./glib/gmain.c:3822 #3 0x00300444a2dc in g_main_context_iteration (context=0x7f29a4000990, may_block=may_block@entry=1) at /build/glib2.0-2.46.2/./glib/gmain.c:3901 #4 0x0030182dca5b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f29a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x003018283d6a in QEventLoop::exec(QFlags) (this=this@entry=0x7f29ab374de0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x0030180a0854 in QThread::exec() (this=) at thread/qthread.cpp:503 #7 0x0030406d5105 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x0030180a57fe in QThreadPrivate::start(void*) (arg=0xbf1e60) at thread/qthread_unix.cpp:331 #9 0x003000c07454 in start_thread (arg=0x7f29ab375700) at pthread_create.c:334 #10 0x0030004e8edd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f29a0f27700 (LWP 4961)): #0 0x003000c0d04f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x0030180a6a9b in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0xbc44a0) at thread/qwaitcondition_unix.cpp:136 #2 0x0030180a6a9b in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0xaefc60, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f29a917802b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*) (this=this@entry=0xb2ac90, th=) at ../../src/weaver.cpp:594
[konversation] [Bug 360709] Automatically joins on invitations
https://bugs.kde.org/show_bug.cgi?id=360709 Eli MacKenziechanged: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||argo...@gmail.com --- Comment #1 from Eli MacKenzie --- This means you have the channel invitation warning dialog disabled. Go to Configure Konversation… -> Notifications -> Warning Dialogs and enable it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360197] [WACOM CINTIQ] can't pick colors with tablet pen by hotkeying alt and left click
https://bugs.kde.org/show_bug.cgi?id=360197 Boudewijn Remptchanged: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- Summary|[UNKNOWN] can't pick colors |[WACOM CINTIQ] can't pick |with tablet pen by |colors with tablet pen by |hotkeying alt and left |hotkeying alt and left |click |click --- Comment #3 from Boudewijn Rempt --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #36 from Maciej Sitarz--- I read on some blog (one of KDE developers?) that most of the problems related to multi monitor handling can and are caused by bugs in Qt.I was waiting for new version of Qt. Qt 5.6 was released 2 days ago and I've just upgraded (just appeared in Archlinux testing repository). I made few (dis)connects of external LCD and it looks like everything is working fine when using Qt 5.6. Give it a go and confirm. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 351628] Akonadi DAV Resource does not sync all calendars on ownCloud any more
https://bugs.kde.org/show_bug.cgi?id=351628 somniumchanged: What|Removed |Added CC||stam...@stampernet.de --- Comment #17 from somnium --- I'm not quite sure, if this is the same problem, but my owncloud contacts and calendars are not shown in kontact etc. anymore. In the akonadi console the resources are present and "ready", so no obvious errors. But there is no entry in kontact. I'm using owncloud 9.0 and php7 on the server, and Arch linux with the KDE Applications 15.12.3 on the client side. The calenders and contacts are shown in android and ios, as well as thunderbird. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #43 from Bob Wya--- I'm running Gentoo - but now with: Qt 5.6.0 kde-frameworks 5.20.0 kde-plasma 5.5.95 Newly "minted" from the gcc factory. I can't reproduce the bug anymore!! Played a full screen game. Unplugged and re-plugged in an external (HDMI connected) monitor. My 2 bottom panels are restored to their original positions - in both instances. Previously they would both fly onto the external monitor and stick there... Yay!! All is right(ish) now :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360647] Plasma Crashes when Searching for Application to Launch
https://bugs.kde.org/show_bug.cgi?id=360647 Marco Martinchanged: What|Removed |Added Resolution|--- |DUPLICATE CC||notm...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 360648 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #37 from Bernd Steinhauser--- Nope, been using Qt 5.6 for 2-3 weeks now and it did not improve things. Neither the -rc, nor the release version. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 347602] Update Manager systray icon and info still reports pending updates after updates applied
https://bugs.kde.org/show_bug.cgi?id=347602 Aleix Polchanged: What|Removed |Added CC||ostrowski.mari...@gmail.com --- Comment #49 from Aleix Pol --- *** Bug 360118 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360683] Cannot deselect (un-highlight) a date in the Calendar popup
https://bugs.kde.org/show_bug.cgi?id=360683 --- Comment #1 from Abderrahman Najjar--- Created attachment 97955 --> https://bugs.kde.org/attachment.cgi?id=97955=edit Screenshot of Calendar popup with the previous day selected -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 Nakatochanged: What|Removed |Added CC||chronicli...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360601] Canvas doesn't update with OpenGL activated
https://bugs.kde.org/show_bug.cgi?id=360601 Dimichanged: What|Removed |Added CC||dimim...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 360604] The links in the update files are outdated
https://bugs.kde.org/show_bug.cgi?id=360604 Orgad Shanehchanged: What|Removed |Added CC||org...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 360624] New: Implement "Invert Filter" option
https://bugs.kde.org/show_bug.cgi?id=360624 Bug ID: 360624 Summary: Implement "Invert Filter" option Product: dolphin Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: bars: filter Assignee: dolphin-bugs-n...@kde.org Reporter: sowi...@dukun.de I love the filter bar, and it's one of Dolphin's features I miss immediately in other file browsers. As I often use this feature, I had many cases where I wished I had an invert-filter option, to only show the files where the filter did not match. Use case: For instance, I have a folder with all the files from a camera, containing not only *.jpg, but also various info-files, movies, sounds, …. It would be great to type ctrl+i and .jpg, then press an invert-filter-checkbox and only the non-jpeg-files are shown, so that I can ctrl+a these files and delete/move them. I suggest to add an 'Invert' checkbox after the filter bar, but a well documented pattern expression for inversion would also be fine (maybe a ! at the start of a pattern). I hope it is not to complex to be implemented and hope that it is useful for many more people. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #23 from Ben Cooksley--- Probably better would be to tweak the name to either lack the "via KDE Bugzilla" (simpler) or say "Anonymous via KDE Bugzilla" / "Unknown via KDE Bugzilla" when we don't know the name. In terms of changing the From address itself, that can't be done due to the previously mentioned DMARC issues. Doesn't exist with mailing lists as the authorised sender actually sent it. We attach our signature to mail that passes through KDE.org lists for legacy reasons - that setup predates the existence of DMARC. It doesn't harm (or help) things though. Comments? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 360661] New: Kontact crash when switching multipart mail to html view
https://bugs.kde.org/show_bug.cgi?id=360661 Bug ID: 360661 Summary: Kontact crash when switching multipart mail to html view Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kdeb...@munin-soft.de Application: kontact (5.1.2) Qt Version: 5.5.1 Operating System: Linux 4.4.3-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160307) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I had the text part of a mail open in the view pane. I selected the HTML part in teh structure view underneath and just hovered with the mouse over the link to switch to the view to HTML (not clicked yet) when Kontact crashed. I had Kontact open already some hours. After restart, the same sequence of actions coul dbe executed without the crash re-occuring. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fad8cbb8900 (LWP 2196))] Thread 24 (Thread 0x7fad6e721700 (LWP 2215)): #0 0x7fad8984449d in poll () at /lib64/libc.so.6 #1 0x7fad82fb8432 in () at /usr/lib64/libxcb.so.1 #2 0x7fad82fba007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fad7086fe29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fad8a14b94f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fad82b944a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fad8984cded in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fad673e9700 (LWP 2246)): #0 0x7fad82b9a07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fad873e62ab in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fad873e62e9 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fad82b944a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fad8984cded in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7fad222ea700 (LWP 2319)): #0 0x7fad823bc554 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fad8237924e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fad8237939c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fad8a37052b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fad8a31a61a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fad8a146b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fad8a14b94f in () at /usr/lib64/libQt5Core.so.5 #7 0x7fad82b944a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fad8984cded in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7fad1554e700 (LWP 2490)): #0 0x7fad82b9a07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fad870f4754 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fad87415131 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fad82b944a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fad8984cded in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7fad14d4d700 (LWP 2491)): #0 0x7fad82b9a07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fad870f5783 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fad87415131 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fad82b944a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fad8984cded in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7fad1454c700 (LWP 2492)): #0 0x7fad82b9a07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fad870f5783 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fad87415131 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fad82b944a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fad8984cded in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fad13d4b700 (LWP 2493)): #0 0x7fad82b9a07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fad870f5783 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fad87415131 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fad82b944a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fad8984cded in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7fad1354a700 (LWP 2494)): #0 0x7fad82b9a07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fad870f5783 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fad87415131 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fad82b944a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fad8984cded in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fad12d49700 (LWP 2495)): #0 0x7fad82b9a07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fad870f5783 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fad87415131 in () at
[plasmashell] [Bug 360575] Desktop crash on startup
https://bugs.kde.org/show_bug.cgi?id=360575 Marco Martinchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||notm...@gmail.com --- Comment #2 from Marco Martin --- *** This bug has been marked as a duplicate of bug 358565 *** -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #18 from Pali Rohár--- Please do something with this bug! Just having string "via KDE Bugzilla" in From header without any other information about sender/creator makes my work with bugzilla really hard. I --- as maintainer of Kopete IM client, which is part of KDE --- needs some working system, not something like this. I really do not want to take Kopete project out of this KDE system, but if you are not able to fix bug which is regression I would need to start thinking what to do with it. As I'm really unable to use such broken system. It is probably good that users can report Kopete bugs into KDE bugzilla, but really useless if those who want to fix them cannot easily use such system. Please thing about it! Anyway, I do not understand why you have problem with signing DKIM with @kde.org domain key as lot of emails are normally received by gmail into INBOX (not SPAM!) which has different DKIM key as domain specified in email address in From: header. So there is probably broken also something else... If you need some other assistance, I can help, but I really od not like this that nobody care about this my reported bug and there is just silence... -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 271152] splash screen has incorrect size
https://bugs.kde.org/show_bug.cgi?id=271152 --- Comment #5 from Peter Lewis--- This is fixed for me in 5.5.95 (at least). Thanks! However, I still get the bad behaviour on the lock screen. I suppose this is a separate bug...? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 41744] konsole lacks the option of showing Unicode characters with ambiguous width as FULLWIDTH or HALFWIDTH
https://bugs.kde.org/show_bug.cgi?id=41744 Arfrever Frehtes Taifersar Arahesischanged: What|Removed |Added CC||arfrever@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 347344] KInfoCenter crashes after click Energy Information
https://bugs.kde.org/show_bug.cgi?id=347344 Christoph Feckchanged: What|Removed |Added CC||miras199...@gmail.com --- Comment #20 from Christoph Feck --- *** Bug 360650 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360699] Font settings ignored with qt 5.6
https://bugs.kde.org/show_bug.cgi?id=360699 --- Comment #2 from beojan--- All decorations, but I was using Papirus Dark (Aurorae). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360595] Krita crashes when we cancel the save custom shortcut dialog box
https://bugs.kde.org/show_bug.cgi?id=360595 Quiraltachanged: What|Removed |Added CC||rjquira...@gmail.com --- Comment #3 from Quiralta --- I can confirm the same behaviour for both actions as Jumpei, also Scotts crash, Archlinux here, last appimage. As for the first described issue (changing the shortcuts) doesn't happens every single time, (maybe 8 out of ten, haven't counted though) but when doesn't crash, then the changes are simply ignored. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 212091] Configure phonon from command line
https://bugs.kde.org/show_bug.cgi?id=212091 --- Comment #20 from Joe--- (In reply to Marcelo Bossoni from comment #19) > Thanks for the script Joe > I'll probably need to change it to query xrandr instead, since I wan't to > route audio only when HDMI video is enabled, not just connected. Hack away! It's sufficiently hard-coded so that you have to modify it anyway. The main deal is that you know where to look for the interface which switches the audio. I would appreciate a copy of anything you get to work (off list). Especially if it ends up less hard-coded than my version. Of course, that's optional since it's GPL code. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 259382] Make clicking the current folder in places list reset filter bar
https://bugs.kde.org/show_bug.cgi?id=259382 sowi...@dukun.de changed: What|Removed |Added CC||sowi...@dukun.de --- Comment #5 from sowi...@dukun.de --- Its technically correct, but not intuitive. For instance by clicking the home-folder I would expect to get to a sane default, thus no filters selected, for what other reason would I click this button (regardless if, but especially when I already am inside). This is clearly only an edge case, but another step on the road towards perfection. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #22 from Pali Rohár--- Nicolás, thank you! Please at least do that. Anyway, I still do not understand, why problem is with Bugzilla and not with (KDE) mailing lists?? I see that KDE mailing lists servers set DKIM-Signature email header with "d=kde.org" value even if From: header contains @gmail.com domain. And such emails are normally received to gmail users into INBOX, not to spam. So again, why bugzilla do not set correct From: and Sender: headers? If problem would be really with mismatching domain in (d=) in DKIM-Signature header and domain (after @...) in From header, then also emails sent by mailing lists would go to spam... Also I see others (non KDE) emails with different domain in DKIM-Signature and From. And they also go to gmail INBOX, not spam. So I would suspect, that problem is not in DKIM header/signature, but on different place... Please can you look at it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX
https://bugs.kde.org/show_bug.cgi?id=360033 --- Comment #37 from m00nraker--- Ok, vanilla, only __invite_fbo_red.diff applied: pass 1-4 false kwin_x11 --replace QXcbConnection: XCB error: 8 (BadMatch), sequence: 806, resource id: 67108869, major code: 42 (SetInputFocus), minor code: 0 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce Go 7950 GTX/PCIe/SSE2 OpenGL version string: 2.1.2 NVIDIA 304.131 OpenGL shading language version string: 1.20 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 304.131 GPU class: NV40/G70 OpenGL version: 2.1.2 GLSL version: 1.20 X server version: 1.17.2 Linux kernel version: 4.1.15 Requires strict binding:no GLSL shaders: limited Texture NPOT support: yes Virtual Machine:no Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) pass 1 false Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) pass 2 false Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) pass 3 false Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) pass 4 false Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 0, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0, 1, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.44882, 0.14882, 0.14882, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.50064, 0.80064, 0.50064, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.05054, 0.05054, 0.35054, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.3, 0, 0, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0.4, 0, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0, 0.5, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.3, 0.4, 0.5, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.134646, 0.044646, 0.044646, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.200256, 0.320256, 0.200256, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.02527, 0.02527, 0.17527, 0.6) Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.360172, 0.390172, 0.420172, 0.6) kwin_core: ShaderManager self test failed kwin_core: Failed to initialize compositing, compositing disabled QXcbConnection: XCB error: 3 (BadWindow), sequence: 912, resource id: 579, major code: 3 (GetWindowAttributes), minor code: 0 QXcbConnection: XCB error: 9 (BadDrawable), sequence: 913, resource id: 579, major code: 14 (GetGeometry), minor code: 0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 344192] Crash while trying to save a file as an already open file
https://bugs.kde.org/show_bug.cgi?id=344192 Kevin Funkchanged: What|Removed |Added Keywords||junior-jobs Target Milestone|--- |5.0.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360601] New: Canvas doesn't update with OpenGL activated
https://bugs.kde.org/show_bug.cgi?id=360601 Bug ID: 360601 Summary: Canvas doesn't update with OpenGL activated Product: krita Version: 3.0 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: dimim...@gmail.com Krita version: krita3-prealpha3-9694dac The canvas doesn't update when OpenGL is activated. It only shows the changes if I do something that forces it to redraw the canvas, like changing the windows size or activating wrap around mode. It's difficult to use Krita for animation without the OpenGL features. I also frequently use the wraparound mode, so deactivating OpenGL is a bad workaround. I'm on Windows 10 and my gpu is an Intel HD 3000. I tried using all the drivers available, from old ones to the latest and even unofficial ones. It doesn't make a difference. The last Krita version that behaved as expected was krita_2.9.10.1ae_beta_x64. Reproducible: Always Steps to Reproduce: 1.Activate OpenGL 2.try to draw on canvas Actual Results: Canvas doesn't update. Expected Results: Normal behavior. Windows 10 Intel HD 3000 Tried every driver available. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360621] plasmashell hangs when moving panel
https://bugs.kde.org/show_bug.cgi?id=360621 --- Comment #2 from Bernd Steinhauser--- Yes, all three patches were applied before building Qt 5.6.0. Does not matter for this one, though. This happens with and without the patches. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 360690] New: Konsole crashs everytime under VirtualBox Windows Host with 3D Acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=360690 Bug ID: 360690 Summary: Konsole crashs everytime under VirtualBox Windows Host with 3D Acceleration enabled Product: konsole Version: 15.12.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: tl_web...@outlook.com Application: konsole (15.12.2) Qt Version: 5.5.1 Operating System: Linux 4.4.3-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160307) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: - Konsole crashes everytime it's executed - Custom settings of the application: - No custom settings of the application. I run VirtualBox Windows Host and the crashes started after I enabled VirtualBox's 3D Acceleration. The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f514e3ff940 (LWP 3452))] Thread 7 (Thread 0x7f513891e700 (LWP 3453)): #0 0x7f514dd4d49d in poll () at /lib64/libc.so.6 #1 0x7f5145527432 in () at /usr/lib64/libxcb.so.1 #2 0x7f5145529007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f513a646e29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f514a15b94f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f51451034a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f514dd55ded in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f513037d700 (LWP 3457)): #0 0x7f514dd25fdd in nanosleep () at /lib64/libc.so.6 #1 0x7f5132228109 in RTThreadSleepNoLog () at /usr/lib64/dri/vboxvideo_dri.so #2 0x7f5132208237 in () at /usr/lib64/dri/vboxvideo_dri.so #3 0x7f5132229d1c in () at /usr/lib64/dri/vboxvideo_dri.so #4 0x7f5132237c90 in () at /usr/lib64/dri/vboxvideo_dri.so #5 0x7f51451034a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f514dd55ded in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f5130b7e700 (LWP 3458)): #0 0x7f514510907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f512b98ff03 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f512b98fd87 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f51451034a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f514dd55ded in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f512511d700 (LWP 3459)): #0 0x7f514510907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f512b98ff03 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f512b98fd87 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f51451034a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f514dd55ded in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f512491c700 (LWP 3460)): #0 0x7f514510907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f512b98ff03 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f512b98fd87 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f51451034a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f514dd55ded in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f512411b700 (LWP 3461)): #0 0x7f514510907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f512b98ff03 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f512b98fd87 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f51451034a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f514dd55ded in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f514e3ff940 (LWP 3452)): [KCrash Handler] #6 0x7f51339e6ab8 in () at /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #7 0x7f51339e6c8d in () at /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #8 0x7f513a662955 in QXcbWindow::create() () at /usr/lib64/libQt5XcbQpa.so.5 #9 0x7f513a64e721 in QXcbIntegration::createPlatformWindow(QWindow*) const () at /usr/lib64/libQt5XcbQpa.so.5 #10 0x7f514a877267 in QWindowPrivate::create(bool) () at /usr/lib64/libQt5Gui.so.5 #11 0x7f514b044c78 in QWidgetPrivate::create_sys(unsigned long long, bool, bool) () at /usr/lib64/libQt5Widgets.so.5 #12 0x7f514b045259 in QWidget::create(unsigned long long, bool, bool) () at /usr/lib64/libQt5Widgets.so.5 #13 0x7f514b04483b in QWidget::winId() const () at /usr/lib64/libQt5Widgets.so.5 #14 0x7f514d04fceb in KMainWindow::applyMainWindowSettings(KConfigGroup const&) () at /usr/lib64/libKF5XmlGui.so.5 #15 0x7f514d087082 in KXmlGuiWindow::applyMainWindowSettings(KConfigGroup const&) () at /usr/lib64/libKF5XmlGui.so.5 #16 0x7f514d05017b in KMainWindow::setAutoSaveSettings(QString const&, bool) () at /usr/lib64/libKF5XmlGui.so.5 #17 0x7f514e030126 in () at
[blogilo] [Bug 326244] Does not correctly handle images
https://bugs.kde.org/show_bug.cgi?id=326244 chrystelle.grangla...@gmail.com changed: What|Removed |Added CC||chrystelle.grangladen@gmail ||.com --- Comment #1 from chrystelle.grangla...@gmail.com --- I have the same problem. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 341122] Error message "failed to rescan"
https://bugs.kde.org/show_bug.cgi?id=341122 Aranjedeathchanged: What|Removed |Added CC||orangewi...@gmail.com --- Comment #6 from Aranjedeath --- I don't know what to do with this information, but I think it's related. New Network Manager 1.2 coming out soon, release candidate within the next two weeks. post on new wifi scanning https://blogs.gnome.org/dcbw/2016/01/18/networkmanager-1-2-has-better-wi-fi-scanning/ ubuntu bug for nm 1.2 https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1552424 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358771] Plasma crashed when changed the icon theme
https://bugs.kde.org/show_bug.cgi?id=358771 Marco Martinchanged: What|Removed |Added Resolution|--- |DUPLICATE CC||notm...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 358565 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360719] Secondary user actions popup remains visible
https://bugs.kde.org/show_bug.cgi?id=360719 --- Comment #3 from Viorel-Cătălin Răpițeanu--- Created attachment 97962 --> https://bugs.kde.org/attachment.cgi?id=97962=edit Kwin qdbus log from the machine using bumblebee (intel + nvidia) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360635] New: kde crash when connecting external monitor
https://bugs.kde.org/show_bug.cgi?id=360635 Bug ID: 360635 Summary: kde crash when connecting external monitor Product: plasmashell Version: 5.5.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: marco.bry...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.2.0-34-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: running: xrand --output VGA1 --auto xrand --output VGA1 --prefered but external monitor remain in sleep mode. Since last update I faced some problems connecting my external monitor. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f43053a1800 (LWP 1035))] Thread 8 (Thread 0x7f42f0758700 (LWP 1038)): #0 0x7f42ffaac88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f4303b7abd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f4303b7c74f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f42f28a17e9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f43001a2a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f42ff28e6aa in start_thread (arg=0x7f42f0758700) at pthread_create.c:333 #6 0x7f42ffab7e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f42edf4a700 (LWP 1055)): #0 0x7f42ffaa844d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f42fc8854e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f42fc841cd4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f42fc842190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f42fc8422fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f43003da50b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f430038150a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f430019dac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4302a4bc35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f43001a2a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f42ff28e6aa in start_thread (arg=0x7f42edf4a700) at pthread_create.c:333 #11 0x7f42ffab7e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f42de907700 (LWP 1083)): #0 0x7f42ffaac88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f42fc8421ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f42fc8422fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f43003da50b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f430038150a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f430019dac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4302a4bc35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f43001a2a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f42ff28e6aa in start_thread (arg=0x7f42de907700) at pthread_create.c:333 #9 0x7f42ffab7e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f42dcaac700 (LWP 1090)): #0 0x7f42ffaa844d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f42fc8854e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f42fc841cd4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f42fc842190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f42fc8422fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f43003da50b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f430038150a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f430019dac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4302a4bc35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f43001a2a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f42ff28e6aa in start_thread (arg=0x7f42dcaac700) at pthread_create.c:333 #11 0x7f42ffab7e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f42d6fbc700 (LWP 1137)): #0
[plasmashell] [Bug 353507] plasmashell uses too much CPU when copying/moving/deleting files
https://bugs.kde.org/show_bug.cgi?id=353507 --- Comment #4 from Abderrahman Najjar--- This is still an issue in the latest stable (5.5.5) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356064] Regression: Using a non-Breeze icon theme results in mixed non-Breeze + Breeze icons.
https://bugs.kde.org/show_bug.cgi?id=356064 Wolfgang Bauerchanged: What|Removed |Added CC||wba...@tmo.at --- Comment #7 from Wolfgang Bauer --- (In reply to opensuse.lietuviu.kalba from comment #3) > Please for non-Breeze themes respect specifications: > according > http://standards.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html > , > the default fallback icon theme must be "hicolor". > I.e. as fallback, please use /usr/share/icons/hicolor/ and /usr/share/pixmaps Actually the fallback is "hicolor". If you delete the corresponding breeze icon, the one from hicolor is taken then. It's "just" that "breeze" seems to be used as fallback additionally, and preferred over the real fallback, hicolor. But yes, still a bug (I suppose). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 360537] Keyboard Backlight endless loop when changed, only inside plasma session
https://bugs.kde.org/show_bug.cgi?id=360537 --- Comment #7 from Thomas Pfeiffer--- Oh okay, they do that directly? Fine, then. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360607] New: "Complementary colors" are not documented
https://bugs.kde.org/show_bug.cgi?id=360607 Bug ID: 360607 Summary: "Complementary colors" are not documented Product: systemsettings Version: 5.5.95 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_colors Assignee: mwoehlke.fl...@gmail.com Reporter: aspotas...@gmail.com CC: jpwhit...@kde.org There is no description for "Complementary colors" in the handbook. I don't understand what it means. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 334541] Authentication Error - Muon Update Manager (This operation cannot continue since proper authorization was not provided
https://bugs.kde.org/show_bug.cgi?id=334541 bk...@gnu.org changed: What|Removed |Added CC||bk...@gnu.org --- Comment #17 from bk...@gnu.org --- > # apt-get update > PackageKit is blocking zypper. This happens if you have an updater applet or > other software management application using PackageKit running. > Tell PackageKit to quit? [yes/no] (no): yes > PackageKit is still running (probably busy). > Try again? [yes/no] (no): no > System management is locked by the application with pid 2572 > (/usr/lib/packagekitd). > Close this application before trying again. I can confirm that here we are two years after the initial report and many people have this problem (including me). I have no idea what is triggering it since I was not trying to update anything until I tried to update the updater. There is no process running with "PackageKit" as its program. My KDE version is 5.5.4. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 360612] 15.13.0 git master - issues with the new gradient feature in Title Editor
https://bugs.kde.org/show_bug.cgi?id=360612 --- Comment #2 from Jean-Baptiste Mardelle--- Yes, that is a work in progress. I have submitted a patch to MLT that is still pending - hopefully should be merged in the next days - that makes it work correctly in the monitors / rendering. WIll let you know when the merge is done in MLT, would be interested by your feedback. It works quite nicely for me, I also added text shadow which was really missing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359707] Merging invisible layers unhides them
https://bugs.kde.org/show_bug.cgi?id=359707 Boudewijn Remptchanged: What|Removed |Added Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/krit |a/ded5b95703aa4edc0a9392376 |a/b57216a6556f72e54492331b9 |ebffaef36d0101b |e294a94b979bb9b --- Comment #3 from Boudewijn Rempt --- Git commit b57216a6556f72e54492331b9e294a94b979bb9b by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 16/03/2016 at 07:02. Pushed by rempt into branch 'rempt-osx-port'. Fix merging invisible layers They should be just deleted and not merged M +187 -34 libs/image/kis_layer_utils.cpp M +45 -0libs/image/kis_layer_utils.h M +2-1libs/ui/kis_layer_manager.cc M +18 -95 libs/ui/kis_node_juggler_compressed.cpp http://commits.kde.org/krita/b57216a6556f72e54492331b9e294a94b979bb9b -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 360615] 15.13.0 git master - Use "Shift+Left Click" to select multiple clips in timeline instead of "Ctrl+Left Click"?
https://bugs.kde.org/show_bug.cgi?id=360615 Jessechanged: What|Removed |Added CC||jesse.dub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 360654] Please add button to re-run search in files
https://bugs.kde.org/show_bug.cgi?id=360654 Aleix Polchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||aleix...@kde.org Ever confirmed|0 |1 --- Comment #1 from Aleix Pol --- +1, I'd like that too -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 360698] Inform user that they must select a display in order to change its settings
https://bugs.kde.org/show_bug.cgi?id=360698 Kai Uwe Broulikchanged: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #5 from Kai Uwe Broulik --- Works for me too on 5.6 -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 360619] New: Please add bug reporting to plasmathemeexplorer
https://bugs.kde.org/show_bug.cgi?id=360619 Bug ID: 360619 Summary: Please add bug reporting to plasmathemeexplorer Product: Plasma SDK Version: 5.5.95 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: plasmathemeexplorer Assignee: plasma-b...@kde.org Reporter: aspotas...@gmail.com CC: giorgos.tsiapalio...@kde.org Most KDE apps have Help -> Report Bug... menu item. "plasmathemeexplorer" should have it as well. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360683] Cannot deselect (un-highlight) a date in the Calendar popup
https://bugs.kde.org/show_bug.cgi?id=360683 Martin Klapetekchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Martin Klapetek --- Thanks for the report This certainly was possible, but must have gotten broken. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359508] Plasma crash after opening Audio Volume Settings via Tray
https://bugs.kde.org/show_bug.cgi?id=359508 --- Comment #2 from Simon--- Another duplicate https://bugs.kde.org/show_bug.cgi?id=358339 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 148550] allow a case sensitive sorting
https://bugs.kde.org/show_bug.cgi?id=148550 Emmanuel Pescostachanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/dolp ||hin/92c0ecde90f30061bef321f ||50fbea99616e852a7 Version Fixed In||16.04.0 Status|CONFIRMED |RESOLVED --- Comment #20 from Emmanuel Pescosta --- Git commit 92c0ecde90f30061bef321f50fbea99616e852a7 by Emmanuel Pescosta, on behalf of Arnav Dhamija. Committed on 16/03/2016 at 19:53. Pushed by emmanuelp into branch 'master'. Add case sensitive sorting mode Dolphin users can now choose between 3 different sorting modes: * natural sorting * case insensitive sorting * case sensitive sorting REVIEW: 126467 FIXED-IN: 16.04.0 M +26 -6src/kitemviews/kfileitemmodel.cpp M +6-1src/kitemviews/kfileitemmodel.h M +10 -5src/settings/dolphin_generalsettings.kcfg M +51 -8src/settings/general/behaviorsettingspage.cpp M +8-1src/settings/general/behaviorsettingspage.h http://commits.kde.org/dolphin/92c0ecde90f30061bef321f50fbea99616e852a7 -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 360685] New: Can't export drawn data as any picture format.
https://bugs.kde.org/show_bug.cgi?id=360685 Bug ID: 360685 Summary: Can't export drawn data as any picture format. Product: kmplot Version: 1.2.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: neko1...@gmail.com 1. push button " export" of file. 2. appear new window "export" 3. pull down filter. 4. appear menu window to select picture format. 4. read "all files supported" at top of menu window, but blanks for others. 5. push button "save", then tell "Don't support this file format" Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 259678] Partitionmanager should not require root privileges to start.
https://bugs.kde.org/show_bug.cgi?id=259678 --- Comment #11 from Martin Gräßlin--- (In reply to Andrius Štikonas from comment #10) > Clearly we need to move to Wayland ASAP which is getting closer thanks to > your effort... which will be just another reason to go for a polkit approach. Launching root-owned gui applications just doesn't work. I just tried it for the first time and all I got were error messages (and I also expected that). -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 360674] Post-daylight savings time, kalarm records alarms 1 hour later than it should
https://bugs.kde.org/show_bug.cgi?id=360674 --- Comment #2 from David Rosenstrauch--- Created attachment 97946 --> https://bugs.kde.org/attachment.cgi?id=97946=edit Work around the problem by setting "ignore time zone" Only when I set "ignore time zone" does the alarm get recorded - and alerted - at the correct time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359735] Intermittent, Unresponsive when running Krita
https://bugs.kde.org/show_bug.cgi?id=359735 --- Comment #6 from Boudewijn Rempt--- The 3.0 pre-alpha 3 does not need installing: just unzip the zip file, then if necessary, run the vcredist.exe (it's need if on starting Krita, a message box pops up claiming some microsoft dll is missing), and then double-click on the krita link. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360560] [HUION] setting pen second button as right mouse button won't work
https://bugs.kde.org/show_bug.cgi?id=360560 noxer...@gmail.com changed: What|Removed |Added CC||noxer...@gmail.com --- Comment #1 from noxer...@gmail.com --- I've tested this on the Huion 610pro in 2.9 and 3.0 pre-alpha, and the problem is still present for me as well. Neither of the stylus buttons work for krita. I think this issue may be similar to https://bugs.kde.org/show_bug.cgi?id=338352 and may be the case for most Huion tablet stylus'. -- You are receiving this mail because: You are watching all bug changes.
[kcontrol] [Bug 60638] No "Are you sure" prompt when deleting Web Shortcuts
https://bugs.kde.org/show_bug.cgi?id=60638 Boudewijn Remptchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/krit ||a/0129982e9e93f1e27be6fea73 ||d499f2e04f220cd --- Comment #5 from Boudewijn Rempt --- Git commit 0129982e9e93f1e27be6fea73d499f2e04f220cd by Boudewijn Rempt. Committed on 17/03/2016 at 18:31. Pushed by rempt into branch 'master'. Restore the ability to D remote images This never worked on OSX or Windows because we don't have KIO there, and was broken on Linux when we removed our depedency on KIO. I know the eventloop implementation isn't a Good Thing, but it's better than nothing. M +1-1libs/ui/CMakeLists.txt A +80 -0libs/ui/KisRemoteFileFetcher.cpp [License: GPL (v2+)] A +55 -0libs/ui/KisRemoteFileFetcher.h [License: GPL (v2+)] M +27 -11 libs/ui/KisView.cpp D +0-45 libs/ui/KisWelcomeScreen.cpp D +0-44 libs/ui/KisWelcomeScreen.h http://commits.kde.org/krita/0129982e9e93f1e27be6fea73d499f2e04f220cd -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359611] Plasmashell loads itself incompletely and with long delays
https://bugs.kde.org/show_bug.cgi?id=359611 Jonathan Riddellchanged: What|Removed |Added CC||j...@jriddell.org Severity|normal |critical -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX
https://bugs.kde.org/show_bug.cgi?id=360033 --- Comment #36 from Thomas Lübking--- Created attachment 97987 --> https://bugs.kde.org/attachment.cgi?id=97987=edit Invite the right order No, all fine. Ok, let's try an older theory and invite the GPU to write before read (though i've not much hope - this might account for "exotic" chips, but the blob should really handle this correctly) The attached patch is the only one you need on top of the vanilla code and when it says something like "pass 1 true" or at least thinks the texture is pink, we'll have made some progress (it will fail later on anyway because i did't want to copy the lines a dozen times for no reason ;-) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360659] New: yakuake forgets which splitview I had open before.
https://bugs.kde.org/show_bug.cgi?id=360659 Bug ID: 360659 Summary: yakuake forgets which splitview I had open before. Product: yakuake Version: 3.0.2 Platform: Archlinux Packages URL: https://bugs.archlinux.org/task/48618?project=5 OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: h...@kde.org Reporter: kde@estada.ch Since the last update yakuake forgets in which part of the splitted tab I was. This is realy annoying and started on my laptop with version 3.X.Y Reproducible: Always Steps to Reproduce: 1. Install yakuake and start it inside a clean/fresh kde5 profile 2. Split the terminal, default keys: Ctrl+( 3. type something into the new shell 4. minimize yakuake 5. open it again Actual Results: continue typeing and now you are in the old tab Expected Results: I would like to return in the same shell I left * package version: 3.0.2-2 * no config -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 360675] Plasma widgets and comics all have the same icon
https://bugs.kde.org/show_bug.cgi?id=360675 Aleix Polchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Aleix Pol --- Please suggest icons for each -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 259382] Make clicking the current folder in places list reset filter bar
https://bugs.kde.org/show_bug.cgi?id=259382 Thomas Pfeifferchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||colo...@autistici.org --- Comment #6 from Thomas Pfeiffer --- I agree with sowi...@dukun.de: Yes, the current behavior is technically correct, but what's technically correct isn't automatically what users expect. >From a user perspective, there isn't much difference between clicking on the current entry on the side bar, or a different one. Also, why would users click on the folder they're already in if they didn't expect anything to change? Therefore the proposed change makes sense. Notice that this does not apply if the filter is "locked", of course. -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 360628] New: Yousendit should be renamed to hightail
https://bugs.kde.org/show_bug.cgi?id=360628 Bug ID: 360628 Summary: Yousendit should be renamed to hightail Product: storageservicemanager Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: onelove.nyahbi...@gmail.com The YouSendIt account service should be renamed to Hightail for accuracy purposes. Reproducible: Always YouSendIt changed its name to Hightail since 2013. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359197] [HUION] 100% pressure at stroke start
https://bugs.kde.org/show_bug.cgi?id=359197 woltherachanged: What|Removed |Added CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Hey there! Does this still happen with the 3.0 pre-alpha 3? If so, could you maybe make a tablet log(https://docs.krita.org/KritaFAQ#What_if_your_tablet_is_not_recognized_by_Krita.3F)? That'd be super-useful! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 360700] Disable "Unify outputs" when there is only one display
https://bugs.kde.org/show_bug.cgi?id=360700 Christoph Feckchanged: What|Removed |Added Version|unspecified |1.0.5 Product|systemsettings |KScreen Component|general |kcm Assignee|plasma-b...@kde.org |se...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 360669] New: plasma-nm is older than other plasma packages
https://bugs.kde.org/show_bug.cgi?id=360669 Bug ID: 360669 Summary: plasma-nm is older than other plasma packages Product: neon Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: unstable packaging Assignee: n...@kde.org Reporter: l.bonn...@laposte.net Hi, all neon packages for plasma have a 5.5.4+git version number except plasma-nm that is at version 5.5.3. This is a problem because it is less recent than the package provided by the kubuntu-ppa/backports PPA and is perhaps the cause of bug #360668. $ apt-cache policy plasma-nm plasma-nm: Installed: 4:5.5.4-0ubuntu1~ubuntu15.10~ppa1 Candidate: 4:5.5.4-0ubuntu1~ubuntu15.10~ppa1 Version table: *** 4:5.5.4-0ubuntu1~ubuntu15.10~ppa1 0 500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 4:5.5.3+git20160316.1404+15.10-0 0 500 http://archive.neon.kde.org.uk/unstable/ wily/main amd64 Packages [...] Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359813] images inserted in mail with CID are not displayed
https://bugs.kde.org/show_bug.cgi?id=359813 Laurent Montelchanged: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.2 Status|UNCONFIRMED |RESOLVED --- Comment #7 from Laurent Montel --- For me it works fine here (5.2) I didn"t test in 5.1.3 but for sure in 5.2 it works. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 348972] Web shortcuts changes aren't reflected in other locations
https://bugs.kde.org/show_bug.cgi?id=348972 --- Comment #6 from Greg Lepore--- Created attachment 97923 --> https://bugs.kde.org/attachment.cgi?id=97923=edit Screenshot showing two different web shortcuts modules -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356186] Background not transparent when started with dual monitor
https://bugs.kde.org/show_bug.cgi?id=356186 Thomas Van Paryschanged: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360645] New: Cannot open configuration for more than one widget inside one containment
https://bugs.kde.org/show_bug.cgi?id=360645 Bug ID: 360645 Summary: Cannot open configuration for more than one widget inside one containment Product: plasmashell Version: 5.5.95 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: aspotas...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org See Steps to Reproduce below. Reproducible: Always Steps to Reproduce: 1. Add digital-clock and folderview widget onto panel. 2. Select "Configure widget [...]" in context menu of digital clock. This opens a configuration dialog for the digital clock, as expected. 3. Select "Configure widget [...]" in context menu of folder view widget. Actual Results: Configuration dialog for folder view opens, but configuration dialog for digital-clock closes at the moment in time. Expected Results: Both of these configuration dialogs should be open. The same problem exists when opening configuration dialogs for two widgets on the desktop (e.g. in a folder view containment). But opening two configuration dialogs for one widget on panel and another one on desktop works. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360592] system settings crash when going BACK
https://bugs.kde.org/show_bug.cgi?id=360592 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 343543 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 360085] Search field gets cleared in mid-typing while on home screen. Can't finish search string (video example included)
https://bugs.kde.org/show_bug.cgi?id=360085 Aleix Polchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 360654] Please add button to re-run search in files
https://bugs.kde.org/show_bug.cgi?id=360654 Kevin Funkchanged: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 360602] Reply to picks wrong (unrelated list) recipient address
https://bugs.kde.org/show_bug.cgi?id=360602 Laurent Montelchanged: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- could you save this mail as mbox and attach it here please ? (I think that mail from mesa devel is not secret :) ) I need it for testing it Thanks -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359813] images inserted in mail with CID are not displayed
https://bugs.kde.org/show_bug.cgi?id=359813 Danielechanged: What|Removed |Added CC||denni.gran...@gmail.com --- Comment #8 from Daniele --- Opensuse Tumbleweed here with kmail 5.1.3 from kdepim 15.12.3 running on frameworks 5.20.0 and the bug persist. Ciao Daniele -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions
https://bugs.kde.org/show_bug.cgi?id=341497 le.t...@gmail.com changed: What|Removed |Added CC||le.t...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360663] New: The progress bar shown on the layer doesn't get cleared after operation is completed , instead it gets stuck at 0% thus hiding the layer icons
https://bugs.kde.org/show_bug.cgi?id=360663 Bug ID: 360663 Summary: The progress bar shown on the layer doesn't get cleared after operation is completed , instead it gets stuck at 0% thus hiding the layer icons Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: raghavendr.ra...@gmail.com The progress bar shown on the layer doesn't get cleared after operation is completed , instead it gets stuck at 0% thus hiding the layer icons like alpha and locks. you can see the screenshot here-> https://dl.dropboxusercontent.com/u/3793/layer-progressbar.png this happens mostly to copy pasted or duplicated layer, this is also noticed on gmic output layer Reproducible: Sometimes -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360695] New: Non-functional info button in Display Configuration
https://bugs.kde.org/show_bug.cgi?id=360695 Bug ID: 360695 Summary: Non-functional info button in Display Configuration Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: psychon...@nothingisreal.com In the "Display Configuration" section of the "Display Configuration" dialog, there is an info button displayed in the upper pane below the monitor layout diagram (see attached screenshot). The button is clickable, but clicking on it has no observable effect. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360626] Desktop crash
https://bugs.kde.org/show_bug.cgi?id=360626 Marco Martinchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||notm...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 357435 *** -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 356194] The tray icon show update even there is nothing to update
https://bugs.kde.org/show_bug.cgi?id=356194 Aleix Polchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 347602 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 341043] Highlighting exceeds the margins of the line
https://bugs.kde.org/show_bug.cgi?id=341043 Germano Massullochanged: What|Removed |Added Version|0.20.2 |0.24.0 --- Comment #2 from Germano Massullo --- Confirming on Plasma desktop 5.5.5 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 344192] Crash while trying to save a file as an already open file
https://bugs.kde.org/show_bug.cgi?id=344192 Kevin Funkchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Kevin Funk --- @Francis: You could try removing the QueuedConnection flag from here: shell/mainwindow.cpp: connect(Core::self()->documentController(), ::documentOpened, this, ::updateTabColor, Qt::QueuedConnection); connect(Core::self()->documentController(), ::documentUrlChanged, this, ::updateTabColor, Qt::QueuedConnection); Does it still crash then? Care to investigate a bit? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329697] digiKam crash when browsing albums (qt-sqlite plugin broken due to BC issue with libsqlite)
https://bugs.kde.org/show_bug.cgi?id=329697 --- Comment #159 from caulier.gil...@gmail.com --- *** Bug 360665 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.