[kdeconnect] [Bug 480197] KDE Connect crashes on startup
https://bugs.kde.org/show_bug.cgi?id=480197 --- Comment #2 from Alvaro Avalos --- Created attachment 165145 --> https://bugs.kde.org/attachment.cgi?id=165145=edit New crash information added by DrKonqi kdeconnectd (23.08.4) using Qt 5.15.12 Happened after system update and reboot, did not help reinstalling, nor erasing ./config/kdeconnect folder -- Backtrace (Reduced): #4 Device::reloadPlugins (this=this@entry=0x55939a6efab0) at ./core/device.cpp:184 #5 0x7f2cfdf37aa1 in Device::pairingHandler_pairingSuccessful (this=0x55939a6efab0) at ./core/device.cpp:253 #6 0x7f2cfc8f4db4 in QtPrivate::QSlotObjectBase::call (a=0x7ffc694d3ca0, r=0x55939a6efab0, this=0x55939a6f0680) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate (sender=0x55939a70d2c0, signal_index=5, argv=0x7ffc694d3ca0) at kernel/qobject.cpp:3925 #8 0x7f2cfc8f4db4 in QtPrivate::QSlotObjectBase::call (a=0x7ffc694d3e80, r=0x55939a6efab0, this=0x55939a6f0250) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 480197] KDE Connect crashes on startup
https://bugs.kde.org/show_bug.cgi?id=480197 Alvaro Avalos changed: What|Removed |Added CC||alvaroaval...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 3212] Option to hide backup files as well as dotfiles?
https://bugs.kde.org/show_bug.cgi?id=3212 --- Comment #77 from Alvaro Aguilera --- Is there a point in keeping tickets like this open for 23+ years? I keep receiving notifications for several of them. If a problem isn't resolved in, let's say 5 years, it probably never will or the affected component will be deprecated and replaced with something else. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 468745] Konsole Context Menu: Open File Manager Option Fails to Open
https://bugs.kde.org/show_bug.cgi?id=468745 Alvaro Carroz changed: What|Removed |Added CC||alvaro.car...@gmail.com --- Comment #10 from Alvaro Carroz --- Also happens to me with Konsole 23.04.2, on both Wayland and XOrg. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458839] New: I can not save my edited pdf on my computer. The error is: Access denied to C:
https://bugs.kde.org/show_bug.cgi?id=458839 Bug ID: 458839 Summary: I can not save my edited pdf on my computer. The error is: Access denied to C: Product: okular Version: 20.12.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: alvarosaizuni...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Save my edited pdf in a file in the desktop 2. 3. OBSERVED RESULT I can't save the edited pdf in the folder where I had the original pdf EXPECTED RESULT It is saved successfully in the same folder where the original pdf was located 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.
[lattedock] [Bug 456199] Panel indicator line remain when panel is hidden or visible
https://bugs.kde.org/show_bug.cgi?id=456199 --- Comment #2 from Alvaro --- (In reply to Michail Vourlakos from comment #1) > this is a kwin issue. Latte is not responsible for that line But Latte is directly interacting with it, isn't? Should I report a kwin issue? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456203] Panel indicator line is shown in the wrong place
https://bugs.kde.org/show_bug.cgi?id=456203 --- Comment #1 from Alvaro --- Created attachment 150318 --> https://bugs.kde.org/attachment.cgi?id=150318=edit Panel -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456199] Panel indicator line remain when panel is hidden or visible
https://bugs.kde.org/show_bug.cgi?id=456199 Alvaro changed: What|Removed |Added Blocks||456203 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=456203 [Bug 456203] Panel indicator line is shown in the wrong place -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456203] New: Panel indicator line is shown in the wrong place
https://bugs.kde.org/show_bug.cgi?id=456203 Bug ID: 456203 Summary: Panel indicator line is shown in the wrong place Product: lattedock Version: 0.10.8 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: panabu...@gmail.com CC: mvourla...@gmail.com, panabu...@gmail.com Depends on: 456199 Target Milestone: --- Created attachment 150317 --> https://bugs.kde.org/attachment.cgi?id=150317=edit Issue Video SUMMARY *** When I move the pointer to where the panel is, it isn't showing the panel indicator line in the place it suppose to be, instead it will show above of it *** I'm attaching a video with the problem that it will explain better for itself STEPS TO REPRODUCE 1. Move the pointer where the panel is to make it visible 2. Make the panel visible OBSERVED RESULT Panel indicator line isn't where the panel is EXPECTED RESULT Panel indicator line should be where the panel is SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.18.6-1-MANJARO (64-bit) KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Graphics Platform: X11 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=456199 [Bug 456199] Panel indicator line remain when panel is hidden or visible -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456199] Panel indicator line remain when panel is hidden or visible
https://bugs.kde.org/show_bug.cgi?id=456199 Alvaro changed: What|Removed |Added CC||panabu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456199] New: Panel indicator line remain when panel is hidden or visible
https://bugs.kde.org/show_bug.cgi?id=456199 Bug ID: 456199 Summary: Panel indicator line remain when panel is hidden or visible Product: lattedock Version: 0.10.8 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: panabu...@gmail.com Target Milestone: --- Created attachment 150316 --> https://bugs.kde.org/attachment.cgi?id=150316=edit Issue Video SUMMARY *** When I move the pointer slowly to the panel to make it visible, the panel indicator line will be still visible when it should be hidden *** I'm attaching a video with the problem that it will explain better for itself STEPS TO REPRODUCE 1. Move slowly the pointer where the panel is to make it visible 2. Make the panel visible 3. Move the pointer out of the panel to hide it OBSERVED RESULT Panel indicator line still visible EXPECTED RESULT Panel indicator line should be hidden SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.18.6-1-MANJARO (64-bit) KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 452382] KScreen turns my monitor back on after "xset dpms force off"
https://bugs.kde.org/show_bug.cgi?id=452382 Alvaro Carroz changed: What|Removed |Added CC||alvaro.car...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 442061] Valgrind: very slow execution under Fedora 34
https://bugs.kde.org/show_bug.cgi?id=442061 --- Comment #4 from Alvaro Kuolas --- I want to clarify that I installed debuginfo to try gdb reverse-step. The packages installed where: dnf install debuginfo-install glibc-2.33-20.fc34.x86_64 libgcc-11.2.1-1.fc34.x86_64 libstdc++-11.2.1-1.fc34.x86_64 Without the debuginfo packages it works as expected. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 442061] Valgrind: very slow execution under Fedora 34
https://bugs.kde.org/show_bug.cgi?id=442061 Alvaro Kuolas changed: What|Removed |Added CC||kuo...@gmail.com --- Comment #1 from Alvaro Kuolas --- Created attachment 141323 --> https://bugs.kde.org/attachment.cgi?id=141323=edit perf record data Attached is perf record data -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 442061] New: Valgrind: very slow execution under Fedora 34
https://bugs.kde.org/show_bug.cgi?id=442061 Bug ID: 442061 Summary: Valgrind: very slow execution under Fedora 34 Product: valgrind Version: unspecified Platform: Fedora RPMs OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: kuo...@gmail.com Target Milestone: --- SUMMARY I am running valgrind on my PC with dual boot Windows 10 and Fedora 34. Running the same test on Ubuntu 20.04 (under Windows 10 WSL2) valgrind runs in less than a second, but on Fedora 34 is very slow, several minutes slow. On Fedora 34 it looks like the time spent is reading symbols. This is the part that takes most of the time: --23524-- Reading syms from /usr/lib64/libstdc++.so.6.0.29 --23524-- Considering /usr/lib/debug/.build-id/bd/d633ff5da0bba64d19ecf277a9eed7001da127.debug .. --23524-- .. build-id is valid --23524-- Considering /usr/lib/debug/.build-id/bd/../../../../../usr/lib/debug/usr/lib64/../../.dwz/gcc-11.2.1-1.fc34.x86_64 .. --23524-- .. build-id is valid --23524-- Reading syms from /usr/lib64/libm-2.33.so --23524-- Considering /usr/lib/debug/.build-id/c1/784bbe8a93a6e62f74b16105a2076a03b398ac.debug .. --23524-- .. build-id is valid --23524-- Reading syms from /usr/lib64/libgcc_s-11-20210728.so.1 --23524-- Considering /usr/lib/debug/.build-id/46/e10c9ee769c5cfc7cdb638e3ccbc3169c0a949.debug .. --23524-- .. build-id is valid --23524-- Considering /usr/lib/debug/.build-id/46/../../../../../usr/lib/debug/lib64/../.dwz/gcc-11.2.1-1.fc34.x86_64 .. --23524-- .. build-id is valid --23524-- Reading syms from /usr/lib64/libc-2.33.so --23524-- Considering /usr/lib/debug/.build-id/9d/e0f6e78ec16db4c6c167efc6b37466705edeff.debug .. --23524-- .. build-id is valid --23524-- Considering /usr/lib/debug/.build-id/9d/../../../../../usr/lib/debug/lib64/../.dwz/glibc-2.33-20.fc34.x86_64 .. --23524-- .. build-id is valid STEPS TO REPRODUCE 1. Run valgrind on a simple binary OBSERVED RESULT It takes minutes to execute. EXPECTED RESULT It should be instant as the program is very simple like "hello world". SOFTWARE/OS VERSIONS Linux: 5.13.13-200.fc34.x86_64 #1 SMP Thu Aug 26 17:06:39 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ADDITIONAL INFORMATION Using GCC 11 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 226548] Groups goes crazy after closing and reopen kopete
https://bugs.kde.org/show_bug.cgi?id=226548 --- Comment #21 from Alvaro Manuel Recio Perez --- Ok, I've realized that I wasn't the original reporter of the issue. I was closing all the issues for which I had received the request to confirm the bug and I marked this one as resolved by mistake. If anyone else can confirm the issue, please feel free to reopen it. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 226548] Groups goes crazy after closing and reopen kopete
https://bugs.kde.org/show_bug.cgi?id=226548 Alvaro Manuel Recio Perez changed: What|Removed |Added Resolution|--- |LATER Status|CONFIRMED |RESOLVED --- Comment #20 from Alvaro Manuel Recio Perez --- I'm no longer using Kopete. I can't confirm the bug so I'm changing the status of this issue, as requested. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 227963] Kopete rich text formatting options changed after pasting rich text
https://bugs.kde.org/show_bug.cgi?id=227963 Alvaro Manuel Recio Perez changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |LATER --- Comment #5 from Alvaro Manuel Recio Perez --- I'm no longer using Kopete. I can't confirm the bug so I'm changing the status of this issue, as requested. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 231219] Memory leak when using multiple jabber accounts
https://bugs.kde.org/show_bug.cgi?id=231219 Alvaro Soliverez changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 309566] XPS displays fine but print and print preview output a mangled page
https://bugs.kde.org/show_bug.cgi?id=309566 Alvaro Soliverez changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 432373] New: Discover application crashes when opened
https://bugs.kde.org/show_bug.cgi?id=432373 Bug ID: 432373 Summary: Discover application crashes when opened Product: Discover Version: 5.12.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: kort...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.12.8) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 5.4.0-51-generic x86_64 Distribution: Ubuntu 18.04.5 LTS -- Information about the crash: - What I was doing when the application crashed: Trying to opèn Discover, both from the launch menu and from the system tray notification (updates notified) The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0f46008800 (LWP 17874))] Thread 13 (Thread 0x7f0efce71700 (LWP 17897)): #0 0x7ffd0d77099a in clock_gettime () #1 0x7f0f415efd36 in __GI___clock_gettime (clock_id=1, tp=0x7f0efce70b20) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f0f41f1c1c1 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0f41f1a9f9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0f41f1afd5 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0f41f1cc3c in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0f3bdcab28 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f0f3bdcb4fb in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f0f3bdcb6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f0f41f1c8ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f0f41ec190a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f0f41ce023a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f0f41ce517d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f0f3def36db in start_thread (arg=0x7f0efce71700) at pthread_create.c:463 #14 0x7f0f415e071f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f0efda88700 (LWP 17896)): #0 0x7f0f3def9fb9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f0efda87c40, expected=0, futex_word=0x7f0ef8009a90) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f0f3def9fb9 in __pthread_cond_wait_common (abstime=0x7f0efda87d00, mutex=0x7f0ef8009a40, cond=0x7f0ef8009a68) at pthread_cond_wait.c:533 #2 0x7f0f3def9fb9 in __pthread_cond_timedwait (cond=0x7f0ef8009a68, mutex=0x7f0ef8009a40, abstime=0x7f0efda87d00) at pthread_cond_wait.c:667 #3 0x7f0f41ce6468 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0f41ce253d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0f41ce517d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0f3def36db in start_thread (arg=0x7f0efda88700) at pthread_create.c:463 #7 0x7f0f415e071f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f0efe289700 (LWP 17890)): #0 0x7f0f3def9fb9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f0efe288c40, expected=0, futex_word=0x7f0ef8006fc0) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f0f3def9fb9 in __pthread_cond_wait_common (abstime=0x7f0efe288d00, mutex=0x7f0ef8006f70, cond=0x7f0ef8006f98) at pthread_cond_wait.c:533 #2 0x7f0f3def9fb9 in __pthread_cond_timedwait (cond=0x7f0ef8006f98, mutex=0x7f0ef8006f70, abstime=0x7f0efe288d00) at pthread_cond_wait.c:667 #3 0x7f0f41ce6468 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0f41ce253d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0f41ce517d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0f3def36db in start_thread (arg=0x7f0efe289700) at pthread_create.c:463 #7 0x7f0f415e071f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f0eff0a6700 (LWP 17888)): #0 0x7f0f3def9fb9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f0eff0a5c40, expected=0, futex_word=0x7f0ef80042f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f0f3def9fb9 in __pthread_cond_wait_common (abstime=0x7f0eff0a5d00, mutex=0x7f0ef80042a0, cond=0x7f0ef80042c8) at pthread_cond_wait.c:533 #2 0x7f0f3def9fb9 in __pthread_cond_timedwait (cond=0x7f0ef80042c8, mutex=0x7f0ef80042a0, abstime=0x7f0eff0a5d00) at pthread_cond_wait.c:667 #3 0x7f0f41ce6468 in
[okular] [Bug 205496] Okular's "Advance to the next page" jumps to middle of next page
https://bugs.kde.org/show_bug.cgi?id=205496 alvaro changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #31 from alvaro --- I can confirm this issue is no longer present for the documents i've seen so far. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 423003] krunner crashes as soon as I start typing when PIM Contact Search plugin is enabled
https://bugs.kde.org/show_bug.cgi?id=423003 --- Comment #45 from Alvaro --- Created attachment 131002 --> https://bugs.kde.org/attachment.cgi?id=131002=edit New crash information added by DrKonqi krunner (5.19.4) using Qt 5.14.2 - What I was doing when the application crashed: Pressed Alt-F2 and typing whatever and then crash, restarting krunner didn't fix the error -- Backtrace (Reduced): #4 QReadWriteLock::tryLockForRead (this=0x5633f4611010, timeout=-1) at thread/qreadwritelock.cpp:263 #5 0x7f74709b7b72 in QReadLocker::relock (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qreadwritelock.h:113 #6 QReadLocker::QReadLocker (areadWriteLock=, this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qreadwritelock.h:125 #7 Plasma::QueryMatch::urls (this=this@entry=0x5633f4c80690) at ./src/querymatch.cpp:264 #8 0x7f74709a52ac in Plasma::AbstractRunner::mimeDataForMatch (this=, match=...) at ./src/abstractrunner.cpp:225 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 423003] krunner crashes as soon as I start typing when PIM Contact Search plugin is enabled
https://bugs.kde.org/show_bug.cgi?id=423003 Alvaro changed: What|Removed |Added CC||panabu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 395854] Unable to enter Korean text with remote keyboard
https://bugs.kde.org/show_bug.cgi?id=395854 Alvaro Fernando García changed: What|Removed |Added CC||alvarofernandogarcia@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405659] Plasma segfault when removing widget
https://bugs.kde.org/show_bug.cgi?id=405659 Alvaro Prataviera Filho changed: What|Removed |Added CC||alvaro.prata.fi...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413616] plasma crashed after attempting to delete widgets
https://bugs.kde.org/show_bug.cgi?id=413616 Alvaro Prataviera Filho changed: What|Removed |Added CC||alvaro.prata.fi...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 413448] New: Plasmoid shows a big margin in right side
https://bugs.kde.org/show_bug.cgi?id=413448 Bug ID: 413448 Summary: Plasmoid shows a big margin in right side Product: plasma-pa Version: 5.17.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: panabu...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 123485 --> https://bugs.kde.org/attachment.cgi?id=123485=edit Audio plasmoid SUMMARY Audio plasmoid shows a big margin in the right side, which it wasn't shown with plasma 5.17.0. When the plasmoid is opened from the system tray the bug is not happening and it shows as normal. STEPS TO REPRODUCE 1. Add Plasmoid to a bar 2. Click on it OBSERVED RESULT The plasmoid shows a big right margin EXPECTED RESULT Show as usual SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE NEON (available in About System) KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Using late dock 0.9.3 4k screen but using resolution 2560x1440 with a scaling factor of 1.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413018] Plasma crashes in slideshow
https://bugs.kde.org/show_bug.cgi?id=413018 Alvaro Carroz changed: What|Removed |Added CC||alvaro.car...@gmail.com --- Comment #26 from Alvaro Carroz --- I think Bug 350148 is also related to this bug. It causes the .xsession-errors to grow to over 20MB just after login. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpackage] [Bug 350148] plasmashell wants "metadata.desktop" files in slideshow sub-directories for some reason and isn't too shy to mention it 3 times per image
https://bugs.kde.org/show_bug.cgi?id=350148 Alvaro Carroz changed: What|Removed |Added CC||alvaro.car...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpackage] [Bug 396994] plasma shell desktop wallpaper slideshow: log filling up with "No metadata file in the package"
https://bugs.kde.org/show_bug.cgi?id=396994 Alvaro Carroz changed: What|Removed |Added CC||alvaro.car...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409805] New: No error when no space left on device via sftp
https://bugs.kde.org/show_bug.cgi?id=409805 Bug ID: 409805 Summary: No error when no space left on device via sftp Product: dolphin Version: 19.04.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: asolive...@kde.org CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY Tried to copy a large number of files from a USB to a remote server via sftp. Server disk was too small and ran out of space, but still Dolphin said copying finished successfully STEPS TO REPRODUCE 1. Open USB folder 2. Open a new pane in Dolphin 3. Open server folder using sftp (sftp://server:/home/asoliverez/folder 4. Copy and paste files into the new folder 5. After only a few seconds, copying finishes, seemingly successfully 6. No files have been copied, because server ran out of disk space OBSERVED RESULT No files copied No error message Only message is Copying (finished) EXPECTED RESULT Error message with "No space left on device" SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409484] Dock does not show when drag and drop file
https://bugs.kde.org/show_bug.cgi?id=409484 --- Comment #2 from Alvaro --- (In reply to Michail Vourlakos from comment #1) > I had tested this with upcoming git version and it was working, > unfortunately v0.8 maintenance has ended in favor of upcoming v0.9 OK, thanks. I'm looking forward to try the new version. Is there any release date at the moment? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409484] Dock does not show when drag and drop file
https://bugs.kde.org/show_bug.cgi?id=409484 Alvaro changed: What|Removed |Added CC||panabu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409484] New: Dock does not show when drag and drop file
https://bugs.kde.org/show_bug.cgi?id=409484 Bug ID: 409484 Summary: Dock does not show when drag and drop file Product: lattedock Version: 0.8.9 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: panabu...@gmail.com Target Milestone: --- When I try to drag a file to the dock when it's hidden, it doesn't show up. You can check the problem in this GIF: https://media.giphy.com/media/MCQykQqkKCM8HHkWhJ/giphy.gif STEPS TO REPRODUCE 1. Set the dock in Dodge Active or auto hide 2. Maximize Dolphin window or cover the dock with it 3. Drag a file from Dolphin to the dock OBSERVED RESULT The dock does not show up so I cannot maximize the desired program to share the file. Maybe something to do with the UDH screen? EXPECTED RESULT The dock show up and then I can maximize another windows to share the file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Screen Resolution: UHD ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Tasks are only launched when are clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 --- Comment #35 from Alvaro --- Yhea...issue solved for me as well with the upgrade Thanks @Michail Vourlakos for the time -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 Alvaro changed: What|Removed |Added Attachment #118177|text/plain |image/jpg mime type|| -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 Alvaro changed: What|Removed |Added Attachment #118177|Latte layout file |ll description|| -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 Alvaro changed: What|Removed |Added Attachment #118177|0 |1 is obsolete|| Attachment #118177|layout_latte.layout.latte |ll filename|| -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 --- Comment #12 from Alvaro --- Created attachment 118177 --> https://bugs.kde.org/attachment.cgi?id=118177=edit Latte layout file -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404285] Click on the mid-bottom zone of the dock do nothing
https://bugs.kde.org/show_bug.cgi?id=404285 --- Comment #4 from Alvaro --- (In reply to Alvaro from comment #3) > (In reply to Michail Vourlakos from comment #2) > > Have you enabled PLASMA_USE_QT_SCALING? > > Not really, should I? and how can enable it? Just execute latte-dock with PLASMA_USE_QT_SCALING and I'm having the same behavior. Also I've changed to FullHd resolution with no scaling and same behavior :S -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404285] Click on the mid-bottom zone of the dock do nothing
https://bugs.kde.org/show_bug.cgi?id=404285 --- Comment #3 from Alvaro --- (In reply to Michail Vourlakos from comment #2) > Have you enabled PLASMA_USE_QT_SCALING? Not really, should I? and how can enable it? -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404285] Click on the mid-bottom zone of the dock do nothing
https://bugs.kde.org/show_bug.cgi?id=404285 --- Comment #1 from Alvaro --- Created attachment 118035 --> https://bugs.kde.org/attachment.cgi?id=118035=edit Right Click different behavior -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404285] Click on the mid-bottom zone of the dock do nothing
https://bugs.kde.org/show_bug.cgi?id=404285 Alvaro changed: What|Removed |Added CC||panabu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404285] New: Click on the mid-bottom zone of the dock do nothing
https://bugs.kde.org/show_bug.cgi?id=404285 Bug ID: 404285 Summary: Click on the mid-bottom zone of the dock do nothing Product: latte-dock Version: 0.8.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: panabu...@gmail.com Target Milestone: --- After update to Plasma 5.15 latte dock started to stop work properly. Clicking in the mid-bottom zone of the dock has different behavior. - Left Click: Do nothing - Middle Scroll Click: Do nothing - Down Scroll: Act like left click - Right Click: Show just latte dock contextual menu but not the launcher menu I've attached a screenshot with the two different menus with right click (full menu when click in mid-top zone and just latte menu on mid-bottom zone) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION Screen: 4k Screen scaling: 2x Laptop: Dell XPS15 9550 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 208320] Opening Links in Kopete
https://bugs.kde.org/show_bug.cgi?id=208320 --- Comment #2 from Alvaro Aguilera --- I moved to pidgin several years ago and haven't used kopete ever since. Feel free to close the bug. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397344] Force solid background for maximized windows not working with qt apps and borderless maximized windows active when they are maximized with double-clicking and screen scale fa
https://bugs.kde.org/show_bug.cgi?id=397344 --- Comment #16 from Alvaro --- (In reply to Michail Vourlakos from comment #15) > This is kwin upstream issue and you can follow the discussion there when I > uploaded the infos. > > Fast way to solve this: > > 1. The issue appears when double-clicking the window titlebar and only for > qt-based apps. If you drag the window title bar to the top the issue doesnt > appear > > 2. In order to workaround it another way is to change the panel heights and > make it even e.g. 31px., 33px. etc... > it breaks only for odd values, 32px., 34px. etc.. 1. That's true 2. I've tried to change the panel height but the issue still there. PS:Just saying thanks for the great work you are doing :) -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397344] Force solid background for maximized windows not working with qt apps and borderless maximized windows active
https://bugs.kde.org/show_bug.cgi?id=397344 --- Comment #13 from Alvaro --- (In reply to Michail Vourlakos from comment #12) > ok, I think I found it, in your parameters there is: > > QT_SCREEN_SCALE_FACTORS=eDP-1=2;DP-1=2;HDMI-1=2;DP-2=2;HDMI-2=2; > > in my system even when from plasma systemsettings I use Scale Factor=2 these > variables dont change. > > 1. what is your plasma version? > 2. Have you set that manually? > 3. What is your Qt version? 1. 5.13.4 2. No, I set the scale parameter from the monitor settings window 3. 5.11.1 > in my system even when from plasma systemsettings I use Scale Factor=2 these > variables dont change. Maybe you should logout or restart. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397344] Force solid background for maximized windows not working with qt apps and borderless maximized windows active
https://bugs.kde.org/show_bug.cgi?id=397344 --- Comment #14 from Alvaro --- (In reply to Michail Vourlakos from comment #11) > (In reply to Alvaro from comment #10) > > (In reply to Michail Vourlakos from comment #9) > > > (In reply to Alvaro from comment #8) > > > > Yhea...with scale = 1 the issue is fixed > > try to run latte from the terminal with command: latte-dock -d --with-window > > > it will show you a Latte debug window, when the issue appears what is the > screen resolution used by Latte dock, do you notice anything strange? I've noticed that when I change the active window between app with no issue and app with issue the parameter StartLayoutSize(no fill applets) change a lot: Not Issued apps - Firefox: 1071 px - Thunderbird: 985 px - Android studio: 483 px Issued apps - Konsole: 483 px - Systemsettings: 490 px - KsysGuard: 483 px Also the value "Draw Shadows(external)" changes. When I maximize the windows with no issue the value change from "No" to "Yes" and when I do it with the apps with the issue it remains in "No" -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397344] Force solid background for maximized windows not working with qt apps and borderless maximized windows active
https://bugs.kde.org/show_bug.cgi?id=397344 --- Comment #10 from Alvaro --- (In reply to Michail Vourlakos from comment #9) > (In reply to Alvaro from comment #8) > > I've sent you the layout file. I'm using scaling in the main settings, 2x > > scaling > > it works just fine in my system. > If you change your scaling to 1x the issue is fixed? Yhea...with scale = 1 the issue is fixed -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397344] Force solid background for maximized windows not working with qt apps and borderless maximized windows active
https://bugs.kde.org/show_bug.cgi?id=397344 --- Comment #8 from Alvaro --- I've sent you the layout file. I'm using scaling in the main settings, 2x scaling -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397344] Force solid background for maximized windows not working with qt apps and borderless maximized windows active
https://bugs.kde.org/show_bug.cgi?id=397344 --- Comment #6 from Alvaro --- XDG_VTNR=7 LC_PAPER=en_GB XDG_SESSION_ID=4 SSH_AGENT_PID=2986 PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket LC_ADDRESS=en_GB LC_MONETARY=en_GB GPG_AGENT_INFO=/home/panabuntu/.gnupg/S.gpg-agent:0:1 TERM=xterm-256color SHELL=/bin/bash KONSOLE_DBUS_SERVICE=:1.158 DERBY_HOME=/usr/lib/jvm/java-8-oracle/db QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 KONSOLE_PROFILE_NAME=Profile 1 GS_LIB=/home/panabuntu/.fonts WINDOWID=148897799 LC_NUMERIC=en_GB SHELL_SESSION_ID=4446d38f1db240d79689d43055136e10 GTK_MODULES=appmenu-gtk-module XDG_SESSION_CLASS=user KDE_FULL_SESSION=true USER=panabuntu LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36: XCURSOR_SIZE=0 QT_ACCESSIBILITY=1 LC_TELEPHONE=en_GB XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session3 XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 QT_AUTO_SCREEN_SCALE_FACTOR=0 SSH_AUTH_SOCK=/tmp/ssh-FDEUfz96U2x9/agent.2939 SESSION_MANAGER=local/panalaptop:@/tmp/.ICE-unix/3040,unix/panalaptop:/tmp/.ICE-unix/3040 QT_SCREEN_SCALE_FACTORS=eDP-1=2;DP-1=2;HDMI-1=2;DP-2=2;HDMI-2=2; DEFAULTS_PATH=/usr/share/gconf//usr/share/xsessions/plasma.default.path LIBVIRT_DEFAULT_URI=qemu:///system XDG_CONFIG_DIRS=/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg PATH=/home/panabuntu/bin:/home/panabuntu/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin DESKTOP_SESSION=/usr/share/xsessions/plasma LC_IDENTIFICATION=en_GB XDG_SESSION_TYPE=x11 PWD=/home/panabuntu JAVA_HOME=/usr/lib/jvm/java-8-oracle KONSOLE_DBUS_WINDOW=/Windows/1 LANG=en_GB.UTF-8 KDE_SESSION_UID=1000 MANDATORY_PATH=/usr/share/gconf//usr/share/xsessions/plasma.mandatory.path LC_MEASUREMENT=en_GB UBUNTU_MENUPROXY=1 KONSOLE_DBUS_SESSION=/Sessions/1 XDG_SEAT=seat0 SHLVL=1 HOME=/home/panabuntu COLORFGBG=15;0 LANGUAGE=en_GB:en_US KDE_SESSION_VERSION=5 XCURSOR_THEME=breeze_cursors XDG_SESSION_DESKTOP=KDE LOGNAME=panabuntu XDG_DATA_DIRS=/home/panabuntu/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share/:/usr/share//usr/share/xsessions/plasma:/home/panabuntu/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop J2SDKDIR=/usr/lib/jvm/java-8-oracle DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-WPoWgmiM9n,guid=f74dccd69a089617640d31d35b7a7661 LESSOPEN=| /usr/bin/lesspipe %s XDG_RUNTIME_DIR=/run/user/1000 PROFILEHOME= DISPLAY=:0 XDG_CURRENT_DESKTOP=KDE J2REDIR=/usr/lib/jvm/java-8-oracle/jre LESSCLOSE=/usr/bin/lesspipe %s %s LC_TIME=en_GB XAUTHORITY=/home/panabuntu/.Xauthority LC_NAME=en_GB COLORTERM=truecolor _=/usr/bin/env -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397344] Force solid background for maximized windows not working with qt apps and borderless maximized windows active
https://bugs.kde.org/show_bug.cgi?id=397344 --- Comment #4 from Alvaro --- Sorry, I don't know how to check that. Could you tell me please? -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397344] Force solid background for maximized windows not working with qt apps and borderless maximized windows active
https://bugs.kde.org/show_bug.cgi?id=397344 --- Comment #2 from Alvaro --- To reproduce the bug: - Create a top bar - Activate "Force solid background for maximized or snapped windows" - Activate "Hide background for not maximized windows" - Check "Support borderless maximized windows in different layouts" checkbox in Preferences tab of Settings windows and activate for the layout in "Layout" tab - Open Dolphin and maximize it In my case the bug happens with apps made in Qt: Dolphin, qbittorrent, Settings, Discover, Vlc With other apps such Firefox the tweak is working fine. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397344] Force solid background for maximized windows not working with qt apps and borderless maximized windows active
https://bugs.kde.org/show_bug.cgi?id=397344 Alvaro changed: What|Removed |Added CC||panabu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397344] New: Force solid background for maximized windows not working with qt apps and borderless maximized windows active
https://bugs.kde.org/show_bug.cgi?id=397344 Bug ID: 397344 Summary: Force solid background for maximized windows not working with qt apps and borderless maximized windows active Product: latte-dock Version: 0.8.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: panabu...@gmail.com Target Milestone: --- Created attachment 114392 --> https://bugs.kde.org/attachment.cgi?id=114392=edit Transparent bar background with System Settings windows Force solid background for maximized windows is not working when I use qt apps (dolphin, qtbittorrent...) and borderless maximezed windows. When I use firefox works normally. Notice that I have installed Active Windows Control and Global Menu plasmoids. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 395771] Some plasmoid settings (specifically Active Window Control) are not persisted within latte-dock git (master)
https://bugs.kde.org/show_bug.cgi?id=395771 Alvaro changed: What|Removed |Added CC||panabu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373793] New: Workspace behavior crash every time
https://bugs.kde.org/show_bug.cgi?id=373793 Bug ID: 373793 Summary: Workspace behavior crash every time Product: systemsettings Version: 5.8.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: wagneralvar...@gmail.com Target Milestone: --- Application: systemsettings5 (5.8.4) Qt Version: 5.7.1 Frameworks Version: 5.27.0 Operating System: Linux 4.8.14-300.fc25.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Just browsing in the workspcae behavior section - Unusual behavior I noticed: I did not notice anything unusual - Custom settings of the application: My most significant change was in the composer I changed from opengl 2.0 to opengl 3 The crash can be reproduced every time. -- Backtrace: Application: Configurações do Sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f37a10d06c0 (LWP 8112))] Thread 7 (Thread 0x7f376ef7a700 (LWP 8356)): #0 0x7f37a5b42814 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f37a5afd10a in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f37a5afd26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f37ada7073b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f37ada2173a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f37ad87e5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f374ee342c7 in KCupsConnection::run() () at /lib64/libkcupslib.so #7 0x7f37ad8829da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f37a9d466ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f37acc75f6f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f376e0cd700 (LWP 8163)): #0 0x7f37acc6a00d in poll () at /lib64/libc.so.6 #1 0x7f37a5afd156 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f37a5afd26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f37ada7073b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f37ada2173a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f37ad87e5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f37ac4424e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f37ad8829da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f37a9d466ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f37acc75f6f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f377fd46700 (LWP 8125)): #0 0x7f37acc65bdd in read () at /lib64/libc.so.6 #1 0x7f37a5b41450 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f37a5afcc60 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f37a5afd0f4 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f37a5afd4e2 in g_main_loop_run () at /lib64/libglib-2.0.so.0 #5 0x7f37964d7946 in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0 #6 0x7f37a5b24b03 in g_thread_proxy () at /lib64/libglib-2.0.so.0 #7 0x7f37a9d466ca in start_thread () at /lib64/libpthread.so.0 #8 0x7f37acc75f6f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f3780547700 (LWP 8124)): #0 0x7f37acc6a00d in poll () at /lib64/libc.so.6 #1 0x7f37a5afd156 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f37a5afd26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f37a5afd2b1 in glib_worker_main () at /lib64/libglib-2.0.so.0 #4 0x7f37a5b24b03 in g_thread_proxy () at /lib64/libglib-2.0.so.0 #5 0x7f37a9d466ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f37acc75f6f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f378d9fb700 (LWP 8114)): #0 0x7f37ad87ad93 in QMutex::unlock() () at /lib64/libQt5Core.so.5 #1 0x7f37ada70611 in postEventSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #2 0x7f37a5afcba9 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f37a5afd0f4 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f37a5afd26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f37ada7073b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f37ada2173a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f37ad87e5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f37ae16d739 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #9 0x7f37ad8829da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f37a9d466ca in start_thread () at
[plasmashell] [Bug 367947] New: Task manager shows tasks from wrong screen
https://bugs.kde.org/show_bug.cgi?id=367947 Bug ID: 367947 Summary: Task manager shows tasks from wrong screen Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: alvaro.aguil...@gmail.com CC: plasma-b...@kde.org KDE 5 has "some issues" handling an external monitor plugged to the laptop. While it remembers the resolution and relative position, the laying out of the panels isn't very smart. Reproducible: Always Steps to Reproduce: 1. Plug an external monitor to your laptop 2. Add a panel with a task manager to the new screen 3. Move this panel to the small laptop's screen, and the panel from the laptop screen to the external monitor (this is sometimes necessary because when you disconnect the monitor, its panel is moved to the other screen, overlapping with the other one. After reconnecting the monitor, it's not always the case, that the overlapping panel is automatically moved back to the screen) Actual Results: Task manager on screen A shows only the tasks from screen B and vice versa. Expected Results: Task manager A showing tasks on screen A -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 329430] Description fields outputs html tags when used in Reports
https://bugs.kde.org/show_bug.cgi?id=329430 --- Comment #3 from Alvaro Soliverez <asolive...@kde.org> --- I don't think you understand. It's not that I intended to output html. Any new task that I create will output these tags, instead of a clean text. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359432] New: Plasma chashes when disconnecting wired connection from tray
https://bugs.kde.org/show_bug.cgi?id=359432 Bug ID: 359432 Summary: Plasma chashes when disconnecting wired connection from tray Product: plasmashell Version: 5.4.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kort...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.2) Qt Version: 5.4.2 Operating System: Linux 4.2.0-27-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Connecting to a different wired connection. I have two different wird connections and switch among them from time to time. In several occasions when switching back to the main connections makes Plasma crash. The crash can be reproduced sometimes. -- 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 0x7f87c67ff800 (LWP 16359))] Thread 7 (Thread 0x7f87ab5ef700 (LWP 16365)): #0 0x7f87c174b369 in QElapsedTimer::isMonotonic () at tools/qelapsedtimer_unix.cpp:150 #1 0x7f87c18cf22e in QTimerInfoList::repairTimersIfNeeded (this=0x7f87a4002ed0) at kernel/qtimerinfo_unix.cpp:155 #2 0x7f87c18cf2a3 in QTimerInfoList::timerWait (this=0x7f87a4002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:380 #3 0x7f87c18d067e in timerSourcePrepareHelper (timeout=0x7f87ab5eebe4, src=) at kernel/qeventdispatcher_glib.cpp:127 #4 timerSourcePrepare (source=, timeout=0x7f87ab5eebe4) at kernel/qeventdispatcher_glib.cpp:160 #5 0x7f87bdd5377d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f87bdd5411b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f87bdd542fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f87c18d129b in QEventDispatcherGlib::processEvents (this=0x7f87a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #9 0x7f87c187775a in QEventLoop::exec (this=this@entry=0x7f87ab5eeda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #10 0x7f87c16953d4 in QThread::exec (this=) at thread/qthread.cpp:503 #11 0x7f87c3ebdf85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7f87c169a2be in QThreadPrivate::start (arg=0x1a51740) at thread/qthread_unix.cpp:337 #13 0x7f87c07896aa in start_thread (arg=0x7f87ab5ef700) at pthread_create.c:333 #14 0x7f87c0fb2eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f87a0207700 (LWP 16366)): #0 0x7ffd491bf949 in ?? () #1 0x7ffd491bfc75 in clock_gettime () #2 0x7f87c0fc138d in __GI___clock_gettime (clock_id=, tp=tp@entry=0x7f87a0206b10) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7f87c174b3a6 in qt_clock_gettime (ts=0x7f87a0206b10, clock=) at tools/qelapsedtimer_unix.cpp:105 #4 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:161 #5 qt_gettime () at tools/qelapsedtimer_unix.cpp:170 #6 0x7f87c18ced29 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f8798002cd0) at kernel/qtimerinfo_unix.cpp:84 #7 0x7f87c18cf295 in QTimerInfoList::timerWait (this=0x7f8798002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:379 #8 0x7f87c18d067e in timerSourcePrepareHelper (timeout=0x7f87a0206be4, src=) at kernel/qeventdispatcher_glib.cpp:127 #9 timerSourcePrepare (source=, timeout=0x7f87a0206be4) at kernel/qeventdispatcher_glib.cpp:160 #10 0x7f87bdd5377d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f87bdd5411b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f87bdd542fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f87c18d129b in QEventDispatcherGlib::processEvents (this=0x7f87980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #14 0x7f87c187775a in QEventLoop::exec (this=this@entry=0x7f87a0206da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #15 0x7f87c16953d4 in QThread::exec (this=) at thread/qthread.cpp:503 #16 0x7f87c3ebdf85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7f87c169a2be in QThreadPrivate::start (arg=0x1d93370) at thread/qthread_unix.cpp:337 #18 0x7f87c07896aa in start_thread (arg=0x7f87a0207700) at pthread_create.c:333 #19 0x7f87c0fb2eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f879da2e700 (LWP 16370)): #0 0x7f87bdd98884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f87bdd541a6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f87bdd542fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3
