[lokalize] [Bug 404635] New: Lokalize crashes on project overview during file update
https://bugs.kde.org/show_bug.cgi?id=404635 Bug ID: 404635 Summary: Lokalize crashes on project overview during file update Product: lokalize Version: 18.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: sdepi...@gmail.com Reporter: alex...@gmail.com CC: sha...@ukr.net Target Milestone: --- Application: lokalize (18.12.2) Qt Version: 5.12.0 Frameworks Version: 5.55.0 Operating System: Linux 4.20.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was downloading new translations from server. There are approx.150 files in my project, so I update them in batch via helper script - and I noticed that if Lokalize window is open while my script update files one by one, Lokalize crashes. The crash can be reproduced every time. -- Backtrace: Application: Lokalize (lokalize), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7159f4c980 (LWP 7419))] Thread 8 (Thread 0x7f70afbe7700 (LWP 7432)): [KCrash Handler] #6 0x004d4d79 in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x8000) at /usr/include/c++/8/bits/atomic_base.h:390 #7 QAtomicOps::load (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x8000) at /usr/include/qt5/QtCore/qbasicatomic.h:103 #9 QtPrivate::RefCount::isShared (this=0x8000) at /usr/include/qt5/QtCore/qrefcount.h:101 #10 QList::append (t=..., this=0x3ffef08) at /usr/include/qt5/QtCore/qlist.h:584 #11 UpdateStatsJob::run (this=0x3ffeee0) at /usr/src/debug/lokalize-18.12.2-1.1.x86_64/src/project/projectmodel.cpp:1420 #12 0x7f715c2505b1 in QThreadPoolThread::run (this=0x3ee33d0) at thread/qthreadpool.cpp:99 #13 0x7f715c24c6e2 in QThreadPrivate::start (arg=0x3ee33d0) at thread/qthread_unix.cpp:361 #14 0x7f715b231fab in start_thread () from /lib64/libpthread.so.0 #15 0x7f715bde666f in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f714d934700 (LWP 7431)): #0 0x7f715b237fdc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f715b77209a in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7f715b7720bb in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7f715b231fab in start_thread () from /lib64/libpthread.so.0 #4 0x7f715bde666f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f714ead5700 (LWP 7426)): #0 0x7f715b237fdc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f715c252613 in QWaitConditionPrivate::wait (deadline=..., this=0x2be6760) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x15b8ab0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f715c2526f9 in QWaitCondition::wait (this=this@entry=0x2b6f9a0, mutex=mutex@entry=0x15b8ab0, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f715c2507c2 in QThreadPoolThread::run (this=0x2b6f990) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:240 #5 0x7f715c24c6e2 in QThreadPrivate::start (arg=0x2b6f990) at thread/qthread_unix.cpp:361 #6 0x7f715b231fab in start_thread () from /lib64/libpthread.so.0 #7 0x7f715bde666f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f714f2d6700 (LWP 7424)): #0 0x7f715b237fdc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f715c252613 in QWaitConditionPrivate::wait (deadline=..., this=0x2b40690) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x2682aa8, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f715c2526f9 in QWaitCondition::wait (this=0x2682ab0, mutex=0x2682aa8, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f715d18bc05 in ?? () from /usr/lib64/libQt5Widgets.so.5 #5 0x7f715c24c6e2 in QThreadPrivate::start (arg=0x2682a98) at thread/qthread_unix.cpp:361 #6 0x7f715b231fab in start_thread () from /lib64/libpthread.so.0 #7 0x7f715bde666f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f714700 (LWP 7423)): #0 0x7f715b237fdc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7154899053 in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f7154898da7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f715b231fab in start_thread () from /lib64/libpthread.so.0 #4 0x7f715bde666f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f715698f700 (LWP 7422)): #0 0x7f715bdd7684 in read () from /lib64/libc.so.6 #1 0x7f715a978b10 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f715a932b0f in g_main_context_check () from
[kwin] [Bug 404634] New: Kwin crash on SDL2 application startup
https://bugs.kde.org/show_bug.cgi?id=404634
Bug ID: 404634
Summary: Kwin crash on SDL2 application startup
Product: kwin
Version: 5.14.5
Platform: Slackware Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: hanni...@astral.lodz.pl
Target Milestone: ---
Application: kwin_x11 (5.14.5)
Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.20 x86_64
Distribution (Platform): Slackware Packages
-- Information about the crash:
Kwin crash when I fireup my SDL2 application. It only apperars only on first
and second kwin instance (I mean, orginal - and second started automatically
after crash). Third one seems to be immune. Problem back after restart.
SDL2 init code looks that (w.o. error processing):
window = SDL_CreateWindow("Some label", SDL_WINDOWPOS_UNDEFINED,
SDL_WINDOWPOS_UNDEFINED, screenX, screenY, SDL_WINDOW_FULLSCREEN);
screen = SDL_CreateRenderer(window, -1, SDL_RENDERER_ACCELERATED);
back = SDL_CreateTexture(screen, SDL_PIXELFORMAT_RGBA,
SDL_TEXTUREACCESS_TARGET, screenX, screenY);
SDL_SetRenderTarget(screen, back);
screenX and screenY are get in following way:
for (i = 0; i < SDL_GetNumVideoDisplays(); i++) {
for (j = 0; j < SDL_GetNumDisplayModes(i); j++) {
SDL_GetDisplayMode(i, j, );
if ((mode.w * mode.h) > (screenX * screenY)) {
screenX = mode.w;
screenY = mode.h;
}
}
}
The crash can be reproduced sometimes.
-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6fa9c50ec0 (LWP 2064))]
Thread 6 (Thread 0x7f6f91902700 (LWP 2257)):
#0 0x7f6fb25391b3 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7f6fb429e53a in () at /usr/lib64/libQt5Script.so.5
#2 0x7f6fb429e559 in () at /usr/lib64/libQt5Script.so.5
#3 0x7f6fb253319c in start_thread () at /lib64/libpthread.so.0
#4 0x7f6fb0a954cf in clone () at /lib64/libc.so.6
Thread 5 (Thread 0x7f6f93cb5700 (LWP 2223)):
#0 0x7f6fb25391b3 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7f6fa03d67db in () at /usr/lib64/xorg/modules/dri/i965_dri.so
#2 0x7f6fa03d6587 in () at /usr/lib64/xorg/modules/dri/i965_dri.so
#3 0x7f6fb253319c in start_thread () at /lib64/libpthread.so.0
#4 0x7f6fb0a954cf in clone () at /lib64/libc.so.6
Thread 4 (Thread 0x7f6fa2522700 (LWP 2206)):
#0 0x7f6fb0a89b12 in ppoll () at /lib64/libc.so.6
#1 0x7f6fb1104a59 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib64/libQt5Core.so.5
#2 0x7f6fb1105d49 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3 0x7f6fb10b871b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4 0x7f6fb0f0b8f6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5 0x7f6fb3a27435 in () at /usr/lib64/libQt5Qml.so.5
#6 0x7f6fb0f14ebc in () at /usr/lib64/libQt5Core.so.5
#7 0x7f6fb253319c in start_thread () at /lib64/libpthread.so.0
#8 0x7f6fb0a954cf in clone () at /lib64/libc.so.6
Thread 3 (Thread 0x7f6fa3fff700 (LWP 2112)):
#0 0x7f6fb0a89b12 in ppoll () at /lib64/libc.so.6
#1 0x7f6fb1104a59 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib64/libQt5Core.so.5
#2 0x7f6fb1105d49 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3 0x7f6fb10b871b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4 0x7f6fb0f0b8f6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5 0x7f6fb21bb505 in () at /usr/lib64/libQt5DBus.so.5
#6 0x7f6fb0f14ebc in () at /usr/lib64/libQt5Core.so.5
#7 0x7f6fb253319c in start_thread () at /lib64/libpthread.so.0
#8 0x7f6fb0a954cf in clone () at /lib64/libc.so.6
Thread 2 (Thread 0x7f6fa93a2700 (LWP 2088)):
#0 0x7f6fb0a89a39 in poll () at /lib64/libc.so.6
#1 0x7f6fb2189d17 in () at /usr/lib64/libxcb.so.1
#2 0x7f6fb218b80a in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3 0x7f6fa98a2ee9 in () at
/usr/lib64/qt5/plugins/platforms/../../../libQt5XcbQpa.so.5
#4 0x7f6fb0f14ebc in () at /usr/lib64/libQt5Core.so.5
#5 0x7f6fb253319c in start_thread () at /lib64/libpthread.so.0
#6 0x7f6fb0a954cf in clone () at /lib64/libc.so.6
Thread 1 (Thread 0x7f6fa9c50ec0 (LWP 2064)):
[KCrash Handler]
#6 0x7f6fb09bf22b in raise () at /lib64/libc.so.6
#7 0x7f6fb09a1524 in abort () at /lib64/libc.so.6
#8 0x7f6fb09a140f in _nl_load_domain.cold.0 () at /lib64/libc.so.6
#9 0x7f6fb09b04f2 in () at /lib64/libc.so.6
#10
[plasmashell] [Bug 404611] Date string doesn't always take up the full amount of available horizontal space with with a vertical panel
https://bugs.kde.org/show_bug.cgi?id=404611 --- Comment #2 from antnyzi...@gmail.com --- I've never submitted a patch before, but I followed the links and went through the process and submitted a change to Phabricator. It seems like I messed up the formatting of the commit message, but the change I wanted to make is there. https://phabricator.kde.org/D19194 I tested the change tonight and didn't notice any issue with a horizontal panel. As far as I know it shouldn't have any effect on it. With the vertical panel, all I'm doing is setting the date string height to the same size as the time string height. I've kept this change in my own modified plasmoid for quite a while now and haven't noticed any issues yet. I don't know if there was a specific reason the date string was formatted the way it was before, so it's possible this isn't a good change but it seems to fix the issue I was having. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 404633] New: Compatibility with ASAN
https://bugs.kde.org/show_bug.cgi?id=404633 Bug ID: 404633 Summary: Compatibility with ASAN Product: Heaptrack Version: 1.1.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: m...@milianw.de Reporter: french.ebook.lo...@gmail.com Target Milestone: --- SUMMARY It seems that it is impossible to use Heaptrack with asan linked. I get empty stats when I try (0 allocations), and I assume this is because of Asan's instrumentation of the alloc/dealloc primitives. Is there any known workaround to this? Thanks in advance -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404632] New: KWin Crashed
https://bugs.kde.org/show_bug.cgi?id=404632 Bug ID: 404632 Summary: KWin Crashed Product: kwin Version: 5.12.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: zoltan.antal...@gmail.com Target Milestone: --- Application: kwin_x11 (5.12.7) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-32-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: Write an e-mail with thunderbird, then clicked to taskbar to a vlc icon, that plays a video. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fccf0a15040 (LWP 18049))] Thread 5 (Thread 0x7fcccf7fe700 (LWP 20474)): #0 0x7fccefc519f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fccd0019b9c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fccefc519f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fccd0019b48, cond=0x7fccd0019b70) at pthread_cond_wait.c:502 #2 0x7fccefc519f3 in __pthread_cond_wait (cond=0x7fccd0019b70, mutex=0x7fccd0019b48) at pthread_cond_wait.c:655 #3 0x7fcc38150b1b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fcc38150847 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fccefc4b6db in start_thread (arg=0x7fcccf7fe700) at pthread_create.c:463 #6 0x7fccf01f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7ff55700 (LWP 18150)): #0 0x7fccefc519f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fccec35bfb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fccefc519f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fccec35bf68, cond=0x7fccec35bf90) at pthread_cond_wait.c:502 #2 0x7fccefc519f3 in __pthread_cond_wait (cond=0x7fccec35bf90, mutex=0x7fccec35bf68) at pthread_cond_wait.c:655 #3 0x7fccec0655f4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fccec065639 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fccefc4b6db in start_thread (arg=0x7ff55700) at pthread_create.c:463 #6 0x7fccf01f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fccced86700 (LWP 18140)): #0 0x7fccf017bcf6 in __GI_ppoll (fds=0x7fccc4000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fcced15a5c1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fcced15bcde in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fcced1039ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fccecfa in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcce7ac96f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fccecf2716d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fccefc4b6db in start_thread (arg=0x7fccced86700) at pthread_create.c:463 #8 0x7fccf01f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fccc700 (LWP 18070)): #0 0x7fccf017bcf6 in __GI_ppoll (fds=0x7fccc800afb8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fcced15a5c1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fcced15bcde in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fcced1039ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fccecfa in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcce69a2d45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fccecf2716d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fccefc4b6db in start_thread (arg=0x7fccc700) at pthread_create.c:463 #8 0x7fccf01f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fccf0a15040 (LWP 18049)): [KCrash Handler] #6 0x7fccf04531b0 in main_arena () at /lib/x86_64-linux-gnu/libc.so.6 #7 0x7fccef850d6d in KWin::Workspace::constrainedStackingOrder() () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #8 0x7fccef851538 in KWin::Workspace::updateStackingOrder(bool) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #9 0x7fccef851ac0 in KWin::Workspace::blockStackingUpdates(bool) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #10 0x7fccef7fc870 in KWin::Client::destroyClient() () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #11
[okular] [Bug 404549] Printing N copies results in N^2 copies printed instead
https://bugs.kde.org/show_bug.cgi?id=404549 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Michael Weghorn --- This sounds like it might be related to the CUPS filter chain, rather than Okular. The following information might help to further narrow this down: 1) Does this happen for all files or just specific ones? 2) Can you attach the CUPS log for one such print job (with LogLevel set to debug)? 3) the file as generated by Okular: Can you (using a non-confidential file) * temporarily disable the printer using 'sudo cupsdisable ' * start printing from Okular * attach the print file called 'd_001' from directory '/var/spool/cups' (which should be a PostScript file) You can then enable the printer again using 'sudo cupsenable ? 4) Can you attach the PPD files of the printer(s), which should be located at /etc/cups/ppd/? 5) What is the device URI of the printer (which is shown e.g. when running 'lpstat -v'? 6) Can you attach the file as generated by the CUPS filters? In order to get this, you can set up a dummy printer that prints to a file as follows: * set 'FileDevice Yes' in /etc/cup/cups-files.conf * restart CUPS * set up a dummy printer that prints to a file, using the real printer's PPD file: 'sudo lpadmin -p tofile -v file:/tmp/tofile -P /etc/cups/ppd/ -E' * print the PDF file from Okular to the "tofile" printer * attach the file that is generated at /tmp/tofile -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404080] Logarithmic blend modes causes floating point exception (core dumped)
https://bugs.kde.org/show_bug.cgi?id=404080
--- Comment #13 from reptilli...@live.com ---
I got my computer overheating issue fixed, so I can test changes.
For Rebecca Breu, as you know how to compile and edit code by copy and pasting
as well as having a computer where this bug can be reproduced (I can't
reproduce it). Can you confirm this change works?
template
inline T cfColorBurnLogarithmic(T src, T dst) {
using namespace Arithmetic;
//Also known as Darken from EffectBank/Illusions.hu. IFS Illusions had used
this blending mode.
qreal fsrc = scale(src);
qreal fdst = scale(dst);
if (fdst == unitValue()) {
return scale(log2(abs(1.0 + fsrc/inv(.99)/8)));
}
return scale(log2(abs(1.0 + fsrc/inv(fdst)/8)));
}
If it does work, I'll submit a patch on phabricator.
The changes I have made is to remove abs inside, and then wrap the absolute
next to log2 to force everything to go to positive. And yes, it does compile.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 382646] XMP sidecar file doesn't contain GPS tags
https://bugs.kde.org/show_bug.cgi?id=382646 --- Comment #2 from Mark F --- Created attachment 118244 --> https://bugs.kde.org/attachment.cgi?id=118244=edit Sidecar file written after geocoding the image in digiKam and selecting 'write metadata'. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382646] XMP sidecar file doesn't contain GPS tags
https://bugs.kde.org/show_bug.cgi?id=382646 Mark F changed: What|Removed |Added CC||mfseas...@gmail.com --- Comment #1 from Mark F --- Created attachment 118243 --> https://bugs.kde.org/attachment.cgi?id=118243=edit Metadata settings in digiKam I also ran into this. I used digiKam to correlate a GPX track with some NEF files, and then also manually set the coordinates in some of them which weren't in the GPX file's time range. That part worked great. But then when I went to save the GPS info to my files, I found that it isn't supported to write directly to the RAW file, and it also doesn't seem to show up in the XMP sidecar file. I would like to have the GPS data in my image files for portability. If it's just in digiKam's database, then of course it cannot be used in other apps. I intend to use RawTherapee or Darktable for image adjustments, probably, so finally exporting a JPEG with GPS metadata would happen from them. I also just migrated from LightRoom, so I'm very focused on making sure whatever solution I use next stores all the metadata I care about in the files, not in its own catalog/database. Thanks in advance for any help, and for writing/sharing digiKam! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397968] Arrow symbols to expand and contract recipient lists are interchanged
https://bugs.kde.org/show_bug.cgi?id=397968 Kishore Gopalakrishnan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Kishore Gopalakrishnan --- Seems to be fixed in version 5.10.2. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 404631] New: Folder View listing inconsistent
https://bugs.kde.org/show_bug.cgi?id=404631 Bug ID: 404631 Summary: Folder View listing inconsistent Product: kdeplasma-addons Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: hamidrjaf...@gmail.com Target Milestone: --- SUMMARY Setting the widget to show files created today will add extra copies of same files to the list. STEPS TO REPRODUCE 1. Add a folder view widget to a panel or on desktop. 2. In its properties head to and set it to and then . 3. Hit , . OBSERVED RESULT Check the contents of the widget. There are multiple instances of same files shown. EXPECTED RESULT Each item should be listed only once. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404628] When virtual desktops are swapped, it is reflected in other activities
https://bugs.kde.org/show_bug.cgi?id=404628 Martin Flöser changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Martin Flöser --- Virtual desktops are not per activity. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404617] KWin Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=404617 Martin Flöser changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 --- Comment #4 from Martin Flöser --- The crash is still lacking debug symbols. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404582] Make an option to disable quarter tiling
https://bugs.kde.org/show_bug.cgi?id=404582 --- Comment #6 from Martin Flöser --- It's two additional chech boxes. It needs additional code path. The complexity of KWin increases by factor 4. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403707] Add more apps into Featured apps' list from all categories
https://bugs.kde.org/show_bug.cgi?id=403707 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404037] The text if inserted in a picture, cannot be edited. I changed the font type, color and size but stays on default.
https://bugs.kde.org/show_bug.cgi?id=404037 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 403889] Unable to start amarok
https://bugs.kde.org/show_bug.cgi?id=403889 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 403524] in "save as" the drop down list of recent places doesn't contain recent places
https://bugs.kde.org/show_bug.cgi?id=403524 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 403585] Mouse cursor becomes bigger over windows after attaching another screen
https://bugs.kde.org/show_bug.cgi?id=403585 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404630] New: Akonadi server crashed when after using Akonadi Console
https://bugs.kde.org/show_bug.cgi?id=404630 Bug ID: 404630 Summary: Akonadi server crashed when after using Akonadi Console Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: luislezc...@gmail.com Target Milestone: --- Application: akonadiserver (5.10.2) Qt Version: 5.12.1 Frameworks Version: 5.55.0 Operating System: Linux 4.20.10-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I deleted many times the "local folders" email agent. It was constantly reappearing. After that I closed the application and it crashed -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe6b924cfc0 (LWP 1199))] Thread 32 (Thread 0x7fe673fff700 (LWP 3210)): #0 0x7fe6bd97ac21 in poll () from /usr/lib/libc.so.6 #1 0x7fe6bc327540 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fe6bc32762e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fe6bdec7d04 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fe6bde70b2c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x559e9903ddb3 in ?? () #6 0x7fe6bdea8b57 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fe6bde9d10b in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #8 0x7fe6bde71e77 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #9 0x7fe6bdec7095 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #10 0x7fe6bdec7922 in ?? () from /usr/lib/libQt5Core.so.5 #11 0x7fe6bc325a2f in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #12 0x7fe6bc3275e9 in ?? () from /usr/lib/libglib-2.0.so.0 #13 0x7fe6bc32762e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #14 0x7fe6bdec7ce9 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #15 0x7fe6bde70b2c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #16 0x7fe6bdcb4569 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #17 0x7fe6bdcb596c in ?? () from /usr/lib/libQt5Core.so.5 #18 0x7fe6bd11fa9d in start_thread () from /usr/lib/libpthread.so.0 #19 0x7fe6bd985b23 in clone () from /usr/lib/libc.so.6 Thread 31 (Thread 0x7fe640ff9700 (LWP 1477)): #0 0x7fe6bc2d53b9 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0 #1 0x7fe6bc327506 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fe6bc32762e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fe6bdec7d04 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fe6bde70b2c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x559e9903ddb3 in ?? () #6 0x7fe6bdea8b57 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fe6bde9d10b in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #8 0x7fe6bde71e77 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #9 0x7fe6bdec7095 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #10 0x7fe6bdec7922 in ?? () from /usr/lib/libQt5Core.so.5 #11 0x7fe6bc325a2f in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #12 0x7fe6bc3275e9 in ?? () from /usr/lib/libglib-2.0.so.0 #13 0x7fe6bc32762e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #14 0x7fe6bdec7ce9 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #15 0x7fe6bde70b2c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #16 0x7fe6bdcb4569 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #17 0x7fe6bdcb596c in ?? () from /usr/lib/libQt5Core.so.5 #18 0x7fe6bd11fa9d in start_thread () from /usr/lib/libpthread.so.0 #19 0x7fe6bd985b23 in clone () from /usr/lib/libc.so.6 Thread 30 (Thread 0x7fe6417fa700 (LWP 1468)): #0 0x7fe6bd9767a4 in read () from /usr/lib/libc.so.6 #1 0x7fe6bc2d5971 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fe6bc3260b0 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7fe6bc3274e6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7fe6bc32762e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7fe6bdec7d04 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fe6bde70b2c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x559e9903ddb3 in ?? () #8 0x7fe6bdea8b57 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7fe6bde9d10b in QObject::event(QEvent*) ()
[plasmashell] [Bug 404301] Virtual desktop pager is not displayed when only one desktop exists
https://bugs.kde.org/show_bug.cgi?id=404301
--- Comment #9 from andydecle...@gmail.com ---
If it's not to be configurable, might it make sense to hide the pager only when
there is exactly one desktop AND the currentDesktopSelected is absent ("Do
nothing")?
This combined with Eike Hein's idea in #c6 would be sufficient, IMO.
If the user has chosen to make something happen re: the current desktop when
they click on the current desktop in the pager, it should not become impossible
to do so due to the number of non-current desktops. To be specific, having only
one desktop doesn't make the show-desktop action less useful (in fact, the
reverse is true).
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 404301] Virtual desktop pager is not displayed when only one desktop exists
https://bugs.kde.org/show_bug.cgi?id=404301 --- Comment #8 from andydecle...@gmail.com --- Related: https://bugs.kde.org/show_bug.cgi?id=389499 While resolving this linked issue would mitigate the UX problems described here, it would not eliminate them, especially as current behavior makes access to click-current-desktop and right-click pager disappear. Please re-open this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404416] Sliders and Colour pickers with Pen in Windows 10
https://bugs.kde.org/show_bug.cgi?id=404416 Carson changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #9 from Carson --- I have done more testing with Krita to figure out why there is this issue that I mentioned before. I found that the right click pop up palette does NOT have the issue. Here is a link to two videos showing the differences. https://imgur.com/a/MTGHW4o The first video does not capture all the pen movements (also the pen location is captured off center). In the RGB slider video, I place the pen where the slider is on the Red channel and begin sliding the pen. The slider then jumps to the pen location (in the video it looks like it freezes in place for a moment then jumps, but that's not what I see on screen). The pop up palette video is self explanatory as it is working as intended. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 221115] Shortcuts to add/remove virtual desktops
https://bugs.kde.org/show_bug.cgi?id=221115 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389499] Ability to set keyboard shortcut to add and remove virtual desktop
https://bugs.kde.org/show_bug.cgi?id=389499 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404618] Request: Add actions for selecting current desktop
https://bugs.kde.org/show_bug.cgi?id=404618 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404618] Request: Add actions for selecting current desktop
https://bugs.kde.org/show_bug.cgi?id=404618 --- Comment #3 from andydecle...@gmail.com --- Created attachment 118242 --> https://bugs.kde.org/attachment.cgi?id=118242=edit Screenshot of the setting under discussion -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404618] Request: Add actions for selecting current desktop
https://bugs.kde.org/show_bug.cgi?id=404618 andydecle...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from andydecle...@gmail.com --- (In reply to David Edmundson from comment #1) > What do you mean by actions? In the context menu? Context menu actions would be a nice bonus, but no, I'm referring to the option as listed in this report's title: "Selecting current desktop" -- where there are currently exactly two options as listed in the report. I've now attached a screenshot of the setting this report intends to discuss to eliminate any ambiguities. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 322922] Dolphin should not store .directory files inside the actual directory to avoid cluttering and polluting the filesystem; should instead use ~/.local/share/dolphin/view_propertie
https://bugs.kde.org/show_bug.cgi?id=322922 Christoph Feck changed: What|Removed |Added CC||k...@i.yeb.me --- Comment #15 from Christoph Feck --- *** Bug 404629 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404629] Alternative to .directory files for folder-specific view settings
https://bugs.kde.org/show_bug.cgi?id=404629 Christoph Feck changed: What|Removed |Added Severity|normal |wishlist Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 322922 *** -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 404161] kpat crashes when trying to play the second or third different game
https://bugs.kde.org/show_bug.cgi?id=404161 --- Comment #13 from Víktor --- Do mirrors matter? kpat version installed is 18.12.2-1 This is my current /etc/pacman.d/mirrorlist - # Chakra repository mirrorlist # The first not commented (no # at the beginning of the line) mirror is # used. Mirrors are used in order, starting from the top. Add a # at # the start of a line to disable a mirror. # Australia Server = http://mirror.aarnet.edu.au/pub/chakra/$repo/x86_64 # Brazil Server = http://chakra.c3sl.ufpr.br/$repo/x86_64 # China Server = http://mirrors.ustc.edu.cn/chakra/$repo/x86_64 Server = http://mirrors.tuna.tsinghua.edu.cn/chakra/$repo/x86_64 # Colombia Server = http://mirror.edatel.net.co/chakra/$repo/x86_64 # France Server = http://www-ftp.lip6.fr/pub/linux/distributions/chakra/$repo/x86_64 Server = http://ftp.ciril.fr/pub/linux/chakra/$repo/x86_64 Server = http://elgrande74.net/chakra/packages/$repo/x86_64 Server = https://mirrors.deogracia.xyz/chakra/packages/$repo/x86_64 # Germany Server = http://ftp.halifax.rwth-aachen.de/chakra/$repo/x86_64 Server = http://mirror.selfnet.de/chakra/$repo/x86_64 Server = http://mirror.wh-stuttgart.net/chakra/$repo/x86_64 Server = https://mirror.alpix.eu/chakra/$repo/x86_64 #Server = https://rsync.chakralinux.org/packages/$repo/x86_64 # Greece Server = http://ftp.cc.uoc.gr/mirrors/linux/chakra/$repo/x86_64 # Italy Server = http://chakra.mirror.garr.it/mirrors/chakra/$repo/x86_64 # Russia Server = http://mirror.yandex.ru/mirrors/chakra/$repo/x86_64 # Sweden Server = http://ftp.acc.umu.se/mirror/chakralinux.org/packages/$repo/x86_64 # Switzerland Server = https://mirror.puzzle.ch/chakralinux/$repo/x86_64 # Taiwan Server = http://free.nchc.org.tw/chakra/packages/$repo/x86_64 Server = http://ftp.yzu.edu.tw/Linux/chakra/$repo/x86_64 Server = http://mirror.ossplanet.net/chakra/packages/$repo/x86_64 Server = http://ftp.ubuntu-tw.org/mirror/chakra/packages/$repo/x86_64 Server = http://ftp.tku.edu.tw/Linux/Chakra/packages/$repo/x86_64 # United States Server = http://mirror.rit.edu/chakra/$repo/x86_64 Server = http://www.gtlib.gatech.edu/pub/chakra/packages/$repo/x86_64 -- So I guess I'm using the one in Australia. I have kpat-debug installed since Albert asked me to use valgrind, but running valgrind kpat gets me a message saying the trace is useless... :-( -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404629] New: Alternative to .directory files for folder-specific view settings
https://bugs.kde.org/show_bug.cgi?id=404629 Bug ID: 404629 Summary: Alternative to .directory files for folder-specific view settings Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@i.yeb.me CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 118241 --> https://bugs.kde.org/attachment.cgi?id=118241=edit Current view settings window In Dolphin when you're in a folder and change any of its view settings, Dolphin will create a .directory file in the folder to remember these settings that are unique to the current folder. This gets annoying quickly: 1. It makes it hard to delete empty folders automatically, you can no longer just run a simple commands like "rmdir *" and "find -type d -empty -delete" etc. 2. It makes the process manually deleting empty folders more cumbersome. I can't just view the recursive folder properties to check it says 0 files then delete it. It's a time consuming process of turning on 'show hidden files' and manually checking that there's only .directory files in all the sub-folders of the tree. 3. They get in the way in other places, such as needing to add .directory to .gitignore and lots of other things like that, which often get forgotten, and some software makes it hard to ignore files. 4. It messes with the folder's modified timestamp - I can no longer look at the folder timestamp to actually see when an actual meaningful data change to the contents was made. 5. Just more general junk being distributed to remote systems like desktop.ini / .DS_Store /._* files that we see littered through projects and servers etc that is irrelevant to everyone except for the one-and-only person that the files passed through where the junk got added. I know I can just disable custom view settings altogether with "Use common properties for all folders", but I still want to be able to set + remember custom view settings on my local folders. It would be great if there were an option to leave the target directory itself untouched, and instead just store this data somewhere under ~/.cache/dolphin or ~/.config/dolphin or somewhere like that. Yes - of course this means that if you rename/move the folder, the settings are lost. But it's not anything important being lost, for me that's much more preferable to the current .directory littering everywhere, or disabling custom views entirely. Alternatively maybe these settings could be stored in extended filesystem attributes (I guess that won't work on NTFS etc though?). In this case it could just fall back to .directory or not remembering settings on those filesystems. I'm not saying that the .directory files should be abandoned completely, or that we should change the default behaviour ... just an option would be nice so that we can pick between .directory -or- ~/.cache/dolphin See the attached screenshot of: Dolphin > Settings > Configure Dolphin > General tab > Behavior tab > View ... It currently has the options: - Remember properties for each folder - Use common properties for all folders I propose changing this to something like: - Remember properties for each folder using .directory files - Remember properties for each folder using ~/.cache/dolphin - Use common properties for all folders ...or... - Remember properties for each folder using .directory files - Remember properties for each folder using extended filesystem attributes - Use common properties for all folders -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398317] Login and lock screen text have no shadows when using software rendering
https://bugs.kde.org/show_bug.cgi?id=398317 --- Comment #8 from Christoph Feck --- Gianni, I suggest to either re-open or report the cropping issue as a new ticket. Closed tickets are rarely revisited by developers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404628] New: When virtual desktops are swapped, it is reflected in other activities
https://bugs.kde.org/show_bug.cgi?id=404628 Bug ID: 404628 Summary: When virtual desktops are swapped, it is reflected in other activities Product: kwin Version: 5.15.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: henriquesarmentogoulartagu...@gmail.com Target Milestone: --- SUMMARY When I swap virtual desktop through the "Desktop Grid" effect (by dragging on an empty space, rather than a window), I have noticed the change reflects in other activities - their virtual desktops and windows have been swapped too. STEPS TO REPRODUCE 1. Have at least two activities; 2. Place distinct windows on two different virtual desktops (e.g. Kate on activity 1 desktop 1, Konsole on activity 1 desktop 2; Dolphin on activity 2 desktop 1, System Settings on activity 2 desktop 2), and take note of the placement of each application/window; 3. On one activity, activate Desktop Grid; 4. Drag on an empty space of a desktop (e.g. Activity 1, desktop 1), and swap it with the other desktop (e.g. Activity 1, desktop 2) - as per the example above, this'll make it so Kate is on desktop 2, and Konsole now on desktop 1. OBSERVED RESULT The swapped desktops will be reflected on other activities. Still using the example, if you go back to activity 2, you'll notice System Settings is in desktop 1, and Dolphin on desktop 2. EXPECTED RESULT As activities are separate and independent, this shouldn't happen. SOFTWARE/OS VERSIONS OS: Manjaro (2019-02-19) Kernel Version: 4.19.23-1-MANJARO KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION I have four activities, with four virtual desktop each. Two activities have been stopped/frozen, however, for the entire duration of when I've noticed and tested this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404620] openGL app on plasma makes plasma crash with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=404620 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #3 from Christoph Feck --- Crashes in libnvidia-glcore.so.410.93 Please report this issue directly to NVIDIA developers via https://devtalk.nvidia.com/default/topic/522835/linux/if-you-have-a-problem-please-read-this-first/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401227] Global hotkey resets with each restart
https://bugs.kde.org/show_bug.cgi?id=401227 David changed: What|Removed |Added CC||avi...@gmail.com --- Comment #5 from David --- If you have text selected, the middle mouse button pastes that text. It doesn't mean pressing alt+= is assigned to copying text. I'm getting the same issue, but with my "9" key (I had to use the number pad to type that.) For me, with xev -root, pressing "9" gives: FocusIn event, serial 21, synthetic NO, window 0x111, mode NotifyGrab, detail NotifyInferior KeymapNotify event, serial 21, synthetic NO, window 0x0, keys: 1 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 PropertyNotify event, serial 21, synthetic NO, window 0x111, atom 0x14d (CLIP_TEMPORARY), time 67595257, state PropertyNewValue FocusOut event, serial 21, synthetic NO, window 0x111, mode NotifyUngrab, detail NotifyInferior PropertyNotify event, serial 21, synthetic NO, window 0x111, atom 0x14d (CLIP_TEMPORARY), time 67595259, state PropertyDelete My "9" key is not assigned to "copy" but to something else. If I go to Settings and Global Shortcuts configuration, go to an unused shortcut and press the reassign button, I can press "9" to assign it to that shortcut. If I then delete the assignment again without applying, I regain normal use of my "9" key (until the next reboot). I think there is definitely a bug here. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403978] oxygen theme incompatible with qt5 5.12.1-1 libs
https://bugs.kde.org/show_bug.cgi?id=403978 Christoph Feck changed: What|Removed |Added CC||beth...@gmail.com --- Comment #14 from Christoph Feck --- *** Bug 404109 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404109] Oxygen theme causes Plasmashell's giant memory leak
https://bugs.kde.org/show_bug.cgi?id=404109 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 403978 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404109] Oxygen theme causes Plasmashell's giant memory leak
https://bugs.kde.org/show_bug.cgi?id=404109 --- Comment #2 from Christoph Feck --- Looks like https://bugreports.qt.io/browse/QTBUG-73691 But it isn't yet sure if the bug is in Qt, or actually in Oxygen. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 403690] new tab should be opened after the current tab in tab list, not at the end
https://bugs.kde.org/show_bug.cgi?id=403690 --- Comment #8 from vini.ipsma...@gmail.com --- > Please test it out to see if it works as expected :) Almost. Indeed, opening the folder in a new tab from the context menu will open the folder in the right-hand side of current tab. However, if I middle-click some folder, it'll be added to the end of the tab list. It should have the same behaviour described in previous paragraph. Opening a new tab with Ctrl+T will keep the previous behaviour, adding to the end of list. This is the correct behaviour for new unrelated tabs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404627] New: Desktop grid does not deactivate through the same shortcut in Wayland
https://bugs.kde.org/show_bug.cgi?id=404627 Bug ID: 404627 Summary: Desktop grid does not deactivate through the same shortcut in Wayland Product: kwin Version: 5.15.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: henriquesarmentogoulartagu...@gmail.com Target Milestone: --- SUMMARY Unlike on XOrg, when I activate the "Desktop Grid" effect through the assigned shortcut (namely, meta+tab) in Wayland, when I use the same shortcut, I am not returned to the virtual desktop. Instead, I must manually select one, through the cursor or meta+[number]. STEPS TO REPRODUCE 1. Enable "Desktop Grid" effect; 2. Use the assigned shortcut to activate it. 3. Attempted to use it again to deactivate it. OBSERVED RESULT Nothing happens; a virtual desktop must be selected through the cursor, or meta+[number]. EXPECTED RESULT To be restored to the virtual desktop I was in before. SOFTWARE/OS VERSIONS OS: Manjaro (2019-02-19) Kernel: 4.19.23-1-MANJARO KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION I use the shortcut meta+tab -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 404225] Feature req: save current view state with regards to visible date
https://bugs.kde.org/show_bug.cgi?id=404225 --- Comment #3 from mach...@gmail.com --- "Save page state" did not work for me. However, "Overwrite bookmark state" did work. (Plus saving on close.) Thanks! (Bug can be closed.) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 404559] Rename dialog should not put spaces in suggested filenames
https://bugs.kde.org/show_bug.cgi?id=404559 Christoph Feck changed: What|Removed |Added Resolution|INTENTIONAL |DUPLICATE --- Comment #4 from Christoph Feck --- An unobstrusive way would be: - "file.txt" collision detected - User clicks "Suggest New Name" - Dialog suggests "file (1).txt" - User edits the suggestion to e.g. "Copy 1 of file.txt" or "file[001].txt" - Dialog remembers these changes as the template for further suggestions (and for automatic suggestions) A requirement would be that the original filename and extension is still part of the edited suggestion, and that at least one field with a number is still part of the additions. Otherwise automatic suggestions cannot work, and it would fall back to the "Name (#).ext" for next suggestions. Good luck :) *** This bug has been marked as a duplicate of bug 317320 *** -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 317320] When pasting a file with a name that exists already in the folder, no space should be inserted in the suggested new name
https://bugs.kde.org/show_bug.cgi?id=317320 Christoph Feck changed: What|Removed |Added CC||r...@alum.mit.edu --- Comment #13 from Christoph Feck --- *** Bug 404559 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[step] [Bug 404626] New: Problem opening files and examples
https://bugs.kde.org/show_bug.cgi?id=404626 Bug ID: 404626 Summary: Problem opening files and examples Product: step Version: 0.1.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ks.vladi...@gmail.com Reporter: divineblasphem...@gmail.com Target Milestone: --- Created attachment 118240 --> https://bugs.kde.org/attachment.cgi?id=118240=edit Error obtain by clicking any .step file SUMMARY HI! I'm having troubles with step... STEPS TO REPRODUCE 1. I opened a .step file 2. An error appeared saying "wrong format URL" OBSERVED RESULT I haven't been able to open any .step file! (even saving my own simulations the error appeared) Thanks for your help! SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 27 KDE Plasma Version: KDE Frameworks 5.54.0 Qt 5.11.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404483] Multicolor works wrong when Im using Active Screen Corners and Edges to show desktop
https://bugs.kde.org/show_bug.cgi?id=404483 --- Comment #29 from Michail Vourlakos --- (In reply to Jacobtey from comment #27) > (In reply to Jacobtey from comment #18) > > And pay attention to attachments 0.8.5 and 0.8.6. The resulting changes are > > not associated with plasma's active edges. > > Or I should create a new bugreport for it? > > What should i do with this? I suddenly found out that this is a special case > of another global problem. If you open NOT maximized window over another > maximized one, the panel background disappears yes open a new bug report for this because it needs to be discussed, concerning what colors should be shown in that case. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 398996] Konqueror is running in the background after quit
https://bugs.kde.org/show_bug.cgi?id=398996 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com --- Comment #3 from Rex Dieter --- In some brief testing, I found by going to settings->configure konqueror -> performance -> *uncheck* always try to have one preloaded instance seems to avoid this problem for me. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404613] Docs are missing
https://bugs.kde.org/show_bug.cgi?id=404613 --- Comment #2 from Christoph Feck --- https://cgit.kde.org/digikam says there is a separate repository for the documentation. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404625] New: Abnormal spacing between elements / icons on Icons view
https://bugs.kde.org/show_bug.cgi?id=404625 Bug ID: 404625 Summary: Abnormal spacing between elements / icons on Icons view Product: dolphin Version: 18.12.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: spiral_wa...@zoho.com Target Milestone: --- SUMMARY Files & folders with long names creates abnormal spacing between elements which makes it hard to search to the naked eye due to high inconsistency . I'm aware you can limit the number of lines used for names on Dolphin's option... which fix the weird spacing but on a real-life scenario working with multimedia files that needs A LOT of informative tags that you need to check while working with those files & folders... the readability is totally ruined and makes it really hard to spot the full name ( you can check the status bar if the folder/file is highlited... but let's agree this is far from ideal ) . This seems to be an old but i'm surprised nobody else mentioned before... from what i've seen this doesn't happen on other Linux DE's ( on other DE's you can see the full long name when the file/folder is highlighted/ selected ) STEPS TO REPRODUCE 1. On Icons-view creat one folder 2. Inside that folder create 3 + 3 rows of files & folders with random names using 2-3-4-5-6 lines OBSERVED RESULT You should be looking at the weirdest spacing between elements, with the max space between elements being determined by the file/folder with the longest name... and a lot of empty space below files/folders with short names . EXPECTED RESULT Files & folders should keep equal distance between elements despite the file/folder name's length. It's been like that on other DE's & OSs for years, you can check any other popular DE for reference . SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon user edition ( 18.04 based ) up to date KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403015] Shortcut ALT+U (bash: make word uppercase) not working, just cursor blinking
https://bugs.kde.org/show_bug.cgi?id=403015 Mariusz Glebocki changed: What|Removed |Added Summary|shortcut ALT+U not working |Shortcut ALT+U (bash: make |, just cursor blinking |word uppercase) not ||working, just cursor ||blinking CC||m...@arccos-1.net --- Comment #2 from Mariusz Glebocki --- Works here as well. What is selected in right click → edit profile settings → keyboard? Does alt+u works in other graphical terminal emulators, e.g. xterm, gnome-terminal? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404624] New: When details for an update are shown, the list of update does not show the new version anymore
https://bugs.kde.org/show_bug.cgi?id=404624 Bug ID: 404624 Summary: When details for an update are shown, the list of update does not show the new version anymore Product: Discover Version: 5.15.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: thomas.pfeif...@kde.org CC: aleix...@kde.org Target Milestone: --- Created attachment 118239 --> https://bugs.kde.org/attachment.cgi?id=118239=edit Screenshot of the problem SUMMARY When the details for an update are shown, the column with the list of updates becomes narrow and only the current package version is still visible STEPS TO REPRODUCE 1. Go to Updates 2. Click on a package 3. Click "Show Details" (or whatever the button is labeled) OBSERVED RESULT Only the current version is visible in the list of updates EXPECTED RESULT The new version is still visible 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.
[latte-dock] [Bug 404483] Multicolor works wrong when Im using Active Screen Corners and Edges to show desktop
https://bugs.kde.org/show_bug.cgi?id=404483 --- Comment #28 from Jacobtey --- Created attachment 118238 --> https://bugs.kde.org/attachment.cgi?id=118238=edit background -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404483] Multicolor works wrong when Im using Active Screen Corners and Edges to show desktop
https://bugs.kde.org/show_bug.cgi?id=404483 --- Comment #27 from Jacobtey --- (In reply to Jacobtey from comment #18) > And pay attention to attachments 0.8.5 and 0.8.6. The resulting changes are > not associated with plasma's active edges. > Or I should create a new bugreport for it? What should i do with this? I suddenly found out that this is a special case of another global problem. If you open NOT maximized window over another maximized one, the panel background disappears -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 404161] kpat crashes when trying to play the second or third different game
https://bugs.kde.org/show_bug.cgi?id=404161 --- Comment #12 from Adrián Chaves (Gallaecio) --- When I said repositories, I meant mirrors, but to be honest it’s a long stretch. I can’t think of a good reason why it would crash for you and not for me. If you are really invested into getting this fixed, I guess the best steps to follow now would be to install the kpat-debug package (Chakra includes separate -debug packages for all KDE software, which should make tracebacks more useful), and see if you can get a more useful backtrace then. Bona sort! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 297219] Places pane shows all unmounted nfs mounts from /etc/fstab, which could be a very very long list
https://bugs.kde.org/show_bug.cgi?id=297219 Stefan Brüns changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #18 from Stefan Brüns --- I mentioned x-gvfs-hide 10 months ago, including a link. If you ignore it, that's your fault. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404621] I can not import the album Google Photo
https://bugs.kde.org/show_bug.cgi?id=404621 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The image are downloaded, but without a file extension and therefore not visible for digiKam. We get from the GPhoto API only the image without the title. I will fix it. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404623] Desktop is NOT unloading properly the SlideShow wallpaper plugin
https://bugs.kde.org/show_bug.cgi?id=404623 Michail Vourlakos changed: What|Removed |Added Summary|Desktop is loading |Desktop is NOT unloading |unloading properly the |properly the SlideShow |SlideShow wallpaper plugin |wallpaper plugin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404623] New: Desktop is loading unloading properly the SlideShow wallpaper plugin
https://bugs.kde.org/show_bug.cgi?id=404623
Bug ID: 404623
Summary: Desktop is loading unloading properly the SlideShow
wallpaper plugin
Product: plasmashell
Version: 5.15.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Image Wallpaper
Assignee: notm...@gmail.com
Reporter: mvourla...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
SUMMARY
I discovered a case that the slideshow wallpaper plugin is not unloaded
properly when the Activity for which is assigned is stopped
STEPS TO REPRODUCE
1. Add in slideshow plugin at its main.qml file and more specific for its
onModelImageChanged the following:
onModelImageChanged: {
Qt.callLater(loadImage);
console.log("NEW SLIDESHOW IMAGE ::: " + modelImage);
}
2. Go into a new Activity and activate for it the slideshow plugin
3. Set for SlideShow a very small interval e.g. 5secs
4. When the Activity is running you will notice that properly it shows the
above inserted message
5. Stop now this Activity
6. You will keep noticing the above message and that never ends
EXPECTED RESULT
The inserted messages shouldnt be shown because the Desktop should be unloaded
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Tumbleweed / 5.15.0
KDE Plasma Version: 5.15.0
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.0
--
You are receiving this mail because:
You are watching all bug changes.
[latte-dock] [Bug 404483] Multicolor works wrong when Im using Active Screen Corners and Edges to show desktop
https://bugs.kde.org/show_bug.cgi?id=404483 --- Comment #26 from Jacobtey --- Created attachment 118237 --> https://bugs.kde.org/attachment.cgi?id=118237=edit Appearance new -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395390] After making the default panel vertically-oriented, Kickoff's layout is messed up until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=395390 --- Comment #16 from Piotr Mierzwinski --- Created attachment 118236 --> https://bugs.kde.org/attachment.cgi?id=118236=edit Changed colors of KickOff after applying Dmiry fix -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 404161] kpat crashes when trying to play the second or third different game
https://bugs.kde.org/show_bug.cgi?id=404161 --- Comment #11 from Víktor --- Not sure what you mean about upgrading. Everything in core that has "(kf5)" is version 5.55.0-1 About building packages from sources, I think the only one I use is the telegram one, tdesktop. The repositories I'm using are lib32, core, desktop and gtk. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395390] After making the default panel vertically-oriented, Kickoff's layout is messed up until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=395390
--- Comment #15 from Piotr Mierzwinski ---
(In reply to Dmitry Khlestkov from comment #13)
> I'm using locally modified version of kickoff with this modifications for
> "left" orientation (ui/FullRepresentation.qml):
>
> AnchorChanges {
> target: tabBar
> anchors {
> left: root.left
> - top: root.top
> right: undefined
> bottom: header.top
> }
> }
>
> + PropertyChanges {
> + target: tabBar
> + height: units.gridUnit * 29
> + }
>
> E.g. anchors.top replaced with implicit height. Similar workaround may be
> applied to "right" orientation. Obviously height should be calculated from
> tab count instead of being hardcoded.
>
> Yes, this is not a proper fix but we can't be picky at this moment, can we?
> I've reported this issue 10 months ago and no one seems to have skills
> and/or resolve to fix it properly.
I applied your changes to the "right" orientation. Issue with disappearing
button seems to be fixed, but unfortunately body (place where I see for example
"All Applications") just changed color or actually became much brightest (looks
like all would be disabled) than right vertical bar with buttons. Note that in
original version color body and vertical bar are the same. I suppose this is
because of using "tabBar" in "PropertyChanges".
I use Breeze dark scheme and kvantum addon.
After changes I restarted plasmashell like this:
kbuildsycoca5 && kquitapp5 plasmashell && kstart5 plasmashell
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 398741] Improve system-switch-user icon in system.svgz
https://bugs.kde.org/show_bug.cgi?id=398741 Nate Graham changed: What|Removed |Added Latest Commit||https://cgit.kde.org/plasma ||-framework.git/commit/?id=e ||1248d68c27c3aea74f776089b9a ||1ca0184faa7d Version Fixed In||5.56 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398741] Improve system-switch-user icon in system.svgz
https://bugs.kde.org/show_bug.cgi?id=398741 Krešimir Čohar changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||kco...@gmail.com --- Comment #2 from Krešimir Čohar --- Resolved as part of https://phabricator.kde.org/D19020 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 404484] --include-dependencies does not pull in qt5
https://bugs.kde.org/show_bug.cgi?id=404484 --- Comment #5 from jm.ouwerk...@gmail.com --- Okay so with updated understanding on my part: - We do not want to edit metadata because we're not the only consumer - Instead we want some 'magic' in kdesrc-build which: 1. Should detect whether or not qt5 module set/submodules are *available* 2. Should detect whether or not they are (implicitly) required 3. Should then update the internal dependency state in kdesrc-build to include qt5/submodules - This logic should trigger only in specific circumstances. Exact trigger TBD. E.g. only when using `--include-dependencies`? Any specific "but omit these module" type switches that might conflict and should presumably take precedence? Also: maybe add a simple `--try-building-qt5` switch for testing during development while we figure out the exact trigger conditions here? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 404605] SDDM themes installed via Discover are not listed in KCM_SDDM
https://bugs.kde.org/show_bug.cgi?id=404605 --- Comment #4 from Patrick Silva --- kcm has the same bug described in discover's bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 404605] SDDM themes installed via Discover are not listed in KCM_SDDM
https://bugs.kde.org/show_bug.cgi?id=404605 --- Comment #3 from Nate Graham --- That bug is about Discover, though. Not the SDDM KCM. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404620] openGL app on plasma makes plasma crash with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=404620 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Mathias Homann --- The crashes happen only when running any of the various Second Life clients... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402818] Escape key doesn't cancel dragging task
https://bugs.kde.org/show_bug.cgi?id=402818 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404621] I can not import the album Google Photo
https://bugs.kde.org/show_bug.cgi?id=404621 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|Import-Albums |Export-Google -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 404486] kdesrc-build should consider adjusting PATH to find tools in qtdir
https://bugs.kde.org/show_bug.cgi?id=404486 jm.ouwerk...@gmail.com changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||kdesrc-build/commit/69ca1a3 ||1fcd294e0f02196716124718849 ||f2b780 --- Comment #6 from jm.ouwerk...@gmail.com --- Git commit 69ca1a31fcd294e0f02196716124718849f2b780 by Johan Ouwerkerk. Committed on 20/02/2019 at 19:16. Pushed by ouwerkerk into branch 'master'. Consider and prefer using tools from qtdir/bin and kdedir/bin if available. Fixes: #18 Differential Revision: https://phabricator.kde.org/D19127 M +5-1modules/ksb/Application.pm M +7-4modules/ksb/Util.pm https://invent.kde.org/kde/kdesrc-build/commit/69ca1a31fcd294e0f02196716124718849f2b780 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404622] New: Discover crashed when closed immediately after opening
https://bugs.kde.org/show_bug.cgi?id=404622 Bug ID: 404622 Summary: Discover crashed when closed immediately after opening Product: Discover Version: 5.15.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: bugsefor...@gmx.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.15.1) Qt Version: 5.12.1 Frameworks Version: 5.55.0 Operating System: Linux 4.20.10-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I opened Discover via kickoff and closed it immediately. I can't reproduce consistently. The crash can be reproduced sometimes. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9e64a80e40 (LWP 13743))] Thread 14 (Thread 0x7f9e36912700 (LWP 13965)): [KCrash Handler] #6 0x7f9e376b40e8 in flatpak_installation_list_installed_refs_for_update () at /usr/lib/libflatpak.so.0 #7 0x7f9e48053abe in () at /usr/lib/qt/plugins/discover/flatpak-backend.so #8 0x7f9e69368a11 in () at /usr/lib/libQt5Core.so.5 #9 0x7f9e6936496c in () at /usr/lib/libQt5Core.so.5 #10 0x7f9e6848aa9d in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f9e6904eb23 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f9e35910700 (LWP 13919)): #0 0x7f9e68490ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9e6936abc9 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f9e6936ad07 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f9e69368c2b in () at /usr/lib/libQt5Core.so.5 #4 0x7f9e6936496c in () at /usr/lib/libQt5Core.so.5 #5 0x7f9e6848aa9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f9e6904eb23 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f9e13dbb700 (LWP 13787)): #0 0x7f9e69043c21 in poll () at /usr/lib/libc.so.6 #1 0x7f9e67634540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f9e6763462e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f9e69576d04 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f9e6951fb2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f9e69363569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f9e6936496c in () at /usr/lib/libQt5Core.so.5 #7 0x7f9e6848aa9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f9e6904eb23 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f9e37fff700 (LWP 13765)): #0 0x7f9e68490ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9e6936abc9 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f9e6936ad07 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f9e69368c2b in () at /usr/lib/libQt5Core.so.5 #4 0x7f9e6936496c in () at /usr/lib/libQt5Core.so.5 #5 0x7f9e6848aa9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f9e6904eb23 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f9e4886b700 (LWP 13764)): #0 0x7f9e6903f7a4 in read () at /usr/lib/libc.so.6 #1 0x7f9e675e2971 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f9e676330b0 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f9e676344e6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f9e6763462e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f9e69576d04 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f9e6951fb2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f9e69363569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f9e6936496c in () at /usr/lib/libQt5Core.so.5 #9 0x7f9e6848aa9d in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f9e6904eb23 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f9e490e6700 (LWP 13763)): #0 0x7f9e6903f7a4 in read () at /usr/lib/libc.so.6 #1 0x7f9e675e2971 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f9e676330b0 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f9e676344e6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f9e6763462e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f9e69576d04 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f9e6951fb2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f9e69363569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f9e6936496c in () at
[okular] [Bug 383651] Custom/image stamp annotations are not saved into the PDF file in a way that can be printed or that other readers can see
https://bugs.kde.org/show_bug.cgi?id=383651 Dimitrios T Tanis changed: What|Removed |Added CC||dimitrios.ta...@kdemail.net --- Comment #25 from Dimitrios T Tanis --- Is there any update on this? I agree with Kevin that data loss can be a buzz but when advocating for the bells and whistles of linux and KDE as a pro business environment, sending an annotated pdf that others can't view is even worst (I've just been hit by that). It's been quite a few years since I've coded in C++ and Qt so I can't be of use in coding but I can help with testing if needed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404621] New: I can not import the album Google Photo
https://bugs.kde.org/show_bug.cgi?id=404621 Bug ID: 404621 Summary: I can not import the album Google Photo Product: digikam Version: 6.0.0 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Import-Albums Assignee: digikam-bugs-n...@kde.org Reporter: ok...@i.ua Target Milestone: --- Created attachment 118235 --> https://bugs.kde.org/attachment.cgi?id=118235=edit screenshot SUMMARY STEPS TO REPRODUCE 1. Import 2. Import from Google Photo 3. Select album OBSERVED RESULT Failed to save image to D:/Photos//image-2009-05-05T13:40:51Z EXPECTED RESULT D:/Photos/image-2009-05-05T13:40:51Z SOFTWARE/OS VERSIONS Windows: Windows 10 64x MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 241726] BQM Resize tool : make options more flexible [patch]
https://bugs.kde.org/show_bug.cgi?id=241726 Sambhav Dusad changed: What|Removed |Added Attachment #118169|0 |1 is obsolete|| Attachment #118233|0 |1 is obsolete|| --- Comment #17 from Sambhav Dusad --- Created attachment 118234 --> https://bugs.kde.org/attachment.cgi?id=118234=edit New Improvements -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404620] openGL app on plasma makes plasma crash with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=404620 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from David Edmundson --- >Running an openGL app Can you be more specific. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404620] New: openGL app on plasma makes plasma crash with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=404620 Bug ID: 404620 Summary: openGL app on plasma makes plasma crash with nvidia drivers Product: plasmashell Version: 5.15.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mathias.hom...@opensuse.org CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.15.1) Qt Version: 5.12.1 Frameworks Version: 5.55.0 Operating System: Linux 4.12.14-lp150.12.48-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: Running an openGL app. These crashes have become somewhat less frequent since I updated to the latest 4xx driver series, but they still happen occasionally. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7faad3958940 (LWP 3148))] Thread 19 (Thread 0x7faa48857700 (LWP 9538)): #0 0x7faaca1ba89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faacd43b92b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7faacd43bc39 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7faad17d4658 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7faad17d4a8a in () at /usr/lib64/libQt5Quick.so.5 #5 0x7faacd4347e2 in () at /usr/lib64/libQt5Core.so.5 #6 0x7faaca1b4559 in start_thread () at /lib64/libpthread.so.0 #7 0x7faaccd3581f in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7faa49058700 (LWP 9537)): #0 0x7faaccd2b07b in poll () at /lib64/libc.so.6 #1 0x7faa867ef831 in () at /usr/lib64/libpulse.so.0 #2 0x7faa867e11f0 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7faa867e1880 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7faa867e1910 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7faa867ef779 in () at /usr/lib64/libpulse.so.0 #6 0x7faa86389438 in () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so #7 0x7faaca1b4559 in start_thread () at /lib64/libpthread.so.0 #8 0x7faaccd3581f in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7faa4a7fd700 (LWP 8249)): #0 0x7faaca1ba89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faacd43b92b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7faacd43bc39 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7faad17d4658 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7faad17d4a8a in () at /usr/lib64/libQt5Quick.so.5 #5 0x7faacd4347e2 in () at /usr/lib64/libQt5Core.so.5 #6 0x7faaca1b4559 in start_thread () at /lib64/libpthread.so.0 #7 0x7faaccd3581f in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7faa4affe700 (LWP 8237)): #0 0x7faaca1ba89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faacd43b92b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7faacd43bc39 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7faad17d4658 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7faad17d4a8a in () at /usr/lib64/libQt5Quick.so.5 #5 0x7faacd4347e2 in () at /usr/lib64/libQt5Core.so.5 #6 0x7faaca1b4559 in start_thread () at /lib64/libpthread.so.0 #7 0x7faaccd3581f in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7faa69042700 (LWP 7221)): #0 0x7faaca1ba89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faacd43b92b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7faacd43bc39 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7faad17d4658 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7faad17d4a8a in () at /usr/lib64/libQt5Quick.so.5 #5 0x7faacd4347e2 in () at /usr/lib64/libQt5Core.so.5 #6 0x7faaca1b4559 in start_thread () at /lib64/libpthread.so.0 #7 0x7faaccd3581f in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7faa715c5700 (LWP 5583)): #0 0x7faaca1ba89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faacd43b92b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7faacd43bc39 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7faad17d4658 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7faad17d4a8a in () at /usr/lib64/libQt5Quick.so.5 #5 0x7faacd4347e2 in () at /usr/lib64/libQt5Core.so.5 #6
[plasmashell] [Bug 404619] New: After I set del key as shortcut to delete files, plasma sends file to trash when I cancel the dialog to confirm permanent deletion
https://bugs.kde.org/show_bug.cgi?id=404619 Bug ID: 404619 Summary: After I set del key as shortcut to delete files, plasma sends file to trash when I cancel the dialog to confirm permanent deletion Product: plasmashell Version: 5.14.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. search for "standard shorcuts" kcm in the apps launcher and open it 2. search for "delete" action, change current shortcut to delete key, apply the change 3. restart plasma 4. select any file located on your desktop 5. press delete key 6. a dialog shows up asking for your confirmation to delete the file permanently (click "Cancel" button) OBSERVED RESULT plasma sends your file to trash EXPECTED RESULT the file remains on your desktop SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 Additional info Observed result does not occur if I use context menu + shift key instead of keyboard shorcut. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404483] Multicolor works wrong when Im using Active Screen Corners and Edges to show desktop
https://bugs.kde.org/show_bug.cgi?id=404483 --- Comment #25 from Jacobtey --- (In reply to Michail Vourlakos from comment #22) > forget [1]-[3] I manage to reproduce... > > it happens only when there is a maximized window and afterward we try to > show desktop correct ? sure -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404483] Multicolor works wrong when Im using Active Screen Corners and Edges to show desktop
https://bugs.kde.org/show_bug.cgi?id=404483 --- Comment #24 from Jacobtey --- (In reply to Michail Vourlakos from comment #21) > 1. something is very strange in your system, it looks as if compositing is > NOT enabled there are no animations from kwin > 2. [screenshot] from plasma systemsettings -> display and monitor -> > Compositor > 3. [screenshot] from top panel -> Appearance advanced settings. I am > interested for Colors and Background sections I turned off the compositing while recording screencast, to save resources (In reply to Michail Vourlakos from comment #21) > 1. something is very strange in your system, it looks as if compositing is > NOT enabled there are no animations from kwin > 2. [screenshot] from plasma systemsettings -> display and monitor -> > Compositor > 3. [screenshot] from top panel -> Appearance advanced settings. I am > interested for Colors and Background sections I turned off the compositing while recording screencast, to save resources -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404540] [feature] new indicator style from Gnome's Dash to Panel
https://bugs.kde.org/show_bug.cgi?id=404540 Michail Vourlakos changed: What|Removed |Added Summary|For Latte dock, option to |[feature] new indicator |have alternative indicator |style from Gnome's Dash to |style copied from Gnome's |Panel |Dash to Panel. | -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404539] [feature] - option to require pressure to show the panel.
https://bugs.kde.org/show_bug.cgi?id=404539 --- Comment #1 from Michail Vourlakos --- this has been requested many times my opinion for the matter is very strict: 1. Someone must support this in KWin and Latte will afterwards support it 2. If there is someone that wants to add it in Latte no problem but he is going to maintain it afterwards (if this could also wayland compatible, even better) 3. Personally I am not interested at all -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404539] [feature] - option to require pressure to show the panel.
https://bugs.kde.org/show_bug.cgi?id=404539 Michail Vourlakos changed: What|Removed |Added Summary|Option to require pressure |[feature] - option to |to show the panel. |require pressure to show ||the panel. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 404225] Feature req: save current view state with regards to visible date
https://bugs.kde.org/show_bug.cgi?id=404225 --- Comment #2 from Stephane MANKOWSKI --- Do you have an answer? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404618] Request: Add actions for selecting current desktop
https://bugs.kde.org/show_bug.cgi?id=404618 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from David Edmundson --- What do you mean by actions? In the context menu? -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404483] Multicolor works wrong when Im using Active Screen Corners and Edges to show desktop
https://bugs.kde.org/show_bug.cgi?id=404483 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit||https://commits.kde.org/lat ||te-dock/c6178e58bde07324ced ||5db91ecaf08abee90b852 --- Comment #23 from Michail Vourlakos --- Git commit c6178e58bde07324ced5db91ecaf08abee90b852 by Michail Vourlakos. Committed on 20/02/2019 at 20:52. Pushed by mvourlakos into branch 'master'. only touching windows at DynamicBackground criteria --at the same time disable Blur for isBusy state of panel drawing M +1-2containment/package/contents/ui/VisibilityManager.qml M +4-5containment/package/contents/ui/main.qml https://commits.kde.org/latte-dock/c6178e58bde07324ced5db91ecaf08abee90b852 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404618] New: Request: Add actions for selecting current desktop
https://bugs.kde.org/show_bug.cgi?id=404618 Bug ID: 404618 Summary: Request: Add actions for selecting current desktop Product: plasmashell Version: 5.15.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Pager Assignee: h...@kde.org Reporter: andydecle...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Two existing actions would be a natural fit for this feature of the pager: - Present windows -- current desktop - Desktop grid ( org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.invokeShortcut ShowDesktopGrid ) The only options right now are: - do nothing - show current desktop SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 Related: https://bugs.kde.org/show_bug.cgi?id=379319 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404617] New: KWin Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=404617 Bug ID: 404617 Summary: KWin Crashes After Waking Up From Sleep Product: kwin Version: 5.15.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: arjungme...@gmail.com Target Milestone: --- Application: kwin_x11 (5.15.1) Qt Version: 5.12.1 Frameworks Version: 5.55.0 Operating System: Linux 4.20.10-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I put my computer to sleep through the K Start Menu. When it wakes up, KWin consistently crashs. I'm running Arch Linux, with all of the latest stable Plasma and other KDE applications. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f516b1f2840 (LWP 871))] Thread 5 (Thread 0x7f51523d3700 (LWP 970)): #0 0x7f51717c4afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f51722c928c in () at /usr/lib/libQt5Script.so.5 #2 0x7f51722c92a9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f51717bea9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f5173e75b23 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f515b895700 (LWP 965)): #0 0x7f5173e6ad16 in ppoll () at /usr/lib/libc.so.6 #1 0x7f51729e2bab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f51729e408b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f517298fb2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f51727d3569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f5170f7b969 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f51727d496c in () at /usr/lib/libQt5Core.so.5 #7 0x7f51717bea9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f5173e75b23 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f5169a35700 (LWP 936)): #0 0x7f5173e6ad16 in ppoll () at /usr/lib/libc.so.6 #1 0x7f51729e2bab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f51729e408b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f517298fb2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f51727d3569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f51709e0ba6 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f51727d496c in () at /usr/lib/libQt5Core.so.5 #7 0x7f51717bea9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f5173e75b23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f516aa96700 (LWP 928)): #0 0x7f5173e6ac21 in poll () at /usr/lib/libc.so.6 #1 0x7f51726f8630 in () at /usr/lib/libxcb.so.1 #2 0x7f51726fa2db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f516adbe949 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f51727d496c in () at /usr/lib/libQt5Core.so.5 #5 0x7f51717bea9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f5173e75b23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f516b1f2840 (LWP 871)): [KCrash Handler] #6 0x7f51724d5739 in () at /usr/lib/libkwin4_effect_builtins.so.1 #7 0x7f51724d57f6 in () at /usr/lib/libkwin4_effect_builtins.so.1 #8 0x7f51724d6df8 in () at /usr/lib/libkwin4_effect_builtins.so.1 #9 0x7f51724d7812 in () at /usr/lib/libkwin4_effect_builtins.so.1 #10 0x7f5173be0774 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #11 0x7f5172446ffa in () at /usr/lib/libkwin4_effect_builtins.so.1 #12 0x7f5173be0774 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #13 0x7f517253a51d in KWin::Effect::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwineffects.so.12 #14 0x7f5173be0774 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #15 0x7f517253a51d in KWin::Effect::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwineffects.so.12 #16 0x7f5173be0774 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #17 0x7f5173bcac3d in KWin::Scene::finalPaintWindow(KWin::EffectWindowImpl*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #18 0x7f5173be0605 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at
[frameworks-kio] [Bug 297219] Places pane shows all unmounted nfs mounts from /etc/fstab, which could be a very very long list
https://bugs.kde.org/show_bug.cgi?id=297219 Felix Miata changed: What|Removed |Added Resolution|INTENTIONAL |--- Status|RESOLVED|REOPENED --- Comment #17 from Felix Miata --- This bug lays fallow for 6 years, and then because I don't have time to respond within three weeks you close it? I don't know what x-gvfs-hide is. And, this is not about one user - it's about over a hundred users across at least 60 installations. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 241726] BQM Resize tool : make options more flexible [patch]
https://bugs.kde.org/show_bug.cgi?id=241726 --- Comment #16 from Maik Qualmann --- I have reset the development/dplugins branch before the first change to the resize tool. Save your resize.cpp and resize.h and syncronize your branch and play back your modified data and create a new patch. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404558] Very slow SDDM with Breeze theme when using plasma-workspace-5.15.0
https://bugs.kde.org/show_bug.cgi?id=404558 --- Comment #7 from Francesco Turco --- I'm not sure if related, but I also have another similar problem. Certain online videos (but not all) on Falkon are played in a terribly slow way on my system. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404483] Multicolor works wrong when Im using Active Screen Corners and Edges to show desktop
https://bugs.kde.org/show_bug.cgi?id=404483 --- Comment #22 from Michail Vourlakos --- forget [1]-[3] I manage to reproduce... it happens only when there is a maximized window and afterward we try to show desktop correct ? -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404483] Multicolor works wrong when Im using Active Screen Corners and Edges to show desktop
https://bugs.kde.org/show_bug.cgi?id=404483 --- Comment #21 from Michail Vourlakos --- 1. something is very strange in your system, it looks as if compositing is NOT enabled there are no animations from kwin 2. [screenshot] from plasma systemsettings -> display and monitor -> Compositor 3. [screenshot] from top panel -> Appearance advanced settings. I am interested for Colors and Background sections -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404603] Text is cut off in "Update" page when some update is unselected and the description of some update is open
https://bugs.kde.org/show_bug.cgi?id=404603 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Here's a patch: https://phabricator.kde.org/D19192 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404483] Multicolor works wrong when Im using Active Screen Corners and Edges to show desktop
https://bugs.kde.org/show_bug.cgi?id=404483 --- Comment #20 from Jacobtey --- https://www.youtube.com/watch?v=GCqptYLQoxw -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403015] shortcut ALT+U not working , just cursor blinking
https://bugs.kde.org/show_bug.cgi?id=403015 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- I can't confirm. alt+u works with konsole 18.12.2 on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 403040] '$'\n'' chars not shown in file name
https://bugs.kde.org/show_bug.cgi?id=403040 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404109] Oxygen theme causes Plasmashell's giant memory leak
https://bugs.kde.org/show_bug.cgi?id=404109 Benjamin Robin changed: What|Removed |Added CC||benjarobin+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 241726] BQM Resize tool : make options more flexible [patch]
https://bugs.kde.org/show_bug.cgi?id=241726 --- Comment #15 from Maik Qualmann --- Your patch can not be applied, you are not in sync with the git archive. Best you load your resize.cpp completely high. Maik -- You are receiving this mail because: You are watching all bug changes.
