Public bug reported:
I don't know what the problem is
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.1
I've separated the more recent duplicate bugs on VirtualBox where Mir is
starting OK (there are sufficient DRM resources) but then crashing. I
think that will inevitably require a separate fix -> bug 1584894.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
On Tue, Jul 26, 2016 at 5:40 PM, ernsteiswuerfel
wrote:
> Check your boot messages with "journalctl -k" and your
> /var/log/Xorg.0.log then you will get a hint what went wrong with r128.
>
> On current Ubuntu versions there is no need for an xorg.conf, only if
> you need to
Another Ubuntu Perthian! Excellent! I checked another laptop and the
kernel only listed the native resolution of the screen on that as well,
so perhaps the issue is in xserver/modeset after all. But out of
curiosity, what role is the kernel supposed to take here? It does list
all the modes for my
Check your boot messages with "journalctl -k" and your
/var/log/Xorg.0.log then you will get a hint what went wrong with r128.
On current Ubuntu versions there is no need for an xorg.conf, only if
you need to tune some specific parameters. No fiddling around with "sudo
Xorg-configure" needed.
--
The attachment "xdm.diff" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for
Public bug reported:
Hi
This patch implements automated branding fallback to xorg.xpm for Ubuntu
derivatives. While at it, it also makes this part of debian/rules
compatible with Debian and so easier to merge.
** Affects: xdm (Ubuntu)
Importance: Undecided
Status: New
** Tags:
** Changed in: ubuntu-gnome
Status: New => Confirmed
** Changed in: ubuntu-gnome/xenial
Status: New => Confirmed
** Changed in: xdiagnose (Ubuntu)
Importance: Undecided => Medium
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in:
@ernst:
I saw one of my problems, on the Xorg configure I didn't run "sudo service
lightdm stop" first . . . maybe I'll try that later or tomorrow . . . still
wondering why "r128" didn't show up in "lsmod" . . . .
F
--
You received this bug notification because you are a member of Ubuntu-X,
>
> Just found out that the needed xserver-xorg-video-r128 package is no
> longer installed by default in Yakkety. Maybe this is also the case in
> Xenial. So the easy solution for you would be to "sudo apt-get install
> xserver-xorg-video-r128" and reboot. Maybe you get an accelerated 24bpp
>
I've updated the BIOS and I've also removed all the non trusty kernels.
So now I'm running on 3.13.0-92-generic. I haven't had a crash yet but I
will report back if/when I do.
One other thing though that might be of importance. I noticed when
cleaning up the kernel packages that I have
➜ ~ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
JBET61WW (1.25 )
07/13/2016
--
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/1598904
Title:
X server crashes
I receive:
mount: can't find /root in /proc/mounts
`more /proc/mounts` shows:
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=4067424k,nr_inodes-1016856,mode=755
0 0
Stefan Freyr, as per http://support.lenovo.com/us/en/products/Laptops-
and-netbooks/ThinkPad-T-Series-laptops/ThinkPad-
T450s?linkTrack=GPS%253ABody_Search%2BProducts==false an
update to your computer's buggy, insecure, and outdated BIOS is
available (1.25). When you update to this following
rohshall, as per
https://www.asus.com/Motherboards/Z97K/HelpDesk_Download/ an update to
your computer's buggy, insecure, and outdated BIOS is available (2902).
When you update to this following
https://help.ubuntu.com/community/BIOSUpdate how does this improve the
situation?
For more on BIOS
Yes, unfortunately, the reason I upgraded the kernel is this issue. So
this happens with the default kernel.
--
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/1598904
Title:
X server crashes
It feels like the problem is occurring less frequently after I upgraded
the kernel but that may very well just be wishful thinking.
--
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/1598904
Title:
17 matches
Mail list logo