First logout attempt does not terminate #254
Comments
|
Are you using the latest release, or the latest master branch?
…On Sun, Aug 4, 2024, 8:08 PM Batuhan Karaca ***@***.***> wrote:
*Describe the bug*
A clear and concise description of what the bug is. If the contents of the
subsections do not apply, simply replace the contents with N/A.
*version*
Please include the version Brightness Controller you are using.
*To Reproduce*
Steps to reproduce the behavior:
I assume (without proof) arch based systems require two logout attempts to
successfully logout in general. In other words, the first attempt cannot
terminate the process hence it fails. The second attempt works. In my
current arch based system (Artix) with KDE-plasma, in the first logout
attempt, KDE-workspace throws "logout canceled by brightness-controller".
Similarly my old system was Manjaro (arch based) with xfce4, which didn't
have such notifications but again two attempts were required in the same
manner.
*Expected behavior*
A clear and concise description of what you expected to happen.
A single logout attempt should be enough. Many apps such as browsers quit
when a corresponding logout/shutdown signal is received. I am not
knowledgeable about debian based systems
*Screenshots*
If applicable, add screenshots to help explain your problem.
*Desktop (please complete the following information):*
- OS: Linux 6.6.42-1-lts (Artix)
- DE: KDE Plasma 6.1.3
*Additional context*
Add any other context about the problem here. Typically, the output of xrandr
-q.
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 382mm x 214mm
2560x1440 120.05*+ 60.02
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
—
Reply to this email directly, view it on GitHub
<#254>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXL2XFKALTMI6UX5CUR6ILZP266XAVCNFSM6AAAAABL7IINO2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2DOMZVG4ZTANI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
I didn't understand what you meant. My exec in /usr/bin imports from a python package having the same tree structure as the master branch. But the files in /usr/bin are from releases branch. Contents of the init package give 2.3.6. |
How did you install it? |
|
https://aur.archlinux.org/packages/brightness-controller-git. I tried to use autostart scripts of kde. I also tried to kill it inside bash_logout |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A clear and concise description of what the bug is. If the contents of the subsections do not apply, simply replace the contents with N/A.
I assume when the process for the app is running, (without proof) arch based systems require two logout attempts to successfully logout in general. In other words, the first attempt cannot terminate the process hence it fails. The second attempt works. In my current arch based system (Artix) with KDE-plasma, in the first logout attempt, KDE-workspace throws "logout canceled by brightness-controller". Similarly my old system was Manjaro (arch based) with xfce4, which didn't have such notifications but again two attempts were required in the same manner.
version
2.3.6 (I checked the init file)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
A single logout attempt should be enough. Many apps such as browsers quit when a corresponding logout/shutdown signal is received. I am not knowledgeable about debian based systems
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here. Typically, the output of
xrandr -q.The text was updated successfully, but these errors were encountered: