[Breeze] [Bug 387675] "Draw window borders for maximized windows" setting causes titlebar buttons' click zones to shrink
https://bugs.kde.org/show_bug.cgi?id=387675 Martin Flöser changed: What|Removed |Added Product|kwin|Breeze Component|decorations |window decoration Assignee|kwin-bugs-n...@kde.org |hugo.pereira.da.costa@gmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387757] Color manage pick() method of org.kde.kwin.ColorPicker
https://bugs.kde.org/show_bug.cgi?id=387757 Martin Flöser changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387755] Add a delay to org.kde.kwin.Screenshot - "interactive" method
https://bugs.kde.org/show_bug.cgi?id=387755 Martin Flöser changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387740] Window parts popup when raising another window
https://bugs.kde.org/show_bug.cgi?id=387740 --- Comment #3 from Martin Flöser --- Please provide output of qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 387759] Konsole Lacks the "Ambiguous-width characters" Option
https://bugs.kde.org/show_bug.cgi?id=387759 --- Comment #1 from qdzcu...@sharklasers.com --- Created attachment 109283 --> https://bugs.kde.org/attachment.cgi?id=109283&action=edit Effect in gnome-terminal (https://wiki.gnome.org/Apps/Terminal), Font: Migu 1M -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 387759] New: Konsole Lacks the "Ambiguous-width characters" Option
https://bugs.kde.org/show_bug.cgi?id=387759 Bug ID: 387759 Summary: Konsole Lacks the "Ambiguous-width characters" Option Product: konsole Version: 17.08.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: qdzcu...@sharklasers.com Target Milestone: --- Created attachment 109282 --> https://bugs.kde.org/attachment.cgi?id=109282&action=edit Effect in Konsole, Font: Migu 1M Related: Bug 41744 The issue in Bug 41744 still exists in version 17.08.3. OVERVIEW The option "Ambiguous-width characters" is unavailable. Thus, all ambiguous-width characters are considered "narrow". Symbols such as "●", "★" and "※" will be shown overlapping other characters. STEPS TO REPRODUCE 1) Prepare a text containing ambiguous-width characters, such as "●", "★" and "※". 2) Display the text in Konsole (e.g. using "cat" to display the text file) ACTUAL RESULT The symbols overlapped other normal characters. (Please see attachment) EXPECTED RESULT An option "Ambiguous-width characters" with two choices, "Narrow" and "Wide", should be provided. When "Wide" is chosen, the characters do not overlap. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373638] Digikam doesn't show any files.
https://bugs.kde.org/show_bug.cgi?id=373638 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||5.8.0 Resolution|--- |FIXED --- Comment #8 from caulier.gil...@gmail.com --- The problem is last Qt 5.9.3 used by digiKam < 5.8.0 which break the album view. We fix the problem in 5.8.0 implementation to be compatible with last Qt release. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 385988] [mockup] UI suggestions
https://bugs.kde.org/show_bug.cgi?id=385988 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 385987] UI-consistency; change 'new' button into text.
https://bugs.kde.org/show_bug.cgi?id=385987 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Nate Graham --- This seems like a WONTFIX; the new New Vault UI that went in with https://cgit.kde.org/plasma-vault.git/commit/?id=fef23f48913f1c7027f50da83e6137bb27bab10d has this being a normal button, to match other plasmoids (like BLuetooth). We now *are* consistent--consistent with other Plasmoids. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387675] "Draw window borders for maximized windows" setting causes titlebar buttons' click zones to shrink
https://bugs.kde.org/show_bug.cgi?id=387675 --- Comment #13 from Nate Graham --- Created attachment 109281 --> https://bugs.kde.org/attachment.cgi?id=109281&action=edit The issue with borders turned on Video showing the issue with window borders set to something other than No Borders -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387675] "Draw window borders for maximized windows" setting causes titlebar buttons' click zones to shrink
https://bugs.kde.org/show_bug.cgi?id=387675 Nate Graham changed: What|Removed |Added Summary|After upgrading from 5.9.5 |"Draw window borders for |to 5.11.4, for my user |maximized windows" setting |only, every window |causes titlebar buttons' |titlebar's close button's |click zones to shrink |click zone isn't as big as | |it used to be | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387675] After upgrading from 5.9.5 to 5.11.4, for my user only, every window titlebar's close button's click zone isn't as big as it used to be
https://bugs.kde.org/show_bug.cgi?id=387675 Nate Graham changed: What|Removed |Added Attachment #109246|0 |1 is obsolete|| --- Comment #12 from Nate Graham --- Created attachment 109280 --> https://bugs.kde.org/attachment.cgi?id=109280&action=edit Problem occurs when "Draw window borders for maximized windows" is checked Found the issue. you can perfectly reproduce it by turning on System Settings > Application Style > Window Decorations > Breeze > Configure > "Draw window borders for maximized windows". With that setting checked, the click zone for the right-most button seems to shrink. It isn't just that the border relocates the click zone; the click zone actually shrinks. You can see this by changing your window borders to No Borders; the titlebar buttons don't move, but the click zone shrinks. I'm attaching a video that shows the exact issue. Also it doesn't make sense to have this option even available with No Borders (there are no borders to draw!), but that's a separate issue. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 387743] When looking at my swap used it shows the home used
https://bugs.kde.org/show_bug.cgi?id=387743 --- Comment #9 from auronhi...@gmail.com --- https://forums.linuxmint.com/viewtopic.php?f=56&t=257139 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 387743] When looking at my swap used it shows the home used
https://bugs.kde.org/show_bug.cgi?id=387743 --- Comment #8 from auronhi...@gmail.com --- https://forums.linuxmint.com/viewtopic.php?f=56&t=257139 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373638] Digikam doesn't show any files.
https://bugs.kde.org/show_bug.cgi?id=373638 --- Comment #7 from Jason Straight --- The appimage for 5.8.0 works -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373638] Digikam doesn't show any files.
https://bugs.kde.org/show_bug.cgi?id=373638 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t --- Comment #6 from Jason Straight --- Yes, with 5.7.0 in neon. My first attempt to use an existing folder as an album, digikam filled my SSD by going into a loop, creating the same folder within that one, and so on. For example, I had several levels of /home/junfan/Pictures/Pictures/Pictures/Pictures/ After that, I moved ~/Pictures and created a new ~/Pictures, deleted ~/.local/share/digikam and ~/.config/digicamrc (?) When I relaunched and reconfigured (wizard), I dropped a pic in the folder and under the album, in digikam, it added a blank folder. No files visible. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384850] Series of transform mask bugs with large images
https://bugs.kde.org/show_bug.cgi?id=384850 reptilli...@live.com changed: What|Removed |Added OS|Linux |MS Windows Platform|Other |MS Windows --- Comment #4 from reptilli...@live.com --- I have tested with cloned group layer, there are no issues for there. Mind you, I have only tested group layer with a big LAB file I have, but it works well. It's only the one I have found in other use case scenario is where there is bugs. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 387758] New: krunner segmentation fault
https://bugs.kde.org/show_bug.cgi?id=387758 Bug ID: 387758 Summary: krunner segmentation fault Product: krunner Version: 5.11.3 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: niktische...@gmail.com Target Milestone: --- Application: krunner (5.11.3) Qt Version: 5.9.3 Frameworks Version: 5.40.0 Operating System: Linux 4.9.67 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: - What I was doing when the application crashed: Just hit standard shortcut for KRunner - Alt+F2 and type something - Result: KRunner crached The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f335e3ae400 (LWP 2800))] Thread 4 (Thread 0x7f333f5ef700 (LWP 2872)): #0 0x7f3358cfc41b in poll () at /lib64/libc.so.6 #1 0x7f3350bb75f1 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3350bb76fc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3359b92dbb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f3359b3b10a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f335995e63a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f335cac0625 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f335996322e in () at /usr/lib64/libQt5Core.so.5 #8 0x7f3354c3c565 in start_thread () at /lib64/libpthread.so.0 #9 0x7f3358d080af in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f334605f700 (LWP 2859)): #0 0x7f3350bfafa4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f3350bb6e39 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3350bb756f in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3350bb76fc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f3359b92dbb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f3359b3b10a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f335995e63a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f335b7dbc55 in () at /usr/lib64/libQt5DBus.so.5 #8 0x7f335996322e in () at /usr/lib64/libQt5Core.so.5 #9 0x7f3354c3c565 in start_thread () at /lib64/libpthread.so.0 #10 0x7f3358d080af in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f33484b0700 (LWP 2807)): #0 0x7f3358cfc41b in poll () at /lib64/libc.so.6 #1 0x7f3357d5ff32 in () at /usr/lib64/libxcb.so.1 #2 0x7f3357d61c47 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f334a311a39 in () at /usr/lib64/qt5/plugins/platforms/../../../libQt5XcbQpa.so.5 #4 0x7f335996322e in () at /usr/lib64/libQt5Core.so.5 #5 0x7f3354c3c565 in start_thread () at /lib64/libpthread.so.0 #6 0x7f3358d080af in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f335e3ae400 (LWP 2800)): [KCrash Handler] #6 0xaad0 in () #7 0x7f3328f828d6 in () at /usr/lib64/libgobject-2.0.so.0 #8 0x7f332a4fe878 in () at /usr/lib64/qt5/plugins/plasma_runner_marble.so #9 0x002e in () #10 0x0001 in () #11 0x7f3328f513c4 in _init () at /usr/lib64/libgobject-2.0.so.0 #12 0x7f332a4ff058 in () at /usr/lib64/qt5/plugins/plasma_runner_marble.so #13 0x7f335e21378c in _dl_init () at /lib64/ld-linux-x86-64.so.2 #14 0x7f335e2186ef in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #15 0x7f3358d4999c in _dl_catch_error () at /lib64/libc.so.6 #16 0x7f335e217c29 in _dl_open () at /lib64/ld-linux-x86-64.so.2 #17 0x7f3351081f26 in dlopen_doit () at /lib64/libdl.so.2 #18 0x7f3358d4999c in _dl_catch_error () at /lib64/libc.so.6 #19 0x7f33510825c5 in _dlerror_run () at /lib64/libdl.so.2 #20 0x7f3351081fa1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2 #21 0x7f3359b389fc in () at /usr/lib64/libQt5Core.so.5 #22 0x7f3359b321b5 in () at /usr/lib64/libQt5Core.so.5 #23 0x7f335a78525a in KPluginLoader::load() () at /usr/lib64/libKF5CoreAddons.so.5 #24 0x7f335a78534a in KPluginLoader::pluginVersion() () at /usr/lib64/libKF5CoreAddons.so.5 #25 0x7f333c6df534 in () at /usr/lib64/libKF5Runner.so.5 #26 0x7f333c6e096e in () at /usr/lib64/libKF5Runner.so.5 #27 0x7f333c6dd7ca in Plasma::RunnerManager::launchQuery(QString const&, QString const&) () at /usr/lib64/libKF5Runner.so.5 #28 0x7f333c8f79b8 in Milou::SourcesModel::setQueryString(QString const&) () at /usr/lib64/libmilou.so.5 #29 0x7f333c8fcbb5 in () at /usr/lib64/libmilou.so.5 #30 0x7f335caab3ef in () at /usr/lib64/libQt5Qml.so.5 #31 0x7f335caabce6 in () at /usr/lib64/libQt5Qml.so.5 #32 0x7f
[kwin] [Bug 387757] New: Color manage pick() method of org.kde.kwin.ColorPicker
https://bugs.kde.org/show_bug.cgi?id=387757 Bug ID: 387757 Summary: Color manage pick() method of org.kde.kwin.ColorPicker Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: je...@zemarmot.net Target Milestone: --- We need to be able to convert the picked pixel into the sRGB color space in case the screen is color-managed. Through the dbus API, we don't even know the pixel coordinates (so in multi-display setups, we could not know for sure which is the right profile to get anyway); and in any case, I'm not sure if we can get the display profiles in Wayland (well at least right now our code doesn't have the implementation). The "pick" method needs to return a converted color or the monitor profile it is displayed with so that we can convert ourselves or apply it. See: https://bugzilla.gnome.org/show_bug.cgi?id=779942#c5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387756] New: Changing the time settings in the Plasma panel makes it crash the entire Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=387756 Bug ID: 387756 Summary: Changing the time settings in the Plasma panel makes it crash the entire Plasma desktop Product: plasmashell Version: 5.8.7 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: hamnisd...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.7) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.9.56-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: I was changing the clock settings regarding the date and timezone and I also enabled holidays. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f522dd88800 (LWP 5302))] Thread 10 (Thread 0x7f51392b8700 (LWP 5074)): #0 0x7f522847000d in poll () at /lib64/libc.so.6 #1 0x7f52253d6c94 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f52253d6d9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f5228d78e2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f5228d2449a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f5228b5e3bc in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f5228b62ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f5227c6c66d in start_thread () at /lib64/libpthread.so.0 #8 0x7f522847be4d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f51596dc700 (LWP 6906)): #0 0x7f522846b92d in read () at /lib64/libc.so.6 #1 0x7f521de51c81 in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #2 0x7f521e6f385e in pa_mainloop_prepare () at /lib64/libpulse.so.0 #3 0x7f521e6f4260 in pa_mainloop_iterate () at /lib64/libpulse.so.0 #4 0x7f521e6f4320 in pa_mainloop_run () at /lib64/libpulse.so.0 #5 0x7f521e701f16 in thread () at /lib64/libpulse.so.0 #6 0x7f521de809c8 in internal_thread_func () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #7 0x7f5227c6c66d in start_thread () at /lib64/libpthread.so.0 #8 0x7f522847be4d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f515add6700 (LWP 6905)): #0 0x7f522541b970 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f52253d64f9 in g_main_context_query () at /lib64/libglib-2.0.so.0 #2 0x7f52253d6c0f in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f52253d6d9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f5228d78e2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f5228d2449a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f5228b5e3bc in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f522b3ef205 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7f5228b62ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f5227c6c66d in start_thread () at /lib64/libpthread.so.0 #10 0x7f522847be4d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f517b8a8700 (LWP 6589)): #0 0x7f522847000d in poll () at /lib64/libc.so.6 #1 0x7f52253d6c94 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f52253d6d9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f5228d78e2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f5228d2449a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f5228b5e3bc in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f522bd74902 in QQuickPixmapReader::run() () at /lib64/libQt5Quick.so.5 #7 0x7f5228b62ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f5227c6c66d in start_thread () at /lib64/libpthread.so.0 #9 0x7f522847be4d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f5205d6b700 (LWP 6588)): #0 0x7f5227c71c4f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f522d7dc234 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f522d7dc279 in () at /lib64/libQt5Script.so.5 #3 0x7f5227c6c66d in start_thread () at /lib64/libpthread.so.0 #4 0x7f522847be4d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f5207bbf700 (LWP 6587)): #0 0x7f5228d78520 in idleTimerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #1 0x7f52253d622d in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7f52253d6bc3 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f52253d6d9c in g_main_context_ite
[frameworks-qqc2-desktop-style] [Bug 385950] Crashes running a simple qml file
https://bugs.kde.org/show_bug.cgi?id=385950 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387755] New: Add a delay to org.kde.kwin.Screenshot - "interactive" method
https://bugs.kde.org/show_bug.cgi?id=387755 Bug ID: 387755 Summary: Add a delay to org.kde.kwin.Screenshot - "interactive" method Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: je...@zemarmot.net Target Milestone: --- A common feature in screenshot applications is to add a delay. A very common usage I have of it is for instance when I need to shoot an intermediary state of a window. For instance, when I want to shoot a menu contents: I would set a 2 sec delay, then quickly open the menu and wait for the screenshot. For fullscreen screenshots, it can be added programmatically before the dbus call, and for "screenshotArea" as well when a "selectArea" will be implemented (cf. bug 387721) in between the 2 dbus calls. But "interactive" manages everything from window selection to snapshot. So this would need to be added as a parameter to the dbus method (uint parameter for delay in second maybe?). Moreover doing so, it may be interesting to add a OSD effect to display a countdown before the screenshot (this countdown effect could of course be optional with another argument, boolean, to the method "interactive"). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387745] Shift button breaking Hold-Space (pan, etc.) controls
https://bugs.kde.org/show_bug.cgi?id=387745 --- Comment #3 from Scott Petrovic --- You can't get to the rotation tool until you press shift, so I am not sure what you mean that it breaks it when you press it. Are you simply saying that holding down Shift + Spacebar doesn't activate the rotation tool? It seems to work on the version I am testing with. Maybe someone else can chime in and see if it is an issue for them -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 387595] amarok_crashes
https://bugs.kde.org/show_bug.cgi?id=387595 Myriam Schweingruber changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Myriam Schweingruber --- *** This bug has been marked as a duplicate of bug 325723 *** -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 325723] Amarok (apparently) crashes during quit
https://bugs.kde.org/show_bug.cgi?id=325723 Myriam Schweingruber changed: What|Removed |Added CC||desdicha...@gmail.com --- Comment #12 from Myriam Schweingruber --- *** Bug 387595 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 387753] Usage of `qmlplugindump` causes sandbox violations
https://bugs.kde.org/show_bug.cgi?id=387753 Christophe Giboudeaux changed: What|Removed |Added Resolution|UPSTREAM|DOWNSTREAM --- Comment #2 from Christophe Giboudeaux --- Downstream issue rather, according to https://bugzilla.gnome.org/show_bug.cgi?id=744135#c1 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 387754] New: this always happens when I close ktorrent
https://bugs.kde.org/show_bug.cgi?id=387754 Bug ID: 387754 Summary: this always happens when I close ktorrent Product: ktorrent Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: tonypsh...@gmail.com Target Milestone: --- Application: ktorrent (5.1.0) Qt Version: 5.7.1 Frameworks Version: 5.38.0 Operating System: Linux 4.10.0-42-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: I was closing the application down using 'File menu - Quit' , this also happens if I close the application when I do so via the 'X' icon in the top right hand corner The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe6e7177900 (LWP 8634))] Thread 6 (Thread 0x7fe6797e2700 (LWP 8690)): #0 0x7fe6dd1f7510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe6e20f0aeb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fe6e6a76122 in () at /usr/lib/x86_64-linux-gnu/libKF5Torrent.so.6 #3 0x7fe6e20efc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe6dd1f16da in start_thread (arg=0x7fe6797e2700) at pthread_create.c:456 #5 0x7fe6e14dcd7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7fe67c1ff700 (LWP 8659)): #0 0x7fe6dd1f7510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe6844e4acb in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7fe6844e47f7 in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7fe6dd1f16da in start_thread (arg=0x7fe67c1ff700) at pthread_create.c:456 #4 0x7fe6e14dcd7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7fe6ccaf6700 (LWP 8638)): #0 0x7fe6e20e6d99 in QMutex::lock() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fe6e231282f in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fe6db2bfa6d in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe6db2c049b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe6db2c068c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe6e23130bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe6e22bcbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe6e20eaf83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe6e20efc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fe6dd1f16da in start_thread (arg=0x7fe6ccaf6700) at pthread_create.c:456 #10 0x7fe6e14dcd7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7fe6ce508700 (LWP 8636)): #0 0x7fe6db305edb in g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe6db2bfce1 in g_main_context_query () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe6db2c04e8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe6db2c068c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe6e23130bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe6e22bcbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe6e20eaf83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe6e36b45d5 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fe6e20efc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fe6dd1f16da in start_thread (arg=0x7fe6ce508700) at pthread_create.c:456 #10 0x7fe6e14dcd7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fe6d02e1700 (LWP 8635)): #0 0x7fe6e14ead3c in __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7fe6e1456b68 in _int_free (av=0x7fe6e1795b00 , p=0x5592d0e3ce00, have_lock=0) at malloc.c:3999 #2 0x7fe6e145ad2c in __GI___libc_free (mem=mem@entry=0x5592d0e3ce10) at malloc.c:2984 #3 0x7fe6e7075cd7 in __GI__dl_deallocate_tls (tcb=tcb@entry=0x7fe697fff700, dealloc_tcb=dealloc_tcb@entry=false) at dl-tls.c:560 #4 0x7fe6dd1f15d6 in __free_stacks (limit=41943040) at allocatestack.c:284 #5 0x7fe6dd1f15d6 in queue_stack (stack=0x7fe6e145ad2c <__GI___libc_free+76>) at allocatestack.c:312 #6 0x7fe6dd1f15d6 in __deallocate_stack (pd=0x7fe6e1
[extra-cmake-modules] [Bug 387753] Usage of `qmlplugindump` causes sandbox violations
https://bugs.kde.org/show_bug.cgi?id=387753 Elias Probst changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM URL||https://bugzilla.gnome.org/ ||show_bug.cgi?id=744135 --- Comment #1 from Elias Probst --- It looks like this is actually an upstream issue: https://bugzilla.gnome.org/show_bug.cgi?id=744135 As documented in Gentoo's bugtracker: https://bugs.gentoo.org/570624 -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 387753] New: Usage of `qmlplugindump` causes sandbox violations
https://bugs.kde.org/show_bug.cgi?id=387753 Bug ID: 387753 Summary: Usage of `qmlplugindump` causes sandbox violations Product: extra-cmake-modules Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: ecm-bugs-n...@kde.org Reporter: m...@eliasprobst.eu Target Milestone: --- Created attachment 109279 --> https://bugs.kde.org/attachment.cgi?id=109279&action=edit sandbox.log of "sandbox qmlplugindump QtQuick.Window 2.1" The usage of `qmlplugindump` causes sandbox violations, e.g. here on Gentoo when trying to build kwin since @fe9664fd8 [1] It looks like `qmlplugindump` is not quite environment agnostic but instead tries to do all kind of stuff depending on the environment in which it is executed in, which is clearly shown by e.g. running `sandbox qmlplugindump QtQuick.Window 2.1`, (as regular user of a Plasma/Wayland session) causing at least 4 sandbox violations of which at least the one attempting to write to /dev/dri/card0 would be considered severe: trimmed sandbox.log, full log attached: F: chmod P: /run/user/1000 F: mkostemp P: /run/user/1000/wayland-cursor-shared-XX F: open_wr P: /dev/dri/card0 F: mkostemp P: /run/user/1000/mesa-shared-XX The sandbox.log of the build process (as root, no graphical session) looks similar: F: open_wr P: /dev/dri/renderD128 C: /usr/lib64/gstreamer-1.0/gst-plugin-scanner -l F: open_wr P: /dev/dri/card0 C: /usr/lib64/gstreamer-1.0/gst-plugin-scanner -l F: open_wr P: /dev/video0 C: /usr/lib64/qt5/bin/qmlplugindump QtMultimedia 5.0 This seems to only happen with QtQuick.Window, so I'm not sure whether that's an issue with the way ECM calls qmlplugindump, qmlplugindump itself or just QtDeclarative's "QtQuick.Window". [1] https://phabricator.kde.org/R108:fe9664fd8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 387752] New: System Settings crash
https://bugs.kde.org/show_bug.cgi?id=387752 Bug ID: 387752 Summary: System Settings crash Product: systemsettings Version: 5.11.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: parajulidarsh...@gmail.com Target Milestone: --- Application: systemsettings5 (5.11.4) Qt Version: 5.9.3 Frameworks Version: 5.40.0 Operating System: Linux 4.14.4-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I was simply browsing various settings. I was in font section, crash occurred as I closed the window. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd35e423800 (LWP 17575))] Thread 2 (Thread 0x7fd342077700 (LWP 17577)): #0 0x7fd35a08df2b in poll () at /usr/lib/libc.so.6 #1 0x7fd353c44ed3 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd353c44fae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fd35a9cc204 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd35a96f99b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fd35a78827e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fd35ade7376 in () at /usr/lib/libQt5DBus.so.5 #7 0x7fd35a78d1cb in () at /usr/lib/libQt5Core.so.5 #8 0x7fd355e4408a in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fd35a09842f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fd35e423800 (LWP 17575)): [KCrash Handler] #5 0x5604c91aaac0 in () #6 0x7fd349727406 in () at /usr/lib/libKF5Notifications.so.5 #7 0x7fd3497274a9 in () at /usr/lib/libKF5Notifications.so.5 #8 0x7fd35a99ec6d in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #9 0x7fd35a9a88ac in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #10 0x7fd3496f8819 in () at /usr/lib/libKF5Notifications.so.5 #11 0x7fd359fd9448 in __run_exit_handlers () at /usr/lib/libc.so.6 #12 0x7fd359fd949a in () at /usr/lib/libc.so.6 #13 0x7fd359fc2f51 in __libc_start_main () at /usr/lib/libc.so.6 #14 0x5604c27ced4a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387751] New: Certain TIFF file type can't be opened
https://bugs.kde.org/show_bug.cgi?id=387751 Bug ID: 387751 Summary: Certain TIFF file type can't be opened Product: krita Version: 4.0 pre-alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: ene...@gmail.com Target Milestone: --- Please check this cutout people pack: http://xoio-air.de/2011/cutout-people-collection/ Files just can't be opened. Might somehow be related, this poeple pack should have layers visible: http://xoio-air.de/2012/greenscreen_people_01/ -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 313815] Add "Print current view" option to the print dialogue
https://bugs.kde.org/show_bug.cgi?id=313815 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 384925] Window decoration missing
https://bugs.kde.org/show_bug.cgi?id=384925 --- Comment #5 from Rob --- I experimented with this. Finally I was able to localize the problem. In my case, the problem was not gwenviewrc but ~/.config/org.kde.gwenviewrc. In fact, when any of the widh AND height parameters exacly equal the total display geometry (in my case 1400x1050), you should delete them, and the decoration is back again. Sample Snippet from this file: [MainWindow] Height 1024=742 Height 1050=1050 Height 768=768 ToolBarsMovable=Disabled Width 1024=1024 Width 1280=990 Width 1400=1400 Window-Maximized 768x1024=true -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387740] Window parts popup when raising another window
https://bugs.kde.org/show_bug.cgi?id=387740 Kai Uwe Broulik changed: What|Removed |Added Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Component|generic-wayland |wayland-generic Target Milestone|1.0 |--- CC||k...@privat.broulik.de Product|plasmashell |kwin --- Comment #2 from Kai Uwe Broulik --- That's subsurfaces flickering through, re-assigning to kwin (I bet that's already been reported) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379997] Always "Akonadi not started" overlay on reboot
https://bugs.kde.org/show_bug.cgi?id=379997 David Faure changed: What|Removed |Added Latest Commit|https://commits.kde.org/ako |https://commits.kde.org/ako |nadi/f8d59a48e68fc89949bd16 |nadi/10db44a34c4fa0d0907bdc |cf97097f207f609324 |1abfec674fed920dcf --- Comment #3 from David Faure --- Git commit 10db44a34c4fa0d0907bdc1abfec674fed920dcf by David Faure. Committed on 09/12/2017 at 20:58. Pushed by dfaure into branch 'Applications/17.12'. ErrorOverlay: don't show by mistake if called with Running twice. Summary: If serverStateChanged(Running) is called twice, the first time this would hide the overlay and set mOverlayActive=false, so the second time this goes into the else branch, which shows the overlay... The reason it's called twice isn't because ServerManager emits stateChanged(Running) twice, obviously (it only emits on actual change). The reason is that the ErrorOverlay constructor calls serverStateChanged(state) and connects to &ServerManager::stateChanged. It can happen that for this initial state, ServerManager::state() finds out "Running" before ServerManager gets a chance to notice by itself and emit stateChanged(). Test Plan: Found with debug output, during session startup, over many weeks (it's clearly a race condition). Reviewers: dvratil, vkrause Reviewed By: dvratil Subscribers: #kde_pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D9264 (cherry picked from commit f8d59a48e68fc89949bd16cf97097f207f609324) M +7-5src/widgets/erroroverlay.cpp https://commits.kde.org/akonadi/10db44a34c4fa0d0907bdc1abfec674fed920dcf -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379997] Always "Akonadi not started" overlay on reboot
https://bugs.kde.org/show_bug.cgi?id=379997 David Faure changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/ako ||nadi/f8d59a48e68fc89949bd16 ||cf97097f207f609324 Resolution|--- |FIXED --- Comment #2 from David Faure --- Git commit f8d59a48e68fc89949bd16cf97097f207f609324 by David Faure. Committed on 09/12/2017 at 20:58. Pushed by dfaure into branch 'master'. ErrorOverlay: don't show by mistake if called with Running twice. Summary: If serverStateChanged(Running) is called twice, the first time this would hide the overlay and set mOverlayActive=false, so the second time this goes into the else branch, which shows the overlay... The reason it's called twice isn't because ServerManager emits stateChanged(Running) twice, obviously (it only emits on actual change). The reason is that the ErrorOverlay constructor calls serverStateChanged(state) and connects to &ServerManager::stateChanged. It can happen that for this initial state, ServerManager::state() finds out "Running" before ServerManager gets a chance to notice by itself and emit stateChanged(). Test Plan: Found with debug output, during session startup, over many weeks (it's clearly a race condition). Reviewers: dvratil, vkrause Reviewed By: dvratil Subscribers: #kde_pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D9264 M +7-5src/widgets/erroroverlay.cpp https://commits.kde.org/akonadi/f8d59a48e68fc89949bd16cf97097f207f609324 -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 387446] Build fails with Qt 5.10
https://bugs.kde.org/show_bug.cgi?id=387446 --- Comment #2 from Christophe Giboudeaux --- Thanks. Builds fine now, but the twitter accounts remains empty. Removing / Adding back the account still results in choqok(9820) - org.kde.choqok.twitterapi: : Error: "Could not authenticate you." -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387720] GDBus.Error:org.kde.kwin.ColorPicker.Error.Cancelled: Color picking got cancelled
https://bugs.kde.org/show_bug.cgi?id=387720 --- Comment #2 from Jehan --- (In reply to Martin Flöser from comment #1) > I just installed d-feet and gave it a try: works fine. > > Possibilities I see is a setup error in Fedora or a bug in the version (5.10 > is no longer maintained, that's also the reason why it's not in the list). > > Reasons for the canceled message are: > * right click > * Escape beint pressed Hmm… well I won't be able to make the time to build an updated version of kwin/plasma. I guess I will just assume my implementation is fine or wait for Fedora to update their package to test again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387722] Right click context menu - move to screen
https://bugs.kde.org/show_bug.cgi?id=387722 Eike Hein changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Eike Hein --- *** This bug has been marked as a duplicate of bug 386046 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386046] Missing option "Move to Screen" for minimized window of application
https://bugs.kde.org/show_bug.cgi?id=386046 Eike Hein changed: What|Removed |Added CC||polarathene-signup@hotmail. ||com --- Comment #1 from Eike Hein --- *** Bug 387722 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 387750] New: TV Bildfrequenz zu zu gering
https://bugs.kde.org/show_bug.cgi?id=387750 Bug ID: 387750 Summary: TV Bildfrequenz zu zu gering Product: kaffeine Version: 2.0.13 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mchehab+...@kernel.org Reporter: gerhard.arn...@live.de Target Milestone: --- TV-bilder laufen mit höchstens 20 Bilder inder secunde -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382144] Flash icon when it requests attention, instead of displaying little orange line
https://bugs.kde.org/show_bug.cgi?id=382144 --- Comment #6 from Eike Hein --- I'd suggest discussing it inside the VDG. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387720] GDBus.Error:org.kde.kwin.ColorPicker.Error.Cancelled: Color picking got cancelled
https://bugs.kde.org/show_bug.cgi?id=387720 --- Comment #1 from Martin Flöser --- I just installed d-feet and gave it a try: works fine. Possibilities I see is a setup error in Fedora or a bug in the version (5.10 is no longer maintained, that's also the reason why it's not in the list). Reasons for the canceled message are: * right click * Escape beint pressed -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 387749] New: Every 8 number of calendar is invisible
https://bugs.kde.org/show_bug.cgi?id=387749 Bug ID: 387749 Summary: Every 8 number of calendar is invisible Product: kdeplasma-addons Version: 5.11.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: fuzzy-clock Assignee: plasma-b...@kde.org Reporter: jsbm...@gmail.com Target Milestone: --- Created attachment 109278 --> https://bugs.kde.org/attachment.cgi?id=109278&action=edit Bug with missing number 8 Steps to reproduce: 1. Add digital clock widget 1.2. Add holidays in settings 2. Click on clock and open calendar 3. Click on 8 date (28 also works) 4. No number 8 P.S. wrong component in the bug summary? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 387749] Every 8 number of calendar is invisible
https://bugs.kde.org/show_bug.cgi?id=387749 Dmitry Vakhnin changed: What|Removed |Added CC||jsbm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387748] Regression: Kdevelop no longer parses/renders doxygen (javadoc) comments
https://bugs.kde.org/show_bug.cgi?id=387748 Francis Herne changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||m...@flherne.uk Resolution|--- |DUPLICATE --- Comment #2 from Francis Herne --- This was disabled in 5.2.1, because it triggers a bug in libclang [1] that causes KDevelop to crash. When that problem is fixed upstream it can be re-enabled. [1] https://bugs.llvm.org/show_bug.cgi?id=35333 *** This bug has been marked as a duplicate of bug 387279 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387279] Doxygen highlighting does not work
https://bugs.kde.org/show_bug.cgi?id=387279 Francis Herne changed: What|Removed |Added CC||spalmr...@gmail.com --- Comment #3 from Francis Herne --- *** Bug 387748 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387748] Regression: Kdevelop no longer parses/renders doxygen (javadoc) comments
https://bugs.kde.org/show_bug.cgi?id=387748 --- Comment #1 from Staffan Palmroos --- Created attachment 109277 --> https://bugs.kde.org/attachment.cgi?id=109277&action=edit The exact same code in Kdevelop 5.1.1 formatted and rendered properly in the tooltip -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387748] New: Regression: Kdevelop no longer parses/renders doxygen (javadoc) comments
https://bugs.kde.org/show_bug.cgi?id=387748 Bug ID: 387748 Summary: Regression: Kdevelop no longer parses/renders doxygen (javadoc) comments Product: kdevelop Version: 5.2.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Documentation viewer Assignee: kdevelop-bugs-n...@kde.org Reporter: spalmr...@gmail.com Target Milestone: --- Created attachment 109276 --> https://bugs.kde.org/attachment.cgi?id=109276&action=edit Unparsed doxygen comment in the tooltip. In Kdevelop 5.1.1 doxygen comments were parsed and properly rendered in the tooltips when hovering over your types (See pictures). In version 5.2.1 it just shows the raw text without formatting, which is a regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387725] Ugly brush dabs when painting on 1-channel layers (ie Masks, Fill Layer) with a Build-Up brush
https://bugs.kde.org/show_bug.cgi?id=387725 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #3 from wolthera --- Can confirm here. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387745] Shift button breaking Hold-Space (pan, etc.) controls
https://bugs.kde.org/show_bug.cgi?id=387745 --- Comment #2 from remirosent...@gmail.com --- (In reply to Scott Petrovic from comment #1) > Shift + Space is a shortcut for rotating the canvas. Could you clarify a > little more? The moment I press down shift, it breaks rotating as well as panning and zooming. For example if I try to use shift + space while dragging with my pen, it will draw instead of rotating. I am likely to use shift to change the pen size or rotate which makes this a major problem. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 387446] Build fails with Qt 5.10
https://bugs.kde.org/show_bug.cgi?id=387446 Andrea Scarpino changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370278] Device notifier loses setting changes after logout
https://bugs.kde.org/show_bug.cgi?id=370278 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #5 from Alexander Mentyu --- Can't confirm this bug in: Distribution: KDE neon Developer Edition - Stable Branches Plasma: 5.11.4 Frameworks: 5.41.0 Qt: 5.9.3 Kernel 4.10.0-40-generic Also tried 'Configure Removable Devices' settings -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 384711] Window grows larger and larger after every debugging session
https://bugs.kde.org/show_bug.cgi?id=384711 --- Comment #3 from tuxtor...@openmailbox.org --- I did some testing, and it looks like it comes from the toolviews, specifically from the bottom one. I attached a commented testing session with the different actions I made. The Bottom Toolbar has a constraint on its size driven by the size of the names of the tools it is showing. Plus an extra empty space on the right. Where the left and right toolbars can overflow, the bottom one can't, so it resizes the whole window and forces it to follow its constraints. Furthermore, when changing modes (main/debug/execute/…), the Toolbox statuses aren't saved completely (saved when «right click>Tool View Position>…» but not when «right click>Remove Tool View» and «right click>…(add tool view)»), and when changing modes back, some tools change to other toolboxes, making them grow suddenly. So the ideal case would be to always remember where the tools where, and to be able to overflow the bottom toolbox too, or even better, wrap the tools, in all of the toolboxes. In the code, I came across this code block: kdevelop/kdevplatform/sublime/idealbuttonbarwidget.cpp: 164-170 //apol: here we set the usual width of a button for the vertical toolbars as the minimumWidth //this is done because otherwise when we remove all the buttons and re-add new ones we get all //the screen flickering. This is solved by not defaulting to a smaller width when it's empty int w = button->sizeHint().width(); if (orientation() == Qt::Vertical && w > minimumWidth()) { setMinimumWidth(w); } Even though it is talking about the vertical bars, it's the minimumWidth that is set. There might be a link between this code and the strange behaviour. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 384711] Window grows larger and larger after every debugging session
https://bugs.kde.org/show_bug.cgi?id=384711 --- Comment #2 from tuxtor...@openmailbox.org --- Created attachment 109275 --> https://bugs.kde.org/attachment.cgi?id=109275&action=edit Commented test output Launched KDevelop from the shell and commented and detailed it's output. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 387746] Please add a disable button to kactivitymanagerd
https://bugs.kde.org/show_bug.cgi?id=387746 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- You can mark an activity as private / incognito in activity settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387747] New: desktop freeze
https://bugs.kde.org/show_bug.cgi?id=387747 Bug ID: 387747 Summary: desktop freeze Product: plasmashell Version: 5.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ar...@m-a-g.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.13.0-19-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: I was trying to use the kde-connect browse remote filesystem to browse my phone with dolhin4 from desktop -- 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 0x7f48c3202900 (LWP 3881))] Thread 9 (Thread 0x7f47e6f09700 (LWP 10039)): #0 0x7f48bc12264b in futex_reltimed_wait_cancelable (private=, reltime=0x7f47e6f08b50, expected=0, futex_word=0x563164e68d80) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f48bc12264b in __pthread_cond_wait_common (abstime=0x7f47e6f08c10, mutex=0x563164e68d30, cond=0x563164e68d58) at pthread_cond_wait.c:533 #2 0x7f48bc12264b in __pthread_cond_timedwait (cond=0x563164e68d58, mutex=0x563164e68d30, abstime=0x7f47e6f08c10) at pthread_cond_wait.c:667 #3 0x7f48bcd4a588 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f48bcd457cc in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f48bcd4929d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f48bc11b7fc in start_thread (arg=0x7f47e6f09700) at pthread_create.c:465 #7 0x7f48bc64bb0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f47f7c43700 (LWP 9349)): #0 0x7f48bc63f901 in __GI___poll (fds=0x7f47f0004f30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f48b7272169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f48b727227c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f48bcf7f49b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f48bcf24e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f48bcd443ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f48c0a3a846 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f48bcd4929d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f48bc11b7fc in start_thread (arg=0x7f47f7c43700) at pthread_create.c:465 #9 0x7f48bc64bb0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f4807ff7700 (LWP 8133)): #0 0x7f48b72b75d4 in g_mutex_unlock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f48b7271698 in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f48b727209b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f48b727227c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f48bcf7f49b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f48bcf24e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f48bcd443ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f48bcd4929d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f48bc11b7fc in start_thread (arg=0x7f4807ff7700) at pthread_create.c:465 #9 0x7f48bc64bb0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f489778b700 (LWP 6139)): #0 0x7f48bc122072 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f48c29ddfb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f48bc122072 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f48c29ddf68, cond=0x7f48c29ddf90) at pthread_cond_wait.c:502 #2 0x7f48bc122072 in __pthread_cond_wait (cond=0x7f48c29ddf90, mutex=0x7f48c29ddf68) at pthread_cond_wait.c:655 #3 0x7f48c26e9bd4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f48c26e9c19 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f48bc11b7fc in start_thread (arg=0x7f489778b700) at pthread_create.c:465 #6 0x7f48bc64bb0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f48a238f700 (LWP 5244)): #0 0x7f48b7271927 in g_main_context_query () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f48b72720e7 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f48b727227c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f48bcf7f49b in QEventDispatcherGlib:
[partitionmanager] [Bug 387743] When looking at my swap used it shows the home used
https://bugs.kde.org/show_bug.cgi?id=387743 --- Comment #7 from Andrius Štikonas --- (In reply to auronhines from comment #6) > (In reply to Andrius Štikonas from comment #4) > > I guess they'll upgrade soon after Ubuntu 18.04 LTS is released. > > > > It was a bit unfortunate that Debian/Ubuntu were lagging in packaging new > > versions of KPM for a while. But now they have caught up. > > Thing is they're gonna stop using KDE after 18.3 so i want to add the > programs to the repository I did't think they'll stop syncing programs from Ubuntu. They'll just not make KDE ISO spin. Or am I wrong? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378281] column width in messages list view not retained
https://bugs.kde.org/show_bug.cgi?id=378281 ka...@iki.fi changed: What|Removed |Added CC||ka...@iki.fi --- Comment #1 from ka...@iki.fi --- Can confirm this bug in two different computers after upgrading from openSUSE Leap 42.2 to Leap 42.3. The column widths in the classic (traditional) list view are not retained after a restart. The column widths must be adjusted manually after every restart. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375474] Renaming People Tag Causes Unpredictable Sort Order
https://bugs.kde.org/show_bug.cgi?id=375474 --- Comment #5 from hardy.pub...@gmail.com --- Created attachment 109273 --> https://bugs.kde.org/attachment.cgi?id=109273&action=edit Before rename. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 387743] When looking at my swap used it shows the home used
https://bugs.kde.org/show_bug.cgi?id=387743 --- Comment #6 from auronhi...@gmail.com --- (In reply to Andrius Štikonas from comment #4) > I guess they'll upgrade soon after Ubuntu 18.04 LTS is released. > > It was a bit unfortunate that Debian/Ubuntu were lagging in packaging new > versions of KPM for a while. But now they have caught up. Thing is they're gonna stop using KDE after 18.3 so i want to add the programs to the repository -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375474] Renaming People Tag Causes Unpredictable Sort Order
https://bugs.kde.org/show_bug.cgi?id=375474 --- Comment #6 from hardy.pub...@gmail.com --- Created attachment 109274 --> https://bugs.kde.org/attachment.cgi?id=109274&action=edit After rename. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 387743] When looking at my swap used it shows the home used
https://bugs.kde.org/show_bug.cgi?id=387743 --- Comment #5 from auronhi...@gmail.com --- (In reply to Andrius Štikonas from comment #4) > I guess they'll upgrade soon after Ubuntu 18.04 LTS is released. > > It was a bit unfortunate that Debian/Ubuntu were lagging in packaging new > versions of KPM for a while. But now they have caught up. Thing is they're gonna stop using KDE after 18.3 so i want to add the programs to the repository -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375474] Renaming People Tag Causes Unpredictable Sort Order
https://bugs.kde.org/show_bug.cgi?id=375474 --- Comment #4 from hardy.pub...@gmail.com --- Yes, still there. Example of Albert renamed to Alberto attached. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385630] Views Requiring Maps Takes ~30s to Launch
https://bugs.kde.org/show_bug.cgi?id=385630 --- Comment #15 from hardy.pub...@gmail.com --- Yes, it' still there. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383203] I have some inspirations from my favorite paid(!) application
https://bugs.kde.org/show_bug.cgi?id=383203 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WAITINGFORINFO --- Comment #3 from caulier.gil...@gmail.com --- Please give a feedback here... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 387744] Plasma Discover doesn't honour pinned packages
https://bugs.kde.org/show_bug.cgi?id=387744 Nate Graham changed: What|Removed |Added Component|discover|PackageKit CC||pointedst...@zoho.com --- Comment #1 from Nate Graham --- Discover interacts with PackageKit, and doesn't touch apt directly. So it's likely that this is an upstream PackageKit feature request, but I'll let Aleix make that determination. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 371635] Unable to use keyboard only to process imported photos
https://bugs.kde.org/show_bug.cgi?id=371635 --- Comment #3 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 367784] Thumbnails Disappear After Tagging
https://bugs.kde.org/show_bug.cgi?id=367784 --- Comment #4 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376426] Exit Full Screen does not restore maximized window
https://bugs.kde.org/show_bug.cgi?id=376426 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374783] Window location is not restored correctly after restart
https://bugs.kde.org/show_bug.cgi?id=374783 --- Comment #6 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374355] Video preview lags in the beginning
https://bugs.kde.org/show_bug.cgi?id=374355 --- Comment #29 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 386188] Preview Does Not Display Some JPGs Editor Crashes Program
https://bugs.kde.org/show_bug.cgi?id=386188 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382688] tag cannot be shown in photo's metadata
https://bugs.kde.org/show_bug.cgi?id=382688 --- Comment #1 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372041] "Add Folders" attempts to import parent directory AND target dir.
https://bugs.kde.org/show_bug.cgi?id=372041 --- Comment #1 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379081] GPS data are in file but geolocation indicator is not shown and map view empty
https://bugs.kde.org/show_bug.cgi?id=379081 --- Comment #6 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383020] Only one GPS bookmark can be saved
https://bugs.kde.org/show_bug.cgi?id=383020 --- Comment #3 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385630] Views Requiring Maps Takes ~30s to Launch
https://bugs.kde.org/show_bug.cgi?id=385630 --- Comment #14 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375474] Renaming People Tag Causes Unpredictable Sort Order
https://bugs.kde.org/show_bug.cgi?id=375474 --- Comment #3 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 386653] Message error on face detectior
https://bugs.kde.org/show_bug.cgi?id=386653 --- Comment #10 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375945] Face detection not scanning my images
https://bugs.kde.org/show_bug.cgi?id=375945 --- Comment #5 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383078] After selecting photo and clicking sendmail no photo is attached to email
https://bugs.kde.org/show_bug.cgi?id=383078 --- Comment #6 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375424] Thumbnails are not being removed from AlbumsView after moving the images to Trash
https://bugs.kde.org/show_bug.cgi?id=375424 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Version Fixed In||5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379986] Cannot add collection
https://bugs.kde.org/show_bug.cgi?id=379986 --- Comment #2 from caulier.gil...@gmail.com --- Note : there is an option in Setup/misc config panel to use native file dialog instead Qt one. By this way you will see all mount point from Windows. Please test and feedback. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379986] Cannot add collection
https://bugs.kde.org/show_bug.cgi?id=379986 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384934] Install failed on Windows 10
https://bugs.kde.org/show_bug.cgi?id=384934 --- Comment #3 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 371840] crashes while editing pictures meta data or rotating the picture
https://bugs.kde.org/show_bug.cgi?id=371840 --- Comment #7 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377444] C++ runtime error
https://bugs.kde.org/show_bug.cgi?id=377444 --- Comment #3 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 380148] Windows installer causes BSOD during "Close Conflicting Programs"
https://bugs.kde.org/show_bug.cgi?id=380148 --- Comment #2 from caulier.gil...@gmail.com --- This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 387746] New: Please add a disable button to kactivitymanagerd
https://bugs.kde.org/show_bug.cgi?id=387746 Bug ID: 387746 Summary: Please add a disable button to kactivitymanagerd Product: kactivitymanagerd Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: dib...@wp.pl CC: plasma-b...@kde.org Target Milestone: --- Please add a disable button to the system settings if you want to collect the data using kactivitymanagerd. Recent opened files, videos, images in task bar context menu is a big NO NO for my privacy. I must stop this service manually from command line -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387745] Shift button breaking Hold-Space (pan, etc.) controls
https://bugs.kde.org/show_bug.cgi?id=387745 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- Shift + Space is a shortcut for rotating the canvas. Could you clarify a little more? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 Germano Massullo changed: What|Removed |Added CC|germano.massu...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #257 from Dngrsone --- MEgg, The instructions are in comment 214. I can try to make it a little more understandable, but it boils down to the reader having some understanding of the workings of Linux and KDE: 1) Switch the pager from a Virtual Desktop (VD) to an Activity pager: - unlock the taskbar - right click on the pager - select the "Alternatives..." menu entry - click "Activity Pager" and then the "Switch" button => now the pager tracks activities While there, right click on the pager again, select "Activity Pager Settings..." and configure to taste. 2) Move to a single Virtual Desktop, so each Activity = 1 VD = 1 screen - System Settings => Desktop Behavior => Virtual Desktops, reduce to 1. 3) Create as many activities as you need "screens" (same number as the qty of VDs you used to use); - System Settings => Desktop Behavior => Activities, create and name as needed. Now you see the Activities in your pager, and from the pager point of view it's as before except activities replaced VDs. 4) Enable the mouse wheel to switch between activities - Right click on the desktop background => Configure Desktop - Select the "Mouse Actions" tab - Item "Vertical-Scroll", select "Switch Activity" IMPORTANT: this setting is per activity. So you need to repeat this for all the created activities. If you want to switch between Activities using your keyboard, use meta+Tab and meta+Shift+Tab. Or, as I did: a right-click on the desktop, go to Activities, and then Settings, and change these shortcuts to Ctrl+Alt+[Right arrow] and Ctrl+Alt+[Left arrow]. These are the commands I used to use back in the earlier times to page between Virtual Desktops. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 303062] Add image direction in Map module (from EXIF of geotagging pictures with compass heading))
https://bugs.kde.org/show_bug.cgi?id=303062 Milan Knížek changed: What|Removed |Added CC||kni...@volny.cz --- Comment #7 from Milan Knížek --- Mee too - Eric described it very well! I got the Solmeta MAX-EOS but I use it only as a logger on my Olympus camera (Solmeta supports only Nikon & Canon) - the data are stored as NMEA log. Apart from digiKam not handling the GPSImgDirection tag yet, there is a problem that GPX standard does not define heading at all (older version did define course, but that's not the same as heading). So digiKam should allow to GPS Correlate also from other file types (various NMEA data, possibly others). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 387739] PlasmaComponents3.ComboBox [master version] creates a crash....
https://bugs.kde.org/show_bug.cgi?id=387739 Michail Vourlakos changed: What|Removed |Added Component|components |general Product|frameworks-plasma |frameworks-qqc2-desktop-sty ||le CC||k...@davidedmundson.co.uk Version|unspecified |5.40.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387745] New: Shift button breaking Hold-Space (pan, etc.) controls
https://bugs.kde.org/show_bug.cgi?id=387745 Bug ID: 387745 Summary: Shift button breaking Hold-Space (pan, etc.) controls Product: krita Version: 3.2.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: remirosent...@gmail.com Target Milestone: --- On 3.3.2 as well. When I press or hold shift it breaks the ability to use the space key with the mouse to pan, rotate or zoom, and vice versa. It acts as if I am not holding the modifier down. It is usable again after focusing a different window, or switching brushes or layers. Sometimes ctrl breaks space as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387742] Window class string in window-specific settings is saved in lower case
https://bugs.kde.org/show_bug.cgi?id=387742 --- Comment #1 from Martin Flöser --- I understand why that happens: we used to convert window classes to lower case internally. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387741] kwin crashes.
https://bugs.kde.org/show_bug.cgi?id=387741 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Flags||NVIDIA+ Resolution|--- |UPSTREAM --- Comment #1 from Martin Flöser --- Crash happens in the proprietary Nvidia driver. Please report to Nvidia. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 387744] New: Plasma Discover doesn't honour pinned packages
https://bugs.kde.org/show_bug.cgi?id=387744 Bug ID: 387744 Summary: Plasma Discover doesn't honour pinned packages Product: Discover Version: 5.10.5 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: tomhut...@aim.com Target Milestone: --- To use firefox 57.1 from Debian/sid, I have set up apt pinning to restrict all packages except firefox to Debian/buster: Package: * Pin: release o=Debian,a=buster Pin-Priority: 900 Package: firefox Pin: release o=Debian,a=sid Pin-Priority: 1000 While aptitude shows me no packages to update, Plasma Discover shows all newer packages from sid as upgradable. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 387743] When looking at my swap used it shows the home used
https://bugs.kde.org/show_bug.cgi?id=387743 --- Comment #4 from Andrius Štikonas --- I guess they'll upgrade soon after Ubuntu 18.04 LTS is released. It was a bit unfortunate that Debian/Ubuntu were lagging in packaging new versions of KPM for a while. But now they have caught up. -- You are receiving this mail because: You are watching all bug changes.