[lattedock] [Bug 413461] Latte-dock is badly positioned on Debian Wayland
https://bugs.kde.org/show_bug.cgi?id=413461 --- Comment #3 from Michail Vourlakos --- 5. Send also your env ourput -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413464] New: Crash in Windows 10 when 'browsing' images before initial 'import' complete
https://bugs.kde.org/show_bug.cgi?id=413464 Bug ID: 413464 Summary: Crash in Windows 10 when 'browsing' images before initial 'import' complete Product: digikam Version: 6.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gl...@dazedowl.uk Target Milestone: --- SUMMARY Installed digiKam for first time and pointed to a collection of 35,000+ images (jpg and raw). Each time I selected a folder that I knew contained images, digiKam would lock up and then close/crash. This happened _every time_ I tried (ie 100% repro), until I noticed in the status bar that digiKam was still working through the collection of images for the first time (ie the process progress bar was present and slowly progressing). Once I realised this I left digiKam to complete this task (which took a long time of course). Once it was complete everything was fine and I experienced no further crashes. This was obviously user error, but of course a crash is still undesireable behaviour. Also some sort of message that digiKam is still working through the files would be helpful feedback for the user. This might be a common problem encountered by new users with an already extensive collection of images. (Apologies, I don't know which componenet to attribute this too) STEPS TO REPRODUCE 1. Install digiKam for first time use 2. In Collections setting point digiKam to a very large collection of images (in my case with date-based subfolders) 3. Whilst digiKam is still in the process of collecting these images, attempt to browse through the image folders OBSERVED RESULT digiKam locks up and crashes EXPECTED RESULT No crash. Perhaps a helpful message to usr to be more patient and bring their attention to the fact digiKam is still working at bringin the images into the db (r whatever it is doing at this point) SOFTWARE/OS VERSIONS Windows: Windows 10.0.18362 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413464] Crash in Windows 10 when 'browsing' images before initial 'import' complete
https://bugs.kde.org/show_bug.cgi?id=413464 --- Comment #1 from glenn --- Update (already): The crash is still happening for me, if I try browsing whilst 'Find New Items' is in progress. I have 'Scan For New Items At Start Up' selected and a related message is presented at each new start up, but it turns out that when that completes and digiKam proper opens, that Find New Item process is still running, and being a very large collection of images this takes a very long time. In otherwords, Find New Items At Start Up casuses instability and difficulty for the user when working with a large collection. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Holger changed: What|Removed |Added CC||hos...@hotmail.de --- Comment #34 from Holger --- Issue also existing in tumbleweed: Sync of calendar entries by means of caldav does not work. Desktop: Operating System: openSUSE Tumbleweed 20191023 KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.6-1-default OS Type: 64-bit Server: Ubuntu 18.04 bionic Nextcloud 17.0.0 both of the systems are up to date. Behavior: create an calendar entry in korganizer: entry is shown up in Nextcloud create an calendar entry in Nextcloud: entry not beeing shown in korganizer the only error message I was able to fetch was in akonadi console: org.kde.pim.akonadiserver: Error while handling command FetchItems on connection akonadi_davgroupware_resource_0 (0x559c914ecc00) your help would be very much appreciated. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 --- Comment #35 from Christophe Giboudeaux --- (In reply to Steffen Hartmann from comment #32) > Also a problem for me. Since the last update I can't sync to my nextcloud > server anymore. I don't understand the explanations but the behavior is just > as described in this bug report. > Make sure your distribution added this commit to the kio package: https://cgit.kde.org/kio.git/commit/?id=02a8d3 It will be part of the 5.64 release and is only needed if you're using kio 5.63.0. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 --- Comment #36 from Christophe Giboudeaux --- (In reply to Holger from comment #34) > Issue also existing in tumbleweed: > > Sync of calendar entries by means of caldav does not work. The fix is on the way to the factory repo. It may take a couple days before the request is accepted. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411927] Crash during initial scan
https://bugs.kde.org/show_bug.cgi?id=411927 Maik Qualmann changed: What|Removed |Added CC||gl...@dazedowl.uk --- Comment #9 from Maik Qualmann --- *** Bug 413464 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413464] Crash in Windows 10 when 'browsing' images before initial 'import' complete
https://bugs.kde.org/show_bug.cgi?id=413464 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 411927 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413464] Crash in Windows 10 when 'browsing' images before initial 'import' complete
https://bugs.kde.org/show_bug.cgi?id=413464 --- Comment #3 from Maik Qualmann --- You can use the pre-release version of digiKam-6.4.0: https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413464] Crash in Windows 10 when 'browsing' images before initial 'import' complete
https://bugs.kde.org/show_bug.cgi?id=413464 Maik Qualmann changed: What|Removed |Added Component|general |Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413464] Crash in Windows 10 when 'browsing' images before initial 'import' complete
https://bugs.kde.org/show_bug.cgi?id=413464 --- Comment #4 from glenn --- Maik, thanks -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 --- Comment #37 from Alexander Zhigalin --- (In reply to chp321 from comment #30) > I have this bug with server baikal, since version 19.08.2 > Sync addresses (cardDav) works fine, but calDav does no longer synchronize > with my baikal server. > I really do need this feature. > I will change for Evolution. I hope this bug will be solved very soon, > because I like KDE. Please note, those who only begin experiencing this problem recently (starting from from comment #30) are not actually experiencing this bug but rather an another one with similar result. Please don't close this as fixed because this issue has no fix yet. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 413465] New: Provide expense/income chart by payee
https://bugs.kde.org/show_bug.cgi?id=413465 Bug ID: 413465 Summary: Provide expense/income chart by payee Product: kmymoney Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: tbaumg...@kde.org Target Milestone: --- SUMMARY A simple example of what I'd like to achieve with such a chart would be groceries I buy at various discounters. The corresponding transactions all have the category 'groceries', and I'd like to see in the chart whether I have a bias to buy them at discounter A, B or C. As I said in the first post, the report "transactions->by payee" basically generates the relevant data (when filtered by category), and a pie chart with the name of the payee and the respective sum would make them just easier to grasp ADDITIONAL INFORMATION Original source: https://forum.kde.org/viewtopic.php?f=69&t=162888 -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 413039] Critical: could not load fallback mirror list from QUrl
https://bugs.kde.org/show_bug.cgi?id=413039 --- Comment #33 from Christoph Cullmann --- Actually, comparing file sizes is not important. Yes, the new installers are larger, in most parts due to spellcheckers/translations + e.g. icons. The important part is: they are kind of maintained. The nice 4.10.2 release from X years ago has security flaws like https://kde.org/info/security/advisory-20190807-1.txt (and that is just one inside our libs, not counting the stuff we bundled there) If you use e.g. Kate with the built-in file browser from that version, you might just get hi-jacked just by browsing e.g. your Downloads folder... I really think we shall not make it easy to install that stuff. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413466] New: akonadi displaying problems, I can't open applications e.g kontact, kmail etc.
https://bugs.kde.org/show_bug.cgi?id=413466 Bug ID: 413466 Summary: akonadi displaying problems, I can't open applications e.g kontact, kmail etc. Product: Akonadi Version: 5.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- Created attachment 123490 --> https://bugs.kde.org/attachment.cgi?id=123490&action=edit Akonadictl errors SUMMARY I can't open kmail, korganizer etc. If you look at the attached file, then there's lots of errors happening e.g. /usr/bin/akonadi_sendlater_agent: symbol lookup error: /usr/lib64/libKF5ContactEditor.so.5: undefined symbol: _ZN9KContacts9Addressee16staticMetaObjectE org.kde.pim.akonadicontrol: ProcessControl: Application '/usr/bin/akonadi_sendlater_agent' returned with exit code 127 (Unknown error) org.kde.pim.akonadicontrol: "/usr/bin/akonadi_sendlater_agent" crashed too often and will not be restarted! I've run akonadictl fsck and also vacuum, no errors reported. I completely reinstalled opensuse last week, so it's still relatively clean I think. No errors appear in journalctl, and I'm unsure where to look tbh. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT As above - kontact, kmail etc don't open. EXPECTED RESULT kontact, kmail opens correctly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW 20191023 (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 413467] New: Contact list in notification area would be good
https://bugs.kde.org/show_bug.cgi?id=413467 Bug ID: 413467 Summary: Contact list in notification area would be good Product: kopete Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Notifications Assignee: kopete-bugs-n...@kde.org Reporter: tnem...@free.fr Target Milestone: --- SUMMARY Hi dear kopete developpers. I often made the reflexion that it would be a big time saver to be able to click on a recipient contact directly from the notification area kopete icon. That would have the effect to directly open the conversation window for that contact instead of having to open the main window, double-click on the contact and the close the main window. Thank you in advance. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #63 from Andrei Ivnitskii --- Hi all! I upgraded my Kubuntu to 19.10 and... bug is over. KDE Plasma 5.16.5 Qt 5.12.4 Who use Kubuntu please check and confirm it. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413466] akonadi displaying problems, I can't open applications e.g kontact, kmail etc.
https://bugs.kde.org/show_bug.cgi?id=413466 Christophe Giboudeaux changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Christophe Giboudeaux --- Installation issue. Most likely caused by a wrong kcontacts package version. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413468] New: Kdenlive sometime crashed during video preview.
https://bugs.kde.org/show_bug.cgi?id=413468 Bug ID: 413468 Summary: Kdenlive sometime crashed during video preview. Product: kdenlive Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: desertcla...@yandex.com Target Milestone: --- SUMMARY While I was editing video for a project, Kdenlive sometimes crash during preview playback. Good thing is, I can recover back without losing much of my work. However, this crash is breaking my flow. STEPS TO REPRODUCE 1. Insert video, and start cutting or adding effect. 2. play the video to preview the effects. 3. kdenlive crash (force close) without any prompt. SOFTWARE/OS VERSIONS Linux: Ubuntu 18.04.3 LTS DE: Gnome 3.28.2 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413466] akonadi displaying problems, I can't open applications e.g kontact, kmail etc.
https://bugs.kde.org/show_bug.cgi?id=413466 James Th changed: What|Removed |Added Resolution|DOWNSTREAM |WAITINGFORINFO --- Comment #2 from James Th --- is the wrong version of kcontacts able to stop kmail, korganizer, Akregator, and several other programs from starting, please? Also what should the correct version of kcontact be please? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413466] akonadi displaying problems, I can't open applications e.g kontact, kmail etc.
https://bugs.kde.org/show_bug.cgi?id=413466 --- Comment #3 from Christophe Giboudeaux --- Yes, if the symbols found at runtime don't match the ones used for building these applications, they won't start. the kcontacts version in openSUSE Tumbleweed is 5.63.0. If you still have 19.08.1, you need to downgrade the packages (zypper dup would have done that for you) So: check the libKF5Contacts5 version. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411538] Alphabetical selection matching ignores de-select
https://bugs.kde.org/show_bug.cgi?id=411538 Méven Car changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||19.12 Latest Commit||https://commits.kde.org/dol ||phin/a5ce798f282b6cf9e153bb ||a89f9caea0cec37da0 Status|CONFIRMED |RESOLVED --- Comment #4 from Méven Car --- Git commit a5ce798f282b6cf9e153bba89f9caea0cec37da0 by Méven Car. Committed on 26/10/2019 at 10:53. Pushed by meven into branch 'master'. When the selection is deselected, restart the keyboard search from the beginning Summary: FIXED-IN: 19.12 Test Plan: Open a directory with 3 files starting with the same letter. 1. Press this letter key twice 2. The second file is selected 3. Deselect the file with the mouse or using Esc 4. Wait 1 second 5. Press the same key again Before: The third file gets selected After: The first file get selected ctest Reviewers: #dolphin, elvisangelaccio, ngraham Reviewed By: #dolphin, elvisangelaccio, ngraham Subscribers: ngraham, kfm-devel Tags: #dolphin Differential Revision: https://phabricator.kde.org/D23716 M +2-0src/kitemviews/kitemlistcontroller.cpp M +16 -3src/kitemviews/private/kitemlistkeyboardsearchmanager.cpp M +3-0src/kitemviews/private/kitemlistkeyboardsearchmanager.h M +6-0src/tests/kitemlistcontrollertest.cpp M +11 -4src/tests/kitemlistkeyboardsearchmanagertest.cpp https://commits.kde.org/dolphin/a5ce798f282b6cf9e153bba89f9caea0cec37da0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413470] New: kdenlive crashes when editing a text clip
https://bugs.kde.org/show_bug.cgi?id=413470 Bug ID: 413470 Summary: kdenlive crashes when editing a text clip Product: kdenlive Version: 19.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: supp...@bb-services.co.za Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Load a project 2. Change a text clip 3. OBSERVED RESULT Application: Kdenlive (kdenlive), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f15c4f78e80 (LWP 3095))] Thread 37 (Thread 0x7f153a25c700 (LWP 3147)): #0 0x7f15c296fa7b in getpid () from /lib64/libc.so.6 #1 0x7f15be3989a3 in pa_detect_fork () from /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7f15c222decf in pa_stream_writable_size () from /lib64/libpulse.so.0 #3 0x7f158a6e358d in ?? () from /lib64/libSDL2-2.0.so.0 #4 0x7f158a63560e in ?? () from /lib64/libSDL2-2.0.so.0 #5 0x7f158a6850b0 in ?? () from /lib64/libSDL2-2.0.so.0 #6 0x7f158a70132d in ?? () from /lib64/libSDL2-2.0.so.0 #7 0x7f15c21d64c0 in start_thread () from /lib64/libpthread.so.0 #8 0x7f15c29a2553 in clone () from /lib64/libc.so.6 Thread 36 (Thread 0x7f1519045700 (LWP 3146)): #0 0x7f15c21dc3c5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f15c4d90e3b in ?? () from /lib64/libmlt.so.6 #2 0x55e4225b2771 in RenderThread::run() () #3 0x7f15c2e934e6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #4 0x7f15c21d64c0 in start_thread () from /lib64/libpthread.so.0 #5 0x7f15c29a2553 in clone () from /lib64/libc.so.6 Thread 35 (Thread 0x7f1539a5b700 (LWP 3145)): #0 0x7f15c21dc3c5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f158b23bb49 in ?? () from /usr/lib64/mlt/libmltsdl2.so #2 0x7f15c21d64c0 in start_thread () from /lib64/libpthread.so.0 #3 0x7f15c29a2553 in clone () from /lib64/libc.so.6 Thread 34 (Thread 0x7f153a29d700 (LWP 3144)): #0 0x7f15c299359c in read () from /lib64/libc.so.6 #1 0x7f15be3a9205 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7f15c2224dc6 in pa_mainloop_prepare () from /lib64/libpulse.so.0 #3 0x7f15c2225864 in pa_mainloop_iterate () from /lib64/libpulse.so.0 #4 0x7f15c2225920 in pa_mainloop_run () from /lib64/libpulse.so.0 #5 0x7f158a6e3703 in ?? () from /lib64/libSDL2-2.0.so.0 #6 0x7f158a6850b0 in ?? () from /lib64/libSDL2-2.0.so.0 #7 0x7f158a70132d in ?? () from /lib64/libSDL2-2.0.so.0 #8 0x7f15c21d64c0 in start_thread () from /lib64/libpthread.so.0 #9 0x7f15c29a2553 in clone () from /lib64/libc.so.6 Thread 33 (Thread 0x7f154d895700 (LWP 3135)): #0 0x7f15c2997ae7 in poll () from /lib64/libc.so.6 #1 0x7f15c2233ce6 in ?? () from /lib64/libpulse.so.0 #2 0x7f15c22251f1 in pa_mainloop_poll () from /lib64/libpulse.so.0 #3 0x7f15c2225873 in pa_mainloop_iterate () from /lib64/libpulse.so.0 #4 0x7f15c2225920 in pa_mainloop_run () from /lib64/libpulse.so.0 #5 0x7f15c2233c2d in ?? () from /lib64/libpulse.so.0 #6 0x7f15be3d8d1c in ?? () from /usr/lib64/pulseaudio/libpulsecommon-12.2.so #7 0x7f15c21d64c0 in start_thread () from /lib64/libpthread.so.0 #8 0x7f15c29a2553 in clone () from /lib64/libc.so.6 Thread 32 (Thread 0x7f154be5d700 (LWP 3131)): [KCrash Handler] #6 0x55e43290aa60 in ?? () #7 0x7f15c4525ad6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #8 0x7f15c452f150 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #9 0x7f15c303ade8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #10 0x7f15c303dd8b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #11 0x7f15c308ff27 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #12 0x7f15be585ecd in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #13 0x7f15be586260 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #14 0x7f15be586303 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #15 0x7f15c308fcb5 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #16 0x7f15c3039ceb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #17 0x7f15c2e92395 in QThread::exec() () from /lib64/libQt5Core.so.5 #18 0x7f15c4027e7a in QQuickPixmapReader::run() () from /lib64/libQt5Quick.so.5 #19 0x7f15c2e934e6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #20 0x7f15c21d64c0 in start_thread () from /lib64/libpthread.so.0 #21 0x7f15c29a2553 in clone () from /lib64/libc.
[kdenlive] [Bug 413469] New: Fit Zoom to Project do not change zoom level
https://bugs.kde.org/show_bug.cgi?id=413469 Bug ID: 413469 Summary: Fit Zoom to Project do not change zoom level Product: kdenlive Version: 19.08.2 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: pierre.ner...@free.fr Target Milestone: --- SUMMARY I would expect that menu or button "Fit Zoom to Project" would change the zoom level accordingly. STEPS TO REPRODUCE 1. Zoom to any part of a project with either middle mouse button, either zoom slider at the bottom right 2. Menu "Fit Zoom to Project" or button 3. The slider Zoom do not change, then the middle button of the mouse do not zoom as expected with the view but according to the current position of the zoom slider OBSERVED RESULT The slider Zoom do not change EXPECTED RESULT The zoom slider should change to match the part of the project displayed. SOFTWARE/OS VERSIONS kdenlive-19.08.2b-x86_64.appimage ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413470] kdenlive crashes when editing a text clip
https://bugs.kde.org/show_bug.cgi?id=413470 --- Comment #1 from Leon --- SOFTWARE/OS VERSIONS Fedora 30 - 5.3.7-200.fc30.x86_64 Linux/KDE Plasma: KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 392635] Compile error on KDE Neon 5.12: cannot convert ‘const wchar_t*’ to ‘TagLib::FileName
https://bugs.kde.org/show_bug.cgi?id=392635 Serhiy Zahoriya changed: What|Removed |Added Ever confirmed|0 |1 CC||serhiy@gmail.com Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 392635] Compile error on KDE Neon 5.12: cannot convert ‘const wchar_t*’ to ‘TagLib::FileName
https://bugs.kde.org/show_bug.cgi?id=392635 --- Comment #3 from Serhiy Zahoriya --- If you want to get rid of this message you can remove L before "wchar". But I'm not sure it's safe because on a freshly-installed Lubuntu 19.10 Amarok does not compile with this and two other errors: 1. Somehow not seeing pthread_create 2. MySQL test failing -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395392] Dolphin doesn’t use locale settings for displaying the number of files
https://bugs.kde.org/show_bug.cgi?id=395392 Karl Ove Hufthammer changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://phabricator.kde.org ||/R249:b0dbb285bd2119fe980a7 ||14f7d01ec140f2b8138 --- Comment #3 from Karl Ove Hufthammer --- This bug seems to be fixed by this commit to ki18n: https://phabricator.kde.org/R249:b0dbb285bd2119fe980a714f7d01ec140f2b8138 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 168134] Locale settings are not correctly used for displaying numbers
https://bugs.kde.org/show_bug.cgi?id=168134 Karl Ove Hufthammer changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #8 from Karl Ove Hufthammer --- Fixed by this commit to ki18n: https://phabricator.kde.org/R249:b0dbb285bd2119fe980a714f7d01ec140f2b8138 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413466] akonadi displaying problems, I can't open applications e.g kontact, kmail etc.
https://bugs.kde.org/show_bug.cgi?id=413466 --- Comment #4 from James Th --- Thank you so much - you were correct. I had a look at my repos, and for some unknown reason I had a Leap repo enabled and active, in my TW distro. I disabled that, and it downgraded the kontact versions, when I did a zypper dup! Thanks again, you saved me a complete headache today! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413304] Chinese characters instead of Polish diacritical marks
https://bugs.kde.org/show_bug.cgi?id=413304 Dave Gilbert changed: What|Removed |Added CC||gilbertd+...@treblig.org --- Comment #13 from Dave Gilbert --- Created attachment 123491 --> https://bugs.kde.org/attachment.cgi?id=123491&action=edit broken rendering in okular Happening for me; Fedora 31 - packaged okular 1.7.3 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413471] New: Picture of the day not available
https://bugs.kde.org/show_bug.cgi?id=413471 Bug ID: 413471 Summary: Picture of the day not available Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: l...@gmx.ch CC: bhus...@gmail.com Target Milestone: --- I would like to use the Bing picture of the day as a background image on the lock screen. In the dialog where you can configure the lockscreen background, there is a dropdown available allowing to select the 'Picture of the day' provider. But when I do so, there is no provider list shown. There is a Text field which says something like: Choose Provider, but there is no pull-down shown by the side. For the moment I would already be happy to know how to configure it manually in the relevant configuration file. I am on the latest released version of Plasma. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411980] Wayland session crashes after I change some settings in system settings
https://bugs.kde.org/show_bug.cgi?id=411980 --- Comment #7 from Roman Gilg --- I have a patch created: https://phabricator.kde.org/D24954 The patch is quite large but I still intend it to put it into 5.17.2 if I can get some feedback from people over the weekend that can compile KWin with the patch and it works on their systems and no other regressions happen. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 180107] smb:// cannot browse other ports
https://bugs.kde.org/show_bug.cgi?id=180107 Petr Berestov changed: What|Removed |Added CC||berest...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 180107] smb:// cannot browse other ports
https://bugs.kde.org/show_bug.cgi?id=180107 Petr Berestov changed: What|Removed |Added Assignee|plasma-b...@kde.org |berest...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413466] akonadi displaying problems, I can't open applications e.g kontact, kmail etc.
https://bugs.kde.org/show_bug.cgi?id=413466 Christophe Giboudeaux changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 413472] New: GMail accounts not working in KMail
https://bugs.kde.org/show_bug.cgi?id=413472 Bug ID: 413472 Summary: GMail accounts not working in KMail Product: kmail2 Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: enautge...@gmail.com Target Milestone: --- SUMMARY When trying to add a new Gmail account, google accounts denies the "Akonadi Resources for Google Services", because it is not verified as a compatible app for working with "Access with Google" STEPS TO REPRODUCE 1. Download KMail 2. Select "add account", fill in with the email and password and click next. 3. The account wizard will find the config online, and it will select the gmail config 4. Press add account, and a pop up will appear, in which you may log in to your google account in order to connect Akonadi Services For Google Services with your google account. 5. After the log in, there is the error, saying that the app is not compatible yet with google accounts. OBSERVED RESULT When syncing gmail and "Akonadi Resources for Google Services" (when the "add account" button is pressed), an error pop ups saying "Akonadi Resources for Google Services" is not verified yet to work with "Access with Google" EXPECTED RESULT Log in and sync emails without problems. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.17.1 (available in About System) KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 KMail version: 19.08.2 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 383682] kstars 2.8.1 crash after click 'Settings-Geographic' and 1 hour error in korea
https://bugs.kde.org/show_bug.cgi?id=383682 Shinjo Park changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Shinjo Park --- Closed again per bug #291203. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412276] no root access from normal user login using plasma 5.16.90
https://bugs.kde.org/show_bug.cgi?id=412276 olignomi changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from olignomi --- I reported all the info requested within the given time. see comment 4 and 5. If more detailed info is needed, specify it please. Due to my own investigation, at least I solved the issue on my system. see comment 5. If you are happy with this - close the reported. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412276] no root access from normal user login using plasma 5.16.90
https://bugs.kde.org/show_bug.cgi?id=412276 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #9 from David Edmundson --- I don't think there's anything we can do. There's nothing that suggests plasma is at fault given it worked after removing some other files. Obviously if you find something, please reopen -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 411259] Preview opens scripts as binary files
https://bugs.kde.org/show_bug.cgi?id=411259 --- Comment #3 from Chris --- (In reply to Méven Car from comment #2) > I don't reproduce it with the file ark-19.08.0.tar.xz found at > https://download.kde.org/stable/applications/19.08.0/src/ark-19.08.0.tar.xz > > Previewing file Messages.sh inside works at expected. > > Operating System: Kubuntu 19.10 > KDE Plasma Version: 5.17.80 > KDE Frameworks Version: 5.64.0 > Qt Version: 5.12.4 > > Does the issue still reproduce with a more recent version of KDE Frameworks > and/or ark ? Operating System: Slackware64-current KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 4.19.80 Ark Version: 19.08.2 I can still reproduce With the above. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 Erasmo Caponio changed: What|Removed |Added CC||erasmocapo...@tiscali.it --- Comment #8 from Erasmo Caponio --- Same problem here. I am running kde neon user edition, plasma version 5.17.1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 411417] akonadi server won't start
https://bugs.kde.org/show_bug.cgi?id=411417 Erasmo Caponio changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Erasmo Caponio --- *** This bug has been marked as a duplicate of bug 411093 *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 413473] New: Kile complains about failure and deletes file if one tries to overwrite an existing template.
https://bugs.kde.org/show_bug.cgi?id=413473 Bug ID: 413473 Summary: Kile complains about failure and deletes file if one tries to overwrite an existing template. Product: kile Version: 2.9.93 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: user interface Assignee: michel.lud...@kdemail.net Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 123492 --> https://bugs.kde.org/attachment.cgi?id=123492&action=edit Screenshot of the error message. SUMMARY If we try to overwrite (through File > Create template from document) a previously created user template, Kile claims that creation failed and then deletes the file the user used to create the template. However, the template modification actually succeeds. STEPS TO REPRODUCE 1. Create a template. 2. Create a new .tex document using this template and make some changes in it. 3. File > Create template from document. 4. Choose to overwrite the existing template. OBSERVED RESULT Kile throws up an error saying 'failed to create template' (see attached screenshot). Once we dismiss the error, it then complains that the file has been deleted by another program. However, if we check the modified template by creating a new document, we find that the changes we made have actually been applied to the template, contrary to what the error message claimed. EXPECTED RESULT Kile should not falsely claim template creation failed. It should also not delete the document the user used to create the template. SOFTWARE/OS VERSIONS Linus distro: Arch Linux KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION If we try to create a new template (using a previously nonexistent template name), it succeeds and does not delete the document used, as expected. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 --- Comment #9 from Erasmo Caponio --- *** Bug 411417 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 411608] Color scheme configuration lacks a setting for the grid in agenda view
https://bugs.kde.org/show_bug.cgi?id=411608 Allen Winter changed: What|Removed |Added CC||win...@kde.org --- Comment #2 from Allen Winter --- just to be clear I understand this request. You are asking that the Korganizer configuration dialog=>Colors and Fonts should offer a setting for "Agenda view grid color" right? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 413474] New: Crash when adding variable into swap file name
https://bugs.kde.org/show_bug.cgi?id=413474
Bug ID: 413474
Summary: Crash when adding variable into swap file name
Product: kate
Version: 19.08.2
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: sgd.or...@gmail.com
Target Milestone: ---
Created attachment 123493
--> https://bugs.kde.org/attachment.cgi?id=123493&action=edit
Video example
SUMMARY
Kate crashed when adding variable to swap file name.
STEPS TO REPRODUCE
1. Start Kate
2. Go to > Menu > Settings > Configure Kate > [Editor Component] Open/Save >
Advanced
3. Make prefix or suffix inputs focused (click on them)
4. Click on the icon '{}' on the right side which shows when the input is
focused
5. Select something from the list which popped up (I did Date:Locale)
OBSERVED RESULT
Kate crashes.
EXPECTED RESULT
Kate runs.
SOFTWARE/OS VERSIONS
Operating System: Artix Linux
KDE Plasma Version: 5.17.1
KDE Frameworks Version: 5.63.0
Qt Version: 5.13.1
Kernel Version: 4.19.80-1-lts
OS Type: 64-bit
Processors: 2 × Intel® Pentium® CPU B980 @ 2.40GHz
Memory: 7,6 GiB of RAM
ADDITIONAL INFORMATION
See the video
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 413475] New: Dolphin detects wrong location for device if it is bind-mounted
https://bugs.kde.org/show_bug.cgi?id=413475 Bug ID: 413475 Summary: Dolphin detects wrong location for device if it is bind-mounted Product: dolphin Version: 19.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kishor...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I have a partition in which certain folders are bind-mounted to folders in my home directory. When I click this device in the dolphin sidebar, it opens one of the folders which have been bind-mounted, instead of the actual device. The directory structure is schematically as follows: /run/media/kishore/oldhome (mountpoint of the partition, which is named `Arch-home`) |- Documents |- some other directories `Documents` is bind-mounted to /home/kishore/Documents STEPS TO REPRODUCE: 1. Mount a partition (say 'Arch-home') which has multiple folders. 2. Bind-mount one of the folders (say 'Documents') to a folder in your home directory. 3. Click on the partition name in the 'devices' section of Dolphin's sidebar. OBSERVED RESULT When I click the item labelled 'Arch-home' in the dolphin sidebar (it appears under 'Devices'), I am taken to /home/kishore/Documents, instead of /run/media/kishore/oldhome (Note that the contents of these two locations are not the same, so it is not merely about displaying the right path in the addressbar.) EXPECTED RESULT Dolphin should correctly open the actual partition. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Bug 330563 is a similar bug, but for krusader. Relevant portion of fstab: #Old home. UUID=9ae18791-bede-41a9-904f-dbea4d3993da /run/media/kishore/oldhome ext4 defaults,rw,relatime,nofail 0 0 #Bind mounts for ~ /run/media/kishore/oldhome/kishore/Downloads/home/kishore/Downloads none defaults,bind,uid=1000,gid=1000,nofail0 0 /run/media/kishore/oldhome/kishore/Documents/home/kishore/Documents none defaults,bind,uid=1000,gid=1000,nofail0 0 /run/media/kishore/oldhome/kishore/Pictures /home/kishore/Pictures none defaults,bind,uid=1000,gid=1000,nofail0 0 /run/media/kishore/oldhome/kishore/build/home/kishore/build none defaults,bind,uid=1000,gid=1000,nofail0 0 Output of `mount -t ext4` ``` /dev/sda2 on / type ext4 (rw,relatime) /dev/sda3 on /home type ext4 (rw,relatime,data=ordered) /dev/sdb14 on /run/media/kishore/oldhome type ext4 (rw,relatime) /dev/sdb14 on /home/kishore/Documents type ext4 (rw,relatime) /dev/sdb14 on /home/kishore/Downloads type ext4 (rw,relatime) /dev/sdb14 on /home/kishore/Pictures type ext4 (rw,relatime) /dev/sdb14 on /home/kishore/build type ext4 (rw,relatime) ``` Output of `lsblk` ``` NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 111.8G 0 disk ├─sda18:10 512M 0 part ├─sda28:2050G 0 part / ├─sda38:30 49.3G 0 part /home └─sda48:4012G 0 part [SWAP] sdb 8:16 0 931.5G 0 disk ├─sdb18:17 0 500M 0 part /boot ├─sdb28:18 040M 0 part ├─sdb38:19 0 128M 0 part ├─sdb48:20 0 750M 0 part ├─sdb58:21 070G 0 part ├─sdb78:23 0 734.7G 0 part /run/media/kishore/Files ├─sdb12 8:28 0 8.4G 0 part ├─sdb13 8:29 035G 0 part ├─sdb14 8:30 070G 0 part /run/media/kishore/oldhome └─sdb16 259:0012G 0 part [SWAP] ``` If I type the actual mountpoint into the addressbar, it shows me the correct location as expected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413322] Plasma crashes after login
https://bugs.kde.org/show_bug.cgi?id=413322 Julian Leyh changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Julian Leyh --- Thanks to the comment in #opensuse-kde, the bug is fixed by deleting the folder ~/.cache/plasmashell/qmlcache -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 413476] New: Wayland/Pipewire segfault on connection
https://bugs.kde.org/show_bug.cgi?id=413476 Bug ID: 413476 Summary: Wayland/Pipewire segfault on connection Product: krfb Version: 19.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: t...@r.je Target Milestone: --- SUMMARY When a connection is received, Krfb crashes when using wayland/pw plugin. STEPS TO REPRODUCE 1. Run Krfb on Wayland 2. Try to connect with KRDC OBSERVED RESULT Krfb accepts the login, asks for authorisation and once authorisation is granted, Krfb crashes. Log as follows: $ krfb found plugin at "/usr/lib/qt/plugins/krfb/krfb_framebuffer_xcb.so" Loaded plugin with name "xcb" found plugin at "/usr/lib/qt/plugins/krfb/krfb_framebuffer_pw.so" Loaded plugin with name "pw" found plugin at "/usr/lib/qt/plugins/krfb/krfb_framebuffer_qt.so" Loaded plugin with name "qt" Using FrameBuffer: "pw" Initializing D-Bus connectivity with XDG Desktop Portal DBus session created: "/org/freedesktop/portal/desktop/request/1_49/krfb2951929398" Starting server. Listen port: 5900 Listen Address: "0.0.0.0" Password enabled: true Couldn't select sources for the screen-casting session about to start authentication found plugin at "/usr/lib/qt/plugins/krfb/krfb_events_x11.so" Loaded plugin with name "x11" found plugin at "/usr/lib/qt/plugins/krfb/krfb_events_xdp.so" Loaded plugin with name "xdp" Segmentation fault (core dumped) EXPECTED RESULT Linux/KDE Plasma: Arch / 5.17.1 (available in About System) KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: Qt5 5.13.1 Krfb version: 19.8.2 (not in the list above) ADDITIONAL INFORMATION It is very difficult to find documentation on what is required to get this working on wayland so I may be missing something. On the host, I have installed pipewire and started the service. The log says says "Couldn't select sources for the screen-casting session" which suggests I might be missing something. I am also running 2x 4k displays with a desktop resolution of 7680x2160 which may be a higher resolution that something in the stack supports. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 343190] Duplicates appear in translation memory
https://bugs.kde.org/show_bug.cgi?id=343190 Adrián Chaves (Gallaecio) changed: What|Removed |Added CC||adr...@chaves.io --- Comment #12 from Adrián Chaves (Gallaecio) --- So do we close this? Does this still happen? Is it normal for Lokalize to show entries from multiple translation memories? (I though it only showed those from the translation memory with a name that matches the name of the current project) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413477] New: "browse device" opens a text file
https://bugs.kde.org/show_bug.cgi?id=413477 Bug ID: 413477 Summary: "browse device" opens a text file Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: i501ed+cn6smcaeh3...@sharklasers.com Target Milestone: --- SUMMARY I have my device connected and it works except when I click "browse device" it opens a file in Gedit named something like ~/.cache/kioexec/krun/12345_0/unnamed. The "12345" can be any four or five digit number. The file is zero bytes. It is owned by the user I'm logged in as. The MIME type is text/plain. "ls -al" give the permissions -rw-r--r--. I'm running XFCE on Debian. My computer does have Dolphin browser but I do not know how to tell KDE Connect to use it. My mom is running Xubuntu and her computer opens Angrysearch when trying to browse her phone. "Send file" does work correctly. STEPS TO REPRODUCE 1. Successfully pair Debian with XFCE PC to Android phone 2. Click browse device in the KDE indicator in the notifications area OBSERVED RESULT It opens a text file named something like ~/.cache/kioexec/krun/12345_0/unnamed EXPECTED RESULT It opens a file manager which can browse the phone's file system. SOFTWARE/OS VERSIONS OS: Debian GNU/Linux bullseye/sid x86_64 Kernel: 5.2.0-3-amd64 Shell: zsh 5.7.1 desktop: Xfce window manager: Xfwm4 ADDITIONAL INFORMATION My mom has a similar problem on Xubuntu. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413478] New: Dolphin should not try to enter invalid gzip archive.
https://bugs.kde.org/show_bug.cgi?id=413478 Bug ID: 413478 Summary: Dolphin should not try to enter invalid gzip archive. Product: dolphin Version: 19.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kishor...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 123494 --> https://bugs.kde.org/attachment.cgi?id=123494&action=edit Screenshot showing the issue SUMMARY If we try to browse an invalid gzip archive by opening it in Dolphin, Dolphin correctly complains about 'invalid protocol', but then it actually updates the location in the location bar to show that we are inside the archive (see attached screenshot), while still showing the contents of the parent folder. STEPS TO REPRODUCE 1. Create an invalid gzip archive (run the command `touch text.gzip`) 2. Open this archive by single/double-clicking it (depends on your settings) OBSERVED RESULT Note that while the location in the location bar tells us we are inside the archive (/home/kishore/Downloads/test.gz), the main pane just shows the contents of the parent folder (/home/kishore/Downloads). EXPECTED RESULT When we click on an invalid archive which is detected as such by Dolphin, Dolphin should not actually enter it. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63 Qt Version: 5.13.1 ADDITIONAL INFORMATION 'Back' and 'Up' items in the 'Go' menu also do not work properly once Dolphin enters such an archive. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 343198] Alphabetic keys can no longer be used for filling in messages from TM
https://bugs.kde.org/show_bug.cgi?id=343198 Adrián Chaves (Gallaecio) changed: What|Removed |Added CC||adr...@chaves.io --- Comment #17 from Adrián Chaves (Gallaecio) --- Is this still happening? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 413479] New: problem w ads
https://bugs.kde.org/show_bug.cgi?id=413479 Bug ID: 413479 Summary: problem w ads Product: Falkon Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: now...@gmail.com Reporter: supp...@tigernassau.com Target Milestone: --- it is hanging, crashing, skipping content go to www.espn.com/nfl - hit scores - hangs go to www.zero-hedge.com - shows lots of ads - sometimes just adds not content- ads seem to reference doubleclick go to reddit.com/r/linux - listings get chopped off running falkon 3.1.0 latest on Fedora 30, latest on debian sid need ublock origin falkon becoming unusuable 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 302841] Additional parentheses at the end of strings finished in parentheses added from an alternative translation
https://bugs.kde.org/show_bug.cgi?id=302841 Adrián Chaves (Gallaecio) changed: What|Removed |Added Assignee|sha...@ukr.net |adr...@chaves.io -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413480] New: KDE crash on login when using wayland
https://bugs.kde.org/show_bug.cgi?id=413480 Bug ID: 413480 Summary: KDE crash on login when using wayland Product: plasmashell Version: 5.16.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: aals...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.12.5 Frameworks Version: 5.61.0 Operating System: Linux 5.3.6-300.fc31.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Login using wayland - Unusual behavior I noticed: When logging in with wayland a black screen appears and no response comes from the computer, I can only switch between tty (ctrl+alt+number). When not using wayland the os login without issue, when using wayland the page one (ctrl+alt+1) shows the login page, while page two (ctrl+alt+2) shows the black screen and sometimes I can shutdown the computer with logging in to tty3, but this is not always the case. The system is newly installed with nothing else installed from the standard fedora installation but steam and dota2. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f11039ced00 (LWP 5689))] Thread 30 (Thread 0x7f106affd700 (LWP 6221)): [KCrash Handler] #6 0x7f1107202625 in raise () from /lib64/libc.so.6 #7 0x7f11071eb8d9 in abort () from /lib64/libc.so.6 #8 0x7f1107610b1b in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #9 0x7f10f69219f4 in QtWaylandClient::QWaylandDisplay::checkError() const () from /lib64/libQt5WaylandClient.so.5 #10 0x7f10f6921c61 in QtWaylandClient::QWaylandDisplay::dispatchQueueWhile(wl_event_queue*, std::function, int) () from /lib64/libQt5WaylandClient.so.5 #11 0x7f10f6926323 in QtWaylandClient::QWaylandWindow::waitForFrameSync(int) () from /lib64/libQt5WaylandClient.so.5 #12 0x7f10f415c022 in QtWaylandClient::QWaylandGLContext::swapBuffers(QPlatformSurface*) () from /usr/lib64/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #13 0x7f1107bfa871 in QOpenGLContext::swapBuffers(QSurface*) () from /lib64/libQt5Gui.so.5 #14 0x7f11093f1661 in QSGRenderThread::syncAndRender() () from /lib64/libQt5Quick.so.5 #15 0x7f11093f53c8 in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #16 0x7f11076464e6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #17 0x7f1106ae14e2 in start_thread () from /lib64/libpthread.so.0 #18 0x7f11072c7643 in clone () from /lib64/libc.so.6 Thread 29 (Thread 0x7f106b7fe700 (LWP 6220)): #0 0x7f1106ae7d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f10eed19cab in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f10eed198bb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f1106ae14e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7f11072c7643 in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7f106bfff700 (LWP 6209)): #0 0x7f1106ae7d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f110764bff3 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #2 0x7f110764c081 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #3 0x7f11093f51b9 in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #4 0x7f11093f545d in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #5 0x7f11076464e6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #6 0x7f1106ae14e2 in start_thread () from /lib64/libpthread.so.0 #7 0x7f11072c7643 in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7f1070ad8700 (LWP 6208)): #0 0x7f1106ae7d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f10eed19cab in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f10eed198bb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f1106ae14e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7f11072c7643 in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f10858e9700 (LWP 6077)): #0 0x7f1105f44d1f in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #1 0x7f1105f456cb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f1105f458d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f1107842cd3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f11077ecceb in QEventLoop::exec(QFlags) () from /li
[plasmashell] [Bug 413481] New: plasmashell segfault on login
https://bugs.kde.org/show_bug.cgi?id=413481 Bug ID: 413481 Summary: plasmashell segfault on login Product: plasmashell Version: 5.17.0 Platform: Exherbo Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: ing...@exherbo.org Target Milestone: 1.0 Created attachment 123495 --> https://bugs.kde.org/attachment.cgi?id=123495&action=edit dmesg SUMMARY I cannot log in to KDE atm. dmesg shows a segfault. I'll attach a backtrace & the coredump STEPS TO REPRODUCE 1. Enter login & password 2. Press enter to login 3. plasmashell segfaults OBSERVED RESULT Plasmashell segfaults EXPECTED RESULT SOFTWARE/OS VERSIONS macOS: Linux/KDE Plasma: Latest linux kernel 5.3.7 (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION - X.org server 1.20.5 using modesetting driver - Intel haswell on-board graphics chip - Tested with 5.17.1, same error. BT is from 5.17.0 - I noticed this in dmesg: broken atomic modeset userspace detected, disabling atomic -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413481] plasmashell segfault on login
https://bugs.kde.org/show_bug.cgi?id=413481 --- Comment #1 from Ingmar Vanhassel --- Created attachment 123496 --> https://bugs.kde.org/attachment.cgi?id=123496&action=edit coredumpctl gdb 841 gdb coredump + BT -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413481] plasmashell segfault on login
https://bugs.kde.org/show_bug.cgi?id=413481 --- Comment #2 from Ingmar Vanhassel --- Coredump is available at http://dev.exherbo.org/~ingmar/logs/plasmashell/ At 4,4 MB it's to big to be uploaded here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 Ville Aakko changed: What|Removed |Added CC||ville.aa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 413482] New: Elisa does not add audio files in the playlist dialog
https://bugs.kde.org/show_bug.cgi?id=413482 Bug ID: 413482 Summary: Elisa does not add audio files in the playlist dialog Product: elisa Version: 0.4.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: valterm...@gmail.com Target Milestone: --- Created attachment 123497 --> https://bugs.kde.org/attachment.cgi?id=123497&action=edit playlist area with no playlist SUMMARY When trying to add an album in the playlist, or open a folder, from the album view, Elisa does nothing and show an icon for forbidden action (screeshot attached). It doesn't crash. STEPS TO REPRODUCE 1. Open Elisa (it scans the "music" folder) 2. Try to Add/Open/Replace an album 3. OBSERVED RESULT The command doesn't work and the playlist is "empty" EXPECTED RESULT It should add or replace a group of music files (album), but it doesn't add nor open the containing music folder. SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 Kernel Version: 5.0.0-32-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 31,4 GiB ADDITIONAL INFORMATION The default scanned folder, "Musica", is correct, and contains subfolders with albums inside. Note: Amarok works correctly, it opens and reads and play normally. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 411384] CTRL+RIGHT / CTRL+LEFT
https://bugs.kde.org/show_bug.cgi?id=411384 --- Comment #7 from Nickolay Platonov --- Any news on making the fix actually available for the masses? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413478] Dolphin should not try to enter invalid gzip archive.
https://bugs.kde.org/show_bug.cgi?id=413478 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Keywords||usability Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 413395] Spectacle breaks after xrandr --scale
https://bugs.kde.org/show_bug.cgi?id=413395 --- Comment #1 from Frederick Zhang --- After applying the patch from bug 385885 and scaling both of the 1080p monitors with xrandr --scale 2.0, Spectacle now works so it seems that this issue only happens when the monitors have different panning configurations in my setup. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 413474] Crash when adding variable into swap file name
https://bugs.kde.org/show_bug.cgi?id=413474 Juraj changed: What|Removed |Added Component|general |general Version|19.08.2 |5.63.0 Product|kate|frameworks-ktexteditor -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 413483] New: Leading space trimming produces broken multiline output
https://bugs.kde.org/show_bug.cgi?id=413483 Bug ID: 413483 Summary: Leading space trimming produces broken multiline output Product: cantor Version: 19.08 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sage-backend Assignee: cantor-b...@kde.org Reporter: aro...@archlinux.org Target Milestone: --- SUMMARY Trimming the leading spaces can sometime lead to corrupt output. Test: input 'x^2' in sage Expected output: 2 x Actual output: 2 x -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413444] Opening Photoshop file causes crash
https://bugs.kde.org/show_bug.cgi?id=413444 --- Comment #4 from Stephen Bennington --- Created attachment 123498 --> https://bugs.kde.org/attachment.cgi?id=123498&action=edit Photoshop image file Not sure if you received .PSD image so sending it again here. Had to reduce size as it was over 4000Kb. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413380] Compositor crash
https://bugs.kde.org/show_bug.cgi?id=413380 Kirill changed: What|Removed |Added CC||kiryaso...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 413484] New: Tablet device missing (Cintiq Pro 13 Touch Finger touch)
https://bugs.kde.org/show_bug.cgi?id=413484 Bug ID: 413484 Summary: Tablet device missing (Cintiq Pro 13 Touch Finger touch) Product: wacomtablet Version: 3.2.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: defresne.thie...@gmail.com Target Milestone: --- SUMMARY The device for Cintiq Pro 13 Touch is missing, it can be enabled by restarting Wacom Tablet service. STEPS TO REPRODUCE 1. Plug-in Cintiq Pro 13 2. Run `kcmshell5 kcm_wacomtablet` 3. The touch module of the tablet is missing in the drop-down `Select Tablet` SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION `~/.config/tabletdblocalrc` (culprit is *0353*): ``` [034F] layout=unknown model=unknown name=Wacom Cintiq Pro 13 Pen padbuttons=0 statusleds=0 touchring=false touchstripl=false touchstripr=false wheel=false [0353] layout=unknown model=unknown name=Wacom Cintiq Pro 13 Touch Finger touch padbuttons=0 statusleds=0 touchring=false touchstripl=false touchstripr=false wheel=false ``` -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 413474] Crash when adding variable into swap file name
https://bugs.kde.org/show_bug.cgi?id=413474 --- Comment #1 from Juraj --- Created attachment 123500 --> https://bugs.kde.org/attachment.cgi?id=123500&action=edit Backtrace from KDevelop with same crash I have KDevelop compiled from source, hope backtrace can help. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Maverick changed: What|Removed |Added CC||basi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 413474] Crash when adding variable into swap file name
https://bugs.kde.org/show_bug.cgi?id=413474 Juraj changed: What|Removed |Added Attachment #123500|0 |1 is obsolete|| --- Comment #2 from Juraj --- Created attachment 123501 --> https://bugs.kde.org/attachment.cgi?id=123501&action=edit Backtrace from KDevelop with same crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 343592] Desktop grid effect does not work with some custom shortcuts (Default: ctrl+F8)
https://bugs.kde.org/show_bug.cgi?id=343592 --- Comment #19 from Tom B --- This works fine in Wayland with one caveat: You can't assign keys that are already assigned. For example, assigning Meta+1 doesn't work until you first manually unassign the default behaviour "Activate Task Manager Entry 1". However, this does fix the problem: Meta+Shift+1, Meta+Shift+2, etc can now be assigned and used as intended. As long as you're on Wayland, X11 still seems broken. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411980] Wayland session crashes after I change some settings in system settings
https://bugs.kde.org/show_bug.cgi?id=411980 --- Comment #8 from Patrick Silva --- I tried to apply your patch on Arch Linux, but I got building failure :( /home/myusername/kwin/input.cpp: In lambda function: /home/myusername/kwin/input.cpp:1783:51: error: ‘keyboardKeyPressRequested’ is not a member of ‘KWayland::Server::FakeInputDevice’ 1783 | connect(device, &FakeInputDevice::keyboardKeyPressRequested, this, | ^ /home/myusername/kwin/input.cpp:1790:51: error: ‘keyboardKeyReleaseRequested’ is not a member of ‘KWayland::Server::FakeInputDevice’ 1790 | connect(device, &FakeInputDevice::keyboardKeyReleaseRequested, this, | ^~~ make[2]: *** [CMakeFiles/kwin.dir/build.make:628: CMakeFiles/kwin.dir/input.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:173: CMakeFiles/kwin.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Christian Boltz changed: What|Removed |Added CC||kde-b...@cboltz.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 413485] New: Crash when downloading files
https://bugs.kde.org/show_bug.cgi?id=413485 Bug ID: 413485 Summary: Crash when downloading files Product: frameworks-baloo Version: 5.63.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: kamika...@web.de Target Milestone: --- Application: baloo_file_extractor (5.63.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.6-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was downloading some audio files. The crash occured when the downloads were still in progress. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8b16a27800 (LWP 17124))] Thread 3 (Thread 0x7f8b0700 (LWP 17126)): #0 0x7f8b16f345a4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f8b16ee92a3 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8b16ee93cf in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8b1834e99b in QEventDispatcherGlib::processEvents (this=0x7f8b08000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8b182f70db in QEventLoop::exec (this=this@entry=0x7f8b0fffed70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f8b1812f021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f8b193694f6 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f8b181301a2 in QThreadPrivate::start (arg=0x7f8b193ebd80) at thread/qthread_unix.cpp:360 #8 0x7f8b17845f2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f8b17db74af in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f8b149c4700 (LWP 17125)): #0 0x7f8b17dacbdf in poll () from /lib64/libc.so.6 #1 0x7f8b16e87742 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f8b16e883fa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f8b14bd9f90 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f8b181301a2 in QThreadPrivate::start (arg=0x55b7893408b0) at thread/qthread_unix.cpp:360 #5 0x7f8b17845f2a in start_thread () from /lib64/libpthread.so.0 #6 0x7f8b17db74af in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f8b16a27800 (LWP 17124)): [KCrash Handler] #6 0x7f8b17cf40d1 in raise () from /lib64/libc.so.6 #7 0x7f8b17cdd55d in abort () from /lib64/libc.so.6 #8 0x7f8b17a086f3 in mdb_assert_fail (env=0x55b7893f0090, expr_txt=expr_txt@entry=0x7f8b17a0a04c "mp->mp_pgno != pgno", func=func@entry=0x7f8b17a0a988 <__func__.7286> "mdb_page_touch", line=line@entry=2433, file=0x7f8b17a0a010 "mdb.c") at mdb.c:1542 #9 0x7f8b179fea1a in mdb_page_touch (mc=mc@entry=0x7ffc80e99120) at mdb.c:2441 #10 0x7f8b179fef38 in mdb_page_search (mc=mc@entry=0x7ffc80e99120, key=0x55b7893f02e0, flags=flags@entry=1) at mdb.c:5657 #11 0x7f8b17a004a1 in mdb_cursor_touch (mc=mc@entry=0x7ffc80e99600) at mdb.c:6515 #12 0x7f8b17a035f5 in mdb_cursor_put (mc=mc@entry=0x7ffc80e99600, key=key@entry=0x7ffc80e999f0, data=data@entry=0x7ffc80e99a00, flags=flags@entry=0) at mdb.c:6657 #13 0x7f8b17a0644b in mdb_put (txn=0x55b7893f04d0, dbi=4, key=key@entry=0x7ffc80e999f0, data=data@entry=0x7ffc80e99a00, flags=flags@entry=0) at mdb.c:9022 #14 0x7f8b19417991 in Baloo::DocumentDB::put (this=this@entry=0x7ffc80e99b20, docId=, docId@entry=436339939647487488, list=...) at /usr/src/debug/baloo5-5.63.0-1.1.x86_64/src/engine/documentdb.cpp:79 #15 0x7f8b1944a0d0 in Baloo::WriteTransaction::replaceDocument (this=0x55b7893f0010, doc=..., operations=operations@entry=...) at /usr/src/debug/baloo5-5.63.0-1.1.x86_64/src/engine/writetransaction.cpp:210 #16 0x7f8b1943b372 in Baloo::Transaction::replaceDocument (this=0x55b7893f2960, doc=..., operations=...) at /usr/src/debug/baloo5-5.63.0-1.1.x86_64/src/engine/transaction.cpp:293 #17 0x55b78848baa5 in ?? () #18 0x55b78848d56b in ?? () #19 0x7f8b18330382 in QtPrivate::QSlotObjectBase::call (a=0x7ffc80e99fa0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #20 QSingleShotTimer::timerEvent (this=0x55b7893f01e0) at kernel/qtimer.cpp:318 #21 0x7f8b18323e85 in QObject::event (this=0x55b7893f01e0, e=) at kernel/qobject.cpp:1282 #22 0x7f8b18d2ac62 in QApplicationPrivate::notify_helper (this=this@entry=0x55b789318140, receiver=receiver@entry=0x55b7893f01e0, e=e@entry=0x7ffc80e9a2c0) at kernel/qapplication.cpp:3703 #23 0x7f8b18d341e0 in QApplication::notify (this=0x7ffc80e9a5a0, receiver=0x55b7893f01e0, e=0x7ffc80e9a2c0) at kernel/qapplication.cpp:3449 #24 0x7f8b182f8572 in QCoreApplicatio
[krita] [Bug 413486] New: Drawing becomes corrupted after resuming from sleep mode.
https://bugs.kde.org/show_bug.cgi?id=413486 Bug ID: 413486 Summary: Drawing becomes corrupted after resuming from sleep mode. Product: krita Version: 4.2.7.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: anon...@openmailbox.org Target Milestone: --- Created attachment 123502 --> https://bugs.kde.org/attachment.cgi?id=123502&action=edit Corrupted graphics after resuming from sleep mode. SUMMARY Drawing becomes corrupted after resuming from sleep mode. STEPS TO REPRODUCE 1. Open Krita 2. Draw 3. Enter sleep mode with Krita Open 4. Resume your session from sleep mode OBSERVED RESULT 5. Krita canvas is completely corrupted EXPECTED RESULT Krita canvas still looks as I left it SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE, Plasma 5.16.5 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION I'm using Nvidia Driver version 435 and I think it's related to it. I don't think it happens on Nouveau. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413486] Drawing becomes corrupted after resuming from sleep mode.
https://bugs.kde.org/show_bug.cgi?id=413486 --- Comment #1 from Mark Smith --- By the way, the canvas can be refreshed and fixed by disabling and enabling layers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413487] New: Kde battery monitor show the wrong number and it does not update ever
https://bugs.kde.org/show_bug.cgi?id=413487 Bug ID: 413487 Summary: Kde battery monitor show the wrong number and it does not update ever Product: plasmashell Version: 5.16.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: nighte...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The kde battery monitor does not refresh the remaining time. It stucks with the same value forever. STEPS TO REPRODUCE 1. Boot the Kde 5.16.5 2. Unplug the AC. 3. OBSERVED RESULT I see a wrong remaming time value. EXPECTED RESULT To see the wright remaining time value every couple of minutes updated. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 with KDE Plasma 5.16.5 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION I did not modifified any pakcage myself, those are the KDE orginal packets from Kubuntu 19.10. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 411608] Color scheme configuration lacks a setting for the grid in agenda view
https://bugs.kde.org/show_bug.cgi?id=411608 --- Comment #3 from fred...@free.fr --- (In reply to Allen Winter from comment #2) > just to be clear I understand this request. > > You are asking that the Korganizer configuration dialog=>Colors and Fonts > should offer a setting for "Agenda view grid color" > right? Yes, that would be great as a first step. Something I would even appreciate more: having a single theme applied to both "month" and "agenda" views (currently, "month" view seems to have an hard-coded theme that cannot be modified) and have a "grid color" setting (and all the other colors) applied to all the calendar views, not only the agenda one. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413488] New: Albums/Database inconsistencies digiKam
https://bugs.kde.org/show_bug.cgi?id=413488 Bug ID: 413488 Summary: Albums/Database inconsistencies digiKam Product: digikam Version: 6.4.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: Database-Albums Assignee: digikam-bugs-n...@kde.org Reporter: chasa.im...@xs4all.nl Target Milestone: --- SUMMARY Cleaned up some test albums. Deleted all images from test directory from within digiKam Then I was unable to delete the created album under 'Album'. The option 'Delete' is greyed out. They I choose Tools/Maintenance to 'perform database cleaning'. And a few seconds later digiKam crashed. version: digiKam-6.4.0-git-20191024T225458-Win64.exe OBSERVED RESULT Crash EXPECTED RESULT not crash SOFTWARE/OS VERSIONS digiKam-6.4.0-git-20191024T225458-Win64.exe Win 10 pro 64bit Microsoft Windows [Version 10.0.18362.418] ADDITIONAL INFORMATION Now when I start digiKam I'm unable to create a fresh album. I get an error message saying its directory doesn't exist anymore. Only after recreating it myself, it works again. I've searched in digikamrc for the Album location, but couldn't find it. Probably it is stored in the database? But Tools/Database management does NOT fix this problem. And afterwards, if you manually recreate a 'New Album', there are 2 x 'New Album' entries under 'Album'. And when you delete one of them, the actual 'New Album' directory gets deleted from the file system, but in digiKam you can still see another 'New Album' entry (database issue?). You can only get rid of this when manually recreating a 'New Album' directory in the file system and then deleting it again from digiKam (not the other way around). So there is no x-reference check on database entry for physical (file system) locations and entries of virtual albums in digiKam. This should either correctable with maintenance tools and/or repaired with e.g. database tools. Because the right mouse-options-entries on a created sub-Album in digiKam do not work as expected. Fault bucket 1849065716265782745, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: digikam.exe P2: 0.0.0.0 P3: 5db20d54 P4: libdigikamgui.dll P5: 0.0.0.0 P6: 5db20d35 P7: c005 P8: 001ecdf8 P9: P10: Faulting application name: digikam.exe, version: 0.0.0.0, time stamp: 0x5db20d54 Faulting module name: libdigikamgui.dll, version: 0.0.0.0, time stamp: 0x5db20d35 Exception code: 0xc005 Fault offset: 0x001ecdf8 Faulting process id: 0x223c Faulting application start time: 0x01d58c2ed3f33eb6 Faulting application path: C:\Program Files\digiKam\digikam.exe Faulting module path: C:\Program Files\digiKam\libdigikamgui.dll Report Id: e8db273c-c85c-4bba-b25e-ec33018ed269 Faulting package full name: Faulting package-relative application ID: -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413463] Wallpaper slideshow set to "random" is not random at all
https://bugs.kde.org/show_bug.cgi?id=413463 --- Comment #1 from Mathias Homann --- i can actually choose "next wallpaper" from the desktop context menu, and I'll always get the same sequence of wallpapers so ... NOT random. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413489] New: Location of digikamrc seems not logical/strange
https://bugs.kde.org/show_bug.cgi?id=413489 Bug ID: 413489 Summary: Location of digikamrc seems not logical/strange Product: digikam Version: 6.4.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Setup-ConfigFiles Assignee: digikam-bugs-n...@kde.org Reporter: chasa.im...@xs4all.nl Target Milestone: --- SUMMARY I was looking for the digikamrc file and to my surprise I found it in the root of C:\Users\[user name]\Appdata\Local! And not in something like: C:\Users\[user name]\AppData\Local\digiKam or C:\Users\[user name]\AppData\Roaming\digiKam OBSERVED RESULT wrong location EXPECTED RESULT To reside in the logical and expected directory. SOFTWARE/OS VERSIONS Windows: Microsoft Windows [Version 10.0.18362.418] -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413488] Albums/Database inconsistencies digiKam
https://bugs.kde.org/show_bug.cgi?id=413488 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Delete Album is only grayed out if you have selected a virtual album. You can not delete virtual albums. in the physical Album view, "Delete Album" is never greyed out. Please take a screenshot. Download DebugView from Microsoft and post the messages. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413489] Location of digikamrc seems not logical/strange
https://bugs.kde.org/show_bug.cgi?id=413489 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 402346 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402346] The digikamrc file is not recorded into the digikam directory
https://bugs.kde.org/show_bug.cgi?id=402346 Maik Qualmann changed: What|Removed |Added CC||chasa.im...@xs4all.nl --- Comment #5 from Maik Qualmann --- *** Bug 413489 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413488] Albums/Database inconsistencies digiKam
https://bugs.kde.org/show_bug.cgi?id=413488 --- Comment #2 from Maik Qualmann --- The "root" album of a collection can not be deleted. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411980] Wayland session crashes after I change some settings in system settings
https://bugs.kde.org/show_bug.cgi?id=411980 --- Comment #9 from Fabian Vogt --- (In reply to Patrick Silva from comment #8) > I tried to apply your patch on Arch Linux, but I got building failure :( You have to apply the diff on top of Plasma/5.17, otherwise arc bases it on master instead. That way it built fine here. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413486] Drawing becomes corrupted after resuming from sleep mode.
https://bugs.kde.org/show_bug.cgi?id=413486 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #2 from Boudewijn Rempt --- Yes... That's a known thing, but it's not really Krita specific. The texture memory of the gpu is reset to random after resuming, and it needs to be explicitly reset after that. Unfortunately, Krita doesn't get any signal that the system has been suspended and resumed, so, as far as we know, we just cannot do that programmatically! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413118] Scrollbar mouse down/click on background zone not registered.
https://bugs.kde.org/show_bug.cgi?id=413118 Michael Walser changed: What|Removed |Added CC||k...@mwalser.net --- Comment #2 from Michael Walser --- Created attachment 123503 --> https://bugs.kde.org/attachment.cgi?id=123503&action=edit Patch to fix the scrollbar behavior This changed scrollbar behavior really annoyed me. I tried to come up with a patch which rectifies this issue. What I did was to remove the margin on the scrollbar element (this margin was added in D21639) and replace it with a border around the trough element. This should restore the correct behavior while not changing the visual appearance. Please take this with a grain of salt since I have absolutely not previous GTK experience. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413490] New: Krita unable to open a krita file
https://bugs.kde.org/show_bug.cgi?id=413490 Bug ID: 413490 Summary: Krita unable to open a krita file Product: krita Version: 4.2.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: se.wra...@gmail.com Target Milestone: --- SUMMARY Saved my work as a .kra file yesterday, attempted to open the file today through krita (had no issues with the file previously when opening it) and a pop-up message stating "Could not open file:\\\C:\Users\\OneDrive\Desktop\X.kra. Reason: The file format cannot be parsed.. Reasons: Not a valid Krita File", I've attempted to shut down my pc and reboot it as that has worked previously when this issue has occurred in the past however the result did not change this time. STEPS TO REPRODUCE 1. Open Krita 2. Open .kra file 3. File opens OBSERVED RESULT Aforementioned pop-up message appears and the file does not open. EXPECTED RESULT File opens as per usual SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Attempting to open the autosave file yields the same results. This is Google drive link to the file : https://drive.google.com/file/d/1LveHPvEwlBI0lR0rjqxh_7rOLW4Dr6LG/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration
https://bugs.kde.org/show_bug.cgi?id=179678 --- Comment #88 from lega99 --- If I remember correctly, this is a Dolphin file manager. I read big players plan to leave support for Plasma and KDE. In Kali update program plasma product dont work, synaptic work. I am no longer interested in constantly updating and constantly adding actions that I do not need, every new version uploads 200-300 files initially, and this is repeated all the time on verzion x,x 01 to x. x.5 . After that a new plsma version, new round of the same -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 400418] Wish - Applet to control Night Color feature in the system tray under Wayland
https://bugs.kde.org/show_bug.cgi?id=400418 Stefan Zurucker changed: What|Removed |Added CC||s...@posteo.at Version|5.15.3 |5.17.1 Platform|Archlinux Packages |unspecified --- Comment #4 from Stefan Zurucker --- I would like to emphasize the importance/convenience of this request. It's good to have the setting available in the system settings, but it's not the most visible or convenient place for the user to toggle Night Color. Having a switch in the tray that exposes the settings as well as enabling the user to turn it on and off at the press of a button (like the Redshift control applet) would make Night Color feature-complete, imho, and just simplify things for the user. Thanks for your time! PS: Changed the Plasma Version and Platform in order to better reflect the general context of this feature request. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 413154] Attempting to add item to application menu generates error
https://bugs.kde.org/show_bug.cgi?id=413154 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Wolfgang Bauer --- *** This bug has been marked as a duplicate of bug 413079 *** -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 413079] problem adding/modifying menu entires
https://bugs.kde.org/show_bug.cgi?id=413079 Wolfgang Bauer changed: What|Removed |Added CC||yumpottedm...@gmail.com --- Comment #1 from Wolfgang Bauer --- *** Bug 413154 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Eric Donkersloot changed: What|Removed |Added CC||eric.donkersl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 412189] No way to switch different cameras
https://bugs.kde.org/show_bug.cgi?id=412189 --- Comment #5 from selfishje...@riseup.net --- Sorry for the late reply I'm 99.7% certain that there was no option to choose camera same as if it isn't even connected. To be absolutely sure and maybe to take a hilarious picture I wanted to look in the settings again with the webcam (left alone at home) but I ended up staying at dorm for another weekend and usb webcams are strangely not a common occurrence anymore. To the issue, it seems to be some bug with my setup (a bit messy arch installed on cerebooted thinkpad with webcam hw killswitch added) and not a missing important feature so if it doesn't affect many users I don't think it's really worth chasing down. Anyway, I can provide any logs if needed (hopefully, next week, with the second webcam). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411075] “Do Not Disturb” automaticaly set in any full screen mode activities
https://bugs.kde.org/show_bug.cgi?id=411075 bjoe...@arcor.de changed: What|Removed |Added CC||bjoe...@arcor.de -- You are receiving this mail because: You are watching all bug changes.
