1.) Start Ubuntu
2.) Login
3.) Gnome-Shell appear for a short time
4.) I end back on the login screen
5.) I change to xorg and log in succesfully
I reportat this on:
https://discourse.ubuntu.com/t/since-update-to-jelly-wayland-do-not-anymore-work/26681
According to the feedback i got I Created t
Oh sorry, I see the problem:
[ 76.192764] Klappi org.gnome.Shell.desktop[3287]:
Gjs:ERROR:../gi/interface.cpp:101:bool
InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&):
assertion failed: (args[0].isObject())
[ 76.201950] Klappi org.gnome.Shell.desktop[3287]: Bail out!
You have been subscribed to a public bug:
Hardware: https://linux-hardware.org/?probe=1055dc7082
Worked without Problem in 21.04
Had some flicker and problem with the left dock in 21.10
not working since updating to 22.04
now I'm running xorg.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Packag
Thanks for the bug report.
Can you explain in more detail what is not working? Maybe with a photo
or video?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Package changed: gnome-shell (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of
Public bug reported:
Hardware: https://linux-hardware.org/?probe=1055dc7082
Worked without Problem in 21.04
Had some flicker and problem with the left dock in 21.10
not working since updating to 22.04
now I'm running xorg.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1
** Bug watch added: Red Hat Bugzilla #2036604
https://bugzilla.redhat.com/show_bug.cgi?id=2036604
** Also affects: gnome-shell (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=2036604
Importance: Unknown
Status: Unknown
--
You received this bug notification because you ar
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-42 fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1960585
Title:
g
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5078
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5078
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5078
Importance: Unknown
Status: Unknown
** Changed in: gnome-shell (
XorgLogOld.txt is showing that Xorg crashed. If that's a recurring issue
then it might explain this bug.
It looks most likely to be bug 1811023 which is also the most common
Xorg crash globally for Ubuntu right now. It also seems to mostly affect
Nvidia users.
Please reproduce the issue a few mor
Sounds like a variation of bug 1878838.
** Summary changed:
- Xorg freeze
+ Dell Precision 5520 no longer boots properly (black screen)
** Summary changed:
- Dell Precision 5520 no longer boots properly (black screen)
+ Dell Precision 5520 boots to the wrong VT (black screen)
** Package change
You have been subscribed to a public bug:
I have several Dell Laptops model Precision 5520. Ubuntu LTS 20.04.2
seems to run fine without issues. After do a software update which
appears to update to LTS 20.04.3, the laptops no longer boot properly. I
end up at a black screen with an underscore cu
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1960857
Title:
gdm3 self-enables during upgrade
To manage notifications about this bug go to:
https://bugs.launchp
> those drivers are always behind and rather unstable in my experience,
especially with nouveau currently.
I was suggesting the 5.5 beta driver which is the latest (December 2021)
- https://www.synaptics.com/products/displaylink-
graphics/downloads/ubuntu. It works with the official jammy kernel 5
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can
from the newly installed system with 20.04, warnings came for
/var/lib/gdm3.config and .local not being empty.
root@ubuntu-inspiron-5482:/var/lib/gdm3# ls -lrta
total 32
drwxr-xr-x 3 root root 4096 feb 5 12:33 .config
drwx-- 3 gdm gdm 4096 feb 5 12:34 .nv
drwx-- 4 gdm gdm 4096
hi, this machine has not been much customised. I only switched display manager
because the supplied one did not work. I cannot reinstall and lose data.
Display link does not work on at least 2 of my systems with kernel 5.13 and
they reopened a bug because I reported it - those drivers are always
Oh also maybe this would be handy, I use etckeeper(8) with unattended-
upgrades(8) so I can show you that the change happened when gdm went
from 3.36.3-0ubuntu0.20.04.3 -> 3.36.3-0ubuntu0.20.04.4:
root@romane:~# etckeeper vcs log
fea52b81f4bbc9c171206a56a4d53087bf82b82d~..fea52b81f4bbc9c171206a56
Public bug reported:
I've been running Ubuntu 20.04 LTS on some servers for a while. This
week, they started going non-responsive. Plugging in monitors and
keyboards to them, I found they had gone to sleep, and waking them up
showed the purple gdm login screen. Before, they've always just had my
g
thank for the reply, closing then, it's not really possible to figure
out what was wrong without access to the system to get the details
** Changed in: gtk+3.0 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whi
gedit no longer uses tepl, so I'm closing this bug.
** Changed in: gedit (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1901446
Title:
Add gir
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1743366
Title:
The user session should run under systemd
To manage notifications about this bug
Interesting, thanks for verifying. I just re-tested this and indeed for
`systemctl --user is-active graphical-session.target` we have
- Impish clean install: active
- Jammy clean install: inactive
So looks like this we switched to systemd sessions at some point, but
this bug never got closed,
Apologies for the confusion. I was not using a fresh Impish install.
I just did a clean install and graphical-session.target is reported as active.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.l
Maybe useful: https://wiki.gnome.org/Initiatives/SystemdUser
I'll add that I was confused by this as systemd.special(7) says about
graphical-session.target:
This target is active whenever any graphical session is running. [...]
and it took me a while to figure out that's not true in our case.
This bug was filed pre-Bionic and explicitly mentions Bionic, but looks
like the issue is still present in Jammy:
$ systemctl --user is-active graphical-session.target
inactive
verified in a clean Jammy install and also on Impish (thanks ~ogayot).
Other than the .path units under /usr/lib/system
Bug still exists in 2022.
Observed on an ext4fs that is mounted over smb.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/42571
Title:
eog won't delete images on different volume
To m
26 matches
Mail list logo
