[kate] [Bug 412987] Close Icon Missing on Tabs
https://bugs.kde.org/show_bug.cgi?id=412987 François Bissey changed: What|Removed |Added CC||frp.bis...@gmail.com --- Comment #3 from François Bissey --- I have just updated to 19.08.3 (from 19.04.3) in Gentoo and I just had the same surprise. Of course ctrl+w still works and there is a contextual menu (on which "close document" appears with a specific icon) but there is no close button visible. Not visible is not the same as not there. Clicking on the right of the tab does close it. Which suggests it is just invisible somehow. Plasma: 5.16.5 Framework: 5.64.0 Qt: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 411542] Add ability to display nvme drives temperature
https://bugs.kde.org/show_bug.cgi?id=411542 --- Comment #6 from Shmerl --- Just confirming that it works. I just built 5.5-rc1 and can observe nvme temperature in ksysguard! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414957] Unable to Open program
https://bugs.kde.org/show_bug.cgi?id=414957 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 414973] feature request: possibility to let latte just color the elements of the dock...
https://bugs.kde.org/show_bug.cgi?id=414973 --- Comment #3 from PK --- I'm amazed! Thank you so much! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414543] Weighted brush smoothing doesn't work well.
https://bugs.kde.org/show_bug.cgi?id=414543 --- Comment #4 from Manu --- Created attachment 124396 --> https://bugs.kde.org/attachment.cgi?id=124396=edit Image settings sorry for the late reply, here's a screenshot of my new document settings. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414943] digiKam shows image twice and isn't usable
https://bugs.kde.org/show_bug.cgi?id=414943 --- Comment #7 from s...@anders-hamburg.de --- Compiled Version is using: KDE Frameworks 5.54.0 Qt 5.11.3 (kompiliert gegen 5.11.3) Das xcb Fenstersystem App Image Version 6.4.0 (having the crash) is using: KDE Frameworks 5.61.0 Qt 5.13.1 (kompiliert gegen 5.13.1) Das xcb Fenstersystem App Image Version 6.3.0 (without crash) is using: KDE Frameworks 5.59.0 Qt 5.11.3 (kompiliert gegen 5.11.3) Das xcb Fenstersystem -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414974] New: Akonadi crashed while deleting emails
https://bugs.kde.org/show_bug.cgi?id=414974 Bug ID: 414974 Summary: Akonadi crashed while deleting emails Product: Akonadi Version: 5.11.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: bugs.kde.att...@online.de Target Milestone: --- Application: akonadiserver (5.11.3) Qt Version: 5.12.5 Frameworks Version: 5.64.0 Operating System: Linux 5.3.13-300.fc31.x86_64 x86_64 Distribution: "Fedora release 31 (Thirty One)" -- Information about the crash: - What I was doing when the application crashed: I have deleted a couple of emails. Kmail did not delete them and they were still marked as "new". This happens frequently. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8b6bc32800 (LWP 1679))] Thread 32 (Thread 0x7f8afbfff700 (LWP 2203)): #0 0x7f8b6f70e44c in read () from /lib64/libc.so.6 #1 0x7f8b6e36e4cf in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f8b6e3262e7 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f8b6e326742 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f8b6e3268d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f8b6fcb2cd3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f8b6fc5cceb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x55f546d4e5ce in Akonadi::Server::Connection::handleIncomingData() () #8 0x7f8b6fc94656 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #9 0x7f8b6fc88c15 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #10 0x7f8b6fc5dd55 in doNotify(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #11 0x7f8b6fc5dde8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7f8b6fcb1f78 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #13 0x7f8b6fcb282c in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #14 0x7f8b6e3264a0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #15 0x7f8b6e326830 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #16 0x7f8b6e3268d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #17 0x7f8b6fcb2cb5 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #18 0x7f8b6fc5cceb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #19 0x7f8b6fab5395 in QThread::exec() () from /lib64/libQt5Core.so.5 #20 0x7f8b6fab64e6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #21 0x7f8b6ef274e2 in start_thread () from /lib64/libpthread.so.0 #22 0x7f8b6f71d693 in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f8ae57fa700 (LWP 2137)): #0 0x7ffefc78a6cb in ?? () #1 0x7ffefc78a918 in clock_gettime () #2 0x7f8b6f6e46ab in clock_gettime@GLIBC_2.2.5 () from /lib64/libc.so.6 #3 0x7f8b6fcb24c5 in qt_gettime() () from /lib64/libQt5Core.so.5 #4 0x7f8b6fcb100d in QTimerInfoList::updateCurrentTime() () from /lib64/libQt5Core.so.5 #5 0x7f8b6fcb1419 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #6 0x7f8b6fcb2984 in timerSourcePrepareHelper(GTimerSource*, int*) () from /lib64/libQt5Core.so.5 #7 0x7f8b6fcb2a32 in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #8 0x7f8b6e325d1a in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #9 0x7f8b6e3266cb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #10 0x7f8b6e3268d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #11 0x7f8b6fcb2cd3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #12 0x7f8b6fc5cceb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #13 0x55f546d4e5ce in Akonadi::Server::Connection::handleIncomingData() () #14 0x7f8b6fc94656 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #15 0x7f8b6fc88c15 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7f8b6fc5dd55 in doNotify(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7f8b6fc5dde8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f8b6fcb1f78 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #19 0x7f8b6fcb282c in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #20 0x7f8b6e3264a0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x7f8b6e326830 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #22 0x7f8b6e3268d3 in
[lattedock] [Bug 414973] feature request: possibility to let latte just color the elements of the dock...
https://bugs.kde.org/show_bug.cgi?id=414973 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Michail Vourlakos --- https://github.com/psifidotos/plasma-systray-latte-tweaks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #73 from Nick Stefanov --- This get weirder - it randomizes the icons 5-6 times for the past few days but now it randomized them without restart. I was watching a movie and when I closed the movie player I realized the icons are messed up again. I tried to rearrange them (again...) but this doesnt work - when I drop an icon to the location I want it doesn't go there but in the middle of the screen. I recorded a video: https://youtu.be/TCQOBym1KRU This is ridiculous... LTS??? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414969] New: Bluetooth devices found during scan show up as paired devices as well
https://bugs.kde.org/show_bug.cgi?id=414969 Bug ID: 414969 Summary: Bluetooth devices found during scan show up as paired devices as well Product: systemsettings Version: 5.17.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m...@andycc.dev Target Milestone: --- Created attachment 124393 --> https://bugs.kde.org/attachment.cgi?id=124393=edit Screenshot of the behavior SUMMARY STEPS TO REPRODUCE 1. Open Bluetooth / Devices in System Settings. 2. Click the + button to add a device OBSERVED RESULT As devices show up in the scan dialog, they also show up in the devices list. EXPECTED RESULT Devices show up in the scan dialog and the list of paired devices doesn't change. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.3.12-1-default KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414969] Bluetooth devices found during scan show up as paired devices as well
https://bugs.kde.org/show_bug.cgi?id=414969 Andy changed: What|Removed |Added CC||m...@andycc.dev -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414335] Transmission icon in notification area should be monochrome
https://bugs.kde.org/show_bug.cgi?id=414335 --- Comment #3 from Vinzenz Vietzke --- Did so and added VDG as reviewer. Working first time with Phabricator I hopefully did everything right... https://phabricator.kde.org/D25815 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414966] Akonadi crash when performing search with already-present Last Search results
https://bugs.kde.org/show_bug.cgi?id=414966 --- Comment #1 from Marcus Harrison --- Created attachment 124392 --> https://bugs.kde.org/attachment.cgi?id=124392=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 414967] New: Focuss module issues at F2
https://bugs.kde.org/show_bug.cgi?id=414967 Bug ID: 414967 Summary: Focuss module issues at F2 Product: kstars Version: git Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jrlangsto...@gmail.com Target Milestone: --- When using focuss module with a F2 RASA the underlying algorithms are not suited to developing a vcurve at F2. Basically the method used tries to establish a curve and if it's having trouble it sets a very high step of around 600 to even 4000! assuming that the system is slow I guess But at F2 any steps more than say 150 will just produce a large donought that isn't recognised as a star or not even visible. This occurs with gradient, iterative, polynomial etc. It seems to do this as a very shallow curve is produced as focuss changes with only a small amount of steps and larger steps result in no stars being recognised. maybe it expects a steeper curve? A possible solution is to have an input box that specifies the maximum number of steps the software will make in any single focuss movement. This way if I know steps above 150 will produce donoughts I can limit maximum step to say 100. Issue has occurred on all versions incl current git using celestron sct indi driver. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 414968] New: Using provided custom colour package Midnight Commander, renaming files is difficult, as line colours are very pale.
https://bugs.kde.org/show_bug.cgi?id=414968 Bug ID: 414968 Summary: Using provided custom colour package Midnight Commander, renaming files is difficult, as line colours are very pale. Product: krusader Version: 2.6.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: subnorm...@hotmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Import colour scheme - Midnight Commander 2. Pick a file to rename 3. Observe all 3 colours (selected, unselected foreground and background) of the current line are quite pale. 4. None of the colours in this specific instance can be modified - None of the customization options or colour scheme in Midnight Commander appear to change the colour of this. OBSERVED AND EXPECTED RESULT Colours on the rename selected file line appear very pale (white and light grey) when they should be constrasted, legible. The specific colours here are also uncustomizable in the provided Midnight Commander colour theme. It makes renaming files much more difficult than it should be. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Version 2.6.0 "Stiff Challenges" (available in About System) KDE Plasma Version: ? KDE Frameworks Version: KDE Frameworks 5.44.0 Qt Version: Qt 5.9.5 (built against 5.9.5) ADDITIONAL INFORMATION The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 414973] feature request: possibility to let latte just color the elements of the dock...
https://bugs.kde.org/show_bug.cgi?id=414973 --- Comment #1 from PK --- Created attachment 124395 --> https://bugs.kde.org/attachment.cgi?id=124395=edit latte dock in control. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 414973] New: feature request: possibility to let latte just color the elements of the dock...
https://bugs.kde.org/show_bug.cgi?id=414973 Bug ID: 414973 Summary: feature request: possibility to let latte just color the elements of the dock... Product: lattedock Version: 0.9.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: pieterkristen...@gmail.com Target Milestone: --- Created attachment 124394 --> https://bugs.kde.org/attachment.cgi?id=124394=edit plasma drawing elements SUMMARY Latte can let plasma draw the colors of the elements of the (eg) systray. It can also draw the colors negative or intelligent if you wish. What I would like to see is the option to let latte draw these elements and not plasma. Then there would be e.g. no more stragne colored dropox icon in my system tray. STEPS TO REPRODUCE 1. use latte dock 2. use certain plasma theme 3. use dropbox OBSERVED RESULT Dropbox icon shows up black EXPECTED RESULT Dropbox icon shows up white just like the others SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414966] New: Akonadi crash when performing search with already-present Last Search results
https://bugs.kde.org/show_bug.cgi?id=414966 Bug ID: 414966 Summary: Akonadi crash when performing search with already-present Last Search results Product: Akonadi Version: 5.12.3 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Application: akonadiserver (5.12.3) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 4.15.0-72-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I used the search function (under Tools -> Find Messages...) to create a search folder called Last Search. The first search was successful. Consecutive attempts to use the same search function with different parameters failed, searching forever without updating the Last Search folder. Sometimes the Last Search folder would populate with all messages in the searched folders. Finally, quiting Kontact caused both Kontact and Akonadi server to crash. Performing these steps in sequence fairly reliably causes the crash in my experience. The crash can be reproduced every time. -- Backtrace (Reduced): #6 _mm_crc32_u64 (__V=, __C=) at /usr/lib/gcc/x86_64-linux-gnu/7/include/smmintrin.h:848 #7 crc32 (ptr=0xfe0600044fe0, len=, h=) at tools/qhash.cpp:112 #8 0x7f03a144e3c2 in hash (seed=, len=, p=) at tools/qhash.cpp:223 #9 qHash (key=..., seed=) at tools/qhash.cpp:239 #10 0x55ba0511201b in QHash::findNode (this=this@entry=0x55ba0609b328, akey=..., ahp=ahp@entry=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:934 Possible duplicates by query: bug 414229, bug 413844, bug 413385, bug 413205, bug 413201. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414961] Arrow on send button is blurry on HiDPI
https://bugs.kde.org/show_bug.cgi?id=414961 Simon Redman changed: What|Removed |Added Assignee|si...@ergotech.com |albertv...@gmail.com Component|messaging-application |common -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414965] New: Systemsettings complains about missing shared library
https://bugs.kde.org/show_bug.cgi?id=414965
Bug ID: 414965
Summary: Systemsettings complains about missing shared library
Product: systemsettings
Version: 5.17.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: fli...@vongellhorn.ch
Target Milestone: ---
SUMMARY
Systemsettings complains about missing shared library, with different kcm
files. The files are inside the plugins folder and everything works as intended
STEPS TO REPRODUCE
1. Execute systemsettings via terminal
2. click into a setting
3.
OBSERVED RESULT
Terminal Log:
QQmlEngine::setContextForObject(): Object already has a QQmlContext
kf5.kactivity.stat: [Error at ResultSetPrivate::initQuery]: QSqlError("1",
"Unable to execute statement", "no such column: rl.initiatingAgent")
kf5.kactivity.stat: [Error at ResultSetPrivate::initQuery]: QSqlError("1",
"Unable to execute statement", "no such column: rl.initiatingAgent")
org.kde.kcoreaddons: Error loading plugin "kcm_desktoptheme" "The shared
library was not found."
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
QQmlEngine::setContextForObject(): Object already has a QQmlContext
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Solus
(available in About System)
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64
Qt Version: 5.13.2
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 389665] Rotating screen doesn't work on wayland
https://bugs.kde.org/show_bug.cgi?id=389665 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com Assignee|kwin-bugs-n...@kde.org |subd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406491] [wayland] neither primary selection neither copy paste working
https://bugs.kde.org/show_bug.cgi?id=406491 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #6 from Roman Gilg --- This is still not specific enough. Please name example applications and at best ways a way/path of action to trigger the issue reliably. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] Menubar - No text
https://bugs.kde.org/show_bug.cgi?id=395497 Albert Astals Cid changed: What|Removed |Added CC||jgarijoga...@outlook.com --- Comment #27 from Albert Astals Cid --- *** Bug 414936 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414970] New: Windows Decoration crash
https://bugs.kde.org/show_bug.cgi?id=414970 Bug ID: 414970 Summary: Windows Decoration crash Product: systemsettings Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: troy.dwijan...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.4.2-1-MANJARO x86_64 Distribution: Manjaro Linux -- Information about the crash: - What I was doing when the application crashed: Looking around in Window Decorations, probably due to an absurd amount of windows themes. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1dcb170800 (LWP 20438))] Thread 9 (Thread 0x7f1d9700 (LWP 21556)): #0 0x7f1dcd648479 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f1dcd6968ce in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f1dcd6980c8 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f1dcd6981f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f1dcfc6cb2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1dcfc1383c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f1dcfa45305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f1dced4d449 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f1dcfa46530 in () at /usr/lib/libQt5Core.so.5 #9 0x7f1dce2a04cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f1dcf6d22d3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f1dab7fe700 (LWP 21554)): #0 0x7f1dcf6c342c in read () at /usr/lib/libc.so.6 #1 0x7f1dcd6489f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1dcd6969e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f1dcd6980c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1dcd6981f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f1dcfc6cb2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f1dcfc1383c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f1dcfa45305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f1dced4d449 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f1dcfa46530 in () at /usr/lib/libQt5Core.so.5 #10 0x7f1dce2a04cf in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f1dcf6d22d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f1dabfff700 (LWP 21547)): #0 0x7f1dcf6c79ef in poll () at /usr/lib/libc.so.6 #1 0x7f1dcd698120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1dcd6990c3 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #3 0x7f1db4d53bc8 in () at /usr/lib/libgio-2.0.so.0 #4 0x7f1dcd674bb1 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f1dce2a04cf in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1dcf6d22d3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f1db4c2a700 (LWP 21546)): #0 0x7f1dcf6c79ef in poll () at /usr/lib/libc.so.6 #1 0x7f1dcd698120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1dcd6981f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1dcd698242 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1dcd674bb1 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f1dce2a04cf in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1dcf6d22d3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f1db75ef700 (LWP 20447)): #0 0x7f1dcf6c79ef in poll () at /usr/lib/libc.so.6 #1 0x7f1dcd698120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1dcd6981f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1dcfc6cb2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1dcfc1383c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1dcfa45305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1dced4d449 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f1dcfa46530 in () at /usr/lib/libQt5Core.so.5 #8 0x7f1dce2a04cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f1dcf6d22d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f1dc1b84700 (LWP 20445)): #0 0x7f1dcf6c342c in read () at /usr/lib/libc.so.6 #1 0x7f1dcd6489f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1dcd6969e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f1dcd6980c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1dcd6981f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f1dcfc6cb2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6
[KSystemLog] [Bug 414971] New: ksystemlog cannot start from the menu
https://bugs.kde.org/show_bug.cgi?id=414971 Bug ID: 414971 Summary: ksystemlog cannot start from the menu Product: KSystemLog Version: 19.08.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: nicolas.ternis...@gmail.com Reporter: davidshe...@gmail.com Target Milestone: --- ksystemlog cannot start from the menu and there's no error message. However, if I execute the ksystemlog from the console, the application can start normally with the following message logged in the console. ksystemlog: Log manager is not yet initialized STEPS TO REPRODUCE 1. Install ksystemlog version 19.08.3 on Plasma 5 DE 2. Open the start menu and search for ksystemlog 3. Click on the icon to start the application 3. OBSERVED RESULT Nothing happens EXPECTED RESULT The ksystemlog application should start. SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: Gentoo 64 bit Plasma 5 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.64.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION Full console log when starting ksystemlog from a console. Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 92: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 106: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 125: Having multiple values in isn't supported and may not work as expected ksystemlog: Log manager is not yet initialized -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414936] Menu bar buttons show "No text" instead of appropriate names
https://bugs.kde.org/show_bug.cgi?id=414936 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|RESOLVED CC||aa...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Albert Astals Cid --- *** This bug has been marked as a duplicate of bug 395497 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 413973] Editing partitions resets touchpad configuration
https://bugs.kde.org/show_bug.cgi?id=413973 Jan Przybylak changed: What|Removed |Added CC||jplx...@gmail.com --- Comment #27 from Jan Przybylak --- *** Bug 412373 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412373] Formatting drives messes with my trackpad
https://bugs.kde.org/show_bug.cgi?id=412373 Jan Przybylak changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Jan Przybylak --- *** This bug has been marked as a duplicate of bug 413973 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412490] Breeze icon for SimpleScreenRecorder
https://bugs.kde.org/show_bug.cgi?id=412490 Vinzenz Vietzke changed: What|Removed |Added CC||v...@vinzv.de --- Comment #1 from Vinzenz Vietzke --- I made an initial breeze version: https://phabricator.kde.org/D25820 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 414972] New: KDE Marble crash after Power Management switched screen off
https://bugs.kde.org/show_bug.cgi?id=414972 Bug ID: 414972 Summary: KDE Marble crash after Power Management switched screen off Product: marble Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: p...@420blaze.it Target Milestone: --- Application: marble (2.2.20 (2.3 development version)) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-24-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: After getting a critical battery warning and replugging in AC power, I later (15+ minutes) returned to the computer, logged back in, and found Marble had crashed -- Backtrace: Application: Marble Virtual Globe (marble), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fca77d34f00 (LWP 31421))] Thread 18 (Thread 0x7fc9e3fff700 (LWP 2564)): #0 0x7fca891676e0 in futex_abstimed_wait_cancelable (private=, abstime=0x7fc9e3ffe470, clockid=, expected=0, futex_word=0x7fc9e3ffe5b8) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 0x7fca891676e0 in __pthread_cond_wait_common (abstime=0x7fc9e3ffe470, clockid=, mutex=0x7fc9e3ffe568, cond=0x7fc9e3ffe590) at pthread_cond_wait.c:520 #2 0x7fca891676e0 in __pthread_cond_timedwait (cond=0x7fc9e3ffe590, mutex=0x7fc9e3ffe568, abstime=0x7fc9e3ffe470) at pthread_cond_wait.c:656 #3 0x7fca8406a10b in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fca8406aab2 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fca8406aba6 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fca8402c705 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fca8402ef96 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fca8402f258 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fca8406cc75 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fca89160669 in start_thread (arg=) at pthread_create.c:479 #11 0x7fca89c4c323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fc9bbfff700 (LWP 31530)): #0 0x7fca89c3b2ac in __GI___libc_read (nbytes=16, buf=0x7fc9bbffe490, fd=94) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7fca89c3b2ac in __GI___libc_read (fd=94, buf=0x7fc9bbffe490, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fca887a863f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fca8876058e in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fca887609e2 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fca88760b73 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fca8a2026c3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fca8a1a963b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fca89fe2a75 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fca89fe3cc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fca89160669 in start_thread (arg=) at pthread_create.c:479 #11 0x7fca89c4c323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fca3a7fc700 (LWP 31451)): #0 0x7fca891672c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fca3a7fb5c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fca891672c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7fca3a7fb578, cond=0x7fca3a7fb5a0) at pthread_cond_wait.c:508 #2 0x7fca891672c6 in __pthread_cond_wait (cond=0x7fca3a7fb5a0, mutex=0x7fca3a7fb578) at pthread_cond_wait.c:638 #3 0x7fca8406a03d in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fca8406aac0 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fca8406ab63 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fca8402c718 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fca8402ef96 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fca8402f318 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fca8406cc75 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fca89160669 in start_thread (arg=) at pthread_create.c:479 #11 0x7fca89c4c323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7fca3affd700 (LWP 31450)): #0 0x7fca89bc18eb in __lll_lock_wait_private (futex=0x7fca89d174b0 <_IO_stdfile_2_lock>) at ./lowlevellock.c:35 #1 0x7fca89ba7146 in buffered_vfprintf (s=s@entry=0x7fca89d155c0 <_IO_2_1_stderr_>,
[korganizer] [Bug 410167] Cannot change or enter time for calendar entry
https://bugs.kde.org/show_bug.cgi?id=410167 --- Comment #9 from B Rhodes --- I think the problem has to do with time zones. I went into my System Settings -> Regional Settings -> Date & Time, changed the time zone and then changed it back. The problem seems to be better now. I think somewhere along the pike KOrg couldn't read the time zone values properly, so it would mess up calculating event times and then default to 00:00 - 23:59. See if this works for you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #74 from Nick Stefanov --- Sorry, the video is here: https://youtu.be/P0wg1e5ZIn8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414335] Transmission icon in notification area should be monochrome
https://bugs.kde.org/show_bug.cgi?id=414335 --- Comment #4 from Nate Graham --- Thanks, you did great! We'll get that reviewed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414942] New: Plasma segfault on installing widget
https://bugs.kde.org/show_bug.cgi?id=414942 Bug ID: 414942 Summary: Plasma segfault on installing widget Product: plasmashell Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jnoricha...@blueyonder.co.uk CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: Dragged 'Network Monitor' widget from widget install menu to desktop. Plasma segfaulted; applications running (Dolphin, Kate) were unaffected. Widget was not installed. - Unusual behavior I noticed: Subsequent attempt to install Network Monitor widget was successful -- 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 0x7f481ab3b800 (LWP 1678))] Thread 11 (Thread 0x7f47a7fff700 (LWP 2698)): #0 0x7f48118929f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e5979b27e0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e5979b2790, cond=0x55e5979b27b8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e5979b27b8, mutex=0x55e5979b2790) at pthread_cond_wait.c:655 #3 0x7f4814961aeb in QWaitConditionPrivate::wait (deadline=..., this=0x55e5979b2790) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55e598055600, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f4814961df9 in QWaitCondition::wait (this=this@entry=0x55e598055608, mutex=mutex@entry=0x55e598055600, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7f4818985ec8 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x55e5980555f8) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x55e598055580) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7f48189862fa in QSGRenderThread::run (this=0x55e598055580) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7f481495ab52 in QThreadPrivate::start (arg=0x55e598055580) at thread/qthread_unix.cpp:360 #10 0x7f481188c6db in start_thread (arg=0x7f47a7fff700) at pthread_create.c:463 #11 0x7f481425788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f47c22e5700 (LWP 1960)): #0 0x7f48118929f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e59780b934) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e59780b8e0, cond=0x55e59780b908) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e59780b908, mutex=0x55e59780b8e0) at pthread_cond_wait.c:655 #3 0x7f4814961aeb in QWaitConditionPrivate::wait (deadline=..., this=0x55e59780b8e0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x7f48c080, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f4814961df9 in QWaitCondition::wait (this=this@entry=0x7f48c088, mutex=mutex@entry=0x7f48c080, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7f4818985ec8 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x7f48c078) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x7f48c000) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7f48189862fa in QSGRenderThread::run (this=0x7f48c000) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7f481495ab52 in QThreadPrivate::start (arg=0x7f48c000) at thread/qthread_unix.cpp:360 #10 0x7f481188c6db in start_thread (arg=0x7f47c22e5700) at pthread_create.c:463 #11 0x7f481425788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f47c11e3700 (LWP 1959)): #0 0x7f48118929f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e597ace7d4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e597ace780, cond=0x55e597ace7a8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e597ace7a8, mutex=0x55e597ace780) at pthread_cond_wait.c:655 #3 0x7f4814961aeb in QWaitConditionPrivate::wait (deadline=..., this=0x55e597ace780) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55e5982178d0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f4814961df9 in QWaitCondition::wait (this=this@entry=0x55e5982178d8, mutex=mutex@entry=0x55e5982178d0,
[krita] [Bug 414507] Hope to trigger Undo with tablet button
https://bugs.kde.org/show_bug.cgi?id=414507 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #4 from Boudewijn Rempt --- You need to configure this on the tablet driver settings level. How that is done, depends on the OS and the tablet brand and model. Configure the pen button to send ctrl-z in the tablet configuration utility that comes with your OS. Vanilla Ubuntu uses Gnome these days, which comes with a suitable utility. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414942] Plasma segfault on installing widget
https://bugs.kde.org/show_bug.cgi?id=414942 Jonathan Richards changed: What|Removed |Added Platform|unspecified |Neon Packages --- Comment #1 from Jonathan Richards --- This is a very recent reinstall of KDE Neon. In order to make Plasma work at all I had to back up .config and create a new empty one, so I don't think the cause can be a configuration hangover from previous versions. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 414944] New: vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7D 0x48 0xEF 0xC0 0x48 0x8D 0x7D 0xD0
https://bugs.kde.org/show_bug.cgi?id=414944 Bug ID: 414944 Summary: vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7D 0x48 0xEF 0xC0 0x48 0x8D 0x7D 0xD0 Product: valgrind Version: 3.14.0 Platform: Debian stable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: caiyueq...@bytedance.com Target Milestone: --- SUMMARY On Debian 9, run valgrind checking rocksdb, meet that, unhandled instruction bytes: 0x62 0xF1 0x7D 0x48 0xEF 0xC0 0x48 which will not happen on Debian 8 STEPS TO REPRODUCE run valgrind checking rocksdb OBSERVED RESULT vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7D 0x48 0xEF 0xC0 0x48 0x8D 0x7D 0xD0 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==789529== valgrind: Unrecognised instruction at address 0x4d2fa7. ==789529==at 0x4D2FA7: rocksdb::BlockBasedTableFactory::BlockBasedTableFactory(rocksdb::BlockBasedTableOptions const&) (/root/repos/bytedrive/third/byte/thirdparty/rocksdb/table/block_based_table_factory.cc:44) ==789529==by 0x4B1392: rocksdb::ColumnFamilyOptions::ColumnFamilyOptions() (/root/repos/bytedrive/third/byte/thirdparty/rocksdb/options/options.cc:100) ==789529==by 0x2956B2: __static_initialization_and_destruction_0(int, int) [clone .constprop.830] (/root/repos/bytedrive/third/byte/thirdparty/rocksdb/options/options_helper.cc:1598) ==789529==by 0x5F06AC: __libc_csu_init (in /root/repos/bytedrive/build/bytedrive/blockmaster/rocksdb_store_test) ==789529==by 0x7B1926F: (below main) (24/csu/../csu/libc-start.c:247) EXPECTED RESULT should no unhandled instruction bytes SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux n18-065-078 4.19.28.bsk.4-amd64 #4.19.28.bsk.4 SMP Debian 4.19.28.bsk.4 Wed Apr 24 12:15:15 UTC x86_64 GNU/Linux (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 r...@bnnr.mn changed: What|Removed |Added CC||r...@bnnr.mn -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414945] New: Smiley icon is blurry and truncated with HiDPI
https://bugs.kde.org/show_bug.cgi?id=414945 Bug ID: 414945 Summary: Smiley icon is blurry and truncated with HiDPI Product: systemsettings Version: 5.17.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_activities Assignee: ivan.cu...@kde.org Reporter: pos...@posteo.eu CC: plasma-b...@kde.org Target Milestone: --- Created attachment 124375 --> https://bugs.kde.org/attachment.cgi?id=124375=edit Screenshot of the issue. SUMMARY The default yellow smiley for the default activity has a low resolution in the activities list and is truncated at the top and bottom. In the settings dialog for this very activity, the smiley appears sharp and complete. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION Scaling: 1.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414945] Smiley icon is blurry and truncated with HiDPI
https://bugs.kde.org/show_bug.cgi?id=414945 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414943] Digikam shows image twice and isnt uasble
https://bugs.kde.org/show_bug.cgi?id=414943 --- Comment #1 from s...@anders-hamburg.de --- Created attachment 124374 --> https://bugs.kde.org/attachment.cgi?id=124374=edit Screenshot of "Leuchttisch" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414943] New: Digikam shows image twice and isnt uasble
https://bugs.kde.org/show_bug.cgi?id=414943 Bug ID: 414943 Summary: Digikam shows image twice and isnt uasble Product: digikam Version: 6.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor Assignee: digikam-bugs-n...@kde.org Reporter: s...@anders-hamburg.de Target Milestone: --- Created attachment 124373 --> https://bugs.kde.org/attachment.cgi?id=124373=edit Screen of Bildbearbeiten SUMMARY STEPS TO REPRODUCE 1. Open digikam6.4.0 AppImage on Debian Stretch 64 Bit with NVIDIA Graphics 2. Open "Bildbearbeiten" (German) English ImageEditor OBSERVED RESULT The Picture is showen twice and the gui isn't usable The same behavior is when i open the "Leuchttisch" english: Light Table EXPECTED RESULT Like in digikam 6.3.0 the gui should open only once SOFTWARE/OS VERSIONS Debian: Buster Linux: 4.19.0-6-amd64 (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414943] Digikam shows image twice and isnt uasble
https://bugs.kde.org/show_bug.cgi?id=414943 s...@anders-hamburg.de changed: What|Removed |Added Platform|Other |Debian stable -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #159 from Peter Hatina --- (In reply to Andrew from comment #152) > Solution for my case: > 1. 2560 / 1.3 = 1969,23076923 > 2. Round to 1970 > 3. 2560 / 1970 = 1,29949238579 > 4. Open ~/.config/kdeglobals and set it manually: > > [KScreen] > ScaleFactor=1,29949238579 > ScreenScaleFactors=eDP-1=1.0;HDMI-1=1,29949238579;DP-1=1,29949238579;HDMI- > 2=1,29949238579; > > It solves the issue. I have resolution of 1920x1080 on XPS13. Scale factor I set in Plasma is 1.2 which gives integral values. I still can see horizontal lines. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354688] Can't remove file File Association in System Settings
https://bugs.kde.org/show_bug.cgi?id=354688 Walther Pelser changed: What|Removed |Added CC||w.pel...@web.de --- Comment #8 from Walther Pelser --- In the last weeks I have the same problem. Syremsetting5 cannot change the file endings at the end of the prozess. It changes the file in ~/.local/mime/application/vnd.lotus-1-2-3.xml for instance, but this takes no effect. Expected behaviour was: the local file should override the settings in /usr/share/mime/application/vnd.lotus-1-2-3 in this example, but this does not happen. It seems, that that the changed userdefined mime types are not read again by systemsettings5 to make them work. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 413756] Ad calculation and compensation of CO2-emissions
https://bugs.kde.org/show_bug.cgi?id=413756 --- Comment #3 from Volker Krause --- Statistics page with CO2 impact estimation and year-by-year trends has been added now. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414943] Digikam shows image twice and isnt uasble
https://bugs.kde.org/show_bug.cgi?id=414943 --- Comment #2 from s...@anders-hamburg.de --- Update: I have compiled digikam from sources wich wasrealy painful. When I start this version of digikam, everything looks good. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414946] New: The "monitor image" to set actions at the screen borders needs a HiDPI version
https://bugs.kde.org/show_bug.cgi?id=414946 Bug ID: 414946 Summary: The "monitor image" to set actions at the screen borders needs a HiDPI version Product: systemsettings Version: 5.17.4 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 124376 --> https://bugs.kde.org/attachment.cgi?id=124376=edit Screenshot of the issue. SUMMARY You can see a lot of rough edges in the screenshot. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION Scaling: 1.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414946] The "monitor image" to set actions at the screen borders needs a HiDPI version
https://bugs.kde.org/show_bug.cgi?id=414946 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414947] New: The cursor theme previews need a HiDPI version
https://bugs.kde.org/show_bug.cgi?id=414947 Bug ID: 414947 Summary: The cursor theme previews need a HiDPI version Product: systemsettings Version: 5.17.4 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 124377 --> https://bugs.kde.org/attachment.cgi?id=124377=edit Screenshot of the issue. There are all blurry on HiDPI. Please the see screenshot. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414947] The cursor theme previews need a HiDPI version
https://bugs.kde.org/show_bug.cgi?id=414947 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414951] Avatar is blurry at the audio test kcm
https://bugs.kde.org/show_bug.cgi?id=414951 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414951] New: Avatar is blurry at the audio test kcm
https://bugs.kde.org/show_bug.cgi?id=414951 Bug ID: 414951 Summary: Avatar is blurry at the audio test kcm Product: systemsettings Version: 5.17.4 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_audiocd Assignee: plasma-b...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 124381 --> https://bugs.kde.org/attachment.cgi?id=124381=edit Screenshot of the issue. Hardware -> Audio -> Advanced: There's the user avatar placed in conjunction with the speakers position. This avatar is blurry on a HiDPI screen. Please see the screenshot. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414950] Krita closes when trying to open a project
https://bugs.kde.org/show_bug.cgi?id=414950 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Could you also attach the file? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 414053] vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFE 0x8 0x6F 0x45 0x0 0xC5 0xF8 0x11
https://bugs.kde.org/show_bug.cgi?id=414053 caiyueq...@bytedance.com changed: What|Removed |Added CC||caiyueq...@bytedance.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413463] Wallpaper slideshow set to "random" is not random at all
https://bugs.kde.org/show_bug.cgi?id=413463 Marcin Gurtowski changed: What|Removed |Added CC||halftough...@gmail.com --- Comment #7 from Marcin Gurtowski --- (In reply to Nate Graham from comment #6) > Git commit 9dca7d6cd44cbb16c6d7fb1aca5588760544b1d6 by Nate Graham, on > behalf of David Edmundson. > Committed on 29/10/2019 at 19:39. > Pushed by ngraham into branch 'Plasma/5.17'. > > [wallpapers/image] Randomise new batches of images in the slideshow > > Summary: > There was a concious decision that when we add a new wallpaper we should > append to the existing random order collection, rather than shuffle > existing ones. > > The logic is fine but if we start with 0 wallpapers and then add 20 new > ones we don't shuffle anything. > > This patch changes it so when a new batch of N wallpapers is added, > those N are shuffled when appending to the existing sort order. > FIXED-IN: 5.17.2 > > Test Plan: qDebug + ran a few times > > Reviewers: #plasma, ngraham, davidre > > Reviewed By: ngraham, davidre > > Subscribers: davidre, plasma-devel > > Tags: #plasma > > Differential Revision: https://phabricator.kde.org/D24986 > > M +1-0wallpapers/image/slidefiltermodel.cpp > > https://commits.kde.org/plasma-workspace/ > 9dca7d6cd44cbb16c6d7fb1aca5588760544b1d6 Has this been released yet? Because now on 5.17.4 after changing my wallpaper directories I can definitively see patterns. Namely wallpapers from new directory I added are all showed one after another, but old ones also continue to appear in same order as they are structured in a directory. What's more after booting up the first wallpaper is actually random, but after that the next one will be second from the list, third one and so on. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link
https://bugs.kde.org/show_bug.cgi?id=414742 --- Comment #12 from Walther Pelser --- In that case (second Bug of comment 11) I added a comment to bug # 354688 and tried to describe it as transparent as possible. Maybe at will work. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414948] New: The emojis look blurry on HiDPI
https://bugs.kde.org/show_bug.cgi?id=414948 Bug ID: 414948 Summary: The emojis look blurry on HiDPI Product: systemsettings Version: 5.17.4 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_emoticons Assignee: brandon...@gmail.com Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 124378 --> https://bugs.kde.org/attachment.cgi?id=124378=edit Screenshot of the issue. Please see the screenshot. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414948] The emojis look blurry on HiDPI
https://bugs.kde.org/show_bug.cgi?id=414948 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414948] The emojis look blurry on HiDPI
https://bugs.kde.org/show_bug.cgi?id=414948 --- Comment #1 from Postix --- However, only the ones from Breeze. EmojiOne's and Konqi's are fine. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414949] Global Design "missing preview" and Plasma Style previews look blurry on a HiDPI Screen
https://bugs.kde.org/show_bug.cgi?id=414949 --- Comment #1 from Postix --- Created attachment 124380 --> https://bugs.kde.org/attachment.cgi?id=124380=edit Screenshot of the Plasma Styles -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414949] New: Global Design "missing preview" and Plasma Style previews look blurry on a HiDPI Screen
https://bugs.kde.org/show_bug.cgi?id=414949 Bug ID: 414949 Summary: Global Design "missing preview" and Plasma Style previews look blurry on a HiDPI Screen Product: systemsettings Version: 5.17.4 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_lookandfeel Assignee: plasma-b...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 124379 --> https://bugs.kde.org/attachment.cgi?id=124379=edit Screenshot of the Global Design's "missing preview" Please see the screenshots. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414949] Global Design "missing preview" and Plasma Style previews look blurry on a HiDPI Screen
https://bugs.kde.org/show_bug.cgi?id=414949 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414950] New: Krita closes when trying to open a project
https://bugs.kde.org/show_bug.cgi?id=414950 Bug ID: 414950 Summary: Krita closes when trying to open a project Product: krita Version: 4.2.8 Platform: Debian testing OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: j...@lnxd.es Target Milestone: --- Hello, When I work with a Krita project, there comes a time when the file doesn't open and the program closes. Trying to open that file in different versions, I could open it with the appimage version 4.2.7 Versions of Krita that close when I open the file: * krita 4.2.8 instalado en debian testing bullseye * https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/krita-4.3.0-prealpha-818c841-x86_64.appimage * https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/lastSuccessfulBuild/artifact/krita-4.2.9-alpha-51fcc8c-x86_64.appimage * https://download.kde.org/stable/krita/4.2.8/krita-4.2.8-x86_64.appimage Version of Krita that opens the file: * https://download.kde.org/stable/krita/4.2.7.1/krita-4.2.7.1b-x86_64.appimage Logs of Krita 4.2.8 installed on Debian bullseye (testing): Launched from the shell $krita ./my-file.kra Set style "fusion" Invalid profile : "/usr/share/color/icc/colord/Crayons.icc" "Crayon Colors" Invalid profile : "/usr/share/color/icc/colord/x11-colors.icc" "X11 Colors" krita.general: Failed to load "paintoppresets/Special_dyna_dots.kpp" from bundle "/usr/share/krita/bundles/Krita_3_Default_Resources.bundle" QObject::startTimer: Timers cannot have negative intervals /usr/lib/x86_64-linux-gnu/krita-python-libs/krita added to PYTHONPATH Violación de segmento (krita close) Krita LOG SESSION: 08 Dec 2019 00:21:07 +0100. Executing krita ./my-file.kra ADVERTENCIA: Este archivo contiene información sobre su sistema y sobre las imágenes con las que ha estado trabajando. Si tiene algún problema con Krita, los desarrolladores de Krita le podrían pedir que comparta este archivo con ellos. La información de este archivo no se comparte automáticamente con los desarrolladores de Krita de ninguna manera. Puede desactivar el registro en este archivo en el diálogo de configuración de Krita. Por favor, revise el contenido de este archivo antes de compartirlo con alguien. Krita Version: 4.2.8 Languages: es Hidpi: true Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.3.0-2-amd64 Pretty Productname: Debian GNU/Linux bullseye/sid Product Type: debian Product Version: unknown OpenGL Info Vendor: "nouveau" Renderer: "NVC1" Version: "4.3 (Compatibility Profile) Mesa 19.2.6" Shading language: "4.30" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.3, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.3 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 7947 Mb Number of Cores: 8 Swap Location: /tmp Current Settings Current Swap Location: /tmp Undo Enabled: 1 Undo Stack Limit: 30 Use OpenGL: 1 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 0 Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 0 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 0 Use Zip64: 0 08 Dec 2019 00:21:15 +0100: Importing application/x-krita to application/x-krita. Location: /home/user/path/./my-file.kra. Real location: /home/user/path/./my-file.kra. Batchmode: 0 KRITA DID NOT CLOSE CORRECTLY (translated texts, sorry) Greetings, Xabi. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414943] Digikam shows image twice and isnt uasble
https://bugs.kde.org/show_bug.cgi?id=414943 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- So it's a packaging problem Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 414729] Dead links for KDiskFree and KDE Partition Manager in Dolphin
https://bugs.kde.org/show_bug.cgi?id=414729 Elvis Angelaccio changed: What|Removed |Added Component|general |general Product|dolphin |frameworks-knewstuff Version|18.04.1 |5.64.0 Assignee|dolphin-bugs-n...@kde.org |jpwhit...@kde.org CC||elvis.angelac...@kde.org, ||kdelibs-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411682] Copy-paste doesn't work in firefox
https://bugs.kde.org/show_bug.cgi?id=411682 --- Comment #5 from Rainer Finke --- I did set in "/etc/environment" the "export MOZ_ENABLE_WAYLAND=1" environment variable. With this I see in Firefox-nightly (webrender is enabled too) in about:support that the Window Protocol is set to Wayland. Copy and paste from any application to Firefox doesn't work, not even from Firefox to Firefox, only from Firefox to another application. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414952] New: unable to draw in one file
https://bugs.kde.org/show_bug.cgi?id=414952 Bug ID: 414952 Summary: unable to draw in one file Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: til.schmit...@gmx.de Target Milestone: --- SUMMARY before i say anything else, i managed to fix this by saving the file as a .tif . i was drawing on krita-nightly-x64-v4.3.0-prealpha-809-g2c21a4c21e and all of a sudden i wasn't able to draw anymore. can't use brushes or any other tools, can't erase, can't use filters etc. i can however hide layers, delete them or create new ones, adding a fill layer for example doesn't show on the canvas though. this somehow only affects this single file, so idk if it's a setting i accidentally changed? does such a setting exist? my blend mode is normal and the opacity 100% btw. ABOUT MY SYSTEM Win 10 8GB DDR4 i7-6700 cintiq 13 pro -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414952] unable to draw in one file
https://bugs.kde.org/show_bug.cgi?id=414952 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||b...@valdyas.org --- Comment #2 from Boudewijn Rempt --- You probably had a very small selection active in the kra file. It's hard to say from the screenshot, since it doesn't include the statusbar which contains the warning icon about active selections. Please check with the original kra file. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414952] unable to draw in one file
https://bugs.kde.org/show_bug.cgi?id=414952 --- Comment #1 from til.schmit...@gmx.de --- Created attachment 124382 --> https://bugs.kde.org/attachment.cgi?id=124382=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414957] New: Unable to Open program
https://bugs.kde.org/show_bug.cgi?id=414957 Bug ID: 414957 Summary: Unable to Open program Product: krita Version: 4.2.8 Platform: Windows CE OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: riceri...@gmail.com Target Milestone: --- SUMMARY Updated from 4.2.7.1 to 4.2.8 unable to open. User Receives "not responding" and application never loads Update occurred after Widows update around 8pm est on 12/7/2019 STEPS TO REPRODUCE 1. Reverted to 4.1.7 works. Updated to 4.2.6 user receives "not responding" 2. Reinstalled all drivers of GPU application still receives "not responding" 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Chat that user had with Dev's regarding issue. +Asuna Greetings, I need to report an issue, I have recently updated krita in 2 ways in attempt to get this to work. I have it through the MS store and the exe file. After a small windows update last night. I attempted to open the application and it goes into "not responding". Can you help? tiar-ty Asuna: are you just opening the program with a file or without the file +Asuna just the program file tiar-ty Asuna: try to reset your configuration using this instruction: https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration +Asuna already cleared tiar-ty Asuna: can you please download portable (.zip) version of Krita 4.1.7 and check that one? +Asuna Sure thing, one moment +Asuna tiar-sp Asuna: can you check 4.2.0 as well? +Asuna @tiar-sp i don't see 4.2.0 only 4.2.6 * tiar-sp needs to go for a bit, will be back in 15-20 min +Asuna The 4.2.6 version give the not responding when opened Lynx3d Asuna, all older versions can be found here: https://download.kde.org/Attic/krita/ +Asuna we confirmed that v4.1.7 works for me however anything after 4.2 doesn't for some reason i keep getting a not responding when opening. this just started last night and i was running a 4.2 version before this happened +hyperion101010 @tiar-sp tiar-sp Asuna: what GPU do you have? +Asuna GTX1070 Ti +hyperion101010 that is something powerful you have i will say that @Asuna +Asuna thanks @hyperion101010 +Asuna tiar-sp Asuna: hmm, and what version of the graphics card driver do you have? +Asuna @tiar-sp current driver is 441.41 tiar-sp Asuna: do you know what DebugView is? It would be really helpful if you could check opening Krita with it tiar-sp Asuna: you can try reinstalling the driver, even if it's the latest version - I needed to do that recently after Windows Update as well tiar-sp it might help +Asuna @tiar-sp i have never used the debugview before, and i have already gone through all updates this morning before reaching out. tiar-sp Asuna: ok. I would like you to make a bug report on bugs.kde.org to resolve this Asuna: and DebugView output would be really useful Asuna: you can download it, it doesn't need installing, just unzipping and clicking on the file +Asuna @tiar-sp will do and will look into the debug view, thank you for the help. tiar-sp Asuna: thanks for coming here :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414848] Problem with additing Slide-Show Clip to project in MS Win
https://bugs.kde.org/show_bug.cgi?id=414848 emohr changed: What|Removed |Added Flags||timeline_corruption+ Status|REPORTED|NEEDSINFO CC||fritzib...@gmx.net Resolution|--- |WAITINGFORINFO --- Comment #1 from emohr --- Version 18.12.1 is not supported anymore. Issue with importing slide show is solved with the current verison 19.08. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 414587] Set F4 shortcut to open the terminal in Kate like in Dolphin
https://bugs.kde.org/show_bug.cgi?id=414587 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kat |kate/commit/4fec9bf8a8283bf |e/4fec9bf8a8283bfd00d15707a |d00d15707aa1615f438f9ab05 |a1615f438f9ab05 --- Comment #13 from Nate Graham --- Git commit 4fec9bf8a8283bfd00d15707aa1615f438f9ab05 by Nate Graham. Committed on 08/12/2019 at 16:50. Pushed by scmsync into branch 'master'. Open/close and focus/defocus terminal using the same shortcuts as Dolphin Summary: Users have complained that Kate's terminal doesn't use the same shortcut as Dolphin to open and close. This patch makes it do so, using the same shortcuts that dolphin uses to both open/close and also focus/de-focus: F4: Open/close Ctrl+Shift+F4: Focus/de-focus (also open if currently closed) FIXED-IN: 20.04.0 Closes T12318 Test Plan: Hit F4 twice -> terminal opens and closes Hit Ctrl+Shift+F4 twice -> terminal focuses and de-focuses Reviewers: #kate, cullmann Reviewed By: #kate, cullmann Subscribers: cullmann, kwrite-devel Tags: #kate Maniphest Tasks: T12318 Differential Revision: https://phabricator.kde.org/D25805 M +20 -2addons/konsole/kateconsole.cpp M +5-0addons/konsole/kateconsole.h M +3-2addons/konsole/ui.rc https://commits.kde.org/kate/4fec9bf8a8283bfd00d15707aa1615f438f9ab05 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 414587] Set F4 shortcut to open the terminal in Kate like in Dolphin
https://bugs.kde.org/show_bug.cgi?id=414587 Nate Graham changed: What|Removed |Added Latest Commit|https://cgit.kde.org/konsol |https://invent.kde.org/kde/ |e.git/commit/?id=bbdf27cc9f |kate/commit/4fec9bf8a8283bf |ee4cf40e7f2551769445b2146ec |d00d15707aa1615f438f9ab05 |20c | Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Version Fixed In|19.12 |20.04.0 --- Comment #12 from Nate Graham --- Git commit 4fec9bf8a8283bfd00d15707aa1615f438f9ab05 by Nate Graham. Committed on 08/12/2019 at 16:50. Pushed by ngraham into branch 'master'. Open/close and focus/defocus terminal using the same shortcuts as Dolphin Summary: Users have complained that Kate's terminal doesn't use the same shortcut as Dolphin to open and close. This patch makes it do so, using the same shortcuts that dolphin uses to both open/close and also focus/de-focus: F4: Open/close Ctrl+Shift+F4: Focus/de-focus (also open if currently closed) FIXED-IN: 20.04.0 Closes T12318 Test Plan: Hit F4 twice -> terminal opens and closes Hit Ctrl+Shift+F4 twice -> terminal focuses and de-focuses Reviewers: #kate, cullmann Reviewed By: #kate, cullmann Subscribers: cullmann, kwrite-devel Tags: #kate Maniphest Tasks: T12318 Differential Revision: https://phabricator.kde.org/D25805 M +20 -2addons/konsole/kateconsole.cpp M +5-0addons/konsole/kateconsole.h M +3-2addons/konsole/ui.rc https://invent.kde.org/kde/kate/commit/4fec9bf8a8283bfd00d15707aa1615f438f9ab05 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414903] Optimize/free unused canvas space in all layers
https://bugs.kde.org/show_bug.cgi?id=414903 --- Comment #7 from Tymond --- > > @boud if you're talking about autocropping the actual content of layers on > > saving, I'm really really strongly against it > > Would you mind elaborating on why? > The main reason I opened this bug rather than directly attempt a patch is > because I suspected this might be an issue, though I have no precise idea on > why (concurrency issue when saving in the background maybe?). > > No, auto-cropping on save is exactly what I had in mind. > (I'm not sure I understand what you're proposing though ;)) I'm strongly against cropping the content behind user's back. First of all, that kind of defeats the whole purpose of being able to paint outside of the canvas if every time you save - including autosave, I presume? - it crops out the content from outside the canvas. Gimp users asked for this feature for years, are we supposed to just light-handedly get rid of it? For example, one of the advantage of having content outside of the canvas is transforming the layer later without an artificial edge where the canvas boundary was. It's very useful both at the beginning of painting process when you can sketch and modify the sketch a lot to figure out composition, and later too, when you see that the composition needs some improvement or that because of some changes you need to bring back something that was outside of the canvas but now it's needed inside again. Another thing is our future animated Transform Mask. To get a nice zooming-in or out animation, it's better to paint a very big, much bigger than the canvas, background, and then zoom in using the Transform Mask. Cutting the content outside of the canvas won't allow for such trick. In both cases, just the fact that you can paint outside of the canvas doesn't mean a lot when saving the file destroys the data. What I would be supposed to do, avoid saving to make sure I don't lose it? That doesn't sound like a good idea at all. Removing empty tiles is of course very much fine with me, since they wouldn't contain any data that I may want/need later. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414850] I can only drug files to Project's Tree. It isn't work selections from folders.
https://bugs.kde.org/show_bug.cgi?id=414850 emohr changed: What|Removed |Added Flags||timeline_corruption+ Status|REPORTED|NEEDSINFO CC||fritzib...@gmx.net Resolution|--- |WAITINGFORINFO --- Comment #1 from emohr --- Version 18.12.1 is not supported anymore. Issue to see other drives is solved with the current verison 19.08. With this version you can import the complete content of a directory/folder with "add clip or folder". -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 414933] Icons randomly rearrange themselves when minimizing/restoring
https://bugs.kde.org/show_bug.cgi?id=414933 --- Comment #2 from heroofg...@gmail.com --- Created attachment 124383 --> https://bugs.kde.org/attachment.cgi?id=124383=edit Layout -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414957] Unable to Open program
https://bugs.kde.org/show_bug.cgi?id=414957 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Platform|Windows CE |MS Windows Status|REPORTED|NEEDSINFO CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Can you please attach the output of help->system information for bug reports to this bug, and preferably also a debugview (https://docs.microsoft.com/en-us/sysinternals/downloads/debugview) log of starting Krita. Does your computer have a dual GPU, so you can run Krita either on Intel or on the Nvidia gpu? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 414933] Icons randomly rearrange themselves when minimizing/restoring
https://bugs.kde.org/show_bug.cgi?id=414933 --- Comment #4 from heroofg...@gmail.com --- (In reply to Michail Vourlakos from comment #1) > 1. Send me a screenshot of plasma systemsettings->Display And > Monitor->Compositor > 2. Latte is not responsible for tasks ordering, plasma libtaskmanager is. If > you use plasma icon-only taskmanager instead of Latte, dont you have the > same issue in your system? > 3. Send me your Latte layout file please to check it out if I can reproduce > in my system The icon-only taskmanager does not exhibit this problem. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 414933] Icons randomly rearrange themselves when minimizing/restoring
https://bugs.kde.org/show_bug.cgi?id=414933 --- Comment #3 from heroofg...@gmail.com --- Created attachment 124384 --> https://bugs.kde.org/attachment.cgi?id=124384=edit system settings -> display and monitor -> compositor -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414955] KMail stops responding when preview pane active on Wayland-Plasma
https://bugs.kde.org/show_bug.cgi?id=414955 Sandro Knauß changed: What|Removed |Added Severity|crash |normal --- Comment #1 from Sandro Knauß --- It is reported as Debian Bug: https://bugs.debian.org/946365 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414958] New: System settings crashes when crawling in Application Style settings
https://bugs.kde.org/show_bug.cgi?id=414958 Bug ID: 414958 Summary: System settings crashes when crawling in Application Style settings Product: systemsettings Version: 5.17.4 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nheghathivhis...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.4) (Compiled from sources) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.4.2-gentoo x86_64 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: Switched focus from Application Style to Window Decorations. The crash can be reproduced every time. -- Backtrace: Application: Nastavení systému (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f170bd344c0 (LWP 30272))] Thread 34 (Thread 0x7f1670daa700 (LWP 30376)): #0 0x7f170e0f5819 in g_mutex_lock (mutex=mutex@entry=0x7f1664000c30) at ../glib-2.60.7/glib/gthread-posix.c:1354 #1 0x7f170e0a7180 in g_main_context_acquire (context=0x7f1664000c30) at ../glib-2.60.7/glib/gmain.c:3250 #2 0x7f170e0a7ff5 in g_main_context_iterate (context=context@entry=0x7f1664000c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib-2.60.7/glib/gmain.c:3877 #3 0x7f170e0a826f in g_main_context_iteration (context=0x7f1664000c30, may_block=may_block@entry=1) at ../glib-2.60.7/glib/gmain.c:3988 #4 0x7f1710220edb in QEventDispatcherGlib::processEvents (this=0x7f1664000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f17101ca13b in QEventLoop::exec (this=this@entry=0x7f1670da9e10, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f1710022931 in QThread::exec (this=this@entry=0x559935e2cb50) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f170f2cf165 in QQmlThreadPrivate::run (this=0x559935e2cb50) at qml/ftw/qqmlthread.cpp:152 #8 0x7f17100239d1 in QThreadPrivate::start (arg=0x559935e2cb50) at thread/qthread_unix.cpp:360 #9 0x7f170e95efd4 in start_thread (arg=) at pthread_create.c:479 #10 0x7f170fc51e5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 33 (Thread 0x7f169897e700 (LWP 30374)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x559935b71658) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x559935b71608, cond=0x559935b71630) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x559935b71630, mutex=0x559935b71608) at pthread_cond_wait.c:638 #3 0x7f170374c9db in cnd_wait (mtx=0x559935b71608, cond=0x559935b71630) at ../mesa-19.3.0-rc6/include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x559935f0c680) at ../mesa-19.3.0-rc6/src/util/u_queue.c:275 #5 0x7f170374c5e7 in impl_thrd_routine (p=) at ../mesa-19.3.0-rc6/include/c11/threads_posix.h:87 #6 0x7f170e95efd4 in start_thread (arg=) at pthread_create.c:479 #7 0x7f170fc51e5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7f16735bf700 (LWP 30372)): #0 0x7f170fc49a7f in __GI___poll (fds=0x7f166c0dcaf0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f170e0a814e in g_main_context_poll (priority=, n_fds=1, fds=0x7f166c0dcaf0, timeout=, context=0x7f166c0d6680) at ../glib-2.60.7/glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x7f166c0d6680, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib-2.60.7/glib/gmain.c:3922 #3 0x7f170e0a826f in g_main_context_iteration (context=0x7f166c0d6680, may_block=may_block@entry=1) at ../glib-2.60.7/glib/gmain.c:3988 #4 0x7f1710220edb in QEventDispatcherGlib::processEvents (this=0x7f166c0b4a90, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f17101ca13b in QEventLoop::exec (this=this@entry=0x7f16735bee10, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f1710022931 in QThread::exec (this=this@entry=0x559935e460a0) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f170f2cf165 in QQmlThreadPrivate::run (this=0x559935e460a0) at qml/ftw/qqmlthread.cpp:152 #8 0x7f17100239d1 in QThreadPrivate::start (arg=0x559935e460a0) at thread/qthread_unix.cpp:360 #9 0x7f170e95efd4 in start_thread (arg=) at pthread_create.c:479 #10 0x7f170fc51e5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7f169a5fc700 (LWP 30305)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x559935856398) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1
[kdenlive] [Bug 414815] Automatic creating profile upon clip addition crashes the app
https://bugs.kde.org/show_bug.cgi?id=414815 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||timeline_corruption+ --- Comment #1 from emohr --- I tried with the daily build and it doesn't crash anymore. I think it was fixed with 19.11.90. Try with todays nighlty build. BTW: Your clip has 29.303fps?! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414959] New: Send by émail with Thunderbird does not work anymore
https://bugs.kde.org/show_bug.cgi?id=414959 Bug ID: 414959 Summary: Send by émail with Thunderbird does not work anymore Product: digikam Version: 6.3.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Generic-SendByMail Assignee: digikam-bugs-n...@kde.org Reporter: philippe.quag...@laposte.net Target Milestone: --- Since few releases, it seems that the «send by email» tool does not work anymore. It does not open Thunderbird, however the other steps are working fine (the pop up windows asking for the image size, etc.). I wonder if it does not comes from the the new packaging method (with the PPA it was working, but may be no more with the new appimage packaging method ? Best regards STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414943] Digikam shows image twice and isnt uasble
https://bugs.kde.org/show_bug.cgi?id=414943 --- Comment #5 from s...@anders-hamburg.de --- Hi Maik, I did not use wayland. echo $XDG_SESSION_TYPE returns x11 Sven -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414939] Compositions names untranslatable.
https://bugs.kde.org/show_bug.cgi?id=414939 emohr changed: What|Removed |Added Status|REPORTED|CONFIRMED Flags||Brainstorm+ Ever confirmed|0 |1 CC||fritzib...@gmx.net --- Comment #1 from emohr --- Hello Gabriel. You are right only 2 compostions are translated "Barrido" and "Componer y transformer". No it's not on the radar. Could you do the translation? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414950] Krita closes when trying to open a project
https://bugs.kde.org/show_bug.cgi?id=414950 --- Comment #3 from Xabi --- (In reply to Boudewijn Rempt from comment #1) > Could you also attach the file? By cleaning the layers, I have been able to see that what prevents the file from being loaded is a layer of paint with a coloration mask. I attach the file. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414950] Krita closes when trying to open a project
https://bugs.kde.org/show_bug.cgi?id=414950 --- Comment #2 from Xabi --- Created attachment 124385 --> https://bugs.kde.org/attachment.cgi?id=124385=edit ZIP with Krita file -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414960] New: fails to function in i3
https://bugs.kde.org/show_bug.cgi?id=414960 Bug ID: 414960 Summary: fails to function in i3 Product: dolphin Version: 19.08.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@poeritz.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY dolphin start up takes 28 seconds if /usr/libexec/kactivitymanagerd is not running. By default i3 does not care/know about /usr/libexec/kactivitymanagerd. Even when /usr/libexec/kactivitymanagerd runs, dolphin lacks basic functionality: - right click menu on files, does not appear at all (so no 'open with...' or see properties' options) - when exiting from within the program, it takes about 45 sec to shut down. All in all, dolphin should start (fast) and function normaly, even if not run inside a KDE-Plasma desktop environment. For now on Fedore-KDE-spin, it does not. STEPS TO REPRODUCE 1. install Fedora 31 KDE-spin 2. install i3 and run it 3. start dolphin and see the errors listed above OBSERVED RESULT EXPECTED RESULT Should work just as it does in the KDE-Plasma Desktop. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 31 KDE spin (available in About System) KDE Plasma Version: 5.64.0-1.fc31 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414959] Send by émail with Thunderbird does not work anymore
https://bugs.kde.org/show_bug.cgi?id=414959 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Works here without problems, both native digiKam version, as well as AppImage under openSUSE. Do you use native digiKam Ubuntu packages or the AppImage? Can you please post the output from the console? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414959] Send by émail with Thunderbird does not work anymore
https://bugs.kde.org/show_bug.cgi?id=414959 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- It work here too, using Mageia 6/7 and Centos 7 (both native and Appimage) Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414943] Digikam shows image twice and isnt uasble
https://bugs.kde.org/show_bug.cgi?id=414943 --- Comment #6 from caulier.gil...@gmail.com --- Which Qt version is used by both digiKam (RPM and compiled). Look in Help/Components Info for details. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414943] digiKam shows image twice and isn't usable
https://bugs.kde.org/show_bug.cgi?id=414943 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Digikam shows image twice |digiKam shows image twice |and isnt uasble |and isn't usable -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414959] Send by émail with Thunderbird does not work anymore
https://bugs.kde.org/show_bug.cgi?id=414959 --- Comment #3 from philippe.quag...@laposte.net --- Hello, I'm using the AppImage package. Here is the output of the console: philippe@philippe-desktop:~/Applications$ ./digikam-6.3.0-x86-64_680a39a84a93856de2caed4b4086c7db.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Note: to integrate this bundle to your desktop, use AppImageLauncher. libudev.so.0 -- Preloading shared libs: Digikam::DXmlGuiWindow::setupIconTheme: Breeze icons resource file found Digikam::DXmlGuiWindow::setupIconTheme: Breeze-dark icons resource file found Digikam::ApplicationSettings::setApplicationStyle: Switch to widget style: "" Digikam::AlbumWatch::AlbumWatch: AlbumWatch is disabled Digikam::AlbumManager::setDatabase: Database Parameters: Type: "QSQLITE" DB Core Name: "/home/philippe/Images/BDDDigikam/digikam4.db" DB Thumbs Name: "/home/philippe/Images/BDDDigikam/thumbnails-digikam.db" DB Face Name: "/home/philippe/Images/BDDDigikam/recognition.db" DB Similarity Name: "/home/philippe/Images/BDDDigikam/similarity.db" Connect Options: "" Host Name:"" Host port:-1 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "" Password: "" Digikam::DbEngineConfigSettingsLoader::readConfig: Loading SQL code from config file "/tmp/.mount_digikaxv6gmw/usr/share/digikam/database/dbconfig.xml" Digikam::DbEngineConfigSettingsLoader::readConfig: Checking XML version ID => expected: 3 found: 3 Digikam::CoreDbSchemaUpdater::update: Core database: running schema update Digikam::CoreDbSchemaUpdater::startUpdates: Core database: have a structure version 10 Digikam::CoreDbSchemaUpdater::makeUpdates: Core database: makeUpdates 10 to 10 Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/philippe/Images" uuid "volumeid:?uuid=5112bacb-ebc3-43a3-a340-6895793ef206" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2011_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/Photos_scans" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2010_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2008_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2006_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2005_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/1999_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2012_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2013_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2014_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2015_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2016_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2017_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2018_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/2019_Photos" uuid "volumeid:?uuid=2f05e4b1-d13b-445d-8c36-93703587c231" Digikam::CollectionManager::updateLocations: location for "/home/philippe/Images" is available true Digikam::CollectionManager::updateLocations: location for "/mnt/2f05e4b1-d13b-445d-8c36-93703587c231/2011_Photos" is available true Digikam::CollectionManager::updateLocations: location for "/mnt/2f05e4b1-d13b-445d-8c36-93703587c231/Photos_scans" is available true Digikam::CollectionManager::updateLocations: location for "/mnt/2f05e4b1-d13b-445d-8c36-93703587c231/2010_Photos" is available true Digikam::CollectionManager::updateLocations: location for "/mnt/2f05e4b1-d13b-445d-8c36-93703587c231/2008_Photos" is available true
[kdenlive] [Bug 414939] Compositions names untranslatable.
https://bugs.kde.org/show_bug.cgi?id=414939 --- Comment #2 from Gabriel Gazzán --- Well, that's what I'm reporting: that they currently *can't* be translated. Whenever they do I will translate them for sure. ;) (Spanish translation is always at "100% translated" status since years ago, whatever you happen to see untranslated is most likely because either it is not available to be translated, or is a recently added feature that I still didn't see in the last PO file). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397677] Folder list shows all mails as unread
https://bugs.kde.org/show_bug.cgi?id=397677 Saeid Akbari changed: What|Removed |Added CC||saeidsc...@yahoo.com --- Comment #3 from Saeid Akbari --- Having this issue for quite some time. Used to work around it by using: akonadictl fsck while KMail is running and then restarting KMail afterward. But even this doesn't work anymore. It is really annoying and makes KMail unusable. KMail 19.08.3 KDE Frameworks 5.64.0 Qt 5.12.5 PostgreSQL 10.9 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414957] Unable to Open program
https://bugs.kde.org/show_bug.cgi?id=414957 --- Comment #2 from Asuna --- Well, Good news and Bad news. when I went to re download the version that was causing the problem I prompted that the program was already running so I went into task manager I wasn't showing processes as running went into details and it was still running there killed it. ran the installer and the program opened up. I rebooted my PC however just to be sure that this wasn't going be an ongoing issues and ran the debug view (attached) and it went into not responding again. I can set it up that it can run on the GPU but i never set it up that way when i built this PC On Sun, Dec 8, 2019 at 11:53 AM Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=414957 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO >Platform|Windows CE |MS Windows > Status|REPORTED|NEEDSINFO > CC||b...@valdyas.org > > --- Comment #1 from Boudewijn Rempt --- > Can you please attach the output of help->system information for bug > reports to > this bug, and preferably also a debugview > (https://docs.microsoft.com/en-us/sysinternals/downloads/debugview) log of > starting Krita. > > Does your computer have a dual GPU, so you can run Krita either on Intel > or on > the Nvidia gpu? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411003] Tabs that do not fit in Konsole window expand it instead of being hidden
https://bugs.kde.org/show_bug.cgi?id=411003 answer2...@yandex.ru changed: What|Removed |Added Version Fixed In||19.08.1 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from answer2...@yandex.ru --- Fixed in 19.08.1 and up. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414959] Send by email with Thunderbird does not work anymore
https://bugs.kde.org/show_bug.cgi?id=414959 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Send by émail with |Send by email with |Thunderbird does not work |Thunderbird does not work |anymore |anymore --- Comment #4 from caulier.gil...@gmail.com --- thunderbird executable is not in you PATH variable ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389665] Rotating screen doesn't work on wayland
https://bugs.kde.org/show_bug.cgi?id=389665 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #33 from Oded Arbel --- Still an issue with KWin 5.17.80+p19.10+git20191203.2043-0 from KCI. This issue is the main reason I'm still using X11. Regarding the discussion in https://phabricator.kde.org/D19860 (I'm commenting here because I'm not sure if users commenting about their experiences are welcome in phabricator), I don't think that supporting desktop effects should block this non-eye-candy change - especially in regards to blur - which already works very partially in X11 and doesn't behave well on rotated screens there either. -- You are receiving this mail because: You are watching all bug changes.
