I looked into some more things to get this solved.
While the Setting application says my power mode - the one it keeps
getting back too despizte I chose another is "balanced", looking into
the system it tells mie it's on powersafe:
$ cat /sys/devices/system/cpu/*/cpufreq/scaling_governor
Public bug reported:
In Jammy when I have Chrome running and I log out of a Wayland session
and then log back in and restart Chrome it says it wasn't shut down
correctly.
I'm pretty sure in earlier releases Chrome was given the opportunity to
shut down cleanly when I logged out, but :shrug: I
Hi,
Thanks for the response.
After removing extensions, logout/login and than lock screen:
- I see info about ethernet, wifi, bluetooth,battery, nightlight- I can
operate sound level and suspend computer
After putting back extensions dir, not enabling custom extensions,
logout/login and than lock
I logged out immediately after logging in again as described above, then
went to log in again and checked the options menu, and it correctly had
"Ubuntu on Xorg" selected as my session type, but when I finished
logging in I was in a Wayland session, not an Xorg session. So for some
reason my
Public bug reported:
On Jammy, I log out of a Wayland session, click my name on the login
screen, go down to the options menu and select Ubuntu on Xorg, enter my
password, get "Oh no! Something has gone wrong. A probleme has occurred
and the system can't recover. Please log out and try again.
maybe it is interesting that, before i got it working under wayland as I
want it to be, I reverted back for a while to xorg.
It was after I got the hints here to uninstall extensions, that I did
that, and only then got back to the wayland session.
I dont know why it should be, but it could also
** Summary changed:
- Power Mode keeps switching back to balanced afert performance is selected
manually
+ Power Mode keeps switching back to balanced after performance is selected
manually
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Changed in: php-defaults (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
demotion of pcre3 (8.x) a.k.a pcre
** Changed in: zsh (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
demotion of pcre3 (8.x) a.k.a pcre (without the 3) in
In reply to #56.
I can confirm Alt-TAB stops working when Thunderbird mis-behaves.
Normally it would show 1 more red (i.e. Window) dot than necessary.
But today it is showing 5 extra dots.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Bug watch added: Debian Bug tracker #18
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18
** Also affects: zsh (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Maybe related - but I had this thunderbird issue, too, but not anymore
since upgrading to 21.10.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1950925
Title:
alt-tab doesnt
It sounds like this might be specific to AppIndicator. Can you provide a
photo of the issue?
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
appindicator (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I come from
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328
For me, they look related.
Before using Thunderbird (or before it mis-behaves), Alt-TAB works.
When Thunderbird goes wrong, Alt-TAB stops working.
--
You received this bug notification because you are a member of
Sounds like you need the fix for bug 1943162, which is only in 22.04
(http://cdimage.ubuntu.com/daily-live/current/)
** Package changed: gnome-control-center (Ubuntu) => power-profiles-
daemon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
This may be caused by gnome-shell quietly crashing on logout.
Please:
1. Uninstall these extensions:
'mprisindicatorbut...@jasonlg1979.github.io',
'bat...@martin.zurowietz.de', 'multi-volume@tigersoldier',
'allowlockedremotedesk...@kamens.us'
2. Log in again and verify the bug still occurs.
3.
Sounds like bug 1952457 but we should figure out the root cause of this
bug separately.
Please:
1. Uninstall these extensions:
'mprisindicatorbut...@jasonlg1979.github.io',
'bat...@martin.zurowietz.de', 'multi-volume@tigersoldier',
'allowlockedremotedesk...@kamens.us'
2. Log in again and verify
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
You have been subscribed to a public bug:
have to reboot if choosing Ubuntu on xorg results in loading of Ubuntu
(wayland) - reboot allows xorg to be used. Logging out/in does not load
X even though it was chosen
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu1
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1952515
Title:
QA Test Ubuntu 22.04 Gnome-shell Crashed
To
Thanks for the bug report.
Please:
1. Reboot.
2. Log in and reproduce the bug.
3. Run:
journalctl -b0 > journal.txt
4. Attach the resulting text file here.
5. Also follow these steps to check for crashes:
21 matches
Mail list logo
