According to the launchpad page for mesa 22.2.5-0ubuntu0.1~22.04.2
(https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.04.2)
the package is still in proposed, not updates. @tjaalton 's message in
#72 suggests it has been released to updates but this appears incorrect.
I'm on 22.04 with
After happening every day for a week, this hasn't happened again since I
logged this bug.
I also disabled Firefox WebRender so maybe that was a contributor.
I'll re-open if I can provide any useful data.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Incomplete
--
You rec
** Attachment added: "dmesg-2020-02-15.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+attachment/5328274/+files/dmesg-2020-02-15.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati i
Public bug reported:
Since the update:
xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic;
which resulted from:
https://bugs.launchpad.net/fedora/+source/xserver-xorg-video-
ati/+bug/1841718
I've experienced GPU freezes where all video becomes unresponsive, both
Xorg and Ctr
** Attachment added: "dmesg-2020-02-14.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+attachment/5328273/+files/dmesg-2020-02-14.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati i
*** This bug is a duplicate of bug 1841718 ***
https://bugs.launchpad.net/bugs/1841718
After a little more investigation, this is resolved on
https://bugs.launchpad.net/fedora/+source/xserver-xorg-video-
ati/+bug/1841718 and the fix is currently in ppa:canonical-x/x-staging
** This bug has be
I am also seeing the same thing as the screencast.
It can be reproduced with tooltips and the Alt+Tab window.
Graphics card:
Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870]
Driver package:
xserver-xorg-video-ati-hwe-18.04/bionic-updates,now 1:19.0.1-0ubuntu1~18.04.1
--
You rec
Happening to me too. Full details available on this issue:
https://github.com/brave/brave-browser/issues/7439
** Bug watch added: github.com/brave/brave-browser/issues #7439
https://github.com/brave/brave-browser/issues/7439
--
You received this bug notification because you are a member of Ub
Public bug reported:
Hi there,
I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to
replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However,
there is one issue which occurs frequently whereby the display flickers and
becomes unusable. The best way to descr
So, the pauses I am experiencing is likely due to simply the fact that
the keyboards and mice are being removed then added back, which is a
different issue than the crashes (which appear nvidia related). I will
likely create a PR to only trigger the input subsystem on an as-needed
base to reduce th
I had some luck with this not pausing/blinking gnome-shell:
$ sudo udevadm control --reload-rules
$ sudo udevadm trigger --subsystem-nomatch=input
$ sudo udevadm trigger --property-match=ID_INPUT_JOYSTICK=1
Alan, perhaps you can upgrade to core from edge (since it does some
things with ID_INPUT_J
I noticed I could prevent gnome-shell from blinking/pausing if instead
of 'sudo udevadm control --reload-rules && sudo udevadm trigger' I
instead did 'sudo udevadm control --reload-rules && sudo udevadm trigger
--subsystem-nomatch=input'. I'm not sure there is much that snapd can do
with that infor
I suspect this is because snapd will do 'sudo udevadm control --reload-
rules && sudo udevadm trigger' on interface connections. These
operations are supposed to be safe but I've seen with my Intel graphics
that gnome-shell/X11 will blink when this happens (due to the 'udevadm
trigger') but it does
** Summary changed:
- Blank screen with only mouse pointer after mesa driver update; display does
not switch to tty7 upon lightdm start; Xorg.0.log quickly grows
+ Blank screen with only mouse pointer after 7.10 radeon driver update; display
does not switch to tty7 upon lightdm start; Xorg.0.log
This issue has a workaround:
Download 7.9 radeon driver Ubuntu package (xserver-xorg-video-radeon-
hwe-16.04_7.9.0-0ubuntu1~16.04.1_amd64.deb) from:
https://launchpad.net/ubuntu/xenial/amd64/xserver-xorg-video-radeon-
hwe-16.04/1:7.9.0-0ubuntu1~16.04.1
Execute the following on the downloaded .de
Line 3039 in the source can also cause the message:
if (flip_sync == FLIP_ASYNC) {
if (!drmmode_wait_vblank(crtc,
DRM_VBLANK_RELATIVE |
Okay, a little code inspection leads to one of these two function calls
failing at line 3062:
if (crtc == ref_crtc) {
if (drmmode_page_flip_target_absolute(pRADEONEnt,
drmmode_crtc,
I'll "gdb attach" the Xorg process next and see if I can't get some
runtime data.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati-hwe-16.04 in Ubuntu.
https://bugs.launchpad.net/bugs/1750393
Title:
Blank screen with only
Specifically, the source file:
./src/drmmode_display.c:xf86DrvMsg(scrn->scrnIndex, X_WARNING,
"flip queue failed: %s\n",
Line 3093 in the source code of `drmmode_display.c`:
flip_error:
xf86DrvMsg(scrn->scrnIndex, X_WARNING, "flip queue failed: %s\n",
Source of warning message from radeon_drv.so:
./src/drmmode_display.c:xf86DrvMsg(scrn->scrnIndex, X_WARNING, "flip
queue failed: %s\n",
./src/radeon_kms.c: xf86DrvMsg(scrn->scrnIndex, X_WARNING, "flip queue
failed in %s: %s\n",
./src/radeon_kms.c: xf86DrvMsg(scrn->scrnIndex, X_WAR
The warning string in the Xorg.0.log, "flip queue failed", is found in the
following driver:
/usr/lib/xorg/modules/drivers/radeon_drv.so
found in package: xserver-xorg-video-radeon-hwe-16.04
This module is loaded in Xorg on my machine. I'll download the source
and start looking through the code.
I think something is hosed with the radeon driver in mesa 17.2.8, but I
can't find the 17.2.4 pkgs to roll back and test the theory. The 17.2.4
was pulled from updates and proposed lines. I'm hesitant to rollback to
11.2.
I can get you anything you need (logs, etc...) look at the issue. I'm a
l
Failed to upgrade fglrx to 2:15.201-0ubuntu0.14.04.2
Please check full log as attached.
dependency problems:
update-initramfs: deferring update (trigger activated)
dpkg: dependency problems prevent configuration of fglrx:
fglrx depends on xorg-video-abi-11 | xorg-video-abi-12 | xorg-video-abi-13
More details:
- this is on Ubuntu 12.04
- the module does load into the kernel
- lightdm does present a login screen
- nvidia-340 doesn't work on this system
- compiz fails to start (from ~/.xsession-errors):
gnome-session[6632]: WARNING: App 'compiz.desktop' respawning too quickly
gnome-session[66
I see this on:
01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 305M]
(rev a2) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device 395a
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at d200 (32-bit, non-prefetchable) [size=16M]
Could this be related to https://bugs.launchpad.net/bugs/1604872 ?
--
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/1603904
Title:
X apps that use dbus (GTK, Firefox) either don't start or
This is the fix. It's still an issue in 16.10 Yakkety with the latest
drivers and everything else. I did a fresh install.
https://itsfoss.com/fix-brightness-ubuntu-1310/
FIX BRIGHTNESS CONTROL ISSUE WITH INTEL CARD IN UBUNTU 14.04 AND LINUX
MINT 17:
Open a terminal and create the following confi
Wouldn't you know it, after weeks of running 16.04 and not seeing it, I
saw it last night.
$ cat /proc/version_signature
Ubuntu 4.3.0-7.18-generic 4.3.3
I'm running 4.3 due to another bug. I've not (yet) seen this bug with a
4.4 kernel.
--
You received this bug notification because you are a m
I can say for sure that the 16.04 kernels don't exhibit this behavior. I
believe the wily release kernel (and later) did not as well.
--
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/1467595
Title:
The situation seems to be improved with the 4.2 kernel in the
canonical-kernel-team ppa:
$ cat /proc/version_signature
Ubuntu 4.2.0-6.6-generic 4.2.0-rc8
I have suspended and resumed several times with the external monitor
coming up properly and have not (yet) seen this bug with this kernel.
--
Thanks for the additional workaround. I didn't happen to have this enabled so I
had to:
$ gsettings set org.gnome.settings-daemon.peripherals.mouse locate-pointer true
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.
Sigh, with kernel 4.1.0.1.1~rc2 I just had the cursor disappear, so it
is not fixed as I had hoped. :\
That said, arround the time this happened I noticed this in syslog:
Jul 16 10:37:33 jamie-XPS-13-9343 kernel: [11297.284147]
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
I updated to A04 and it did not make a difference.
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A04
05/15/2015
Furthermore, I tried on 4.0 and 4.1 kernels (keeping the 15.04
userspace) and this also made no difference.
You asked to specify what happened with A04, it is
FYI, for unrelated reasons, I started using the 4.0 from wily and the
4.1 kernel from https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/. I was able to run an X/Unity session under
the 4.1.0-1.1~dogfoodv1 kernel for two days without rebooting without
the cursor disappearing (I am no
Ok, this happened just now with A04 and stock vivid kernel.
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A04
05/15/2015
** Changed in: xorg (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: xorg (Ubuntu)
Importance: Low => High
--
You received this b
I upgraded to A04 and will let you know how it goes. I don't have a
reproducer so I'll just watch out for it and report back either way.
--
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/1467595
Titl
FYI, this has happened 3 times today already and none of those times did
the cursor come back (tried compiz --replace, unity, the gsettings
command, closing apps, going to vt). I had to logout and back in and
lose all state. The first time made me late for a meeting.
--
You received this bug noti
Also, no EE lines in Xorg.0.log or Xorg.0.log.old:
$ grep '(EE' /var/log/Xorg.0.log*
/var/log/Xorg.0.log:(WW) warning, (EE) error, (NI) not implemented, (??)
unknown.
/var/log/Xorg.0.log.old:(WW) warning, (EE) error, (NI) not implemented,
(??) unknown.
--
You received this bug noti
** Summary changed:
- after screenlock and screen suspend, external display link monitor doesn't
resume properly
+ after screenlock and screen suspend, external display port monitor doesn't
resume properly
--
You received this bug notification because you are a member of Ubuntu-X,
which is sub
Public bug reported:
I have a Dell XPS 13 9343 with external display link monitor which I use
in non-mirrored mode as two different screens. If the screen locks and
suspends (simply locking is not enough) if I tap a key/move the
mouse/etc the laptop screen comes up and the external monitor flashes
** Information type changed from Private Security to Public
--
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/1419394
Title:
I don't know
To manage notifications about this bug go to:
https://bugs
(In reply to 1544c from comment #94)
> (In reply to Ryan Underwood from comment #93)
> > You didn't actually install the packages that include the fix. :-) Try
> > dist-upgrade.
>
> Newbie here. I tried the same thing as Jamie Jackson but it keeps crashing.
> I ha
(In reply to Alex from comment #100)
> Jamie Jackson, having read you issue with www.google.com/chrome, I've
> visited the site at least 10 times using Chrome after yesterday's updates
> and all went just fine. Are you facing the same issue when you're using
> chrome or
What's the edgers/package-based workaround?
I tried the following (on Linux Mint 17):
sudo apt-add-repository ppa:xorg-edgers/ppa && sudo apt-get update &&
sudo apt-get upgrade
...and I got some new packages, but also saw that some were held back:
The following packages have been kept back:
l
** Information type changed from Private Security to Public
--
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/1395532
Title:
My mouse doesn't work
To manage notifications about this bug go to:
htt
** Information type changed from Private Security to Public
--
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/1387712
Title:
start up error
To manage notifications about this bug go to:
https://bu
** Information type changed from Private Security to Public
--
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/1386014
Title:
travou
To manage notifications about this bug go to:
https://bugs.launc
** Changed in: xorg-server (Ubuntu Raring)
Status: Confirmed => Won't Fix
--
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/1197921
Title:
LibreOffice spreadsheet causes full Xorg cra
$ ls -l /dev/dri/
total 0
crw-rw 1 root video 226, 0 Apr 3 19:38 card0
crw-rw 1 root video 226, 64 Apr 3 19:38 controlD64
This seems to be normal. I also was not in the video group, however if I
add myself to the video group, logout and back in, then I don't have the
.xsession-errors an
Public bug reported:
I rebooted into up to date trusty and noticed Unity was incredibly slow.
I hadn't rebooted in a while, so I'm not sure what package caused the
issue, though I'm guessing it is mesa (I saw i965 pci ids were ifdef'd
in the Launchpad diff, but I didn't look super closely).
~/.xs
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1298446
Title:
Xorg crashed with SIGABRT
To manage notifications about this
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1299348
Title:
fglrx (not installed): fglrx kernel module failed to build
T
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1286162
Title:
[gm45] False GPU lo
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1286162
Title:
[gm45] False GPU lockup
Status: New
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Status: New => Triaged
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subsc
If I add this to the apparmor policy, it works:
/sys/devices/pci[0-9]*/**/uevent r,
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1286162
Title:
[gm45] False GPU lockup IPE
Hmmm, I did notice these two denials:
Mar 5 10:37:06 localhost kernel: [ 7375.981987] type=1400
audit(1394037426.321:300): apparmor="DENIED" operation="open"
profile="com.ubuntu.developer.jdstrand.blabble_blabble_0.2.1"
name="/sys/devices/pci:00/:00:02.0/uevent" pid=20162 comm="qmlscene
(available in the app store), the following environment is
set up by aa-exec-click (I ommitted the env vars that aa-exec-click
doesn't set):
APP_ID='com.ubuntu.developer.jdstrand.blabble_blabble_0.2.1'
LD_LIBRARY_PATH='/opt/click.ubuntu.com/.click/users/jamie/com.ubuntu.develo
Public bug reported:
I ran my click app on my desktop, and the desktop froze. It said
something about a libGL error, but I didn't capture the information
before restarting X.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
ProcVersionSignature:
I no longer use Ubuntu or that machine so I can't help.
--
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/677694
Title:
Firefox Crashes X
To manage notifications about this bug go to:
https
>From oss-security:
Please use CVE-2013-6424 for the issue in xorg-server
Please use CVE-2013-6425 for the issue in pixman.
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-6425
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-6424
--
You received this
** Changed in: pixman (Ubuntu)
Importance: Low => Medium
--
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/1197921
Title:
LibreOffice spreadsheet causes full Xorg crash with Anti-Aliasing
** Changed in: pixman (Ubuntu Precise)
Importance: Low => Medium
** Changed in: pixman (Ubuntu Quantal)
Importance: Low => Medium
** Changed in: pixman (Ubuntu Raring)
Importance: Low => Medium
** Changed in: pixman (Ubuntu Saucy)
Importance: Low => Medium
--
You received this bug
** Changed in: pixman (Ubuntu Precise)
Status: In Progress => Fix Committed
** Changed in: pixman (Ubuntu Quantal)
Status: In Progress => Fix Committed
** Changed in: pixman (Ubuntu Raring)
Status: In Progress => Fix Committed
** Changed in: pixman (Ubuntu Saucy)
Stat
FYI, the freedesktop.org bug is for pixman, not xorg. The xorg-server patch is
in patchwork:
http://patchwork.freedesktop.org/patch/14769/
but has not received comment from xorg yet. The CVE request CC'd
xorg_security, but the message is in moderation.
** Changed in: pixman (Ubuntu Precise)
I
Ritesh: oops, sorry, you did update the series file correctly (I was
comparing it to the Debian update which didn't use the quilt patch
system and got confused).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.
** Changed in: pixman (Ubuntu Precise)
Status: New => In Progress
** Changed in: pixman (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: pixman (Ubuntu Precise)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: pixman (Ubunt
CVE request: http://www.openwall.com/lists/oss-security/2013/12/03/8
--
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/1197921
Title:
LibreOffice spreadsheet causes full Xorg crash with Anti
Ritesh: one more thing, you add a quilt patch but the series file was
not updated.
--
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/1197921
Title:
LibreOffice spreadsheet causes full Xorg c
Ritesh, thanks for your patches! A couple of notes:
- these are security patches, so you should use -security instead of
-proposed
- I'm not sure if launchpad would autoclose a bug with 'lp: #1197921' in the
changelog, but that is non-conventional. You should use 'LP: #1197921' instead
- there is
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-joystick in Ubuntu.
https://bugs.launchpad.net/bugs/283399
Title:
[Intrepid] lshal output for different joystick, joy
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1225541
Title:
package fglrx-updates (not installed) failed to insta
** Information type changed from Private Security to Public
--
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/1215470
Title:
compiz
To manage notifications about this bug go to:
https://bugs.launc
** Summary changed:
- SDK applications require too many accesses on desktop with nvidia
+ SDK applications require /tmp access with nvidia (should honor TMPDIR)
** Description changed:
Nvidia desktop users need the following AppArmor permissions to avoid denials:
- owner /tmp/gl* mrw,
+ ow
I am going to add the following to the SDK template to silence the denial:
deny /tmp/gl* mrw,
This should still be fixed in nvidia*.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-tegra in Ubuntu.
https://bugs.launchpa
lso affects: nvidia-graphics-drivers-tegra3 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-tegra (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor-easyprof-ubuntu (Ubuntu Saucy)
Assignee: (unassigned) => Jamie Stra
** Information type changed from Private Security to Public
--
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/1194114
Title:
Xorg crashed with SIGABRT in DamageRegister()
To manage notifica
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
** Information type changed from Private Security to Public
--
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/1167670
Title:
Reporta un error de "xorg" paquete de ...
To manage notifications about
** Information type changed from Private Security to Public
--
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/1168248
Title:
Apport GPU error
To manage notifications about this bug go to:
https://
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Oh! I didn't realize. Both programs seem to work reliably.
Thanks for this workaround, Matthieu!
Nvidia GeForce 9600m GT with 304.84 Nvidia driver
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.la
The C program also hangs at the loop.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/535065
Title:
launcher icon corruption after wake-up from suspend
To manage notifications
The python script did not work for me. (Cinnamon 1.6.7 on Linux Mint 14)
it hangs in the loop.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/535065
Title:
launcher icon corru
** Information type changed from Private Security to Public
--
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/1131675
Title:
Xorg crashed with SIGABRT in raise()
To manage notifications abo
** Information type changed from Private Security to Public
--
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/1133061
Title:
Problem with graphics and OS speed
To manage notifications about this b
fwiw, qt5 is an evolution of qt4, so it doesn't need a new security
review. That said, we do *not* want to support qt4 and qt5 in 14.04 LTS
(and preferably sooner). Is there a plan to migrate supported packages
to qt5 so we can drop qt4 to universe?
** Changed in: qtbase-opensource-src (Ubuntu)
** Information type changed from Private Security to Public
--
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/1113404
Title:
bug
To manage notifications about this bug go to:
https://bugs.launchpa
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Ok, there is conflicting information in #18 and #20. I can say that
things seem to be working ok now (I have xserver-xorg-input-vmmouse
1:12.9.0-0ubuntu3 in the guest) after downgrading qemu-kvm to what is in
precise. I am going to mark this as fixed released.
** Changed in: xorg-server (Ubuntu)
1 - 100 of 445 matches
Mail list logo
