[plasmashell] [Bug 396111] Activity doesn't update files shown on desktop
https://bugs.kde.org/show_bug.cgi?id=396111 Dominik Stańczak changed: What|Removed |Added CC||stanczakdomi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #2 from Michail Vourlakos --- In what distro? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 --- Comment #2 from Michail Vourlakos --- Have you tried to disable the animations? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411001] Brushes will not appear
https://bugs.kde.org/show_bug.cgi?id=411001 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 410227] stars 3.3.2 crashes on startup
https://bugs.kde.org/show_bug.cgi?id=410227 Bug Janitor Service changed: What|Removed |Added Resolution|FIXED |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 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.
[marble] [Bug 411665] New: Misspelled words on the website
https://bugs.kde.org/show_bug.cgi?id=411665 Bug ID: 411665 Summary: Misspelled words on the website Product: marble Version: unspecified Platform: Other OS: other Status: REPORTED Severity: normal Priority: NOR Component: website Assignee: marble-b...@kde.org Reporter: gka...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Enter greek version of the website 2. read text in greek version. OBSERVED RESULT τξ, δόμους, αυθαίρεοτ, Αρχίστρ EXPECTED RESULT τη, δρόμους, αυθαίρετο, Αρχίστε -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411664] New: clicking on a certain brush preset crashes software
https://bugs.kde.org/show_bug.cgi?id=411664 Bug ID: 411664 Summary: clicking on a certain brush preset crashes software Product: krita Version: 4.2.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: viv...@zetune.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. make a preset of the soft airbrush 2. click on it 3. OBSERVED RESULT loading wheel appears next to the cursor then, after a few seconds the whole software shuts down or crashes 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.
[frameworks-syntax-highlighting] [Bug 409380] Formatting by KSyntaxHighlighting::SyntaxHighlighter of normal text seems to be dropped partially (Qt >=5.13.0/5.12.4)
https://bugs.kde.org/show_bug.cgi?id=409380 Patrick Silva changed: What|Removed |Added CC||sk.griffi...@gmail.com --- Comment #5 from Patrick Silva --- *** Bug 411656 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411656] previews of text files in dolphin are unreadable when using dark themes (breeze dark,breath dark etc)
https://bugs.kde.org/show_bug.cgi?id=411656 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 409380 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 411226] Temperature shown to 6 decimal places in SMART Status
https://bugs.kde.org/show_bug.cgi?id=411226 --- Comment #2 from Mathew --- Tested this and it's working fine. Slight correction: this is significant figures not decimal places (https://doc.qt.io/qt-5/qstring.html#argument-formats) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411506] Kwin requires constant restart after weeks of uptime to refresh windows
https://bugs.kde.org/show_bug.cgi?id=411506 --- Comment #2 from Michael Butash --- I am pretty sure not, it's a 1070GTX. This only occurs with kde/kwin so far, where I've been testing again of late, but otherwise have been using Mate/Cinnamon mostly as kde's been a basketcase for me the past year or so. I do a fair amount of gaming on this too, never have an issue running linux-native or proton-based windoze steam games, so long as it's not freaking out at the moment, it works just fine. Thus I really don't think it's a video bandwidth/capabilities thing, but the compositor. I just toggle opengl modes in ksettings, and it's good again for a few days. Kwin currently is using about 3.8gb of ram, and plasmashell uses 17.4gb, so it's quite resource intensive to use, but having a 20-core system with 128gb of ram helps, but it just seems to come unglued at some point. I'm trying to put gputop on this to watch it, I've done so with my laptop in the past, but the package seems broken for arch currently yay install it... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 --- Comment #1 from leftcrane --- It takes about two-three seconds to UPDATE the task list when switching desktops. It's very inconvenient when switching desktops rapidly. You have to wait for all the tasks to get displayed. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] New: Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 Bug ID: 411663 Summary: Eliminate delay in dock when using workspace isolation Product: lattedock Version: git (master) Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: leftcr...@tutanota.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Set "show launchers from current desktop" 2. Open some windows 3. Switch to next desktop. OBSERVED RESULT It takes about three seconds to show the task list (dock) EXPECTED RESULT When switching desktops, the dock should appear instantly. Task list should be remembered for each virtual workspace, so it doesn't have to generated on the fly. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 411644] Crash when hovering over a forward declared typedef'd struct
https://bugs.kde.org/show_bug.cgi?id=411644 krzysio.ku...@wp.pl changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from krzysio.ku...@wp.pl --- *** This bug has been marked as a duplicate of bug 396847 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 396847] kdev-clang: test_duchain-clang crashes on exit
https://bugs.kde.org/show_bug.cgi?id=396847 krzysio.ku...@wp.pl changed: What|Removed |Added CC||krzysio.ku...@wp.pl --- Comment #2 from krzysio.ku...@wp.pl --- *** Bug 411644 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411662] New: plasmashell segmentation fault after configuring the task manager to set the Show tooltips to off in Plasma 5.16.4 on Wayland
https://bugs.kde.org/show_bug.cgi?id=411662 Bug ID: 411662 Summary: plasmashell segmentation fault after configuring the task manager to set the Show tooltips to off in Plasma 5.16.4 on Wayland Product: plasmashell Version: 5.16.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: matthew.fagn...@utoronto.ca CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.4) Qt Version: 5.12.4 Frameworks Version: 5.61.0 Operating System: Linux 5.3.0-0.rc7.git0.1.fc31.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I right clicked on the task manager bar at the bottom of the screen in Plasma 5.16.4 on Wayland in Fedora 31. I selected Configure Task Manager... I set Show tooltips to off. I clicked OK. - Unusual behavior I noticed: plasmashell crashed, and the task manager disappeared and reappeared shortly afterwards. The crashing thread 1 had "error reading variable: Cannot access memory at address 0xbc9" in frames #7-11, which is likely the reason for the segmentation fault. The shorter than normal address 0xbc9 might indicate memory corruption. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), 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 0x7f8468cf7d00 (LWP 1371))] Thread 21 (Thread 0x7f83f61f8700 (LWP 1913)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x7f84041d9484) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f84041d9430, cond=0x7f84041d9458) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f84041d9458, mutex=0x7f84041d9430) at pthread_cond_wait.c:638 #3 0x7f8466c16273 in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x7f84041d9430) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x555a379761e0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f8466c16301 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x555a379761e8, mutex=mutex@entry=0x555a379761e0, time=time@entry=18446744073709551615) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #6 0x7f84689e0ff9 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x555a379761d8) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x555a37976160) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7f84689e129d in QSGRenderThread::run() (this=0x555a37976160) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7f8466c10776 in QThreadPrivate::start(void*) (arg=0x555a37976160) at thread/qthread_unix.cpp:361 #10 0x7f84660644e2 in start_thread (arg=) at pthread_create.c:479 #11 0x7f8466884643 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f83f69f9700 (LWP 1912)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x555a37a42b88) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x555a37a42b38, cond=0x555a37a42b60) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x555a37a42b60, mutex=0x555a37a42b38) at pthread_cond_wait.c:638 #3 0x7f844e510edb in cnd_wait (mtx=0x555a37a42b38, cond=0x555a37a42b60) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x555a37a37a90) at ../src/util/u_queue.c:272 #5 0x7f844e510aeb in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7f84660644e2 in start_thread (arg=) at pthread_create.c:479 #7 0x7f8466884643 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f83f77fe700 (LWP 1901)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x555a36f4aee0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x555a36f4ae90, cond=0x555a36f4aeb8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x555a36f4aeb8, mutex=0x555a36f4ae90) at pthread_cond_wait.c:638 #3 0x7f8466c16273 in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x555a36f4ae90) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x555a375d11f0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f8466c16301 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x555a375d11f8, mutex=mutex@entry=0x555a375d11f0,
[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB
https://bugs.kde.org/show_bug.cgi?id=389848 Stefan Brüns changed: What|Removed |Added CC||dasmith@electronicaidesdesi ||gn.com --- Comment #106 from Stefan Brüns --- *** Bug 411660 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 411660] Baloo Crashes Quite Offten When Doing Normal Tasks In Plasma
https://bugs.kde.org/show_bug.cgi?id=411660 Stefan Brüns changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Stefan Brüns --- *** This bug has been marked as a duplicate of bug 389848 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411661] New: "Select a Color" dialog is modeless when setting fg color and modal when setting bg color
https://bugs.kde.org/show_bug.cgi?id=411661 Bug ID: 411661 Summary: "Select a Color" dialog is modeless when setting fg color and modal when setting bg color Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: nikola.knezevic@gmail.com Target Milestone: --- 1. When setting foreground color via "Select a Color" dialog it is possible to continue work without closing dialog (modeless). 2. When setting background color via "Select a Color" dialog it isn't possible to continue work without closing dialog (modal). I like to be able to work without closing this dialog. It is possible to open both dialogs when opening dialog for foreground and another dialog for background after that. It even can be useful when working with brushes with gradient color. EXPECTED RESULT I think the behavior should be unified and both of dialogs should be modeless. SOFTWARE/OS VERSIONS Windows: 10 pro 64 bit Krita 4.3.0-prealpha (git 5c326ec) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 411660] New: Baloo Crashes Quite Offten When Doing Normal Tasks In Plasma
https://bugs.kde.org/show_bug.cgi?id=411660 Bug ID: 411660 Summary: Baloo Crashes Quite Offten When Doing Normal Tasks In Plasma Product: frameworks-baloo Version: 5.45.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: dasm...@electronicaidesdesign.com Target Milestone: --- Application: baloo_file (5.45.0) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.70-default x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: - What I was doing when the application crashed: I was just downloading a pdf file from https://www.manualslib.com using Firefox Version Quantum 68.1.0esr (64-bit), which came pre-compiled with OpenSUSE Leap 15.0 Workstation. The following is what versions of my desktop system is running: KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.45.0 Qt Version: 5.9.4 Kernel Version: 4.12.14-lp150.12.70-default All software packages were installed pre-compiled from OpenSUSE Leap 15.0 installation source. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6656b66680 (LWP 2351))] Thread 3 (Thread 0x7f6648b8c700 (LWP 5308)): [KCrash Handler] #6 0x7f66544f8160 in raise () from /lib64/libc.so.6 #7 0x7f66544f9741 in abort () from /lib64/libc.so.6 #8 0x7f66522bb922 in mdb_assert_fail (env=0x5612c922b8a0, expr_txt=expr_txt@entry=0x7f66522bd3af "rc == 0", func=func@entry=0x7f66522bdce8 <__func__.6935> "mdb_page_dirty", line=line@entry=2071, file=0x7f66522bd390 "mdb.c") at mdb.c:1487 #9 0x7f66522b0e05 in mdb_page_dirty (txn=0x5612c922bcb0, mp=) at mdb.c:2071 #10 0x7f66522b1fea in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7f6648b8b088, mc=) at mdb.c:2252 #11 0x7f66522b2259 in mdb_page_touch (mc=mc@entry=0x7f6648b8b5c0) at mdb.c:2370 #12 0x7f66522b3d54 in mdb_cursor_touch (mc=mc@entry=0x7f6648b8b5c0) at mdb.c:6273 #13 0x7f66522b6eee in mdb_cursor_put (mc=0x7f6648b8b5c0, key=0x7f6648b8b990, data=0x7f6648b8b9a0, flags=) at mdb.c:6407 #14 0x7f66522b99ab in mdb_put (txn=0x5612c922bcb0, dbi=2, key=key@entry=0x7f6648b8b990, data=data@entry=0x7f6648b8b9a0, flags=flags@entry=0) at mdb.c:8765 #15 0x7f6655b7ee5c in Baloo::PostingDB::put (this=this@entry=0x7f6648b8ba80, term=..., list=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:78 #16 0x7f6655b8b5d0 in Baloo::WriteTransaction::commit (this=0x7f263c003b20) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:289 #17 0x7f6655b844c2 in Baloo::Transaction::commit (this=this@entry=0x7f6648b8bb90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262 #18 0x5612c7b166cd in Baloo::NewFileIndexer::run (this=0x5612c94171e0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/newfileindexer.cpp:75 #19 0x7f6654ff1372 in QThreadPoolThread::run (this=0x5612c933c750) at thread/qthreadpool.cpp:99 #20 0x7f6654ff40ce in QThreadPrivate::start (arg=0x5612c933c750) at thread/qthread_unix.cpp:368 #21 0x7f6653610569 in start_thread () from /lib64/libpthread.so.0 #22 0x7f66545baa2f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f66496bf700 (LWP 2378)): #0 0x7fffc2dfa822 in clock_gettime () #1 0x7f66545c8326 in clock_gettime () from /lib64/libc.so.6 #2 0x7f6655217631 in qt_clock_gettime (ts=0x7f66496bea30, clock=) at kernel/qelapsedtimer_unix.cpp:111 #3 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7f6655215f09 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f6644005130) at kernel/qtimerinfo_unix.cpp:91 #6 0x7f6655216485 in QTimerInfoList::timerWait (this=0x7f6644005130, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7f66552179ce in timerSourcePrepareHelper (timeout=0x7f66496beae4, src=) at kernel/qeventdispatcher_glib.cpp:132 #8 timerSourcePrepare (source=, timeout=0x7f66496beae4) at kernel/qeventdispatcher_glib.cpp:165 #9 0x7f6650c95789 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #10 0x7f6650c9615b in ?? () from /usr/lib64/libglib-2.0.so.0 #11 0x7f6650c9633c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #12 0x7f6655217c1b in QEventDispatcherGlib::processEvents (this=0x7f6644000b30, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #13 0x7f66551c009a in QEventLoop::exec (this=this@entry=0x7f66496beca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #14 0x7f6654fef4da in QThread::exec (this=) at
[amarok] [Bug 411620] No sound on AirPlay speakers
https://bugs.kde.org/show_bug.cgi?id=411620 Myriam Schweingruber changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Myriam Schweingruber --- Sound device selection does not depend on Amarok, but on Pulseaudio, please select your output devices in the general sound settings of your system. Unfortunately you did not specify your marok version or your platform and version... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411659] New: Unknown error.
https://bugs.kde.org/show_bug.cgi?id=411659 Bug ID: 411659 Summary: Unknown error. Product: krita Version: 4.2.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: mrgrahamcracke...@gmail.com Target Milestone: --- SUMMARY While attempting to render an animation, the window displaying the loading bar appears, halts at approximately 70%, and then either crashes the application and exports only the frames, or displays a window that states "Could not render animation:Unknown error." and exports a blank, 0 byte document that cannot seem to be opened with any application. STEPS TO REPRODUCE 1. Download the most recent builds of both Krita and Ffmpeg. Unzip the Ffmpeg file. 2. Create an animation (a simple one is recommended for testing purposes), and go to File> Render Animation. Select to export as a video and render as a GIF. 3. Click on the file icon (which displays "Select file name..." when the cursor hovers over it) next to the "FFMpeg: " box, which will bring you to downloads. 4. Open the extracted file "ffmpeg", then the file "bin", and select ffmpeg.exe, after which you will be returned to the "Render Animation" window, now with the address to that file in the "FFMpeg: " box. 5. Click "Ok" OBSERVED RESULT The program either crashes and exports only the frames, or displays an error message and exports an empty file. There does not seem to be any pattern to the outcome. EXPECTED RESULT The file should be exported as a GIF. SOFTWARE/OS VERSIONS Windows: Windows 10, version 1903 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.
[kcharselect] [Bug 411658] New: Chess Symbols not displaying correctly for any font
https://bugs.kde.org/show_bug.cgi?id=411658 Bug ID: 411658 Summary: Chess Symbols not displaying correctly for any font Product: kcharselect Version: 19.08.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: cf...@kde.org Reporter: igory...@gmail.com Target Milestone: --- SUMMARY Chess Symbols not displaying correctly for any font, getting only squares (though in konsole, for example, they display like normal when using the same font). STEPS TO REPRODUCE 1. Open kcharselect 2. Select 'Symbols' in 'Select a category' list menu 3. Select 'Chess Symbols' in 'Select a block to be displayed' list menu OBSERVED RESULT Chess symbols displaying as squares, as if not supported by the font being used. EXPECTED RESULT Chess symbols having appearance of actual chess pieces. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Kernel Version: 5.2.11-arch1-1-ARCH ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #1 from Filipe Azevedo --- As a workaround, disable meta shortcut support from latte dock configure dialog and restart the application hide the issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411081] Crash Without Warning
https://bugs.kde.org/show_bug.cgi?id=411081 4lph4dr4g0nl...@gmail.com changed: What|Removed |Added Resolution|FIXED |WORKSFORME --- Comment #25 from 4lph4dr4g0nl...@gmail.com --- (In reply to Dmitry Kazakov from comment #22) > Ah, I'm sorry. I gave you a link to a wrong branch, sorry :( > > Could you try this one: > https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/ > > And at the same time, could you check if you have access to this folder? > C:\Users\nitef\AppData\Local\Temp > > It looks like Krita tries to create a swap file there, but fails. > > If you still have a crash, try to go to > Preferences->Performance->SwapFileLocation and select some writable > location, which you are sure about. After that restart Krita. > > If you still have a problem, attach a log from DebugView :) - Sorry for waiting so long to reply, but because it didn't show itself last time, I took a few days to test the build for the crash. I've been actively trying to duplicate the crash, and so far it hasn't happened yet. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 411599] Open/Save dialog is much too small.
https://bugs.kde.org/show_bug.cgi?id=411599 --- Comment #3 from Christoph Feck --- Note that most of KDE's UI is just Qt widgets. While KDE developers can (and do) submit Qt patches, they need to work on all platforms. GNOME developers have full control over GTK and don't have to care about Windows, macOS, or mobile systems. That's why GTK is ahead in Linux hardware adaptibility (pen/touch input). Looking is easy, but actually getting Qt changed is harder. More contributors are needed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 --- Comment #121 from David Edmundson --- The message is normal, but arguably pointless. I'll revsit that. VMWware (and whatever) else we can't fix. Every client needs to reset itself after a graphics resets. That's on VMWare (or whatever other client) to fix. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] New: Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657
Bug ID: 411657
Summary: Latte dock free when used with some combinations of
plasmoids
Product: lattedock
Version: 0.9.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: mvourla...@gmail.com
Reporter: pas...@gmail.com
Target Milestone: ---
When using some particular combinations of plasmoid with a "(panel) latte dock"
latte dock regularly freeze and need to be killed / restarted so it works
again.
Also, promoting a dock to panel then removing its latte plasmoid, always lead
to freeze, ie a plasmoid latte dock less panel always freeze.
STEPS TO REPRODUCE
1. Create a new user
2. Log in with this user
3. You should arrive on a plasma having a bottom latte dock
4. Create a top panel dock
5. Add 2 or 3 web browser plasmoids
6. Add system tray (or notifications) plasmoid
7. Open the web browser plasmoid popup
8. Use kde shortcut to resize / move windows: Meta+ Up/Left/Top/Bottom
9. Notice after the second shortcut trigger the popup does no longer render
correctly
10. Try to use your panel / dock
11. It's not working, it's frozen
OBSERVED RESULT
Latte dock freeze
EXPECTED RESULT
No freeze
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.13.0
ADDITIONAL INFORMATION
Some combinations that works / freeze:
Panel + NO latte + browser = Freeze
Panel + latte + browser = OK
Panel + latte + browser + notifications = Freeze
Output traces from -d --with-window:
23:25:58.740 lattedock(2122/2122) WARNING:
QProcess::~QProcess|Latte::UniversalSettings::kwin_metaForwardedToLatte|Latte::GlobalShortcuts::showViews
QProcess: Destroyed while process ("kreadconfig5") is still running.
/!\ At this point i have a dead / zombie kreadconfig5 process.
Back trace at the time of the freeze:
#0 0x70e1cc12 in ppoll () at /lib/libc.so.6
#1 0x71c8e760 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2 0x71bcc92f in QProcessPrivate::waitForFinished(int) () at
/usr/lib/libQt5Core.so.5
#3 0x71bc2f3d in QProcess::waitForFinished(int) () at
/usr/lib/libQt5Core.so.5
#4 0x71bc3682 in QProcess::~QProcess() () at /usr/lib/libQt5Core.so.5
#5 0x004f8bad in Latte::UniversalSettings::kwin_metaForwardedToLatte()
const ()
#6 0x00506f6b in Latte::GlobalShortcuts::showViews() ()
#7 0x71c6a730 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#8 0x71c6a730 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#9 0x71c759e7 in QTimer::timeout(QTimer::QPrivateSignal) () at
/usr/lib/libQt5Core.so.5
#10 0x71c6adbb in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#11 0x73a8db81 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#12 0x73a94aa0 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#13 0x71c419f9 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#14 0x71c91ae3 in QTimerInfoList::activateTimers() () at
/usr/lib/libQt5Core.so.5
#15 0x71c922bc in idleTimerSourceDispatch(_GSource*, int (*)(void*),
void*) () at /usr/lib/libQt5Core.so.5
#16 0x7fffe852b51e in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#17 0x7fffe852b788 in () at /usr/lib/libglib-2.0.so.0
#18 0x7fffe852b80c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#19 0x71c925d3 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#20 0x71c406fb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#21 0x71c4839e in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#22 0x00471c9c in main ()
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 411635] Add a folder-open-recent icon similar to document-open-recent
https://bugs.kde.org/show_bug.cgi?id=411635
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.62
Status|CONFIRMED |RESOLVED
Latest Commit||https://commits.kde.org/bre
||eze-icons/c58bedafd926e525e
||2acabd91e084601055b3486
Resolution|--- |FIXED
--- Comment #3 from Nate Graham ---
Git commit c58bedafd926e525e2acabd91e084601055b3486 by Nate Graham.
Committed on 06/09/2019 at 21:32.
Pushed by ngraham into branch 'master'.
Create new "Recent folders" icon
Summary:
Needed for D7446.
FIXED-IN: 5.62
Test Plan:
{F7325143, size=full}
{F7325144, size=full}
Reviewers: #vdg, ndavis
Reviewed By: #vdg, ndavis
Subscribers: ndavis, kde-frameworks-devel, meven
Tags: #frameworks
Differential Revision: https://phabricator.kde.org/D23760
A +12 -0icons-dark/actions/16/folder-open-recent.svg
A +12 -0icons-dark/actions/22/folder-open-recent.svg
A +12 -0icons/actions/16/folder-open-recent.svg
A +12 -0icons/actions/22/folder-open-recent.svg
https://commits.kde.org/breeze-icons/c58bedafd926e525e2acabd91e084601055b3486
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 411596] Dolphin crashes when tries to play a video preview after I select a folder
https://bugs.kde.org/show_bug.cgi?id=411596 --- Comment #1 from Patrick Silva --- This crash only occurs on Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410774] Cannot reply on second SMS
https://bugs.kde.org/show_bug.cgi?id=410774 --- Comment #8 from Piotr Mierzwinski --- After restart application (from "The crash handler"). KDEConnect stopped report new SMS receiving :/. I received SMS on my device (during typing another one) and KDEConnect noticed nothing. Connection was fine, because I checked it via controlling media extension and it worked. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411656] New: previews of text files in dolphin are unreadable when using dark themes (breeze dark,breath dark etc)
https://bugs.kde.org/show_bug.cgi?id=411656 Bug ID: 411656 Summary: previews of text files in dolphin are unreadable when using dark themes (breeze dark,breath dark etc) Product: dolphin Version: 19.08.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: sk.griffi...@gmail.com Target Milestone: --- Created attachment 122518 --> https://bugs.kde.org/attachment.cgi?id=122518=edit Shows screenshot demonstrating the bug SUMMARY: Previewing text files shows white fonts on white background, making them unreadable. They should be black font on white background STEPS TO REPRODUCE 1. Enable breath dark or breeze dark colour scheme 2. open dolphin 3. hover over a .txt file in dolphin OBSERVED RESULT: Text in the preview is unreadable 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.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 Vlad Zahorodnii changed: What|Removed |Added Resolution|FIXED |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 Keziolio changed: What|Removed |Added Resolution|UPSTREAM|FIXED --- Comment #16 from Keziolio --- Oh ok, thanks for the support -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411655] New: When it's opened the terminal of Dolphin, the focus still keep on Dolphin
https://bugs.kde.org/show_bug.cgi?id=411655 Bug ID: 411655 Summary: When it's opened the terminal of Dolphin, the focus still keep on Dolphin Product: dolphin Version: 19.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: fdelgado...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Click once on a file 2. Click F4 to open the terminal 3. Try to write on it (terminal) Forces you to do click with the mouse in the terminal to get the focus. I think it would be convenient if the focus could keep in the terminal when oneself opened it. SOFTWARE/OS VERSIONS OS: Manjaro 18.0.4 Illyria Kernel: x86_64 Linux 5.2.11-1-MANJARO DE: KDE 5.61.0 / Plasma 5.16.4 WM: KWin Qt: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #15 from Vlad Zahorodnii --- (In reply to Keziolio from comment #13) > "kwin" is always broken since I can't open yakuake in the rightmost monitor, > the problem is persistent > > > Is the issue with the panel and not with kwin? I'm confused on what does what kwin is not broken. Something down the stack is. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411607] Add shadows behind desktop icons
https://bugs.kde.org/show_bug.cgi?id=411607 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Nate Graham --- Can you provide an example screenshot of where this is a problem such that adding a shadow would fix it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #14 from Vlad Zahorodnii --- Report this bug to amdgpu developers. https://bugs.freedesktop.org/enter_bug.cgi?product=xorg=Driver/AMDgpu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411605] Plasma freezes when Visual Studio Code is overloaded with opened files
https://bugs.kde.org/show_bug.cgi?id=411605 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 411641] Powerdevil settings UI looks messy
https://bugs.kde.org/show_bug.cgi?id=411641 Nate Graham changed: What|Removed |Added Resolution|--- |MOVED URL||https://phabricator.kde.org ||/T7256 Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- It sure does. There is a plan in place to fix this, tracked at https://phabricator.kde.org/T7256 We'll keep tracking it there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #13 from Keziolio --- "kwin" is always broken since I can't open yakuake in the rightmost monitor, the problem is persistent Is the issue with the panel and not with kwin? I'm confused on what does what -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411596] Dolphin crashes when tries to play a video preview after I select a folder
https://bugs.kde.org/show_bug.cgi?id=411596 Nate Graham changed: What|Removed |Added CC||meve...@gmail.com, ||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 411599] Open/Save dialog is much too small.
https://bugs.kde.org/show_bug.cgi?id=411599 --- Comment #2 from leftcrane --- Also gtk-style hiding scrollbars could be really beneficial for these cases. The current bars take up ~30-40 pixels of space horizontally in the dialog, all the time. It also clutters the interface. It would help to have an autohide scrollbars option in Breeze. It is possible to show that an view is scrollable without an always on scrollbar. GTK does it by adding dashed lines to indicate possible scrolling directions. I think it's a good solution, at least as an option. (In general I think it would benefit KDE to just go right down the line and look at all the things Gnome does differently with the UI, then adopt the good parts if feasible. Many of UI problems have already been solved by Gnome.) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 411654] New: When it's removed a HDMI wire, still is visible the Screen Configuration icon
https://bugs.kde.org/show_bug.cgi?id=411654 Bug ID: 411654 Summary: When it's removed a HDMI wire, still is visible the Screen Configuration icon Product: frameworks-plasma Version: 5.16.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: fdelgado...@gmail.com Target Milestone: --- Created attachment 122517 --> https://bugs.kde.org/attachment.cgi?id=122517=edit The first icon to the left In the system tray, I've got configured "Screen Configuration", its visibility as automatic. In this way, when it's connected a HDMI wire, the icon appears automatically. Ok, until here all good. pitfall? when the wire no longer stays, but its icon yes. SOFTWARE/OS VERSIONS OS: Manjaro 18.0.4 Illyria Kernel: x86_64 Linux 5.2.11-1-MANJARO DE: KDE 5.61.0 / Plasma 5.16.4 WM: KWin Qt: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #12 from Keziolio --- Created attachment 122516 --> https://bugs.kde.org/attachment.cgi?id=122516=edit xprop -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #11 from Keziolio --- Created attachment 122515 --> https://bugs.kde.org/attachment.cgi?id=122515=edit qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #10 from Vlad Zahorodnii --- and also output of qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #9 from Vlad Zahorodnii --- Please post xprop output of the panel when "kwin" is broken. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #8 from Keziolio --- Yes I can, both "symptoms" persist with compositing disabled -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 411599] Open/Save dialog is much too small.
https://bugs.kde.org/show_bug.cgi?id=411599 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Keywords||usability CC||n...@kde.org --- Comment #1 from Nate Graham --- Yeah, it really is. I need to finally figure out what the heck is going on here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411606] Show undo notification after un-pinning an app from task manager
https://bugs.kde.org/show_bug.cgi?id=411606 Nate Graham changed: What|Removed |Added Summary|Add confirmation dialog for |Show undo notification |un-pinning an app from task |after un-pinning an app |manager |from task manager CC||n...@kde.org --- Comment #1 from Nate Graham --- In general, confirmation dialogs for user-initiated actions are annoying and counterproductive because people become accustomed to clicking through them without reading. What we could maybe do instead is show a notification with an undo button in it, like the one that appears when you remove a widget. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #7 from Vlad Zahorodnii --- Can you reproduce the bug when compositing is suspended? (press Alt+Shift+F12 to toggle compositing) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #6 from Keziolio --- I can reproduce the bug with "Full Screen Repaints" enabled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #5 from Vlad Zahorodnii --- s/setting/settings/ -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 411653] New: After exit Dolphin, the connection with Google Drive doesn't work
https://bugs.kde.org/show_bug.cgi?id=411653 Bug ID: 411653 Summary: After exit Dolphin, the connection with Google Drive doesn't work Product: kio-gdrive Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: fdelgado...@gmail.com Target Milestone: --- Created attachment 122514 --> https://bugs.kde.org/attachment.cgi?id=122514=edit Error Message when access to Google Drive tltd; Google Drive needs to renew always the account after exit Dolphin. STEPS TO REPRODUCE 1. Add the account of Google in System Preferences > Accounts. 2. Connect with Google Drive via Dolphin. "gdrive:/email_from_goo...@gmail.com/" 3. It works 4. If exit Dolphin and open it again, then when you access once again to the previous path from Google Drive you'll see an error. The following error showed by Dolphin is "Error desconocido." (spanish). In English the message would be like "Unknown error". SOFTWARE/OS VERSIONS OS: Manjaro 18.0.4 Illyria Kernel: x86_64 Linux 5.2.11-1-MANJARO DE: KDE 5.61.0 / Plasma 5.16.4 WM: KWin Qt: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #4 from Vlad Zahorodnii --- Can you reproduce this bug when full screen repaints are forced? In order to force full screen repaints, go to compositor setting and choose "Full screen repaints" swap(tearing prevention) strategy. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410774] Cannot reply on second SMS
https://bugs.kde.org/show_bug.cgi?id=410774 --- Comment #7 from Piotr Mierzwinski --- This time when I tried to reply on SMS KDEConnect just crashed. I don't have useful backtrace, probably because I don't have installed debug package. Anyway I did something like this - received SMS - clicked "Reply" (popup window) - wrote and sent, all fine - received another SMS - clicked "Reply" (popup window) - started typing - my phone notified my that I received another SMS, but KDEConnect didn't report it. In Notification I saw only old one. - clicked "Send" and then KDEConnect crashed with not useful (for The crash handler) backtrace. Anyway I put it below: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f81de174380 (LWP 1334))] Thread 4 (Thread 0x7f81cfebe700 (LWP 8989)): #0 0x7f81e1dbe415 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f81d42bff5c in ?? () from /usr/lib/dri/i965_dri.so #2 0x7f81d42bfb58 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7f81e1db857f in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f81e2a950e3 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f81d6e33700 (LWP 1375)): #0 0x7f81e11fd36c in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #1 0x7f81e11fd9a6 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f81e11fdb51 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f81e302b9bc in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f81e2fd25ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f81e2e052f5 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f81e2e06520 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f81e1db857f in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f81e2a950e3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f81d7634700 (LWP 1373)): #0 0x7f81e2a8a667 in poll () from /usr/lib/libc.so.6 #1 0x7f81e11fda80 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f81e11fdb51 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f81e302b9bc in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f81e2fd25ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f81e2e052f5 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f81e3263b37 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7f81e2e06520 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f81e1db857f in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f81e2a950e3 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f81de174380 (LWP 1334)): [KCrash Handler] #6 0x7f81e4260edd in ?? () from /usr/lib/libkdeconnectcore.so.1 #7 0x7f81e42604c6 in KdeConnectPlugin::sendPacket(NetworkPacket&) const () from /usr/lib/libkdeconnectcore.so.1 #8 0x7f81d581a592 in ?? () from /usr/lib/qt/plugins/kdeconnect/kdeconnect_notifications.so #9 0x7f81e2fffb70 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #10 0x7f81d580d3a8 in ?? () from /usr/lib/qt/plugins/kdeconnect/kdeconnect_notifications.so #11 0x7f81d581fc2e in ?? () from /usr/lib/qt/plugins/kdeconnect/kdeconnect_notifications.so #12 0x7f81e2fffb70 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #13 0x7f81e3cd4879 in QDialogPrivate::finalize(int, int) () from /usr/lib/libQt5Widgets.so.5 #14 0x7f81e2fffa11 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #15 0x7f81e3c6c779 in ?? () from /usr/lib/libQt5Widgets.so.5 #16 0x7f81e2fffa11 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #17 0x7f81e3bc4663 in QAbstractButton::clicked(bool) () from /usr/lib/libQt5Widgets.so.5 #18 0x7f81e3bc488c in ?? () from /usr/lib/libQt5Widgets.so.5 #19 0x7f81e3bc5c92 in ?? () from /usr/lib/libQt5Widgets.so.5 #20 0x7f81e3bc5e56 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5Widgets.so.5 #21 0x7f81e3b0ecb6 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #22 0x7f81e3acb4d5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #23 0x7f81e3ad4c6c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #24 0x7f81e2fd39c2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #25 0x7f81e3ad3d4b in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib/libQt5Widgets.so.5 #26 0x7f81e3b2b211 in ?? () from /usr/lib/libQt5Widgets.so.5 #27 0x7f81e3b2e154 in ?? () from /usr/lib/libQt5Widgets.so.5 #28 0x7f81e3acb4d5 in
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #3 from Keziolio --- The screenshot "Full Screen (All Monitors)" in spectacle looks good, so does the qdbus command you gave me, it's not broken Regarding the screenshots issue, it's just the "preview" thing inside spectacle that is shifted, and I can't reach the leftmost part because it's "outside" the monitors -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #2 from Vlad Zahorodnii --- Use this command qdbus org.kde.KWin /Screenshot screenshotFullscreen -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411651] New tool to export photos to Canon Irista
https://bugs.kde.org/show_bug.cgi?id=411651 --- Comment #2 from Eric Brunel --- Since I have an account there, I contacted their support team to know if there's something like a public API. They usually answer quite quickly, I'll post a new comment here as soon as I get an answer. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 411635] Add a folder-open-recent icon similar to document-open-recent
https://bugs.kde.org/show_bug.cgi?id=411635 --- Comment #2 from Nate Graham --- https://phabricator.kde.org/D23760 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 --- Comment #1 from Vlad Zahorodnii --- Can you take screenshot of all screens when kwin is broken? Does it look good? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411652] New: General breakage with multiple monitors (affecting yakuake and spectacle)
https://bugs.kde.org/show_bug.cgi?id=411652 Bug ID: 411652 Summary: General breakage with multiple monitors (affecting yakuake and spectacle) Product: kwin Version: 5.16.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multihead Assignee: kwin-bugs-n...@kde.org Reporter: keziolio...@gmail.com Target Milestone: --- SUMMARY Please see the video: https://youtu.be/zikzg5cDIrs This is with xorg, mesa with amd gpu The two major things are: 1) spectacle's "rectangular region" mode is shifted to the left, and I can't screenshot the left part of the desktop 2) yakuake doesn't show up on a monitor, or, with two monitors, it shows but with a smaller / wrong width This seems to also glitch part of some applications, for example QtCreator works "better" on the left monitor, on the rightmost one it tends to glitch and not update the screen / render some panels with wrong size STEPS TO REPRODUCE 1. attach more than one monitor (tested with 2 and 3 4k monitors) 2. admire the breakage I can reproduce this with another clean user, so it shouldn't be a configuration issue OBSERVED RESULT Bugs EXPECTED RESULT The absence of bugs SOFTWARE/OS VERSIONS Latest version of everything in Arch Linux, this has been going on for ages ADDITIONAL INFORMATION $ xrandr --listmonitors Monitors: 3 0: +*DisplayPort-1 3840/600x2160/340+3840+0 DisplayPort-1 1: +DisplayPort-0 3840/607x2160/345+7680+0 DisplayPort-0 2: +HDMI-A-1 3840/608x2160/345+0+0 HDMI-A-1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411651] New tool to export photos to Canon Irista
https://bugs.kde.org/show_bug.cgi?id=411651 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- I can not find a public developer API. I suspect that this service is closed source. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411651] New: New tool to export photos to Canon Irista
https://bugs.kde.org/show_bug.cgi?id=411651 Bug ID: 411651 Summary: New tool to export photos to Canon Irista Product: digikam Version: 5.9.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Plugin-Generic-WishForNewTools Assignee: digikam-bugs-n...@kde.org Reporter: eric.bru...@netcourrier.com Target Milestone: --- It would be nice to be able to export photos to the Canon Irista photo sharing website (https://www.irista.com), which is a nice alternative to sites like Flickr or Imgur. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390681] OFX import and unrecognized tag
https://bugs.kde.org/show_bug.cgi?id=390681 --- Comment #15 from Thomas Baumgart --- Nothing has changed since early July in the OFX parts, so it must be something else. Maybe, the bank sends slightly different data than before so that a different hash is computed. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 411650] New: Python plugin errors.
https://bugs.kde.org/show_bug.cgi?id=411650 Bug ID: 411650 Summary: Python plugin errors. Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: edpi...@orange.fr Target Milestone: --- Compiled latest git,tried latest extensions and others from falkon store, but got same error: TypeError: 'Shiboken.ObjectType' object is not iterable. 1) from toolbartools.Spacer import Spacer File "/home/edmond/.config/falkon/plugins/toolbartools/Spacer.py", line 20, in class Spacer(QtWidgets.QWidget): TypeError: 'Shiboken.ObjectType' object is not iterable Failed to import module "toolbartools" 2) File "/usr/lib64/qt5/plugins/falkon/runaction/__init__.py", line 18, in from .runaction import * File "/usr/lib64/qt5/plugins/falkon/runaction/runaction.py", line 20, in from runaction import actionmanager, button File "/usr/lib64/qt5/plugins/falkon/runaction/actionmanager.py", line 20, in import subprocess File "/usr/lib64/python3.8/subprocess.py", line 49, in import signal File "/usr/lib64/python3.8/signal.py", line 8, in IntEnum._convert_( File "/usr/lib64/python3.8/enum.py", line 461, in _convert_ cls = cls(name, members, module=module) File "/usr/lib64/python3.8/enum.py", line 306, in __call__ return cls._create_(value, names, module=module, qualname=qualname, type=type, start=start) File "/usr/lib64/python3.8/enum.py", line 416, in _create_ enum_class = metacls.__new__(metacls, class_name, bases, classdict) File "/usr/lib64/python3.8/enum.py", line 164, in __new__ enum_class = super().__new__(metacls, cls, bases, classdict) TypeError: 'Shiboken.ObjectType' object is not iterable Failed to import module "runaction" -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 411602] Unable to choose a file for all unsolved whitespace conflicts in 1.8
https://bugs.kde.org/show_bug.cgi?id=411602 michael changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 411472] kdiff3 cannot insert a blank line in 3way merge
https://bugs.kde.org/show_bug.cgi?id=411472 michael changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 411472] kdiff3 cannot insert a blank line in 3way merge
https://bugs.kde.org/show_bug.cgi?id=411472 michael changed: What|Removed |Added Attachment #122437|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411649] Audacious no longer recognized after update 5.16.5
https://bugs.kde.org/show_bug.cgi?id=411649 Aulos Plautius changed: What|Removed |Added CC||aulo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411649] New: Audacious no longer recognized after update 5.16.5
https://bugs.kde.org/show_bug.cgi?id=411649 Bug ID: 411649 Summary: Audacious no longer recognized after update 5.16.5 Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Media Player Assignee: k...@privat.broulik.de Reporter: aulo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 122513 --> https://bugs.kde.org/attachment.cgi?id=122513=edit Screenshot of Media Player and Audacious SUMMARY Media Player in the System Tray no longer recognizes Audacious as a media player, this includes control of Audacious via media keys. STEPS TO REPRODUCE 1. Open Audacious on Plasma 5.16.5-1 2. Click on the Media Player applet or attempt to control Audacious with the keyboard media keys. OBSERVED RESULT Media Player shows no active media player. Media keys doesn't works. EXPECTED RESULT Audacious should be displayed as a media player. Current music should be displayed in the Media Player. Media keys should pause/play and switch to previous/next song in playlist. SOFTWARE/OS VERSIONS OS/Kernel: Archlinux 5.2.11-arch1-1-ArCH KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Audacious: 3.10.1 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 409415] Freeze when opening edit dialog for second time
https://bugs.kde.org/show_bug.cgi?id=409415 Thomas Fischer changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|ASSIGNED|NEEDSINFO --- Comment #2 from Thomas Fischer --- Have you been able to test the suggestions I made in comment 1 on July 18? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 411648] New: Crash when creating a new shortcut
https://bugs.kde.org/show_bug.cgi?id=411648 Bug ID: 411648 Summary: Crash when creating a new shortcut Product: kstars Version: 3.3.4 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: marc.lan...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Go to the configure shortcuts tab 2. press input where you want to create your new shortcut 3. OBSERVED RESULT Kstars is closing without a warning after 2 seconds after the input click. When starting a new kstars session, the new shortcut is not present. When an existing shortcut is used, a warning message appear without a crash EXPECTED RESULT A new shortcut is created and appears in the list SOFTWARE/OS VERSIONS Windows: 10 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.
[kmail2] [Bug 411647] New: regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 Bug ID: 411647 Summary: regression: adding a new imap account prompts no error but no directory tree is created Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- I tried to add a new imap account. The process triggers no errors and everything seems fine. However, the directory tree (inbox, sent, etc) is not created. Tried several times with same result every time. This is an office 365 account, analogous to another I configured few months before with no issue, so I suppose this is some sort of regression. Also, adding the account to Trojita works just fine, so it doesn't seem to be something internal to the servers. Could you please try to add a new imap account to see if you can reproduce the issue in your system? Not sure if the issue in kmail is specific for office365 imap accounts or general. Any help is more than appreciated! SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 Kernel Version: 5.0.0-27-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.4 GiB -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 411646] New: Please consider adding a configuration to use local sagemath documentation
https://bugs.kde.org/show_bug.cgi?id=411646 Bug ID: 411646 Summary: Please consider adding a configuration to use local sagemath documentation Product: cantor Version: 19.08 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sage-backend Assignee: cantor-b...@kde.org Reporter: paulo.cesar.pereira.de.andr...@gmail.com Target Milestone: --- In newer cantor 19.08 several backends have an option to set a path to local documentation. Please consider adding it also for the sagemath backend. Both, the upstream sagemath tarball and at least Fedora sagemath provide local documentation. Upstream tarball is $SAGE_ROOT/local/share/doc/sage/html/$LANG/index.html and the Fedora package has it at $SAGE_ROOT/doc/html/$LANG/index.html -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 411645] New: Make sagemath backend compatible with sagemath built with python3
https://bugs.kde.org/show_bug.cgi?id=411645 Bug ID: 411645 Summary: Make sagemath backend compatible with sagemath built with python3 Product: cantor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sage-backend Assignee: cantor-b...@kde.org Reporter: paulo.cesar.pereira.de.andr...@gmail.com Target Milestone: --- Created attachment 122512 --> https://bugs.kde.org/attachment.cgi?id=122512=edit cantor-sagemath-python3.patch I am working on some updates to the Fedora sagemath package. This attached patch works with both, python2 and python3. The reason of the patch is self described below: $ python3 -c 'print 1, 2' File "", line 1 print 1, 2 ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(1, 2)? $ python3 -c 'print(1, 2)' 1 2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384469] [Regression] Not able to associate a notification sound to "This device can now be safely removed."
https://bugs.kde.org/show_bug.cgi?id=384469 --- Comment #1 from Paul --- Any chance of this being implemented I wonder. The audible notification was quite useful when copying large amounts of data to a USB drive, to bring to one's attention the fact all of the buffered data had been written. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 411644] New: Crash when hovering over a forward declared typedef'd struct
https://bugs.kde.org/show_bug.cgi?id=411644 Bug ID: 411644 Summary: Crash when hovering over a forward declared typedef'd struct Product: kdevelop Version: 5.4.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: krzysio.ku...@wp.pl Target Milestone: --- SUMMARY typedef struct Foo Foo; Hovering over the 2nd Foo will result in an immediate crash. STEPS TO REPRODUCE 1. Open a new source file with .cpp extension 2. Type in the above line 3. Hover over the last Foo OBSERVED RESULT Immediate crash EXPECTED RESULT A dialog popup with information about struct. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed 20190902 (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 411643] New: krunner crash
https://bugs.kde.org/show_bug.cgi?id=411643 Bug ID: 411643 Summary: krunner crash Product: krunner Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: hugo.klep...@gmail.com Target Milestone: --- Application: krunner (5.16.5) Qt Version: 5.13.0 Frameworks Version: 5.61.0 Operating System: Linux 5.2.11-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Trying to search for an installed application. - Unusual behavior I noticed: The keyboard shortcut to open krunner did not open the search window. I was able to search and open the application by just typing on an open desktop, which opened krunner and ran the search. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f94b9d89840 (LWP 3269))] Thread 24 (Thread 0x7f9445ffb700 (LWP 3292)): #0 0x7f94be2b4415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f94bef505a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f94bef50692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f94c09747bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f94c0974a6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f94bef4a520 in () at /usr/lib/libQt5Core.so.5 #6 0x7f94be2ae57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f94bebd70e3 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f94467fc700 (LWP 3291)): #0 0x7f94be2b4415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f94bef505a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f94bef50692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f94b0334309 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f94b0337d8b in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #22 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #23 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #24 0x7f94b0335ecc in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #25 0x7f94bef4a520 in () at /usr/lib/libQt5Core.so.5 #26 0x7f94be2ae57f in start_thread () at /usr/lib/libpthread.so.0 #27 0x7f94bebd70e3 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f9446ffd700 (LWP 3290)): #0 0x7f94be2b4415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f94bef505a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f94bef50692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f94b0334309 in
[Breeze] [Bug 411635] Add a folder-open-recent icon similar to document-open-recent
https://bugs.kde.org/show_bug.cgi?id=411635 Nate Graham changed: What|Removed |Added Assignee|visual-des...@kde.org |n...@kde.org --- Comment #1 from Nate Graham --- Working on this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 --- Comment #120 from Txutxifel --- I forgot to say I use vmware workstation;) Cheers -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 --- Comment #119 from Txutxifel --- Thanks, now my system works better after suspend I would like say that: -Sometimes y get a message after resume with: Desktop effects were restarted due to a graphics reset. I don't know if it's normal. -I found that vmware guests shows same composite problems as before. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411642] New: Mit der startet Dolphin mit leeren Verzeichnispfad. Start eines zweiten Dolphin-Fenster nicht möglich
https://bugs.kde.org/show_bug.cgi?id=411642 Bug ID: 411642 Summary: Mit der startet Dolphin mit leeren Verzeichnispfad. Start eines zweiten Dolphin-Fenster nicht möglich Product: dolphin Version: 19.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: schwarzweis...@gmx.de CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux Arch Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 (kompiliert gegen 5.13.0) ADDITIONAL INFORMATION Dolphin startet mit leeren Verzeichnispfad. Wir ein Pfad geöffnet und Dolphin wir ein zweites mal gestartet erscheint kein zweites Dolphin-Fenster sondern im ersten Fenster erscheint ein neuer Reiter mit leerem Verzeichnispfad. Wird die "Fenstereinstellung: Geteilte Ansicht" deaktiviert startet Dolphin im zweiten Fenster mit vorgegebenem Standart-Pfad. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 411641] New: Powerdevil settings UI looks messy
https://bugs.kde.org/show_bug.cgi?id=411641 Bug ID: 411641 Summary: Powerdevil settings UI looks messy Product: Powerdevil Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: matejm98m...@gmail.com Target Milestone: --- https://imgur.com/a/dYxuofi -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411603] Unable to key in number for Clip Speed
https://bugs.kde.org/show_bug.cgi?id=411603 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||Brainstorm+ Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from emohr --- Thank you for the very detailed reporting. Issue is opened for this: https://invent.kde.org/kde/kdenlive/issues/173. By clicking into the field you can adjust with the mouse wheel only. Or Change duration per keyboard via: Timeline > Current Clip > Edit Duration. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 195074] settings in $HOME/.kde/config/kdeglobals doesn't respect XDG_DATA_DIRS
https://bugs.kde.org/show_bug.cgi?id=195074 --- Comment #4 from Shmerl --- (In reply to Erik Quaeghebeur from comment #3) > (In reply to Shmerl from comment #2) > > But something still creates $HOME/.kde/config/kdeglobals for me (it's the > > only file remaining there now). > See Bug 405750. > (This is off-topic for this bug.) Ah, I see. Thanks. I commented there. Not sure why there is some resistance to actually fixing this for good. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411001] Brushes will not appear
https://bugs.kde.org/show_bug.cgi?id=411001 --- Comment #2 from zpodsch...@gmail.com --- Sorry for the late reply, Yes, I do have the brush preset tag selected in the docker, the problem is that Im limited to 3 brushes atm (standard pencil brush, eraser, and an ink brush), opposed to the extensive library of brushes i had previously. On Tue, Aug 27, 2019 at 8:26 AM Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=411001 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > CC||b...@valdyas.org > > --- Comment #1 from Boudewijn Rempt --- > Hi, > > Do you have any tag selected in the brush preset docker? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410254] Clipboard from platform to OS doesn't work 100% of the time
https://bugs.kde.org/show_bug.cgi?id=410254 deadite66 changed: What|Removed |Added CC||lee295...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 408350] Dolphin crashes on copy overwrite skip all existing files
https://bugs.kde.org/show_bug.cgi?id=408350 David Faure changed: What|Removed |Added Latest Commit||https://commits.kde.org/kio ||/4306dce1e8d9ca61ef5b7246bd ||602e21a5e63621 Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||5.62.0 --- Comment #1 from David Faure --- Git commit 4306dce1e8d9ca61ef5b7246bd602e21a5e63621 by David Faure, on behalf of Ahmad Samir. Committed on 06/09/2019 at 14:07. Pushed by dfaure into branch 'master'. [CopyJob] Fix crash when copying an already existing dir and pressing "Skip" Summary: In copyNextFile() if all files have been skipped QList::erase() will return end() iterator, accessing the element it denotes will cause a segmentation fault. Make sure the iterator is valid if it's changed inside the while loop, if we're going to use it before control reaches the loop condition. Add a unit test. FIXED-IN: 5.62.0 Test Plan: kioclient5 copy SOME_DIR_WITH_FILES DEST kioclient5 copy --interactive SOME_DIR_WITH_FILES DEST - In the "folder already exists" dialog enable "Apply to all" then hit "Skip" - Without the patch you'd get a segmentation fault, with the patch the copy should finish as expected All unit tests passed (except kiocore-kacltest, but that's unrelated). Reviewers: #frameworks, dfaure Reviewed By: dfaure Subscribers: kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D23708 M +31 -0autotests/jobtest.cpp M +2-0autotests/jobtest.h M +1-1src/core/copyjob.cpp https://commits.kde.org/kio/4306dce1e8d9ca61ef5b7246bd602e21a5e63621 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411484] Speed change on extracted footage renders to white screen
https://bugs.kde.org/show_bug.cgi?id=411484 --- Comment #8 from emohr --- I like to open an issue in our tracker. Could you just make another test? Create a new project with 25fps or 50fps and import the section out of the 100fps clip. This to see if this is a pull/down issue (100fps devided by 30fps = 3.1/3). Still the same behavior? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 411635] Add a folder-open-recent icon similar to document-open-recent
https://bugs.kde.org/show_bug.cgi?id=411635 Nate Graham changed: What|Removed |Added CC||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it
https://bugs.kde.org/show_bug.cgi?id=370975 --- Comment #56 from Nate Graham --- There is nothing KDE can do about that. You should contact the Kubuntu people about it. See for example the related request for another Solid backport: https://phabricator.kde.org/T9525 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411536] Weird resize crash only when specific values are used
https://bugs.kde.org/show_bug.cgi?id=411536 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/0f9c5472581252 ||a6c5e34ec912a292138d960ef8 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #5 from Dmitry Kazakov --- Git commit 0f9c5472581252a6c5e34ec912a292138d960ef8 by Dmitry Kazakov. Committed on 06/09/2019 at 13:46. Pushed by dkazakov into branch 'master'. Fix crash after cropping a specific image This patch ends the era of the custom "empty extent" value QRect(quint32_MAX, quint32_MAX, 0, 0). When I started refactoring tile engine ten years ago in 2009, this "empty extent" flag was already present. It was just a result of the way how extent was calculated those days. I guess it was also considered as an "optimization", or as "a flag" that could ease debugging a bit (and it actually did help debugging a couple of times). Years passed by and I considered to remove this custom value multiple times. It was always causing troubles, because the QRect is not safe against integer oveflows. But the problem was, there was code outside tiles engine that relied on this behavior. So I was always scared of the actual removal. Even when the tile engine was rewritten again to become lockfree in 2017, I insisted on keeping the old behavior... So, it looks like now all code that relies on this custom value is gone, so it should be safe to remove it. Funny side, I guess it was one of few artifacts that were still kept in Krita since 'tiles' and 'tiles_new' days (has anyone ever wondered why the engine's folder is called 'tiles3'?) ;) M +9-9libs/image/tests/kis_iterator_test.cpp M +11 -11 libs/image/tests/kis_iterators_ng_test.cpp M +10 -10 libs/image/tiles3/KisTiledExtentManager.cpp M +14 -4libs/image/tiles3/kis_memento.h M +1-1libs/image/tiles3/tests/kis_tiled_data_manager_test.cpp https://invent.kde.org/kde/krita/commit/0f9c5472581252a6c5e34ec912a292138d960ef8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it
https://bugs.kde.org/show_bug.cgi?id=370975 Claudio changed: What|Removed |Added CC||claudiolancone...@gmail.com Platform|Manjaro |Kubuntu Packages --- Comment #55 from Claudio --- Kubuntu 18.04.3 LTS still has this annoying bug. solid version 5.44 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411640] New: Could not create collection trash, resourceId: 8
https://bugs.kde.org/show_bug.cgi?id=411640 Bug ID: 411640 Summary: Could not create collection trash, resourceId: 8 Product: kmail2 Version: 5.9.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: jor...@gmail.com Target Milestone: --- Kmail has suddenly become disfunctional. When I launch it, it immediately terminates with the message: Im E-Mail-Programm ist ein schwerwiegender Fehler aufgetreten. Das Programm wird beendet. Die Fehlermeldung lautet: Could not create collection trash, resourceId: 8 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian: GNU Linux Buster KDE Plasma Version: 5.14.5.1 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 410604] GIMP - theme problem when starting via Desktop icon or via Application Launcher
https://bugs.kde.org/show_bug.cgi?id=410604 --- Comment #4 from valentin --- The same happens when open a file through Dolphin with "Open with" -> GIMP -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 402910] Need preferences-desktop-navigation icon
https://bugs.kde.org/show_bug.cgi?id=402910
Björn Feber changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/bre
||eze-icons/debde7d66d896c310
||4813981bc5c2106f4ae34fd
Status|REPORTED|RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Björn Feber ---
Git commit debde7d66d896c3104813981bc5c2106f4ae34fd by Björn Feber.
Committed on 06/09/2019 at 12:04.
Pushed by bfeber into branch 'master'.
Add "preferences-desktop-navigation" icon
Summary:
{F7324021}
Test Plan: Search for "preferences-desktop-navigation" in Cuttlefish.
Reviewers: #vdg, ndavis
Reviewed By: #vdg, ndavis
Subscribers: kde-frameworks-devel, #vdg
Tags: #frameworks
Differential Revision: https://phabricator.kde.org/D23749
A +39 -0icons-dark/preferences/32/preferences-desktop-navigation.svg
A +39 -0icons/preferences/32/preferences-desktop-navigation.svg
https://commits.kde.org/breeze-icons/debde7d66d896c3104813981bc5c2106f4ae34fd
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 410254] Clipboard from platform to OS doesn't work 100% of the time
https://bugs.kde.org/show_bug.cgi?id=410254 --- Comment #4 from Nicolas Fella --- I don't think that helps us in any way here -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410254] Clipboard from platform to OS doesn't work 100% of the time
https://bugs.kde.org/show_bug.cgi?id=410254 bstallma...@gmail.com changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from bstallma...@gmail.com --- Is it possible for the KDE android app the ask for admin app permissions on Android from now on and utilize it? -- You are receiving this mail because: You are watching all bug changes.
