i guess rebuilding gnome snaps with proposed on arm64 and testing that
new gnome snap on mantic for pi5 & x1s would help.
--
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/2037604
Title:
Backport
libcamera is not shipped on the images, and will be SRUed once tested.
** Changed in: pipewire (Ubuntu)
Status: Triaged => Invalid
** Changed in: libcamera (Ubuntu)
Milestone: None => mantic-updates
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I cannot tell if
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1923363 has FFe
or not for the uaccess addition on udev rules.
** Changed in: mesa (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
[ Impact ]
* HWE for Raspberry Pi 5 https://raspberrypi.com/5
[ Test Plan ]
* Private builds tested on all existing/supported Raspberry Pi SKUs in
armhf & arm64 variants
* No regressions on any existing SKUs
* Test that Raspberry Pi 5 boards work
[ Where problems
** Description changed:
Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
almost seven weeks past it's original release date. But at least we have
an rc3 which is "only" two weeks old. Yes, we are getting close to
mantic release but this series is something we want for
** Description changed:
Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
almost seven weeks past it's original release date. But at least we have
an rc3 which is "only" two weeks old. Yes, we are getting close to
mantic release but this series is something we want for
Specifically version 390.157-0ubuntu2 needs to be removed on i386 and
armhf
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2008434
Title:
NBS cleanup required in
Public bug reported:
NBS cleanup in lunar-proposed on i386 and armhf
old binaries left on i386: libcuda1-384, libnvidia-cfg1-390, nvidia-384,
nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390,
nvidia-headless-390, nvidia-headless-no-dkms-390,
** Summary changed:
- ftbfs with linux 5.16+
+ ftbfs with linux 5.16 & 5.17
** Description changed:
- ftbfs with linux 5.16+
+ [Impact]
- https://github.com/tseliot/nvidia-graphics-drivers/issues/44
+ * FTBFS from with 5.16 & 5.17 kernels
- Due to changes in the kernel w.r.t. stdarg.h
Public bug reported:
ftbfs with linux 5.16+
https://github.com/tseliot/nvidia-graphics-drivers/issues/44
Due to changes in the kernel w.r.t. stdarg.h and stddef.h includes.
** Affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
** Affects:
I can confirm that this freezing issue disappeared after changing the
motherboard – as well as another annoying issue where the screen would
suddenly start flickering, on/off every second or so.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Dell also changed the motherboard of the workstation last week. No more
freezing since that change, fingers crossed 爛
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1917037
Unfortunately, I still experience freezes after the GM107GL graphics
card exchange - perhaps less often but it's hard to tell.
The only positive outcome is the now silent operation of the
workstation.
I'll keep looking into the hardware side, but I'm back to square one, it
could be a software
I eventually contacted Dell support and was sent a new GM107GL graphics card
(under extended warranty). Double improvement:
* no more freezing (fingers crossed),
* much less noise from the workstation (although I had cleaned the fan with
compressed air).
It looks like a hardware issue, the
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4684/2021-10-12_16:41:27/impish_nvidia-
graphics-drivers-390_content.diff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
That also does not work, due to:
/var/lib/dkms/nvidia/390.144/build/nvidia-modeset/nvidia-modeset-linux.c:72:5:
note: in expansion of macro ‘do_div’
72 | do_div(result, 100);
./include/asm-generic/div64.h:245:36: error: passing argument 1 of ‘__div64_32’
from incompatible pointer
** Patch added: "lp1946642.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+attachment/5531917/+files/lp1946642.patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in
Testing in https://bileto.ubuntu.com/#/ticket/4681
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1946642
Title:
nvidia-graphics-drivers-390 ftbfs on armhf
To manage
That failed, missed one more place. Retesting.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1946642
Title:
nvidia-graphics-drivers-390 ftbfs on armhf
To manage
** Patch added: "lp1946642.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+attachment/5531904/+files/lp1946642.patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in
Testing patch in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4680
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1946642
Title:
Public bug reported:
nvidia-graphics-drivers-390 ftbfs on armhf
In file included from
/var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:16:
/var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c: In function
‘os_flush_cpu_write_combine_buffer’:
kernel-packages is now subscribed.
--
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] egl-wayland
To manage notifications about this bug go to:
Symbols tracking has been added in
https://launchpad.net/ubuntu/+source/egl-wayland/1:1.1.7-2 which is not
migrating as it is stuck behind glibc
ADT test is hard to provide => functional one needs nvidia graphics
cards that are not present in ADT; and compile test is equally hard
given that it is
I have opened an issue upstream, on freedkestop.org:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/551
** Bug watch added:
gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues #551
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/551
sshd_config is user modifyable and maintained. Some options can be
changed using dpkg-reconfigure openssh-server but otherwise changes to
it should be preserved.
Can you please provide steps to reproduce changes to sshd_config getting
lost?
--
You received this bug notification because you are
/boot/grub/grub.cfg is a generated file that must not be modified by
hand. Instead one is supposed to modify things like /etc/default/grub
/etc/default/grub.d/* /etc/grub.d/*
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
Public bug reported:
Just after the screen freezes, I am sometimes able to log in with SSH
and the log file typically reads:
Feb 26 11:18:15 is233895 kernel: [15385.625416] nouveau :01:00.0: fifo:
SCHED_ERROR 0a [CTXSW_TIMEOUT]
Feb 26 11:18:15 is233895 kernel: [15385.625436] nouveau
We could use gfxpalyload blacklist, to mark certain nvidia cards there.
And then gfxpayload will not be set to keep, and then vt.handoff will
not be appended.
See grub-gfxpayload-lists package, and files in /usr/share/grub-
gfxpayload-lists/blacklist/
My current preference would be the gdm3 fix.
However dropping vt.handoff is not regression free it may impact
flavours that use lightdm.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia]
Ubuntu no longer uses vt.handover and it should not be specified at all
anymore.
We boot directly to tty1, always and everywhere, and we should not be
setting that at all.
Thus a patch changing that from 7 to 1 is not a good idea for focal+.
And I can't quite remember which releases we have
** Also affects: systemd via
https://github.com/systemd/systemd/issues/14322
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-qxl in Ubuntu.
Public bug reported:
Please drop i386 dkms package, as there are no i386 kernel
Systems should enable amd64 archive and install amd64 kernel & the amd64
dkms package.
** Affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
@SRU team, actually we will cherrypick more things into systemd, to make
systemd & xkeyboard-config play nice with each other, as is destined to
be upstream and in disco.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xkeyboard-config (Ubuntu
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
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/1796822
Title:
Desktop live cd boots corrupted screen
I'm not sure about shipping above mentioned patch, due to:
- MODULE_LICENSE("MIT");
+ MODULE_LICENSE("GPL");
But i guess GPL is a superset of MIT
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Assignee: (unassigned) => Canonical Kernel (canonical-kernel)
--
You received this
Don't we need to cherrypick e.g.
https://devtalk.nvidia.com/default/topic/1026876/patch-for-387-34-and-
linux-4-15-0-rc1/
into all of them? Note that we need to SRU this back to xenial too, due
to hwe stack, no?
--
You received this bug notification because you are a member of Ubuntu-X,
which
FTBFS dkms module with 4.15 kernel:
/var/lib/dkms/nvidia-304/304.137/build/nv.c:3032:5: error: implicit declaration
of function ‘init_timer’; did you mean ‘init_timers’?
[-Werror=implicit-function-declaration]
init_timer(>rc_timer);
^~
init_timers
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1748000
Title:
Remove from the archive:
Ubuntu Bionic)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
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/1749199
Title:
purge conf files on removal of upstart (was session fails
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu Bionic)
Status: Triaged => Won't Fix
** Changed in: xorg (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
mesa is blocked, in addition to this bug, by other issues, and qtbase is
unrelated (e.g. migrating qtbase will not regress this further, nor fix
this issue). Thus removing block-proposed tag to migrate qtbase update.
** Tags removed: block-proposed
--
You received this bug notification because
why is this filed with "block-proposed" tag? Do you intend to prevent
mesa from migrating or qt? At the moment this bug is blocking qtbase
migration, which is a rebuild against openssl1.1 and I do not see how
that change can be related to this bug report.
--
You received this bug notification
led "vdpauinfo" on 2017-07-27, probably in order to investigate
this bug:
Start-Date: 2017-07-27 22:30:56
Commandline: apt install vdpauinfo
Requested-By: dimitri (1000)
Install: vdpauinfo:amd64 (1.0-1)
End-Date: 2017-07-27 22:31:01
So the updates responsible for this bug probably o
** No longer affects: systemd (Ubuntu Xenial)
** No longer affects: systemd (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1590590
Title:
Touchpad not
Should a fix for this be backported to 16.10 and 16.04?
Are there people who have the relevant hardware available, and are willing to
test the fix on both 16.10 and 16.04?
I do not have the hardware available, thus without available testers I would
not want to upload this fix.
--
You received
As far as I can tell the patch for hwdb sensitivity for Dell Latitude
E7470 is shipped in zesty now.
Is anything else required to have this resolved in zesty? Or hwdb update
is all that is needed here? If that is the case, then we can remove all
the other packages marked as affected and simply
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu)
Milestone: None =>
xserver-xorg-core-lts-xenial and systemd are now co-installable.
** 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-lts-xenial in Ubuntu.
https://launchpad.net/ubuntu/trusty/+queue?queue_state=1_text=
** Changed in: xorg-server-lts-xenial (Ubuntu Trusty)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server-lts-xenial in Ubuntu.
Public bug reported:
[Impact]
* With introduction of snapd/systemd in trusty, it has become impossible to
install xorg-server-lts-xenial simultaniously with snapd/systemd.
* In trusty, logind is managed by upstart, and is not restarted on upgrades,
therefore the protective breaks in
** Patch added: "trusty-systemd.patch"
https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724/+attachment/4802970/+files/trusty-systemd.patch
** Changed in: xorg-server-lts-xenial (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Also affects:
Public bug reported:
$ xdpyinfo | grep -B2 resolution
screen #0:
dimensions:3840x2160 pixels (1016x571 millimeters)
resolution:96x96 dots per inch
The pixels are right, the dimensions in millimeters are off the charts.
It's just a laptop.
ProblemType: Bug
DistroRelease: Ubuntu
Public bug reported:
Expectation:
fakeroot ./debian/rules tests
from ubiquity 17.04.1 package, from zesty-proposed to build
successfully.
It does in zesty-release. It does in zesty-proposed too, if one
downgrades: libgl1-mesa-glx libglapi-mesa
If one uses libgl1-mesa-glx libglapi-mesa from
It wasn't in 2013 =) now things look good.
** Changed in: mesa (Ubuntu)
Status: Incomplete => Fix Released
--
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/1246013
Title:
Would be nice
And for autopkgtests arguabily, one should be seeding/depending
installing on the right gl1 for the architecture, that are runnable on
autopkgtest machines.
Anyway, above change request should not regress bug 1374131
--
You received this bug notification because you are a member of Ubuntu-X,
It's not about dropping the dep, but changing it.
From: libgl1-mesa-dri
To: libgl1-mesa-dri | libgl1
Which should make it possible to create seeds, for touch, to not install
bogus and large/unused gl implementations
--
You received this bug notification because you are a member of
** Changed in: mesa (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => Timo Aaltonen (tjaalton)
--
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/1278871
Title:
please consider making lib
** Changed in: console-setup (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => Mathieu Trudel-Lapierre
(mathieu-tl)
** Changed in: console-setup (Ubuntu Trusty)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
** Changed in: ubiquity (Ubuntu)
Assignee: Dimitri John
** Changed in: libxfont (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxfont in Ubuntu.
https://bugs.launchpad.net/bugs/1522376
Title:
libxfont: FTBFS: dh_install: libxfont-dev missing files
Public bug reported:
Imported from Debian bug http://bugs.debian.org/806471:
5
** Affects: libxfont (Ubuntu)
Importance: Undecided
Status: New
** Affects: libxfont (Debian)
Importance: Undecided
Status: New
** Tags: s390x
** Bug watch added: Debian Bug tracker
uploaded xutils to fix the autoconf macro, to fix this build.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxfont in Ubuntu.
https://bugs.launchpad.net/bugs/1522376
Title:
libxfont: FTBFS: dh_install: libxfont-dev missing files
Public bug reported:
/var/log/upstart# cat failsafe-x.log
expr: non-integer argument
/usr/share/xdiagnose/failsafeXServer: line 87: [: -lt: unary operator expected
gdm: unrecognized service
stop: Unknown instance:
xinit /usr/share/xdiagnose/failsafeXinit /etc/X11/xorg.conf.failsafe
with-lightdm
@Norbert nrbrtx - please stop reproducing and commenting on this bug
report. This is bug is not fixed, and has status confirmed, thus
everyone knows that this was not fixed yet.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in
Please do not comment and continue to reproduce this bug. It has status
open, therefore it is known that it is not fixed yet. A developer should
upload a patch to fix close this bug report in the remaining
components that it is open against.
--
You received this bug notification because you are
I think this is hardware dependant as well. Since on my Ideapad Yoga i
never have mouse pointer appearing. Can we please disable the cursor
plugin and release it as SRU?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Public bug reported:
FTBFS with llvm 3.5, git master has a few commits to resolve build
failures.
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: ftbfs llvm-3.5
** Tags added: ftbfs llvm-3.5
** Changed in: mesa (Ubuntu)
Status: New = Confirmed
Public bug reported:
norbert xnox: http://packages.ubuntu.com/trusty/nvidia-current says
Transitional package for nvidia-current (try apt-cache search nvidia-
current yourself, to see the description), which is a circular
description; it should say [...] for nvidia-304
** Affects:
(In reply to comment #2)
Dimitri, would you be able to confirm this patch is ok for you?
Yes, the proposed patch works great for my use cases.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https
** Changed in: xkeyboard-config (Ubuntu Trusty)
Assignee: (unassigned) = Dimitri John Ledkov (xnox)
** Changed in: xkeyboard-config (Ubuntu Trusty)
Milestone: None = ubuntu-14.04.2
** Changed in: ubiquity (Ubuntu Trusty)
Milestone: None = ubuntu-14.04.2
** Changed in: xkeyboard
** Changed in: ubiquity (Ubuntu Trusty)
Assignee: (unassigned) = Dimitri John Ledkov (xnox)
** Changed in: console-setup (Ubuntu)
Assignee: (unassigned) = Dimitri John Ledkov (xnox)
** No longer affects: ubiquity
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) = Dimitri
** Changed in: xkeyboard-config (Ubuntu Trusty)
Assignee: Dimitri John Ledkov (xnox) = Maarten Kumpen (maarten)
** Changed in: console-setup (Ubuntu Trusty)
Assignee: (unassigned) = Dimitri John Ledkov (xnox)
** Changed in: console-setup (Ubuntu Trusty)
Status: Incomplete = Confirmed
Maarten Lankhorst, proposed the following sample patch. Can you please
forward it upstream and/or upload into ubuntu? it appears to do what we
need/want for at least some languages.
** Changed in: xkeyboard-config (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
**
)
MarkForUpload: True
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
** Changed in: ubiquity (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) = (unassigned)
** Changed in: ubiquity (Ubuntu Trusty)
Assignee: Dimitri John Ledkov (xnox) = (unassigned
Once upstream supports it, and xkeyboard-config supports it, we can
modify console-setup and ubiquity to support Super+Space key combos.
** Changed in: xkeyboard-config (Ubuntu Trusty)
Status: Confirmed = Incomplete
** Changed in: xkeyboard-config (Ubuntu)
Assignee: Maarten Lankhorst
The video to me looks like gdm never starts...
** Also affects: gdm (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/1307776
Title:
screen
being installed
** Affects: mesa (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: Confirmed
** Affects: qtdeclarative-opensource-src (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: Confirmed
** Also affects
** Also affects: libxi (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libxi (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: unity (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: libxi (Ubuntu)
Status: New =
Please correct apt-pinning levels on the affected system.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxi in Ubuntu.
https://bugs.launchpad.net/bugs/1267665
Title:
Unable to upgrade Unity due to libxi6 dependency
To manage
= Incomplete
** Changed in: unity (Ubuntu Precise)
Status: New = Invalid
** Changed in: libxi (Ubuntu Precise)
Assignee: (unassigned) = Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxi in Ubuntu.
https
** Attachment added: xorg-is-not-official.png
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1262856/+attachment/3932785/+files/xorg-is-not-official.png
** Tags added: precise
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg (Ubuntu
The package xorg is installed on the CD and is the same as the latest
on available in precise-updates pocket, 1:7.6+12ubuntu2
--
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/1262856
Title:
after executing apt-get update, I was able to report bug against xorg.
** Changed in: xorg (Ubuntu Precise)
Status: New = Invalid
** Changed in: xorg (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The cdrom is 12.04.3 LTS amd64 20131216
--
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/1262856
Title:
cannot report xorg bug in precise daily image
To manage notifications about this bug go
** Attachment added: broken-resolution.png
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1262860/+attachment/3932812/+files/broken-resolution.png
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
Public bug reported:
On live session in precise daily images there are resolution bugs in particular:
* the unity-panel launcher appear to be is squeezed thiner than suppose to
The background appears to be not-distored in the same manner, although
it's hard to tell, given how abstract it is.
Well... as stated in #34 status us set to Fix released for gtk+3.0, but
what about Saucy users? Do we have to move on using Trusty to get this
bug fixed?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Public bug reported:
Failure to work with multiple workspaces
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CompizPlugins:
Public bug reported:
Executing this script crashes the X-Server
#!/bin/sh
xinput --create-master A1
xinput --create-master A2
xinput --create-master A3
xinput --create-master A4
xinput --create-master A5
xinput --create-master A6
xinput --create-master A7
xinput --remove-master A1 keyboard
--
xinput crashes X-Server after adding and removing pointers
https://bugs.launchpad.net/bugs/681626
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
___
Mailing list:
with blank screen and
didn't respond for any key. :(
The same applies to me, I tried the instructions Renate posted, but no
successful wakeup ...
Dimitri
--
[RC410] Xpress 200M hangs when resuming from suspend with DRI
https://bugs.launchpad.net/bugs/305301
You received this bug notification
I just tried that version of the kernel: resuming from suspend stills
hangs my machine...
Dimitri
On 10/14/2009 08:25 PM, Tormod Volden wrote:
Has anyone tried 2.6.32-rc4 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/ ?
--
[RC410] Xpress 200M hangs when resuming from suspend
Not for me. Last time I suspended and resumed successfully, it was with
fglrx.
Dimitri
On 10/14/2009 02:20 PM, Tormod Volden wrote:
Did suspend/resume ever work on an RC410 card with the radeon driver and
DRI enabled?
Not that it helps you, but the same issue for my X700 card (comment 45
--
[RC410] Xpress 200M hangs when resuming from suspend with DRI
https://bugs.launchpad.net/bugs/305301
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
___
Mailing
94 matches
Mail list logo
