[plasmashell] [Bug 396770] Icons have wrong scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=396770 --- Comment #7 from el...@seznam.cz --- Update to my previous observations: Wayland + scale factor 2 + dock size 48px = OK, but icons have jagged edges Wayland + scale factor 2 + dock size 96px = large icons, but no jagged edges Wayland + scale factor 2 + dock size 48px + PLASMA_USE_QT_SCALING=1= OK, but icons have jagged edges So it seems that PLASMA_USE_QT_SCALING has no effect in Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396770] Icons have wrong scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=396770 --- Comment #5 from el...@seznam.cz --- I would like to have latte dock of size 48px. With various settings it works like this: X11 + scale factor 1 + dock size 48px = OK X11 + scale factor 2 + dock size 48px = small icons X11 + scale factor 2 + dock size 96px = OK X11 + scale factor 2 + dock size 48px + PLASMA_USE_QT_SCALING=1 = size OK, but icons have jagged edges Wayland + scale factor 2 + dock size 48px = OK Wayland + scale factor 2 + dock size 96px = large icons I believe that scaling should be done on background and front end application should be using same size of 48px regardless of scale factor. Of course front end application must be aware of scale factor when displaying high resolution content like images or bitmap icons. I'm also attaching another picture. It shows desktop right click menu. In front is my actual desktop and in the background is VirtualBox which basically doubles the size of display without scaling. However as you can see font size about the same (I have font DPI set to 192). But icons on real desktop are only half the size as they should be. When I set PLASMA_USE_QT_SCALING=1, icons are scaled as expected and font size remains the same. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396770] Icons have wrong scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=396770 --- Comment #5 from el...@seznam.cz --- I would like to have latte dock of size 48px. With various settings it works like this: X11 + scale factor 1 + dock size 48px = OK X11 + scale factor 2 + dock size 48px = small icons X11 + scale factor 2 + dock size 96px = OK X11 + scale factor 2 + dock size 48px + PLASMA_USE_QT_SCALING=1 = size OK, but icons have jagged edges Wayland + scale factor 2 + dock size 48px = OK Wayland + scale factor 2 + dock size 96px = large icons I believe that scaling should be done on background and front end application should be using same size of 48px regardless of scale factor. Of course front end application must be aware of scale factor when displaying high resolution content like images or bitmap icons. I'm also attaching another picture. It shows desktop right click menu. In front is my actual desktop and in the background is VirtualBox which basically doubles the size of display without scaling. However as you can see font size about the same (I have font DPI set to 192). But icons on real desktop are only half the size as they should be. When I set PLASMA_USE_QT_SCALING=1, icons are scaled as expected and font size remains the same. --- Comment #6 from el...@seznam.cz --- Created attachment 114078 --> https://bugs.kde.org/attachment.cgi?id=114078=edit Scaling of desktop right click menu -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396779] New: Desaturated reference images still give original saturated color when using the color picker
https://bugs.kde.org/show_bug.cgi?id=396779 Bug ID: 396779 Summary: Desaturated reference images still give original saturated color when using the color picker Product: krita Version: 4.1.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools/Reference Images Assignee: krita-bugs-n...@kde.org Reporter: altgu...@gmail.com Target Milestone: --- Created attachment 114077 --> https://bugs.kde.org/attachment.cgi?id=114077=edit Video Example Adding a reference image, desaturating the image using the reference image tool options, then color picking from the desaturated reference image will pick the original saturated color from the reference image. Reproducable: Always Steps to reproduce: 1) Add a color reference image 2) Us the Reference Image Tool Options to desaturate the reference image 3) Switch to the Color Selector Tool and pick a color from the desaturated reference image Actual Result: The Color Picker will pick the original, fully saturated color from the reference image. Expected Result: The Color Picker picks the desaturated color. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396770] Icons have wrong scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=396770 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from David Edmundson --- > PLASMA_USE_QT_SCALING=1, You can't randomly set hidden internal environment variables. Lots of things will be broke. Can you clarify if the Wayland behavior is correct? You used the term double size. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 396778] New: Baloo crashes after login
https://bugs.kde.org/show_bug.cgi?id=396778 Bug ID: 396778 Summary: Baloo crashes after login Product: frameworks-baloo Version: 5.47.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: misba...@gmail.com Target Milestone: --- Application: baloo_file_extractor (5.47.0) Qt Version: 5.10.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.6-200.fc28.x86_64 x86_64 Distribution: "Fedora release 28 (Twenty Eight)" -- Information about the crash: - What I was doing when the application crashed: Baloo crashes everytime after I login, I am using the default setting the came with Fedora. This started since I upgraded to Fedora 28. The crash can be reproduced sometimes. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2948ed8940 (LWP 2109))] Thread 3 (Thread 0x7f2925214700 (LWP 2151)): #0 0x7f2945ccf659 in poll () from /lib64/libc.so.6 #1 0x7f2941216be6 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f2941216d10 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f2946b9bc2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f2946b4a12b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f29469989c6 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f2948f4e299 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f294699d11d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f2945002594 in start_thread () from /lib64/libpthread.so.0 #9 0x7f2945cda0df in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f292edb1700 (LWP 2127)): #0 0x7f2945ccf659 in poll () from /lib64/libc.so.6 #1 0x7f294073a04f in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f294073bcaa in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f29317604d9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f294699d11d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f2945002594 in start_thread () from /lib64/libpthread.so.0 #6 0x7f2945cda0df in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f2948ed8940 (LWP 2109)): [KCrash Handler] #6 0x7f2945c16feb in raise () from /lib64/libc.so.6 #7 0x7f2945c015c1 in abort () from /lib64/libc.so.6 #8 0x7f2947bcdc62 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x7f2947bc2b95 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x7f2947bc3e36 in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x7f2947bc406b in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x7f2947bc5c9c in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0 #13 0x7f2947bc8d9f in mdb_cursor_put () from /lib64/liblmdb.so.0.0.0 #14 0x7f2947bcba4b in mdb_put () from /lib64/liblmdb.so.0.0.0 #15 0x7f2948457e40 in Baloo::PositionDB::put(QByteArray const&, QVector const&) () from /lib64/libKF5BalooEngine.so.5 #16 0x7f294846b4f6 in Baloo::WriteTransaction::commit() () from /lib64/libKF5BalooEngine.so.5 #17 0x7f29484617f6 in Baloo::Transaction::commit() () from /lib64/libKF5BalooEngine.so.5 #18 0x563094b2c6cc in Baloo::App::processNextFile() () #19 0x7f2946b7feba in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #20 0x7f2946b749db in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f2947412e95 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #22 0x7f294741a83a in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #23 0x7f2946b4b376 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #24 0x7f2946b9af19 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #25 0x7f2946b9b7bc in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #26 0x7f29412168ad in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #27 0x7f2941216c78 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #28 0x7f2941216d10 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #29 0x7f2946b9bc13 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #30 0x7f29317ee065 in QPAEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5XcbQpa.so.5 #31 0x7f2946b4a12b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #32 0x7f2946b525b6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #33 0x563094b29e52 in main () Possible duplicates by query: bug 394918, bug
[plasmashell] [Bug 395594] Icon size for launcher in vertical panels
https://bugs.kde.org/show_bug.cgi?id=395594 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||h...@kde.org --- Comment #2 from Eike Hein --- Can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396777] New: Error--Okular when boot to openSUSE 42.3
https://bugs.kde.org/show_bug.cgi?id=396777 Bug ID: 396777 Summary: Error--Okular when boot to openSUSE 42.3 Product: okular Version: 1.1.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: twc...@gmail.com Target Milestone: --- Created attachment 114076 --> https://bugs.kde.org/attachment.cgi?id=114076=edit Error message upon booting Every time I boot OpenSUSE 42.3, I get an error box pop up on one of the two screens I have attached to the computer. It says: "Could not open file:///tmp/mozilla_tomatx3-s0/4256777.pdf" When I click on "OK" button in the box, the box and its message disappear. I reinstalled the operating system today, reformatting / and swap devices and I still get this message when I boot. My version of Okular, which appears to be quite dated is what was included in the OpenSUSE distribution 42.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378443] Plasma 5 start-button gets too big when the panel is vertical. (there was no problem in Plasma 4)
https://bugs.kde.org/show_bug.cgi?id=378443 Eike Hein changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #33 from Eike Hein --- Thanks. Let's use the new ticket then. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396111] Activity doesn't update files shown on desktop
https://bugs.kde.org/show_bug.cgi?id=396111 --- Comment #5 from Eike Hein --- Thanks, that's useful extra info. I'll see if I can reproduce with the symlink. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396775] New: Incorrect unallocated size calculated for LVM with cache pool
https://bugs.kde.org/show_bug.cgi?id=396775 Bug ID: 396775 Summary: Incorrect unallocated size calculated for LVM with cache pool Product: partitionmanager Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: c...@daniel.priv.no Target Milestone: --- 1. Add one 1 TB physical volume and one 100 GB physical volume to a new LVM volume group. Setup a standard logical volume on the 1 TB PV and create a cache pool of of the 100 GB PV. 2. Open partitionmanager and select the volume group. Expected: Should show one 1 TB, and 1 cache pool of 100 GB. Actual: Displays one volume of 1 TB and incorrectly shows 100 GB to be unallocated. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396776] New: Incorrect unallocated size calculated for LVM with RAID
https://bugs.kde.org/show_bug.cgi?id=396776 Bug ID: 396776 Summary: Incorrect unallocated size calculated for LVM with RAID Product: partitionmanager Version: 3.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: c...@daniel.priv.no Target Milestone: --- 1. Add two 1 TB physical volumes to a new LVM volume group. Add one logical volume of 1 TB of type RAID1 to that volume group. You now have two identical disks and have consumed all available space in that volume group. 2. Open partitionmanager and select the volume group. Expected: Should show one volume of 2 (or “2x1”) TB, and 0 unallocated storage. Actual: Displays one volume of 1 TB and incorrectly shows 1 TB to be unallocated. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional
https://bugs.kde.org/show_bug.cgi?id=389191 Eike Hein changed: What|Removed |Added CC||h...@kde.org --- Comment #16 from Eike Hein --- I'm not super happy with this being marked WONTFIX. It makes the Wayland session extremely unpleasant to use for the time being. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 396708] It's easy to accidentally select a context menu item when you accidentally right-click
https://bugs.kde.org/show_bug.cgi?id=396708 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED URL||https://bugreports.qt.io/br ||owse/QTBUG-57849 Resolution|--- |UPSTREAM --- Comment #4 from Nate Graham --- Christoph is right, let's track this upstream. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 396774] New: Lokalize automatically wraps long lines at 80
https://bugs.kde.org/show_bug.cgi?id=396774 Bug ID: 396774 Summary: Lokalize automatically wraps long lines at 80 Product: lokalize Version: 2.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: sha...@ukr.net Reporter: hamidrjaf...@gmail.com Target Milestone: --- Translation robot of a package I am translating refuses to accept line breaks for paragraphs longer than 80 characters. The text string should remain as is. Lokalize wraps all lines at 80 without providing an option for turning it on / off. It requires rework after every bit of translation to remove line breaks. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396754] Add an option in the Latte setting that let the user uses the Super key to activate Application Menu
https://bugs.kde.org/show_bug.cgi?id=396754 --- Comment #4 from tr...@yandex.com --- You can write something like "(disable this option before removing Latte-dock)" into the option's label or a msgbox when the user checks into it... to warn him. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396754] Add an option in the Latte setting that let the user uses the Super key to activate Application Menu
https://bugs.kde.org/show_bug.cgi?id=396754 --- Comment #3 from tr...@yandex.com --- If there is some bug, then it is another problem need to be solved. That is another story. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396754] Add an option in the Latte setting that let the user uses the Super key to activate Application Menu
https://bugs.kde.org/show_bug.cgi?id=396754 --- Comment #2 from tr...@yandex.com --- It could possibly create some bug reports for KWin, in theory. But in fact, I don't see any bug with it. Moreover, almost everyone wants to activate the application menu with the Super key, they would very likely do this manually, whether you add that option or not. And they still report bugs wrongly. It does not depend on that option. So, adding that option (disabled by default, of course) would certainly affect nothing. It just makes the UX better. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396773] Dock appears twice with Kwin edge after hiding
https://bugs.kde.org/show_bug.cgi?id=396773 --- Comment #2 from el...@seznam.cz --- Yes, it is the left dock and your solution works perfectly. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390553] update xen support to Xen 4.10
https://bugs.kde.org/show_bug.cgi?id=390553 marma...@mimuw.edu.pl changed: What|Removed |Added CC||marma...@mimuw.edu.pl --- Comment #2 from marma...@mimuw.edu.pl --- I'm interested in this too. Any chance for this to be merged? I've tested it and it works fine. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396725] configure desktop effects dialog has scaling bug which makes reading the effects names imposible
https://bugs.kde.org/show_bug.cgi?id=396725 --- Comment #3 from Christoph Feck --- kwin repo at https://cgit.kde.org/kwin.git/ > Information about where to find documentation about the settingsapplication > would be appreciated too. https://docs.kde.org/index.php?language=en=kde-workspace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396770] Icons have wrong scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=396770 --- Comment #3 from el...@seznam.cz --- And when I say plasma panel, I mean System Tray icons which are quite small without PLASMA_USE_QT_SCALING=1. Also right click menu uses small icons which look like 16px icons on HiDPI display. And to make things more confusing, Wayland session seems to do this differently. System Tray icons have correct size and Latte Dock icons have double size. So this actually behaves like I would expect it to. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396770] Icons have wrong scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=396770 --- Comment #2 from el...@seznam.cz --- Let's say I use icons with size 32px and scale 1. Then I switch scale to 2, I still should be using icons with size 32px, right? Or is pixel always considered physical pixel and then I should use 64px? I'm coming from web world where pixel is considered as virtual pixel and screen density manages how many physical pixels are mapped to virtual pixel. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396773] Dock appears twice with Kwin edge after hiding
https://bugs.kde.org/show_bug.cgi?id=396773 Michail Vourlakos changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Michail Vourlakos --- If this is the Left dock then you must disable all touch gestures from plasma systemsettings... otherwise the usual stuff you must remove PLASMA_USE_QT_SCALING=1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396770] Icons have wrong scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=396770 Michail Vourlakos changed: What|Removed |Added Assignee|mvourla...@gmail.com|k...@davidedmundson.co.uk Component|plasmoid|general Product|latte-dock |plasmashell Version|0.8.0 |5.13.3 CC||plasma-b...@kde.org Target Milestone|--- |1.0 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396770] Icons have wrong scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=396770 --- Comment #1 from Michail Vourlakos --- > I use PLASMA_USE_QT_SCALING=1, because other apps do not scale correctly > without it (like original plasma panel). I suppose you must contact plasma devs and find out how to setup your environment correctly without PLASMA_USE_QT_SCALING=1 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396773] New: Dock appears twice with Kwin edge after hiding
https://bugs.kde.org/show_bug.cgi?id=396773 Bug ID: 396773 Summary: Dock appears twice with Kwin edge after hiding Product: latte-dock Version: 0.8.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: el...@seznam.cz Target Milestone: --- I have HiDPI display, scale factor 2, PLASMA_USE_QT_SCALING=1. I use setting "Dodge Active" and "Activate KWin edge after hiding". When dock is hidden and I move mouse to the edge, dock appears, then immediately hides and then shows again. Shortcut Meta+` doesn't have this problem. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396772] Dock doesn't dodge active window half way on HiDPI
https://bugs.kde.org/show_bug.cgi?id=396772 Michail Vourlakos changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Michail Vourlakos --- same issue you must remove PLASMA_USE_QT_SCALING=1 as mentioned at: https://bugs.kde.org/show_bug.cgi?id=396678 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396771] Blurry block above dock
https://bugs.kde.org/show_bug.cgi?id=396771 Michail Vourlakos changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Michail Vourlakos --- (In reply to elman from comment #0) > Created attachment 114074 [details] > Blurry block > > I have HiDPI display, scale factor 2, and I use PLASMA_USE_QT_SCALING=1. > > With release 0.8.0 I have weird blurry block above dock. See screenshot. you must disable PLASMA_USE_QT_SCALING=1 as mentioned also at: https://bugs.kde.org/show_bug.cgi?id=396678 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396772] New: Dock doesn't dodge active window half way on HiDPI
https://bugs.kde.org/show_bug.cgi?id=396772 Bug ID: 396772 Summary: Dock doesn't dodge active window half way on HiDPI Product: latte-dock Version: 0.8.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: el...@seznam.cz Target Milestone: --- Created attachment 114075 --> https://bugs.kde.org/attachment.cgi?id=114075=edit window not dogged I have HiDPI display, scale factor 2, use PLASMA_USE_QT_SCALING=1. I have set visibility Dodge Windows. With my settings dodging is not working halfway under dock. I have to move window more than half under dock to hide. I assume it has some relation to scaling factor. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396771] New: Blurry block above dock
https://bugs.kde.org/show_bug.cgi?id=396771 Bug ID: 396771 Summary: Blurry block above dock Product: latte-dock Version: 0.8.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: el...@seznam.cz Target Milestone: --- Created attachment 114074 --> https://bugs.kde.org/attachment.cgi?id=114074=edit Blurry block I have HiDPI display, scale factor 2, and I use PLASMA_USE_QT_SCALING=1. With release 0.8.0 I have weird blurry block above dock. See screenshot. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396770] New: Icons have wrong scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=396770 Bug ID: 396770 Summary: Icons have wrong scaling on HiDPI Product: latte-dock Version: 0.8.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: el...@seznam.cz Target Milestone: --- Created attachment 114073 --> https://bugs.kde.org/attachment.cgi?id=114073=edit Wrong scaling After update to 0.8.0 all icons in task manager have wrong scaling. Version 0.7.x was fine. Previously I used size 96px, now I have 48px. See screenshot attached. I use PLASMA_USE_QT_SCALING=1, because other apps do not scale correctly without it (like original plasma panel). Font DPI is set correctly to 192 DPI. Scaling factor is 2. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 396769] New: Chromium and kontact crashed
https://bugs.kde.org/show_bug.cgi?id=396769 Bug ID: 396769 Summary: Chromium and kontact crashed Product: kontact Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: daf...@gmail.com Target Milestone: --- Application: kontact (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-20-generic x86_64 Distribution: Ubuntu 18.04 LTS -- Information about the crash: I did nothing spezial. Just started it. Its a problem which came from one day to another - did not happend in the past ... maybe an update The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fae028e6600 (LWP 12713))] Thread 27 (Thread 0x7faca75ca700 (LWP 12907)): #0 0x7fadffde61ec in QElapsedTimer::isMonotonic() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fadffde4fce in QTimerInfoList::repairTimersIfNeeded() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fadffde5043 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fadffde667e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fadf8f8a998 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fadf8f8b36b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fadf8f8b54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fadffde690b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fadffd8b9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fadffbaa22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fadffbaf16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fadfb00b6db in start_thread (arg=0x7faca75ca700) at pthread_create.c:463 #12 0x7fadff28d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7facb382a700 (LWP 12804)): #0 0x7fadfb0119f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5624168c1870) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fadfb0119f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5624168c1820, cond=0x5624168c1848) at pthread_cond_wait.c:502 #2 0x7fadfb0119f3 in __pthread_cond_wait (cond=0x5624168c1848, mutex=0x5624168c1820) at pthread_cond_wait.c:655 #3 0x7fadffbb059b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fadffba8c0b in QSemaphore::acquire(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7facb8a4080c in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so #6 0x7fadffbaf16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fadfb00b6db in start_thread (arg=0x7facb382a700) at pthread_create.c:463 #8 0x7fadff28d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7facb9834700 (LWP 12801)): #0 0x7fadff27c0b4 in __GI___libc_read (fd=76, buf=0x7facb9833810, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fadf8fcf960 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fadf8f8af27 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fadf8f8b3e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fadf8f8b54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fadffde690b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fadffd8b9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fadffbaa22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fadffbaf16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fadfb00b6db in start_thread (arg=0x7facb9834700) at pthread_create.c:463 #10 0x7fadff28d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7faccab12700 (LWP 12789)): #0 0x7fadff27c0b4 in __GI___libc_read (fd=70, buf=0x7faccab11810, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fadf8fcf960 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fadf8f8af27 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fadf8f8b3e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fadf8f8b54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fadffde690b in QEventDispatcherGlib::processEvents(QFlags) () at
[frameworks-plasma] [Bug 396177] Plasmashell dialog regression when KDE is used with Xmonad introduced by fix for 381242
https://bugs.kde.org/show_bug.cgi?id=396177 Bill Sun changed: What|Removed |Added CC||billk...@gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Bill Sun --- And here's the related reports on XMonad's github: https://github.com/xmonad/xmonad/issues/174#issuecomment-406886552 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396725] configure desktop effects dialog has scaling bug which makes reading the effects names imposible
https://bugs.kde.org/show_bug.cgi?id=396725 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- kcmkwin/kwincompositing -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396474] No information about pasting image failure, plus issues when pasting images from Chrome
https://bugs.kde.org/show_bug.cgi?id=396474 --- Comment #2 from konrados --- @Scott > I wonder if this is specific to Ubuntu 16.04 Well, could be. I even installed "CopyQ" program, which enables previewing the clipboard content, so after copying something I can see what it is (image / text). But... my investigation didn't bring any clear results :( I mean I admit I gave up, because it seems there are problems with the CopyQ program itself. Sometimes after copying an image I can see... two images listed there, each with different quality o.O I thought that maybe it's simpler for Krita's devs to see what is exactly going on, step by step (what does the program receives from OS), than for me to make wild guesses based on another app which could be buggy (CopyQ):) -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 228054] allow specifying order of device actions
https://bugs.kde.org/show_bug.cgi?id=228054 --- Comment #4 from Gregor Mi --- I have to correct myself: After a reboot, "Open with File Manager" is on the second position in the list of three items. The order is also not alphabetically. This could be filed as a new issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396766] Can't add collection on removable disk
https://bugs.kde.org/show_bug.cgi?id=396766 --- Comment #2 from paul --- Yes, checking the "use native file dialog" under misc changes things so that there's a level corresponding to the top of the Mac file hierarchy, from which I can select the external drive. Oddly, the folder display under "macintosh HD" is still wonky. But at least selecting is possible. thanks -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 389591] awk syntax: incorrect parse of double quotes in /.../ regexp
https://bugs.kde.org/show_bug.cgi?id=389591 jonathan.poe...@gmail.com changed: What|Removed |Added URL||https://phabricator.kde.org ||/D12854 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://cgit.kde.org/syntax ||-highlighting.git/commit/?i ||d=d5c5f4d3c85ad9762b198df78 ||5acb7e6c990e41a CC||jonathan.poe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396766] Can't add collection on removable disk
https://bugs.kde.org/show_bug.cgi?id=396766 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Maybe you have to activate the file dialog from the system only in the digiKam settings under Miscellaneous. Please test it. Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 396768] New: LibreOffice PDF Export Dialog focuses file list instead of Name field
https://bugs.kde.org/show_bug.cgi?id=396768 Bug ID: 396768 Summary: LibreOffice PDF Export Dialog focuses file list instead of Name field Product: frameworks-kio Version: 5.47.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: fa...@kde.org Reporter: codestr...@posteo.org CC: kdelibs-b...@kde.org Target Milestone: --- I am not sure if this is the correct place to report this bug. Today I noticed the following: 1. Have a LibreOffice document open (e.g. Writer) 2. Click the Export to PDF button => a Plasma style Export... dialog opens 3. Hit the Enter key. => The file is not saved as expected but the the current selection of the file list is copied to the Name field of the dialog. The reason is, that the file list is focused instead of the Name field. I could not find another Save file dialog that also behaves this way. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 396767] New: kdesu doesn't work when "use_pty" sudo option is enabled
https://bugs.kde.org/show_bug.cgi?id=396767 Bug ID: 396767 Summary: kdesu doesn't work when "use_pty" sudo option is enabled Product: frameworks-kdesu Version: 5.48.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: itgvk...@grr.la Target Milestone: --- "use_pty" is sudo option which enhance its security[0] and is supposed to be enabled in future sudo release[1]. You can enable it by adding below toy sudoers config: Defaults use_pty [0] http://www.openwall.com/lists/oss-security/2018/06/12/2 [1] http://www.openwall.com/lists/oss-security/2018/06/12/4 Unfortunately after enabling it kdesu stops working. There is following message in comsole: $ QT_LOGGING_RULES= kdesu -d -c echo [ /build/kdesu/src/kdesu-5.48.0/src/stubprocess.cpp : 219 ] Unknown request: "ok" -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396684] Calendar View not available for scheduled transactions
https://bugs.kde.org/show_bug.cgi?id=396684 --- Comment #3 from Jack --- I'll add it to the pending list of doc updates. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396766] Can't add collection on removable disk
https://bugs.kde.org/show_bug.cgi?id=396766 caulier.gil...@gmail.com changed: What|Removed |Added Component|Albums-Engine |Bundle-MacOS CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 396742] EKOS | Capture | multiple occurrence of the same sequence job ignored
https://bugs.kde.org/show_bug.cgi?id=396742 --- Comment #10 from Wolfgang Reissenberger --- Bug fix submitted as https://phabricator.kde.org/D14280 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396684] Calendar View not available for scheduled transactions
https://bugs.kde.org/show_bug.cgi?id=396684 --- Comment #2 from conner.r.phill...@gmail.com --- Uhm, then maybe it should be removed from the manual? Section 10.7. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396766] New: Can't add collection on removable disk
https://bugs.kde.org/show_bug.cgi?id=396766 Bug ID: 396766 Summary: Can't add collection on removable disk Product: digikam Version: 5.9.0 Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: major Priority: NOR Component: Albums-Engine Assignee: digikam-bugs-n...@kde.org Reporter: d...@pw.users.panix.com Target Milestone: --- Created attachment 114072 --> https://bugs.kde.org/attachment.cgi?id=114072=edit /Volumes and other folders should be here Because on current Mac OS (10.13.5) there appears to be no way to select a removable disk. Removable disks are not displayed at the top level of the file-browser dialog, nor is /Volumes among the folders displayed when / is selected for viewing. This makes digikam essentially useless for users affected by this bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396765] schema update to V 9 failed
https://bugs.kde.org/show_bug.cgi?id=396765 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Tomorrow I will upload a customized dbconfig.xml with the patch for digiKam-5.9.0 from bug 393855 here. Maik *** This bug has been marked as a duplicate of bug 393855 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393855] MySQL/MariaDB upgrade fails
https://bugs.kde.org/show_bug.cgi?id=393855 Maik Qualmann changed: What|Removed |Added CC||stschoe...@web.de --- Comment #2 from Maik Qualmann --- *** Bug 396765 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 321669] multipart mails incompletely displayed
https://bugs.kde.org/show_bug.cgi?id=321669 Denis Kurz changed: What|Removed |Added Version|4.14.10 |5.8.3 Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #8 from Denis Kurz --- Oh man, now I wonder how I could miss that. I'm sorry. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396765] New: schema update to V 9 failed
https://bugs.kde.org/show_bug.cgi?id=396765
Bug ID: 396765
Summary: schema update to V 9 failed
Product: digikam
Version: 5.9.0
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Database-Schema
Assignee: digikam-bugs-n...@kde.org
Reporter: stschoe...@web.de
Target Milestone: ---
After upgrading the digikam rpm package from OpenSuse Leap 42.3 to OpenSuse
Leap 15.0 with digikam-5.9.0-lp150.1.3.x86_64 rpm package, digikam tries to
convert the MySQL dackend database from schema version 8 to schema version 9
and fails. The error messages are:
digikam.general: AlbumWatch use QFileSystemWatcher
digikam.general: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam_metadata"
DB Thumbs Name: "digikam_thumbnails"
DB Face Name: ""
Connect Options: ""
Host Name:"localhost"
Host port:3306
Internal Server: false
Internal Server Path: ""
Internal Server Serv Cmd: ""
Internal Server Init Cmd: ""
Username: "digikam_user"
Password: "XX"
digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected: 3 found: 3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version 8
digikam.coredb: Core database: makeUpdates 8 to 9
digikam.dbengine: Failure executing query:
""
Error messages: "QMYSQL: Unable to execute query" "Illegal mix of collations
(utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '='"
1267 2
Bound values: ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV7ToV9" ]
Statement [ "CALL drop_index_if_exists('AlbumRoots', 'identifier');" ]
digikam.coredb: Core database: schema update to V 9 failed!
digikam.coredb: Core database: cannot process schema initialization
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-ktexteditor] [Bug 396764] KTextEditor does not accept soft-hyphen as input
https://bugs.kde.org/show_bug.cgi?id=396764 --- Comment #1 from Tore Havn --- I should of course specify that the soft-hyphen character is U+00AD. (See https://unicode-table.com/en/00AD/) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 396764] New: KTextEditor does not accept soft-hyphen as input
https://bugs.kde.org/show_bug.cgi?id=396764 Bug ID: 396764 Summary: KTextEditor does not accept soft-hyphen as input Product: frameworks-ktexteditor Version: 5.48.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: v...@veqz.net Target Milestone: --- I've recently added soft-hyphen as a key on my keyboard layout, and found that Kate does not accept it as input. Hitting the key has no effect in Kate. I tried the same in LibreOffice Writer and in KWrite. LibreOffice Writer handles it as expected, and creates a zero-width character in the text, which turns to a hyphen when the word it is in encounters a line break. KWrite does not react, same as in Kate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 --- Comment #138 from Antonio Orefice --- I don't understand; the case specific to the issue this bug is reporting (Turning off compositing breaks Plasma panel rendering) is fixed? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396582] Cannot drag folder from Dolphin to Google Drive via Google Chrome
https://bugs.kde.org/show_bug.cgi?id=396582 --- Comment #4 from Julian Schraner --- Okay, thanks for the bug report and your testing :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396725] configure desktop effects dialog has scaling bug which makes reading the effects names imposible
https://bugs.kde.org/show_bug.cgi?id=396725 --- Comment #1 from Matthias Fabinski --- small update: I tested with different scaling factors and found out, that with 1.0, 2.0 and 3.0 the dialog works properly. The following scaling factors where tested and had similar graphical glitches: 1.2, 1.5, 2.5. The fontsetting has no impact on this, so it can be ignored in further work on this bug. Can someone point me to the sourcecode (repository) of the Desktop Effects Dialog, as i was not able to find it. Information about where to find documentation about the settingsapplication would be appreciated too. Kind regards, Matthias Fabinski -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 230744] Dolphin ignores change of archive files
https://bugs.kde.org/show_bug.cgi?id=230744 Julian Schraner changed: What|Removed |Added Component|tar |default Status|UNCONFIRMED |CONFIRMED CC||juliquad...@gmail.com Product|kio |kio-extras Version|4.4 |18.04.3 Ever confirmed|0 |1 --- Comment #1 from Julian Schraner --- This is still the case with Dolphin 18.04.3 and KDE Frameworks 5.48, you need to force a refresh with F5 to see the new contents. Moving to kio-extras. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 137543] open large tgz file results in full /tmp partition and displays wrong content list of tar-file in konqueror
https://bugs.kde.org/show_bug.cgi?id=137543 Julian Schraner changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||juliquad...@gmail.com --- Comment #1 from Julian Schraner --- I cannot test this bug on my own because I don't have a separate /tmp partition. If this email does somehow still reach you and you do still have a setup similar to the one described in the original report it'd be great if you could try to reproduce this behavior - if it does still exist I'd need to move it over to kio-extras. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 106838] Kio tar:// rely on file extension to determine file type
https://bugs.kde.org/show_bug.cgi?id=106838 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #2 from Julian Schraner --- I agree with Thiago, this would most likely require a non-trivial amount of resources spent whenever you open a .tar file and might then cause more bugs so it's not really worth the effort. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 95496] Writing into tar:/ should be possible
https://bugs.kde.org/show_bug.cgi?id=95496 Julian Schraner changed: What|Removed |Added Product|kio |kio-extras Version|3.3 |18.04.3 CC||juliquad...@gmail.com Component|tar |default --- Comment #2 from Julian Schraner --- This wish is still not present with KDE Frameworks 5.48 & Dolphin 18.04.3 and even though I am not sure how easy this would be to implement this would surely be a cool feature. I'll move it to kio-extras for now. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 396742] EKOS | Capture | multiple occurrence of the same sequence job ignored
https://bugs.kde.org/show_bug.cgi?id=396742 --- Comment #9 from Wolfgang Reissenberger --- OK, thanks for the hint. I've installed arc and will try to use it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396763] New: Print Settings KDE applet crashes on start
https://bugs.kde.org/show_bug.cgi?id=396763 Bug ID: 396763 Summary: Print Settings KDE applet crashes on start Product: Discover Version: 5.13.1 Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: ali...@she-devel.com Target Milestone: --- Application: plasma-discover (5.13.1) Qt Version: 5.10.1 Frameworks Version: 5.47.0 Operating System: Linux 4.9.0-3-amd64 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: I tried starting the application two ways: with left-click on "Print Settings" in launcher menu, which produced an icon in the system tray for one second, then nothing. Then I tried right-click on the same launcher item and selected "Manage Print Settings", which tried longer to open but still crashed. - Unusual behavior I noticed: No output is produced with the left click: no error message. The right click produces some notification popups that report errors. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f281cb58300 (LWP 25960))] Thread 12 (Thread 0x7f27d1338700 (LWP 25980)): #0 0x7f282135acf4 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2821314c39 in g_main_context_query () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f28213153b7 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f282131554c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f28266fd1bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f28266a0b6a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f28264b67ea in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f28264bbb4f in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2822cd4f2a in start_thread (arg=0x7f27d1338700) at pthread_create.c:463 #9 0x7f28261c1edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f27d1b39700 (LWP 25974)): #0 0x7f282135acf4 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2821314988 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f282131536b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f282131554c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f28266fd1bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f28266a0b6a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f28264b67ea in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f28264bbb4f in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2822cd4f2a in start_thread (arg=0x7f27d1b39700) at pthread_create.c:463 #9 0x7f28261c1edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f27d313d700 (LWP 25972)): #0 0x7f282135acd9 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2821314b81 in g_main_context_query () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f28213153b7 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f28213157d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f27e10cde26 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x7f282133ce05 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f2822cd4f2a in start_thread (arg=0x7f27d313d700) at pthread_create.c:463 #7 0x7f28261c1edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f27d393e700 (LWP 25971)): #0 0x7f282135acd9 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f28213142e0 in g_main_context_acquire () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f28213152f5 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f282131554c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2821315591 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f282133ce05 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f2822cd4f2a in start_thread (arg=0x7f27d393e700) at pthread_create.c:463 #7 0x7f28261c1edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f27e3903700 (LWP 25968)): #0 0x7f28261b7739 in __GI___poll (fds=0x7f27dc11d910, nfds=1, timeout=48347) at
[latte-dock] [Bug 396753] Show a [Super] badge for Application Menu if the user has set the [Super] key to activate it
https://bugs.kde.org/show_bug.cgi?id=396753 --- Comment #1 from Michail Vourlakos --- As mentioned earlier, Currently there is no winkey badge and the codepaths are different, Meta is called from KWin and applets/tasks activation from KGlobalAccel. Even if we want to just a badge to be shown when Meta+' is triggered then other cases should also be considered. What happens when app launcher is in different dock? What happens if the app launcher is between other applets? Only I can think of is to show a Meta badge (https://www.utf8icons.com/character_image/8984-place-of-interest-sign.png , unicode character \u2318) for application launcher without showing its unified shortcut at all cases and at the same time provide the unified Global Shortcuts flag... This way the following can be supported, 1-2-⌘-4-5-6-7 ⌘-1-2-3-4-5-6-7-8 with no unified shortcuts ⌘-2-3-4-5-6-7-8 with unified shortcuts 1-2-3-4-5-6-7-8 and ⌘ in different dock The unified global shortcuts can be added at Latte settings Window also but only for Master branch, v0.8 is in string freeze -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 321669] multipart mails incompletely displayed
https://bugs.kde.org/show_bug.cgi?id=321669 --- Comment #7 from Rawk --- Dennis, as I've written in my comment it used to be KMail 5.8.1 at that time, now it is 5.8.3. Currently the best way to handle those multipart messages is to show the message structure (menu "Message") and click on the HTML part. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 396762] New: convert SVG flowRoot to Text
https://bugs.kde.org/show_bug.cgi?id=396762 Bug ID: 396762 Summary: convert SVG flowRoot to Text Product: Oxygen Version: 5.13.3 Platform: Other OS: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: icons Assignee: n...@oxygen-icons.org Reporter: jo.spa...@gmx.at Target Milestone: --- Created attachment 114071 --> https://bugs.kde.org/attachment.cgi?id=114071=edit Conatining corrected files I repaired some SVGs, that contained (empty and some non-empty) flowRoot and converted it to SVG-1.1-DTD-valid text. https://github.com/KDE/oxygen-icons5/pull/2 Maybe two examples: * https://commons.wikimedia.org/wiki/File:Oxygen480-mimetypes-message-news.svg#filehistory * https://commons.wikimedia.org/wiki/File:Oxygen480-mimetypes-hidef-text-x-rpm-spec.svg#filehistory -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396754] Add an option in the Latte setting that let the user uses the Super key to activate Application Menu
https://bugs.kde.org/show_bug.cgi?id=396754 --- Comment #1 from Michail Vourlakos --- (In reply to trmdi from comment #0) > Currently the user has to do this manually: > https://github.com/psifidotos/Latte-Dock/wiki/F.A.Q.#q-can-i-use-my-super- > key-to-open-the-app-launcher > > I suggest a new option in the Latte setting to help the user archives that > more easily with just a click. That option will be disabled by default. unfortunately I had promised to Martin from KWin team to not automate this because he was afraid that this would create a bunch of bug reports for KWin. So I can not add it without first communicate with KWin team. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- >out of by setting BorderlessMaximizedWindows=true Setting how? -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 228054] allow specifying order of device actions
https://bugs.kde.org/show_bug.cgi?id=228054 --- Comment #3 from Gregor Mi --- Just for reference: On my current Plasma 5 installation, "Open with File Manager" is listed first. So the requested wish is seems to be implemented. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 365257] Columns in main window do not resize properly to fit their contents
https://bugs.kde.org/show_bug.cgi?id=365257 Andrey Bondarenko changed: What|Removed |Added CC||abon...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 374602] Cannot resize columns
https://bugs.kde.org/show_bug.cgi?id=374602 Andrey Bondarenko changed: What|Removed |Added CC||abon...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 337105] Shortcut Alt+Enter not enabled for Desktop icons
https://bugs.kde.org/show_bug.cgi?id=337105 --- Comment #3 from Gregor Mi --- Just recently, the issues was fixed in Plasma 5: https://bugs.kde.org/show_bug.cgi?id=389862 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396582] Cannot drag folder from Dolphin to Google Drive via Google Chrome
https://bugs.kde.org/show_bug.cgi?id=396582 Gus Gustafson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Gus Gustafson --- Ok, after more testing, I found that I need to "swirl" my drag-selection over the Google Drive and Dropbox webpages a few more times to get the webpage to recognize it. Working for both Firefox and G Chrome... Marking resolved/invalid. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396582] Cannot drag folder from Dolphin to Google Drive via Google Chrome
https://bugs.kde.org/show_bug.cgi?id=396582 Gus Gustafson changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #2 from Gus Gustafson --- It is not working with Firefox either Versions: Dolphin: 17.12.3 Kubuntu: 18.04 Plasma: 5.12.6 Firefox: 61.0.1 (64bit) Google Chrome: 67.0.3396.99-1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 393441] CSV import: description field original text not saved permanently
https://bugs.kde.org/show_bug.cgi?id=393441 --- Comment #4 from Martin Steigerwald --- (In reply to Jack from comment #3) > If you provide a suggested improvement to the manual, I'll be glad to > consider including it. You could also suggest a change to the actual > wording included on the dialog itself, but those are constrained by > real-estate > and programmer time. […] I reviewed the documentation and I think it is good. I did not know the CSV importer was documented (until I found a bug report about this by accident today). I think the GUI should make it obvious that you can add mutiple fields to memo. Usually ways would be to have a list were the user can select mutiple items via shift or ctrl + mouse click or to have a check mark for each field and the user can select mutiple ones. Also I´d probably allow to add any field there, no matter whether it is used elsewhere or not, in any order. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 groveover changed: What|Removed |Added CC||a...@gajewiak.com --- Comment #1 from groveover --- The same problem in KDE Neon after update to Plasma 5.13.3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396761] New: menu items "no text"
https://bugs.kde.org/show_bug.cgi?id=396761 Bug ID: 396761 Summary: menu items "no text" Product: okular Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: amye...@gmail.com Target Milestone: --- Created attachment 114070 --> https://bugs.kde.org/attachment.cgi?id=114070=edit screenshot In the OKULAR installed on this computer, some of the menu items say "no text". See screenshot. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 395352] problem with importing of csv/ascii data-files with mixed text/numeric columns
https://bugs.kde.org/show_bug.cgi?id=395352 --- Comment #2 from Alexander Semke --- Eduard, can you please provide more info on this? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396760] New: accounts overview: improve initial display (usability)
https://bugs.kde.org/show_bug.cgi?id=396760 Bug ID: 396760 Summary: accounts overview: improve initial display (usability) Product: kmymoney Version: 5.0.1 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: mar...@lichtvoll.de Target Milestone: --- Created attachment 114069 --> https://bugs.kde.org/attachment.cgi?id=114069=edit initial display of accounts overview. If you expand the categories, the sorting is reverse When starting up KMyMoney I in the accounts overview - Verbindlichkeiten (debts) - Anlagen (assets) in exactly this order. Thus I first expand both categories to actually see my accounts. Then I reverse the sorting of account names so I receive proper alphabetical order. Then I still miss from Qt 4 or less versions of KMyMoney that it also shows the current balance of each account in a second column. I can open a new issue for that one. Thus I´d like a more suitable initial display of the accounts list. :) -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 106908] Unable to extract files from ZIP using internal plugin
https://bugs.kde.org/show_bug.cgi?id=106908 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com Status|CONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #4 from Julian Schraner --- Imploded zip files are extremely uncommon nowadays and the effort to add support in Dolphin/Konqueror is most likely way higher than the reward, especially because you should be able to extract them just fine using unzip. We have also added a dialog so the user should not run into zero size files. Therefore I'll close this report as WONTFIX, but we will of course accept patches that add support for this compression method. Thanks for your understanding! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396759] New: CSV: ordering of buttons when finishing wizard
https://bugs.kde.org/show_bug.cgi?id=396759 Bug ID: 396759 Summary: CSV: ordering of buttons when finishing wizard Product: kmymoney Version: 5.0.1 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: mar...@lichtvoll.de Target Milestone: --- Created attachment 114068 --> https://bugs.kde.org/attachment.cgi?id=114068=edit screenshot showing the button order when finishing the importer (german text) Usually when I run the CSV import wizard, then I like to import an CSV file. I found that I clicked on "Finish" (german "Abschließen") instead of "Import CSV file" (german "CSV-Datei importieren") due to the expectation that the most usual action would be next to the cancel button. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 394508] ksmserver-logout-greeter crashes after GPU switch using prime-select (Backtrace included) (nvidia-384 driver)
https://bugs.kde.org/show_bug.cgi?id=394508 saurabh changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 394508] ksmserver-logout-greeter crashes after GPU switch using prime-select (Backtrace included) (nvidia-384 driver)
https://bugs.kde.org/show_bug.cgi?id=394508 saurabh changed: What|Removed |Added CC||saurabhpradhan1...@gmail.co ||m --- Comment #1 from saurabh --- I am facing same issue. For me it happens both way switching from nvidia to intel and vise versa. Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fba1ad57940 (LWP 2641))] Thread 2 (Thread 0x7fba0293f700 (LWP 2643)): #0 0x7fba1660074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fba0f57d38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fba0f57d49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fba16f180bb in QEventDispatcherGlib::processEvents (this=0x7fb9f40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fba16ebf5ba in QEventLoop::exec (this=this@entry=0x7fba0293ec40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7fba16cf45e4 in QThread::exec (this=this@entry=0x7fba17dc2d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:525 #6 0x7fba17b49f35 in QDBusConnectionManager::run (this=0x7fba17dc2d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7fba16cff727 in QThreadPrivate::start (arg=0x7fba17dc2d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:367 #8 0x7fba111d96ba in start_thread (arg=0x7fba0293f700) at pthread_create.c:333 #9 0x7fba1660c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fba1ad57940 (LWP 2641)): [KCrash Handler] #6 0x7fba1653a428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fba1653c02a in __GI_abort () at abort.c:89 #8 0x7fba16cd190d in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1842 #9 QMessageLogger::fatal (this=this@entry=0x7ffd8b60ab70, msg=msg@entry=0x7fba037af400 "Could not initialize GLX") at global/qlogging.cpp:880 #10 0x7fba037acb4f in QGLXContext::init (this=0xc27d20, screen=0xb90a80, share=) at qglxintegration.cpp:375 #11 0x7fba037a9e87 in QXcbGlxIntegration::createPlatformOpenGLContext (this=, context=0x7ffd8b60ad00) at qxcbglxintegration.cpp:185 #12 0x7fba067b2501 in QXcbIntegration::createPlatformOpenGLContext (this=, context=0x7ffd8b60ad00) at qxcbintegration.cpp:281 #13 0x7fba174c515d in QOpenGLContext::create (this=this@entry=0x7ffd8b60ad00) at kernel/qopenglcontext.cpp:612 #14 0x7fba037ad395 in QGLXContext::queryDummyContext () at qglxintegration.cpp:757 #15 0x7fba037ad9c9 in QGLXContext::supportsThreading () at qglxintegration.cpp:804 #16 0x7fba1968fe3b in QSGRenderLoop::instance () at scenegraph/qsgrenderloop.cpp:205 #17 0x7fba196fee9a in QQuickWindowPrivate::init (this=0xbcbf10, c=0xbcbc10, control=0x0) at items/qquickwindow.cpp:554 #18 0x7fba1a807dd4 in KQuickAddons::QuickViewSharedEngine::QuickViewSharedEngine (this=0xbcbc10, parent=) at /workspace/build/src/quickaddons/quickviewsharedengine.cpp:148 #19 0x004075e8 in KSMShutdownDlg::KSMShutdownDlg (this=0xbcbc10, parent=, maysd=, choose=, sdtype=KWorkSpace::ShutdownTypeNone, plasmaShell=0x0) at /workspace/build/ksmserver/logout-greeter/shutdowndlg.cpp:81 #20 0x00406600 in Greeter::adoptScreen (this=this@entry=0x7ffd8b60b190, screen=0xb89400) at /workspace/build/ksmserver/logout-greeter/main.cpp:112 #21 0x00406890 in Greeter::init (this=this@entry=0x7ffd8b60b190) at /workspace/build/ksmserver/logout-greeter/main.cpp:104 #22 0x00405f03 in main (argc=6, argv=) at /workspace/build/ksmserver/logout-greeter/main.cpp:223 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395517] can't set print default to duplex
https://bugs.kde.org/show_bug.cgi?id=395517 --- Comment #7 from Amnon --- I tried MuPDF - it has virtually no controls, and no print command as far as I can tell. Am I to understand (by reading between the lines) that there is some breakdown between the OKULAR team and the UBUNTU team? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 329579] Extracted file is corrupt
https://bugs.kde.org/show_bug.cgi?id=329579 Julian Schraner changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Component|zip |default Assignee|fa...@kde.org |plasma-b...@kde.org Version|4.11.3 |18.04.3 Product|kio |kio-extras Ever confirmed|0 |1 CC||juliquad...@gmail.com --- Comment #1 from Julian Schraner --- I can reproduce this behavior using KDE Frameworks 5.48, relocating to kio-extras. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396758] New: CSV: creates bogus payee´s with csv file with combines payee/description field
https://bugs.kde.org/show_bug.cgi?id=396758 Bug ID: 396758 Summary: CSV: creates bogus payee´s with csv file with combines payee/description field Product: kmymoney Version: 5.0.1 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: mar...@lichtvoll.de Target Milestone: --- Created attachment 114067 --> https://bugs.kde.org/attachment.cgi?id=114067=edit privacy-edited csv file, saved as UTF-8 by Libreoffice, was ISO-8859-15 or so I have no idea what to do about it, but when having a file that uses a description file either for description the type of transaction or the recipient, for any lines that describe the type of transaction KMyMoney adds a payee. For example I attach a privacy-edited file for a debit card. There are description fields like "compensation debit card according to invoice from some date". KMyMoney adds a payee for each of them. In case of the description with a date or another information that changes these add up. Probably it would be easier to be able to leave out the description/payee field altogether and stuff it all into memo. Then I can just go through the entries myself and add the right payee with autocomplete. Another option would be a way to auto clean up payees without any transactions. Even better would be a standard CSV format for all banks and debit cards with one field for payee and one for description… but well… that would be up to the banks, so KMyMoney has to work with what it receives. Related to: 393441 - CSV import: description field original text not saved permanently -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 325173] krusader has problems opening certain zip files or showing their content correctly
https://bugs.kde.org/show_bug.cgi?id=325173 Julian Schraner changed: What|Removed |Added Assignee|fa...@kde.org |plasma-b...@kde.org Component|zip |default Status|UNCONFIRMED |CONFIRMED CC||juliquad...@gmail.com Ever confirmed|0 |1 Product|kio |kio-extras Version|unspecified |18.04.3 --- Comment #3 from Julian Schraner --- I can still reproduce this behavior with the third zip you mentioned. I'll move the bug over to kio-extras. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 393441] CSV import: description field original text not saved permanently
https://bugs.kde.org/show_bug.cgi?id=393441 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net Severity|normal |wishlist --- Comment #3 from Jack --- If you provide a suggested improvement to the manual, I'll be glad to consider including it. You could also suggest a change to the actual behavior or to wording included on the dialog itself, but those are constrained by real-estate and programmer time. However, I'm switching this to wish-list, so it can server as a reminder. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 393441] CSV import: description field original text not saved permanently
https://bugs.kde.org/show_bug.cgi?id=393441 Martin Steigerwald changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Martin Steigerwald --- (In reply to Jack from comment #1) > If you set the column for the PAYEE field first, then you can set the same > column for inclusion in the MEMO field. The interface is not as clear as it > could be about what happens, but it does work. You can also include > multiple columns in the MEMO field, but they need to be selected for any > other purpose first, and then assign them to the MEMO field. Whoa. This works. It is very well hidden tough. I think I let this bug open for now, as I think this is an usability issue. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 379567] Big Break Now
https://bugs.kde.org/show_bug.cgi?id=379567 --- Comment #9 from Albert Astals Cid --- Ah ok, that makes more sense now :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396729] crashes when trying to close any window
https://bugs.kde.org/show_bug.cgi?id=396729 --- Comment #7 from miklos --- (In reply to David Edmundson from comment #6) > >I suspected that the problem is that I'm not using Breeze window decorations > > what are you using? I'm using Plastik. Its colored window border allows me to see more clearly which window is active than Breeze's shadows. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396757] New: Texts copying generates mirrored texts.
https://bugs.kde.org/show_bug.cgi?id=396757 Bug ID: 396757 Summary: Texts copying generates mirrored texts. Product: okular Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: dr_w...@hotmail.com Target Milestone: --- RTL texts copying generates mirrored texts. and the search does not work with RTL words or texts. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396679] Open Album in Terminal
https://bugs.kde.org/show_bug.cgi?id=396679 --- Comment #5 from caulier.gil...@gmail.com --- This first approach sound acceptable. Look also the Qtbase approach, even if it use a wrong way with KDE and KIO, and it's a little bit complicated. At least all most important cases are processed, and it must work with MacOS: https://github.com/qt/qtbase/blob/5.11/src/platformsupport/services/genericunix/qgenericunixservices.cpp#L78 You can certainly take few ideas from this code. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394335] Can't open System Settings category with Enter key
https://bugs.kde.org/show_bug.cgi?id=394335 Nate Graham changed: What|Removed |Added Version Fixed In||5.13.4 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396679] Open Album in Terminal
https://bugs.kde.org/show_bug.cgi?id=396679
--- Comment #4 from Kusi ---
I investigated a bit the problem of launching a terminal cross platform
The following code snippet allows to handle the case of KDE, but it should be
easy to extend it for various desktop environments. I just guessed the values
for GNOME, I didn't test for GNOME
QByteArray env = qgetenv("XDG_CURRENT_DESKTOP");
QString desktopEnvironment = QString::fromLocal8Bit(env.data());
QMap terminals;
terminals["KDE"] = "konsole";
terminals["GNOME"] = "gnome-shell";
terminals["WINDOWS"] = "cmd.exe";
if (terminals.contains(desktopEnvironment))
{
QProcess *process = new QProcess(this);
QString terminal = terminals[desktopEnvironment];
QString folder = "/share/pictures";
process->setWorkingDirectory(folder);
process->start(terminal);
}
While getting the current platform (linux/win/osx) seems straight forward with
either QSysInfo or https://wiki.qt.io/Get_OS_name, it is tricky to get the
desktop environment, but it is still feasible w/o too much hassle:
https://stackoverflow.com/questions/47022134/how-can-i-find-out-at-runtime-which-desktop-environment-that-a-qt-application
Remember, if the terminal is not available, the option is just disabled. It
doesn't have to exist for every exotic desktop environment
what do you think?
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 396756] New: ‘Holidays’ and ‘Timezones’ categories in clock/calendar settings has too narrow columns for names and descriptions
https://bugs.kde.org/show_bug.cgi?id=396756 Bug ID: 396756 Summary: ‘Holidays’ and ‘Timezones’ categories in clock/calendar settings has too narrow columns for names and descriptions Product: plasmashell Version: 5.13.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: k...@huftis.org Target Milestone: 1.0 Created attachment 114066 --> https://bugs.kde.org/attachment.cgi?id=114066=edit Screenshot showing the default narrow columns The ‘Holidays’ category in clock/calendar settings has too narrow columns for the ‘Name’ and ‘Description’ columns. This results in much of the text being clipped. Even though there’s lots of space available, the actual table columns only occupy a fraction of the space reserved for the table. The same issue is present for the ‘Timezones’ category. I’ll attach a screenshot showing the problem. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 384075] korganizer crashes when selecting a calendar to be shown in agenda/day/week/month view (regression 17.08.*)
https://bugs.kde.org/show_bug.cgi?id=384075 Denis Kurz changed: What|Removed |Added Version Fixed In||5.7.3 Latest Commit||a3a66bb10020e6fbdd354b4ecc6 ||c0fee6741c467 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #13 from Denis Kurz --- Sorry, I haven't seen this in some time now. I'm pretty sure it was a release build, though, if it still matters. Apparently, this was fixed in https://phabricator.kde.org/D11517 as David describes the same problem, which was some bug in incidencetreemodel.cpp's greaterThan function. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 --- Comment #137 from Allan --- (In reply to Mahendra Tallur from comment #136) > Hi ! I don't want to get you people excited over nothing but here's an It's a partial excitement. It doesn't solve the other cases that break plasma rendering, like Lockscreen and many OpenGL apps (including browsers occasionally). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396755] New: System Settings Crash
https://bugs.kde.org/show_bug.cgi?id=396755 Bug ID: 396755 Summary: System Settings Crash Product: systemsettings Version: 5.12.6 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mircosoft1...@gmail.com Target Milestone: --- Application: systemsettings5 (5.12.6) Qt Version: 5.10.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.6-200.fc28.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: I applied new Look and Feel settings, clicked the close button and the dialog crashed. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9fd4097940 (LWP 2634))] Thread 6 (Thread 0x7f9f8ed02700 (LWP 2934)): #0 0x7f9fc77acf83 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #1 0x7f9fc77adb1b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f9fc77add10 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f9fcfb2fc2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f9fcfade12b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f9fcf92c9c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f9fcde413a9 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f9fcf93111d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f9fcc4cf594 in start_thread () at /lib64/libpthread.so.0 #9 0x7f9fcec6e0df in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f9f53e2e700 (LWP 2830)): #0 0x7f9fc77ad081 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #1 0x7f9fc77adb1b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f9fc77add10 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f9fcfb2fc2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f9fcfade12b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f9fcf92c9c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f9fcf93111d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f9fcc4cf594 in start_thread () at /lib64/libpthread.so.0 #8 0x7f9fcec6e0df in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f9f8700 (LWP 2653)): #0 0x7f9fcec5f0c4 in read () at /lib64/libc.so.6 #1 0x7f9fc77f3070 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f9fc77ad6db in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f9fc77adb90 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f9fc77adfa2 in g_main_loop_run () at /lib64/libglib-2.0.so.0 #5 0x7f9f953b16ba in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0 #6 0x7f9fc77d5f2a in g_thread_proxy () at /lib64/libglib-2.0.so.0 #7 0x7f9fcc4cf594 in start_thread () at /lib64/libpthread.so.0 #8 0x7f9fcec6e0df in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f9f94b1f700 (LWP 2652)): #0 0x7f9fc77f448d in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7f9fc77acf9b in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7f9fc77adb1b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f9fc77add10 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f9fc77add61 in glib_worker_main () at /lib64/libglib-2.0.so.0 #5 0x7f9fc77d5f2a in g_thread_proxy () at /lib64/libglib-2.0.so.0 #6 0x7f9fcc4cf594 in start_thread () at /lib64/libpthread.so.0 #7 0x7f9fcec6e0df in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f9facce2700 (LWP 2637)): #0 0x7f9fcec5f0c4 in read () at /lib64/libc.so.6 #1 0x7f9fc77f3070 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f9fc77ad6db in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f9fc77adb90 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f9fc77add10 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f9fcfb2fc2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f9fcfade12b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f9fcf92c9c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f9fd4172299 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #9 0x7f9fcf93111d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f9fcc4cf594 in start_thread () at /lib64/libpthread.so.0 #11 0x7f9fcec6e0df in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f9fd4097940 (LWP 2634)): [KCrash Handler] #6 0x7f9f8f10154c in QHash, Tp::Connection::Private::HandleContext*>::findNode(QPair const&, unsigned
[krita] [Bug 384529] Color model type selection in Color Hotkeys
https://bugs.kde.org/show_bug.cgi?id=384529 Mohit Kumar Fagna changed: What|Removed |Added CC||mohitkumarfa...@gmail.com --- Comment #3 from Mohit Kumar Fagna --- Hi, In support of this feature: In the current set of shortcuts, if the user hits lighter color shortcut five times and then hits darker color shortcut five times, it lands on a completely different color then the initial color. It would be better if Hue didn't shift along with saturation and lightness. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 396754] New: Add an option in the Latte setting that let the user uses the Super key to activate Application Menu
https://bugs.kde.org/show_bug.cgi?id=396754 Bug ID: 396754 Summary: Add an option in the Latte setting that let the user uses the Super key to activate Application Menu Product: latte-dock Version: git (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tr...@yandex.com Target Milestone: --- Currently the user has to do this manually: https://github.com/psifidotos/Latte-Dock/wiki/F.A.Q.#q-can-i-use-my-super-key-to-open-the-app-launcher I suggest a new option in the Latte setting to help the user archives that more easily with just a click. That option will be disabled by default. -- You are receiving this mail because: You are watching all bug changes.
