hm, that revert is already in the xenial kernel since
Ubuntu-4.4.0-23.41, so you're seeing something else or it depends on
some other commit which isn't there
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
ht
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
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/1565729
Upstream says nouveau is known to not support multi-threaded rendering and will
crash:
https://bugs.freedesktop.org/show_bug.cgi?id=92438
So that completely explains yesterday's crash in bug 1623507.
Hopefully that vaguely explains this one too.
** Bug watch added: freedesktop.org Bugzilla #9
** Summary changed:
- Mir is just a black screen and mouse cursor on Nvidia GTX 900
+ Mir is just a black screen and mouse cursor on Nvidia GTX 900 (and sometimes
"Failed to schedule page flip")
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to m
Confirmed by duplicate/similar bug 1623507
** Summary changed:
- unity8 crashed with SIGSEGV on nouveau, in eglMakeCurrent() ... nv50_flush()
... pushbuf_kref()
+ Mir crashes on nouveau (nv50) in pushbuf_kref()
** Changed in: qtmir (Ubuntu)
Status: Incomplete => Invalid
** Also affects:
*** This bug is a duplicate of bug 1553328 ***
https://bugs.launchpad.net/bugs/1553328
Aha!
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1553328, so it is being marked as such. Pleas
I'm marking the nouveau/Mesa crash as high severity. And the secondary
Mir crash is only medium because that's not really the problem at all.
Here's the Mesa crash:
#9
No locals.
#10 0x7fe1e4c4f06c in pushbuf_kref () from
/tmp/apport_sandbox_hSYpvb/usr/lib/x86_64-linux-gnu/libdrm_nouveau.s
I don't think we need to verify this one. Maybe just jump to
verification-done.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1617932
Title:
Xmir with glamor is spending 11% of its CPU t
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1581076
Title:
Xorg segfaults on start-up on Big Endian PPC hardware
The workaround is not working :( -
$ sudo setfacl -m u:kodi:rw /dev/tty0 /dev/tty7
setfacl: Option -m: Invalid argument near character 3
$ sudo chmod 0660 /dev/tty*
$
$ startx
...
Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (No such file or directory)
...
Any ideas?
--
Yo
I enabled xenial-proposed and installed xmir. I can confirm this bug is
fixed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.n
I have enabled xenial-proposed and installed xmir. I can confirm this
bug is fixed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launch
I have enabled xenial-proposed and installed xmir. I can confirm this
bug is fixed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launch
Further info—Xorg.log.Old is completely blank after a failed boot. I'm
assuming that means Xorg failed to start altogether?
--
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/1623294
Title:
Black sc
*** This bug is a duplicate of bug 1623294 ***
https://bugs.launchpad.net/bugs/1623294
Thanks Hans!
--
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/1623295
Title:
Black screen on startup aft
I see that the build has completed successfully. I manually fetched and
installed https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.1/+build/10751236/+files/xserver-xorg-
core_1.18.4-0ubuntu0.1_powerpc.deb , and Xorg came to life as expected,
without the segfault.
--
You receive
*** This bug is a duplicate of bug 1623294 ***
https://bugs.launchpad.net/bugs/1623294
>Accidentally submitted this bug twice . . . Not sure how to delete the
duplicate.
Look for "Mark as duplicate" towards the top on the right side. I've
marked this issue as a duplicate of the other.
** Th
Hi Andy,
Thanks very much. We will certainly test this ASAP once it lands in
proposed, and report back.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1581076
Title:
Xorg segfaults on st
This bug fixed in Xenial, but still needs to be patched in Trusty. This
also will fix it in Trusty based distros like Elementary OS Freya.
I have just requested an upgrade on those. You'll be noticed when that's
ready.
** Changed in: light-locker (Ubuntu)
Status: New => Invalid
** Changed
fixes https://bugs.launchpad.net/ubuntu/xenial/+source/xorg-
server/+bug/1575000
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1619142
Title:
[MRE] Update to 1.18.4
To manage notificati
Hello Timo, or anyone else affected,
Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
Hello Albert, or anyone else affected,
Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Alex, or anyone else affected,
Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
Hello Xinxiu, or anyone else affected,
Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Victor, or anyone else affected,
Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Daniel, or anyone else affected,
Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Daniel, or anyone else affected,
Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Daniel, or anyone else affected,
Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
you should be able to fix this issue, creating a file as following:
$ cat /etc/X11/xorg.conf.d/jabra.conf
Section "InputClass"
Identifier "Jabra Audio docking station"
MatchDevicePath "/dev/input/event*"
MatchProduct "Netcom"
MatchVendor "GN_Netcom_A_S"
Option "Ignore" "true"
E
I was probably wrong last year.
- In [1] there are still many crash reports to Mozilla.
- These point very often too to the ~GLContextGLX destructor, similar to
comment #0.
- Kernels are often Ubuntu kernels.
- Probably just on 14.04 LTS.
- Gallium 0.4 on NV46 or NV4B.
[1] https://crash-
stats.mo
Public bug reported:
problemi scheda radeon
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Com
Updated debdiff after adding new changelog and backporting to Mir 0.21.
** Attachment removed: "debdiff for Xenial SRU"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1613708/+attachment/4739347/+files/debdiff
** Attachment added: "debdiff for Xenial SRU"
https://bugs.launchpa
Public bug reported:
I think this appeared after I suspended my laptop (Lenovo E460). It does
not recognize mouse movement and no cursor is displayed.
I saw a similar bug where the cursor did not show being solved but there they
seemed to be able to click. They were also able to get it back aft
Public bug reported:
1) Ubuntu 16.04.01 LTS
2) 1.8.2-1ubuntu3
3) When releasing the finger from the touchpad (e.g. while marking larger
portions of text, or scrolling using the sidebar) I expect the cursor to remain
in the position it was before the finger was upped from the keyboard.
4) Instead
Public bug reported:
Xmir -rootless: Windows move a little during rapid resizing
This would be due to some confusion around whether the resizing is
coming from Mir or from the X client. We have resizing logic to support
both directions so obviously it's getting a bit of feedback.
** Affects: xor
35 matches
Mail list logo