The crash occurred in Mesa gallium code (so radeon or nouveau). However
the caller was mutter (gnome-shell) from its hybrid GPU logic, which is
only used in Wayland sessions.
I know that doesn't help users right now, but it's important information
for developers.
** Summary changed:
-
** Package changed: xorg (Ubuntu) => apparmor (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1759769
Title:
Failed to start AppArmor initialization.
To manage notifications about this
This bug was fixed in the package libxcb - 1.13-1
---
libxcb (1.13-1) unstable; urgency=medium
[ Julien Cristau ]
* Switch xcb.freedesktop.org URLs in packaging to https.
* Stop building -dbg packages, rely on automatic dbgsym packages instead.
[ Helmut Grohne ]
* Make
Public bug reported:
ob for apparmor.service failed because the control process exited with error
code.
See "systemctl status apparmor.service" and "journalctl -xe" for details.
invoke-rc.d: initscript apparmor, action "restart" failed.
● apparmor.service - AppArmor initialization
Loaded:
Public bug reported:
black screen after logon
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CompizPlugins: No value set
Public bug reported:
after logout i can't login agin
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CompizPlugins: No
after nvidia-390 became nvidia-driver-390 I get back screen.
I have Acer vx5 laptop with nvidia 1050/Intel
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1676583
Title:
*** This bug is a duplicate of bug 1673649 ***
https://bugs.launchpad.net/bugs/1673649
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1673649, so is being marked as such.
I have a Dell R430 server which suffers this issue.
My problem is that in a xrdp session, "xrandr -v" reports: "server
report RandR version 1.1."
After following steps, it still report RandR version is 1.1
0. load mag.ko
1. build and load maga200.ko
2. build mag_drv.so 1.6.5 (downloaded from
I haven't done such testing yet but will do after easter. This is all
staged in Debian experimental for now. As for the other new stuff, I'll
just add the release notes from the first beta:
"This is the alpha for the 1.15 release, containing many bug fixes and a
few new tests.
Compositor writers
Public bug reported:
I usually have my notebook connected with a monitor by HDMI. If I
suspend it, after wake just appear the desktop in the notebook but no in
monitor, and no respond to any input device (mouse, keyboard), except to
combine keys to restart: ctrl+alt+prt sc -> ctrl+alt+F12 ->
[Expired for xserver-xorg-video-nouveau (Ubuntu) because there has been
no activity for 60 days.]
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
*** This bug is a duplicate of bug 1731261 ***
https://bugs.launchpad.net/bugs/1731261
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1731261, so is being marked as such.
Hey Tony,
Have you made sure you are on Xorg and not Wayland session?
On Thu, Mar 29, 2018 at 4:33 PM, Tony Mobily <1042...@bugs.launchpad.net>
wrote:
> Unfortunately, this:
>
> [1] https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X230#Touchpad
>
> No longer works as a fix in Ubuntu 17.10
>
Unfortunately, this:
[1] https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X230#Touchpad
No longer works as a fix in Ubuntu 17.10
Why would that be? Is the file no longer considered by Xorg?
Does anybody here know how to make it work?
I have a fantastic X220, which is still pretty damn fast
Hi,
Oh my goodness...
I am using Wayland!!!
merc@merc-ThinkPad-X220:/disk/home/merc$ ps ax | grep wayl
922 tty1 Ssl+ 0:00 /usr/lib/gdm3/gdm-wayland-session gnome-session
--autostart /usr/share/gdm/greeter/autostart
968 tty1 Sl+0:00 /usr/bin/Xwayland :1024 -rootless -terminate
I am even more confused as I installed -- and configured -- the Compiz
setting manager. So... is it really all compatible? How the heck...?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
18 matches
Mail list logo
