[Discover] [Bug 415874] When session restoration is in use, Discover always gets launched after rebooting
https://bugs.kde.org/show_bug.cgi?id=415874 Tim Taylor changed: What|Removed |Added CC|tim.taylor+bugzilla.bugs.kd | |e@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 428072] New: Discover restarts automatically on reboot after it has been used to update system packages
https://bugs.kde.org/show_bug.cgi?id=428072
Bug ID: 428072
Summary: Discover restarts automatically on reboot after it has
been used to update system packages
Product: Discover
Version: 5.18.5
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: discover
Assignee: lei...@leinir.dk
Reporter: tim.taylor+bugzilla.bugs.kde@gmail.com
CC: aleix...@kde.org
Target Milestone: ---
SUMMARY
After updating system packages using Discover and closing Discover properly
after all packages have been updated, when I next reboot the system Discover
opens up automatically
STEPS TO REPRODUCE
1. Wait until Discover says that some package updates are available
2. Update the packages in Discover ("Update all")
3. When the updates are finished, close Discover
4. Reboot the system
OBSERVED RESULT
Discover opens up automatically even though it was closed down before the
reboot
EXPECTED RESULT
Discover should not open automatically after a reboot (and usually does not
unless I follow the steps outlined above)
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Kubuntu 20.04
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 Tim Taylor changed: What|Removed |Added CC|tim.taylor+bugzilla.bugs.kd | |e@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383769] New: Plasma crash when switching to a second monitor
https://bugs.kde.org/show_bug.cgi?id=383769 Bug ID: 383769 Summary: Plasma crash when switching to a second monitor Product: plasmashell Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: tim.taylor+bugzilla.bugs.kde@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.4) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-32-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: Had just turned on my laptop and plasma had launched. Then plugged in a second monitor via VGA cable, and closed laptop lid so that the other monitor became the only active screen. Then got the Plasma crash message -- 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 0x7ff4e6e82280 (LWP 1976))] Thread 7 (Thread 0x7ff419f79700 (LWP 2773)): #0 0x7ff4db6f5ef4 in g_mutex_unlock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff4db6b0696 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff4e13800bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7ff4e1329bea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff4e1157f83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff41c4965c7 in KCupsConnection::run() () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #6 0x7ff4e115cc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ff4d6da in start_thread (arg=0x7ff419f79700) at pthread_create.c:456 #8 0x7ff4e0a69d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 6 (Thread 0x7ff42e292700 (LWP 2674)): #0 0x7ff4e0a5dd8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7ff4db6b0576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff4db6b068c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff4e13800bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff4e1329bea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff4e1157f83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff4e4ba34c6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7ff4e115cc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff4d6da in start_thread (arg=0x7ff42e292700) at pthread_create.c:456 #9 0x7ff4e0a69d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7ff4c0fa1700 (LWP 2380)): #0 0x7ff4e0005510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7ff4e680d2c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7ff4e680d309 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7ff4d6da in start_thread (arg=0x7ff4c0fa1700) at pthread_create.c:456 #4 0x7ff4e0a69d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7ff4c2fa1700 (LWP 2376)): #0 0x7ff4e0a5dd8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7ff4db6b0576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff4db6b068c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff4e13800bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff4e1329bea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff4e1157f83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff4e401cdf5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7ff4e115cc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff4d6da in start_thread (arg=0x7ff4c2fa1700) at pthread_create.c:456 #9 0x7ff4e0a69d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7ff4c8f7c700 (LWP 2145)): #0 0x7ff4db6f5ed9 in g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff4db6b00f6 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff4db6b05e0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff4db6b068c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff4e13800bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff4e1329bea in QEventLoop::exec(QFlags) () at
[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 --- Comment #17 from Tim Taylor <tim.taylor+bugzilla.bugs.kde@gmail.com> --- I still have this problem with Kubuntu 17.04, running KDE Frameworks 5.31.0 and Plasma 5.9.4 :-( -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365
--- Comment #12 from Tim Taylor <tim.taylor+bugzilla.bugs.kde@gmail.com> ---
I still have this problem with Kubuntu 16.10.
As an interim measure I've written a little script that will report the key
battery stats:
---
#!/bin/bash
upower -i /org/freedesktop/UPower/devices/battery_BAT0 | gawk
'/percentage|state|time/ {print}'
---
--
You are receiving this mail because:
You are watching all bug changes.
[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 Tim Taylor <tim.taylor+bugzilla.bugs.kde@gmail.com> changed: What|Removed |Added CC||tim.taylor+bugzilla.bugs.kd ||e@gmail.com --- Comment #5 from Tim Taylor <tim.taylor+bugzilla.bugs.kde@gmail.com> --- I also have this issue on my HP ProBook 5320m running Kubuntu 16.04. I didn't notice it when running 15.10. In addition to the low level tools successfully reading the battery status, the KDE login screen also shows the battery status correctly. But when I log in, sometimes (not always) the system tray says no battery found. But then if I log out, the login screen still shows the correct battery info again. The system tray monitor is obviously doing something different to the login screen - the latter works reliably but the former does not. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 343313] kate, kwrite Checking Spelling doesn't works.
https://bugs.kde.org/show_bug.cgi?id=343313 Tim Taylor <tim.taylor+bugzilla.bugs.kde@gmail.com> changed: What|Removed |Added CC||tim.taylor+bugzilla.bugs.kd ||e@gmail.com --- Comment #22 from Tim Taylor <tim.taylor+bugzilla.bugs.kde@gmail.com> --- (In reply to Alex from comment #21) > For me it was a font issue. Automatic spellchecking (English) works just > fine with the DejaVu font, but not with the Hack font. Manual checking works > with any font. > > Arch > Kate 16.04 / Kile Git > Frameworks 5.21 > Qt 5.6 Thank you so much for that info, Alex! I have been suffering from lack of spellcheck highlighting in Kate since Kate 15.10 and continuing into 16.04 (I'm using Kubuntu). I had set my default system font to Liberation Sans, and that turned out to be the cause of no spellcheck highlighting in Kate. I've now set my default font in Kate to Noto Mono, and highlighting works again. Really glad to have got this annoying problem fixed at last! -- You are receiving this mail because: You are watching all bug changes.
