29th November 2022
I am on Ubuntu Studio 22.10 installed within the last week and I find the bug 
where the system is frozen when waking from sleep is still there.
As reported previously logs cannot be collected because no user input works.
I believe after all this time using Ubuntu I have to consider using another 
distro. I seriously regret having to consider this but because of the nature of 
what I use my computers for I need a system that still responds after sleeping 
or hibernating.
If I shutdown proper there is no problem.
I have not seen a solution to this posted.

Once again thank you to all the developers involved but, I cannot wait
any longer. I believe two years is more than a reasonable amount of time
to wait for any bug fix that affects the whole system operation.

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.

  system frozen after sleep

Status in Ubuntu MATE:
Status in acpid package in Ubuntu:
Status in linux package in Ubuntu:
Status in systemd package in Ubuntu:
Status in upower package in Ubuntu:

Bug description:
  Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC
  2022 x86_64 x86_64 x86_64 GNU/Linux

  This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly 
but, at that time it was only apparent when I was using video ripping software 
on separate laptops and only when the machines became idle once the ripping 
program had finished.
  I don't think this bug was ever fixed and so I'm returning to it because I 
left my laptop in sleep mode over meal time to come back to a frozen system. I 
was not using the video ripping program this time, just surfing the Net. No 
other program was open.

  I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has
  happened when using an old Dell 1530 laptop.

  I do not believe I am unique in having this bug as someone has a
  similar bug when they have minimised Google Chrome and their system
  had went to sleep. I was also using Chrome this time but, as I have
  already said I was having this happen using another program and not
  using Chrome.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to