Bugzilla – Bug 1201124
Update 2-july-2022 : tlp and tlp-rdw needed to be removed before update progressed
Last modified: 2022-07-28 06:37:29 UTC
This morning, i did a sudo zypper dup on my tumbleweed and it came up with errors saying that a profile package had a conflict. i then removed tlp and tlp-rdw and that solved the problem. do we need tlp packages installed now?
Created attachment 859974 [details] tlp packages
Created attachment 859975 [details] yast2 log 1
Created attachment 859976 [details] yast2 log 2
Same issue. #### YaST2 conflicts list - generated 2022-07-03 13:03:05 #### the to be installed tlp-1.5.0-1.1.noarch conflicts with 'power-profiles-daemon' provided by the installed power-profiles-daemon-0.11.1-1.2.x86_64 [ ] Following actions will be done: do not install tlp-1.5.0-1.1.noarch do not install tlp-rdw-1.5.0-1.1.noarch [x] deinstallation of power-profiles-daemon-0.11.1-1.2.x86_64 #### YaST2 conflicts list END ###
(In reply to Jonzn 4suse from comment #4) > Same issue. > > #### YaST2 conflicts list - generated 2022-07-03 13:03:05 #### > > the to be installed tlp-1.5.0-1.1.noarch conflicts with > 'power-profiles-daemon' provided by the installed > power-profiles-daemon-0.11.1-1.2.x86_64 > > [ ] Following actions will be done: > do not install tlp-1.5.0-1.1.noarch > do not install tlp-rdw-1.5.0-1.1.noarch > [x] deinstallation of power-profiles-daemon-0.11.1-1.2.x86_64 > > #### YaST2 conflicts list END ### FYI: https://bugzilla.suse.com/show_bug.cgi?id=1198549#c4.
(In reply to Jonzn 4suse from comment #4) > Same issue. > > #### YaST2 conflicts list - generated 2022-07-03 13:03:05 #### > > the to be installed tlp-1.5.0-1.1.noarch conflicts with > 'power-profiles-daemon' provided by the installed > power-profiles-daemon-0.11.1-1.2.x86_64 > > [ ] Following actions will be done: > do not install tlp-1.5.0-1.1.noarch > do not install tlp-rdw-1.5.0-1.1.noarch > [x] deinstallation of power-profiles-daemon-0.11.1-1.2.x86_64 > > #### YaST2 conflicts list END ### opensuse tumbleweed seems to run fine without tlp. i haven't noticed any problems yet
(In reply to John Shand from comment #6) > (In reply to Jonzn 4suse from comment #4) > > Same issue. > > > > #### YaST2 conflicts list - generated 2022-07-03 13:03:05 #### > > > > the to be installed tlp-1.5.0-1.1.noarch conflicts with > > 'power-profiles-daemon' provided by the installed > > power-profiles-daemon-0.11.1-1.2.x86_64 > > > > [ ] Following actions will be done: > > do not install tlp-1.5.0-1.1.noarch > > do not install tlp-rdw-1.5.0-1.1.noarch > > [x] deinstallation of power-profiles-daemon-0.11.1-1.2.x86_64 > > > > #### YaST2 conflicts list END ### > > opensuse tumbleweed seems to run fine without tlp. i haven't noticed any > problems yet But what about saving laptop battery power? Without tlp it is realy bad!
Is there any plan to fix this issue? Or any "official" workaround?
(In reply to Brutus from comment #8) > Is there any plan to fix this issue? Or any "official" workaround? +1 It would at least be good to confirm that removing tlp has no ill side effects.
Removing tlp decreases battery life on my machine. So I removed power-profiles-daemon.
(In reply to Alex from comment #10) > Removing tlp decreases battery life on my machine. So I removed > power-profiles-daemon. Can you also confirm that tlp (1.4) + power-profiles-daemon running gives even lower power consumption?
(In reply to Frank Krüger from comment #11) > Can you also confirm that tlp (1.4) + power-profiles-daemon running gives > even lower power consumption? To be honest, I don't know as I used 'Performance' power profile. I force-installed power-profiles-daemon along with tlp 1.5, but it looks like that only one of those can run at the same time. And this time battery life isn't as horrible. I have couple different laptops (HP with AMD Ahtlon 3050U, LG Gram with i5-10210U and ASUS with Celeron N4500) and I might test the battery life because right now I'm trusting feelings and estimated time and they are not precise. Problem is that I don't really know how do I test battery life.
Any update on this issue? This package is still conflicting on my side.