"Changed in xserver-xorg-input-libinput (Ubuntu):
status: Confirmed → Invalid"
Greek! That is greek to me. Very hermetic. The bug has not been patched
yet.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
"No space left on device" usually means your disk is full, so check
that. It can also mean that the process (X server or shell) has just
leaked and exhausted some particular resource.
Since it's a crash we require a stack trace to identify it properly,
since it's likely other people are reporting
I should have mentioned, my Hades has 32GB of RAM.
With 8GB or less of RAM, the problem might persist (if I understand the mailing
list posts).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Try the following:
xrandr --output DVI-D-0 --set TearFree 1
You may need a different output e.g. HDMI-A-0
You can list your outputs by just running "xrandr"
Apply the TearFree option to all of your monitors and try again
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546
** This bug is no longer a duplicate of bug 1508146
Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes),
cannot disable
** This bug has been marked a duplicate of bug 520546
Alt-f2
This just changed for me... but the hardware may matter, as I'm on Hades
Canyon, using the amd gpu, not HD graphics.
A few days ago I updated to the then-latest 4.19-rc2
(and wrote https://ubuntuforums.org/showthread.php?t=2400400 documenting
exactly what I did).
Using plain old X (no desktop) on
** Description changed:
- -What I expected to happen:
+ - What I expected to happen:
Open nvidia-settings and switch between Intel and Nvidia graphic cards.
- -What happened instead:
+ - What happened instead:
Steps (case 1):
1. Install propetary driver.
2. Reboot and select Wayland
** Description changed:
-What I expected to happen:
Open nvidia-settings and switch between Intel and Nvidia graphic cards.
-What happened instead:
Steps (case 1):
1. Install propetary driver.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to
** Attachment added: "lsusb"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+attachment/5187651/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Attachment added: "lspci -v"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+attachment/5187650/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Attachment removed: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/+attachment/5161172/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Public bug reported:
Ubuntu Release: Ubuntu 18.04.1 LTS
Package version: xserver-xorg: 1:7.7+19ubuntu7.1
When my laptop resumes after suspend, the desktop session crashes and a new one
is started. So each time I lose all open applications and unsaved data!
The expected behavior would be
** Description changed:
Steps (case 1):
1. Install propetary driver.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
1. sudo prime-select intel.
2. Reboot and select Wayland session.
3.
** Description changed:
Steps (case 1):
-
1. Install propetary driver.
- 2. reboot and select wayland session.
+ 2. reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
+ 1. sudo prime-select intel.
+ 2.
** Description changed:
When reboot my system and try open nvidia-settings, this message arise
"ERROR: Unable to find display on any available system"
+
+ Over Wayland and X11.
SYSTEM INFORMATION:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
nvidia-settings:
Public bug reported:
When reboot my system and try open nvidia-settings, this message arise
"ERROR: Unable to find display on any available system"
SYSTEM INFORMATION:
Description:Ubuntu 18.04.1 LTS
Release:18.04
nvidia-settings:
Installed: 396.54-0ubuntu0~gpu18.04.1
Candidate:
You have been subscribed to a public bug:
When reboot my system and try open nvidia-settings, this message arise
"ERROR: Unable to find display on any available system"
System information:
Description:Ubuntu 18.04.1 LTS
Release:18.04
nvidia-settings:
Installed:
We will need some more information about the problem.
Can you please:
1. Take a photo of any error messages you see; and
2. Next time you are able to boot OK after a failure, run:
journalctl -b-1 > previous_boot.txt
and attach the file 'previous_boot.txt' to this bug.
**
Public bug reported:
boot up failed *4... may be the [root] could not read f?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
.tmp.unity_support_test.0:
ApportVersion:
** Description changed:
+ [Impact]
+
+ The new libgles1 conflicts with nvidia-340 which ships it's own copy of
+ libGLESv1_CM.so
+
+
+ [Test case]
+
+ Enable proposed, install libgles1 and nvidia-340, they should install
+ fine.
+
+
+ [Regression potential]
+
+ none, just fixes a file
21 matches
Mail list logo
