Fix submitted for AppArmor upstream:
https://gitlab.com/apparmor/apparmor/-/merge_requests/1333
Until the fix arrives in Ubuntu, you can add the additional lines to
your /etc/apparmor.d/abstractions/mesa or (better) create a file
/etc/apparmor.d/abstractions/mesa.d/lp2081692 with the added lines.
There has been not further update for too long, for now we consider it invalid.
Feel free to re-open if there is effort backing it up and motivation to bring
it to main.
** Changed in: vulkan-tools (Ubuntu)
Status: Incomplete => Invalid
** Changed in: vulkan-tools (Ubuntu Jammy)
St
** Description changed:
+ Window actions (like maximize) no more work in wayland for QEMU using
+ GTK backend once the guest UI is intialized.
+
+ This can be seen by running an installed or even a trial Ubuntu from an
+ ISO like:
+
+ $ qemu-system-x86_64 \
+ -boot d \
+ -cdrom ubuntu-22.04.
The reason for esmtp is actually bug 1895011 - but until then track it
here to show better in weekly checks.
** Also affects: esmtp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubu
Thanks for the ping on this old case Alexander!
Can you confirm that this is what you see on 22.04 with the there recent
2:11.3.5-1ubuntu4 version of open-vm-tools?
I have subscribed John Wolfe who looks after open-vm-tools from VMwares
side and might have more details.
Further I added a bug tas
Public bug reported:
Hi,
I've seen this while looking for NBS and saw
intel-opencl-icd holding in the old libigdgmm11
I checked if there was no rebuild, but there was one that would pick up
libigdgmm12 but it is an FTBFS
https://launchpad.net/ubuntu/+source/intel-compute-runtime/21.32.20609-
** Changed in: libxcvt (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcvt in Ubuntu.
https://bugs.launchpad.net/bugs/1960500
Title:
[MIR] libxcvt
To manage notifications about
While this is for CPC, Server team members work on it. Thereby I know
that while obviously we'd appreciate a faster review, this can happen
past 22.04 - but not much later. Also we have to face that the >=Focal
tasks still have some TODOs to even enter security review queue -
therefore this can't b
Thank you Alberto for clarifying that last bit.
By that we now have the MIR-team and the security-team Acks.
That should indeed be ready for promotion now \o/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.lau
I have the same problem on Ubuntu 20.04 with a ATI Radeon HD5770.
Setting VDPAU_DRIVER=none works here, too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libvdpau in Ubuntu.
https://bugs.launchpad.net/bugs/1927773
Title:
Can't play video X.
Still waiting on a response on this - marking incomplete
** Changed in: egl-wayland (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1935082
T
Thanks Alberto, while this is n't perfect yet (many would still need help to
run the test as it isn't detailed enough yet for e.g. me desktop-noob) but you
outlined what it is about - thanks.
But especially for a package like this which could be lost between kernel
(owning it) and Desktop (every
@Lukas - could you in the very same context also look at src:vulkan for
Bionic please?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to vulkan in Ubuntu.
https://bugs.launchpad.net/bugs/1946359
Title:
[MIR] vulkan-tools
To manage notifications
FYI - this is meant to be eventually promoted throughout all our releases.
Since the location changed there is also bug 1947020 for <=Bionic.
While the source changed and even more the source-name, since the rational and
many other things are actually the same I'm merging them here.
** Descriptio
Hi, this was not "wrong" in any way, but since the context, rationale
and so many other things are shared I merged this with the MIR bug
1946359
** Description changed:
- [Availability]
-
- vulkaninfo tool is present up to Bionic in package vulkan-utils, as
- part of vulkan source package:
-
** Changed in: vulkan-tools (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to vulkan-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1946359
Title:
[MIR] vulkan-tools
To manage noti
Hi,
I'd expect something based on those to questions:
- can the test be automated?
- yes => "link to the scripts you run"
- no => a list of the steps & tests that you will do (think of you are run
over by a bus, the next QA person has to do them by the script)
- does this have console outpu
Hi,
now everything is complete except the QA via testing.
We have amended the MIR rules to better clarify as this is one of the cases
that is hard to autopkgtest/build-test but some QA should happen still.
The new rule is:
"The package must include a non-trivial test suite, and if there is no obv
> kernel-packages is now subscribed.
Thanks, then it has the MIR-team ACK now and waits on security to be
complete.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1935082
Title:
[MIR] eg
>From the MIR meeting.
We are ok in regard to the testing, but please be sure that you as the owning
Team should ensure to have the necesary HW to be able to test this on
merges/updates as well as on debugging.
The only concern that is left (which can be clatrified while waiting on
security rev
...
>
> Something we could discuss at next MIR mtg.
>
I totally agree and I think this also is how we handled it so far (to
discuss it in the meeting AND how you suggested handling those HW
dependent cases).
It only seems right to formally express it in the process description.
Please remind me in
Public bug reported:
I got a nonreproducible crash of Xwayland with the following backtrace:
```
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x7f88c73c4859 in __GI_abort () at abort.c:79
#2 0x55dfca054e40 in OsAbort () at ../../../../os/utils.c:1351
#3
Yeah that is what I thought - Thanks for confirming Von!
My search engine use on this case found a few but no really related
issues either. If you happen to stumble over one please let me know.
Since it works fine for me I have to hope for the Desktop team taking a
look from the libepoxy POV what
As I said I added a libepoxy task and subscribed ubuntu-desktop as this
might be much more their home-turf to e.g. be up to date about known
cases why that would fail to initialize GTK/EGL.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy
... I guess "qemu(5.2+dfsg-3ubuntu1)+virgl on GTK/X11" is the bad case
then?
** Also affects: libepoxy (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpa
@Coiby Xu (coiby)
Thank you very much for the patch in #189. It works like a charm.
@Piotr Tomaszewski (nfm886)
Thanks for posting your solution in #201. I was in the exact same situation and
without it, I would probably still be wondering why it didnt work for me.
--
You received this bug noti
Hi didrocks/seb128 - this shows up in component mismatches.
We were wondering if ubuntu-x really still is an active team or if the
desktop-team would today be better to take this over?
Since it was approved in the past once the owner is sorted out this
could be re-promoted.
--
You received this
I tested version '20.0.8-0ubuntu1~20.04.1' from 'focal-proposed' and it
fixes the issues I encountered with EGL and specifically
'es2gears_wayland'.
--
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/1
Thanks @tjaalton. I see from https://launchpad.net/ubuntu/+source/mesa
that version 20.0.8-0ubuntu1 made it into Groovy proposed.
Is there a chance this will also make it into focal-proposed so that it
can be tested on the current LTS? Or do we have to wait until this gets
merged into groovy?
--
Is Mesa 20.0.7 going to be backported to Ubuntu Focal? It would be a
shame to be unable to use native OpenGL programs on Wayland for the next
5 years.
--
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
Public bug reported:
On Mesa 20.0.4, the Intel Iris driver is affected by an issue with
selecting the appropriate dma buffer format on Wayland
(https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4869).
This issue will prevent using most OpenGL applications on Wayland. You
can check if you
Issue definitely also occurs with stock Ubuntu GNOME DE (just did a
fresh install on a ThinkPad t495s with "AMD Ryzen 7 PRO 3700U w/ Radeon
Vega Mobile Gfx"; up-to-date kernel 5.3.0-26-generic and the issue
occurred twice within 12 hours of installing - once upon resuming and
the 2nd time just afte
Public bug reported:
games dont start on my intel graphics
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error:
Public bug reported:
La pantalla crashea al establecer la resolución en 1280x800 en el dispositivo
Lenovo Miix 320 ICR.
Por defecto, se establece en una resolución de 800x1280, es decir, vertical.
Sin embargo, para que antes llegue a mostrar algo en pantalla es necesario
tener que entrar al mod
Public bug reported:
ubuntu 18.04
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
Uname: Linux 4.15.0-64-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompizPl
Hi Luke,
thanks for the bug report and your help to make Ubuntu better.
I'm unsure what ssh could/should do differently in this case.
For similar issues there was a gnome PR [1] that went into gnome that should
allow a "yes and remember" kind of use-case. Not sure if that is missing in the
gnome
Is this fix being backported to bionic?
I am still getting crashes with the snap version of skype (8.34.0.78) on
xwayland-hwe-18.04.
--
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/1754693
FYI:
I was affected by the issue, but there must be another way to trigger than the
(re)install of console-setup and/or keyboard-configuration as those actions
were not triggering the issue for me after I rebooted.
OTOH the time it started to happen perfectly matches a background update to
those
in: mesa (Ubuntu Ee-series)
Status: New => Triaged
** Changed in: qemu (Ubuntu Ee-series)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.l
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244324/+files/WifiSyslog.txt
--
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
Just the plain Disco kernel environment as you get it when spawning a
new guest - data provided changing state of both bug tasks back.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244322/+files/ProcModules.txt
--
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/bu
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244320/+files/ProcEnviron.txt
--
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/bu
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244321/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244319/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.la
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244323/+files/UdevDb.txt
--
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/1818879
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244318/+files/ProcCpuinfo.txt
--
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/bu
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244316/+files/CurrentDmesg.txt
--
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/
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244317/+files/Lspci.txt
--
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/1818879
T
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 7 08:12 seq
crw-rw 1 root audio 116, 33 Mar 7 08:12 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
ArecordDevices: Error: [Errno
@Daniel - on one hand it is also a change in xorg that makes the driver missing
now - so an FYI for that.
But in an IRC discussion there were two potential paths to resolve this issue
overall:
- make the cirrus.ko available in the non -extra package so that it works out
of the box using this dri
The PPA was built against -proposed so I had to enable that to install all libs.
That done the 19.0.0~rc6-1ubuntu0.1 with the set affinity change reverted works
quite nicely.
It would be great to get that into Ubuntu 19.04 until the involved
upstreams agreed how to proceed with it and we can then
Hi Timo,
I tried to test with the mesa from ppa:canonical-x/x-staging
But there is a dependency issue in that PPA - I can't install all packages from
there.
It seems most of the X* packages will need a transition for the new mesa and
those are not in this ppa right now.
Installing all that I can
** Also affects: mesa (Ubuntu Disco)
Importance: Medium
Status: Confirmed
** Also affects: qemu (Ubuntu Disco)
Importance: Undecided
Status: Triaged
** No longer affects: qemu (Ubuntu Disco)
** Changed in: mesa (Ubuntu Disco)
Status: Confirmed => Triaged
** Changed in
Thanks Daniel and MarcAndre for chiming in here.
Atfer thinking more about it I agree to Daniel that actually mesa should honor
and stick with its affinity assignment.
For documentation purpose: the solution proposed on the ML is at
https://lists.freedesktop.org/archives/mesa-dev/2019-February/2
@Ubuntu-Desktop Team (now subscribed) - is there a chance we can revert [1] in
mesa before it will be released with Disco for now. That would be needed until
an accepted solution throughout the stack of libvirt/qemu/mesa is found?
Otherwise using GL backed qemu graphics will fail as outlined in t
Public bug reported:
I am trying to set a desktop background in gnome-flashback. The
background remains a kind of plum color and this error is displayed in
the terminal (if I run gnome-control-center from there):
christian@endor:/etc$ gnome-control-center
(gnome-control-center:4191): background
Hi Gannet,
the discussion of RussianNeuroMancer with upstream ended trying to tackle the
KDE resolution setting [1], but not a change in qemu/libvirt or other
components of the virst-stack. Also it was reported that newer versions were
less (or not)9 affected.
Is your case related to KDE as wel
*** This bug is a duplicate of bug 1769819 ***
https://bugs.launchpad.net/bugs/1769819
FWIW, I am experiencing fairly regular X.org crashes at sleep resume
with my ThinkPad X1c5 (stock KabyLake Intel HD 620 iGPU) on 18.04
(currently running 4.15.0-36 but has been happening for a while). Never
(gdb) bt full
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {171515904, 0, 0, 0, 0, 94870821356889, 94870821322000,
67108868, 140427223543248, 0, 0, 978464917824351488, 54, 94870838790880,
140727493513216, 140427243872632}}
pid =
Public bug reported:
I installed a daily snapshot of 18.10 in a VM.
After removing some unneccessary application, I ran
apt update
apt upgrade
and rebooted. I noticed X crashing after the reboot, taking me back to the
login manager. I have the option selected to automatically login without
pas
*** This bug is a duplicate of bug 1754693 ***
https://bugs.launchpad.net/bugs/1754693
** This bug has been marked a duplicate of bug 1754693
Xwayland crashed with SIGABRT in st_renderbuffer_delete()
--
You received this bug notification because you are a member of Ubuntu-X,
which is subs
*** This bug is a duplicate of bug 1754693 ***
https://bugs.launchpad.net/bugs/1754693
I get the same error when starting the skype snap:
org.gnome.Shell.desktop[2477]: (EE)
org.gnome.Shell.desktop[2477]: (EE) Backtrace:
org.gnome.Shell.desktop[2477]: (EE) 0: /usr/bin/Xwayland (xorg_backtrace
** Project changed: snappy => xorg-server (Ubuntu)
--
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/1760252
Title:
starting slack crashes xwayland on 18.04
To manage notifications about th
Hello,
I confirm this bug also affects me on several Kubuntu 16.04 machines
since this morning, apparently following the unattended upgrades that
happened on Friday.
The symptoms are as described int the bugerport. I see them in okular
and a custom Python application that uses PyQt4. The bug make
** Also affects: spice (Ubuntu)
Importance: Undecided
Status: New
--
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/1719038
Title:
X Server crashes during log in VM since 16.04.2
To mana
Just to clarify above comment from hans005: from what I can read here
his problem (#138, #145) was a completely different issue: standby with
nvidia GPU.
This regression relates to *hibernation* (not mere standby) and AFAIK,
has been experienced with a variety of GPUs (included Intel integrated
GP
** Summary changed:
- Please help me, i need an graphic driver that works on mei notebook!
+ Please help me, i need an graphic driver that works on my notebook!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchp
Public bug reported:
My graphic driver works not correctly.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-119.143~14.04.1-generic 4.4.114
Uname: Linux 4.4.0-119-generic i686
.tmp.unity.support.test.0:
ApportVersion: 2.14.1-0ubuntu
Public bug reported:
My internal display is not working. The internal display works at boot
and goes black during ubuntu boot. I am able to use the hdmi monitor but
i need my internal screen to work.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature:
I just tested it using the bionic live image (couple of days old) -
there it works perfectly, with the kernel 4.15. Maybe it's the 17.10
kernel - can't test it as I went back to 16.04 by now.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinp
** Summary changed:
- [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in
xorg.conf
+ [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in
xorg.conf (intel mesa driver)
--
You received this bug notification because you are a member of Ubuntu-X,
wh
Maybe this is i915/i965 intel driver related. If someone with an in
intel IGP could reproduce this. I have xserver-xorg-video-intel
installed by the way. With not mentioning "intel" explicitly as the
driver in xorg.conf doesn't it automatically uses modesetting or
glamorgl?
--
You received this b
Just had the idea to unload "glx" and see if I can Disable Composite
without crashing Xorg / startx / xinit.
It works!
Here's my xorg.conf:
Section "Module"
Disable "glx"
EndSection
Section "Extensions"
Option "Composite" "0"
EndSection
I'll put my resulting Xorg.0.log as an attachment.
Ho
I suspect libglx0 (transition from libgl1-mesa-glx to libglx0)
Because now we have:
/usr/lib/x86_64-linux-gnu/libGLX.so.0.0.0 (from libglx0 in bionic, new with
bionic)
instead of:
/usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
/usr/lib/x86_64-linux-gnu/mesa/l
Now I remove +s bit from /usr/bin/X, /usr/bin/xinit, /usr/bin/startx,
/usr/bin/Xorg and tried to run Valgrind with it. Honestly I have no idea
about debugging. I just know that valgrind and strace can be somehow use
for it. Hope this helps!
output of valgrind -v startx 1> valgrind_v_startx.txt 2>&
tried with "strace startx"
** Attachment added: "strace startx"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754296/+attachment/5072778/+files/strace_startx_001.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
http
nformational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", Time:
Wed Mar 7 22:43:35 2018
[ 35.801] (==) Using config file: "/etc/X11/xorg.conf"
[ 35.803] (==) Using system config directory "/
Ok, thanks!
However there was nothing in my /var/crash folder. Nonetheless I tried
to file a new bug with ubuntu-bug xorg. It added lots of system
information and logs.
here it is: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754296
--
You received this bug notification because you are
Tried with rebooting and restarting, nothing in /var/crash
--
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/1754177
Title:
[bionic] xserver / startx crashes with Composite Disabled in xorg.
Another interesting thing with this xserver-xorg-core is that it ignores
Option "AIGLX" "Off" in the ServerFlags section and initializes AIGLX.
This also hasn't happened before bionic.
And the crashing (see the Xorg.0.log in my previous post) seems to
happen right where normally some AIGLX initial
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[35.792] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log",
Time: Wed Mar 7 22:43:3
Yes, true, I can see that the touchpad is not detected as own device - so all
the settings apply to the mouse AND the (not separated) touchpad.
So the real problem is that thetouchpad is not properly detected.
--
You received this bug notification because you are a member of Ubuntu-X,
which is s
Public bug reported:
Appearance of a window "software problem after every boot
Apparition d'une fenêtre "problème de logiciel après chaque démérrage
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.
kann mir jemand helfen danke wegen mein bug
Can someone help me thanks because of my bug
--
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/1675057
Title:
I don't know
To manage notifications abou
Public bug reported:
my English is not good
Therefore also no further infos
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.3-0u
Public bug reported:
All games (with or without Steam) freeze after a random amount of time.
This bug is triggered, when another windows gets focus, but it happens
randomly too.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-57.78-gen
I can confirm this bug on an 14.04.5 LTS Intel NUC.
Also there is no nvidia card in my NUC.
I'm about to update to 16.4 or 16.10 so I'm not sure how much help I can
be in the future with this bug but I'll report back if it still exists
after the update
--
You received this bug notification becau
To all those who could hardly await a fix: Since it is closed source
driver, this issue has to be resolved upstream. So far, Nvidia has not
provided an update, although (according to Aaron Plattner) they are
working on it [1]. Just downgrading isn't always preferable, either.
Last update was suppos
Even a tool as innocent as glxinfo fails with an Xsession error similar
to that of the original post. As I am on a Quadro NVS 110M, upgrading to
a newer driver series is not an option. At least non-composited
X-Sessions (e.g. Xfce) still work.
--
You received this bug notification because you are
Well, unfortunatly, upgrading to 1.8 disables both the bluetooth module
and touchscreen on my device(Asus T300 chi), leaving me with no input
options. I suppose that's a separate problem, but it's rather hard to
file. I'll try to find my adapter, borrow a USB keyboard from someone
and file it. I'll
% apt-cache policy libgbm1-lts-vivid
N: Unable to locate package libgbm1-lts-vivid
2016-10-12 23:51 GMT+02:00 Timo Aaltonen :
> apt-cache policy
> libgbm1-lts-vivid
>
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.
Well, it's certainly a problem which appeared after I did the upgrade.
There were no issues before this point.
--
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/1632593
Title:
Xorg does not utilize
Can someone please change this to be about the package containing the
do-release-upgrade command?
--
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/1632593
Title:
Xorg does not utilize the 3D graph
** Attachment added: "Fotos.zip"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632740/+attachment/4759954/+files/Fotos.zip
--
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/1632740
Title:
Public bug reported:
After using my system for a period of time, usually less than an hour,
the screen starts to corrupt. It will vary in intensity, until the
system either crashes, or everything goes back to normal for a while.
When the system does crash, not even the sysrq-key works.
ProblemTy
I reinstalled the package, no dice. I then looked around for it, and
found that it had been renamed to old.libgbm1.so, along with the file it
linked to. I renamed both, removing the "old.", and now 3D works. It's
definitely still a bug though.
--
You received this bug notification because you are
The package is installed, but the file is not there.
On 12 Oct 2016 13:50, "Timo Aaltonen" wrote:
> your logfile disagrees
>
> [ 8.117] (EE) Failed to load /usr/lib/xorg/modules/libglamoregl.so:
> libgbm.so.1: cannot open shared object file: No such file or directory
>
> --
> You received th
No, I have not. Libgbm1 is installed, as well as all other packages
included in the ubuntu-desktop meta-package.
** Changed in: xorg (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://b
1 - 100 of 665 matches
Mail list logo
