Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Battery symbol disappears after a while #402

Open
munzelthecat opened this issue Oct 5, 2024 · 11 comments
Open

Battery symbol disappears after a while #402

munzelthecat opened this issue Oct 5, 2024 · 11 comments

Comments

@munzelthecat
Copy link

munzelthecat commented Oct 5, 2024

Expected behaviour

Actual behaviour

On my Notebook, after a while the battery symbol in the bar disappears. a restart of mate-power-manager in the terminal is not possible.

Steps to reproduce the behaviour

Work with the notebook and wait.

MATE general version

Mate 1.26.2

Package version

mate-power-manager 1.26.1+mint1

Linux Distribution

Linux Mint 22 Mate

Link to bugreport of your Distribution (requirement)

https://termbin.com/xobh

@lukefromdc
Copy link
Member

If you open mate-system-monitor and go to the "processes" tab, you can see if mate-system-monitor is still running or not. If mte-power-manager does not show up in this list of processes, it has crashed, or maybe frozen.

Try running killall -9 mate-power-manager first, then mate-power-manager and if this does not bring back the battery icon, please post whatever text you get in the terminal window from the second command

@munzelthecat
Copy link
Author

Hello,

here are the messages after mate-power-manager

(mate-power-manager:3469): PowerManager-WARNING **: 18:23:52.231: Failed to get session for pid 3469: The name org.freedesktop.ConsoleKit was not provided by any .service files

(mate-power-manager:3469): PowerManager-WARNING **: 18:23:52.236: could not map keysym 1008ffa8 to keycode

@lukefromdc
Copy link
Member

lukefromdc commented Oct 14, 2024 via email

@munzelthecat
Copy link
Author

As long as the terminal remains open, the battery symbol will be visible. If the terminal is closed, it disappears.

@munzelthecat
Copy link
Author

munzelthecat commented Oct 15, 2024

It seems to be a problem where the hardware (of the battery?) could play a role, or there are two problems.

I noticed today that the battery symbol did not disappear, but the charge level did not change for a long time and the battery LED on the notebook began to flash (which remains so even after a shutdown). Also acpi -V showed the wrong charge level.
With
killall -9 mate-power-manager I ended the battery display and then ran
mate-power-manager. The error message then also appeared.

~$ mate-power-manager

(mate-power-manager:5036): PowerManager-WARNING **: 20:20:53.960: Failed to get session for pid 5036: The name org.freedesktop.ConsoleKit was not provided by any .service files

(mate-power-manager:5036): PowerManager-WARNING **: 20:20:53.965: could not map keysym 1008ffa8 to keycode

@lukefromdc
Copy link
Member

Wen running mate-power-manager from terminal, for the icon to disappear when the terminal i closed is the expected behavior, as closing the terminal also closes processes started from it that are holding the prompt.

If you run mate-power-manager & that will send the process to the background and let you keep the icon showing. If it disappears after a while again, restarted without the & keep the terminal window open, and post whatever text shows up when the icon disappears

@lukefromdc
Copy link
Member

If this is being caused by a hardware issue, that could mean nobody without the same hardware problem can duplicate it. Seems to me there is almost always something on a laptop whose makers only support Windows that doesn't work right or doesn't work at all in Linux. I've had two HP laptops in a row where the touchpad isn't detected at all so a separate mouse is required.

@munzelthecat
Copy link
Author

Maybe it is a hardware issue. With dmesg I could find this:

[ 1335.708554] mate-power-mana[2014]: segfault at 7265706c7a ip 0000785dcb3cacd8 sp 00007ffd331ceb88 error 4 in libgobject-2.0.so.0.8000.0[785dcb39d000+37000] likely on CPU 1 (core 0, socket 0)
[ 1335.708573] Code: 8d 15 8c 54 02 00 48 c1 e9 02 4c 8b 0c ca 4d 85 c9 74 07 41 f6 41 16 20 75 36 48 8b 38 48 81 ff fc 03 00 00 76 3c 48 83 e7 fc <f6> 47 16 10 74 05 4d 85 c9 75 4d 31 c0 c3 66 2e 0f 1f 84 00 00 00

@munzelthecat
Copy link
Author

I would like to add something else. I now have the third battery in my notebook and it seems to be working smoothly with this one. Thank you very much for your thoughts.

Best regards
Munzelthecat

@bet5y
Copy link

bet5y commented Oct 28, 2024

crash.tar.gz

This has just happened to me - one minute the battery symbol was there, the next it had gone. Hopefully the following and the attached will be of assistance.

https://termbin.com/euey

It is a regular occurrence on my laptop.

https://termbin.com/9b9s

Addendum. It has happened again. I installed the 'Brightness Applet' to the panel following the error. It previously worked, now it shows the message 'Cannot connect to the mate-power-manager' when the mouse is hovered over it. Also, my laptop was plugged in when the failure occurred. I have set my laptop to display the LED keyboard lights whilst it is plugged in, and turn them off when it is not plugged in. The lights stayed on when I unplugged the laptop.

[code] System: Kernel: 6.8.0-47-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 clocksource: tsc Desktop: MATE v: 1.26.2 wm: marco v: 1.26.2 with: mate-panel,plank tools: mate-screensaver dm: LightDM v: 1.30.0 Distro: Linux Mint 22 Wilma base: Ubuntu 24.04 noble Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X513UA_M513UA v: 1.0 serial: <superuser required> Mobo: ASUSTeK model: X513UA v: 1.0 serial: <superuser required> uuid: <superuser required> UEFI: American Megatrends LLC. v: X513UA.312 date: 04/26/2022 Battery: ID-1: BAT0 charge: 21.6 Wh (71.1%) condition: 30.4/42.1 Wh (72.3%) power: 22.5 W volts: 11.8 min: 11.8 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: charging cycles: 876 CPU: Info: 6-core model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64 type: MT MCP smt: enabled arch: Zen 2 rev: 1 cache: L1: 384 KiB L2: 3 MiB L3: 8 MiB Speed (MHz): avg: 1812 high: 4043 min/max: 400/4056 cores: 1: 1842 2: 1797 3: 1797 4: 1796 5: 400 6: 4043 7: 1394 8: 2587 9: 3903 10: 400 11: 1396 12: 400 bogomips: 50307 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Lucienne vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c class-ID: 0300 temp: 45.0 C Device-2: Quanta USB2.0 HD UVC WebCam driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-3:3 chip-ID: 0408:30d4 class-ID: 0e02 serial: <filter> Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 compositors: 1: Compton v: 1 2: marco v: 1.26.2 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93") Monitor-1: eDP-1 mapped: eDP model: Samsung 0x4161 res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") modes: max: 1920x1080 min: 640x480 API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi inactive: gbm,wayland API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.9-0ubuntu0.2 glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir LLVM 17.0.6 DRM 3.57 6.8.0-47-generic) device-ID: 1002:164c Audio: Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:1637 class-ID: 0403 Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: ASUSTeK driver: N/A pcie: speed: 8 GT/s lanes: 16 bus-ID: 03:00.5 chip-ID: 1022:15e2 class-ID: 0480 Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 03:00.6 chip-ID: 1022:15e3 class-ID: 0403 API: ALSA v: k6.8.0-47-generic status: kernel-api Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin Network: Device-1: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:2725 class-ID: 0280 IF: wlp1s0 state: up mac: <filter> Bluetooth: Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-4:3 chip-ID: 0bda:8771 class-ID: e001 serial: <filter> Report: hciconfig ID: hci1 rfk-id: 5 state: up address: <filter> bt-v: 5.1 lmp-v: 10 sub-v: d922 hci-v: 10 rev: dfc6 class-ID: 6c010c Device-2: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-2:2 chip-ID: 8087:0032 class-ID: e001 Report: ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 5.3 lmp-v: 12 sub-v: 363c hci-v: 12 rev: 363c class-ID: 6c010c Drives: Local Storage: total: 476.94 GiB used: 11.01 GiB (2.3%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLQ512HALU-00000 size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: FXV7101Q temp: 30.9 C scheme: GPT Partition: ID-1: / size: 109.45 GiB used: 1.19 GiB (1.1%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 487 MiB used: 6.1 MiB (1.3%) fs: vfat dev: /dev/nvme0n1p2 ID-3: /home size: 212.43 GiB used: 2.87 GiB (1.4%) fs: ext4 dev: /dev/nvme0n1p6 ID-4: /usr size: 136.45 GiB used: 6.95 GiB (5.1%) fs: ext4 dev: /dev/nvme0n1p5 Swap: ID-1: swap-1 type: partition size: 7.63 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p4 USB: Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Device-1: 1-3:2 info: USB Optical Mouse type: mouse driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s lanes: 1 power: 100mA chip-ID: 30fa:0400 class-ID: 0301 Device-2: 1-4:3 info: Realtek Bluetooth Radio type: bluetooth driver: btusb interfaces: 2 rev: 1.1 speed: 12 Mb/s lanes: 1 power: 500mA chip-ID: 0bda:8771 class-ID: e001 serial: <filter> Hub-2: 2-0:1 info: super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s lanes: 1 chip-ID: 1d6b:0003 class-ID: 0900 Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Device-1: 3-2:2 info: Intel AX210 Bluetooth type: bluetooth driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 100mA chip-ID: 8087:0032 class-ID: e001 Device-2: 3-3:3 info: Quanta USB2.0 HD UVC WebCam type: video driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s lanes: 1 power: 500mA chip-ID: 0408:30d4 class-ID: 0e02 serial: <filter> Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s lanes: 1 chip-ID: 1d6b:0003 class-ID: 0900 Sensors: System Temperatures: cpu: 53.1 C mobo: N/A gpu: amdgpu temp: 47.0 C Fan Speeds (rpm): cpu: 2300 Repos: Packages: pm: dpkg pkgs: 2016 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb https: //www.mirrorservice.org/sites/packages.linuxmint.com/packages wilma main upstream import backport 2: deb http: //archive.ubuntu.com/ubuntu noble main restricted universe multiverse 3: deb http: //archive.ubuntu.com/ubuntu noble-updates main restricted universe multiverse 4: deb http: //archive.ubuntu.com/ubuntu noble-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ noble-security main restricted universe multiverse Info: Memory: total: 8 GiB note: est. available: 7.15 GiB used: 2.6 GiB (36.4%) Processes: 396 Power: uptime: 40m states: freeze,mem,disk suspend: deep wakeups: 1 hibernate: platform Init: systemd v: 255 target: graphical (5) default: graphical Compilers: gcc: 13.2.0 Client: Unknown python3.12 client inxi: 3.3.34 [/code]

@bet5y
Copy link

bet5y commented Oct 31, 2024

Another crash:

https://termbin.com/3lr6

I ran the following as mentioned above after the above crash:

`colin@ASUS-LM22-Mate:$ mate-power-manager &
[1] 8264
colin@ASUS-LM22-Mate:
$
(mate-power-manager:8264): PowerManager-WARNING **: 00:21:31.395: Failed to get session for pid 8264: The name org.freedesktop.ConsoleKit was not provided by any .service files

(mate-power-manager:8264): PowerManager-WARNING **: 00:21:31.401: could not map keysym 1008ffa8 to keycode
`
I also ran the following:

`colin@ASUS-LM22-Mate:$ killall -9 mate-power-manager
colin@ASUS-LM22-Mate:
$ mate-power-manager

(mate-power-manager:8406): PowerManager-WARNING **: 00:23:26.162: Failed to get session for pid 8406: The name org.freedesktop.ConsoleKit was not provided by any .service files

(mate-power-manager:8406): PowerManager-WARNING **: 00:23:26.169: could not map keysym 1008ffa8 to keycode
`

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants