[kwin] [Bug 352019] Qt5 drag pixmaps lag behind mouse cursor
https://bugs.kde.org/show_bug.cgi?id=352019 --- Comment #43 from alfa...@gmx.de --- > Do you mean the slight lag of like couple pixels? About the same as Window > drag? Yes, just a couple of pixels. A few days ago I've tested nouveau and noticed no "lag" but as 3D performance is "non-existent", I've switched back to proprietary driver :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 352019] Qt5 drag pixmaps lag behind mouse cursor
https://bugs.kde.org/show_bug.cgi?id=352019 --- Comment #42 from Artur O.--- (In reply to alfaflo from comment #41) > (In reply to alfaflo from comment #38) > > latest update (plasma 5.6 & qt 5.6) fixed it for me > > by the way: plasma is now smooth like never before - thanks guys! > > > > florian > > An additional note: it seems that it's not fully gone. Compared to using > noveau there's still a (very) little "lag" but I think for daily use it's > not a problem. Do you mean the slight lag of like couple pixels? About the same as Window drag? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 352019] Qt5 drag pixmaps lag behind mouse cursor
https://bugs.kde.org/show_bug.cgi?id=352019 --- Comment #41 from alfa...@gmx.de --- (In reply to alfaflo from comment #38) > latest update (plasma 5.6 & qt 5.6) fixed it for me > by the way: plasma is now smooth like never before - thanks guys! > > florian An additional note: it seems that it's not fully gone. Compared to using noveau there's still a (very) little "lag" but I think for daily use it's not a problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 352019] Qt5 drag pixmaps lag behind mouse cursor
https://bugs.kde.org/show_bug.cgi?id=352019 --- Comment #40 from alfa...@gmx.de --- (In reply to alfaflo from comment #38) > latest update (plasma 5.6 & qt 5.6) fixed it for me > by the way: plasma is now smooth like never before - thanks guys! > > florian An additional note: it seems that it's not fully gone. Compared to using noveau there's still a (very) little "lag" but I think for daily use it's not a problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 Gilboa Davarachanged: What|Removed |Added CC||gilb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361073] New: Session Logout and Session Switch User (from application launcher) get wrong position on the dialog.
https://bugs.kde.org/show_bug.cgi?id=361073 Bug ID: 361073 Summary: Session Logout and Session Switch User (from application launcher) get wrong position on the dialog. Product: plasmashell Version: 5.6.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: commander.alch...@gmail.com CC: plasma-b...@kde.org Since the 5.6 update; session Logout dialog appears lower left of my primary monitor. session switch user appears on the lower right of my primary monitor. I have 3 monitors, (Portrait 1080x1920, Landscape 1920x1080, Landscape 1920x1080) It seems that Logout appears trying to center between screen 0 and 1, while switch user trying to center between them all and failing since the portrait monitor is taller. Reproducible: Always Steps to Reproduce: 1. Have asymmetric screen setup, ie portrait and landscape screen setup. 2. Click Leave - > Session Logout or Leave -> Session Switch User. 3. Dialog does not appear centered on primary monitor like it would before. Actual Results: Wrong position. Expected Results: Centered on primary monitor. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kitemmodels] [Bug 352369] KSelectionProxyModel bug
https://bugs.kde.org/show_bug.cgi?id=352369 Stephen Kellychanged: What|Removed |Added Latest Commit||http://commits.kde.org/kite ||mmodels/0cf75268b00decc0ecb ||e75ba905d7bc556dcca26 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Stephen Kelly --- Git commit 0cf75268b00decc0ecbe75ba905d7bc556dcca26 by Stephen Kelly. Committed on 28/03/2016 at 05:09. Pushed by skelly into branch 'master'. KSPM: Recreate mapping on removal only if needed Previously, the model would create a mapping for the wrong index while processing removal. Constrain the re-creation of the mapping by determining at AboutToBe-time whether to re-create it. This is important because the mapping contains QPersistentModelIndexes to the source model, and when post-processing the removal, that is already invalidated. M +6-1src/kselectionproxymodel.cpp http://commits.kde.org/kitemmodels/0cf75268b00decc0ecbe75ba905d7bc556dcca26 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 361072] New: krunner crashed when attempting to start konsole
https://bugs.kde.org/show_bug.cgi?id=361072 Bug ID: 361072 Summary: krunner crashed when attempting to start konsole 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.6.0-rc1 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: when attempting to start konsole via alt-F2 after restarting a KDE plasma session following updates, krunner crashed and konsole did not start. 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 0x7f90be01b7c0 (LWP 23146))] Thread 12 (Thread 0x7f90bd959700 (LWP 23147)): #0 0x0030004dfe4d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00300340a382 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7f90bd958d00) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 0x00300340a382 in _xcb_conn_wait (c=c@entry=0x2522470, cond=cond@entry=0x25224b0, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:459 #3 0x00300340bff7 in xcb_wait_for_event (c=0x2522470) at ../../src/xcb_in.c:693 #4 0x7f90bddb8789 in QXcbEventReader::run() (this=0x25354c0) at qxcbconnection.cpp:1230 #5 0x0030174a57fe in QThreadPrivate::start(void*) (arg=0x25354c0) at thread/qthread_unix.cpp:331 #6 0x003000c07454 in start_thread (arg=0x7f90bd959700) at pthread_create.c:334 #7 0x0030004e8edd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f90b4973700 (LWP 23151)): #0 0x003000c0d04f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f90b79b3c43 in radeon_drm_cs_emit_ioctl (mtx=0x2618f40, cond=0x2618f68) at ../../../../../../../include/c11/threads_posix.h:159 #2 0x7f90b79b3c43 in radeon_drm_cs_emit_ioctl (sema=0x2618f40) at ../../../../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 0x7f90b79b3c43 in radeon_drm_cs_emit_ioctl (param=param@entry=0x2618bf0) at ../../../../../../../src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:653 #4 0x7f90b79b3397 in impl_thrd_routine (p=) at ../../../../../../../include/c11/threads_posix.h:87 #5 0x003000c07454 in start_thread (arg=0x7f90b4973700) at pthread_create.c:334 #6 0x0030004e8edd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f90b2fd8700 (LWP 23153)): #0 0x00300408ea70 in g_mutex_lock (mutex=mutex@entry=0x7f90ac000990) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthread-posix.c:1338 #1 0x003004049ae1 in g_main_context_query (context=context@entry=0x7f90ac000990, max_priority=2147483647, timeout=timeout@entry=0x7f90b2fd7cb4, fds=fds@entry=0x7f90ac003070, n_fds=n_fds@entry=1) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3544 #2 0x00300404a2a7 in g_main_context_iterate (context=context@entry=0x7f90ac000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3822 #3 0x00300404a43c in g_main_context_iteration (context=0x7f90ac000990, may_block=may_block@entry=1) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3901 #4 0x0030176dca5b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f90ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x003017683d6a in QEventLoop::exec(QFlags) (this=this@entry=0x7f90b2fd7de0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x0030174a0854 in QThread::exec() (this=) at thread/qthread.cpp:503 #7 0x0030476d5105 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x0030174a57fe in QThreadPrivate::start(void*) (arg=0x2956760) at thread/qthread_unix.cpp:331 #9 0x003000c07454 in start_thread (arg=0x7f90b2fd8700) at pthread_create.c:334 #10 0x0030004e8edd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f90a8d20700 (LWP 23289)): #0 0x003000c0d04f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x0030174a6a9b in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x288ed90) at thread/qwaitcondition_unix.cpp:136 #2 0x0030174a6a9b in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x27d39b0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f90b0ddb02b in
[plasmashell] [Bug 361071] New: Weather Forecast Widget - Cannot save configuration when loaded in system tray
https://bugs.kde.org/show_bug.cgi?id=361071 Bug ID: 361071 Summary: Weather Forecast Widget - Cannot save configuration when loaded in system tray Product: plasmashell Version: 5.6.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: aexoxea...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org (Apologies for placing in General; I'm not sure if this is a System Tray issue or a Widget issue. Will try to get back to you in a timely fashion for any info needed for re-assignment.) The Weather Forecast Widget is listed as an "Extra Item" that can be activated in the System Tray. However, it is not useful as there is no default weather station configuration, and a new weather station cannot be set; you can bring up the configuration dialog, search for and set a weather station, but the "Apply" button is never activated and the weather station is not saved when you select the "OK" button. This also applies to other settings (the update frequency and units). You also can't work around this by switching between the configuration modules, as the usual 'unsaved changes' prompt never shows. It's as though you've changed nothing, even though you have. The Widget can be configured fine when added directly to a panel, or to the desktop (both of which serve as workarounds), so it's just when activating it as a System Tray Extra Item. (If the Widget is not meant to be available as a System Tray Extra Item, then I'm happy for this bug to be closed once the configuration that causes it to be available there is removed; however, I will leave that to those who know whether this is intended or not.) Reproducible: Always Steps to Reproduce: 1. Create a panel and add a System Tray to it. 2. Access the System Tray Settings, "Entries" module, and enable "Weather Forecast". The Widget appears by default as a blank space in the System Tray. 3. Access Weather Forecast Settings for that Widget, either "Weather Station" or "Units" modules, and change one or more settings. Note that the "Apply" button does not activate. 4. Press the "OK" button. Note that the Widget does nothing. 5. Re-access Weather Forecast Settings for that Widget. Note that none of the settings that you changed were saved. Actual Results: Widget is not configured and does nothing; re-opening the configuration dialog shows changes not saved. Expected Results: Widget is configured and loads the weather for the specified weather station. plasmashell logs various warnings when accessing the Weather Forecast Widget's configuration dialog. There are two key differences to what happens when doing this for the Widget in the System Tray vs. the Widget directly on the panel/desktop, which may be relevant: (1) The following warnings are logged for Widget in System Tray which are NOT logged for Widget directly in Panel/Desktop: plasmashell: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/configWeatherStation.qml:63: TypeError: Cannot read property 'nativeInterface' of null plasmashell: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/AppletConfiguration.qml:75: TypeError: Cannot read property 'configuration' of null (2) The following warnings are logged for Widget directly in Panel/Desktop which are NOT logged for Widget in System Tray: plasmashell: Calling KPluginInfo::property("Name") is deprecated, use KPluginInfo::name() in "/usr/lib/qt/plugins/plasma/dataengine/ion_noaa.so" instead. plasmashell: Calling KPluginInfo::property("Name") is deprecated, use KPluginInfo::name() in "/usr/lib/qt/plugins/plasma/dataengine/ion_wettercom.so" instead. plasmashell: Calling KPluginInfo::property("Name") is deprecated, use KPluginInfo::name() in "/usr/lib/qt/plugins/plasma/dataengine/ion_envcan.so" instead. plasmashell: init() plasmashell: (...where is different each time.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356617] Primary display is not displayed in notification settings.
https://bugs.kde.org/show_bug.cgi?id=356617 --- Comment #6 from Artur O.--- (In reply to Artur O. from comment #5) > (In reply to Martin Klapetek from comment #3) > > Ok, the cause of the bug is the same as of bug 356461 (so fixing that one > > will fix this one). > > Arch just released plasma 5.5.1-1 and this issue seems to still be there. > > If you open notification settings it will first show up as portrait for me > but when i click over to "keyboard shortcuts" and then back it will be > landscape. There is also some strange behaviour when moving the settings > window. > > Here is a video since I think it will better display the issue at hand. > https://www.youtube.com/watch?v=9epQpiTBPrU Still applies for Plasma 5.6 and QT 5.6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356653] When notification appears for first time, it appears twice
https://bugs.kde.org/show_bug.cgi?id=356653 --- Comment #32 from Artur O.--- (In reply to Artur O. from comment #31) > (In reply to Martin Klapetek from comment #29) > > Sorry, add plasma-workspace 5.6 to the mix. > > Um has this gotten into main? Im still getting duplacate notifications about > unlocked widgets on Arch with (kf5 5.19) and (plasma 5.5.5). After Arch updated to Plasma 5.6 and QT 5.6 the issue is resolved for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 352019] Qt5 drag pixmaps lag behind mouse cursor
https://bugs.kde.org/show_bug.cgi?id=352019 --- Comment #39 from Artur O.--- (In reply to alfaflo from comment #38) > latest update (plasma 5.6 & qt 5.6) fixed it for me > by the way: plasma is now smooth like never before - thanks guys! > > florian (In reply to Thomas Lübking from comment #36) > Please see the referenced https://bugreports.qt.io/browse/QTBUG-48122 I can confirm this also. After Arch updated to QT 5.6 and Plasma 5.6 with the rest the issue is now fixed for me too. Looking at https://bugreports.qt.io/browse/QTBUG-48122 it seems it's not related to this issue or that it was somehow fixed by another issue in QT and that 48122 was not the "leading" cause of the lag. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 349422] [WACOM INTUOS] Tablet middle click loses functionality on window switch
https://bugs.kde.org/show_bug.cgi?id=349422 Raghavendra kamathchanged: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #6 from Raghavendra kamath --- For me this doesn't happen anymore in 3.0 latest git with qt 5.6 on linux. Can someone or the reporter check if this happens on windows? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 361070] New: No icon for .woff and wrong icon for .eot font files.
https://bugs.kde.org/show_bug.cgi?id=361070 Bug ID: 361070 Summary: No icon for .woff and wrong icon for .eot font files. Product: dolphin Version: 15.12.3 Platform: Archlinux Packages URL: http://i.imgur.com/HzywHxR.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: uri_herr...@nitrux.in Dolphin doesn't display an icon for .woff files and uses an unrelated icon for .eot files. I filed it against Dolphin but this happens in every other application. .woff font files mimetype is application/font-woff .eot font files mimetype is: application/vnd.ms-fontobject Using the file names for .woff files: 1. application-font-woff 2. application-x-font-woff Don't load an icon. And using this for e.ot files: 1. application-vnd.ms-fontobject Doesn't change the icon either. Reproducible: Always Steps to Reproduce: 1. Open Dolphin. 2. Got to a folder with .woff and .eot font files in it. 3. Actual Results: .woff font files don't have an icon. .eot font files use application-octet-stream. Expected Results: Font files would use an icon. Like I mentioned I've tried changing the names of files in the mimetypes folder to those above but nothing changes. Dolphin does seem to recognize .woff files as it displays information in the status bar about the file but it says unknown for .eot files. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 361070] No icon for .woff and wrong icon for .eot font files.
https://bugs.kde.org/show_bug.cgi?id=361070 Uri Herrerachanged: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 360687] Konqueror crashed on TVTropes page
https://bugs.kde.org/show_bug.cgi?id=360687 --- Comment #1 from m...@nightrealms.com --- Created attachment 98119 --> https://bugs.kde.org/attachment.cgi?id=98119=edit New crash information added by DrKonqi konqueror (4.14.17) on KDE Platform 4.14.18 using Qt 4.8.7 I'd opened a third tab at TV Tropes by middle-clicking a TV tropes link. -- Backtrace (Reduced): #6 0x7fcc183c2262 in DOM::CanvasContext2DImpl::getImageData(float, float, float, float, int&) () at /lib64/libkhtml.so.5 #7 0x7fcc1856546b in KJS::Context2DFunction::callAsFunction(KJS::ExecState*, KJS::JSObject*, KJS::List const&) () at /lib64/libkhtml.so.5 #8 0x7fcc17ba8de7 in KJS::Machine::runBlock(KJS::ExecState*, WTF::Vector const&, KJS::ExecState*) () at /lib64/libkjs.so.4 #9 0x7fcc17b8a8a0 in KJS::FunctionImp::callAsFunction(KJS::ExecState*, KJS::JSObject*, KJS::List const&) () at /lib64/libkjs.so.4 #10 0x7fcc17ba8de7 in KJS::Machine::runBlock(KJS::ExecState*, WTF::Vector const&, KJS::ExecState*) () at /lib64/libkjs.so.4 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 360687] Konqueror crashed on TVTropes page
https://bugs.kde.org/show_bug.cgi?id=360687 m...@nightrealms.com changed: What|Removed |Added CC||m...@nightrealms.com -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 340795] Browsing results "pages" does not work
https://bugs.kde.org/show_bug.cgi?id=340795 --- Comment #2 from Mehrdad Momeny--- (In reply to Ian Schwarz from comment #1) > Created attachment 89589 [details] > Removes "browsing" buttons, adds very basic "load" more functionality > > My efforts as of today. I have removed the dysfunctional browsing elements > and added a "load more tweets" button in their place. Note that as of now, > it only works the SECOND time it is pressed and it does not display an error > message etc. if there are no more tweets to be found. Also, older tweets are > added on top of the newer ones. I am finding out how to do that next. Thanks for sharing your efforts. However, we use KDE review board[1] to review and apply patches. Also, please submit a finalized patch. [1] https://git.reviewboard.kde.org/r/ -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 361069] OTR fingerprint verification does not stay set to yes.
https://bugs.kde.org/show_bug.cgi?id=361069 --- Comment #1 from octo--- Forgot to mention that I am using the plasma widget "Instant messaging" -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 361069] New: OTR fingerprint verification does not stay set to yes.
https://bugs.kde.org/show_bug.cgi?id=361069 Bug ID: 361069 Summary: OTR fingerprint verification does not stay set to yes. Product: telepathy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: text-ui Assignee: kde-telepathy-b...@kde.org Reporter: octo...@charter.net When i verify a fingerprint for someone in the OTR setting, after I close the chat window, the verification for that person changed to no. The fingerprint is still in there but I have to go through the menus and re verify every time. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361068] New: Icon for Kdevelop
https://bugs.kde.org/show_bug.cgi?id=361068 Bug ID: 361068 Summary: Icon for Kdevelop Product: kdevelop Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI: all modes Assignee: kdevelop-bugs-n...@kde.org Reporter: ad...@mail.csuchico.edu Created attachment 98118 --> https://bugs.kde.org/attachment.cgi?id=98118=edit The taskbar on the left shows just a question mark I have built Kdvelop from source by following http://kfunk.org/2016/02/16/building-kdevelop-5-from-source-on-ubuntu-15-10/ on m Ubuntu but after starting the application I cannot see the Icon instead a question mark icon appears. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 361067] New: krusader ignores icon size from its settings
https://bugs.kde.org/show_bug.cgi?id=361067 Bug ID: 361067 Summary: krusader ignores icon size from its settings Product: krusader Version: 2.4.0-beta3 "Single Step" Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@fork.pl Reporter: bugzi...@kerridis.de It doesn't matter which icon size I use in krusader's settings, it is ignored, krusader (root, user) always uses the same small icon size. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361066] New: [Feature Request] GTK+ 3.20 support
https://bugs.kde.org/show_bug.cgi?id=361066 Bug ID: 361066 Summary: [Feature Request] GTK+ 3.20 support Product: Breeze Version: 5.6.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: gtk theme Assignee: scionicspec...@gmail.com Reporter: jeffbaich...@gmail.com Breeze GTK+ theme is currently unsupported on GTK+ 3.20, and layouts do break. Maybe it is related to this change in GTK+ theming framework as described below... https://blogs.gnome.org/mclasen/2015/11/20/a-gtk-update/ I can provide screenshots if needed. Reproducible: Always Steps to Reproduce: 1. Set GTK+ theme to Breeze 2. Run a GTK+ 3 application (GTK+ 2 works fine of course) 3. Being shocked by broken layouts... broken everything -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 360120] Show Desktop Applet corrupts panel when added to it (spacing issues)
https://bugs.kde.org/show_bug.cgi?id=360120 Kai Uwe Broulikchanged: What|Removed |Added CC||christian.hersevoort@gmail. ||com CC||alexander.schmiec...@gmx.ne ||t --- Comment #7 from Kai Uwe Broulik --- *** Bug 361065 has been marked as a duplicate of this bug. *** --- Comment #8 from Kai Uwe Broulik --- *** Bug 361063 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 360120] Show Desktop Applet corrupts panel when added to it (spacing issues)
https://bugs.kde.org/show_bug.cgi?id=360120 Kai Uwe Broulikchanged: What|Removed |Added CC||christian.hersevoort@gmail. ||com --- Comment #7 from Kai Uwe Broulik --- *** Bug 361065 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361065] "Show Desktop" widget breaks panel and has no icon
https://bugs.kde.org/show_bug.cgi?id=361065 Kai Uwe Broulikchanged: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #3 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 360120 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361065] "Show Desktop" widget breaks panel and has no icon
https://bugs.kde.org/show_bug.cgi?id=361065 --- Comment #2 from Christian Hersevoort--- Thanks for your quick response! No problem, I'm glad it's already fixed! I couldn't find this bug in the tracker, so sorry if this is a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5
https://bugs.kde.org/show_bug.cgi?id=345307 Ivo Raisrchanged: What|Removed |Added Attachment #97556|0 |1 is obsolete|| --- Comment #16 from Ivo Raisr --- Created attachment 98117 --> https://bugs.kde.org/attachment.cgi?id=98117=edit patch for Linux and Solaris calling __gnu_cxx::__freeres from libstdc++ (v2) Patch for Linux and Solaris calling __gnu_cxx::__freeres from libstdc++ (v2). Addresses review comment by Mark - freeres wrappers have been consolidate into one. I tested Linux x86/amd64 architectures. Please test other architectures on Linux as necessary. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361065] "Show Desktop" widget breaks panel and has no icon
https://bugs.kde.org/show_bug.cgi?id=361065 Kai Uwe Broulikchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- That's fixed in 5.6.1 due this week. Sorry for the inconvenience. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361065] "Show Desktop" widget breaks panel and has no icon
https://bugs.kde.org/show_bug.cgi?id=361065 Christian Hersevoortchanged: What|Removed |Added CC||christian.hersevoort@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 94470] unilaterally violate the NETWM spec to support inner xinerama struts
https://bugs.kde.org/show_bug.cgi?id=94470 HDHZchanged: What|Removed |Added CC||hdhochz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361064] New: the search applet (KRunner) does not accept input from keyboard
https://bugs.kde.org/show_bug.cgi?id=361064 Bug ID: 361064 Summary: the search applet (KRunner) does not accept input from keyboard Product: plasmashell Version: 5.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Milou Assignee: m...@vhanda.in Reporter: alexander.schmiec...@gmx.net CC: plasma-b...@kde.org Worked before. KRunner does not accept keyboard entries. Shows single character after typing the character >50 times. Search works as expected in K-Menu and Dolphin, respectively. Reproducible: Always Steps to Reproduce: 1. open KRunner (ALT-F2) 2. try to type Actual Results: Keyboard entries were not accepted by KRunner (or only very slowly) Expected Results: Keyboard entries accepted. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 360435] CSV Importer doesn't recognize security if its symbol isn't lower case
https://bugs.kde.org/show_bug.cgi?id=360435 --- Comment #11 from allan--- Are you sure about the change to csvwizard.cpp? As far as I can see, with "exists = false;" in the while loop, it works correctly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361063] New: taskpanel / control bar screwed up after trying to insert "show desktop" plasmoid
https://bugs.kde.org/show_bug.cgi?id=361063 Bug ID: 361063 Summary: taskpanel / control bar screwed up after trying to insert "show desktop" plasmoid Product: plasmashell Version: 5.6.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: alexander.schmiec...@gmx.net taskpanel / control bar shows senseless content after insertion of the "show desktop" plasmoid Reproducible: Always Steps to Reproduce: 1. unlock mini programs 2. add mini program 3. select "show desktop" plasmoid and try to add it to the panel Actual Results: taskpanel / control bar shows senseless content. The only way go get rid of it is to delete the panel. Expected Results: "show desktop" icon smoothly integrated in panel. -- You are receiving this mail because: You are watching all bug changes.
[ksystraycmd] [Bug 361062] New: kradio4 Tray Icon Doesn't Open KRadio4
https://bugs.kde.org/show_bug.cgi?id=361062 Bug ID: 361062 Summary: kradio4 Tray Icon Doesn't Open KRadio4 Product: ksystraycmd Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: vtp...@myfairpoint.net My update to 16.04, from 15.10, broke RadioTray. I uploaded and am trying KRadio4. Am noticing that when I close all windows and depend on the Kradio4 Panel Icon, clicking on "Open Kradio4" doesn't work. This means that if I want to change a station (I listen to Internet Radio), I have to killall, then restart KRadio4. I haven't found any other way, yet, to "re-invoke" the KRadio4 dialog window. Reproducible: Always Steps to Reproduce: 1. Start KRadio4 2. Pick a station. Close all Windows. 3. Try to "open" KRadio4 from the tray Icon. Actual Results: Nothing happens. Expected Results: Opens the KRadio4 dialog window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361059] Lazarus-Ide Crash
https://bugs.kde.org/show_bug.cgi?id=361059 Thomas Lübkingchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Thomas Lübking --- This is a crash from a scripted effect for a closing window. Unfortunately, libQt5Script is not compiled with debug symbols, so we cannot say what the bug is. If you can reproduce the crash, we can investigate what causes it - otherwise it could be just as much cosmic rays ;-) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 358557] "Online services" menu is empty
https://bugs.kde.org/show_bug.cgi?id=358557 Alexander Potashevchanged: What|Removed |Added CC||aspotas...@gmail.com --- Comment #7 from Alexander Potashev --- I also want a message in place of empty menu. What does RESOLVED::REMIND mean? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361061] New: Drawing assistant partially not working
https://bugs.kde.org/show_bug.cgi?id=361061 Bug ID: 361061 Summary: Drawing assistant partially not working Product: krita Version: 2.9.11 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: katy.le...@live.fr I don't get the directing lines when using the assistants, making it very hard to use as I have no clue as to where my lines will be drawn. What's more, when using assistants, I get some noise gosts brush strokes all over my page even when my tablet pen doesn't touch the tablet and is just hovering over it. System is Windows 7 64 bits. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kitemmodels] [Bug 352369] KSelectionProxyModel bug
https://bugs.kde.org/show_bug.cgi?id=352369 Stephen Kellychanged: What|Removed |Added Assignee|kdelibs-b...@kde.org|steve...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361060] New: Configuration dialog section name "General" is not translatable
https://bugs.kde.org/show_bug.cgi?id=361060 Bug ID: 361060 Summary: Configuration dialog section name "General" is not translatable 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 The name of tab "General" in weather widget's configuration dialog is not translatable. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361059] New: Lazarus-Ide Crash
https://bugs.kde.org/show_bug.cgi?id=361059 Bug ID: 361059 Summary: Lazarus-Ide Crash Product: kwin Version: 5.4.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: abta...@comcast.net Application: kwin_x11 (5.4.2) Qt Version: 5.4.2 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: I was editing in Lazarus-ide 1.6.0, SourceEditor when the crash occurred. I was doing some simple editing removing unwanted parens markers around parameters in if-then statements. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f47f189d840 (LWP 2036))] Thread 3 (Thread 0x7f47d2bb0700 (LWP 2052)): #0 0x7f47f13a46f3 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f47ef9f590f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f47ef9f740e in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f47ef9f793e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f47ef9a075a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f47ef7be3d4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f47ea32cf85 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f47ef7c32be in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f47f09e66aa in start_thread (arg=0x7f47d2bb0700) at pthread_create.c:333 #9 0x7f47f13ade9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f47ca879700 (LWP 2062)): #0 0x7f47f09ebda0 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f47ee953114 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f47ee953159 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f47f09e66aa in start_thread (arg=0x7f47ca879700) at pthread_create.c:333 #4 0x7f47f13ade9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f47f189d840 (LWP 2036)): [KCrash Handler] #6 0x7f47ef9aa7c0 in QMetaObject::propertyOffset() const () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f47ef9aecd2 in QMetaObject::property(int) const () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f47ee9bae38 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #9 0x7f47ee9bb269 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #10 0x7f47ee8cda38 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #11 0x7f47ee92d318 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #12 0x7f47ee86d338 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #13 0x7f47ee8a5f4f in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #14 0x7f474000a842 in () #15 0x01df7808 in () #16 0x7f47c81f3e40 in () #17 0x7f47d0616518 in () #18 0x7f470003 in () #19 0x7f47d05170e8 in () #20 0x7f47ef7c1b39 in QThreadStorageData::get() const () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f47d051d000 in () #22 0x01df7808 in () #23 0x7f47eea3bda8 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #24 0x7f47d056bcb8 in () #25 0x7f47ee85f887 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #26 0x7f47ee8f655b in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #27 0x7f47ee8cda7f in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #28 0x7f47ee9bcf27 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #29 0x7f47ee9c58a5 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #30 0x7f47ef9d3940 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7f47eef6db82 in KWin::EffectsHandler::windowClosed(KWin::EffectWindow*) () at /usr/lib/x86_64-linux-gnu/libkwineffects.so.6 #32 0x7f47ef9d3617 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f47f100586b in () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #34 0x7f47f0eacc82 in () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #35 0x7f47f0ee7206 in () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #36 0x7f47f0eeb333 in () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #37 0x7f47f0eec6df in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #38 0x7f47ef99f8ef in QAbstractEventDispatcher::filterNativeEvent(QByteArray
[plasmashell] [Bug 361058] Plasma crash after disconnecting bluetooth headphones
https://bugs.kde.org/show_bug.cgi?id=361058 Alex Anderchanged: What|Removed |Added Summary|Plasma crash after |Plasma crash after |disconnecting bluetooth |disconnecting bluetooth |headsets|headphones -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361058] New: Plasma crash after disconnecting bluetooth headsets
https://bugs.kde.org/show_bug.cgi?id=361058 Bug ID: 361058 Summary: Plasma crash after disconnecting bluetooth headsets 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: aalexand...@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: I've turned off my Nokia BH-905i headphones, which was connected to laptop. And there was a music, which I heard from Youtube. Bluetooth adapter is Qualcomm Atheros AR9462 (with WiFi) Drivers came with OS, settings are not changed (Only headset got first priority between audio devices) Today Plasma also crashed, when I had connected the headphones. 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 0x7f094e406800 (LWP 10257))] Thread 16 (Thread 0x7f093ace9700 (LWP 10260)): #0 0x7f0948b0788d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f094cbd5bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f094cbd774f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f093d4647e9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f09491fda6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f09482e96aa in start_thread (arg=0x7f093ace9700) at pthread_create.c:333 #6 0x7f0948b12e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f0933fff700 (LWP 10262)): #0 0x7f09491fc9b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f0949434d51 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f094589cc21 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f094589d190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f094589d2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f094943550b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f09493dc50a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f09491f8ac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f094baa6c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f09491fda6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f09482e96aa in start_thread (arg=0x7f0933fff700) at pthread_create.c:333 #11 0x7f0948b12e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7f0927342700 (LWP 10263)): #0 0x7f0948ad6bed in nanosleep () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0948b09e34 in usleep (useconds=) at ../sysdeps/unix/sysv/linux/usleep.c:32 #2 0x7f092b645d00 in ?? () from /usr/lib/dri/fglrx_dri.so #3 0x7f092ad46332 in ?? () from /usr/lib/dri/fglrx_dri.so #4 0x7f092ad46385 in ?? () from /usr/lib/dri/fglrx_dri.so #5 0x7f09482e96aa in start_thread (arg=0x7f0927342700) at pthread_create.c:333 #6 0x7f0948b12e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f0925b28700 (LWP 10264)): #0 0x7f094589c80f in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f094589d11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f094589d2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f094943550b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f09493dc50a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f09491f8ac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f094baa6c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f09491fda6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f09482e96aa in start_thread (arg=0x7f0925b28700) at pthread_create.c:333 #9 0x7f0948b12e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f091fc5f700 (LWP 10265)): #0 0x7f0948b0788d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f094589d1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f094589d2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f094943550b in QEventDispatcherGlib::processEvents(QFlags) () from
[digikam] [Bug 361052] When importing picture file dates are all from importing time. Not creation date
https://bugs.kde.org/show_bug.cgi?id=361052 Maik Qualmannchanged: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- RAW or JPEG files? The modification date is correctly for RAW files. We write the document name in the EXIF for JPEG files or by activated automatic rotation, fix internal date / time and rating or color / pick label change, is the modification date from file changed to the current date. I think we should write the document name optional in the EXIF. If all JPEG operations are disabled, the modification date is unchanged and the file is unchanged. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 361050] CSV importer crashes on assigning columns (repro-file included)
https://bugs.kde.org/show_bug.cgi?id=361050 --- Comment #4 from allan--- (In reply to Felix Leimbach from comment #3) > That's exactly right and is enough to crash kmymoney-4.7.2 as per the "steps > to reproduce" above. Obviously the real file - a paypal transaction export - > contains more rows but they are not required to reproduce. Not for me, I'm afraid. No crash, no matter what column I select for the date. Did you completely remove all the remaining rows? Early on, I did have problems with Paypal, because of the number of columns, but I think that should be OK now. So, I can't go any further at the moment. > In fact we can narrow it down further: Removing all columns starting with > and including "Rechnungs-Nr." in the one single line does not stop kmymoney > from crashing. Remove one more column ("Vorgangs-Nr.") and it does not crash > anymore. > It is not the "Vorgangs-Nr." itself though, because renaming that does not > fix the crash. Also, removing some columns at the beginning can also fix the > crash. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]
https://bugs.kde.org/show_bug.cgi?id=357630 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 361057] New: Every word in names of data engines is capitalized
https://bugs.kde.org/show_bug.cgi?id=361057 Bug ID: 361057 Summary: Every word in names of data engines is capitalized Product: Plasma SDK Version: 5.5.95 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: engineexplorer Assignee: plasma-b...@kde.org Reporter: aspotas...@gmail.com CC: giorgos.tsiapalio...@kde.org KStringHandler::capwords() is used to force (sort of) title capitalization. This is not suitable for many languages, e.g. Russian. engineexplorer/modelviewer.cpp:101:engineName = KStringHandler::capwords(m_engine->pluginInfo().name()); engineexplorer/serviceviewer.cpp:69:engineName = KStringHandler::capwords(m_engine->pluginInfo().name()); engineexplorer/engineexplorer.cpp:513: .subs(KStringHandler::capwords(m_engine->pluginInfo().name())) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 341330] Active terminal doesn't always gain focus correctly after opening the window
https://bugs.kde.org/show_bug.cgi?id=341330 artephiuschanged: What|Removed |Added CC||rushhourresour...@gmail.com --- Comment #12 from artephius --- I don't have focus follows mouse on and this still happens every other time or so... I've found right clicking in the konsole window restores focus, though that is not really a workaround obviously. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336274] "Connecting…" status causes high plasmashell CPU usage
https://bugs.kde.org/show_bug.cgi?id=336274 Dima Ryazanovchanged: What|Removed |Added CC|d...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361056] New: plasma crashes when I change to the previous activity using a custom global keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=361056 Bug ID: 361056 Summary: plasma crashes when I change to the previous activity using a custom global keyboard shortcut Product: plasmashell Version: 5.6.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: pier_andr...@yahoo.it CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.6.0) Qt Version: 5.6.0 Frameworks Version: 5.20.0 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - Unusual behavior I noticed: this is a duplicate 359671 but the application doesn't allow me to check this as duplicate - What I was doing when the application crashed: I change to the previous activity using a custom global keyboard shortcut. - Custom settings of the application: I used the Alt + Ctrl + Down Arrow as a shortcut to navigate to the previous activity. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7efd5ff98800 (LWP 7447))] Thread 36 (Thread 0x7efd47d6c700 (LWP 7463)): #0 0x7efd594c4bbd in poll () at /lib64/libc.so.6 #1 0x7efd5e3f2422 in () at /usr/lib64/libxcb.so.1 #2 0x7efd5e3f400f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7efd4a6f2979 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7efd59bc1079 in () at /usr/lib64/libQt5Core.so.5 #5 0x7efd58cce0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7efd594ccfed in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7efd461bb700 (LWP 7464)): #0 0x7efd594c0c8d in read () at /lib64/libc.so.6 #1 0x7efd51658f45 in () at /usr/lib64/tls/libnvidia-tls.so.340.96 #2 0x7efd55befb60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7efd55bae999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7efd55baedf8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7efd55baef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7efd59dd23fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7efd59d8004b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7efd59bbc5da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7efd5ab3d095 in () at /usr/lib64/libQt5DBus.so.5 #10 0x7efd59bc1079 in () at /usr/lib64/libQt5Core.so.5 #11 0x7efd58cce0a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7efd594ccfed in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7efd3700 (LWP 7467)): #0 0x7efd594c4bbd in poll () at /lib64/libc.so.6 #1 0x7efd55baee64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7efd55baef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7efd59dd23fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7efd59d8004b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7efd59bbc5da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7efd5ceb74d8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7efd59bc1079 in () at /usr/lib64/libQt5Core.so.5 #8 0x7efd58cce0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7efd594ccfed in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7efd2fafa700 (LWP 7509)): #0 0x7efd55bac241 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7efd55bae44b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7efd55baed80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7efd55baef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7efd59dd23fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7efd59d8004b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7efd59bbc5da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7efd5ceb74d8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7efd59bc1079 in () at /usr/lib64/libQt5Core.so.5 #9 0x7efd58cce0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7efd594ccfed in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7efd2e233700 (LWP 7525)): #0 0x7efd594c4bbd in poll () at /lib64/libc.so.6 #1 0x7efd55baee64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7efd55baef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7efd59dd23fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7efd59d8004b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7efd59bbc5da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7efd5ceb74d8 in () at
[konsole] [Bug 355421] Konsole crashed on login
https://bugs.kde.org/show_bug.cgi?id=355421 Götzchanged: What|Removed |Added CC||goetzchr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 344119] 100% CPU usage after closing konsole, after upgrading to 3.0.1/KF5.6.0 with nvidia driver
https://bugs.kde.org/show_bug.cgi?id=344119 --- Comment #38 from Mike--- As it turns out from my experience it has nothing to do with a certain driver version (per se) We first saw thing go away in 361.16 because libglvnd was use standard I had issues with it again in the following driver 361.28, because that did not use libglvnd by default. As I detailed in the parent thread (this is the dupe, the solution was for me to do the following: NVIDIA-Linux-x86_64-361.28.run -s --dkms --install-libglvnd --glvnd-glx-client Today I am also using 364.12 with libglvnd installed and still have no issues. (I am also testing out the new nvidia-modeset and nvidia-drm modules too and haven't had issues with this either) It appears the issue resides in the use or non-use, rather, of GLVND. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 361055] New: the process for mtp protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=361055 Bug ID: 361055 Summary: the process for mtp protocol died unexpectedly Product: dolphin Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ionutz...@gmail.com cannot copyy file from my lg g3,i have linux mint 17.3 and i get error:the process for mtp protocol died unexpectedly Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361054] New: Accelerators do not work in weather applet configuration dialog
https://bugs.kde.org/show_bug.cgi?id=361054 Bug ID: 361054 Summary: Accelerators do not work in weather applet configuration dialog 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 In the weather widget's configuration dialog, holding the Alt+[...] accelerators do not work. For example, I can't go to the "Visibility" combo box by pressing Alt+V. This is a regression w.r.t. Plasma 4.x. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360391] Auto-hiding panel does not return
https://bugs.kde.org/show_bug.cgi?id=360391 David Edmundsonchanged: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #9 from David Edmundson --- It is the same mechanism that does Plasma panels. Thanks I'll look into a fix. -- 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 --- Comment #37 from Götz--- This is strange, since a week or two, using KWin with OpenGL 2.0 and XGL composition, when the locker becomes unresponsive, just switching to a TTY and back (without killing any process) makes the locker become responsive again. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361053] New: Center “click anywhere” message on screen instead of entire virtual desktop
https://bugs.kde.org/show_bug.cgi?id=361053 Bug ID: 361053 Summary: Center “click anywhere” message on screen instead of entire virtual desktop Product: Spectacle Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: lach...@hong-mailing.de Currently, the usage hint in the cropper window is centered in the window instead of the currently active screen. This should be changed so it only appears on the active screen and does not span multiple physical displays. Reproducible: Always Steps to Reproduce: 1. Use the “rectangular region” capture mode on a system with a virtual desktop spanning multiple physical displays Actual Results: Message is centered on the virtual desktop, potentially spanning multiple physical displays. Expected Results: Message is centered on the physical display that corresponds to the active screen. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361034] Use generic icon if no icon is specified
https://bugs.kde.org/show_bug.cgi?id=361034 andreaschanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #4 from andreas --- Hi Emmanuel, I'm not sure where this bug is related but it look like it is in dolphin. when I say right click -> create -> Text file and say a.pdb I get the same than in the bug report. when I say touch a.pdb I get the default unknown mimetype icon (http://imgur.com/C8lp8YB). In krusader I see the unknown icon. Dolphin 15.12.3 KF 5.19.0 Qt 5.5.1 OS Manjaro -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361034] Use generic icon if no icon is specified
https://bugs.kde.org/show_bug.cgi?id=361034 andreaschanged: What|Removed |Added CC||emmanuelpescosta099@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336274] "Connecting…" status causes high plasmashell CPU usage
https://bugs.kde.org/show_bug.cgi?id=336274 kde2e...@tromer.org changed: What|Removed |Added CC||kde2e...@tromer.org --- Comment #33 from kde2e...@tromer.org --- I observe this on Fedora 23, with a cellular data connection. The "Networks" plasmoid is stuck at "Preparing to connect" with a progress animation and consumes 100% CPU, even though the connection is already up for an hour. plasma-desktop-5.5.5-2.fc23.x86_64 kf5-plasma-5.19.0-2.fc23.x86_64 kf5-networkmanager-qt-5.19.0-1.fc23.x86_64 NetworkManager-1.0.10-3.fc23.x86_64 NetworkManager-wwan-1.0.10-3.fc23.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361048] QML-based cropper does not support virtual desktops spanning multiple screens
https://bugs.kde.org/show_bug.cgi?id=361048 --- Comment #8 from Martin Herkt--- Yup, fixed. Nice bonus would be to center the “click anywhere” message on the active screen instead of the entire window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 kde2e...@tromer.org changed: What|Removed |Added CC||kde2e...@tromer.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #3 from Jens B. Benecke--- Thank you! :-) I'd be happy to create a border / backdrop for grouped images, I'll be happy to do it - just tell me what formats you need (probably SVG to zoom it, or are you going to draw it in software?). IMHO: The colored background for expanded groups should be very slight and adhere to the theme that is currently set in KDE. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361048] QML-based cropper does not support virtual desktops spanning multiple screens
https://bugs.kde.org/show_bug.cgi?id=361048 --- Comment #7 from Boudhayan Gupta--- Fixed now? -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 360977] Autocomplete in annotation dialog fails with some category names
https://bugs.kde.org/show_bug.cgi?id=360977 --- Comment #9 from Andreas Schleth--- @Tobias: my build process is really errorprone right now, because every now and then some system updates upgrade some libs to QT5. Therefore, I will keep my 4.7.1 for now, until I run into real problems or the switch to QT5 is done in KPA and all dependencies. (I hope this upgrading in the background does not break things.) Thus: no testing for me right now, sorry! Your idea sounds appealing to me. It will be a bit more tolerant then simple string search and this might be a good thing. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361048] QML-based cropper does not support virtual desktops spanning multiple screens
https://bugs.kde.org/show_bug.cgi?id=361048 Boudhayan Guptachanged: What|Removed |Added Latest Commit|http://commits.kde.org/kscr |http://commits.kde.org/kscr |eengenie/639a1f4f4d9bcb9f08 |eengenie/a1782fc05cab519ecd |8a0a0552a0ec05be61207d |1437eefbe0b418081e4118 --- Comment #6 from Boudhayan Gupta --- Git commit a1782fc05cab519ecd1437eefbe0b418081e4118 by Boudhayan Gupta. Committed on 27/03/2016 at 18:25. Pushed by bgupta into branch 'Applications/16.04'. Fix image sizing inside the editor M +2-2src/QuickEditor/EditorRoot.qml http://commits.kde.org/kscreengenie/a1782fc05cab519ecd1437eefbe0b418081e4118 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 361050] CSV importer crashes on assigning columns (repro-file included)
https://bugs.kde.org/show_bug.cgi?id=361050 Felix Leimbachchanged: What|Removed |Added CC||felix.leimb...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360391] Auto-hiding panel does not return
https://bugs.kde.org/show_bug.cgi?id=360391 --- Comment #8 from christ...@whoop.org --- Folks, I've figured out what's going on here. It looks like by default, screen edges are disabled in KDE 5 (System Settings -> Desktop Behavior -> Screen Edges -> Switch desktop on edge). Once you enable desktop switching, the panel no longer pops up. If you disable it, the panel appears again. Looks like the edge detection logic collides with the panel trigger logic. Note that my virtual desktops are aligned horizontally and my panel is at the bottom, so there's no switching to do when I go near the panel. Anyway, case closed from my side, but a fix for this would obviously be welcome. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 361050] CSV importer crashes on assigning columns (repro-file included)
https://bugs.kde.org/show_bug.cgi?id=361050 --- Comment #3 from Felix Leimbach--- That's exactly right and is enough to crash kmymoney-4.7.2 as per the "steps to reproduce" above. Obviously the real file - a paypal transaction export - contains more rows but they are not required to reproduce. In fact we can narrow it down further: Removing all columns starting with and including "Rechnungs-Nr." in the one single line does not stop kmymoney from crashing. Remove one more column ("Vorgangs-Nr.") and it does not crash anymore. It is not the "Vorgangs-Nr." itself though, because renaming that does not fix the crash. Also, removing some columns at the beginning can also fix the crash. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361048] QML-based cropper does not support virtual desktops spanning multiple screens
https://bugs.kde.org/show_bug.cgi?id=361048 --- Comment #5 from Boudhayan Gupta--- Comment on attachment 98116 --> https://bugs.kde.org/attachment.cgi?id=98116 Patch to fix editor pixmap scaling That patch will break HiDPI support. I'll try to fix it by hooking to Window instead of Screen -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 361050] CSV importer crashes on assigning columns (repro-file included)
https://bugs.kde.org/show_bug.cgi?id=361050 --- Comment #2 from allan--- I see only a single row, of, apparently, headings, but no actual transaction data. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361048] QML-based cropper does not support virtual desktops spanning multiple screens
https://bugs.kde.org/show_bug.cgi?id=361048 --- Comment #4 from Martin Herkt--- Created attachment 98116 --> https://bugs.kde.org/attachment.cgi?id=98116=edit Patch to fix editor pixmap scaling Almost. Works with this patch. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361048] QML-based cropper does not support virtual desktops spanning multiple screens
https://bugs.kde.org/show_bug.cgi?id=361048 Boudhayan Guptachanged: What|Removed |Added Latest Commit||http://commits.kde.org/kscr ||eengenie/639a1f4f4d9bcb9f08 ||8a0a0552a0ec05be61207d Status|UNCONFIRMED |RESOLVED Version Fixed In||16.04 Resolution|--- |FIXED --- Comment #3 from Boudhayan Gupta --- Git commit 639a1f4f4d9bcb9f088a0a0552a0ec05be61207d by Boudhayan Gupta. Committed on 27/03/2016 at 18:01. Pushed by bgupta into branch 'Applications/16.04'. Editor window should be as big as pixmap FIXED-IN: 16.04 M +3-0src/QuickEditor/QuickEditor.cpp http://commits.kde.org/kscreengenie/639a1f4f4d9bcb9f088a0a0552a0ec05be61207d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361049] Krita does not load profiles (canvas input settings) properly
https://bugs.kde.org/show_bug.cgi?id=361049 --- Comment #1 from janr...@gmail.com --- I should add, changes to the default profile do persist between restarts, so this only applies to entirely new profiles. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360034] Activity switcher not showing wallpapers from all activities
https://bugs.kde.org/show_bug.cgi?id=360034 --- Comment #7 from Ivan Čukić--- Cool, thanks for the help, I'll see what went wrong with the patch. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361036] No support for 30bpp X11 display
https://bugs.kde.org/show_bug.cgi?id=361036 --- Comment #9 from Boudhayan Gupta--- Qt's image processor can only handle 8 bits per component. Format_BGR30 just downscales 10bits of precision to 8bits. You'll have to file a QTBUG for this :-( -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361052] New: When importing picture file dates are all from importing time. Not creation date
https://bugs.kde.org/show_bug.cgi?id=361052 Bug ID: 361052 Summary: When importing picture file dates are all from importing time. Not creation date Product: digikam Version: 4.14.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Import Assignee: digikam-de...@kde.org Reporter: sc...@gmx.de When importing images from freshly connected camera all the image file dates and times are all from importing time. Did not pay attention to that until now. in 2014 there all my images have same file date/times as in exif creation date/time. Has this been changed intentionally or is there a not yet found switch to chose behavior or is it a bug? I would rather have the old behavior. Reproducible: Always Steps to Reproduce: 1. Attach camera. choose image download with digikam 2. Digikam Importer window opens. chose pictures for download and initiate the download. 3. open File manager like Dolphin and check date/time of the downloaded files. Actual Results: Date/time is current, not creation date/time of the picture. Expected Results: Date/time of the file is creation date/time of the picture. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361036] No support for 30bpp X11 display
https://bugs.kde.org/show_bug.cgi?id=361036 --- Comment #8 from Martin Herkt--- Yes, it is. At least I get correct colors now :) Now if it could save at higher bit depth as well, that would be the icing on the cake. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- This idea is EXCELENT. I search a lots a visual solution to show grouped images. The current icon was the only way to do it, and i agree that usability is not very good. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 361051] New: Plasma-nm icon does not indicate VPN
https://bugs.kde.org/show_bug.cgi?id=361051 Bug ID: 361051 Summary: Plasma-nm icon does not indicate VPN Product: plasma-nm Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: k...@privat.broulik.de CC: lu...@kde.org When I connect to my company network through VPN the Plasma-nm icon does not reflect that. Worse, it shows the "wifi available but not connected" icon. Reproducible: Always Steps to Reproduce: 1. Connect to WiFi 2. Connect to VPN 3. Actual Results: The icon shows the blue "wifi available but not connected" icon Expected Results: The icon shows the wifi icon with a padlock -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361035] crash when open a folder in dolphin
https://bugs.kde.org/show_bug.cgi?id=361035 Thomas Lübkingchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Thomas Lübking --- Use the breeze decoration. *** This bug has been marked as a duplicate of bug 358369 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome
https://bugs.kde.org/show_bug.cgi?id=358369 --- Comment #17 from Thomas Lübking--- *** Bug 361035 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 361050] CSV importer crashes on assigning columns (repro-file included)
https://bugs.kde.org/show_bug.cgi?id=361050 --- Comment #1 from Felix Leimbach--- Created attachment 98115 --> https://bugs.kde.org/attachment.cgi?id=98115=edit CSV file for crash repro -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361048] QML-based cropper does not support virtual desktops spanning multiple screens
https://bugs.kde.org/show_bug.cgi?id=361048 --- Comment #2 from Martin Herkt--- Same behavior with KWin. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 361050] New: CSV importer crashes on assigning columns (repro-file included)
https://bugs.kde.org/show_bug.cgi?id=361050 Bug ID: 361050 Summary: CSV importer crashes on assigning columns (repro-file included) Product: kmymoney4 Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: csvimporter Assignee: kmymoney-de...@kde.org Reporter: felix.leimb...@gmx.net Kmymoney version 4.7.2 Reproducible: Always Steps to Reproduce: 1. Open the attached CSV File in the CSV Importer 2. Chose the Date-Column at set it to 1 3. kmymoney crashes -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361048] QML-based cropper does not support virtual desktops spanning multiple screens
https://bugs.kde.org/show_bug.cgi?id=361048 --- Comment #1 from Boudhayan Gupta--- Please test with kwin once. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360034] Activity switcher not showing wallpapers from all activities
https://bugs.kde.org/show_bug.cgi?id=360034 --- Comment #6 from Robby Engelmann--- I have three activities, 1 "work", 2 "private" and 3 "finances". Before I executed the konsole commands, previews of 1+3 showed the respective wallpapers and 2 was just gray (with a gradient). After the commands: 2+3 showed the respective wallpapers and 1 was just gray. In the meantime, I restarted the notebook, and now 1 showed the respective wallpaper and 2+3 are just gray. So it randomly varies, which wallpapers are shown in the activity previews and which not. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361049] New: Krita does not load profiles (canvas input settings) properly
https://bugs.kde.org/show_bug.cgi?id=361049 Bug ID: 361049 Summary: Krita does not load profiles (canvas input settings) properly Product: krita Version: 2.9.11 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: janr...@gmail.com Upon creating new Canvas Input Settings profiles (Krita profiles in general?), the profile seems to get saved in .kde/share/apps/krita/input/. However, upon restarting the program, none of the previously created profiles are found in Krita anymore. Reproducible: Always Steps to Reproduce: 1. Create new profile in Canvas Input Settings 2. Rename profile to something, maybe also change one of the default settings 3. Restart Krita Actual Results: Krita is not able to find the previously created profile. However, the profile is still saved in .kde/share/apps/krita/input/ but the program apparently does not find it. Expected Results: Even after restart, Krita is able to find a previously-created profile. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #1 from Jens B. Benecke--- Created attachment 98114 --> https://bugs.kde.org/attachment.cgi?id=98114=edit mockup to better recognize groups of images -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361048] New: QML-based cropper does not support virtual desktops spanning multiple screens
https://bugs.kde.org/show_bug.cgi?id=361048 Bug ID: 361048 Summary: QML-based cropper does not support virtual desktops spanning multiple screens Product: Spectacle Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: lach...@hong-mailing.de The QML-based cropper (in git master) currently fullscreens only on a single display instead of spanning the entire virtual desktop. This is a regression. Reproducible: Always Steps to Reproduce: 1. Use “rectangular region” capture mode Actual Results: Cropper displays only on one screen, virtual desktop screenshot is downscaled to fit. Will save the downscaled region. Expected Results: Cropper window spans entire virtual desktop. Using i3, not KWin. I don’t think it matters, though. Displays set up like this: 1920x1080 | 1920x1080 (primary) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] New: Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 Bug ID: 361047 Summary: Wishlist: make grouped images more prominently visible [MOCKUP] Product: digikam Version: 4.14.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Hello, I have three requests regarding grouped images. Maybe they can make it into 5.0. 1. Display a different kind of border around grouped images so it is at once visible that there are multiple images "behind" the displayed one. Also, when opened, maybe the group can be visualized by using a different background color. See attachment. 2. In a set of grouped images, make it possible to choose which image is the visible thumbnail, i.e. "at the top". 3. When a group is closed, and the front image's properties are modified, apply the changes to all grouped images *unless* this would overwrite previous settings (perhaps with a confirmation dialog). 4. What do you think? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360034] Activity switcher not showing wallpapers from all activities
https://bugs.kde.org/show_bug.cgi?id=360034 --- Comment #5 from Ivan Čukić--- You mean that a preview of an activity disappeared and that it is grey now? Is it so for all activities or you still have some of them with previews? -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 329174] Lost copied text after close application
https://bugs.kde.org/show_bug.cgi?id=329174 --- Comment #17 from Christos Gourdoupis--- I have a dual monitor setup and after cleaning up my xorg.conf the problem went away. Multi-monitor support is broken in kf5 and under some conditions things break and windows start behaving erraticaly. At that point, strange things happen to the clipboard too, like not being able to copy from KDE apps at all. Restarting kwin_x11 --replace then brings back the original problem! So could it be an underlying window manager issue? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays
https://bugs.kde.org/show_bug.cgi?id=333655 --- Comment #66 from Mircea Kitsune--- Just dropping this here: Yesterday I decided to give another shot to Baloo, so I re-enabled the desktop search setting. It took Baloo nearly 20 hours to index everything on my drive! And during this entire day, my system was nearly unusable: Every process would randomly freeze for several seconds, from any open application to the desktop itself. I was later told this has to do with the I/O scheduler, and that Baloo intensively using the drive causes other processes to have to wait in line. Whatever the cause, Baloo in its current state is a nightmare... at least if you have a large home partition (I have nearly 800 GB on mine so yeah). I don't think any system component made me hate it this way, because of how much it can mess with your system! At least now that it's indexed everything, things seem to work alright again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361046] New: Starts lagging when I rotate the canvas
https://bugs.kde.org/show_bug.cgi?id=361046 Bug ID: 361046 Summary: Starts lagging when I rotate the canvas Product: krita Version: 3.0 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: wikusvan...@gmail.com When I rotate the canvas the program starts lagging, it continues even after I stop rotating. The lag only stops when I return the canvas to more or less the right orientation. This only seems to happen when i'm zoomed in Reproducible: Sometimes Steps to Reproduce: 1.Turn canvas with shift+space shortcut 2.Zoom in, the farther, the worse the lag 3. Actual Results: I was able to reproduce the bug Expected Results: Continued running at a stable frame rate Running windows 10 64 bit off of C drive, if that makes a difference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361045] New: Plasma crashes after login
https://bugs.kde.org/show_bug.cgi?id=361045 Bug ID: 361045 Summary: Plasma crashes after login 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: website-...@interfasys.ch CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.4.0-15-generic i686 Distribution: Ubuntu Xenial Xerus (development branch) -- Information about the crash: - What I was doing when the application crashed: I just login and I see the colourful background, then plasma crashes. I've tried turning off desktop effects, but it did not change anything The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb1b56800 (LWP 1982))] Thread 7 (Thread 0xb1723b40 (LWP 1985)): #0 0xb77adc31 in __kernel_vsyscall () #1 0xb4dd4e0f in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0xb714d41d in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1 #3 0xb714f59b in xcb_wait_for_event () from /usr/lib/i386-linux-gnu/libxcb.so.1 #4 0xb185b143 in QXcbEventReader::run (this=0x9ff3418) at qxcbconnection.cpp:1253 #5 0xb50b23fb in QThreadPrivate::start (arg=0x9ff3418) at thread/qthread_unix.cpp:331 #6 0xb4c892b5 in start_thread (arg=0xb1723b40) at pthread_create.c:333 #7 0xb4ddf04e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 6 (Thread 0xb01d2b40 (LWP 1987)): #0 0xb77adc31 in __kernel_vsyscall () #1 0xb4dd4e0f in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0xb4483a90 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb447507c in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb44751b4 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb52e1a94 in QEventDispatcherGlib::processEvents (this=0xaf800470, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0xb5286893 in QEventLoop::processEvents (this=0xb01d21d4, flags=...) at kernel/qeventloop.cpp:128 #7 0xb5286cea in QEventLoop::exec (this=0xb01d21d4, flags=...) at kernel/qeventloop.cpp:204 #8 0xb50acedd in QThread::exec (this=0xa098ad8) at thread/qthread.cpp:503 #9 0xb691e7ff in QQmlThreadPrivate::run (this=0xa098ad8) at qml/ftw/qqmlthread.cpp:141 #10 0xb50b23fb in QThreadPrivate::start (arg=0xa098ad8) at thread/qthread_unix.cpp:331 #11 0xb4c892b5 in start_thread (arg=0xb01d2b40) at pthread_create.c:333 #12 0xb4ddf04e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 5 (Thread 0xaa6afb40 (LWP 1988)): #0 0xb77adc31 in __kernel_vsyscall () #1 0xb4dd4e0f in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0xb4483a90 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb447507c in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb44751b4 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb52e1a94 in QEventDispatcherGlib::processEvents (this=0xa9d00470, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0xb5286893 in QEventLoop::processEvents (this=0xaa6af1d4, flags=...) at kernel/qeventloop.cpp:128 #7 0xb5286cea in QEventLoop::exec (this=0xaa6af1d4, flags=...) at kernel/qeventloop.cpp:204 #8 0xb50acedd in QThread::exec (this=0xa1f3098) at thread/qthread.cpp:503 #9 0xb691e7ff in QQmlThreadPrivate::run (this=0xa1f3098) at qml/ftw/qqmlthread.cpp:141 #10 0xb50b23fb in QThreadPrivate::start (arg=0xa1f3098) at thread/qthread_unix.cpp:331 #11 0xb4c892b5 in start_thread (arg=0xaa6afb40) at pthread_create.c:333 #12 0xb4ddf04e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 4 (Thread 0xa936cb40 (LWP 1989)): [KCrash Handler] #7 0xae1b9f98 in nettle_yarrow256_update () from /usr/lib/i386-linux-gnu/libnettle.so.4 #8 0x9fb06c91 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28 #9 0x9fb06f96 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28 #10 0x9fa6f706 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28 #11 0x9fa630dd in gnutls_global_init () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28 #12 0x9fa439e4 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28 #13 0xb77bd3e5 in call_init (l=, argc=argc@entry=3, argv=argv@entry=0xbfce5c04, env=0xbfce5c14) at dl-init.c:72 #14 0xb77bd50e in call_init (env=0xbfce5c14, argv=0xbfce5c04, argc=3, l=) at dl-init.c:30 #15 _dl_init (main_map=main_map@entry=0x9fe2fc98, argc=3, argv=0xbfce5c04, env=0xbfce5c14) at dl-init.c:120 #16 0xb77c1802 in dl_open_worker (a=0xa936b3bc) at dl-open.c:575 #17 0xb77bd284 in _dl_catch_error (objname=objname@entry=0xa936b3b4, errstring=errstring@entry=0xa936b3b8, mallocedp=mallocedp@entry=0xa936b3b3,
[plasmashell] [Bug 360034] Activity switcher not showing wallpapers from all activities
https://bugs.kde.org/show_bug.cgi?id=360034 --- Comment #4 from Robby Engelmann--- I did it... ..after restarting plasmashell the preview of another activity then before is gray now. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 359758] Dolphin crashes on exit when you specify the --icon command line parameter
https://bugs.kde.org/show_bug.cgi?id=359758 Alexander Potashevchanged: What|Removed |Added CC||aspotas...@gmail.com --- Comment #5 from Alexander Potashev --- I've just got a similar stacktrace from Lokalize-15.12.2 with KF 5.20.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360034] Activity switcher not showing wallpapers from all activities
https://bugs.kde.org/show_bug.cgi?id=360034 --- Comment #3 from Ivan Čukić--- Can you clear the cache just to make sure it is not causing the problems? Open konsole, and write the following kquitapp5 plasmashell rm ~/.cache/activityswitcher_wallpaper_preview.kcache plasmashell &>/dev/null& This will stop plasma, remove the wallpaper cache file and restart plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 329174] Lost copied text after close application
https://bugs.kde.org/show_bug.cgi?id=329174 --- Comment #16 from mgol...@mitchgolden.com --- That is the exact behavior that I originally saw - I believe with firefox. When the application closes the text is lost from the clipboard, but not from klipper, and it can be reselected if another text is chosen in klipper first. -- You are receiving this mail because: You are watching all bug changes.