[kio-gdrive] [Bug 466726] New: kio-grive wrong space of gdrive displayed
https://bugs.kde.org/show_bug.cgi?id=466726 Bug ID: 466726 Summary: kio-grive wrong space of gdrive displayed Classification: Frameworks and Libraries Product: kio-gdrive Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: gradael...@protonmail.com Target Milestone: --- SUMMARY Kio-gdrive on Dolphin displays a wrong "disk usage" of the google drive. It happens only with non-personal drives (education/workspace drives), and it shows the total space of the organization (in my case, 100TB) instead of my personal space limit (3GB, forced by my organization some weeks ago). STEPS TO REPRODUCE 1. Add a non-personal (like education) drive to kio-gdrive 2. Open a folder in that drive with a file manager (in my case, dolphin) 3. Look at the disk usage OBSERVED RESULT It shows the total space of the organization (in my case, 100TB instead of 3GB) EXPECTED RESULT The disk usage is my personal disk usage and the total space is the limit of my personal drive space (like the result observed with personal google account) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Bookworm/Sid, Kernel 5.10.162, x86_64 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 478545] New: Keyboard doesn't write
https://bugs.kde.org/show_bug.cgi?id=478545 Bug ID: 478545 Summary: Keyboard doesn't write Classification: Applications Product: ktouch Version: 23.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sebastian.gottfr...@posteo.de Reporter: giacomol...@gmail.com Target Milestone: --- Open ktouch; first windows ask you for the Name, but the field doesn't take focus to input characters from keyboard. I'm using fedora silverblu 39 on VirtualBox 6.1 Keyboard is a common HP qwerty it keyboard. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 478545] Keyboard doesn't write
https://bugs.kde.org/show_bug.cgi?id=478545 Giacomo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Giacomo --- *** This bug has been marked as a duplicate of bug 473617 *** -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 473617] Cannot enter the name when i first launch the app
https://bugs.kde.org/show_bug.cgi?id=473617 Giacomo changed: What|Removed |Added CC||giacomol...@gmail.com --- Comment #9 from Giacomo --- *** Bug 478545 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 439407] New: Kdeconnect Pointer bug
https://bugs.kde.org/show_bug.cgi?id=439407
Bug ID: 439407
Summary: Kdeconnect Pointer bug
Product: kdeconnect
Version: unspecified
Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: gradael...@gmail.com
Target Milestone: ---
Application: kdeconnectd (1.4.0)
Qt Version: 5.12.8
Frameworks Version: 5.68.0
Operating System: Linux 5.4.0-77-generic x86_64
Windowing system: X11
Distribution: Linux Mint 20.1
-- Information about the crash:
- What I was doing when the application crashed:
I was trying to use my android device with kdeconnect as a pointer
("Telecomando della presentazione" in italian).
- Unusual behavior I noticed:
The crash can be reproduced every time.
-- Backtrace:
Application: Demone di KDE Connect (kdeconnectd), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f823e2b5900 (LWP 45731))]
Thread 14 (Thread 0x7f82057fa700 (LWP 45749)):
#0 0x7f823dfedaff in __GI___poll (fds=0x7f81e80029e0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7f823cc8a36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f823cc8a4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f823e596583 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x7f823e53d4db in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x7f823e375785 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x7f823854c1a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#7 0x7f823e3769d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x7f823d571609 in start_thread (arg=) at
pthread_create.c:477
#9 0x7f823dffa293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 13 (Thread 0x7f8205ffb700 (LWP 45747)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x55b156d6db08) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b156d6dab8,
cond=0x55b156d6dae0) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x55b156d6dae0, mutex=0x55b156d6dab8) at
pthread_cond_wait.c:647
#3 0x7f822afe3b1b in ?? () from
/opt/amdgpu/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4 0x7f822afe384b in ?? () from
/opt/amdgpu/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5 0x7f823d571609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f823dffa293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 12 (Thread 0x7f82067fc700 (LWP 45746)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x55b156d6db08) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b156d6dab8,
cond=0x55b156d6dae0) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x55b156d6dae0, mutex=0x55b156d6dab8) at
pthread_cond_wait.c:647
#3 0x7f822afe3b1b in ?? () from
/opt/amdgpu/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4 0x7f822afe384b in ?? () from
/opt/amdgpu/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5 0x7f823d571609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f823dffa293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 11 (Thread 0x7f8206ffd700 (LWP 45745)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x55b156d6d400) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b156d6d3b0,
cond=0x55b156d6d3d8) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x55b156d6d3d8, mutex=0x55b156d6d3b0) at
pthread_cond_wait.c:647
#3 0x7f822afe3b1b in ?? () from
/opt/amdgpu/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4 0x7f822afe384b in ?? () from
/opt/amdgpu/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5 0x7f823d571609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f823dffa293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 10 (Thread 0x7f82077fe700 (LWP 45744)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x55b156d6d400) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b156d6d3b0,
cond=0x55b156d6d3d8) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x55b156d6d3d8, mutex=0x55b156d6d3b0) at
pthread_cond_wait.c:647
#3 0x7f822afe3b1b in ?? () from
/opt/amdgpu/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4 0x7f822afe384b in ?? () from
/opt/amdgpu/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5 0x7f823d571609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f823dffa293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 9 (Thread 0x7f8
[korganizer] [Bug 462176] New: Korganizer crashed after applying status to an empty partecipant
https://bugs.kde.org/show_bug.cgi?id=462176 Bug ID: 462176 Summary: Korganizer crashed after applying status to an empty partecipant Classification: Applications Product: korganizer Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: gradael...@protonmail.com Target Milestone: --- Application: korganizer (5.15.3 (20.08.3)) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.10.0-19-amd64 x86_64 Windowing system: X11 Distribution: Debian GNU/Linux 11 (bullseye) -- Information about the crash: - What I was doing when the application crashed: I was setting the status of partecipant from KOrganizer (same with Kontact), and the name field was empty. It also doesn't save partecipants informations, but, at least, it doesn't crash in that case. - Custom settings of the application: Radicale server (without particular settings) on my local machine with some calendars. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault [KCrash Handler] #4 0x7f23c0830eda in QSortFilterProxyModel::parent(QModelIndex const&) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f23c07fdd70 in QPersistentModelIndex::parent() const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f23c0814000 in QItemSelection::merge(QItemSelection const&, QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f23c0814b9b in QItemSelectionModel::columnIntersectsSelection(int, QModelIndex const&) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f23c1597ed4 in QHeaderView::paintSection(QPainter*, QRect const&, int) const () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f23c15904ee in QHeaderView::paintEvent(QPaintEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f23c1363fae in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f23c140c42e in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f23c0861d33 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f23c132414e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f23c0861fca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f23c135c116 in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f23c135c962 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f23c135dcb3 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f23c135c67c in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f23c135dcb3 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f23c135dad2 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f23c135dad2 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f23c135c67c in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f23c135dcb3 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f23c135c67c in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f23c135dcb3 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f23c135c67c in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint
[korganizer] [Bug 462176] Korganizer crashed after applying status to an empty partecipant
https://bugs.kde.org/show_bug.cgi?id=462176 Giacomo changed: What|Removed |Added Version|unspecified |5.15.3 CC||gradael...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 492818] New: Subtasks not working properly
https://bugs.kde.org/show_bug.cgi?id=492818 Bug ID: 492818 Summary: Subtasks not working properly Classification: Applications Product: Merkuro Version: 24.08.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: fgiacom...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY STEPS TO REPRODUCE 1. Open Merkuro Calendar 2. Add a task 3. Right click on the new task 4. Click "create subtask" OBSERVED RESULT No window to create a new subtask is opened. From terminal it says "qrc:/IncidenceMouseArea.qml:96: TypeError: Property 'openNewSubTodoEditorDialog' of object IncidenceEditorManager_QMLTYPE_2(0x5efcf8ecc260) is not a function" EXPECTED RESULT Some menu to pop up and let me create the subtaks SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.10.8-arch1-1/6.1.4-1 KDE Plasma Version: KDE Frameworks Version: Qt Version: qt6 ADDITIONAL INFORMATION I'm not on kde plasma DE, I'm on hyprland wm with merkuro-calendar installed -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 492818] Subtasks not working properly
https://bugs.kde.org/show_bug.cgi?id=492818 Giacomo changed: What|Removed |Added CC||fgiacom...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 200017] Provide thumbnail preview support for epub, fb2, and the like using Okular generators
https://bugs.kde.org/show_bug.cgi?id=200017 Giacomo changed: What|Removed |Added CC||giacomo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 348059] In Windows 7 64 bit localisation doesn't work as expected
https://bugs.kde.org/show_bug.cgi?id=348059 --- Comment #3 from Giacomo --- Thank You very much, these are very good news to know. I'l giv it a try as soon as I can! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 Giacomo Venturini changed: What|Removed |Added CC||giacomo.venturi...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481308] screen locker blank-with-cursor [xorg]
https://bugs.kde.org/show_bug.cgi?id=481308 Giacomo Lozito changed: What|Removed |Added CC||giacomo.loz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481308] screen locker blank-with-cursor [xorg]
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #19 from Giacomo Lozito --- Can confirm on Arch Linux current on my laptop, upgraded this morning to plasma 6. No monitor attached, issue occurs on the laptop screen directly. As soon as I lock screen, either via application launcher or via keyboard shortcut, screen goes blank but I can see cursor if I move it, as per previous comments. I can type my password blindly and it unlocks screen and screen is visible again. Perhaps worth mentioning that I get the issue 19 times out of 20. Very rarely, the lock screen works as expected. Also /usr/lib/kscreenlocker_greet --testing always works fine. SOFTWARE/OS VERSIONS Linux: linux 6.7.8-arch1-1 KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Graphics Platform: X11 Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD Radeon Vega 10 Graphics Manufacturer: ASUSTeK COMPUTER INC. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481308] screen locker blank-with-cursor [xorg]
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #25 from Giacomo Lozito --- > Thanks everyone for chiming in with system configurations. Just to make > sure, the trick from the corresponding (now fixed) Wayland bug doesn't help > here, where you press Esc twice to make the display come back? (once to hide > the screen locker and properly turn off the screen, the second time to bring > it back) Not for me. If anything, it shows very odd behaviour. When I lock screen: - screen will be blank - first Esc keypress will cause screen to turn off - second Esc keypress will cause it to turn on again for a moment (but blank), and then the screen will turn off after a second - subsequente Esc keypresses will do the same (screen on for a second but blank, then turning off) - moving the mouse, unlike the Esc keypress, causes the screen to stay on (although still blank) In case it helps, this behaviour is somewhat reproducible with" kscreenlocker_greet --testing" too: - launching the testing screen will work fine (lock screen content is visible within a decorated window) - pressing Esc will cause the screen to turn off - a second Esc keypress will cause the screen to turn on again, but it will turn off on its own after a second - moving the mouse, unlike the Esc keypress, causes the he testing screen to stay on (with content visible) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #35 from Giacomo Lozito --- (In reply to Steven Noonan from comment #32) > Tried applying the patch in the powerdevil merge request and > rebuilt/installed poweredevil. From what I can tell it had no impact on > either the escape key behavior or the blank lock screen render. Same, patch does not seem to change behaviour. Also FWIW, I have turn off screen automatically after 5 mins in Energy Saving config, and allow unlocking without password for 15 seconds in Screen Locking config. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #38 from Giacomo Lozito --- (In reply to Jakob Petsovits from comment #37) > (In reply to Steven Noonan from comment #32) > > Tried applying the patch in the powerdevil merge request and > > rebuilt/installed poweredevil. From what I can tell it had no impact on > > either the escape key behavior or the blank lock screen render. > > (In reply to Giacomo Lozito from comment #35) > > Same, patch does not seem to change behaviour. Also FWIW, I have turn off > > screen automatically after 5 mins in Energy Saving config, and allow > > unlocking without password for 15 seconds in Screen Locking config. > > Thanks for testing, much appreciated. I'm unclear as to why the fix wouldn't > be working. Given that you have a built-from-souce setup, could you do two > more things to help out? > > 1. Please make sure that > $PREFIX/lib/plugins/powerdevil/action/powerdevil_dpmsaction.so was installed > in addition to the powerdevil binary itself. That's where the power > management service's screen turn-off logic (and the proposed fix) is located > in practice. > > 2. Please provide some of that new debug output that I added in the same > commit, to get a rough understanding of how your screen turns blank. On a > system with systemd, the easiest way to make the extra logs show up in > journalctl is: > > systemctl edit --user plasma-powerdevil.service > > and in the free space between the top two comment paragraphs, add this line: > > [Service] > Environment="QT_LOGGING_RULES=org.kde.powerdevil=true" > > The new logging entries all start with "org.kde.powerdevil: DPMS:", they > describe what idle timeouts are set for the action to trigger and when the > screen actually gets turned off. Please paste some of those logs here. If > that's an issue because the screen is blank, I've found that switching > between virtual terminals (e.g. Ctrl+Alt+F7 and back to the original one, > wherever it's located as per `loginctl list-sessions`) will restore the > screen to non-black. > > Thanks! Happy to test. For 1. I confirmed that /usr/lib/qt6/plugins/powerdevil/action/powerdevil_dpmsaction.so is included in the arch powerdevil package I patched and rebuilt. I also confirmed its md5sum being different before/after rebuild/reinstall to make sure it's been modified. For 2. I have enabled logging and I can see some of the logging lines in question, more precisely (filtering only the powerdevil: DPMS lines): Mar 09 17:00:20 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen lock activating) after 6ms Mar 09 17:00:22 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen unlocked) after 30ms Mar 09 17:00:39 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen lock activating) after 6ms Mar 09 17:00:43 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen unlocked) after 30ms Mar 09 17:01:23 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen unlocked) after 30ms Mar 09 17:01:20 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen lock activating) after 6ms Mar 09 17:02:13 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen lock activating) after 6ms Mar 09 17:02:25 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen unlocked) after 30ms for each of the 4 attempts, the first line (screen lock activating) pops up as soon as I activate screen lock using Meta+L. The screen unlocked one comes up as I blindly type my password to unlock screen. Worth mentioning that one of these 4 attempts was "successful" (like I mentioned before, rarely the screenlock screen will show as expected). I also tried to switch virtual terminal in the fourth attempt, which causes the screenlock screen to show correctly once switched back to, but does not seem to produce any additional log line of interest. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #39 from Giacomo Lozito --- Note: reading those log lines and looking at where those are located in the patch, the impression I get is that my timeout for turning off the screen (60 seconds) is not being honored. Instead, it immediately proceeds to turn off the screen. This would also explain why I pressing esc turns on the screen for a moment for me, and then turns it off again (because instead of waiting 60 seconds, it's doing the fast display turn off without waiting for timeout). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #41 from Giacomo Lozito --- > On that note, perhaps run a quick test with powerdevil stopped (i.e. > `systemctl stop --user plasma-powerdevil.service`) to confirm that the DPMS > action is actually responsible for this? Screen stays on with powerdevil > stopped and turns blank with powerdevil running, yes? Just done this test. The screen still goes blank as soon as I activate screen lock, even with powerdevil off, and obviously no powerdevil-related log lines appearing in journalctl. > If you're not seeing those, I have to wonder if perhaps some other component > is independently turning off the screen that's unrelated to PowerDevil. There is an important detail here, which I reported incorrectly in my previous message, sorry. When I activate the screen lock, the screen goes blank, but not off (meaning that I can still see the screen backlight on, and the mouse cursor is visible if I move it). If I then press Esc, it goes off. If I press it again, the screen turns on (with nothing displayed, but the backlight is on) for a moment, then back off. Based on logs, I think you are right on Powerdevil is not turning the screen off. But something is causing the screen lock not to be displayed (as if its window wasn't drawn?) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #43 from Giacomo Lozito --- (In reply to Jakob Petsovits from comment #42) > (In reply to Giacomo Lozito from comment #41) > > Based on logs, I think you are right on Powerdevil is not turning the screen > > off. But something is causing the screen lock not to be displayed (as if its > > window wasn't drawn?) > > Okay, so then we've got two different bugs on our hands. My patch from > https://invent.kde.org/plasma/powerdevil/-/merge_requests/332 should solve > one. We'll still have to figure out where the other one comes from. For my specific issue, I just made some progress. I tried changing the plasma style away from breeze to breeze light and now the screen lock consistently shows up when I lock screen. Once I switch plasma style back to breeze, I can reproduce the issue again. Switching away from breeze to breeze dark or oxygen also fixes it. I have tried deleting ~/.cache on the off chance this is caused by a cached copy of breeze, but does not seem to help. Anyway, even though this issue only manifests with the screen lock (and the symptoms are deceptively similar to what reported by others for powerdevil) my issue is unrelated with powerdevil. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483163] New: blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 Bug ID: 483163 Summary: blank screen on lock screen activation when using breeze plasma style Classification: Plasma Product: kscreenlocker Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: giacomo.loz...@protonmail.com Target Milestone: --- SUMMARY When activating lock screen (via shortcut, menu option or timer), the screen becomes blank. The screen is not turned off and maintains the backlight on, but nothing is drawn on screen. Cursor can be seen when moved, and password can be blindly typed to return into desktop, which becomes immediately visible again. Also, when the lock screen is blank like this, switching to another virtual terminal and returning to the lock screen vt will cause it to be displayed correctly. This behavior only occurs when Breeze is selected as plasma style, and it happens most of the time. Switching to Breeze Light, Breeze Dark or Oxygen will result in the lock screen being displayed correctly 100% of the time. Switching back to Breeze will cause the wrong behavior again. Please note that this bug is separate from https://bugs.kde.org/show_bug.cgi?id=481308 which is powerdevil-related and causes the screen to turn off. Energy settings make no difference for this issue, the screen is still on but blank. The difference to behaviour seems to be made by changing the plasma style. STEPS TO REPRODUCE 1. Use Breeze as plasma style 2. Activate lock screen using keyboard shortcut, launcher option or wait for it to be activated by inactivity 3. 19 times out of 20, the lock screen will be blank, even if the screen is turned on OBSERVED RESULT Blank screen, with the screen turned on. Moving cursor around makes it visible. EXPECTED RESULT Lock screen window correctly drawn. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD Radeon Vega 10 Graphics ADDITIONAL INFORMATION Speculation: one notable difference between Breeze and the other plasma styles (Breeze Light, Dark, etc.) is that Breeze is the only style that is designed to follow the user-chosen color scheme. So it is possible that color scheme implementation in plasma is playing a role into the issue. I have tried changing the color scheme (i.e., using the one from wallpaper or the default one) but changing the scheme itself makes no difference. The issue only seems to occur with the screen locker and I have not seen it anywhere else in plasma. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #49 from Giacomo Lozito --- (In reply to Jakob Petsovits from comment #44) > Not sure how best to deal with bug reports because ideally we'd have two > separate ones, but if the symptoms are indeed very similar then it'll be > difficult to tell them apart. Hopefully a large number of users will see > their setup fixed and the remaining ones can target the screen locker / > Plasma theme issue in a targeted way. I have created a separate bug report (https://bugs.kde.org/show_bug.cgi?id=483163) for the breeze style + kscreenlocker issue. Not an urgent one to fix imho as I can simply switch to Breeze Light for now to mitigate issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 Giacomo Lozito changed: What|Removed |Added CC||giacomo.lozito@protonmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 --- Comment #5 from Giacomo Lozito --- (In reply to Nate Graham from comment #1) > Does it happen on Wayland too, or only X11? It only occurs with X11 for me. Tested this evening with Wayland and Breeze plasma style, did not manage to reproduce; when activating the screen locker in wayland, the screen consistently behaves by going blank for a half second first, and then displaying the lock screen correctly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 --- Comment #10 from Giacomo Lozito --- (In reply to Nate Graham from comment #6) > Ah, this should have been fixed in Plasma 6.0.2, then. Can you test that and > re-open if it's still broken? Just tested on Arch with plasma 6.0.2 and it still occurs for me. I also confirmed same behaviour as reported initially: only occurs with plasma style set to Breeze and only on X11, switching to another plasma style such as Breeze Light will prevent the issue from occurring. Does not occur with Wayland. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 383071] New: Konqueror isn't able to open URLs on startup
https://bugs.kde.org/show_bug.cgi?id=383071 Bug ID: 383071 Summary: Konqueror isn't able to open URLs on startup Product: konqueror Version: 5.0.97 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: khtml Assignee: konq-b...@kde.org Reporter: manta...@gmail.com Target Milestone: --- Hi, if I try to run konqueror with an url parameter, say: $ konqueror 'http://www.kde.org' or if I set startup options as following: When Konqueror starts: Show my start page http://www.kde.org instead of loading the page on startup, konqueror opens a dialog asking how to open document (saying: "Type: HTML document"), with 4 buttons: "Save as...", "Open with firefox", "Open with", "Cancel". If I start Konqueror with an empty page (or with the default start page) and then type in the URL in the URL bar it loads the page without problems. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 383071] Konqueror isn't able to open URLs on startup
https://bugs.kde.org/show_bug.cgi?id=383071 --- Comment #2 from Giacomo Montagner --- The dialog appears with KHTML also. I have no "WebKit" choice in the settings, probably I'm missing some package? I'm using Fedora 26. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 363424] New: Kate does not save settings regarding extensions when closed
https://bugs.kde.org/show_bug.cgi?id=363424 Bug ID: 363424 Summary: Kate does not save settings regarding extensions when closed Product: kate Version: 5.0.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: giacomo.alze...@gmail.com On my system (Kubuntu 16.04 both with plasma 5.5 and plasma 5.6 installed via backports PPA) the Kate application has stopped saving settings. For example I go to settings, extensions and enable the konsole integration. I then close Kate and if I reopen it there's no terminal. I tried to create a new session, then change the settings and save the session but when reopening the session the extensions are gone. This didn't happen with kubuntu 15.10 but I experienced it from when I moved to kubuntu 16.04, both with the "standard" plasma 5.5 and even right now that I have upgraded to plasma 5.6.4 via kubuntu backports. Reproducible: Always Steps to Reproduce: 1. Launch Kate 2. Go to settings and enable an extension 3. close Kate 4. Reopen Kate Actual Results: The extension you have enabled is disabled again. Expected Results: The extension is enabled until you disable it explicitly via the settings. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 363424] Kate does not save settings regarding extensions when closed
https://bugs.kde.org/show_bug.cgi?id=363424 --- Comment #1 from Giacomo Alzetta --- I must add that even sessions aren't being properly saved. Sometimes Kate is able to save the session, however it always result in an empty session (0 open documents). And after closing Kate again sometimes all sessions and even recently opened documents are gone. -- You are receiving this mail because: You are watching all bug changes.
