[kalarm] [Bug 486187] New: cant activate rtc wakeup
https://bugs.kde.org/show_bug.cgi?id=486187
Bug ID: 486187
Summary: cant activate rtc wakeup
Classification: Applications
Product: kalarm
Version: 3.8.1
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: djar...@kde.org
Reporter: dz.wb...@gmail.com
Target Milestone: ---
SUMMARY:
when trying to make an rtc wake-up it does not set it. this is what i get in
terminal:
org.kde.pim.kalarm: Kernel alarm timers not available (no CAP_WAKE_ALARM
capability)
kf.i18n.kuit: "Tag 'b' is not defined in message
{<__kuit_internal_top__>This wakeup will cancel any existing wakeup which
h...}."
Warning from helper: QProcess: Destroyed while process ("/usr/bin/rtcwake") is
still running.
my pc have the rtc option, if i set it manually it works:
echo Setting rtclock; echo "sudopass HERE" | sudo -S rtcwake -m no -l -t $(date
+%s -d 'today 1610')
to show the current wakeup time:
echo "sudopass HERE" | sudo -S rtcwake -m show -l -v |rg alarm: | cut -c 8-30
but with Kalarm it does not work.
STEPS TO REPRODUCE
1. new alarm
2. highlight the alarm
3. actions > wake from suspend
4. use highlighted alarm
OBSERVED RESULT
no rtc wakeup is programmed when clicking "use highlighted alarm"
EXPECTED RESULT
a wakeup program
SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.9.0-rc4-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz
Memory: 11,6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: Dell Inc.
Product Name: Latitude 7480
--
You are receiving this mail because:
You are watching all bug changes.
[konqueror] [Bug 484437] white page shown before opening pages
https://bugs.kde.org/show_bug.cgi?id=484437 --- Comment #8 from zak --- thank you. I'm using manjaro testing branch, when they update konqueror to the latest version i will test it and tell you if the problem is fixed with me. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 484437] white page shown before opening pages
https://bugs.kde.org/show_bug.cgi?id=484437 --- Comment #4 from zak --- (In reply to Stefano Crocco from comment #3) > Unfortunately, the changes I made to make the white flash disappear had > several unwanted consequences, so I'll have to remove or at least refine > them. However, I'd like to better understand something: when you say you use > a dark theme in Konqueror, do you mean you set a custom stylesheet (using > the appearance page in Konqueror configuration dialog) or that you chose a > dark colour theme for your desktop environment? In my tests, using a dark > desktop theme doesn't have any effect on the colour of web pages: page > background is still white and text is still black. "do you mean you set a custom stylesheet" yes, that's what i mean. a dark background and a white text color. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 484437] New: white page shown before opening pages
https://bugs.kde.org/show_bug.cgi?id=484437 Bug ID: 484437 Summary: white page shown before opening pages Classification: Applications Product: konqueror Version: 24.02.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: dz.wb...@gmail.com Target Milestone: --- i'm using a dark theme in konqueror: white text ob black background when i open a new windows or links the page blinks for less than a secons: it showns first a white page then the black one. i ope that you can fix this. this causes me eye stain -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479716] disable temporel dithering
https://bugs.kde.org/show_bug.cgi?id=479716 --- Comment #2 from zak --- an explanation of temporal dithering can be found here: https://wiki.ledstrain.org/docs/known-problems/problems_monitors_laptops/ this is a script to disable it: https://github.com/PrincessDoreena/kwin-effect-limitcolors -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480299] ctrl + e = open the current instance and not a new one
https://bugs.kde.org/show_bug.cgi?id=480299 --- Comment #2 from zak --- "this is a design choice" so is there a way to change it in kde plasma? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480299] New: ctrl + e = open the current instance and not a new one
https://bugs.kde.org/show_bug.cgi?id=480299 Bug ID: 480299 Summary: ctrl + e = open the current instance and not a new one Classification: Applications Product: dolphin Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dz.wb...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- i hope that you make the ctrl + e = open the current instance and not a new one -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 479716] New: disable temporel dithering
https://bugs.kde.org/show_bug.cgi?id=479716 Bug ID: 479716 Summary: disable temporel dithering Classification: Plasma Product: Active Window Control Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: dz.wb...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- i hope that you add the option to disable temporal dithering from the settings in the plasma -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 479286] New: replace font
https://bugs.kde.org/show_bug.cgi?id=479286 Bug ID: 479286 Summary: replace font Classification: Applications Product: kfontview Version: 5.27.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dz.wb...@gmail.com Target Milestone: --- when i have an edited font file and i want to replace the old one with the new one there is no option to update it. i find the install button ins greyed so i need to remove the fond and re install it i hope that there is a direct way to do that -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 476610] kfontview not shown in: open with other application software list
https://bugs.kde.org/show_bug.cgi?id=476610 zak changed: What|Removed |Added CC||dz.wb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 476610] New: kfontview not shown in: open with other application software list
https://bugs.kde.org/show_bug.cgi?id=476610 Bug ID: 476610 Summary: kfontview not shown in: open with other application software list Classification: Applications Product: kfontview Version: 5.27.8 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dz.wb...@gmail.com Target Milestone: --- SUMMARY *** kfontview not shown in: open with other application software list -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 476609] suggestion to add font information in the font viewer
https://bugs.kde.org/show_bug.cgi?id=476609 zak changed: What|Removed |Added CC||dz.wb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 476609] New: suggestion to add font information in the font viewer
https://bugs.kde.org/show_bug.cgi?id=476609 Bug ID: 476609 Summary: suggestion to add font information in the font viewer Classification: Applications Product: kfontview Version: 5.27.8 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dz.wb...@gmail.com Target Milestone: --- SUMMARY *** i hope that you add the option to see the font information like the version and the author in the viewer like gnome font viewer -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 470488] KDE Connect daemon crashes when receiving the attached image from my Android device
https://bugs.kde.org/show_bug.cgi?id=470488 --- Comment #1 from Zak --- *** Bug 470487 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 470487] KDE Connect daemon crashes when receiving a specific jpeg image from my Android device
https://bugs.kde.org/show_bug.cgi?id=470487 Zak changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Zak --- DrKonqi hung rather than indicating that this bug report was successfully filed. I'm closing it as a dupe of #470488, which contains more information. *** This bug has been marked as a duplicate of bug 470488 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 470488] New: KDE Connect daemon crashes when receiving the attached image from my Android device
https://bugs.kde.org/show_bug.cgi?id=470488
Bug ID: 470488
Summary: KDE Connect daemon crashes when receiving the attached
image from my Android device
Classification: Applications
Product: kdeconnect
Version: 23.04.1
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: zak.wil...@gmail.com
CC: andrew.g.r.hol...@gmail.com
Target Milestone: ---
Created attachment 159368
--> https://bugs.kde.org/attachment.cgi?id=159368=edit
Photograph taken with my Android device
SUMMARY
***
Sending this image from my Android device to my PC via KDE Connect causes KDE
Connect daemon to crash. This happens whether the file is sent individually or
in a batch, and whether the transfer is initiated inside the KDE Connect
Android app or via the share menu of another app.
***
STEPS TO REPRODUCE
1. Send the attached file from an Android device to a PC using KDE Connect
OBSERVED RESULT
KDE Connect daemon crashes
EXPECTED RESULT
KDE Connect saves the file to the configured directory and does not crash
SOFTWARE/OS VERSIONS
Linux: 6.3.4-arch1-1 (64-bit)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
ADDITIONAL INFORMATION
Backtrace inline:
Application: KDE Connect Daemon (kdeconnectd), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f2a9da9f2d3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f2a9da4fa08 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f2a9da38538 in __GI_abort () at abort.c:79
#10 0x7f2a9e0a0098 in qt_message_fatal (message=...,
context=) at global/qlogging.cpp:1914
#11 QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7f2a76a80610, msg=msg@entry=0x7f2a9f86e108 "Fatal Error: Got
cmd %d, while waiting for an answer!") at global/qlogging.cpp:893
#12 0x7f2a9f788090 in KIO::SlaveBase::waitForAnswer(int, int, QByteArray&,
int*) (this=this@entry=0x7f2a4c0012e0, expected1=expected1@entry=84,
expected2=expected2@entry=65, data=..., pCmd=pCmd@entry=0x7f2a76a80684) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1149
#13 0x7f2a9f7c8c06 in KIO::SlaveBase::canResume(unsigned long long)
(this=this@entry=0x7f2a4c0012e0, offset=65536) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1116
#14 0x7f2a76a90ec0 in FileProtocol::put(QUrl const&, int,
QFlags) (this=0x7f2a4c0012d0, url=, _mode=-1,
_flags=...) at /usr/src/debug/kio/kio-5.106.0/src/ioslaves/file/file.cpp:550
#15 0x7f2a9f7c8105 in KIO::SlaveBase::dispatch(int, QByteArray const&)
(this=0x7f2a4c0012e0, command=68, data=...) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1289
#16 0x7f2a9f7c02ae in KIO::SlaveBase::dispatchLoop() (this=0x7f2a4c0012e0)
at /usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:342
#17 0x7f2a9f83f0b7 in KIO::WorkerThread::run() (this=0x55b37e881c30) at
/usr/src/debug/kio/kio-5.106.0/src/core/workerthread.cpp:62
#18 0x7f2a9e0f30da in operator() (__closure=) at
thread/qthread_unix.cpp:350
#19 (anonymous
namespace)::terminate_on_exception >
(t=) at thread/qthread_unix.cpp:287
#20 QThreadPrivate::start(void*) (arg=0x55b37e881c30) at
thread/qthread_unix.cpp:310
#21 0x7f2a9da9d44b in start_thread (arg=) at
pthread_create.c:444
#22 0x7f2a9db20e40 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thread 8 (Thread 0x7f2a7dffb6c0 (LWP 373600) "kdeconnectd"):
#1 __pselect (nfds=5, readfds=0x7f2a7dff2a20, writefds=0x0, exceptfds=0x0,
timeout=, sigmask=) at
../sysdeps/unix/sysv/linux/pselect.c:56
#2 0x7f2a99ab06f9 in () at /usr/lib/libusbmuxd-2.0.so.6
#3 0x7f2a99ab13cc in () at /usr/lib/libusbmuxd-2.0.so.6
#4 0x7f2a9da9d44b in start_thread (arg=) at
pthread_create.c:444
#5 0x7f2a9db20e40 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thread 7 (Thread 0x7f2a7e7fc6c0 (LWP 373560) "Qt bearer threa"):
#1 __GI___libc_read (fd=15, buf=buf@entry=0x7f2a7e7fb840,
nbytes=nbytes@entry=8) at ../sysdeps/unix/sysv/linux/read.c:24
#2 0x7f2a9c765560 in read (__nbytes=8, __buf=0x7f2a7e7fb840,
__fd=, __fd=, __buf=,
__nbytes=) at /usr/include/bits/unistd.h:38
#3 g_wakeup_acknowledge (wakeup=) at ../glib/glib/gwakeup.c:216
#4 g_wakeup_acknowledge (wakeup=0x7f2a64000df0) at ../glib/glib/gwakeup.c:208
#5 0x7f2a9c711094 in g_main_context_check (context=0x7f2a64000c30,
max_priority=2147483647, fds=0x7f2a640013f0, n_fds=1) at
../glib/glib/gmain.c:4021
#6 0x7f2a9c76d998 in g_main_context_iterate.isra.0
(context=context@entry=0x7f2a64000c30, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
[kdeconnect] [Bug 470487] New: KDE Connect daemon crashes when receiving a specific jpeg image from my Android device
https://bugs.kde.org/show_bug.cgi?id=470487
Bug ID: 470487
Summary: KDE Connect daemon crashes when receiving a specific
jpeg image from my Android device
Classification: Applications
Product: kdeconnect
Version: 23.04.1
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: zak.wil...@gmail.com
CC: andrew.g.r.hol...@gmail.com
Target Milestone: ---
Application: kdeconnectd (23.04.1)
Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.4-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 5.27.5 [KCrashBackend]
-- Information about the crash:
KDE connect daemon crashes when receiving a specific image. It does not crash
when receiving other files. This is true whether the image is sent as a single
file, or in a batch, and whether the transfer is initiated from within KDE
Connect on the Android device or the share menu of another app.
The crash can be reproduced every time.
-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7fc5e9c9f2d3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7fc5e9c4fa08 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7fc5e9c38538 in __GI_abort () at abort.c:79
#10 0x7fc5ea2a0098 in qt_message_fatal (message=...,
context=) at global/qlogging.cpp:1914
#11 QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7fc5a2215610, msg=msg@entry=0x7fc5eb9a1108 "Fatal Error: Got
cmd %d, while waiting for an answer!") at global/qlogging.cpp:893
#12 0x7fc5eb8bb090 in KIO::SlaveBase::waitForAnswer(int, int, QByteArray&,
int*) (this=this@entry=0x7fc5940012e0, expected1=expected1@entry=84,
expected2=expected2@entry=65, data=..., pCmd=pCmd@entry=0x7fc5a2215684) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1149
#13 0x7fc5eb8fbc06 in KIO::SlaveBase::canResume(unsigned long long)
(this=this@entry=0x7fc5940012e0, offset=65536) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1116
#14 0x7fc5a2a26ec0 in FileProtocol::put(QUrl const&, int,
QFlags) (this=0x7fc5940012d0, url=, _mode=-1,
_flags=...) at /usr/src/debug/kio/kio-5.106.0/src/ioslaves/file/file.cpp:550
#15 0x7fc5eb8fb105 in KIO::SlaveBase::dispatch(int, QByteArray const&)
(this=0x7fc5940012e0, command=68, data=...) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1289
#16 0x7fc5eb8f32ae in KIO::SlaveBase::dispatchLoop() (this=0x7fc5940012e0)
at /usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:342
#17 0x7fc5eb9720b7 in KIO::WorkerThread::run() (this=0x55bcdf18bb00) at
/usr/src/debug/kio/kio-5.106.0/src/core/workerthread.cpp:62
#18 0x7fc5ea2f30da in operator() (__closure=) at
thread/qthread_unix.cpp:350
#19 (anonymous
namespace)::terminate_on_exception >
(t=) at thread/qthread_unix.cpp:287
#20 QThreadPrivate::start(void*) (arg=0x55bcdf18bb00) at
thread/qthread_unix.cpp:310
#21 0x7fc5e9c9d44b in start_thread (arg=) at
pthread_create.c:444
#22 0x7fc5e9d20e40 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thread 8 (Thread 0x7fc5c9ffb6c0 (LWP 8860) "kdeconnectd"):
#1 __pselect (nfds=5, readfds=0x7fc5c9ff2a20, writefds=0x0, exceptfds=0x0,
timeout=, sigmask=) at
../sysdeps/unix/sysv/linux/pselect.c:56
#2 0x7fc5e5be36f9 in () at /usr/lib/libusbmuxd-2.0.so.6
#3 0x7fc5e5be43cc in () at /usr/lib/libusbmuxd-2.0.so.6
#4 0x7fc5e9c9d44b in start_thread (arg=) at
pthread_create.c:444
#5 0x7fc5e9d20e40 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thread 7 (Thread 0x7fc5ca7fc6c0 (LWP 2025) "Qt bearer threa"):
#1 0x7fc5e8910f8a in g_main_context_check (context=0x7fc5b8000c30,
max_priority=, fds=, n_fds=) at
../glib/glib/gmain.c:4103
#2 0x7fc5e896d998 in g_main_context_iterate.isra.0
(context=context@entry=0x7fc5b8000c30, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4273
#3 0x7fc5e890e032 in g_main_context_iteration (context=0x7fc5b8000c30,
may_block=1) at ../glib/glib/gmain.c:4343
#4 0x7fc5ea4e9f2f in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fc5b8000b70, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5 0x7fc5ea499824 in
QEventLoop::exec(QFlags) (this=0x7fc5ca7fbac0,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#6 0x7fc5ea2f6eb6 in QThread::exec() (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#7 0x7fc5ea2f30da in operator() (__closure=) at
thread/qthread_unix.cpp:350
#8 (anonymous
[Tokodon] [Bug 463892] Enhancement request: scale, rather than crop images in timeline view
https://bugs.kde.org/show_bug.cgi?id=463892 --- Comment #2 from Zak --- Tokodon's behavior does not match Mastodon's; Mastodon crops to 16:9 by default while Tokodon crops to a specific height, but the full width of the window, which results in a tiny sliver of the image being shown when the window is set large. Tokodon is also not honoring my preference to never crop images set in Mastodon. I don't like either cropping behavior, but if the thinking is to match what Mastodon does, Tokodon currently doesn't. Simply showing the image scaled to the width of the screen when the crop preference is eventually supported isn't ideal either, as that will lead to images taller than the viewport. Scaling based on the larger of window width and a percentage of hegiht would allow viewing the whole image in-line. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463892] New: Enhancement request: scale, rather than crop images in timeline view
https://bugs.kde.org/show_bug.cgi?id=463892 Bug ID: 463892 Summary: Enhancement request: scale, rather than crop images in timeline view Classification: Applications Product: Tokodon Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: zak.wil...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Tokodon crops images in timeline views to an arbitrary maximum height with no visual indication that they are cropped, or hint as to their real aspect ratio. For those of us who create and follow visual art, that's a pretty unpleasant experience. Scaling images would be better because the whole image is visible while still allowing a limit on vertical space. As a further enhancement, there could be a setting for the height limit. -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 390204] After latest update, Lenovo Yoga 910 brightness keys no longer do anything
https://bugs.kde.org/show_bug.cgi?id=390204 --- Comment #2 from Zak <zakkha...@gmail.com> --- Ope I found out what happened, somehow the shortcut got unassigned in the update process it seems. I changed it back to default settings (it was set to nothing) and now it works again -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 390204] After latest update, Lenovo Yoga 910 brightness keys no longer do anything
https://bugs.kde.org/show_bug.cgi?id=390204 Zak <zakkha...@gmail.com> changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 390204] After latest update, Lenovo Yoga 910 brightness keys no longer do anything
https://bugs.kde.org/show_bug.cgi?id=390204 --- Comment #1 from Zak <zakkha...@gmail.com> --- Oh, no idea if this is related but tapping the lock key and the switch output key produces the letters "l" and "p" respectively (but I have to press them twice to get them to do that?) -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 390204] New: After latest update, Lenovo Yoga 910 brightness keys no longer do anything
https://bugs.kde.org/show_bug.cgi?id=390204 Bug ID: 390204 Summary: After latest update, Lenovo Yoga 910 brightness keys no longer do anything Product: kxkb Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: zakkha...@gmail.com Target Milestone: --- As of the updates pushed just before Feb. 10, 2018 I can no longer use the brightness keys on my Lenovo Yoga 910 keyboard to adjust brightness. They do nothing. I must use the brightness slider in the power/battery icon in the tray. The brightness keys were working before the update so maybe it is a regression? Some config file got slightly messed up somewhere? On KDE Neon with Plasma 5.12 -- You are receiving this mail because: You are watching all bug changes.
