[kde] [Bug 417990] Widgets that launch .desktop apps now open them in a text editor
https://bugs.kde.org/show_bug.cgi?id=417990 --- Comment #6 from David --- FYI, found a fork of the widget that solved the issue, and from the commit that did it, looks like it was something with KIO: https://github.com/XutaxKamay/plasma-applet-resources-monitor/commit/fe5332589cb839327ce89f03645a93934c0ab2c6 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417995] Latte dock takes several seconds to show up after log in
https://bugs.kde.org/show_bug.cgi?id=417995 --- Comment #3 from David --- (In reply to Michail Vourlakos from comment #2) > Have you tried with the Default Latte layout to reproduce this, to make sure > that is not one of your applets to blame? Problem still happens with the default layouts "plasma" and "unity". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 355838] Sort images by orientation mode
https://bugs.kde.org/show_bug.cgi?id=355838 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Isn't sorting by aspect ratio almost the wished feature? Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417049] lamp effect doesnt work no more
https://bugs.kde.org/show_bug.cgi?id=417049 mauro.miate...@virgilio.it changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REOPENED --- Comment #4 from mauro.miate...@virgilio.it --- I already attached report, do you need some more info? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 418074] KDE Connect crashed sometimes when sharing files from Android
https://bugs.kde.org/show_bug.cgi?id=418074 --- Comment #2 from stardiviner --- Created attachment 126325 --> https://bugs.kde.org/attachment.cgi?id=126325=edit KDE Connect can't start after manually stopped previous suspended transfer task -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 418074] KDE Connect crashed sometimes when sharing files from Android
https://bugs.kde.org/show_bug.cgi?id=418074 --- Comment #1 from stardiviner --- Created attachment 126324 --> https://bugs.kde.org/attachment.cgi?id=126324=edit KDE Connect suspend on file transfering sometimes -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418061] Position of faces copied when rotating an image
https://bugs.kde.org/show_bug.cgi?id=418061 --- Comment #9 from Maik Qualmann --- One more word about the face rectangles. The face rectangles are still saved to the aligned image within the digiKam DB so that all old created face rectangles are retained. If you write all the metadata from the DB into the images using the maintenance tool, you should no longer have any problems re-read the metadata from the images. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418061] Position of faces copied when rotating an image
https://bugs.kde.org/show_bug.cgi?id=418061 Maik Qualmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/7305b3927750 ||2e9ad3d2422d7a109013dd666d5 ||e Resolution|--- |FIXED Version Fixed In||7.0.0 Status|REPORTED|RESOLVED --- Comment #8 from Maik Qualmann --- Git commit 7305b39277502e9ad3d2422d7a109013dd666d5e by Maik Qualmann. Committed on 23/02/2020 at 06:39. Pushed by mqualmann into branch 'master'. ignore lazy synchronization for transform actions FIXED-IN: 7.0.0 M +2-1NEWS M +1-1core/libs/fileactionmanager/fileworkeriface.cpp https://invent.kde.org/kde/digikam/commit/7305b39277502e9ad3d2422d7a109013dd666d5e -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #29 from Michail Vourlakos --- This bug is pretty serious, especially the part of not saving user data on each relogin. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 Michail Vourlakos changed: What|Removed |Added Severity|normal |critical Priority|NOR |VHI -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418061] Position of faces copied when rotating an image
https://bugs.kde.org/show_bug.cgi?id=418061 --- Comment #7 from Maik Qualmann --- The cause is active lazy synchronization AND the activated option to re-read the images when changes are made. That will be interesting to fix. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417946] Tool not implemented
https://bugs.kde.org/show_bug.cgi?id=417946 --- Comment #7 from Maik Qualmann --- The Healing Clone Tool is not included in digiKam-6.1.0, it was deactivated because it was not yet finished. If you delete the menu file under kxmlgui5, is the Healing Clone Tool available in the AppImage? Maik -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 418076] New: KDE Connect Slideshow Remote Pointer bug
https://bugs.kde.org/show_bug.cgi?id=418076 Bug ID: 418076 Summary: KDE Connect Slideshow Remote Pointer bug Product: kdeconnect Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: albertodurmie...@yahoo.com Target Milestone: --- Application: kdeconnectd (1.4.0) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.3.0-40-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: When clicking "Pointer" button in KDE Android APP the KDE Connect Crashed. The crash can be reproduced every time. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff850704800 (LWP 3974))] Thread 5 (Thread 0x7ff80d9af700 (LWP 4475)): #0 0x7ff84d0e60b4 in __GI___libc_read (fd=24, buf=0x7ff80d9aeb70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7ff8479ac2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff8479670b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff847967570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff8479676dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff84da510db in QEventDispatcherGlib::processEvents (this=0x7ff80b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7ff84d9f063a in QEventLoop::exec (this=this@entry=0x7ff80d9aed80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7ff84d801317 in QThread::exec (this=) at thread/qthread.cpp:536 #8 0x7ff83c4ab605 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7ff84d8027ec in QThreadPrivate::start (arg=0x55ad153e1e80) at thread/qthread_unix.cpp:342 #10 0x7ff849b046db in start_thread (arg=0x7ff80d9af700) at pthread_create.c:463 #11 0x7ff84d0f788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7ff80e1b0700 (LWP 4474)): #0 0x7ff849b0a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55ad15079c68) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55ad15079c18, cond=0x55ad15079c40) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55ad15079c40, mutex=0x55ad15079c18) at pthread_cond_wait.c:655 #3 0x7ff80eecaebb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7ff80eecaab7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7ff849b046db in start_thread (arg=0x7ff80e1b0700) at pthread_create.c:463 #6 0x7ff84d0f788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7ff830a65700 (LWP 3977)): #0 0x7ff84d0e60b4 in __GI___libc_read (fd=10, buf=0x7ff830a64b90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7ff8479ac2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff8479670b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff847967570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff8479676dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff84da510db in QEventDispatcherGlib::processEvents (this=0x7ff824000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7ff84d9f063a in QEventLoop::exec (this=this@entry=0x7ff830a64da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7ff84d801317 in QThread::exec (this=) at thread/qthread.cpp:536 #8 0x7ff84d8027ec in QThreadPrivate::start (arg=0x55ad14e8fea0) at thread/qthread_unix.cpp:342 #9 0x7ff849b046db in start_thread (arg=0x7ff830a65700) at pthread_create.c:463 #10 0x7ff84d0f788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7ff831c76700 (LWP 3976)): #0 0x7ff84d0e60b4 in __GI___libc_read (fd=7, buf=0x7ff831c75b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7ff8479ac2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff8479670b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff847967570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff8479676dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff84da510db in QEventDispatcherGlib::processEvents (this=0x7ff82c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7ff84d9f063a in QEventLoop::exec (this=this@entry=0x7ff831c75d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7
[digikam] [Bug 418057] icons missing in xubuntu
https://bugs.kde.org/show_bug.cgi?id=418057 --- Comment #5 from Maik Qualmann --- Start digiKam from the console and activate the debug output with: export QT_LOGGING_RULES="digikam.*=true" Then post the messages in the console until digiKam has started. Did you read that you have to restart digiKam after changing the icon theme? Is the Breeze Icon theme in your distribution possibly packed in different packages? Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418075] kwin crashes if a window title contains emoji.
https://bugs.kde.org/show_bug.cgi?id=418075 Khyota changed: What|Removed |Added Attachment #126323|0 |1 is obsolete|| --- Comment #3 from Khyota --- Comment on attachment 126323 --> https://bugs.kde.org/attachment.cgi?id=126323 Opening this file in kate will cause kwin to crash. oops, bugzilla filtered it out. basically just save a file in kate with '' to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418075] kwin crashes if a window title contains emoji.
https://bugs.kde.org/show_bug.cgi?id=418075 --- Comment #2 from Khyota --- Created attachment 126323 --> https://bugs.kde.org/attachment.cgi?id=126323=edit Opening this file in kate will cause kwin to crash. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418075] kwin crashes if a window title contains emoji.
https://bugs.kde.org/show_bug.cgi?id=418075 --- Comment #1 from Khyota --- Created attachment 126322 --> https://bugs.kde.org/attachment.cgi?id=126322=edit backtrace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418075] New: kwin crashes if a window title contains emoji.
https://bugs.kde.org/show_bug.cgi?id=418075 Bug ID: 418075 Summary: kwin crashes if a window title contains emoji. Product: kwin Version: 5.18.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: khy...@redhyena.net Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open the crashtest file in kate. 2. 3. OBSERVED RESULT kwin crashes. EXPECTED RESULT Title bar of the kate window should display the character correctly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67 Qt Version: 5.14.1 ADDITIONAL INFORMATION It has been quite common for this to occur while opening a webpage with a forbidden character. May be related to a window management effect. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 418074] New: KDE Connect crashed sometimes when sharing files from Android
https://bugs.kde.org/show_bug.cgi?id=418074 Bug ID: 418074 Summary: KDE Connect crashed sometimes when sharing files from Android Product: kdeconnect Version: 1.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: numbch...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. select some photos on Android 2. choose share to kde connect 3. KDE Plasmoid kde connection on laptop crashed sometimes OBSERVED RESULT KDE Plasmoid kde connection on laptop crashed sometimes EXPECTED RESULT It should be transfer correctly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.17.5-2 KDE Frameworks Version: Qt Version: 5.14.1-1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 334080] kdeconnect,some sent photo are uncomplete
https://bugs.kde.org/show_bug.cgi?id=334080 stardiviner changed: What|Removed |Added CC||numbch...@gmail.com --- Comment #48 from stardiviner --- This problem stills happens on KDE Connect version 1.4-1. I'm using Arch Linux. I don't know how to upgrade to latest version KDE Connect. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396137] Okular hangs when scrolling fast on both pdf and djvu documents
https://bugs.kde.org/show_bug.cgi?id=396137
antonini44...@gmail.com changed:
What|Removed |Added
CC||antonini44...@gmail.com
--- Comment #12 from antonini44...@gmail.com ---
I think I discovered a cause for this, whuch is related to cgroups and limiting
Okular RAM.
My version of Okular is 1.7.2. My PC has 4 GB of RAM. I was often running into
slowdowns because of thrashing very often. So I set up a few cgroups in order
to actually take control of RAM. I put in cgroups preety much every program
that used more than 100 MB. Okular often went over that much RAM because I
viewed several PDF tabs. I set up cgroups according to
https://askubuntu.com/questions/836469/install-cgconfig-in-ubuntu-16-04.
I was tinkering with the cgroups and I settled for this cgroup config on Okular
like this in /etc/cgconfig:
group main/documents {
memory {
memory.limit_in_bytes = 7200;
memory.soft_limit_in_bytes = 400;
}
}
How did I find it out? Yesterday, I set up a Kubuntu VM. I was also testing
Okular (Kubuntu came with Okular 1.7.3, I'm aware this bug wasn't patched on
it) to try to make the bug happen. I copied to the VM a large PDF with hundreds
of pages. I scrolled it for several minutes, page view set to fit width. I did
it franticallu almost, but nothing happened. Surprisingly, Okular didn't slow
down, nor did this bug triggered.
Today I disabled the cgroup on Okular. I opened the same PDF, and I could not
possibly trigger the bug either. I also noticed Okular beheves preety smoothly.
When the cgroup was enabled, PDFs rendered noticeably slowly. Obviously!
I just found Okular memory settings. I set it to run using as little as
needed.
Thanks Tobias Deiminger for patching out the bug in newer versions.
I hope that this helps with anything.
--
You are receiving this mail because:
You are watching all bug changes.
[elisa] [Bug 418073] New: Overlapped text on the comments
https://bugs.kde.org/show_bug.cgi?id=418073 Bug ID: 418073 Summary: Overlapped text on the comments Product: elisa Version: 19.12.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: gagor...@gmail.com Target Milestone: --- Created attachment 126321 --> https://bugs.kde.org/attachment.cgi?id=126321=edit On this screen shot you could watch the problem in in comments. SUMMARY Overlapped text on the comments. STEPS TO REPRODUCE 1. Go to Tracks. 2. Click over any music on (i) view details. 3. Then, you would be able observe the bug OBSERVED RESULT Comments are overlapped. EXPECTED RESULT The text aren't overlapped. SOFTWARE/OS VERSIONS Linux: 5.3.0-40 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Sorry by any inconvenient. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 418072] New: Lyric doesn't show paragraphs as comments
https://bugs.kde.org/show_bug.cgi?id=418072 Bug ID: 418072 Summary: Lyric doesn't show paragraphs as comments Product: elisa Version: 19.12.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: gagor...@gmail.com Target Milestone: --- Created attachment 126320 --> https://bugs.kde.org/attachment.cgi?id=126320=edit On this screen shot you could watch the problem in lyric and expected result in comments. SUMMARY Lyric doesn't show paragraphs as the comments in attached picture. STEPS TO REPRODUCE 1. Play anyone song with lyric. 2. Go to "Now Playing" 3. Then, you would be able observe the bug OBSERVED RESULT The words are together when it should be separate as a paragraph. EXPECTED RESULT The text are below the previus text as the comments in attached picture. SOFTWARE/OS VERSIONS Linux: 5.3.0-40 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Sorry by any inconvenient. I tested with Clementine software and it show correctly the lyrics but I would prefer Elisa software. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416692] yes
https://bugs.kde.org/show_bug.cgi?id=416692 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416674] Desktop and taskbar crash when I copy a file to a usb flash drive
https://bugs.kde.org/show_bug.cgi?id=416674 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417049] lamp effect doesnt work no more
https://bugs.kde.org/show_bug.cgi?id=417049 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 394204] Kirigami showPassiveNotification with action button hijacks touch events after timeout
https://bugs.kde.org/show_bug.cgi?id=394204 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418071] New: Moving layers that has any area made with select>fill is slow to move with move tool
https://bugs.kde.org/show_bug.cgi?id=418071 Bug ID: 418071 Summary: Moving layers that has any area made with select>fill is slow to move with move tool Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Move Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY Happens in both nightly git 369d552, 4.2.8. Moving layers that has any area that made with select>fill is much slower to move with move tool compared to the layer that has only freehand brushworks. STEPS TO REPRODUCE 1. Select any layer > Select any area with any Selection Tool > Fill with Background or Foreground Color > Deselect 1-1. Try to move the layer with Move Tool 1-2. Clear(erase) the layer > paint the same amount of area with Freehand Brush Tool > Try to move the layer with Move Tool OBSERVED RESULT 1-1 is much laggy and slower to move compared to the case of 1-2, as if you are trying to move the layer about the size of the entire canvas filled with color. EXPECTED RESULT There shouldn't be any difference. SOFTWARE/OS VERSIONS Windows: Win7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION * If you use Fill tool to fill inside any selection it takes a long time to finish(as if you are trying to fill the entire canvas). I think it's all the same issue. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418070] New: [Feature request] KMyMoney should be able to import multiple files
https://bugs.kde.org/show_bug.cgi?id=418070 Bug ID: 418070 Summary: [Feature request] KMyMoney should be able to import multiple files Product: kmymoney Version: git (master) Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY The bank I use doesn't seem to provide the ability to download a single .csv or .ofx file containing all of my transaction history, so in order to import any files for accounting I have to download them manually. As such, I have quite the high number of .ofx files. When I try to import them into KMyMoney, I can only select one file, which makes this a chore. I think KMyMoney should be able to import multiple files at the same time. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 418069] New: Baloo considers .ofx files as having invalid encoding
https://bugs.kde.org/show_bug.cgi?id=418069 Bug ID: 418069 Summary: Baloo considers .ofx files as having invalid encoding Product: frameworks-baloo Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: stefan.bru...@rwth-aachen.de Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY I don't know if this behavior is intended. Baloo seems to ignore indexing for .ofx, Open Financial Exchange, a file format typically used for accounting. It shows the following message: Invalid encoding. Ignoring "/path/to/file.ofx" SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200214 KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 Kernel Version: 5.5.2-1-default -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418068] New: KWin crashes when switching to another text VT and back
https://bugs.kde.org/show_bug.cgi?id=418068 Bug ID: 418068 Summary: KWin crashes when switching to another text VT and back Product: kwin Version: 5.17.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: co...@mimas.ru Target Milestone: --- Application: kwin_x11 (5.17.5) (Compiled from sources) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 4.19.104-gentoo x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: What I was doing when the application crashed: - Have KDE running on vt1, screen unlocked - Switch to vt2, see text login prompt - Wait a few seconds, switch back - Observe KWin crash notification GPU is NVIDIA with proprietary drivers. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7f6b76cf7880 (LWP 1332))] Thread 7 (Thread 0x7f6b6cdde700 (LWP 62562)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55db0760df94) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55db0760df40, cond=0x55db0760df68) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55db0760df68, mutex=0x55db0760df40) at pthread_cond_wait.c:655 #3 0x7f6b7cda4edb in QWaitConditionPrivate::wait (deadline=..., this=0x55db0760df40) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55db07be9ef0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f6b7cda4f49 in QWaitCondition::wait (this=this@entry=0x55db07be9ef8, mutex=mutex@entry=0x55db07be9ef0, time=time@entry=18446744073709551615) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #6 0x7f6b7be0bbf9 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x55db07be9ee8) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x55db07be9e70) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7f6b7be0be69 in QSGRenderThread::run (this=0x55db07be9e70) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7f6b7cd9fb16 in QThreadPrivate::start (arg=0x55db07be9e70) at thread/qthread_unix.cpp:360 #10 0x7f6b7c2d3497 in start_thread (arg=) at pthread_create.c:486 #11 0x7f6b7e3923cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f6b6700 (LWP 4075)): #0 0x7f6b7e386646 in __GI_ppoll (fds=fds@entry=0x7f6b64012388, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f6b7cf7a149 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f6b64012388) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f6b64012388) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll (fds=0x7f6b64012388, nfds=nfds@entry=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:153 #5 0x7f6b7cf7b198 in QEventDispatcherUNIX::processEvents (this=, flags=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #6 0x7f6b7cf2bfbb in QEventLoop::exec (this=this@entry=0x7f6b6fffed40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f6b7cd9ebd1 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f6b7cd9fb16 in QThreadPrivate::start (arg=0x55db075e9610) at thread/qthread_unix.cpp:360 #9 0x7f6b7c2d3497 in start_thread (arg=) at pthread_create.c:486 #10 0x7f6b7e3923cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f6b6e5bd700 (LWP 1550)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x7f6b7c8f4ef8 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f6b7c8f4ea8 , cond=0x7f6b7c8f4ed0 ) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f6b7c8f4ed0 , mutex=0x7f6b7c8f4ea8 ) at pthread_cond_wait.c:655 #3 0x7f6b7c80c0fa in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f6b7c8e6e00 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #4 0x7f6b7c80c119 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #5 0x7f6b7c2d3497 in start_thread (arg=) at pthread_create.c:486 #6 0x7f6b7e3923cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f6b6f7fe700 (LWP 1426)): #0 0x7f6b7e386646 in __GI_ppoll
[tellico] [Bug 418067] New: Internal field names can retain problematic characters
https://bugs.kde.org/show_bug.cgi?id=418067 Bug ID: 418067 Summary: Internal field names can retain problematic characters Product: tellico Version: 3.2.3 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: ro...@periapsis.org Target Milestone: --- Need to remove '.' and ':', among others. Reported here: https://forum.kde.org/viewtopic.php?f=200=164593=b145727e2e6cba25855e12745fbe78af Turns out that the file had internal field names of "lc-no.:" and "internal-sn:". The semi-colons cause problems with the namespace parsing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418066] New: Disconnecting display in Wayland leads to crash in libepoxy
https://bugs.kde.org/show_bug.cgi?id=418066
Bug ID: 418066
Summary: Disconnecting display in Wayland leads to crash in
libepoxy
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: dan...@lbe.rs
Target Milestone: ---
SUMMARY
KWin (Wayland) crashes when switching of a display.
STEPS TO REPRODUCE
1. Dell XPS 9370 with external display connected via USB-C/DisplayPort
2. kscreen-doctor output.1.disable
OBSERVED RESULT
Crash
"Couldn't find current GLX or EGL context."
Core was generated by `/usr/bin/kwin_wayland --xwayland --libinput
--exit-with-session=/usr/lib/startp'.
Program terminated with signal SIGABRT, Aborted.
#0 0x7f15e9e50ce5 in raise () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7f15e37b4840 (LWP 1469))]
(gdb) bt ful
#0 0x7f15e9e50ce5 in raise () at /usr/lib/libc.so.6
#1 0x7f15e9e3a92c in abort () at /usr/lib/libc.so.6
#2 0x7f15e9e3a727 in _nl_load_domain.cold () at /usr/lib/libc.so.6
#3 0x7f15e9e49426 in () at /usr/lib/libc.so.6
#4 0x7f15e92c00d8 in epoxy_get_proc_address (name=0x7f15e92d04d9
"glDeleteProgram")
at ../src/dispatch_common.c:863
__PRETTY_FUNCTION__ = "epoxy_get_proc_address"
egl_api =
__PRETTY_FUNCTION__ = "epoxy_get_proc_address"
#5 epoxy_get_proc_address (name=0x7f15e92d04d9
"glDeleteProgram")
at ../src/dispatch_common.c:839
egl_api =
__PRETTY_FUNCTION__ = "epoxy_get_proc_address"
#6 0x7f15e929672a in epoxy_glDeleteProgram_resolver () at
src/gl_generated_dispatch.c:81668
providers = {PROVIDER_Desktop_OpenGL_2_0, PROVIDER_OpenGL_ES_2_0,
gl_provider_terminator}
entrypoints = {9849, 9849}
#7 epoxy_glDeleteProgram_global_rewrite_ptr (program=19) at
src/gl_generated_dispatch.c:49458
#8 0x7f15e9dc96d6 in KWin::ContrastShader::reset() (this=0x7f15b0008850)
at /usr/src/debug/kwin/effects/backgroundcontrast/contrastshader.cpp:53
#9 KWin::ContrastShader::~ContrastShader() (this=0x7f15b0008850,
__in_chrg=)
at /usr/src/debug/kwin/effects/backgroundcontrast/contrastshader.cpp:43
#10 KWin::ContrastShader::~ContrastShader() (this=0x7f15b0008850,
__in_chrg=)
at /usr/src/debug/kwin/effects/backgroundcontrast/contrastshader.cpp:44
#11 0x7f15e9dc5161 in KWin::ContrastEffect::~ContrastEffect()
(this=0x7f15c000f810, __in_chrg=)
at /usr/src/debug/kwin/effects/backgroundcontrast/contrast.cpp:77
#12 0x7f15e9dc5209 in KWin::ContrastEffect::~ContrastEffect()
(this=0x7f15c000f810, __in_chrg=)
at /usr/src/debug/kwin/effects/backgroundcontrast/contrast.cpp:75
#13 0x7f15eb3ae10b in
KWin::EffectsHandlerImpl::destroyEffect(KWin::Effect*)
(this=this@entry=0x55fc6447c040, effect=0x7f15c000f810) at
/usr/src/debug/kwin/effects.cpp:1464
properties =
{> = {}, {p = {static
shared_null = {ref = {atomic = {_q_value = {> = {static
_S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end =
0, array = {0x0}}, d = 0x55fc644a1f20}, d = 0x55fc644a1f20}}
#14 0x7f15eb3af8e7 in KWin::EffectsHandlerImpl::unloadEffect(QString
const&)
(this=this@entry=0x55fc6447c040, name=...) at
/usr/src/debug/kwin/effects.cpp:1438
it = {i = 0x55fc6475a350}
#15 0x7f15eb3afdf0 in KWin::EffectsHandlerImpl::reloadEffect(KWin::Effect*)
(this=0x55fc6447c040, effect=) at
/usr/src/debug/kwin/effects.cpp:1522
effectName =
{static null = {}, d = 0x7f15e9de4480
}
#16 0x7f15e9dc792d in KWin::ContrastEffect::slotScreenGeometryChanged()
(this=0x7f15c000f810)
at /usr/src/debug/kwin/effects/backgroundcontrast/contrast.cpp:84
#17 0x7f15ea4c946e in () at /usr/lib/libQt5Core.so.5
#18 0x7f15eb2273a6 in KWin::EffectsHandler::screenGeometryChanged(QSize
const&) (this=, _t1=...)
at
/usr/src/debug/build/libkwineffects/kwineffects_autogen/EWIEGA46WW/moc_kwineffects.cpp:1738
_a = {0x0, 0x7fff54c724b0}
#19 0x7f15eb3a56a0 in KWin::EffectsHandlerImpl::desktopResized(QSize
const&) (this=, size=...)
at /usr/src/debug/kwin/effects.cpp:836
#20 0x7f15eb4b6dfe in KWin::Workspace::desktopResized()
(this=0x55fc63bef480)
at /usr/include/qt/QtCore/qsize.h:125
geom = {x1 = 0, y1 = 0, x2 = 1919, y2 = 1199}
#21 0x7f15ea4c94a0 in () at /usr/lib/libQt5Core.so.5
#22 0x7f15ea4c946e in () at /usr/lib/libQt5Core.so.5
#23 0x7f15eb5f9d3b in KWin::DrmBackend::enableOutput(KWin::DrmOutput*,
bool)
(this=0x55fc63b69140, output=, output@entry=0x55fc63be1cf0,
enable=enable@entry=false)
at /usr/src/debug/kwin/plugins/platforms/drm/drm_backend.cpp:572
#24 0x7f15eb60775a in KWin::DrmOutput::atomicDisable()
(this=0x55fc63be1cf0)
at /usr/src/debug/kwin/plugins/platforms/drm/drm_output.cpp:532
#25 0x7f15eb411169 in
KWin::Platform::requestOutputsChange(KWayland::Server::OutputConfigurationInterface*)
(this=0x55fc63b69140, config=0x55fc644faea0) at
/usr/src/debug/kwin/platform.cpp:174
output =
[Qt/KDE Flatpak Runtime] [Bug 417035] Maliit extension for KDE Flatpak Runtime
https://bugs.kde.org/show_bug.cgi?id=417035 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||flatpak-kde-runtime/merge_r ||equests/8 Status|REPORTED|RESOLVED --- Comment #3 from Aleix Pol --- Fix merged, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 418065] New: Crash during autocomplete under Wayland.
https://bugs.kde.org/show_bug.cgi?id=418065 Bug ID: 418065 Summary: Crash during autocomplete under Wayland. Product: kdevelop Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: da...@ingeniumdigital.com Target Milestone: --- Application: kdevelop (5.5.0) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.4-1-vanilla x86_64 Windowing system: Wayland Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: The crash occurs sporadically when autocomplete appears. Usually, upon restarting, the same autocomplete window will work fine, but a future one will crash KDevelop. - Custom settings of the application: Running under wayland. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9af178eac0 (LWP 24336))] Thread 18 (Thread 0x7f9a97fff700 (LWP 24509)): #0 0x7f9aff2ed795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9b01df223b in QWaitConditionPrivate::wait (deadline=..., this=0x55a993517660) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55a9934e6d00, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f9b01df22f9 in QWaitCondition::wait (this=0x55a9934e6c68, mutex=0x55a9934e6d00, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f9afe8766b0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f9afe876a1a in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #15 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #19 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #20 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #21 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #22 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #23 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #24 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #25 0x7f9afe87609b in ThreadWeaver::Thread::run() () from /usr/lib64/libKF5ThreadWeaver.so.5 #26 0x7f9b01dec6f8 in QThreadPrivate::start (arg=0x7f9a900032e0) at thread/qthread_unix.cpp:342 #27 0x7f9aff2e6efa in start_thread () from /lib64/libpthread.so.0 #28 0x7f9b03a5d3bf in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f9aa4de2700 (LWP 24508)): #0 0x7f9aff2ed795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9b01df223b in QWaitConditionPrivate::wait (deadline=..., this=0x55a993517660) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55a9934e6d00, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f9b01df22f9 in QWaitCondition::wait (this=0x55a9934e6c68, mutex=0x55a9934e6d00, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f9afe8766b0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from
[umbrello] [Bug 417937] No documentation for object and communication diagrams
https://bugs.kde.org/show_bug.cgi?id=417937 Oliver Kellogg changed: What|Removed |Added Summary|No documenation for object |No documentation for object |and communication diagrams |and communication diagrams CC||okellogg@users.sourceforge. ||net -- You are receiving this mail because: You are watching all bug changes.
[kbreakout] [Bug 418064] Paddle wont move
https://bugs.kde.org/show_bug.cgi?id=418064 Fredb <53pet...@tpg.com.au> changed: What|Removed |Added CC||53pet...@tpg.com.au -- You are receiving this mail because: You are watching all bug changes.
[kbreakout] [Bug 418064] New: Paddle wont move
https://bugs.kde.org/show_bug.cgi?id=418064 Bug ID: 418064 Summary: Paddle wont move Product: kbreakout Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: viranch.me...@gmail.com Reporter: 53pet...@tpg.com.au CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. start game 2. use the mouse, after about half blocks gone on the first level 3. the paddle stops moving 4. the ball is still moving 5. the mouse cursor appears and moves according to any mouse movements 6. then the paddle can be moved again 7. but by this time the ball has been lost OBSERVED RESULT 1. paddle locks up 2. cursor appears and moves instead (it appears the paddle looses focus hence the mous appears) EXPECTED RESULT 1. the cursor of the mouse should not appear 2. the paddle should never lockup SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: mint (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.
[krita] [Bug 414025] Jagged lines when canvas is too big and zoom out, it makes impossible to draw a smooth circle
https://bugs.kde.org/show_bug.cgi?id=414025 --- Comment #15 from Lissette --- Thank you very much! I confirm this fixed the problem for me :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418057] icons missing in xubuntu
https://bugs.kde.org/show_bug.cgi?id=418057 --- Comment #4 from kisha --- mh nope, still not working, mh strange -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417678] Dolphin Crashed when moving files
https://bugs.kde.org/show_bug.cgi?id=417678 Elvis Angelaccio changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE CC||elvis.angelac...@kde.org --- Comment #1 from Elvis Angelaccio --- No backtraces. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417394] Entries of "Open with" submenu behind Plasma panel on Wayland
https://bugs.kde.org/show_bug.cgi?id=417394 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 417968] Critical Break: Guiding via MOUNT Unavailable.
https://bugs.kde.org/show_bug.cgi?id=417968 --- Comment #5 from mountainai...@outlook.com --- Jasem -- I tried this multiple times, making no changes in between. One time, the Celestron CGX guide option showed up. I cannot figure out how it showed up. I had disconnected from the devices, but not stopped the INDI profile and had not disconnected any power or USB cables from devices. As soon as I disconnected and reconnected, it was gone and I cannot get it back. So somehow this issue is intermittent. Could it be an issue with the order in which the INDI drivers load and connect? I just have tried this 20 times but could not get it back. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 417248] html file received a perl file icon if it has "use strict" or "use warnings" in it
https://bugs.kde.org/show_bug.cgi?id=417248 Elvis Angelaccio changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM CC||elvis.angelac...@kde.org --- Comment #10 from Elvis Angelaccio --- (In reply to Nate Graham from comment #6) > Created attachment 125750 [details] > Test case file > > Bizarre. Can confirm. > > It seems like some code somewhere is unconditionally checking for "use > strict" to determine which icon to show. It's shared-mime-info. I'm not sure the attached test case is a valid HTML file (why would you put a perl script in a HTML page?). If it is, then the bug should be reported upstream at: https://gitlab.freedesktop.org/xdg/shared-mime-info -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 417099] Discover froze and crashed a few seconds later
https://bugs.kde.org/show_bug.cgi?id=417099 Patrick Silva changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Patrick Silva --- I'm not sure if the backtrace of the following reproducible crash is the same, but it's similar at least. 1. open discover 2. search for any of the following apps: volti, screensaver (screen + fire icon), workrave, xscorch, QasHctl 3. open its description page Discover freezes and crashes a few seconds later. Below I"m posting the backtrace after I open description page of workrave. bug 417800 and bug 418013 seem related/duplicate. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 Thread 13 (Thread 0x7fa495c62700 (LWP 5548)): #0 0x7fa4d7be0bf9 in __GI___poll (fds=0x7fa488019ae0, nfds=2, timeout=106714) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa4d233d5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa4d233d6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa4d88e50db in QEventDispatcherGlib::processEvents(QFlags) (this= 0x7fa488000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa4d888463a in QEventLoop::exec(QFlags) (this=this@entry=0x7fa495c61c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fa4d8695317 in QThread::exec() (this=) at thread/qthread.cpp:536 #6 0x7fa4d86967ec in QThreadPrivate::start(void*) (arg=0x556244d52200) at thread/qthread_unix.cpp:342 #7 0x7fa4d44da6db in start_thread (arg=0x7fa495c62700) at pthread_create.c:463 #8 0x7fa4d7bed88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fa485c23700 (LWP 5554)): #0 0x7fa4d7be0bf9 in __GI___poll (fds=0x7fa48c003ba0, nfds=1, timeout=106149) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa4d233d5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa4d233d6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa4d88e50db in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fa444000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa4d888463a in QEventLoop::exec(QFlags) (this=this@entry=0x7fa485c22c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fa4d8695317 in QThread::exec() (this=) at thread/qthread.cpp:536 #6 0x7fa4d86967ec in QThreadPrivate::start(void*) (arg=0x5562445d2170) at thread/qthread_unix.cpp:342 #7 0x7fa4d44da6db in start_thread (arg=0x7fa485c23700) at pthread_create.c:463 #8 0x7fa4d7bed88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fa497245700 (LWP 5547)): #0 0x7fa4d7be0bf9 in __GI___poll (fds=0x7fa490002de0, nfds=1, timeout=9990) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa4d233d5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa4d233d6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa4d88e50bc in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fa49b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7fa4d888463a in QEventLoop::exec(QFlags) (this=this@entry=0x7fa497244c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fa4d8695317 in QThread::exec() (this=) at thread/qthread.cpp:536 #6 0x7fa4d86967ec in QThreadPrivate::start(void*) (arg=0x556244d329e0) at thread/qthread_unix.cpp:342 #7 0x7fa4d44da6db in start_thread (arg=0x7fa497245700) at pthread_create.c:463 #8 0x7fa4d7bed88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fa486c24700 (LWP 5552)): #0 0x7fa4d44e09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x556244e8b880) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fa4d44e09f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x556244e8b830, cond=0x556244e8b858) at pthread_cond_wait.c:502 #2 0x7fa4d44e09f3 in __pthread_cond_wait (cond=0x556244e8b858, mutex=0x556244e8b830) at pthread_cond_wait.c:655 #3 0x7fa4d869cd9b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x556244e8b830) at thread/qwaitcondition_unix.cpp:146 #4 0x7fa4d869cd9b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x556244e8b810, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fa4d869cf19 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x556244e8b818, mutex=mutex@entry=0x556244e8b810, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7fa4dbf2a1d3 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x556244e8b808) at scenegraph/qsgthreadedrenderloop.cpp:255 #7
[krita] [Bug 416918] "Default colour model for new images" is ignored
https://bugs.kde.org/show_bug.cgi?id=416918 feyazabuba...@gmail.com changed: What|Removed |Added CC||feyazabuba...@gmail.com --- Comment #2 from feyazabuba...@gmail.com --- Can confirm for Feb 23rd 4.3.0 prealpha appimage git(369d552). Changing the default at the new file screen doesn't affect the value stored in settings. Claiming bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=401031 David Gow changed: What|Removed |Added CC||da...@ingeniumdigital.com --- Comment #10 from David Gow --- For what it's worth, this is still happening with Plasma 5.18 (on OpenSUSE Tumbleweed) Stacktrace is basically the same (I've only included the relevant thread here:) Thread 1 (Thread 0x7fda93445580 (LWP 18086)): [KCrash Handler] #6 0x7fda95a5b313 in XAddExtension (dpy=dpy@entry=0x55ada1f26e60) at InitExt.c:73 #7 0x7fda7c0422dd in _XftDisplayInfoGet (createIfNecessary=, dpy=0x55ada1f26e60) at xftdpy.c:91 #8 _XftDisplayInfoGet (dpy=dpy@entry=0x55ada1f26e60, createIfNecessary=createIfNecessary@entry=1) at xftdpy.c:62 #9 0x7fda7c04423e in XftFontInfoFill (dpy=dpy@entry=0x55ada1f26e60, pattern=pattern@entry=0x55ada25dc6a0, fi=fi@entry=0x7ffd37fa90f0) at xftfreetype.c:367 #10 0x7fda7c04521f in XftFontOpenPattern (dpy=0x55ada1f26e60, pattern=pattern@entry=0x55ada25dc6a0) at xftfreetype.c:1015 #11 0x7fda8c00837d in KFI::CFcEngine::getFont (this=this@entry=0x55ada252fdd8, size=size@entry=8) at /usr/src/debug/plasma5-desktop-5.18.0-3.1.x86_64/kcms/kfontinst/lib/FcEngine.cpp:1299 #12 0x7fda8c008602 in KFI::CFcEngine::queryFont (this=this@entry=0x55ada252fdd8) at /usr/src/debug/plasma5-desktop-5.18.0-3.1.x86_64/kcms/kfontinst/lib/FcEngine.cpp:1233 #13 0x7fda8c008718 in KFI::CFcEngine::getSizes (this=0x55ada252fdd8) at /usr/src/debug/plasma5-desktop-5.18.0-3.1.x86_64/kcms/kfontinst/lib/FcEngine.cpp:1391 #14 KFI::CFcEngine::getSizes (this=this@entry=0x55ada252fdd8) at /usr/src/debug/plasma5-desktop-5.18.0-3.1.x86_64/kcms/kfontinst/lib/FcEngine.cpp:1383 #15 0x7fda8c00ad71 in KFI::CFcEngine::draw (this=this@entry=0x55ada252fdd8, name=..., style=style@entry=4294967295, faceNo=faceNo@entry=0, txt=..., bgnd=..., w=256, h=256, thumb=true, range=..., chars=0x0) at /usr/src/debug/plasma5-desktop-5.18.0-3.1.x86_64/kcms/kfontinst/lib/FcEngine.cpp:876 #16 0x7fda8c01476f in KFI::CFontThumbnail::create (this=0x55ada252fdd0, path=..., width=128, height=128, img=...) at /usr/include/qt5/QtGui/qbrush.h:159 #17 0x7fda9156f06c in ThumbnailProtocol::createSubThumbnail (segmentHeight=34, segmentWidth=54, filePath=..., thumbnail=..., this=0x7ffd37fa96e0) at /usr/src/debug/kio-extras5-19.12.2-2.1.x86_64/thumbnail/thumbnail.cpp:727 #18 ThumbnailProtocol::drawSubThumbnail (this=this@entry=0x7ffd37fa9c20, p=..., filePath=..., width=width@entry=54, height=height@entry=34, xPos=xPos@entry=9, yPos=38, frameWidth=2) at /usr/src/debug/kio-extras5-19.12.2-2.1.x86_64/thumbnail/thumbnail.cpp:759 #19 0x7fda9156fb57 in ThumbnailProtocol::thumbForDirectory (this=this@entry=0x7ffd37fa9c20, directory=...) at /usr/src/debug/kio-extras5-19.12.2-2.1.x86_64/thumbnail/thumbnail.cpp:562 #20 0x7fda9157152e in ThumbnailProtocol::get (this=0x7ffd37fa9c20, url=...) at /usr/src/debug/kio-extras5-19.12.2-2.1.x86_64/thumbnail/thumbnail.cpp:238 #21 0x7fda9164278e in KIO::SlaveBase::dispatch (this=0x7ffd37fa9c20, command=67, data=...) at /usr/src/debug/kio-5.67.0-1.1.x86_64/src/core/slavebase.cpp:1197 #22 0x7fda91649a56 in KIO::SlaveBase::dispatchLoop (this=this@entry=0x7ffd37fa9c20) at /usr/src/debug/kio-5.67.0-1.1.x86_64/src/core/slavebase.cpp:338 #23 0x7fda91572629 in kdemain (argc=, argv=0x55ada1f105b0) at /usr/src/debug/kio-extras5-19.12.2-2.1.x86_64/thumbnail/thumbnail.cpp:138 #24 0x55ada0ef4bcb in launch (argc=4, _name=0x55ada1f10c98 "/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so", args=, cwd=, envc=0, envs=0x55ada1f10d3e "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x55ada0ef7175 "0") at /usr/src/debug/kinit-5.67.0-1.2.x86_64/src/kdeinit/kinit.cpp:704 #25 0x55ada0ef5df8 in handle_launcher_request (sock=, who=) at /usr/src/debug/kinit-5.67.0-1.2.x86_64/src/kdeinit/kinit.cpp:1142 #26 0x55ada0ef67d4 in handle_requests (waitForPid=0) at /usr/src/debug/kinit-5.67.0-1.2.x86_64/src/kdeinit/kinit.cpp:1335 #27 0x55ada0ef164d in main (argc=5, argv=) at /usr/src/debug/kinit-5.67.0-1.2.x86_64/src/kdeinit/kinit.cpp:1773 [Inferior 1 (process 18086) detached] -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417219] Daemonized Dolphin inappropriately triggers session restoration
https://bugs.kde.org/show_bug.cgi?id=417219 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #6 from Elvis Angelaccio --- (In reply to Nate Graham from comment #1) > Yes, the background daemon is to support the "open new folders in tabs > rather than new windows" feature. If you don't want a daemonized Dolphin > running, you can turn off this feature. Not exactly, the deamon is to support the freedesktop's File Manager DBus Interface and cannot be turned off. There is nothing to fix here, really. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418061] Position of faces copied when rotating an image
https://bugs.kde.org/show_bug.cgi?id=418061 --- Comment #6 from Rico --- Hi Maik, I played now around for a while and confused now. I was not able to reproduce it 100% now. Onetime it happened directly on start up, often not. First thouhgt was also it happens in combination with the preview in dolphin, or when the folder is just open but later it happened also with closed dolphin and worked somethimes with opened. I think it is also file related. One time only for one file the tag was copied. For other it worked in the same session. I cannot say how to reproduce but somethimes it happens. Could digikam lock somehow itself? I was wondering about the statusbar text " x fiels waiting for sync" (rough translated from german) . Could that be something combined with the lazy sync option maybe in combination with writing directly in the file? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417091] [Wayland] Dolphin window crashes as it updates its content
https://bugs.kde.org/show_bug.cgi?id=417091 Elvis Angelaccio changed: What|Removed |Added Keywords||wayland CC||elvis.angelac...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413947] Windows Client stops working correctly when it receives a notification from the phone
https://bugs.kde.org/show_bug.cgi?id=413947 bo08d...@gmail.com changed: What|Removed |Added CC||bo08d...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416989] Konqueror's terminal window does not start in current directory
https://bugs.kde.org/show_bug.cgi?id=416989 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org --- Comment #3 from Elvis Angelaccio --- (In reply to Jonathan Marten from comment #0) > SUMMARY > > Yes, this bug is being initially reported for Dolphin, because even though > the problem only shows up in Konqueror the bug seems to be either in the > DolphinPart or KParts. > > When using Konqueror's Tools - Open Terminal action (F4), the terminal shell > should start in the directory shown in the file manager. Since > https://phabricator.kde.org/D26140 this is not the case, the terminal always > starts in $HOME. > > In DolphinPart::slotOpenTerminal() that change replaced the stat and local > file conversion with KParts::ReadOnlyPart::localFilePath(). localFilePath() > returns d->m_file, which is never set by any function that DolphinPart > calls; it remains as null and so the KToolInvocation::invokeTerminal() > always starts in the home directory. > > DolphinPart::openUrl() calls KParts::ReadOnlyPart::setUrl() with the comment > "remember it at the KParts level", but KParts::ReadOnlyPart::setUrl() does > not set d->m_file, only KParts::ReadOnlyPart::openUrl() does. > > Possible solutions that I can think of would be either: > > (a) Call KParts::ReadOnlyPart::openUrl() instead of setUrl() in > DolphinPart::openUrl(). This looks like the simpler solution to me. Any volunteer? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417010] Dolphin crashes on startup with/after black desktop OpenSuse 15.1
https://bugs.kde.org/show_bug.cgi?id=417010 Elvis Angelaccio changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||elvis.angelac...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Elvis Angelaccio --- Does it crash every time? Have you tried to update your opensuse system? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418063] Adding and removing multiple widgets crash plasma desktop
https://bugs.kde.org/show_bug.cgi?id=418063 --- Comment #1 from medin --- This bug happens with many scenarios and sometimes no bug report is detected in notification area, here is a stack-trace from another scenario different from the one in the attached video but it leads to the same crash Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6c21cc11c0 (LWP 20640))] Thread 16 (Thread 0x7f6bca495700 (LWP 20813)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5608e63390b0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5608e6339060, cond=0x5608e6339088) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5608e6339088, mutex=0x5608e6339060) at pthread_cond_wait.c:638 #3 0x7f6c255fadbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6c255faeb1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6c272967b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f6c27296a1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f6c255f4c92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6c24a93669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f6c25277323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f6bcb28a700 (LWP 20812)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5608e4d643d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5608e4d64380, cond=0x5608e4d643a8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5608e4d643a8, mutex=0x5608e4d64380) at pthread_cond_wait.c:638 #3 0x7f6c255fadbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6c255faeb1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6c272967b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f6c27296a1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f6c255f4c92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6c24a93669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f6c25277323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f6bcbc77700 (LWP 20811)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5608df964850) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5608df964800, cond=0x5608df964828) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5608df964828, mutex=0x5608df964800) at pthread_cond_wait.c:638 #3 0x7f6c255fadbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6c255faeb1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6c272967b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f6c27296a1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f6c255f4c92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6c24a93669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f6c25277323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f6bee5c9700 (LWP 20810)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5608e1a4a2a0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5608e1a4a250, cond=0x5608e1a4a278) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5608e1a4a278, mutex=0x5608e1a4a250) at pthread_cond_wait.c:638 #3 0x7f6c255fadbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6c255faeb1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6c272967b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f6c27296a1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f6c255f4c92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6c24a93669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f6c25277323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f6bedc03700 (LWP 20807)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5608dfa59434) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5608dfa593e0, cond=0x5608dfa59408) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5608dfa59408, mutex=0x5608dfa593e0) at pthread_cond_wait.c:638 #3 0x7f6c255fadbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
[digikam] [Bug 417946] Tool not implemented
https://bugs.kde.org/show_bug.cgi?id=417946 --- Comment #6 from dantou --- Oh ! I have both Digikam : the one implemented with the OS and those in ".Appimage". Did I well understand that :"The File menu may be corrupt. Delete or rename the file under $HOME/.local/share/kxmlgui5/digikam.", tell the .Appimage one what menu had to be actived ? And than Digikam 6.1 has not "Clone" menu, he can't actived it ? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415179] Touchpad disabled when detected as both mouse and touchpad
https://bugs.kde.org/show_bug.cgi?id=415179 --- Comment #4 from akb825 --- After updating today having xf86-input-synaptics installed no longer works around the bug. Applying the X11 config by Mads was able to restore the touchpad. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 411196] Gwenview very slow to launch while the top item in the system clipboard was sent by KDE Connect using the shared clipboard feature
https://bugs.kde.org/show_bug.cgi?id=411196 Florian changed: What|Removed |Added CC||kde-b...@pyoworks.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418063] New: Adding and removing multiple widgets crash plasma desktop
https://bugs.kde.org/show_bug.cgi?id=418063 Bug ID: 418063 Summary: Adding and removing multiple widgets crash plasma desktop Product: plasmashell Version: 5.18.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: 1.0 Created attachment 126319 --> https://bugs.kde.org/attachment.cgi?id=126319=edit crash plasma desktop See my attached for more info about the crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418062] Can't specify svg full path for icon in .desktop file
https://bugs.kde.org/show_bug.cgi?id=418062 --- Comment #3 from Nico Lynzaad --- Created attachment 126318 --> https://bugs.kde.org/attachment.cgi?id=126318=edit Default Path - With Extension -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418062] Can't specify svg full path for icon in .desktop file
https://bugs.kde.org/show_bug.cgi?id=418062 --- Comment #2 from Nico Lynzaad --- Created attachment 126317 --> https://bugs.kde.org/attachment.cgi?id=126317=edit Default Path -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418062] Can't specify svg full path for icon in .desktop file
https://bugs.kde.org/show_bug.cgi?id=418062 --- Comment #1 from Nico Lynzaad --- Created attachment 126316 --> https://bugs.kde.org/attachment.cgi?id=126316=edit Full Path - Without Extension -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418062] New: Can't specify svg full path for icon in .desktop file
https://bugs.kde.org/show_bug.cgi?id=418062 Bug ID: 418062 Summary: Can't specify svg full path for icon in .desktop file Product: plasmashell Version: 5.18.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: nlynz...@zylangroup.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 126315 --> https://bugs.kde.org/attachment.cgi?id=126315=edit Full Path - With Extension SUMMARY When specifying the full path of a svg icon (ie /path/icon.svg), with or without the ".svg" extension specified, for an icon in a .desktop file the icon can't render in either dolphin or in the application launcher. When using the icon in the default icons path the icon displays correctly. This results in various applications that uses custom icon paths for svg icons to not display correctly in the application launcher and dolphin. As test case the following can be done to reproduce (Using KCalc as an example, same problem can be found for JetBrains IDEs and multiple other applications): 1) Copy accessories-calculator.svg from default theme folders to desktop, ie /home/user/desktop. 2) Open /usr/share/applications/org.kde.kcalc.desktop 3) Edit icon path for following three scenarios: 3a) Use full path: icon=/home/user/desktop/accessories-calculator.svg => Result: .desktop file does not display icon. 3b) Use full path excluding extension: icon=/home/user/desktop/accessories-calculator.svg => Result: .desktop file does not display icon. 3c) Use default icon path: icon=accessories-calculator or icon=accessories-calculator.svg => Result: .desktop file displays icon. EXPECTED RESULT Icons should be displayed when full file paths, with the extension specified, are used. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuse TumbleWeed (available in About System) KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Problem seems to be distribution agnostic. Tested on Kubuntu, KDE Neon, Manjaro, OpenSuse and FerenOS -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417461] KCM Color shouldn't use generic GTK CSS color classes
https://bugs.kde.org/show_bug.cgi?id=417461 --- Comment #7 from Nate Graham --- I don't see that this fully fixes Bug 412331. Can you confirm? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418061] Position of faces copied when rotating an image
https://bugs.kde.org/show_bug.cgi?id=418061 --- Comment #5 from Maik Qualmann --- In principle, the problem can only occur if the writing of facial rectangles in images is activated and a facial rectangle is in the metadata of the image. If the image is now read-only, the existing face rectangle is added again. It is also good to see on your image as the face rectangles are different (almost square / rectangle). Image or folder must be read-only. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418061] Position of faces copied when rotating an image
https://bugs.kde.org/show_bug.cgi?id=418061 --- Comment #4 from Rico --- metadata was written in preview of the picture, directly in the image, one time by drwing the rectangle, entering top and confirmed pushbutton with ok. Afterwards (directly I rotated the image in the preview. Each time, the tag was copied on time. The position was shifted also somehow by 90°. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418061] Position of faces copied when rotating an image
https://bugs.kde.org/show_bug.cgi?id=418061 --- Comment #3 from Rico --- Created attachment 126314 --> https://bugs.kde.org/attachment.cgi?id=126314=edit original pic2 Hi Maik, thanks for the fast response. I attached now the original picture, not the screenshot (the tags should be saved 4 times in the pic). Maybe it helps to answer your question. If not let me know where I can get the info you need. Regarding the older pics: It is a good thing to align with standards. Maybe one day face tags can be interpreted by other apps too. Do you think it is stable now and I can fix the position final? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #28 from Michail Vourlakos --- and please send also your .config/lattedockrc file -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395711] Since last Update kmail didn't load external images anymore
https://bugs.kde.org/show_bug.cgi?id=395711 --- Comment #23 from Tim Folger --- Just to add a bit more info: The message preview pane works as expected. That is, it loads external images for html messages. But if you double-click on a message to open a separate window, the message window fails to load the external images. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #27 from Michail Vourlakos --- Since which Latte version you are using Latte in your system? -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 417941] Migrate to Discourse
https://bugs.kde.org/show_bug.cgi?id=417941 --- Comment #5 from Recesvintvs --- I'd seen several bug reports like this: https://discourse.mozilla.org/t/localisation-file-bug-in-thunderbird-extension/24276 and I thought Mozilla was using Discourse as a bug tracker. Maybe just some people is using incorrectly Mozilla's Discourse to report bugs and I was mislead by that. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418061] Position of faces copied when rotating an image
https://bugs.kde.org/show_bug.cgi?id=418061 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- I cannot reproduce the problem. Which metadata settings do you use exactly? Metadata is written in the image? Sidecars? Yes, we have changed the behavior of the face rectangles in relation to the rotation and have now adapted them to other programs. This step was necessary to meet the standard. DigiKam used to save the face rectangles to the aligned image, now to the non-aligned image. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418061] Position of faces copied when rotating an image
https://bugs.kde.org/show_bug.cgi?id=418061 --- Comment #1 from Rico --- Created attachment 126313 --> https://bugs.kde.org/attachment.cgi?id=126313=edit screenshot2 second screenshot -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418061] New: Position of faces copied when rotating an image
https://bugs.kde.org/show_bug.cgi?id=418061 Bug ID: 418061 Summary: Position of faces copied when rotating an image Product: digikam Version: 7.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Maintenance Assignee: digikam-bugs-n...@kde.org Reporter: rico.zie...@posteo.de Target Milestone: --- Created attachment 126312 --> https://bugs.kde.org/attachment.cgi?id=126312=edit screenshot1 SUMMARY Face areas copied when rotating an image STEPS TO REPRODUCE 1. Open a picture 2. Set in preview an face tag (screenshot 1) 3. press 4 times CTRL+SHIFT RIGHT to rotate picture (screenshot 2) OBSERVED RESULT tags are copied 3 or 4 times EXPECTED RESULT should not be copied SOFTWARE/OS VERSIONS I used the latest appimage of digikam (beta3 from 20200220) on opsensuse thumbleweed ADDITIONAL INFORMATION I'm useing digikam sinces some years and discover from release to release problems with the position of tagged faces. It is hard to create a reproducable example because I don't know whether it was an error with a earlier version (when the tag was created) or this one (when the tag was read). I'am pretty sure that there is/was an similar error with the postition face areas in combination with the oriantation of the picture. All the positions from my older, tagged pictures (2017/2018/2019); taken from my mobile phone in potrait mode seems to rotated by 90° with that release. Maybe in combination of rotating meta data? Tags are not copied, seems to be moved by 90° Do you know something that goes into that direction in the past? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418060] New: lubuntu 18.10 upgrade - chromium install with Discover
https://bugs.kde.org/show_bug.cgi?id=418060 Bug ID: 418060 Summary: lubuntu 18.10 upgrade - chromium install with Discover Product: Discover Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: martepocoa...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-25-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: On another apps while Discover was working on download to install an Chromium add-on. From 20 days ago, Discover shows an error on trying actualize, and from 5 days ago, on console (sudo su) apt-get update, apt-get upgrade, nor apt update, doesn't work also. Searching the web I see this LTS version isn't supported, but the 19 version isn't LTS. Thanks, very good and hard job. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6bca982c80 (LWP 15633))] Thread 12 (Thread 0x7f6b8a5ee700 (LWP 15706)): #0 0x7ffd0a9b8b14 in clock_gettime () #1 0x7f6bcfe1b9f6 in __GI___clock_gettime (clock_id=1, tp=0x7f6b8a5edaf0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f6bd0325a81 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f6bd03242b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6bd03248b5 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6bd032653c in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6bcdd5e499 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f6bcdd5ee9b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f6bcdd5f08c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f6bd032615b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f6bd02d316b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f6bd01220b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f6bd012bc87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f6bceeb4164 in start_thread (arg=) at pthread_create.c:486 #14 0x7f6bcfe0cdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f6b8bfff700 (LWP 15673)): #0 0x7ffd0a9b8b14 in clock_gettime () #1 0x7f6bcfe1b9f6 in __GI___clock_gettime (clock_id=1, tp=0x7f6b8bffeaf0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f6bd0325a81 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f6bd03242b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6bd03248b5 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6bd032653c in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6bcdd5e499 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f6bcdd5ee9b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f6bcdd5f08c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f6bd032615b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f6bd02d316b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f6bd01220b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f6bd012bc87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f6bceeb4164 in start_thread (arg=) at pthread_create.c:486 #14 0x7f6bcfe0cdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f6ba6878700 (LWP 15664)): #0 0x7f6bcdda4293 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6bcdd5ea3f in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6bcdd5ef10 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6bcdd5f08c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6bd032615b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6bd02d316b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6bd01220b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6bd012bc87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6bceeb4164 in start_thread (arg=) at
[plasmashell] [Bug 418059] Plasma crashes while searching for program
https://bugs.kde.org/show_bug.cgi?id=418059 --- Comment #1 from etnguyen03+kdeb...@gmail.com --- Created attachment 126311 --> https://bugs.kde.org/attachment.cgi?id=126311=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418059] New: Plasma crashes while searching for program
https://bugs.kde.org/show_bug.cgi?id=418059 Bug ID: 418059 Summary: Plasma crashes while searching for program Product: plasmashell Version: 5.18.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: etnguyen03+kdeb...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.1) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.5-arch1-1 x86_64 Windowing system: X11 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I was trying to search for "VMware Workstation" in the Plasma application launcher but a few letters in (like when I reached the 'w' in VMware) Plasma crashed. -- Backtrace (Reduced): #6 0x7f5b4312d99e in QV4::QObjectWrapper::wrap(QV4::ExecutionEngine*, QObject*) () at /usr/lib/libQt5Qml.so.5 #7 0x7f5b431247ac in QV4::ExecutionEngine::fromVariant(QVariant const&) () at /usr/lib/libQt5Qml.so.5 #8 0x7f5b431ae3f3 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f5b431cf1bf in () at /usr/lib/libQt5Qml.so.5 #10 0x7f5b431d44df in () at /usr/lib/libQt5Qml.so.5 The reporter indicates this bug may be a duplicate of or related to bug 414920, bug 413400, bug 413170. Possible duplicates by query: bug 417975, bug 416933, bug 416215, bug 415831, bug 415433. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #26 from Recesvintvs --- I forgot to say that all those steps were done starting anew, in a deleted user data "virgin" session. No traces of former intents or configurations. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 418000] Music album photo pop-ups are too big
https://bugs.kde.org/show_bug.cgi?id=418000 Nate Graham changed: What|Removed |Added Resolution|DOWNSTREAM |--- CC||mp...@kde.org Component|general |general Product|kde |juk Status|RESOLVED|REPORTED Assignee|unassigned-b...@kde.org |whee...@kde.org --- Comment #5 from Nate Graham --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #25 from Recesvintvs --- Created attachment 126310 --> https://bugs.kde.org/attachment.cgi?id=126310=edit Output for "latte-dock -d" I'll write a brief description: - Latte launchedfrom Konsole with "latte-dock -d" - I created one new layout, Latte crashed and restarted automatically. - Then I reopened the config dialog and asigned that layout to one activity, applied and closed (I believe). - I switched to the 2nd activity to place the dock at the left border for clear distinction. - Switched back to the default activity, entered the configuration window again and shared the default layout with the 2nd activity so the default layout, with its dock in the inferior central part of the screen ir common to both activities. Clicked the Apply button. And then the issue appeared and I saw how the dock for this activity was duplicated and in the 2nd activity only was the original panel I had put to the left, but no dock at the botton border from the default layout. I stopped doing anything related to Latte and copypasted the output. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418022] Difficulty in organizing tags if tags not visible in tag manager window
https://bugs.kde.org/show_bug.cgi?id=418022 --- Comment #2 from Maik Qualmann --- See fixed Bug 413985. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418022] Difficulty in organizing tags if tags not visible in tag manager window
https://bugs.kde.org/show_bug.cgi?id=418022 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||7.0.0 Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 417886] Sharing layouts dont work
https://bugs.kde.org/show_bug.cgi?id=417886 --- Comment #24 from Recesvintvs --- Launching Latte from Konsole throwed a lot of output and very rapidly, so I lost the track to the point where the issues apeared for the first time. Besides I think that my Konsole window hasn't retained all the output lines, so I'm attaching all the content of Konsole's window that I've been able to copy and paste. I hope it's enough, in case contrary, please tell me how can I save more content than the one that Konsole keeps in its buffer. I'm no expert of the command line at all, I'm afraid. Besides, I have not any file called "lattedock". Here is the permissions info of all the files and folders in my .config directory that contain "latte". I hope it serves: ls -la ~/.config | grep latte drwxr-xr-x 1 pruebas pruebas 274 feb 22 21:53 latte -rw--- 1 pruebas pruebas 1203 feb 22 21:53 lattedock.copy1.bak -rw--- 1 pruebas pruebas 1203 feb 22 21:53 lattedock.copy2.bak -rw-r--r-- 1 pruebas pruebas 1444 feb 22 21:53 lattedock.layout.bak -rw--- 1 pruebas pruebas 381 feb 22 21:53 lattedockrc -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418057] icons missing in xubuntu
https://bugs.kde.org/show_bug.cgi?id=418057 --- Comment #3 from Maik Qualmann --- Look in the digiKam settings under Miscellaneous-> Appearance. And select the Breeze Icon theme, either Breeze for a light color theme or Breeze-Dark for a dark one. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418056] not possible to filter for "no labels"
https://bugs.kde.org/show_bug.cgi?id=418056 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.0.0 Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418056] not possible to filter for "no labels"
https://bugs.kde.org/show_bug.cgi?id=418056 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Created attachment 126309 --> https://bugs.kde.org/attachment.cgi?id=126309=edit No rating No rating can be filtered either, see screenshot. Just like no color/pick label. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418057] icons missing in xubuntu
https://bugs.kde.org/show_bug.cgi?id=418057 --- Comment #2 from kisha --- (In reply to Maik Qualmann from comment #1) > You have to install the Breeze Icon package. > > Maik you mean breeze-icon-theme ? Thats unfortunately not working either -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 418000] Music album photo pop-ups are too big
https://bugs.kde.org/show_bug.cgi?id=418000 --- Comment #4 from David --- Created attachment 126308 --> https://bugs.kde.org/attachment.cgi?id=126308=edit big_juk_pop_up Added a screenshot illustrating the issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 418017] Okular does not play sound of an embedded media file
https://bugs.kde.org/show_bug.cgi?id=418017 --- Comment #3 from Alexander Willamowski --- Hi Oliver, thanks for your quick response! The one that can be downloaded from the Fedora Software App Store (Okular version 1.9.2) has the issue. I don't understand why it has a complete other versioning than the one which can be downloaded directly through DNF (19.08.3-1.fc31) and the homepage of Okular. However, the first one has the audio issue. Here are some more details about the codec that comes with the MOV file: VLC reports that the MOV file contains a MPEG H264 - MPEG-4 AVC (part10)(avc1) MPEG ACC Audio stream, Stereo 44100 Hz 32 Bit/sample Okular version 19.08.3 does support the above mentioned audio stream. However, when I use this, something other strange happens to my file system which I might report through another bug ticket. This issue concerns me a bit more and this is why I refuse use version 19.08.3 available from DNF repos for now. Thanks for your support! Okular is great reader tool! I do love it! Regards, Alexander -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418057] icons missing in xubuntu
https://bugs.kde.org/show_bug.cgi?id=418057 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- You have to install the Breeze Icon package. Maik -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 116482] metakit: akregator crashes at startup
https://bugs.kde.org/show_bug.cgi?id=116482 kmi changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|1 |0 CC||kamika...@web.de Platform|Kubuntu Packages|unspecified Status|RESOLVED|REPORTED --- Comment #282 from kmi --- Hardly any commits in https://github.com/KDE/akregator/commits/master/plugins/mk4storage over a few years. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418058] New: discover exits the program
https://bugs.kde.org/show_bug.cgi?id=418058 Bug ID: 418058 Summary: discover exits the program Product: Discover Version: 5.15.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: gregori...@yahoo.com.ar CC: aleix...@kde.org Target Milestone: --- E: Splitting of clearsigned file /var/lib/apt/lists/ar.archive.ubuntu.com_ubuntu_dists_disco-updates_InRelease failed as it doesn't contain all expected parts -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418057] New: icons missing in xubuntu
https://bugs.kde.org/show_bug.cgi?id=418057 Bug ID: 418057 Summary: icons missing in xubuntu Product: digikam Version: 6.3.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-IconView Assignee: digikam-bugs-n...@kde.org Reporter: kdeb...@malevil.cc Target Milestone: --- Created attachment 126307 --> https://bugs.kde.org/attachment.cgi?id=126307=edit icons I installed digikam on xubuntu 18.04 from the repositories (apt install digikam). It works great, but some icons are missing as you can see in the attachment. I guess these are kde icons that are missing in xubuntu, right? How can i add them? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418056] not possible to filter for "no labels"
https://bugs.kde.org/show_bug.cgi?id=418056 kisha changed: What|Removed |Added Summary|not possible to filter for |not possible to filter for |no ratings etc. |"no labels" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418056] New: not possible to filter for no ratings etc.
https://bugs.kde.org/show_bug.cgi?id=418056 Bug ID: 418056 Summary: not possible to filter for no ratings etc. Product: digikam Version: 6.3.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-Filters Assignee: digikam-bugs-n...@kde.org Reporter: kdeb...@malevil.cc Target Milestone: --- You can choose to filter for "images without tags" but there is no options to filter for "images without rating", same is for "without pick/colors" -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 116482] metakit: akregator crashes at startup
https://bugs.kde.org/show_bug.cgi?id=116482 --- Comment #281 from Nicolás Alvarez --- Why did you mark this as fixed, rubi ortiz? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418055] New: Change imported Photoshop Brush color
https://bugs.kde.org/show_bug.cgi?id=418055 Bug ID: 418055 Summary: Change imported Photoshop Brush color Product: krita Version: 4.2.8 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: cyberlumi...@protonmail.com Target Milestone: --- SUMMARY I'm using an imported Photoshop brush (.ABR) and I'm trying to change the color of the brush image. I select the layer, click on the color picker and try to change it, but the color stays the same. STEPS TO REPRODUCE 1. Import brush 2. Use brush 3. Select layer with brush on it, choose color picker and click black. The color does not change OBSERVED RESULT Color stays the same EXPECTED RESULT The color changes to black SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Thanks -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418054] New: Arab filenames not showed correctly
https://bugs.kde.org/show_bug.cgi?id=418054 Bug ID: 418054 Summary: Arab filenames not showed correctly Product: dolphin Version: 18.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: rafael.linux.u...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 126306 --> https://bugs.kde.org/attachment.cgi?id=126306=edit The name is not correctly showed SUMMARY I have several filenames in arab language. However, Dolphin is not respecting my local filename name convention. That's, instead of show filename as "filename.extension", Dolphin is showing in the filename of those files a strange mixture of the name and the extension. STEPS TO REPRODUCE 1. Create some filenames with arab language characters and a extension OBSERVED RESULT Filename not correctly showed EXPECTED RESULT Respect local filename composition when showing filename SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse 15.1 KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 388966] Enabling "Search" plugin freezes KTorrent application
https://bugs.kde.org/show_bug.cgi?id=388966 H.H. changed: What|Removed |Added CC||cyberb...@gmx.de --- Comment #16 from H.H. --- I can confirm this. When will a fix be released? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418010] New Payee not added autoamtically
https://bugs.kde.org/show_bug.cgi?id=418010 Thomas Baumgart changed: What|Removed |Added Resolution|NOT A BUG |WAITINGFORINFO --- Comment #7 from Thomas Baumgart --- Not sure if it is not a bug (on Windows). Bert, can you check what happens if you do the following (on Windows) and report back here: a) Start a new transaction b) create a new payee until you get the dialog in question c) Mark the 'Do not ask again' checkbox d) Press the 'No' button e) Cancel the transaction edit f) Repeat a) and b) and check that the dialog shows up Thanks in advance. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418053] New: Discover applet not available in system tray or Configure System Tray option
https://bugs.kde.org/show_bug.cgi?id=418053 Bug ID: 418053 Summary: Discover applet not available in system tray or Configure System Tray option Product: Discover Version: 5.18.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: b...@briandwright.com CC: aleix...@kde.org Target Milestone: --- SUMMARY After upgrading to KDE LTS 5.18, the Discover applet is not visible in the taskbar. The applet is not visible when tested with multiple user accounts. STEPS TO REPRODUCE 1. sudo apt purge --autoremove plasma-discover 2. sudo apt install plasma-discover OBSERVED RESULT The applet will not appear in the system stray, nor available in the Configure System Tray option EXPECTED RESULT Discover applet should appear and present notifications SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon Plasma LTS 5.18 (available in About System) KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION No metadata file seems to exist for Discover in /usr/share/plasma/plasmoids. KDE Plasma 5.18.1 not available in LTS repositories? -- You are receiving this mail because: You are watching all bug changes.
