Thanks for the bug report. You appear to be using the 'oibaf' PPA for
your graphics packages, which is unsupported and is known to cause bugs.
Please remove it from the system and then open new bugs for any problems
you find.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
What is the problem you would like to report?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
*** This bug is a duplicate of bug 1975379 ***
https://bugs.launchpad.net/bugs/1975379
** This bug has been marked a duplicate of bug 1975379
Xorg crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Those are two unrelated bugs so please pick one only:
* When I record the screen with Kazam the resulting video shows only the
pointer, the rest of the screen is black.
Unless it's been ported to use PipeWire, such legacy screencasting apps
for X11 won't work in Wayland sessions. A black screen
> My understanding from what I have read about this topic was
> that users with hybrid systems (which I take to mean those
> with both an NVIDIA graphics card and a second non-NVIDIA
> graphics card in this context) are expected to see the gear,
> but I may be mistaken.
Technically, yes. Our
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Reflecting on my original issue from the perspective of a lay user,
crashing the windowing system because a custom configuration file
couldn't be parsed seems like a bug in its own right. A lay user may
understandably react very strongly to seeing a black screen at startup.
If they have a more
To clarify, I was defaulted into Wayland (which worked as far as I could
tell aside from the broken Night Light) upon upgrade from Ubuntu 21.04
to Ubuntu 22.04, so what was actually hidden from users not comfortable
manually editing /etc/gdm3/custom.conf in this case was instead X11. My
Public bug reported:
When I record the screen with Kazam the resulting video shows only the pointer,
the rest of the screen is black.
After I sleep and start my HP laptop, Cheese and Zoom do not detect the camera.
Hardware model: HP HP Pavilion Laptop 15-cw1xxx
Processor: AMD® Ryzen 7 3700u
> The one remaining mystery to me is that the gear to switch
> between X11 and Wayland still doesn't show up at the login screen.
We intentionally hide Wayland when the Nvidia driver is present due to
unresolved bugs in the Nvidia Wayland implementation:
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
** Summary changed:
- Desktop resolution was set incorrectly until I booted up the PC AFTER turning
on the monitor
+ Desktop resolution was set
Thank you for your very quick and helpful guidance, Daniel. I will sleep
far easier in the future, my eyes now spared from blue light! The
contents of prevboot.txt contained the following pertinent excerpt:
/usr/libexec/gdm-x-session[1415]: Data incomplete in file
I encountered this bug today. Although the monitor was on, I could not
get a signal till I turned it off and on. Then I just got 1024x768.
Weirdly though, Wayland was in use with no Xorg server running.
Now that I try to reproduce the bug again, I can't. I just get Xorg as
described in bug
15 matches
Mail list logo
