[krita] [Bug 393865] Brush delay
https://bugs.kde.org/show_bug.cgi?id=393865
mvowada changed:
What|Removed |Added
CC||freebo...@tiscali.it
--- Comment #1 from mvowada ---
Hi.
It sounds like you have the ("Tool Options" docker) > "Brush Smoothing" >
"Stabilizer" > "Delay" option, set. Please, retry after unchecking it.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 393788] Window rules editing broken
https://bugs.kde.org/show_bug.cgi?id=393788 Martin Flöser changed: What|Removed |Added Flags||Wayland+, X11+, ||ReviewRequest+ Keywords||regression, reproducible URL||https://phabricator.kde.org ||/D12706 --- Comment #4 from Martin Flöser --- I found the change which introduced the regression and have a patch for it: https://phabricator.kde.org/D12706 Luckily it's only in master branch. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 393868] New: Markdown backend: Configure: Change font size does not update number of pages
https://bugs.kde.org/show_bug.cgi?id=393868 Bug ID: 393868 Summary: Markdown backend: Configure: Change font size does not update number of pages Product: okular Version: 1.3.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: codestr...@posteo.org Target Milestone: --- STEPS: 1. Open an md file 2. Settings --> Configure Backends... --> Markdown 3. Change the font size RESULT: The number of rendered pages stays the same. If the font size was reduced there are empty pages at the end. If the font size was increased, content is missing at the end. WORKAROUND: Close Okular and reopen with the same file. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 393869] New: Markdown backend: Set page format
https://bugs.kde.org/show_bug.cgi?id=393869 Bug ID: 393869 Summary: Markdown backend: Set page format Product: okular Version: 1.3.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: codestr...@posteo.org Target Milestone: --- I discovered that Okular and the Markdown backend do a pretty good job in rendering markdown to pdf including clickable hyperlinks: Open md file and use File -> Export -> PDF. It would be nice if the output paper format was configurable. On my system it seems to be fixed at A4. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 393868] Markdown backend: Configure: Change font size does not update number of pages
https://bugs.kde.org/show_bug.cgi?id=393868 Julian Wolff changed: What|Removed |Added Resolution|--- |DUPLICATE CC||wo...@julianwolff.de Status|UNCONFIRMED |RESOLVED --- Comment #1 from Julian Wolff --- *** This bug has been marked as a duplicate of bug 384070 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384070] Text based genertors need reloading the file after font size change
https://bugs.kde.org/show_bug.cgi?id=384070 Julian Wolff changed: What|Removed |Added CC||codestr...@posteo.org --- Comment #1 from Julian Wolff --- *** Bug 393868 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393870] New: Crash of Plasma when battery reaches low level
https://bugs.kde.org/show_bug.cgi?id=393870 Bug ID: 393870 Summary: Crash of Plasma when battery reaches low level Product: plasmashell Version: 5.12.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: carlon.l...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.4) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-20-generic x86_64 Distribution: Ubuntu 18.04 LTS -- Information about the crash: Plasma suddenly crashed when working. I'm not completely sure, but I suspect this happened when the battery reached low level. The screen dimmed and suddenly the dialog appeared. Please note that it may also not be related. This happened on wayland but never happened on X11. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcc4ad00800 (LWP 13067))] Thread 13 (Thread 0x7fcb59a4a700 (LWP 15449)): #0 0x7fcc43b699f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x555ae2099534) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fcc43b699f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x555ae20994e0, cond=0x555ae2099508) at pthread_cond_wait.c:502 #2 0x7fcc43b699f3 in __pthread_cond_wait (cond=0x555ae2099508, mutex=0x555ae20994e0) at pthread_cond_wait.c:655 #3 0x7fcc449e859b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcc4876d548 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fcc4876d9aa in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fcc449e716d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fcc43b636db in start_thread (arg=0x7fcb59a4a700) at pthread_create.c:463 #8 0x7fcc442dd88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fcb750db700 (LWP 14252)): #0 0x7fcc43b699f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x555adbedb140) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fcc43b699f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x555adbedb0f0, cond=0x555adbedb118) at pthread_cond_wait.c:502 #2 0x7fcc43b699f3 in __pthread_cond_wait (cond=0x555adbedb118, mutex=0x555adbedb0f0) at pthread_cond_wait.c:655 #3 0x7fcc449e859b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcc4876d548 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fcc4876d9aa in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fcc449e716d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fcc43b636db in start_thread (arg=0x7fcb750db700) at pthread_create.c:463 #8 0x7fcc442dd88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fcb75d01700 (LWP 14112)): #0 0x7fcc43b699f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x555ada5b16e4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fcc43b699f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x555ada5b1690, cond=0x555ada5b16b8) at pthread_cond_wait.c:502 #2 0x7fcc43b699f3 in __pthread_cond_wait (cond=0x555ada5b16b8, mutex=0x555ada5b1690) at pthread_cond_wait.c:655 #3 0x7fcc449e859b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcc4876d548 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fcc4876d9aa in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fcc449e716d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fcc43b636db in start_thread (arg=0x7fcb75d01700) at pthread_create.c:463 #8 0x7fcc442dd88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fcb748da700 (LWP 13595)): #0 0x7fcc43b699f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x555ad85f42d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fcc43b699f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x555ad85f4280, cond=0x555ad85f42a8) at pthread_cond_wait.c:502 #2 0x7fcc43b699f3 in __pthread_cond_wait (cond=0x555ad85f42a8, mutex=0x555ad85f4280) at pthread_cond_wait.c:655 #3 0x7fcc449e859b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcc4876d548 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fcc4876d9aa in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fcc449e716d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fcc43b636db in start_thread (arg=0x7fcb748da700) at pthread_create.c:463
[okular] [Bug 393833] Okular crashed when recompile latex file
https://bugs.kde.org/show_bug.cgi?id=393833 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||aa...@kde.org Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Albert Astals Cid --- You okular is very old, please try on something that is not more than 2 years old. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393871] New: plasma crash
https://bugs.kde.org/show_bug.cgi?id=393871 Bug ID: 393871 Summary: plasma crash Product: plasmashell Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mariusz.lib...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.5) Qt Version: 5.10.1 Frameworks Version: 5.45.0 Operating System: Linux 4.16.5-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: just browsing the web in firefox, a few seconds after my laptop resumed from suspend -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f47e688a800 (LWP 21376))] Thread 25 (Thread 0x7f467bcff700 (LWP 8103)): #0 0x7f47dfddbcd9 in poll () at /usr/lib/libc.so.6 #1 0x7f47da65a523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f47da65a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f47e072a254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f47e06cc31b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f47e04db71e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f47e04e0abd in () at /usr/lib/libQt5Core.so.5 #7 0x7f47df6960bc in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f47dfde62ff in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f4714815700 (LWP 8077)): #0 0x7f47dfddbcd9 in poll () at /usr/lib/libc.so.6 #1 0x7f47da65a523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f47da65a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f47e072a254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f47e06cc31b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f47e04db71e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f47e04e0abd in () at /usr/lib/libQt5Core.so.5 #7 0x7f47df6960bc in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f47dfde62ff in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f46eb7ff700 (LWP 8076)): #0 0x7f47dfdd7734 in read () at /usr/lib/libc.so.6 #1 0x7f47da69fed1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f47da659ff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f47da65a4c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f47da65a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f47e072a254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f47e06cc31b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f47e04db71e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f47e04e0abd in () at /usr/lib/libQt5Core.so.5 #9 0x7f47df6960bc in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f47dfde62ff in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f4715c4a700 (LWP 8075)): #0 0x7f47dfddbcd9 in poll () at /usr/lib/libc.so.6 #1 0x7f47da65a523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f47da65a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f47e072a254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f47e06cc31b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f47e04db71e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f47e04e0abd in () at /usr/lib/libQt5Core.so.5 #7 0x7f47df6960bc in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f47dfde62ff in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f46b5ffb700 (LWP 4556)): #0 0x7f47dfddbcd9 in poll () at /usr/lib/libc.so.6 #1 0x7f47d481b773 in () at /usr/lib/libpulse.so.0 #2 0x7f47d480cbd0 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7f47d480d271 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f47d480d301 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f47d481b6ae in () at /usr/lib/libpulse.so.0 #6 0x7f47d3f8c81c in () at /usr/lib/pulseaudio/libpulsecommon-11.1.so #7 0x7f47df6960bc in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f47dfde62ff in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f46b67fc700 (LWP 31835)): #0 0x7f47df69c07c in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f47e04e1f9c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f471ee7752f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f471ee7b
[kwallet-pam] [Bug 393856] patches for CVE-2018-10380 "Access to privileged files" break access to existing wallets
https://bugs.kde.org/show_bug.cgi?id=393856 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from Albert Astals Cid --- For some reason https://cgit.kde.org/kwallet-pam.git/commit/?id=8da1a47035fc92bc1496059583772bc4bd6e8ba6 didn't close this -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 393856] patches for CVE-2018-10380 "Access to privileged files" break access to existing wallets
https://bugs.kde.org/show_bug.cgi?id=393856 Maximiliano Curia changed: What|Removed |Added CC||m...@gnuservers.com.ar Latest Commit||https://commits.kde.org/kwa ||llet-pam/8da1a47035fc92bc14 ||96059583772bc4bd6e8ba6 --- Comment #6 from Maximiliano Curia --- Git commit 8da1a47035fc92bc1496059583772bc4bd6e8ba6 by Maximiliano Curia. Committed on 05/05/2018 at 10:00. Pushed by maximilianocuria into branch 'Plasma/5.12'. Avoid giving an stderr to kwallet Summary: The fixes for CVE-2018-10380 introduced a regression for most users not using kde, and some for kde sessions. In particular the reorder of the close calls and creating a new socket caused that the socket is always assigned the file descriptor 2, aka stderr. Test Plan: It works Reviewers: #plasma, aacid Reviewed By: aacid Subscribers: asturmlechner, rdieter, davidedmundson, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D12702 M +4-1pam_kwallet.c https://commits.kde.org/kwallet-pam/8da1a47035fc92bc1496059583772bc4bd6e8ba6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393865] Brush delay
https://bugs.kde.org/show_bug.cgi?id=393865 Boudewijn Rempt changed: What|Removed |Added Platform|Windows CE |MS Windows Resolution|--- |INVALID CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Boudewijn Rempt --- That sounds very likely. Note also that we've just released 4.0.1, so you might want to update as well. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 393866] missing progress bar
https://bugs.kde.org/show_bug.cgi?id=393866 --- Comment #3 from Todd --- (In reply to Todd from comment #2) > Where exactly? Just did a massive transfer. No sign on a progress indicator anywhere. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 343089] sidebar state forgotten on reload
https://bugs.kde.org/show_bug.cgi?id=343089 thekswen...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from thekswen...@gmail.com --- This bug seems to be fixed in Okular 1.3.3. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 393872] New: sidebar state forgotten when forward search used
https://bugs.kde.org/show_bug.cgi?id=393872 Bug ID: 393872 Summary: sidebar state forgotten when forward search used Product: okular Version: 1.3.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: thekswen...@gmail.com Target Milestone: --- I use vimtex to edit my latex documents. The forward-search feature is very useful in that it bring Okular to the front while moving the page to the current position of the cursor in vim. Unfortunately the sidebar switches state upon refresh. So if I'm in the thumbnails view, which I always am in, Okular switches to contents view. This problem is similar to the one that has been fixed: https://bugs.kde.org/show_bug.cgi?id=343089 It is related to the family of requests for Okular to remember which sidebar is used for each document: https://bugs.kde.org/show_bug.cgi?id=342094 https://bugs.kde.org/show_bug.cgi?id=335189 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 375467] Cantor hangs at "Initializing Session" when choosing Sage backend (Sage version 7.6)
https://bugs.kde.org/show_bug.cgi?id=375467 Alexander Semke changed: What|Removed |Added Assignee|fil...@kde.org |alexander.se...@web.de CC||alexander.se...@web.de --- Comment #7 from Alexander Semke --- (In reply to Kishore Gopalakrishnan from comment #6) > (In reply to Antonio Rojas from comment #5) > > With Cantor 17.08.3 and sage 8.0 on Arch linux, if I run 'cantor -b sage' > from a terminal, there is no terminal output, and Cantor opens, but keeps on > showing the 'initialising Session' dialog box. The communication with Sage was made more stable in 18.04. Can you please check the current release? Do you still have problems with Sage? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393871] plasma crash
https://bugs.kde.org/show_bug.cgi?id=393871 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393870] Crash of Plasma when battery reaches low level
https://bugs.kde.org/show_bug.cgi?id=393870 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 379404] Cantor can't initialize session for maxima backend
https://bugs.kde.org/show_bug.cgi?id=379404 --- Comment #12 from Alexander Semke --- (In reply to hackitforfun from comment #11) > Created attachment 112419 [details] > attachment-13196-0.html > > I confirm that maxima session can be inititiated. > However, I have to manually interrupt the backend (in this case maxima) in > order to do the next calculation. This is not normal, isn't it ? This is not normal, of course. I cannot reproduce this. Do you always have this behavior or for some certain commands only? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 393873] New: Monitors can't be set up with their bottoms aligned
https://bugs.kde.org/show_bug.cgi?id=393873 Bug ID: 393873 Summary: Monitors can't be set up with their bottoms aligned Product: KScreen Version: 5.12.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: haagch.christ...@googlemail.com Target Milestone: --- Created attachment 112423 --> https://bugs.kde.org/attachment.cgi?id=112423&action=edit video of aligning issue This may only happen with monitors with a small difference in vertical resolution. In my case the left primary monitor is 1920x1080 and the right monitor is 1280x1024. The attached video shows how the right screen is snapping to a vertical offset of 28 and 104 and nothing in between so it's impossible to drag it to the position where bottoms would line up, which is probably at a vertical offset of 1080-1024=56. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 393874] New: When i wanna touch settings of software center, the center crashes!
https://bugs.kde.org/show_bug.cgi?id=393874 Bug ID: 393874 Summary: When i wanna touch settings of software center, the center crashes! Product: Discover Version: 5.12.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: nuaanjz...@163.com Target Milestone: --- Application: plasma-discover (5.12.4) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-20-generic x86_64 Distribution: Ubuntu 18.04 LTS -- Information about the crash: - What I was doing when the application crashed: i wanna config something of software center; i touch settings then crash!! The crash can be reproduced every time. -- Backtrace: Application: 发现者 (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdd1f295f40 (LWP 2149))] Thread 9 (Thread 0x7fdcd70c2700 (LWP 2159)): #0 0x7fdd1a97ebf9 in __GI___poll (fds=0x7fdcd0002960, nfds=1, timeout=114575) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fdd1526d439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdd1526d54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdd1b2cc90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdd1b2719ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdd1b09022a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdd1b09516d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fdd171926db in start_thread (arg=0x7fdcd70c2700) at pthread_create.c:463 #8 0x7fdd1a98b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fdce651c700 (LWP 2157)): #0 0x7fdd17198ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fdce651bc40, expected=0, futex_word=0x7fdcd8006df4) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fdce651bd00, mutex=0x7fdcd8006da0, cond=0x7fdcd8006dc8) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fdcd8006dc8, mutex=0x7fdcd8006da0, abstime=0x7fdce651bd00) at pthread_cond_wait.c:667 #3 0x7fdd1b096458 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdd1b09252d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdd1b09516d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdd171926db in start_thread (arg=0x7fdce651c700) at pthread_create.c:463 #7 0x7fdd1a98b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fdce6d1d700 (LWP 2156)): #0 0x7fdd152b2cf4 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fdd1526ce49 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdd1526d3e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdd1526d54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fdd1b2cc90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdd1b2719ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdd1b09022a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fdd1b09516d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdd171926db in start_thread (arg=0x7fdce6d1d700) at pthread_create.c:463 #9 0x7fdd1a98b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fdce829e700 (LWP 2155)): #0 _dl_update_slotinfo (req_modid=1) at ../elf/dl-tls.c:643 #1 0x7fdd1f0c687c in update_get_addr (ti=0x7fdd1b72e6a0) at ../elf/dl-tls.c:799 #2 0x7fdd1f0cca28 in __tls_get_addr () at ../sysdeps/x86_64/tls_get_addr.S:55 #3 0x7fdd1b093ff6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdd1b2cc80a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdd1526c998 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fdd1526d36b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fdd1526d54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fdd1b2cc90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fdd1b2719ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fdd1b09022a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fdd1b09516d in ?? () from /usr/lib/x8
[systemsettings] [Bug 393403] Application launcher global shortcuts get assigned to random neighbours
https://bugs.kde.org/show_bug.cgi?id=393403 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388409] KMail crashed after closing after it hung at Retrieving Folder Contents
https://bugs.kde.org/show_bug.cgi?id=388409 M. Raymond Vaughn changed: What|Removed |Added CC||nethers...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388409] KMail crashed after closing after it hung at Retrieving Folder Contents
https://bugs.kde.org/show_bug.cgi?id=388409 --- Comment #3 from M. Raymond Vaughn --- Created attachment 112424 --> https://bugs.kde.org/attachment.cgi?id=112424&action=edit New crash information added by DrKonqi kmail (5.7.3) using Qt 5.9.4 - What I was doing when the application crashed: attempted to close KMail while it was hanging on "Retrieving Folder Contents" and unable to display the contents of any individual message. -- Backtrace (Reduced): #8 0x7f55a0ed6e69 in QMainWindow::statusBar() const () from /usr/lib64/libQt5Widgets.so.5 #9 0x7f55a1eb0fb1 in KMMainWin::displayStatusMessage(QString const&) () from /usr/lib64/libkmailprivate.so.5 [...] #11 0x7f5596a54c52 in KPIM::BroadcastStatus::statusMsg(QString const&) () from /usr/lib64/libKF5Libkdepim.so.5 #12 0x7f55a1ee5ee4 in KMMainWidget::showMessageActivities(QString const&) () from /usr/lib64/libkmailprivate.so.5 #13 0x7f55a1ee8ff3 in KMMainWidget::itemsFetchDone(KJob*) () from /usr/lib64/libkmailprivate.so.5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 393875] New: ItemAccessors doesn't work with signals
https://bugs.kde.org/show_bug.cgi?id=393875 Bug ID: 393875 Summary: ItemAccessors doesn't work with signals Product: frameworks-kconfig Version: 5.45.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: matt...@mjdsystems.ca Reporter: jakub.jakub.no...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Overview: If we specify ItemAccessors=true in kcfgc and use both signals it produces compilation errors during "make" phase. By "use signals" I mean adding emit tag to entry or using GenerateProperties=true option in kcfgc. Minimal Working Example: https://gist.github.com/MrQubo/ea4acf1aa7ff794f3d42f4e5b5c84368 The exact errors message for this MWE is https://paste.kde.org/pemq0mt6d. Additional informations: We have to add Mutators, because without that signals won't be generated. The error occures because ItemAccessors generates fields of types ItemBool, ItemString etc while in .cpp file it tries to assign variable of type KConfigCompilerSignallingItem to those fields. Possible solution: I'll refer to MWE as an example. The type of mExampleItem should be changed to KConfigSkeletonItem. Function exampleItem() should return the mItem property from KConfigCompilerSignallingItem or the mExampleItem itself casted to correct type (depending on the actual underlying type of mExampleItem). Build Date & Platform: Linux 4.16.5-1-ARCH Thu Apr 26 16:53:40 UTC 2018 x86_64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 393875] ItemAccessors doesn't work with signals
https://bugs.kde.org/show_bug.cgi?id=393875 Jakub Nowak changed: What|Removed |Added CC||jakub.jakub.no...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393149] Transformed windows have gray line between contents and borders
https://bugs.kde.org/show_bug.cgi?id=393149 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 393194] Middle click paste content of clipboard
https://bugs.kde.org/show_bug.cgi?id=393194 Jakub Nowak changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Jakub Nowak --- It looks like there's a setting for this in yakuake. Just edit profile, go to "Mouse" tab and the "Mouse middle button" setting is there. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 393839] Scrollbar background is missing
https://bugs.kde.org/show_bug.cgi?id=393839 --- Comment #1 from Kurt Hindenburg --- Can you provide your profile/colorscheme and perhaps a screenshot please? -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 55111] Don't interrupt batch file copy on errors
https://bugs.kde.org/show_bug.cgi?id=55111 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #6 from Dr. Chapatin --- still an issue on Arch Linux, kio 5.45, it affects both local and remote (via Samba) file copy. File operation does not continue in background when a file conflict dialog appears. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 393844] Yakuake always opens regardless of preferences
https://bugs.kde.org/show_bug.cgi?id=393844 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Dr. Chapatin --- cannot confirm such behavior on Arch Linux. Yakuake starts at login but its window remains hidden until I press the shortcut to invoke it. yakuake 3.0.5 plasma 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 393876] New: A solution to USB connection problems
https://bugs.kde.org/show_bug.cgi?id=393876 Bug ID: 393876 Summary: A solution to USB connection problems Product: kstars Version: 2.9.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jcjes...@free.fr Target Milestone: --- This is not a bug but a solution to USB connection problems. Since I've been interested in astrophotography, I've encountered USB connection problems. I'm on a Mac (and don't want to use Windows) and I've read in forums that USB connection problems were a "feature" of Apple computers. Why ? Nobody said why. I've been using several softwares (among them KStars and TheSkyX). Because these two softwares can manage a lot of devices (scope, dome, cameras, focusers, guiders...), they are also the place where I've encountered USB problems. Sometimes everything was working perfectly, and sometimes NO device could connect. On my Mac (MacBook Pro, mid 2014) there are two USB ports, one on each side of the computer. I used the one on the left side of the computer. When for some reason no device could connect to KStars, I swapped to the right side USB port ... and everything mounted correctly. I've been told that a similar situation is found on Windows computers. Now I'm using only the right side USB port and all devices mount correctly and immediately. I hope this will help others ! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 393876] A solution to USB connection problems
https://bugs.kde.org/show_bug.cgi?id=393876 --- Comment #1 from Jasem Mutlaq --- Thanks for the report Jean-Claude. Maybe post this information on INDI forum so that it can get to more people? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 393876] A solution to USB connection problems
https://bugs.kde.org/show_bug.cgi?id=393876 --- Comment #2 from Jean-Claude --- (In reply to Jasem Mutlaq from comment #1) > Thanks for the report Jean-Claude. Maybe post this information on INDI forum > so that it can get to more people? OK, I will do it Jasem. (By the way, this USB connection problem could have been at the origin of the Microtouch focuser problem we tried to solve the other day !) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393877] New: Shortcut creation only takes effect after user restarts session
https://bugs.kde.org/show_bug.cgi?id=393877 Bug ID: 393877 Summary: Shortcut creation only takes effect after user restarts session Product: systemsettings Version: 5.12.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_keys Assignee: k...@michael-jansen.biz Reporter: yst...@posteo.net Target Milestone: --- WHAT I DID: 1. Launched Global shortcuts from System Settings → Workspace → Keyboard shortcuts → Global shortcuts (or 'kcmshell5 keys') 2. Chose + button, searched for an application (Lokalize), and set its shortcut to Ctrl+Alt+D 3. Chose OK. 4. Tried the shortcut, nothing happened. 5. Logged out and then logged in. 6. Shortcut works! (Tried with other apps and shortcut combos too). **Changing a shortcut of an already-listed entry is not affected (gets applied as expected)** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393877] Shortcut creation only takes effect after user restarts session
https://bugs.kde.org/show_bug.cgi?id=393877 yst...@posteo.net changed: What|Removed |Added CC||yst...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 391243] New web shortcuts take effect only after user restarts sessions
https://bugs.kde.org/show_bug.cgi?id=391243 --- Comment #1 from yst...@posteo.net --- Shortcut **change** of an already-listed item works as expected. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 391243] New web shortcuts take effect only after user restarts sessions
https://bugs.kde.org/show_bug.cgi?id=391243 yst...@posteo.net changed: What|Removed |Added Version|5.12.2 |5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 358231] desktop locks up when moving files
https://bugs.kde.org/show_bug.cgi?id=358231 Dr. Chapatin changed: What|Removed |Added CC||nick.craig@gmail.com --- Comment #12 from Dr. Chapatin --- *** Bug 393748 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393748] Plasma freezes on multiple file CUT - Length of time determined by number of file
https://bugs.kde.org/show_bug.cgi?id=393748 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #6 from Dr. Chapatin --- I can confirm that it's fixed in plasma 5.13 dev. \o/ *** This bug has been marked as a duplicate of bug 358231 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 386959] Properties view: wrong creation date [patch]
https://bugs.kde.org/show_bug.cgi?id=386959 Maik Qualmann changed: What|Removed |Added Attachment #112203|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393877] Shortcut creation only takes effect after user restarts session
https://bugs.kde.org/show_bug.cgi?id=393877 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392749] Moving windows stutters the entire desktop
https://bugs.kde.org/show_bug.cgi?id=392749 --- Comment #16 from Alexey Min --- Can't reproduce this anymore with kernel 4.16.7 (both X11 and wayland). Just tested with kernel 4.16.3, both X11 and wayland had this. Bart Ribbers can you test? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 393878] New: When I install an application the software center does not respect the system language
https://bugs.kde.org/show_bug.cgi?id=393878 Bug ID: 393878 Summary: When I install an application the software center does not respect the system language Product: Discover Version: 5.12.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: emanu@gmail.com Target Milestone: --- When I install an application the software center does not respect the system language (in my case LibreOffice), an expert user who knows how to do it, type: "sudo apt install libreoffice-l10n-it" and has the language in Italian or other language, but an impractical user (who is the user to whom a software center is addressed) finds himself with the language in English. I'm reporting this bug because a user on a forum complained about LibreOffice that is not installed with the system language, but it is in English, and because the same thing happened to me from plasma discover, I had to install the language from the terminal. can you do something about it? (I hope I explained myself well, because I'm writing with google translator) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 386959] Properties view: wrong creation date [patch]
https://bugs.kde.org/show_bug.cgi?id=386959 Maik Qualmann changed: What|Removed |Added Version Fixed In||6.0.0 Latest Commit|https://commits.kde.org/dig |https://commits.kde.org/dig |ikam/ff0fb215633010d563083c |ikam/0e8da899d20a4549e41cff |33e35d45b17d3484f0 |d83a488c85fa7ad85f Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #18 from Maik Qualmann --- Git commit 0e8da899d20a4549e41cffd83a488c85fa7ad85f by Maik Qualmann. Committed on 05/05/2018 at 15:35. Pushed by mqualmann into branch 'master'. check if a date exists more than once and use it FIXED-IN: 6.0.0 M +2-1NEWS M +113 -30 core/libs/dmetadata/metaengine_image.cpp https://commits.kde.org/digikam/0e8da899d20a4549e41cffd83a488c85fa7ad85f -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 393874] When i wanna touch settings of software center, the center crashes!
https://bugs.kde.org/show_bug.cgi?id=393874 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 393775] Problem connecting Maxdome II since KSatrs v. 2.9.4
https://bugs.kde.org/show_bug.cgi?id=393775 Juan M.B. changed: What|Removed |Added CC||jua...@gmail.com --- Comment #1 from Juan M.B. --- I made some changes to the INDI MaxDome II driver on december, 2017. I don't know if this problem could be related to my changes. I have tested the driver extensively, but I am not using a real MaxDome II board. I use an Arduino-based controller implementing the MaxDome II protocol. I could make some tests with a proper MaxDome board, but it could take me some time. Which versions of indilib are causing problems? You can check the version by typing "indiserver" in a terminal. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 393738] Many "timeline:" and "search:" URLs no longer work
https://bugs.kde.org/show_bug.cgi?id=393738 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 393876] A solution to USB connection problems
https://bugs.kde.org/show_bug.cgi?id=393876 Jasem Mutlaq changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393803] Dolphin crash on moving files to SMB drive
https://bugs.kde.org/show_bug.cgi?id=393803 Elvis Angelaccio changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Elvis Angelaccio --- *** This bug has been marked as a duplicate of bug 364039 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 364039] Dolphin crashed on file transfer
https://bugs.kde.org/show_bug.cgi?id=364039 Elvis Angelaccio changed: What|Removed |Added CC||p...@btinternet.com --- Comment #61 from Elvis Angelaccio --- *** Bug 393803 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393670] Dolphin not using previous configuration (dolphinui.rc version number needs update)
https://bugs.kde.org/show_bug.cgi?id=393670 --- Comment #4 from Elvis Angelaccio --- Weird, actually we don't install the dolphinui.rc file anymore (since 17.08). Where did you had to increase the version number? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392749] Moving windows stutters the entire desktop
https://bugs.kde.org/show_bug.cgi?id=392749 Bart Ribbers changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #17 from Bart Ribbers --- You're right, I can confirm that the issue is gone on 4.16.7. Thanks for reporting it! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita
https://bugs.kde.org/show_bug.cgi?id=365222 Nicole changed: What|Removed |Added CC||nicolebro...@alumni.nd.edu --- Comment #15 from Nicole --- I'm on 4.0.0 and Windows 10 and this is still happening. Are there any plans to iron out this bug? It's rather frustrating to have to re-configure the window every time I restart the program. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 90318] I can burn audio and data projects, but shows this error when try to burn an iso image
https://bugs.kde.org/show_bug.cgi?id=90318 Alex changed: What|Removed |Added CC||alessandroberselli63@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 90318] I can burn audio and data projects, but shows this error when try to burn an iso image
https://bugs.kde.org/show_bug.cgi?id=90318 Alex changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #3 from Alex --- Devices --- hp DVDRAM GU70N U703 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7] System --- K3b Version: 17.12.3 KDE Version: 5.44.0 Qt Version: 5.9.5 Kernel: 4.15.0-21-generic Used versions --- cdrecord: 1.1.11 cdrecord --- /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. /usr/bin/wodim: Resource temporarily unavailable. Cannot get mmap for 12587008 Bytes on /dev/zero. Text len: 450 TOC Type: 0 = CD-DA cdrecord command: --- /usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=24 -sao driveropts=burnfree textfile=/tmp/k3b.Ea3326 -useinfo -audio /tmp/k3b_audio_0_01.inf /tmp/k3b_audio_0_02.inf /tmp/k3b_audio_0_03.inf /tmp/k3b_audio_0_04.inf /tmp/k3b_audio_0_05.inf /tmp/k3b_audio_0_06.inf /tmp/k3b_audio_0_07.inf /tmp/k3b_audio_0_08.inf /tmp/k3b_audio_0_09.inf -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita
https://bugs.kde.org/show_bug.cgi?id=365222 --- Comment #16 from Boudewijn Rempt --- I think I've spend about 80 hours trying to figure out how to fix this bug, but I haven't succeeded yet. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 393775] Problem connecting Maxdome II since KSatrs v. 2.9.4
https://bugs.kde.org/show_bug.cgi?id=393775 --- Comment #2 from Jean-Claude --- (In reply to Juan M.B. from comment #1) Hi Juan, I have typed indiserver in a Terminal (on macOS) but it replies : Command not found. The Terminal replies the same when the KStars app or the INDI Server app are running. I've been using KStars 2.9.3, 2.9.4, 2.9.5 Trying to answer your question I tested again KStars 2.9.4 and KStars 2.9.5 which were causing the current problem : these versions work NOW PERFECTLY AND CONNECT MAXDOME II without problem !!! What I did : I simply changed the USB port of my MacBook Pro ! Now all my devices are immediately recognized and mounted. I reported to-day in an INDI forum the fact that changing the USB port of a computer could solve many USB connection problems. Thanks any how and I wish you a nice day ! -- You are receiving this mail because: You are watching all bug changes.
[ksystraycmd] [Bug 393630] System tray icons not clickable and collapsible when a entry visibility is changed to hidden
https://bugs.kde.org/show_bug.cgi?id=393630 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Dr. Chapatin --- cannot reproduce on Arch Linux, plasma 5.12.5. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 393424] Proceed automatically to another cell after entering a value in a spreedsheet
https://bugs.kde.org/show_bug.cgi?id=393424 --- Comment #6 from Alexander Semke --- (In reply to urcindalo from comment #5) > (In reply to Alexander Semke from comment #3) > > (In reply to urcindalo from comment #2) > > > I just sync'ed and compiled five minutes ago, but I don't see the fix. > > > Focus > > > remains in the same cell after entering a value. > > Do you really used the binary you compiled or do you maybe still use the > > executable that was previously installed? I attached a small video showing > > the current behavior in LabPlot. Can you please check once more on your > > side? > > Thanks for your efforts. > In order to be sure, I completely uninstalled labplot from my box, which > also removed its dependencies (Gentoo Linux here). Then, I reinstalled it > (from source, this is Gentoo). Alas, I still get no focus on next cell. > > Let me remind you in other bugs it was only a matter of reinstalling labplot > to see if fixed. > > Might it is locale related? I use commas for decimal separators and my > system language is set to Spanish. > > Maybe the commit does not appear on the server? The code you compiled must have the fix for this. Setting of the focus is not related to the locale - I also use comma as the separator (German settings). Just to make sure you're really using the current code, you compiled the commit 23a99c14446e8ac615215e8ee60aabe9fc86f52 which has a change on ResizableTextEdit.cpp. If you start LabPlot and select a spreadsheet, is the comment text box in the properties dock widget resizable for your? There must be a small grab bar at the bottom of the text field. Do you have this? If yes, then you're using the current code. In this case, would it be feasible for you to record a small video ( SimpleScreenRecorder does the job very well) showing this problem on your side? Can you do a small video of -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 393606] Ctrl+Shift+W doesn't work
https://bugs.kde.org/show_bug.cgi?id=393606 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393513] Settings crash when searching "Menubar" while in a certain menu
https://bugs.kde.org/show_bug.cgi?id=393513 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393061] Focus not transferred properly to child windows in sidebar view
https://bugs.kde.org/show_bug.cgi?id=393061 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 390453] Dolphin crash No. 100 or more
https://bugs.kde.org/show_bug.cgi?id=390453 --- Comment #3 from Syfer Polski --- (In reply to Julian Schraner from comment #2) > Please paste the contents of /etc/fstab so that we can further investigate > this crash. Thanks! On the 29th of March GHO(s...@iforma.net) emailed me about this bug, attaching his fstab. Since it doesn't contain any private information, I'm including it here. It supports the running theory that this problem only happens to people who don't have their UID and GID specified in the mount options. # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sda1 during installation UUID=a427a420-3799-41aa-8d0d-5655b7ef7860 / ext4 errors=remount-ro 0 1 # /DATA was on /dev/sdc6 during installation UUID=28813ACA21F76D42 /DATA ntfsdefaults,umask=007,gid=46 0 0 # /home was on /dev/sdc3 during installation UUID=bdd16a4e-5e3a-4afe-9b80-166707be5b1d /home ext4defaults 0 2 # swap was on /dev/sdc5 during installation UUID=15765e70-613f-498b-9b25-fed28d13b99e noneswapsw 0 0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393879] New: line problem
https://bugs.kde.org/show_bug.cgi?id=393879 Bug ID: 393879 Summary: line problem Product: krita Version: 4.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush Engine/Shape Assignee: krita-bugs-n...@kde.org Reporter: matus.noga@gmail.com Target Milestone: --- Created attachment 112425 --> https://bugs.kde.org/attachment.cgi?id=112425&action=edit here is an example when i draw a line then lift up the pen and draw another line those lines are connected every time -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 268949] Bug in dual screen
https://bugs.kde.org/show_bug.cgi?id=268949 mathew changed: What|Removed |Added CC||matus.noga@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393652] Dolphin crashed after moving a file to Trash - from a network-mounted filesystem
https://bugs.kde.org/show_bug.cgi?id=393652 Julian Schraner changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||juliquad...@gmail.com --- Comment #1 from Julian Schraner --- Thanks for reporting this crash! Can you reproduce this behavior again or was this a one-time occurrence? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393880] New: Dolphin doesn't display available resources in network
https://bugs.kde.org/show_bug.cgi?id=393880 Bug ID: 393880 Summary: Dolphin doesn't display available resources in network Product: dolphin Version: 18.04.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gko...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 112426 --> https://bugs.kde.org/attachment.cgi?id=112426&action=edit Dolphin doesn't display available resources in network Ubuntu 18.04 Dolphin - 4:17.12.3-0ubuntu1 libsmbclient - 2:4.7.6+dfsg In Dolphin resources of network and even the shared local folders aren't shown. If to enter the address smb://192.168.8.1/Shara that it is possible to get access -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393879] line problem
https://bugs.kde.org/show_bug.cgi?id=393879 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO Component|Brush Engine/Shape |tablet support Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Boudewijn Rempt --- What OS? What tablet? What version of Krita? (It's not 4.1, because that is not out yet). We're not mind readers... Chances are, though, that this is not a bug in Krita, but a bug in the driver software for your tablet. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393710] Missing "Send via Bluetooth" entry in context menu when I try to send files with different extensions
https://bugs.kde.org/show_bug.cgi?id=393710 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Julian Schraner --- I can confirm this issue, we'll need to investigate this further. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 375467] Cantor hangs at "Initializing Session" when choosing Sage backend (Sage version 7.6)
https://bugs.kde.org/show_bug.cgi?id=375467 --- Comment #8 from Antonio Rojas --- No, this still doesn't work. Major changes are needed to work with newer versions of Sage (newer than 2 years) in Sage itself (so that it allows running ipython in simple prompt mode), in ipython (i think those are already merged) and in Cantor (to adapt to latest ipython versions using prompt_toolkit instead of readline). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393881] New: Desktop widget position lost after reboot
https://bugs.kde.org/show_bug.cgi?id=393881 Bug ID: 393881 Summary: Desktop widget position lost after reboot Product: plasmashell Version: 5.12.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 I have two displays, the primary is a 3840x2160 display and the secondary is a 1920x1080 display that is configured as an extension to the right of the primary display. The primary display has two horizontal panels, on the top and bottom edge of the screen. No other widgets on the desktop. 1. Unlock widgets and add a Calendar widget on the top right corner of the primary display. Resize the widget so that the calendar grid is visible. 2. Reboot. 3. After the reboot the Calendar widget position is changed. It is now placed in the top right corner of the top left quarter of the primary screen. Widget position should be preserved across reboot. This is a regression in Kubuntu 18.04, the position did save in 17.10. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393881] Desktop widget position lost after reboot
https://bugs.kde.org/show_bug.cgi?id=393881 --- Comment #1 from Lastique --- Created attachment 112427 --> https://bugs.kde.org/attachment.cgi?id=112427&action=edit Screenshot before reboot -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393821] Horizontal spacing is inconsistent for different icon sizes
https://bugs.kde.org/show_bug.cgi?id=393821 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #5 from Julian Schraner --- Looks great! Consider submitting this patch to phabricator.kde.org, where other developers can review the patch and give you feedback for it. Thanks for not only reporting this bug but also providing a patch for it, that is truly amazing :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393881] Desktop widget position lost after reboot
https://bugs.kde.org/show_bug.cgi?id=393881 --- Comment #2 from Lastique --- Created attachment 112428 --> https://bugs.kde.org/attachment.cgi?id=112428&action=edit Screenshot after reboot -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 392447] dolphin shows nothing on smb:// or smb://workgroup/
https://bugs.kde.org/show_bug.cgi?id=392447 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #3 from Dr. Chapatin --- I can not confirm. My two computers run Arch Linux pc A: kde plasma 5.12.5, frameworks 5.45, dolphin 18.04, samba 4.8.1 pc B: Gnome 3.28.1, nautilus 3.28.1, samba 4.8.1 Both computers have "[global] client max protocol = SMB2" in their smb.conf file. Dolphin from pc A shows the samba shares from pc B. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393882] New: OpenEXR conerting layer to mask behaves incorrectly
https://bugs.kde.org/show_bug.cgi?id=393882 Bug ID: 393882 Summary: OpenEXR conerting layer to mask behaves incorrectly Product: krita Version: unspecified Platform: unspecified OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: jeske...@gmail.com Target Milestone: --- I've noticed a bit annoying problem when working with OpenEXR (which in general is awesome format). I often render additional layer that can be used as a selection mask for example - which allows me to quickly arrange the scene. Those layers import correctly. Strange thing happens when I actually convert those to selection mask - they completely disappear from the layer list. Normally those appear as sublayers, but with EXRs they're gone (but at least selection happens). This has been the case since several versions - would love to see it resolve as EXRs are one of the best formats to move your images from 3D app to 2D app. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393882] OpenEXR converting layer to mask behaves incorrectly
https://bugs.kde.org/show_bug.cgi?id=393882 Przemek changed: What|Removed |Added Summary|OpenEXR conerting layer to |OpenEXR converting layer to |mask behaves incorrectly|mask behaves incorrectly -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393883] New: Could not open file.BMP
https://bugs.kde.org/show_bug.cgi?id=393883 Bug ID: 393883 Summary: Could not open file.BMP Product: krita Version: 4.0.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: rud_dim...@mail.ru Target Milestone: --- Could not open file.BMP -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 391761] Unable to load extension
https://bugs.kde.org/show_bug.cgi?id=391761 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #4 from Dr. Chapatin --- at least on Arch, Firefox 59.0.2, I can install plasma browser integration extension without any problem. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393652] Dolphin crashed after moving a file to Trash - from a network-mounted filesystem
https://bugs.kde.org/show_bug.cgi?id=393652 --- Comment #2 from yst...@posteo.net --- (In reply to Julian Schraner from comment #1) > Thanks for reporting this crash! Can you reproduce this behavior again or > was this a one-time occurrence? Glad to help. But no, I actually cannot reproduce it one more time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393883] Could not open file.BMP
https://bugs.kde.org/show_bug.cgi?id=393883 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Dmitry, I'm sorry, but I cannot reproduce what I am guessing you mean: I can save and open bmp files just fine. If your report is about a specific .bmp file, please attach it to the bug report. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 391243] New web shortcuts take effect only after user restarts sessions
https://bugs.kde.org/show_bug.cgi?id=391243 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 393884] New: Discover closed
https://bugs.kde.org/show_bug.cgi?id=393884 Bug ID: 393884 Summary: Discover closed Product: Discover Version: 5.12.4 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: edgar.n...@gmail.com Target Milestone: --- Application: plasma-discover (5.12.4) (Compiled from sources) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-20-generic x86_64 Distribution: Ubuntu 18.04 LTS -- Information about the crash: When I try to see installed aplications from updates into Discover. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f28f85b8f40 (LWP 3105))] Thread 8 (Thread 0x7f28b904a700 (LWP 3117)): #0 0x7f28f3c9c0b4 in __GI___libc_read (fd=15, buf=0x7f28b9049b90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f28ee5d3960 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f28ee58ef27 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f28ee58f3e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f28ee58f54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f28f45ee90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f28f45939ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f28f43b222a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f28f43b716d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f28f04b46db in start_thread (arg=0x7f28b904a700) at pthread_create.c:463 #10 0x7f28f3cad88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f28bb27f700 (LWP 3114)): #0 0x7f28f43ae99c in QMutex::lock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f28f45ee82d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f28ee58e998 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f28ee58f36b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f28ee58f54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f28f45ee90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f28f45939ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f28f43b222a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f28f43b716d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f28f04b46db in start_thread (arg=0x7f28bb27f700) at pthread_create.c:463 #10 0x7f28f3cad88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f28c1104700 (LWP 3111)): #0 0x7f28ee5d4cd9 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f28ee58e2e0 in g_main_context_acquire () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f28ee58f2f5 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f28ee58f54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f28f45ee90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f28f45939ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f28f43b222a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f28f43b716d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f28f04b46db in start_thread (arg=0x7f28c1104700) at pthread_create.c:463 #9 0x7f28f3cad88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f28cbfff700 (LWP 3110)): #0 0x7f28f3ca0bf9 in __GI___poll (fds=0x7f28c4004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f28ee58f439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f28ee58f54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f28f45ee90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f28f45939ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f28f43b222a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f28f77912a6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f28f43b716d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f28f04b46db in start_thread (arg
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 --- Comment #7 from Julian Schraner --- If we do not get a response in the next two weeks, I'll close this bug as WORKSFORME because despite various attempts I have not been able to reproduce the crash. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365026] Crash on Window Size Change
https://bugs.kde.org/show_bug.cgi?id=365026 --- Comment #4 from Julian Schraner --- I'll close this bug in two weeks if we do not get a response until then. Please attach a valgrind log if you can still reproduce this crash. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371880] Dolphin crash
https://bugs.kde.org/show_bug.cgi?id=371880 --- Comment #4 from Julian Schraner --- I'll close this bug in two weeks if we do not get a response until then. Please attach a valgrind log/backtrace with debug symbols if you can still reproduce this crash. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390411] Sqlite opening broken
https://bugs.kde.org/show_bug.cgi?id=390411 Christian David changed: What|Removed |Added CC||christian-da...@web.de --- Comment #4 from Christian David --- Could this be connected with or caused by bug 341304? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 373238] Dolphin Crashes When Viewing Files in Directory
https://bugs.kde.org/show_bug.cgi?id=373238 --- Comment #4 from Julian Schraner --- I'll close this bug in two weeks if we do not get a response until then. Please attach a valgrind log/backtrace with debug symbols if you can still reproduce this crash. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 323409] Git push shows error message, though the operation seems to complete correctly.
https://bugs.kde.org/show_bug.cgi?id=323409 Julian Schraner changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #2 from Julian Schraner --- No response -> closing. Please reopen the report if you can still reproduce this bug. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 279614] The Dolphin shell panel (opend by F4) does not source .bashrc
https://bugs.kde.org/show_bug.cgi?id=279614 --- Comment #28 from Julian Schraner --- If nobody responds in the next two weeks, I'll assume that this bug is indeed fixed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 286973] When a new subfolder is added to SVN, there is no option to add to SVN any files or folders inside it
https://bugs.kde.org/show_bug.cgi?id=286973 Julian Schraner changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Julian Schraner --- No response -> closing. Please reopen this report if you can still reproduce this issue with a newer version of Dolphin. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 393775] Problem connecting Maxdome II since KSatrs v. 2.9.4
https://bugs.kde.org/show_bug.cgi?id=393775 --- Comment #3 from Jean-Claude --- Juan, I've replied too quickly that the problem was gone if I used the other USB port of my computer. This brings an improvement (the dome connects now) but the driver still behaves in a non standard way. Because you told me that you didn't have a real MaxDome II board, if you wish we could do a TeamViewer session . I'm using a Mac but this should not make a real difference to you. Please reply to my proposal. Regards, -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393885] New: Magnifier effect works only when I move cursor on top of the screen
https://bugs.kde.org/show_bug.cgi?id=393885 Bug ID: 393885 Summary: Magnifier effect works only when I move cursor on top of the screen Product: kwin Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 112429 --> https://bugs.kde.org/attachment.cgi?id=112429&action=edit demonstration Watch screencast recorded on Arch Linux, plasma 5.12.5. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393885] Magnifier effect works only when I move cursor on top of the screen
https://bugs.kde.org/show_bug.cgi?id=393885 Dr. Chapatin changed: What|Removed |Added Component|general |effects-various -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 393745] Build is broken with trunk LLVM/Clang
https://bugs.kde.org/show_bug.cgi?id=393745 Sergio Martins changed: What|Removed |Added Assignee|unassigned-b...@kde.org |smart...@kde.org Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379259] Add option to activate last window in grouped icon task
https://bugs.kde.org/show_bug.cgi?id=379259 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393083] Unimplemented fcntl
https://bugs.kde.org/show_bug.cgi?id=393083 --- Comment #2 from pentelja...@o2.pl --- (In reply to Tom Hughes from comment #1) > Can you please run with --trace-syscalls=yes and paste in the last few lines > leading up to the error? lsd@lsd-K56CB:~$ valgrind /usr/bin/flatpak run --branch=master --arch=x86_64 --trace-syscalls=yes --command=q2pro com.github.skullernet.q2pro ==10083== Memcheck, a memory error detector ==10083== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==10083== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==10083== Command: /usr/bin/flatpak run --branch=master --arch=x86_64 --trace-syscalls=yes --command=q2pro com.github.skullernet.q2pro ==10083== błąd: Unknown option --trace-syscalls=yes ==10083== ==10083== HEAP SUMMARY: ==10083== in use at exit: 62,631 bytes in 658 blocks ==10083== total heap usage: 2,827 allocs, 2,169 frees, 366,245 bytes allocated ==10083== ==10083== LEAK SUMMARY: ==10083==definitely lost: 96 bytes in 1 blocks ==10083==indirectly lost: 58 bytes in 1 blocks ==10083== possibly lost: 1,480 bytes in 19 blocks ==10083==still reachable: 60,853 bytes in 635 blocks ==10083== of which reachable via heuristic: ==10083== length64 : 816 bytes in 18 blocks ==10083== newarray : 1,632 bytes in 22 blocks ==10083== suppressed: 0 bytes in 0 blocks ==10083== Rerun with --leak-check=full to see details of leaked memory ==10083== ==10083== For counts of detected and suppressed errors, rerun with: -v ==10083== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) lsd@lsd-K56CB:~$ -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 375378] Pie chart on main screen has no colors when system language is different than english.
https://bugs.kde.org/show_bug.cgi?id=375378 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393083] Unimplemented fcntl
https://bugs.kde.org/show_bug.cgi?id=393083 --- Comment #3 from pentelja...@o2.pl --- (In reply to penteljapan from comment #2) > (In reply to Tom Hughes from comment #1) > > Can you please run with --trace-syscalls=yes and paste in the last few lines > > leading up to the error? > > lsd@lsd-K56CB:~$ valgrind /usr/bin/flatpak run --branch=master --arch=x86_64 > --trace-syscalls=yes --command=q2pro com.github.skullernet.q2pro > ==10083== Memcheck, a memory error detector > ==10083== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. > ==10083== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info > ==10083== Command: /usr/bin/flatpak run --branch=master --arch=x86_64 > --trace-syscalls=yes --command=q2pro com.github.skullernet.q2pro > ==10083== > błąd: Unknown option --trace-syscalls=yes > ==10083== > ==10083== HEAP SUMMARY: > ==10083== in use at exit: 62,631 bytes in 658 blocks > ==10083== total heap usage: 2,827 allocs, 2,169 frees, 366,245 bytes > allocated > ==10083== > ==10083== LEAK SUMMARY: > ==10083==definitely lost: 96 bytes in 1 blocks > ==10083==indirectly lost: 58 bytes in 1 blocks > ==10083== possibly lost: 1,480 bytes in 19 blocks > ==10083==still reachable: 60,853 bytes in 635 blocks > ==10083== of which reachable via heuristic: > ==10083== length64 : 816 bytes in 18 blocks > ==10083== newarray : 1,632 bytes in 22 > blocks > ==10083== suppressed: 0 bytes in 0 blocks > ==10083== Rerun with --leak-check=full to see details of leaked memory > ==10083== > ==10083== For counts of detected and suppressed errors, rerun with: -v > ==10083== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) > lsd@lsd-K56CB:~$ -- lsd@lsd-K56CB:~$ valgrind /usr/bin/flatpak run --branch=master --arch=x86_64 --command=q2pro com.github.skullernet.q2pro ==10176== Memcheck, a memory error detector ==10176== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==10176== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==10176== Command: /usr/bin/flatpak run --branch=master --arch=x86_64 --command=q2pro com.github.skullernet.q2pro ==10176== ==10176== Warning: unimplemented fcntl command: 1033 błąd: fcntl(F_ADD_SEALS): Zły argument ==10176== ==10176== HEAP SUMMARY: ==10176== in use at exit: 86,276 bytes in 1,118 blocks ==10176== total heap usage: 8,712 allocs, 7,594 frees, 1,058,004 bytes allocated ==10176== ==10176== LEAK SUMMARY: ==10176==definitely lost: 120 bytes in 2 blocks ==10176==indirectly lost: 1,974 bytes in 38 blocks ==10176== possibly lost: 1,616 bytes in 20 blocks ==10176==still reachable: 82,030 bytes in 1,053 blocks ==10176== of which reachable via heuristic: ==10176== length64 : 1,080 bytes in 24 blocks ==10176== newarray : 1,696 bytes in 26 blocks ==10176== suppressed: 0 bytes in 0 blocks ==10176== Rerun with --leak-check=full to see details of leaked memory ==10176== ==10176== For counts of detected and suppressed errors, rerun with: -v ==10176== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) lsd@lsd-K56CB:~$ -- You are receiving this mail because: You are watching all bug changes.
