[Bug 1225544] New: When on Battery Power, Installation Cannot Continue Even After Plugging in Laptop
https://bugzilla.suse.com/show_bug.cgi?id=1225544 Bug ID: 1225544 Summary: When on Battery Power, Installation Cannot Continue Even After Plugging in Laptop Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown@suse.com Reporter: sm@eisoft.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- If I start a new Aeon installation with my laptop unplugged and running on battery power, the installer correctly tells me that I need to be plugged into power before proceeding. However, even after plugging my laptop into a power source the aforementioned message cannot be dismissed. Software: openSUSE Aeon RC2 Hardware: Lenovo Thinkpad X1 Carbon 6th Intel Core i7 16GB Memory 1.0TB HD Steps to Reproduce: Start a fresh installation of Aeon via bootable USB while laptop is not connected to power. A message will appear saying that the installation cannot continue while on battery power. Plug laptop into power. Message will not be dismissed and clicking "ok" will result in message reappearing over and over again. Workaround: Make sure laptop is plugged in before starting an Aeon installation. ¯\_(ツ)_/¯ -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225544 Shaun McDonnell <sm@eisoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sm@eisoft.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225544 https://bugzilla.suse.com/show_bug.cgi?id=1225544#c1 --- Comment #1 from Richard Brown <rbrown@suse.com> --- Sounds weird compared to what I tested...but next time I'm doing a test install I'll give this a kicking to confirm your observations are recurrent Thanks for the bug report :) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225544 https://bugzilla.suse.com/show_bug.cgi?id=1225544#c2 Richard Brown <rbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sm@eisoft.com) --- Comment #2 from Richard Brown <rbrown@suse.com> --- I'm tempted to put this down to a kernel/firmware bug with the X1 Carbon on my Dell 5510 I'm able to recreate the following scenario. Boot with AC plugged in - Tik starts - Remove AC power - Click OK on Welcome Screen - AC Power Adapter warning appears - Plug in AC power - Click Ok on AC Power Required screen - Installation continues So this categorically suggests that the tik code is present, correct, and accurate HOWEVER, I'm also able to find an unrelated fun bug on the same Dell 5510 Boot with AC disconnected - tik starts - Click OK on Welcome Screen - Install continues Because the AC wasn't connected on boot the kernel/firmware never established the device nodes we use to calculate if the AC adapter is plugged in..nor does it get restablished when it's plugged in later So..yeah.. today I learned AC power status in the kernel is weird and buggy.. I like the fact tik at least TRIES to warn users.. but I don't think we can really improve much here if the info we're getting from the hardware is bonkers. Any objection to me closing this as WONTFIX? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225544 Ray Yip <ryip10@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ryip10@gmail.com Assignee|rbrown@suse.com |ryip10@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225544 https://bugzilla.suse.com/show_bug.cgi?id=1225544#c4 --- Comment #4 from Ray Yip <ryip10@gmail.com> --- I am working on an edit of that piece of code. Tik will now scan for the AC adapter and scan for a Battery charging/discharging state as well. The user will no longer be locked into that dialog and will only come as a recommendation to be plugged in to the user. This should cover most cases. Except for the weird outlier messed up Cmos battery giving wrong signals case. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225544 Ray Yip <ryip10@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225544 https://bugzilla.suse.com/show_bug.cgi?id=1225544#c5 --- Comment #5 from Ray Yip <ryip10@gmail.com> --- I made changes to Tik, Pull Request pending merge to main branch after review: https://github.com/sysrich/tik/pull/27 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225544 https://bugzilla.suse.com/show_bug.cgi?id=1225544#c6 --- Comment #6 from Ray Yip <ryip10@gmail.com> --- There was a bug in #27 pull request, as grep would automatically follow symlinks while using the '-R' flag. I have fixed this in pull request #31 https://github.com/sysrich/tik/pull/31 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225544 https://bugzilla.suse.com/show_bug.cgi?id=1225544#c8 Ray Yip <ryip10@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED --- Comment #8 from Ray Yip <ryip10@gmail.com> --- Fixed in tik pull request #31 https://github.com/sysrich/tik/pull/31 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com