[bindings] [Bug 381003] python3-pykde4 won't install due to broken dep on sip-py3api-11.2 (provided by python3-sip)
https://bugs.kde.org/show_bug.cgi?id=381003 --- Comment #2 from Bernard Gray--- (In reply to Bernard Gray from comment #1) > Is it possible to build python3-sip to include provides for sip-py3api-11.X > AND sip-py3api-12.X? Alternatively, can neon start including compatible builds of python3-pykde4 in their repos? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381145] New: Plasma Crashed While Browsing In Firefox
https://bugs.kde.org/show_bug.cgi?id=381145 Bug ID: 381145 Summary: Plasma Crashed While Browsing In Firefox Product: plasmashell Version: 5.10.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: m.sriram1...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.1) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.11.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was reading about discordjs in Firefox. It just happened randomly,out of nowhere. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f45dc423d80 (LWP 499))] Thread 9 (Thread 0x7f4520d62700 (LWP 628)): #0 0x7f45d055d6c5 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #1 0x7f45d055dba0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f45d055dd0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f45d6330e9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f45d62d721a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f45d60f940a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f45d9e48836 in () at /usr/lib/libQt5Quick.so.5 #7 0x7f45d60fdcbd in () at /usr/lib/libQt5Core.so.5 #8 0x7f45d52b2297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f45d5a0825f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f45265e1700 (LWP 627)): #0 0x7f45d52b839d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f452b5082fb in () at /usr/lib/xorg/modules/dri/r600_dri.so #2 0x7f452b508037 in () at /usr/lib/xorg/modules/dri/r600_dri.so #3 0x7f45d52b2297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f45d5a0825f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f4526de2700 (LWP 626)): #0 0x7f45d52b839d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f452b5082fb in () at /usr/lib/xorg/modules/dri/r600_dri.so #2 0x7f452b508037 in () at /usr/lib/xorg/modules/dri/r600_dri.so #3 0x7f45d52b2297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f45d5a0825f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f45b5f82700 (LWP 625)): #0 0x7f45d52b839d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f45dbb8bac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7f45dbb8bb09 in () at /usr/lib/libQt5Script.so.5 #3 0x7f45d52b2297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f45d5a0825f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f45b7fff700 (LWP 624)): #0 0x7f45d59fe2bd in poll () at /usr/lib/libc.so.6 #1 0x7f45d055dbf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f45d055dd0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f45d6330e9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f45d62d721a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f45d60f940a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f45d928a645 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f45d60fdcbd in () at /usr/lib/libQt5Core.so.5 #8 0x7f45d52b2297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f45d5a0825f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f45be59a700 (LWP 587)): #0 0x7f45d60f5d7f in QMutex::unlock() () at /usr/lib/libQt5Core.so.5 #1 0x7f45d6330797 in () at /usr/lib/libQt5Core.so.5 #2 0x7f45d055d601 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f45d055dba0 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f45d055dd0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f45d6330e9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f45d62d721a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f45d60f940a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f45d928a645 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f45d60fdcbd in () at /usr/lib/libQt5Core.so.5 #10 0x7f45d52b2297 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f45d5a0825f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f45b700 (LWP 527)): #0 0x7f45d055d63d in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #1 0x7f45d055dba0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f45d055dd0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f45d6330e9b in
[bindings] [Bug 381003] python3-pykde4 won't install due to broken dep on sip-py3api-11.2 (provided by python3-sip)
https://bugs.kde.org/show_bug.cgi?id=381003 --- Comment #1 from Bernard Gray--- Ok, I've worked it out what's actually going wrong. Apologies, lack of sleep and soforth: "python3-pykde4" is an ubuntu provided package, that depends on a virtual package "sip-py3api-11.2" provided by python3-sip (< 4.19) The neon repositories now include python3-sip=4.19.2+dfsg-1+16.04+xenial+build3 but this does not provide "sip-py3api-11.2" # apt-cache show python3-sip | egrep -e ^Provides -e ^Version Version: 4.19.2+dfsg-1+16.04+xenial+build3 Provides: sip-py3api-12.0, sip-py3api-12.1 ... Is it possible to build python3-sip to include provides for sip-py3api-11.X AND sip-py3api-12.X? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381031] Kmail crashes when shutting down, delaying the shutdown process
https://bugs.kde.org/show_bug.cgi?id=381031 --- Comment #3 from fr...@hmrt.nl --- Created attachment 106069 --> https://bugs.kde.org/attachment.cgi?id=106069=edit Backtrace from developer information tab It is reproducible on every shutdown. I have attached the information. Highest regards, Freek -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 381144] New: SmugMug export max dimension limited to 5000 pixels
https://bugs.kde.org/show_bug.cgi?id=381144 Bug ID: 381144 Summary: SmugMug export max dimension limited to 5000 pixels Product: kipiplugins Version: 5.8.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Smug Assignee: kde-imag...@kde.org Reporter: ronuk.ra...@gmail.com Target Milestone: --- SmugMug doesn't accept TIFF files. As a workaround, I can "resize photos before uploading" to get automatic conversion to JPEG, but the max dimensions range picker limits me to 5000 pixels. My pictures are larger than this and ideally I could get the format conversion without any resolution loss. I've submitted a diff at https://phabricator.kde.org/D6209, which I understand is supposed to be the new way to contributing. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 381115] tab completion in konsole freezes system for about 20s
https://bugs.kde.org/show_bug.cgi?id=381115 Bart Van Asschechanged: What|Removed |Added Ever confirmed|0 |1 CC||bvanass...@acm.org Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Bart Van Assche --- Same problem with konsole 17.04.1 on xfce. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow
https://bugs.kde.org/show_bug.cgi?id=381000 --- Comment #17 from sparhawk--- (In reply to Lars Altenhain from comment #13) > If I have the slideshow active on more than one activity the CPU load goes up > every time I wonder if that's similar to my situation, when I only see high CPU with slideshow on dual monitors. (I don't use activities.) (In reply to Chris Holland from comment #14) > What's your slideshow interval? > Does the cpu spike when the image changes? FWIW mine is ten minutes, and it's a constant high CPU, not a spike. Chris, did you manage to reproduce this bug with my settings file from comment #11? Otherwise I can try installing it in a new account and see if it's due to conflating issues, similar to Lars's findings. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 381022] RFE: enable Primary Clipboard support on "edit location"
https://bugs.kde.org/show_bug.cgi?id=381022 --- Comment #7 from Todd--- (In reply to Alex Bikadorov from comment #6) > ah, center click = middle mouse button. Now I get it. > > >To reproduce, open a text editor, in Krusader, highlight the path in "click > >to edit location", move to the text editor, center mouse click to drop the > >highlighted text > > This works for me (in "Edit" mode of course, in "navigation" mode nothing > can be selected). What is not working? I highlight the path, then center click in another documents, and nothing. I have to go back and . It is a big time waster as the Primary Clipboard works everywhere else and have become a ingrained habit. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 381133] [regression] OpenConnect will not connect
https://bugs.kde.org/show_bug.cgi?id=381133 Thiago Macieirachanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Thiago Macieira --- Confirmed as duplicate. Upgrade to 5.10.1 fixed the issue. *** This bug has been marked as a duplicate of bug 380299 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 380299] [openconnect] not successful after valid credentials are provided
https://bugs.kde.org/show_bug.cgi?id=380299 Thiago Macieirachanged: What|Removed |Added CC||thi...@kde.org --- Comment #10 from Thiago Macieira --- *** Bug 381133 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381143] New: Camera not removed between invocations
https://bugs.kde.org/show_bug.cgi?id=381143 Bug ID: 381143 Summary: Camera not removed between invocations Product: digikam Version: 5.5.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Import Assignee: digikam-de...@kde.org Reporter: twcunningham...@outlook.com Target Milestone: --- A camera removed from digiKam settings reappears when digiKam is restarted. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381142] New: Kwin crashed g when I clicked on "Print" buttom
https://bugs.kde.org/show_bug.cgi?id=381142 Bug ID: 381142 Summary: Kwin crashed g when I clicked on "Print" buttom Product: kwin Version: 5.9.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rodrigodeara...@fedoraproject.org Target Milestone: --- Application: kwin_x11 (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.11.3-202.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: I was sending a file to be printed by Brother HL1102. Printer received the documented just fine, but Kwin got crashed. - Unusual behavior I noticed: Kwin crashed in the moment that I cliked on the "Print" buttom (I was using WPS Writer). The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0dca14e940 (LWP 1955))] Thread 6 (Thread 0x7f0da56cc700 (LWP 7651)): #0 0x7f0dd9551001 in ppoll () at /lib64/libc.so.6 #1 0x7f0dda355971 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f0dda356e86 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f0dda30a68a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f0dda1675e3 in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f0de0c6f4e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #6 0x7f0dda16b9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f0ddc0f373a in start_thread () at /lib64/libpthread.so.0 #8 0x7f0dd955ce7f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f0db5718700 (LWP 2723)): #0 0x7f0dd9551001 in ppoll () at /lib64/libc.so.6 #1 0x7f0dda355971 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f0dda356e86 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f0dda30a68a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f0dda1675e3 in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f0de0c6f4e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #6 0x7f0dda16b9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f0ddc0f373a in start_thread () at /lib64/libpthread.so.0 #8 0x7f0dd955ce7f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f0da4ecb700 (LWP 2192)): #0 0x7f0ddc0f9460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0de1a1a2f4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f0de1a1a339 in () at /lib64/libQt5Script.so.5 #3 0x7f0ddc0f373a in start_thread () at /lib64/libpthread.so.0 #4 0x7f0dd955ce7f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f0db6719700 (LWP 2142)): #0 0x7f0dd9551001 in ppoll () at /lib64/libc.so.6 #1 0x7f0dda355971 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f0dda356e86 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f0dda30a68a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f0dda1675e3 in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f0de0c6f4e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #6 0x7f0dda16b9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f0ddc0f373a in start_thread () at /lib64/libpthread.so.0 #8 0x7f0dd955ce7f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f0dca14a700 (LWP 2011)): #0 0x7f0dd9550f3d in poll () at /lib64/libc.so.6 #1 0x7f0dd0a8a166 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f0dd0a8a27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f0dda3596eb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f0dda30a68a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f0dda1675e3 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f0dde8a1fb9 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f0dda16b9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f0ddc0f373a in start_thread () at /lib64/libpthread.so.0 #9 0x7f0dd955ce7f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f0dca14e940 (LWP 1955)): [KCrash Handler] #6 0x in () #7 0x7f0dda338878 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () at /lib64/libQt5Core.so.5 #8 0x7f0de1a5cd2f in
[kwin] [Bug 381141] New: Crash of KWin when opening Chrome on nVidia Proprietary
https://bugs.kde.org/show_bug.cgi?id=381141 Bug ID: 381141 Summary: Crash of KWin when opening Chrome on nVidia Proprietary Product: kwin Version: 5.10.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mcfle...@vrplumber.com Target Milestone: --- Application: kwin_x11 (5.10.1) Qt Version: 5.7.1 Frameworks Version: 5.35.0 Operating System: Linux 4.10.0-22-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: Clicked a chrome launcher in the plasma panel. Chrome launched normally and loaded tabs, but kwin crashed/restarted. Kubuntu 17.04 up to date with current packages from the backports-landing ppa. Package: kwin-x11 Version: 4:5.10.1-0ubuntu1~ubuntu17.04~ppa1 -- 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 0x7f0451c03900 (LWP 2341))] Thread 6 (Thread 0x7f0417fff700 (LWP 5772)): #0 0x7f044ad0c510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f044ecb5b4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f044a13d495 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f044a13dd8a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f044ecb4c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f044ad066da in start_thread (arg=0x7f0417fff700) at pthread_create.c:456 #6 0x7f045163917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7f04237ff700 (LWP 3429)): #0 0x7f045162d251 in __GI_ppoll (fds=0x7f0418000b38, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f044eed4251 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f044eed5b4a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f044ee8288a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f044ecaffe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0449a73df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f044ecb4c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f044ad066da in start_thread (arg=0x7f04237ff700) at pthread_create.c:456 #8 0x7f045163917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f041682a700 (LWP 2478)): #0 0x7f044ad0c510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f044e0342c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f044e034309 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f044ad066da in start_thread (arg=0x7f041682a700) at pthread_create.c:456 #4 0x7f045163917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7f042889f700 (LWP 2470)): #0 0x7f045162d251 in __GI_ppoll (fds=0x7f041c000ac8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f044eed4251 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f044eed5b4a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f044ee8288a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f044ecaffe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0449a73df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f044ecb4c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f044ad066da in start_thread (arg=0x7f042889f700) at pthread_create.c:456 #8 0x7f045163917f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7f043abda700 (LWP 2349)): #0 0x7f045162d18d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f04462ce576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f04462ce68c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f044eed8f2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f044ee8288a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f044ecaffe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0448c425c5 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f044ecb4c98 in () at
[knetwalk] [Bug 356489] Black field
https://bugs.kde.org/show_bug.cgi?id=356489 --- Comment #10 from Texstar--- Qt5 5.9.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 380797] Cannot set MTU of wired connection
https://bugs.kde.org/show_bug.cgi?id=380797 --- Comment #5 from Neil Rickert--- Tumbleweed upgrade plasma-nm to version 5.10.1 today. So I decided to retest. The problem is still there. But I paid closer attention to what is happening. When I start editing the Wired connect settings, I see "Okay", "Apply" and "Cancel" buttons near the bottom of the screen. But the "Apply" is grayed out, so cannot be used. When I change something (I tried changing the MTU from 1472 to 1471), the "Apply" remains greyed out. So the applet is not recognizing that there are changes that need to be saved. By contrast, if I edit a "WiFi" connection settings, then the change of MTU from 1472 to 1471 (and then back to 1472) makes the Apply button active (not grayed out). -- You are receiving this mail because: You are watching all bug changes.
[knetwalk] [Bug 356489] Black field
https://bugs.kde.org/show_bug.cgi?id=356489 --- Comment #9 from Albert Astals Cid--- Which qt? -- You are receiving this mail because: You are watching all bug changes.
[knetwalk] [Bug 356489] Black field
https://bugs.kde.org/show_bug.cgi?id=356489 --- Comment #8 from Texstar--- I'm not sure if this is correct but I fixed it by patching in qApp->setAttribute(Qt::AA_DontCreateNativeWidgetSiblings, true); into the mainwindow.cpp -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 381140] New: Marble 2.2.01 won't open on 64 bit win 7 system.
https://bugs.kde.org/show_bug.cgi?id=381140 Bug ID: 381140 Summary: Marble 2.2.01 won't open on 64 bit win 7 system. Product: marble Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: haigh44...@gmail.com Target Milestone: --- version 2.2.01 windows 64bit - when finished installing message "can't start because MSVCP120.dll is missing from computer". Ran c++ update from ms, restarted, same message. 32 bit version installs and opens. (windows search found the.dll found in 5 different places. (Program opens and runs just fine on 2 old slower Ubuntu laptops.) Got all install files from KDE website. -- You are receiving this mail because: You are watching all bug changes.
[knetwalk] [Bug 356489] Black field
https://bugs.kde.org/show_bug.cgi?id=356489 --- Comment #7 from Texstar--- It repeats... QQuickWidget cannot be used as a native child widget. Consider setting Qt::AA_DontCreateNativeWidgetSiblings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375976] appmenu not shown for gtk apps
https://bugs.kde.org/show_bug.cgi?id=375976 JonnyRobbiechanged: What|Removed |Added CC||marc...@seznam.cz --- Comment #6 from JonnyRobbie --- I understand that it may not be easy to move gtk appmenu to the global widget. However I don't understand the necessity to remove it altogether. Let Qt apps have its globalmenu and leave incapable gtk aps with its local menu. What I don't understand is why do the gtk apps need to lose their menu altogether? Clearly kwin (or whichever component is responsible) is capable and even acting on removing those menus from gtk apps, why not just leave it alone then? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 381010] plasma-pa applet not showing up in systray
https://bugs.kde.org/show_bug.cgi?id=381010 Texstarchanged: What|Removed |Added CC||texs...@gmail.com --- Comment #3 from Texstar --- My plamsa pa applet only starts in the system tray on every other login and I'm not using wayland. Login in and it is there Login again and it is gone Login again and damn it is back again! -- You are receiving this mail because: You are watching all bug changes.
[knetwalk] [Bug 356489] Black field
https://bugs.kde.org/show_bug.cgi?id=356489 Albert Astals Cidchanged: What|Removed |Added CC||aa...@kde.org --- Comment #6 from Albert Astals Cid --- most likely packaging bug. Any debug output on the command line if run from a terminal? Attach strace output? -- You are receiving this mail because: You are watching all bug changes.
[knetwalk] [Bug 356489] Black field
https://bugs.kde.org/show_bug.cgi?id=356489 Texstarchanged: What|Removed |Added CC||texs...@gmail.com --- Comment #5 from Texstar --- The black screen is back in 17.04.2 Qt5 5.9.0 Desktop 5.10.1 Frameworks 5.35.0 Applications 17.04.2 export KF5=/usr export QTDIR=$KF5/lib64/qt5 export PATH=$KF5/bin:$QTDIR/bin:$KF5/share/kf5:/usr/libexec:$PATH export QT_PLUGIN_PATH=$KF5/lib64/qt5/plugins export QML2_IMPORT_PATH=$KF5/lib64/qt5/qml export QML_IMPORT_PATH=$QML2_IMPORT_PATH -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 380900] Notifications won't play sounds
https://bugs.kde.org/show_bug.cgi?id=380900 --- Comment #6 from Albert Astals Cid--- Does installing phonon4qt5-backend-gstreamer help? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #45 from Thomas Schmitt--- Hi, although runs 2 and 3 look good, they show different speed settings and effective speeds. Run 2 gets set to 4x, runs a long time at 2x and then suddenly goes to 4x. Run 3 gets set to 4x but runs at 2x all the time. Are these media from different brands or with different speed printed on their labels ? Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368175] Error creating new partition with KDE auto-mount enabled
https://bugs.kde.org/show_bug.cgi?id=368175 Andrius Štikonaschanged: What|Removed |Added Version Fixed In|3.1.1 |kpmcore 3.1.1, ||partitionmanager 3.1.0 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368175] Error creating new partition with KDE auto-mount enabled
https://bugs.kde.org/show_bug.cgi?id=368175 Andrius Štikonaschanged: What|Removed |Added Status|REOPENED|RESOLVED Latest Commit|https://commits.kde.org/kpm |https://commits.kde.org/par |core/63b5c8c34cf257d29fb8e6 |titionmanager/4e78cd9ff1d99 |7b41da7b606b32aec0 |0fbe1db3f54469aa567d9f908fe Resolution|--- |FIXED --- Comment #13 from Andrius Štikonas --- Git commit 4e78cd9ff1d990fbe1db3f54469aa567d9f908fe by Andrius Štikonas. Committed on 12/06/2017 at 22:06. Pushed by stikonas into branch 'master'. Pass DBUS_SESSION_BUS_ADDRESS environmental variable. This is necessary for disabling Plasma automounter on Wayland. M +2-1src/util/guihelpers.cpp https://commits.kde.org/partitionmanager/4e78cd9ff1d990fbe1db3f54469aa567d9f908fe -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379635] popmenu at desktop doesn't disappear when lost focus.
https://bugs.kde.org/show_bug.cgi?id=379635 Elvis Angelacciochanged: What|Removed |Added CC||tro...@free.fr --- Comment #1 from Elvis Angelaccio --- *** Bug 381125 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381125] [Wayland] After a right click on the desktop, left click does not close the context popup
https://bugs.kde.org/show_bug.cgi?id=381125 Elvis Angelacciochanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||elvis.angelac...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Elvis Angelaccio --- *** This bug has been marked as a duplicate of bug 379635 *** -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #44 from Cristian Aravena Romero--- Created attachment 106068 --> https://bugs.kde.org/attachment.cgi?id=106068=edit k3b_17.04.2_test_3-6.png -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #43 from Cristian Aravena Romero--- Created attachment 106067 --> https://bugs.kde.org/attachment.cgi?id=106067=edit k3b_17.04.2_test_3-6.log 3/6 -> Correct recording :-) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 380406] EncFS package Bad version - ENCFS
https://bugs.kde.org/show_bug.cgi?id=380406 Jonathan Riddellchanged: What|Removed |Added Resolution|--- |MOVED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Jonathan Riddell --- moved to todo https://phabricator.kde.org/T6327 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380825] [wayland] panels dont show single shadow
https://bugs.kde.org/show_bug.cgi?id=380825 David Edmundsonchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/e9e285618ef11e483b1da076f ||85b6fd81dd46056 --- Comment #1 from David Edmundson --- Git commit e9e285618ef11e483b1da076f85b6fd81dd46056 by David Edmundson. Committed on 09/06/2017 at 15:43. Pushed by davidedmundson into branch 'xdgv6'. Make shadows work for windows 100% width or height Summary: Clients provide shadows as 9 images, which then get split into relevant quads. To work out the full width we need the size of an item on the left, the middle and the right. Some elements can be legitiamtely missing so to work out the width of the left edge we need to consider all 3 of topleft,left,bottomleft. Currently we checked both corners in case one was missing, but it's legitimate for both to be missing if the shadow stretches the whole way. Test Plan: Shadow on panel, rest looks the same Reviewers: #plasma Subscribers: plasma-devel, kwin, #kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D6164 M +8-8scene_opengl.cpp M +7-0utils.h https://commits.kde.org/kwin/e9e285618ef11e483b1da076f85b6fd81dd46056 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #42 from Cristian Aravena Romero--- Created attachment 106066 --> https://bugs.kde.org/attachment.cgi?id=106066=edit k3b_17.04.2_test_2-6.png -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #41 from Cristian Aravena Romero--- Created attachment 106065 --> https://bugs.kde.org/attachment.cgi?id=106065=edit k3b_17.04.2_test_2-6.log 2/6 -> Correct recording :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381129] Dragging files over grouped tasks is broken
https://bugs.kde.org/show_bug.cgi?id=381129 Eike Heinchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Eike Hein --- Confirmed, working on this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381139] "Switch desktop on edge" broken
https://bugs.kde.org/show_bug.cgi?id=381139 Eike Heinchanged: What|Removed |Added Component|Pager |general Target Milestone|1.0 |--- Product|plasmashell |kwin Assignee|h...@kde.org|kwin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381139] New: "Switch desktop on edge" broken
https://bugs.kde.org/show_bug.cgi?id=381139 Bug ID: 381139 Summary: "Switch desktop on edge" broken Product: plasmashell Version: 5.10.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Pager Assignee: h...@kde.org Reporter: daniel-ed...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 Since the last update the "Switch desktop on edge" == "Only When Moving Windows" behaves the same as "Disabled". (Btw. why every word starts with a capital letter?). Is this category correct? Sorry, if not. Other settings: * Maximize windows by dragging them to the top of the screen == False * Tile windows by dragging (...) == True * Number of virtual desktops == 2 Note: * to be precise I'm running Manjaro and not Arch -- You are receiving this mail because: You are watching all bug changes.
[kuser] [Bug 381138] New: KUser is still KDE SC 4 based
https://bugs.kde.org/show_bug.cgi?id=381138 Bug ID: 381138 Summary: KUser is still KDE SC 4 based Product: kuser Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gyu...@freemail.hu Reporter: shaloksha...@protonmail.ch Target Milestone: --- Port KUser to kf5 -- You are receiving this mail because: You are watching all bug changes.
[kgeography] [Bug 381078] Scotlands capital edinburgh missing
https://bugs.kde.org/show_bug.cgi?id=381078 --- Comment #1 from Laurent G.--- I used such a much as below, to craft the Great Britain counties map, http://lauranger.free.fr/kgeomapp/?divi=great-britain_counties=Great%20Britain%C2%A0(counties) : http://www.britain-visitor.com/britain-travel-guide/current-counties-uk where the Edinburgh area seems to belong to Midlothian County (n°21). In contrast to Scotland areas and regions maps, where Edingburgh appears on its own right, as we can see on : http://lauranger.free.fr/kgeomapp/?divi=scotland_areas=Scotland%C2%A0(areas) and http://lauranger.free.fr/kgeomapp/?divi=scotland_regions=Scotland%C2%A0(regions) "On par with placing Washington DC in Washington State", you say. Hum, a 22.5km problem to a 4500km mismatch. Would you write in french, I'd locate you not far from Marseille (cliché inside) ;-) -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 365882] Partition Manager shouldn't allow second instance to run
https://bugs.kde.org/show_bug.cgi?id=365882 Dr. Chapatinchanged: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380524] Downloaded window decoration are broken with Nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=380524 Christoph Feckchanged: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #6 from Christoph Feck --- Fix from 5.10 branch was merged to master again. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 381133] [regression] OpenConnect will not connect
https://bugs.kde.org/show_bug.cgi?id=381133 Thiago Macieirachanged: What|Removed |Added Version|5.10.1 |5.10.0 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar
https://bugs.kde.org/show_bug.cgi?id=373824 --- Comment #16 from Alex6--- Only treeview in Dolphin. No bookmarks (web/filesystem) in Dolphin. No web in Dolphin. Now, no root action in Dolphin. 5 years work to destroy konqueror, to make something worse, 5 years wasted work? Thunar is not KDE! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 381133] [regression] OpenConnect will not connect
https://bugs.kde.org/show_bug.cgi?id=381133 --- Comment #2 from Thiago Macieira--- Likely duplicate of bug 380299 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381113] Crash upon changing wallpaper scaling mode
https://bugs.kde.org/show_bug.cgi?id=381113 Dr. Chapatinchanged: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 381137] New: Akregator crash on plasma login
https://bugs.kde.org/show_bug.cgi?id=381137 Bug ID: 381137 Summary: Akregator crash on plasma login Product: akregator Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mtijink.b...@gmail.com Target Milestone: --- Application: akregator (5.5.2) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.11.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Akregator crashes immediately when starting plasma. Starting it afterwards works fine, and closing and restarting akregator manually also works. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f200498e900 (LWP 2025))] Thread 23 (Thread 0x7f1f531b4700 (LWP )): #0 0x7f1ffacab39d in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1fed141ac4 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7f1fed141b09 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7f1ffaca5297 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f200088c25f in clone () from /usr/lib/libc.so.6 Thread 22 (Thread 0x7f1f53fff700 (LWP 2211)): #0 0x7f1ffacab39d in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1feff221c5 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7f1feff226a7 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7f1feff23441 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7f1feff1fb0b in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7f1ffaca5297 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f200088c25f in clone () from /usr/lib/libc.so.6 Thread 21 (Thread 0x7f1f82ffd700 (LWP 2146)): #0 0x7f20008822bd in poll () from /usr/lib/libc.so.6 #1 0x7f1ff8a4dbf9 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f1ff8a4dd0c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f20011aae9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f200115121a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f2000f7340a in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f2000f77cbd in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f1ffaca5297 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f200088c25f in clone () from /usr/lib/libc.so.6 Thread 20 (Thread 0x7f1f837fe700 (LWP 2115)): #0 0x7f200089904b in __lll_lock_wait_private () from /usr/lib/libc.so.6 #1 0x7f200089ad04 in __fprintf_chk () from /usr/lib/libc.so.6 #2 0x7f1fe4af2b3e in ?? () from /usr/lib/libevent-2.0.so.5 #3 0x7f1fe4af2d34 in event_warn () from /usr/lib/libevent-2.0.so.5 #4 0x7f1fe4af74b8 in ?? () from /usr/lib/libevent-2.0.so.5 #5 0x7f1fe4ae145a in event_base_loop () from /usr/lib/libevent-2.0.so.5 #6 0x7f1fefef2fe9 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #7 0x7f1fefeef2b8 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #8 0x7f1feff0be9b in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #9 0x7f1feff23a06 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #10 0x7f1feff1fb0b in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #11 0x7f1ffaca5297 in start_thread () from /usr/lib/libpthread.so.0 #12 0x7f200088c25f in clone () from /usr/lib/libc.so.6 Thread 19 (Thread 0x7f1f83fff700 (LWP 2106)): #0 0x7f1ffacab39d in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1feff17c59 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7f1feff17c87 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7f1fefef29eb in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7f1fefeef2b8 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7f1feff0be9b in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #6 0x7f1feff23a06 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #7 0x7f1feff1fb0b in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #8 0x7f1ffaca5297 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f200088c25f in clone () from /usr/lib/libc.so.6 Thread 18 (Thread 0x7f1f98ff9700 (LWP 2104)): #0 0x7f200087e02d in read () from /usr/lib/libc.so.6 #1 0x7f1fdf2aff51 in pa_read () from /usr/lib/pulseaudio/libpulsecommon-10.0.so #2 0x7f1fe74f830e in pa_mainloop_prepare () from /usr/lib/libpulse.so.0 #3 0x7f1fe74f8d80 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0 #4 0x7f1fe74f8e40 in pa_mainloop_run () from /usr/lib/libpulse.so.0 #5 0x7f1fe7506e29 in ?? () from /usr/lib/libpulse.so.0 #6
[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 --- Comment #1 from andreas.sturmlech...@gmail.com --- This is something I noticed as well upgrading from Frameworks 5.34 to 5.35. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381136] No progress status on systray when copying files
https://bugs.kde.org/show_bug.cgi?id=381136 --- Comment #1 from Kai Uwe Broulik--- Can't reproduce. What plasmashell and KDE Frameworks version is this? Can you perhaps make a Screencast? Do note that progress is only shown when the job takes longer than a second or two. Also make sure application progress is enabled in notification applet settings. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 344874] username/password not being sent in header
https://bugs.kde.org/show_bug.cgi?id=344874 Richard Boschanged: What|Removed |Added CC||richard@xs4all.nl --- Comment #14 from Richard Bos --- Is this big https://github.com/nextcloud/server/issues/5326 related? I opened the bug report at nextcloud, but they refer to KDE. The message I get in logfiles is: No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured in logfile -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381136] New: No progress status on systray when copying files
https://bugs.kde.org/show_bug.cgi?id=381136 Bug ID: 381136 Summary: No progress status on systray when copying files Product: plasmashell Version: master Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: alonsomm2...@hotmail.com CC: mklape...@kde.org Target Milestone: 1.0 When you copy a folder or files from one to place to other it does not show copy progress status under Systray notifications! Copying works fine but is very important to see progress! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 359470] Older Date
https://bugs.kde.org/show_bug.cgi?id=359470 NSLWchanged: What|Removed |Added CC||lukasz.wojnilow...@gmail.co ||m Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from NSLW --- Marking invalid per comment #1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381135] Weather widget configured with yr.no crashes Plasmashell
https://bugs.kde.org/show_bug.cgi?id=381135 Alex10336changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Alex10336 --- *add duplicate #id manually* *** This bug has been marked as a duplicate of bug 375189 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375189] plsama crash notification
https://bugs.kde.org/show_bug.cgi?id=375189 Alex10336changed: What|Removed |Added CC||ap10...@gmail.com --- Comment #9 from Alex10336 --- *** Bug 381135 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381135] New: Weather widget configured with yr.no crashes Plasmashell
https://bugs.kde.org/show_bug.cgi?id=381135 Bug ID: 381135 Summary: Weather widget configured with yr.no crashes Plasmashell Product: plasmashell Version: 5.10.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ap10...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.1) Qt Version: 5.7.1 Frameworks Version: 5.35.0 Operating System: Linux 4.4.0-79-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - What I was doing when the application crashed: 1. Click on Widget icon. 2. Crash \o/ - Since kde 5.10, still crash on 5.10.1 just updated (framework 5.35) on Kde Neon User Édition. N.B. : Can not select has « duplicate of #375189 » from bugs wizard The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4f87b738c0 (LWP 1459))] Thread 10 (Thread 0x7f4eb6c58700 (LWP 1658)): #0 0x7f4f824b7b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4f7dc4d38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4f7dc4d49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4f82dd775b in QEventDispatcherGlib::processEvents (this=0x7f4eb8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f4f82d820ba in QEventLoop::exec (this=this@entry=0x7f4eb6c57cc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f4f82bb1f64 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f4ec11eb587 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f4f82bb6b48 in QThreadPrivate::start (arg=0x5eb3bf0) at thread/qthread_unix.cpp:368 #8 0x7f4f81a5c6ba in start_thread (arg=0x7f4eb6c58700) at pthread_create.c:333 #9 0x7f4f824c382d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f4ec9081700 (LWP 1648)): #0 0x7f4f824b7b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4f7dc4d38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4f7dc4d49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4f82dd775b in QEventDispatcherGlib::processEvents (this=0x7f4ebc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f4f82d820ba in QEventLoop::exec (this=this@entry=0x7f4ec9080d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f4f82bb1f64 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f4f82bb6b48 in QThreadPrivate::start (arg=0x269b690) at thread/qthread_unix.cpp:368 #7 0x7f4f81a5c6ba in start_thread (arg=0x7f4ec9081700) at pthread_create.c:333 #8 0x7f4f824c382d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f4ec98c2700 (LWP 1647)): #0 0x7f4f82bae329 in std::__atomic_base::compare_exchange_strong (__m2=, __m1=std::memory_order_release, __p2=0x0, __p1=@0x7f4ec98c1a88: 0x1, this=0x275d010) at /usr/include/c++/5/bits/atomic_base.h:752 #1 std::atomic ::compare_exchange_strong (__m=std::memory_order_release, __p2=0x0, __p1=@0x7f4ec98c1a88: 0x1, this=0x275d010) at /usr/include/c++/5/atomic:475 #2 QAtomicOps ::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=0x1, _q_value=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:299 #3 QBasicAtomicPointer::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=, this=0x275d010) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:261 #4 QBasicMutex::fastTryUnlock (current=, this=0x275d010) at thread/qmutex.h:92 #5 QMutex::unlock (this=this@entry=0x275d010) at thread/qmutex.cpp:277 #6 0x7f4f82dd6ec1 in QMutexLocker::unlock (this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:147 #7 QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:141 #8 QThreadData::canWaitLocked (this=0x275cfe0) at ../../include/QtCore/5.7.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:253 #9 postEventSourcePrepare (s=0x7f4ec40012d0, timeout=0x7f4ec98c1b14) at kernel/qeventdispatcher_glib.cpp:259 #10 0x7f4f7dc4c91d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f4f7dc4d2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f4f7dc4d49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f4f82dd775b in QEventDispatcherGlib::processEvents (this=0x7f4ec40008c0,
[plasmashell] [Bug 378700] There is gap on the right of every invoked tray icon
https://bugs.kde.org/show_bug.cgi?id=378700 --- Comment #9 from f...@hezll.com --- Don't know what causes this behavior, maybe non-standard fonts size (I use 9 noto font on desktop and 11 noto font on notebook, cause default 10 is very big and small respectively), maybe gfx drivers as mentioned before, but now it's gone and I think bug can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378700] There is gap on the right of every invoked tray icon
https://bugs.kde.org/show_bug.cgi?id=378700 --- Comment #8 from f...@hezll.com --- Somehow it has been disappeared after update to .35 frameworks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378700] There is gap on the right of every invoked tray icon
https://bugs.kde.org/show_bug.cgi?id=378700 f...@hezll.com changed: What|Removed |Added CC||f...@hezll.com --- Comment #7 from f...@hezll.com --- Created attachment 106064 --> https://bugs.kde.org/attachment.cgi?id=106064=edit ok now -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381012] bug in popup palette color
https://bugs.kde.org/show_bug.cgi?id=381012 --- Comment #6 from Boudewijn Rempt--- Okay... Would it be possible to share the .kra file so we can figure out what's up? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381012] bug in popup palette color
https://bugs.kde.org/show_bug.cgi?id=381012 --- Comment #5 from Tomasz--- URGENT This bug happens only in my ONE pictue! When I open other popuppalette work fine. Even if I open two works in one Krita, problem occurs only in this ONE. There is something wrong with picture not with Krita. Please close bug report. For me problem is solved. Tomasz 2017-06-09 13:43 GMT+02:00 Boudewijn Rempt : > https://bugs.kde.org/show_bug.cgi?id=381012 > > Boudewijn Rempt changed: > >What|Removed |Added > > > CC||b...@valdyas.org > Resolution|--- |WAITINGFORINFO > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #1 from Boudewijn Rempt --- > Check whether your kritarc contains a line > > popuppalette/usevisualcolorselector=true > > Because this sounds like you've got the new color selector, not the default > one. Also, please attach a screenshot to the bug so I can verify which > color > selector is enabled. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #40 from Thomas Schmitt--- Hi, > https://phabricator.kde.org/T6316 says "You Shall Not Pass: Restricted Maniphest Task You do not have permission to view this object. Users with the "Can View" capability: This object has a custom policy controlling who can take this action. The owner of a task can always view and edit it." I take ophense and rephuse to use such newfangled contraptions. What's the problem with FreeBSD ? It is supposed to mount UDF. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 363430] Plasma crashes on right click on the menu
https://bugs.kde.org/show_bug.cgi?id=363430 --- Comment #10 from Martin Pagh Goodwin--- It is however not the first time it has happened, so for next time I should like to know what logs/debug info would be helpful. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 363430] Plasma crashes on right click on the menu
https://bugs.kde.org/show_bug.cgi?id=363430 --- Comment #9 from Martin Pagh Goodwin--- Thanx I resolved the issue by doing a complete backup of her home folder, deleting it, and then logging in, forcing a creation of a new skeleton, then I copied in local_mail and kwallet configs into .local/share/ and now everything works. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar
https://bugs.kde.org/show_bug.cgi?id=373824 --- Comment #15 from David Rosenstrauch--- I was using it to display the folder tree in Konqueror's left pane. However, since I read here that the sidebar wasn't going to be supported any more, I've started using Thunar. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 369301] Muon doesn't find packages after installing a package
https://bugs.kde.org/show_bug.cgi?id=369301 James Cainchanged: What|Removed |Added CC||dequ...@mykolab.com --- Comment #8 from James Cain --- The same behavior exists in Neon 5.10, although I don't think that fact alone warrants another bug report. Neon is pretty much useless at the moment, and should be pulled from the repos in it's current state IMHO, as attempting to find a package is pretty much impossible, unless someone knows the package name (and in that case one could easily drop to a cli and install it), and is willing to scroll through every package in the archives to find it. As mentioned above, waiting for the index to complete and closing > re-opening the app seems to work. But do note that each time a new search is queried, an application restart needs to be completed. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 381134] New: The equalizer is not working
https://bugs.kde.org/show_bug.cgi?id=381134 Bug ID: 381134 Summary: The equalizer is not working Product: amarok Version: 2.8.0 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools/Equalizer Assignee: amarok-bugs-d...@kde.org Reporter: nicuju...@lucyu.com Target Milestone: 2.9 Created attachment 106062 --> https://bugs.kde.org/attachment.cgi?id=106062=edit Here is a screen shot which shows that the equalizer is not working In the application Amarock the Equalizer is not working with any songs even its in my home/music directory. Need to fix this minor issue . No modes of equalizer is working. I am using Mint(ubuntu) 18.1 on i3 with 8Gigs of ram -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 381133] [regression] OpenConnect will not connect
https://bugs.kde.org/show_bug.cgi?id=381133 Thiago Macieirachanged: What|Removed |Added Summary|[regression] OpenCpnnect|[regression] OpenConnect |will not connect|will not connect --- Comment #1 from Thiago Macieira --- The problem might not be in plasma-nm5, but elsewhere. After copying all the files from 5.9.5 over and restarting kded5 and plasmashell, I still can't connect. Note also that the login dialog looks like the one from 5.10, not the layout from 5.9.5. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 381123] Kdevelop crashes on parsing php project
https://bugs.kde.org/show_bug.cgi?id=381123 Sven Brauchchanged: What|Removed |Added CC||m...@svenbrauch.de Component|general |Language Support: PHP -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 381133] New: [regression] OpenCpnnect will not connect
https://bugs.kde.org/show_bug.cgi?id=381133 Bug ID: 381133 Summary: [regression] OpenCpnnect will not connect Product: plasma-nm Version: 5.10.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: thi...@kde.org Target Milestone: --- Regression from 5.9.5, where this worked flawlessly. When trying to connect to OpenConnect with the applet, the dialog shows, I type my password and hit connect, but the dialog does not go away. The log shows everything that it was expected to show, but the connection never happens. The connections list shows a spinning wheel indicating that the connection is coming up, but it never finishes and never seems to time out either. NM 1.6.2, NM-openconnect 1.2.4, openconnect 7.08 (all the same version as 5.9.5 that did work). Other info: * /usr/lib/nm-openconnect-service does start at the moment that you start the connection. * kded5 logs: QFormLayout::takeAt: Invalid index 0 * log window logged: POST https://vpn.example.com/ Attempting to connect to server 192.0.2.1:443 Connected to 192.0.2.1:443 Using certificate file /home/tjmaciei/.cert/certificate.p12 Using client certificate 'Macieira\, Thiago' Adding supporting CA 'Xxxx Intranet Basic Issuing CA 1A' Adding supporting CA 'Xxxx Intranet Basic Policy CA' SSL negotiation with vpn.example.com Connected to HTTPS on vpn.example.com Got HTTP response: HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Cache-Control: no-cache Pragma: no-cache Connection: Keep-Alive Date: Mon, 12 Jun 2017 16:29:04 GMT X-Frame-Options: SAMEORIGIN X-Aggregate-Auth: 1 HTTP body chunked (-2) XML POST enabled POST https://vpn.example.com/ SSL negotiation with vpn.example.com Connected to HTTPS on vpn.example.com Got HTTP response: HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Cache-Control: no-cache Pragma: no-cache Connection: Keep-Alive Date: Mon, 12 Jun 2017 16:29:43 GMT X-Frame-Options: SAMEORIGIN X-Aggregate-Auth: 1 HTTP body chunked (-2) * NM logged: [1497284943.7218] audit: op="connection-activate" uuid="37723676-34a4-419f-ad43-8b96be2e9caa" name="Xxx AnyConnect VPN" pid=61979 uid=1000 result="success" [1497284943.7284] vpn-connection[0x55bf06ab67a0,37723676-34a4-419f-ad43-8b96be2e9caa,"Xxx AnyConnect VPN",0]: Started the VPN service, PID 65841 [1497284943.7419] vpn-connection[0x55bf06ab67a0,37723676-34a4-419f-ad43-8b96be2e9caa,"Xxx AnyConnect VPN",0]: Saw the service appear; activating connection [1497284943.7757] keyfile: update /etc/NetworkManager/system-connections/Xxx AnyConnect VPN (37723676-34a4-419f-ad43-8b96be2e9caa,"Xxx AnyConnect VPN") The last time it connected successfully with 5.9.5, the log was: [1497022125.0443] audit: op="connection-activate" uuid="37723676-34a4-419f-ad43-8b96be2e9caa" name="Xxx AnyConnect VPN" pid=2337 uid=1000 result="success" [1497022125.0760] vpn-connection[0x26c2380,37723676-34a4-419f-ad43-8b96be2e9caa,"Xxx AnyConnect VPN",0]: Started the VPN service, PID 71671 [1497022125.1314] vpn-connection[0x26c2380,37723676-34a4-419f-ad43-8b96be2e9caa,"Xxx AnyConnect VPN",0]: Saw the service appear; activating connection [1497022125.1889] keyfile: update /etc/NetworkManager/system-connections/Xxx AnyConnect VPN (37723676-34a4-419f-ad43-8b96be2e9caa,"Xxx AnyConnect VPN") [1497022128.9310] keyfile: update /etc/NetworkManager/system-connections/Xxx AnyConnect VPN (37723676-34a4-419f-ad43-8b96be2e9caa,"Xxx AnyConnect VPN") [1497022128.9676] keyfile: update /etc/NetworkManager/system-connections/Xxx AnyConnect VPN (37723676-34a4-419f-ad43-8b96be2e9caa,"Xxx AnyConnect VPN") [1497022128.9699] audit: op="connection-update" uuid="37723676-34a4-419f-ad43-8b96be2e9caa" name="Xxx AnyConnect VPN" args="connection.timestamp,vpn.secrets" pid=123502 uid=1000 result="success" [1497022128.9703] vpn-connection[0x26c2380,37723676-34a4-419f-ad43-8b96be2e9caa,"Xxx AnyConnect VPN",0]: VPN plugin: state changed: starting (3) openconnect[71678]: Connected to 192.0.2.1:443 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381132] New: Crash when closes libreoffice calc document
https://bugs.kde.org/show_bug.cgi?id=381132 Bug ID: 381132 Summary: Crash when closes libreoffice calc document Product: plasmashell Version: 5.10.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: m...@schimmel.com.ar CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.0) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.11.3-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: I am using a libreoffice spreadsheet, it's not modified since opened. When I closed it Plasmashell crashes. 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 0x7f24395b98c0 (LWP 3025))] Thread 27 (Thread 0x7ee2b076e700 (LWP 6514)): #0 0x7f242da91060 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f242da91c1b in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f242da91dfc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f24335a7afb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f243354ed5a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2433371afa in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f24333767cc in () at /usr/lib64/libQt5Core.so.5 #7 0x7f243253e4e7 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2432c84a2f in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7ee2adb78700 (LWP 4989)): #0 0x7f2432c7b08d in poll () at /lib64/libc.so.6 #1 0x7f24298a5881 in () at /usr/lib64/libpulse.so.0 #2 0x7f2429897240 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f24298978d0 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f2429897960 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f24298a57c9 in () at /usr/lib64/libpulse.so.0 #6 0x7f24288f60b8 in () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #7 0x7f243253e4e7 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2432c84a2f in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f230b7fe700 (LWP 4988)): #0 0x7f2432c7b08d in poll () at /lib64/libc.so.6 #1 0x7f242da91ce9 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f242da91dfc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f24335a7afb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f243354ed5a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2433371afa in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2436476165 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f24333767cc in () at /usr/lib64/libQt5Core.so.5 #8 0x7f243253e4e7 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2432c84a2f in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f23281eb700 (LWP 4966)): #0 0x7f24325445ed in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f236f29878e in () at /usr/lib64/libvlc.so.6 #2 0x7f243253e4e7 in start_thread () at /lib64/libpthread.so.0 #3 0x7f2432c84a2f in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f230bfff700 (LWP 4254)): #0 0x7f24325445ed in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2433377b4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f237caf5f75 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f237caf9ee8 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f237caf513d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f237caf9f42 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f237caf513d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f237caf9f42 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f237caf513d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f237caf9f42 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f237caf513d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f237caf9f42 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f237caf513d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f237caf9f42 in () at /usr/lib64/libKF5ThreadWeaver.so.5
[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar
https://bugs.kde.org/show_bug.cgi?id=373824 --- Comment #14 from avlas--- (In reply to David Faure from comment #13) > So it seems there are still konqueror users and they are missing the sidebar > ;-) > > But before anyone recreates anything... which sidebar modules exactly are > you missing, and do they *have* to be in a sidebar? > > E.g. the history module could be a separate window, so that more width if > available to read titles and URLs. > > On the other hand, the folder tree is only useful as a sidebar, but that's > pure file management, for which I still think/hope that Dolphin is better > suited (and if not, I encourage you to report Dolphin bugs/wishes). > Unless... could it be that the main use of "webdav and web browser and file > browser in one window" is web development? As far as I recall (after all these months my memory fades out...), I used it for these three things: 1- filter webpages from history 2- filter webpages from bookmarks - browse files I cannot recall any other options that were available in the sidebar, my bad :/ Regarding 1 and 2, please note that although extra windows give more room to see things, extra windows are also more annoying (at least for some of us), so it's not bad to activate them via ctrl+h or whatever when we really want/need this, but at least for me, the sidebar always helped me to find things in the best way. Regarding 3, I, for one, use dolphin as my default file browser and I'm very happy with it, but sometimes while browsing you want to access a file or download to a path, and doing so via the sidebar instead of opening an extra application, may be good. This is also a good option when Konqueror is used to visualize e.g. svg's (my default way to see these files), so you can browse via the sidebar and open them in the same window. I am sure other people can contribute to this with more examples... -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 381114] Can't control brightness
https://bugs.kde.org/show_bug.cgi?id=381114 kilian.cavalotti.w...@gmail.com changed: What|Removed |Added CC||kilian.cavalotti.work@gmail ||.com --- Comment #5 from kilian.cavalotti.w...@gmail.com --- Just want to confirm seeing the same issue here. All backlight controls have disappeared from the "Power Management" section of System Settings. It has also been reported here: https://forum.manjaro.org/t/kde-can-not-control-screen-backlight-anymore/25654 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 363430] Plasma crashes on right click on the menu
https://bugs.kde.org/show_bug.cgi?id=363430 --- Comment #8 from Ivan Čukić--- @Martin It seems that sqlite sometimes (rarely) has issues to open its own files - due to a database or filesystem corruption - I haven't been able to reproduce this, so this is mostly guesswork. Removing the .local/share/kactivitymanagerd and restarting the system should fix it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381089] An option for plasmashell to decide that activity switch will show when using "Walk Though Activities" shortcut
https://bugs.kde.org/show_bug.cgi?id=381089 Ivan Čukićchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Ivan Čukić --- There is a command kactivities-cli (you'll need to find in which package ubuntu keeps it). It has --next-activity and --previous-activity commands - you can create custom keyboard shortcuts for them. I don't plan to support this as a GUI option. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 330536] Bluetooth device link
https://bugs.kde.org/show_bug.cgi?id=330536 --- Comment #21 from Saikrishna--- (In reply to kmi from comment #20) > (In reply to Saikrishna from comment #15) > > For the record, remote filesystem browsing will not work over the bluetooth > > backend because it uses SSHFS, which uses an IP network. It should be > > possible to implement FUSE in kdeconnect and transfer file information and > > payloads through kdeconnect itself. > > I don't know if that's possible under Android but just for reference: > Apple’s Continuity negotiates things via Bluetooth LE but for actual file > transfers etc. is opens an Ad-hoc WiFi network. I actually was able to implement a read-only FUSE filesystem (writing will take some work), but it's very buggy/rough (in particular, you may need to do manual cleanup after exiting KDE Connect on the desktop side). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368175] Error creating new partition with KDE auto-mount enabled
https://bugs.kde.org/show_bug.cgi?id=368175 Andrius Štikonaschanged: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #12 from Andrius Štikonas --- I'll reopen this for now as this is only fixed on X11 and does not work on Wayland. Similar problem is encountered in bug #365882. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 365882] Partition Manager shouldn't allow second instance to run
https://bugs.kde.org/show_bug.cgi?id=365882 --- Comment #3 from Andrius Štikonas--- (In reply to Andrius Štikonas from comment #2) > Unfortunately this introduces a regression in Wayland support. I'll revert > the commit for now. I investigated this regression a bit. It seems that under wayland we are not able to make a connection to a current user's dbus daemon. It looks like even setuid does not help in this case (and similar case in kpmcore where we disable plasma automounter, that code also works only on X11). -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #39 from Leslie Zhai--- Hi Thomas, Thanks for your advice! and it needs consider about FreeBSD now :) https://phabricator.kde.org/T6316 Regards, Leslie Zhai -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 380280] Crash when using webengine type in plasma
https://bugs.kde.org/show_bug.cgi?id=380280 --- Comment #2 from kinta--- Created attachment 106061 --> https://bugs.kde.org/attachment.cgi?id=106061=edit backtrace I can reproduce running the specified test plasmoid in another pc. I have attached the backtrace. The good news are that this bug is fixed in kde neon with testing repos enabled, which upgrade the qt version to 5.9. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow
https://bugs.kde.org/show_bug.cgi?id=381000 --- Comment #16 from Lars Altenhain--- (In reply to Lars Altenhain from comment #15) > I also see that the CPU load of plasmashell even with static background > images is slighlty higher on my normal user account. Here I have always ~2% > for plasmashell. On the test user plasmashell stays below 1% even with the > slideshow active and I only see short spikes when the background image > changes or I change the to another activity. > This has nothing to do with the background image / slideshow. I had slightly different settings on the cpu load plasmoid for both users. If I use the same settings also for the test user I see the 2% for plasmashell on both users. I still can't reproduce the problem with my test user. I tried changing between static image and slideshow several times now and the CPU load stays low, no need to set the cache mode in the main.qml file to true or restarting plasmashell. There must be something in the configuration files of my normal user that triggers the high CPU load behaviour. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380476] Kwin draws 1px overlay on the left screen border
https://bugs.kde.org/show_bug.cgi?id=380476 --- Comment #6 from Andrius Štikonas--- It works fine on Plasma Wayland, only on X11 session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380982] folder icon not properly deselected after closing expanded folder view
https://bugs.kde.org/show_bug.cgi?id=380982 --- Comment #1 from Eike Hein--- I can't reproduce your conclusion, but I see a similar problem - the click-and-drag after starts a rectangle selection for me, but it also opens the folder in Dolphin as if it got a double-click pair. This is likely rooted in something related to bug 380354. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 380797] Cannot set MTU of wired connection
https://bugs.kde.org/show_bug.cgi?id=380797 --- Comment #4 from Neil Rickert--- In openSUSE Tumbleweed, NetworkManager shows up as version 1.6.2. On KaOS, where I also see this problem, NetworkManager appears to be version 1.8.0. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 381069] amarok: position marker created at end of track every time "stop playing after this track" used
https://bugs.kde.org/show_bug.cgi?id=381069 Myriam Schweingruberchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Myriam Schweingruber --- This is not a bug, but a feature. Position markers are needed to be able to resume play on start, even if you do not use this feature. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381124] Renaming files on desktop triggers Krunner
https://bugs.kde.org/show_bug.cgi?id=381124 David Edmundsonchanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-framework/b0e8ea29fab41 ||0ac10f1e73d8ee3de5b2900139f Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- Git commit b0e8ea29fab410ac10f1e73d8ee3de5b2900139f by David Edmundson. Committed on 12/06/2017 at 14:22. Pushed by davidedmundson into branch 'master'. Set Containments to have focus within the view Summary: Now that applets are their own focus scope (which makes sense) we've also made containments their own focus scope. We therefore need to also say the containment FocusScope has the focus within the view. Test Plan: Renamed something in folderview Used cursor nav Reviewers: #plasma Subscribers: plasma-devel, #frameworks Tags: #plasma, #frameworks Differential Revision: https://phabricator.kde.org/D6192 M +1-0src/plasmaquick/containmentview.cpp https://commits.kde.org/plasma-framework/b0e8ea29fab410ac10f1e73d8ee3de5b2900139f -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381131] New: Ripping Video DVDs is not possible, k3b tells you to install transcode although it is installed
https://bugs.kde.org/show_bug.cgi?id=381131 Bug ID: 381131 Summary: Ripping Video DVDs is not possible, k3b tells you to install transcode although it is installed Product: k3b Version: unspecified Platform: openSUSE RPMs URL: https://forums.opensuse.org/showthread.php/525349-K3B- unable-to-find-transcode OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video DVD Assignee: k...@kde.org Reporter: wba...@tmo.at CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- In 17.04.0, transcode support has been disabled (bug#360170). This means that it's currently not possible at all to rip Video DVDs. And even worse, k3b tells the user that transcode couldn't be found even if it is installed. openSUSE's transcode seems to work fine though AFAICT, so I would like to ask you to reconsider that decision and enable transcode support again. Why should people not be able to use it (and DVD ripping at all), if their distribution provides a working transcode? Of course ideally support for other tools should be implemented, maybe ffmpeg could be used? In any case, if transcode is not supported, k3b should not ask the user to install it. And if Video DVD ripping is not working at all (as it is the case now), the menu option should probably be removed completely. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380909] Wrong app icon under plasma wayland session
https://bugs.kde.org/show_bug.cgi?id=380909 --- Comment #12 from Leslie Zhai--- Hi Eike, Thanks for your hint! Regards, Leslie Zhai -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow
https://bugs.kde.org/show_bug.cgi?id=381000 --- Comment #15 from Lars Altenhain--- (In reply to Chris Holland from comment #14) > What's your slideshow interval? I have set the interval to 5 minutes. > > Maybe if you wait for the image to change? Does the cpu spike when the image > changes? Maybe it doesn't spike until then (first image loads fine with low > cpu usage). That's one reason I can think of that it would be a 50/50 chance. > > The other is that Qt's image cache is full one time, and not the next. That > actually seems more likely... hmmm, though it's not something I'd be able to > debug. I need to read up on how Qt caches images. If the CPU load stayed low after restarting plasmashell it also didn't go up when the next image change occurred. In that case I only see a short spike every time the image changes. Another thing I found in the meantime: I have logged into a second session using a newly created test user and I can't reproduce the problem with this user at all, even with the original main.qml file. I tried to setup the desktop in the same way I have on my normal user account: Creating 3 activities and activate the slideshow on all of them using the same folder for the images I have used on my normal user account. I also see that the CPU load of plasmashell even with static background images is slighlty higher on my normal user account. Here I have always ~2% for plasmashell. On the test user plasmashell stays below 1% even with the slideshow active and I only see short spikes when the background image changes or I change the to another activity. My normal user account has config files which are carried over from KDE4. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381130] New: Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 Bug ID: 381130 Summary: Notifications are sometimes misplaced in the left upper corner Product: plasmashell Version: 5.10.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: redredempt...@protonmail.com CC: mklape...@kde.org Target Milestone: 1.0 Created attachment 106060 --> https://bugs.kde.org/attachment.cgi?id=106060=edit Screenshot documenting the bug The newest update for KDE Plasma extra packages [5.35.0-1] brought a new bug that causes some notifications to be misplaced in the *very* upper left corner for a very short while. (It was difficult to take a screenshot of it..) A while before a notification expires, it instantly re-appears back on the right upper corner (as defined in the notification settings). Despite I run Plasma on X11, this bug may be a duplicate of that one: https://bugs.kde.org/show_bug.cgi?id=377970 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380909] Wrong app icon under plasma wayland session
https://bugs.kde.org/show_bug.cgi?id=380909 Eike Heinchanged: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #11 from Eike Hein --- Had a look at this now. The problem is in the K3b source, it sets its organization to "k3b", causing its Wayland app id to be org.k3b.k3b, but the .desktop file it installs is org.kde.k3b.desktop. This needs to be fixed in K3b. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377970] [Wayland] Notifications are often misplaced
https://bugs.kde.org/show_bug.cgi?id=377970 Kamilchanged: What|Removed |Added CC||redredempt...@protonmail.co ||m --- Comment #8 from Kamil --- (In reply to Szymon Łągiewka from comment #6) > I'm curious how the patch will change what we now. For me it's now: > 1. First nofitication shows just like in the attachment. > 2. All the rest will pop up in the upper-left corner. > > Tested with notify-send. What's more important - when I'm sending > notifications from Konsole/Yakuake, the focus is stolen in favour of the > notification. Is it related or deserves another bug report? > > What's also interesting is that KRunner seems to behave in a similar manner > - instead of being in the middle of the top part of the screen - it's in the > upper-left corner. I experience the same bug as Szymon does upon updating the KDE Plasma extra packages on Arch today [the version of those packages is: 5.35.0-1]. Despite it was originally believed to affect Wayland only, the issue is also present on X11. I use Yakuake as the main terminal emulator too, and I can confirm that the bug is present with Yakuake both turned off and on. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379737] Printing specific report page
https://bugs.kde.org/show_bug.cgi?id=379737 --- Comment #6 from Ian Whitfield--- Thanks Jaroslaw I've looked a bit deeper and I think I must correct my statement about Kexi deleting the Report!! It seems as if it only deletes the data in the Table (Still VERY bad!!) which then causes the Query to be null and void which in turn makes the Report not to work. The Query and the Report are still listed but the query comes up as a total blank screen and the Report gives the error Opening object “invoice” failed. Switching to other view failed (Data View). I tested this on the DB I sent you so you should be able to check. BTW - I just found a copy of my Report (first Layout draft) on the other computer so that will save me some work I hope. But how do I copy it from the one computer to the other?? Must I bring the whole DB over from the second machine?? Thanks as always. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow
https://bugs.kde.org/show_bug.cgi?id=381000 --- Comment #14 from Chris Holland--- What's your slideshow interval? Maybe if you wait for the image to change? Does the cpu spike when the image changes? Maybe it doesn't spike until then (first image loads fine with low cpu usage). That's one reason I can think of that it would be a 50/50 chance. The other is that Qt's image cache is full one time, and not the next. That actually seems more likely... hmmm, though it's not something I'd be able to debug. I need to read up on how Qt caches images. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 380938] [OpenConnect] Connection timed out when using "AC certificate file"
https://bugs.kde.org/show_bug.cgi?id=380938 --- Comment #4 from Christian González--- Yes, it's the second part of the logs I've posted. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356006] Breeze GTK does not respect the color scheme
https://bugs.kde.org/show_bug.cgi?id=356006 Hamidreza Jafarichanged: What|Removed |Added CC||hamidrjaf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #38 from Thomas Schmitt--- Hi, i think the new message in https://cgit.kde.org/k3b.git/commit/?id=41e6f110c7f2753b20537c23bad56b8ac4896ba2 is a bit courageous and makes the user wonder why the message is emitted at all: > "Found files bigger than 2 GB. These files will be fully accessible." I propose to either - omit the message (and only check for mkisofs option -allow-limited-size) - or to state that the files may be problematic on very old Linux and on systems which do not mount the UDF aspect of an ISO by default. Reasoning: The Large File Support of Linux stems from the early years of this century. E.g. these are introductions with modification dates 2004 and 2005: https://people.redhat.com/berrange/notes/largefile.html http://users.suse.com/~aj/linux_lfs.html The latter is talking of kernels 2.2 and 2.4. mkisofs with option -udf produces both sets of metadata: ISO 9660 and UDF. Linux and MS-Windows mount UDF by default if they see such a ISO 9660/UDF hybrid filesystem. The other operating systems have to be suspected to not handle large data files in ISO 9660 correctly. The ones among them, which do not mount the UDF aspect by default, will show problems. On POSIX compliant systems, which cannot properly read large files from ISO 9660 filesystems, it should be possible to use GNU xorriso for extracting large files to the local disk. Large File Support by the local operating system is then mandatory, of course. (xorriso can cut a large file into pieces before putting it onto hard disk. But such pieces are of course cumbersome to use.) Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381129] New: Dragging files over grouped tasks is broken
https://bugs.kde.org/show_bug.cgi?id=381129 Bug ID: 381129 Summary: Dragging files over grouped tasks is broken Product: plasmashell Version: 5.10.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: aro...@archlinux.org CC: plasma-b...@kde.org Target Milestone: 1.0 Dragging a file to a window which is part of a task manager group is broken in several ways: - When dragging the file over the task manager group, you get the pop-up with the individual windows, but hovering the task items doesn't bring the window to the top. - If you now move to a different group, you always get the pop-up of the first group you hovered instead of the one you're currently over. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 370425] No focus indicator on buttons with Breeze and Breeze dark GTK themes
https://bugs.kde.org/show_bug.cgi?id=370425 Hamidreza Jafarichanged: What|Removed |Added CC||hamidrjaf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381128] [hidpi] Preview shows thumbnails bar bigger than preview
https://bugs.kde.org/show_bug.cgi?id=381128 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- >Since the size is not saved when closing the program the user has to redo this >>everytime the program is opened. Can you imagine seriously that we don't save the GUI geometry properties ??? Not reproducble here with 5.6.0. The thumbbar size is stored in digikamrc file as expected. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.