As for the wrongly detected driver version, can someone with an affected
NVidia system please attach /var/log/jockey.log after the failed
install? It should be in the target system, i. e. after reboot, not in
the live environment. It would also be helpful if you could give me the
output of
jocke
Quackers [2011-11-25 16:49 -]:
> I could install oneiric again and then post the outputs you request
> if you think that might help.
Either from oneiric or a precise install would be fine. It should tell
me more about why it selects the 173 driver. Thanks!
--
You received this bug notificati
** Package changed: udev (Ubuntu) => xorg (Ubuntu)
--
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/656673
Title:
Wireless mouse Logitech M305 sluggish
To manage notifications about this bug go t
Can you please give me the output of this command (from a Terminal):
python -c 'from NvidiaDetector.nvidiadetector import NvidiaDetection;
print NvidiaDetection().selectDriver()'
Thanks!
** Changed in: nvidia-graphics-drivers-173 (Ubuntu Precise)
Status: New => Invalid
** No longer aff
** No longer affects: consolekit (Ubuntu)
** No longer affects: modemmanager (Ubuntu)
** No longer affects: udev (Ubuntu)
** No longer affects: upower (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs
We don't configure two-finger scrolling by default, at least to my
knowledge. Chase, is that something we should get through multi-touch?
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) => Chase Douglas
(chasedouglas)
--
You re
@Chase: just assigned to you for a comment/investigation, feel free to
unassign of course.
--
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/894071
Title:
Mouse pointer does
** Changed in: lightdm (Ubuntu)
Milestone: oneiric-updates => ubuntu-12.04-beta-1
--
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/851612
Title:
Logging out from a FUS session does not
m both the cause and the solution now.
** Affects: libdrm (Ubuntu)
Importance: High
Assignee: Martin Pitt (pitti)
Status: Triaged
** Affects: libdrm (Ubuntu Precise)
Importance: High
Assignee: Martin Pitt (pitti)
Status: Triaged
** Also affects: li
** Summary changed:
- lucid->precise upgrade failure due to libdrm-nouveau1a Conflicts:
+ lucid->precise upgrade holds back X.org video drivers
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/902
On second look it doesn't seem to be that Conflicts:, it's something
else.
** Package changed: libdrm (Ubuntu Precise) => xorg (Ubuntu Precise)
** Changed in: xorg (Ubuntu Precise)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because
So, the reason is that xserver-xorg-video-{nv,v4l} do not exist any
more, and thus it can't get rid of the "xserver-xorg-video-6" provides.
For that we need to explicitly conflict to these two to clean these up
on upgrade. I propose that -nouveau conflicts: -nv, and -vesa Conflicts:
-v4l. Adding th
se) => xserver-xorg-video-nouveau
(Ubuntu Precise)
** Changed in: xserver-xorg-video-nouveau (Ubuntu Precise)
Assignee: (unassigned) => Martin Pitt (pitti)
** Also affects: xserver-xorg-video-vesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-v
Much easier solution: Promote the Breaks: for the old video ABIs to
Conflicts:. That will convince apt to actually remove the old drivers
instead of holding back the whole stack, and it will also do the right
thing in both the main/universe and main-only cases.
-vesa will provide a fallback on mac
** Tags added: rls-p-tracking
--
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/902077
Title:
lucid->precise upgrade holds back X.org video drivers
To manage notifications about this bug go
Indeed, the log says:
[ 96109.353] [mi] EQ overflowing. The server is probably stuck in an infinite
loop.
[ 96109.353]
Backtrace:
[ 96109.358] 0: /usr/bin/X (xorg_backtrace+0x26) [0x460566]
I don't know what that means; Bryce, do you?
** Changed in: xorg (Ubuntu)
Assignee: Canonical Deskt
Handing to Bryce as this is his project. Bryce, please let me know if
you need some hand with this, as conffile handling is a bit special.
Thanks!
** Changed in: xdiagnose (Ubuntu Precise)
Assignee: Ubuntu-X (ubuntu-x-swat) => Bryce Harrington (bryce)
** Changed in: xdiagnose (Ubuntu Precise
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) => Canonical
X.org (canonical-x)
--
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
*** This bug is a duplicate of bug 894486 ***
https://bugs.launchpad.net/bugs/894486
** This bug has been marked a duplicate of bug 894486
After a clean install the touchpad doesn't work untill rebooting xserver or
pc
--
You received this bug notification because you are a member of Ubun
When this happens, can you please give us the output of
gsettings list-recursively org.gnome.settings-
daemon.peripherals.touchpad
? In particular, I'm interested in whether touchpad-enabled flips to
false, which would be a gnome-settings-daemon misbehaviour.
Neither gnome-settings-daemon nor
I cannot reproduce this with doing a (partial) lucid->precise upgrade in
a lucid live system. However, I think I see one thing which could go
wrong:
/var/lib/dpkg/info/x11-common.preinst correctly does
if dpkg --compare-versions "$2" lt-nl "1:7.6+7ubuntu7"; then
remove_conffile_lookup x11-
It seems Bryce is on holiday, I'll just take this.
** Changed in: xdiagnose (Ubuntu Precise)
Assignee: Bryce Harrington (bryce) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubunt
state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
This shows that X.org does not yet know how to translate KEY_MICMUTE to
an X.org key name. Opening -evdev task for now, which is probably wrong
(xkb-data?).
** Package changed: acpi-support (Ubuntu) => xserver-xorg-input-evdev
(Ubunt
Opening task for gnome-settings-daemon as well. Once X.org passes an
actual key event, we need to handle it there to actually mute the
microphone.
** Package changed: gnome-control-center (Ubuntu) => gnome-settings-
daemon (Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Unde
Public bug reported:
If you upgrade from Ubuntu 12.04.x LTS to trusty, the upgrade fails
because of the various *-lts-{quantal,raring,saucy,trusty} packages.
There is currently no upgrade path, so you get in e. g.
https://jenkins.qa.ubuntu.com/view/Trusty/view/All/job/upgrade-ubuntu-
precise-tr
With https://launchpad.net/~canonical-x/+archive/x-staging it looks much
better, but there are still some problems:
Investigating (0) xserver-xorg-glamoregl-lts-saucy [ amd64 ] <
0.5.1-0ubuntu4.2~precise2 -> 3:1~ppa2 > ( oldlibs )
Broken xserver-xorg-glamoregl-lts-saucy:amd64 Depends on
xserver-
Tests with 3:1~ppa5, the previous two problems are now gone. This new
one appeared now, presumably due to some multi-arch confusion? I tested
lts-{quantal,raring,saucy} → trusty, same error on all of them:
The following packages have been kept back:
xserver-xorg-video-geode-lts-quantal:i386
Inv
Above tests were on amd64. On i386 the upgrade now works flawlessly with
3:1~ppa5. Thanks!
--
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/1278737
Title:
Upgrade to trusty fails from precise back
** Attachment added: "apt-get dist-upgrade output with debug for ppa5"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278737/+attachment/3977306/+files/debug.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bu
That's the full log for lts-raring → trusty i386 dist-upgrade with the
PPA enabled.
--
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/1278737
Title:
Upgrade to trusty fails from precise backported
Tested with 3:1~ppa7 now. On apt-get update you now get several dozen
warnings:
W: Unknown Multi-Arch type 'no' for package 'libdrm-dev-lts-quantal'
W: Unknown Multi-Arch type 'no' for package 'xserver-common-lts-quantal'
You probably meant "Multiarch: same"?
Other than that these have exactly t
Works nice now with ~ppa8, thanks!
--
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/1278737
Title:
Upgrade to trusty fails from precise backported enablement stacks
To manage notifications about
http://bazaar.launchpad.net/~auto-upgrade-testing-dev/auto-upgrade-
testing/trunk/revision/96
** Changed in: auto-upgrade-testing
Status: New => Fix Released
** Changed in: xorg-lts-transitional (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because yo
** Changed in: auto-upgrade-testing
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1280155
Title:
test for /usr/bin/xrandr w
Can you please be a little more specific how the keys misbehave? I. e.
which keys did you press, what did you expect to happen, what happened
instead? This isn't clear (at least to me, I'm not an X.org specialist)
from the xmodmap lines. Thanks!
** Package changed: systemd (Ubuntu) => xkeyboard-c
Done in https://launchpad.net/ubuntu/+source/xdiagnose/3.7.1
Thanks Didier!
** Package changed: systemd (Ubuntu) => xdiagnose (Ubuntu)
** Changed in: xdiagnose (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Jamie, Daniel, did you ever get this after the fix in bug 1302264? This
is the typical symptom of logind not working, so if you have that
situation can you please check for a logind crash /var/crash?
** Changed in: compiz
Status: Confirmed => Invalid
** Changed in: unity
Status: Con
systemd 219 is planned in about two weeks which will contain this.
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
Of course the hook needs to do some runtime detection (like checking the
equivalent of $DISPLAY) before it sets the tag.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to weston in Ubuntu.
https://bugs.launchpad.net/bugs/1418262
Title:
apport ho
I propose that weston (or another typical wayland package) ships
something like /usr/share/apport/general-hooks/weston.py (or wayland-
session.py perhaps) which does the appropriate detection, and does
report.setdefault('Tags', '')
report['Tags'] += ' wayland-session'
Does
So I was told that weston isn't actually installed; the wayland libs are
in sync with Debian, so we can also put it into apport. But I want to
point out that I cannot maintain that hook -- if the logic changes, I
depend on external contributors to update it for me.
** Package changed: weston (Ubun
That's pretty much exactly what the u-d-common tests are supposed to
detect -- the new kernel broke the -304 nvidia driver. I talked about
that to Alberto last week, but good to have a bug now.
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => Won't Fix
** Changed in: nvidia-gra
Right. For the record, the plan is to enable reverse test dependencies,
so that u-d-common can test-depend on the kernel and will be triggered
on new kernel uploads (https://bugs.debian.org/779559)
** Bug watch added: Debian Bug tracker #779559
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=7
Reassigning to X.org's evdev driver then. If evtest gets the correct
events, then kernel, keymaps, and evdev are alright, but it seems the
press events somehow get lost in X.org's input driver.
** Package changed: systemd (Ubuntu) => xserver-xorg-input-evdev
(Ubuntu)
--
You received this bug not
It's worth testing this with earlier kernels; do you have one where this
was known to work still? You shold still have some older kernels in the
grub boot menu, under "Advanced options".
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you a
Oh wait -- you are saying that the external monitor does not receive a
signal at any point in time? I thought the external monitor would stop
working *during/after* running dist-upgrade, and start working again
after a reboot.
That sounds like a kernel/video driver/X.org regression then,
reassign
This might actually be on purpose?
$ systemd-inhibit
[...]
Who: martin (UID 1000/martin, PID 2278/unity-settings-)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
I for one really welcome this. Finally my laptop stopped suspending when
it's sitting in the do
For the record, systemd actually checks for "docked/undocked" events, so
in a VT you should not actually get this behaviour. Only under Unity,
because unity-settings-daemon doesn't seem to check for dock events in
particular but just checks the connected monitors. Can you confirm this?
** Package
Public bug reported:
This was spotted by systemd's tests (which involve lightdm) starting to
fail. Cirrus cards (as provided by QEMU) still worked fine until at
least 2015-03-11 (https://jenkins.qa.ubuntu.com/job/vivid-adt-
systemd/119/), but started to fail now.
Start a current i386 vivid image
Didier kindly offered to work on the xdiagnose part. It's not yet clear
whether we also need to change lightdm.
** Changed in: xdiagnose (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
This is due to xdiagnose's
Requires=display-manager.service
OnFailure=failsafe-graphical.target
** Also affects: xdiagnose (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xdiagnose (Ubuntu)
Status: New => Triaged
** Tags added: systemd-boot
--
You received this bug
** Changed in: xdiagnose (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: lightdm (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1441883
** No longer affects: lightdm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1441883
Title:
15.04 Vivid Vervet won't boot after uninstalling lightdm
To manage notifications about
Closing udev task. As far as I can see, KEY_MICMUTE is being emitted
correctly, but X.org cannot handle this key.
** Changed in: udev (Ubuntu)
Status: Triaged => Invalid
** Changed in: udev (Ubuntu Raring)
Status: Triaged => Invalid
--
You received this bug notification because yo
** Package changed: udev (Ubuntu) => 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/763952
Title:
X200 tablet after screen rotation pointer x and y axis not changed
Ah right, turning from "invalid" to "fix released" then, sorry.
** Changed in: udev (Ubuntu)
Status: Invalid => Fix Released
** Changed in: udev (Ubuntu Raring)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscrib
The udev keymaps are correct. As I said, on the kernel level there is
only KEY_SLEEP (suspend to RAM) and KEY_SUSPEND (suspend to disk, aka
hibernate).
On the X.org level, /usr/share/X11/xkb/keycodes/evdev assigns to
KEY_SLEEP and to KEY_SUSPEND. /usr/share/X11/xkb/symbols/inet
then maps to XF
I don't know which particular part of KDE does power management,
starting with kdelibs for now.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1167869
Title:
KEY_SUSPEND should mean
BakLAN [2013-05-23 19:53 -]:
> Should I write the same report on bugs.kde.org?
That would be a good first step, as this affects all distributions.
KDE might want to add support for XF86Suspend.
Thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subs
Public bug reported:
As detected by ubuntu-driver-common's autopkgtest [1], current fglrx
fails to build on saucy.
-- 8< -
$ cat /var/lib/dkms/fglrx/9.010/build/make.logDKMS make.log for fglrx-9.010 for
kernel 3.9.0-2-generic (x86_64)
Wed May 29 06:19:36 UTC 2013
AMD kernel m
dino99, bug 1185253 seems unrelated to me. That doesn't fail because of
a missing version.h, that just simply needs porting to 3.9.
--
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/1185285
Copying info from my duplicate bug. This is perfectly reproducible
everywhere, so this is triaged.
As detected by ubuntu-driver-common's autopkgtest [1], current fglrx fails to
build on saucy.
-- 8< -
$ cat /var/lib/dkms/fglrx/9.010/build/make.logDKMS make.log for fglrx-9.01
This is not a duplicate. Bug 859101 appeared in oneiric already and is
about a completely different issue in the fglrx sources.
** This bug is no longer a duplicate of bug 859101
fglrx 2:8.881-0ubuntu2: fglrx kernel module failed to build (kernel includes
at ... not found or incomplete)
** Ch
Actually not, I'm sorry. Daniel mis-duplicated my report.
** Changed in: fglrx-installer (Ubuntu)
Status: Triaged => Confirmed
** Changed in: fglrx-installer-updates (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
w
Public bug reported:
Reproducer:
- create a fresh test user
- login as that user (Unity session)
- Open all things from the launcher
- Open the dash (I used the windows key)
- type "london", remove and add a few characters and wait a bit
- session crashes
ProblemType: Crash
DistroRelease: Ubuntu
** No longer affects: jockey
--
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/763331
Title:
There should be easy way to install VA-API helper packages
To manage notifications about thi
** Package changed: ubuntu-drivers-common (Ubuntu) => nvidia-graphics-
drivers-304 (Ubuntu)
** Package changed: nvidia-graphics-drivers-304 (Ubuntu) => nvidia-
graphics-drivers-310 (Ubuntu)
** Summary changed:
- Ubable to install proprietary Nvidia drivers with software-properties-gtk in
Quanta
** Package changed: ubuntu-drivers-common (Ubuntu) => fglrx-installer
(Ubuntu)
** Summary changed:
- 13.04: Reverting from fglrx in Additional Drivers results in unknown bad state
+ uninstalling fglrx results in unknown bad state
--
You received this bug notification because you are a member of
As gorgekara found out in the previous comment, the problem was that at
that time there was no fglrx driver available for current X.org. In
current Ubuntu releases it works again, so closing this.
** Package changed: ubuntu-drivers-common (Ubuntu) => fglrx-installer
(Ubuntu)
** Changed in: fglrx-
Removed the lot.
** Changed in: xf86-input-multitouch (Ubuntu)
Status: New => Fix Released
** Changed in: xserver-xorg-input-aiptek (Ubuntu)
Status: New => Incomplete
** Changed in: xserver-xorg-input-aiptek (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: xserver
I promoted the two.
** Changed in: libset-scalar-perl (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: libva (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libset-scalar-perl in Ubun
This needs to be fixed in xdiagnose's apport hook - ':' is an invalid
character in key names.
** Project changed: apport => xdiagnose (Ubuntu)
** Changed in: xdiagnose (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is sub
Since yesterday's dist-upgrade I'm getting
[ 4305.170] (EE) Error compiling keymap
(server-A24141C1DFD907420EB8836C380C7C1C62283A5E)
[ 4305.170] (EE) XKB: Couldn't compile keymap
errors in Xorg.0.log. Also, in qemu guests the keys are now totally
garbled, particularly the cursor keys, Home, et
Whoops, this is in apport after all -- xdiagnose's hook calls
apport.hookutils.attach_file_if_exists().
** Changed in: xdiagnose (Ubuntu)
Status: Triaged => In Progress
** Changed in: xdiagnose (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Package changed
Hello Jason, or anyone else affected,
Accepted llvm-toolchain-3.8 into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-3.8/1:3.8-2ubuntu3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
Hello Rachel, or anyone else affected,
Accepted xinit into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/xinit/1.3.4-3ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
Hello Christopher, 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.3-1ubuntu2.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pack
Please test the -proposed package, it blocks the next SRU that is
waiting in the queue. Thanks!
--
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/1566487
Title:
Container apps should use sam
The version of nvidia-settings-experimental-310 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of nvidia-settings-experimental-310 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of nvidia-settings-experimental-304 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of nvidia-settings-experimental-304 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The verification of the Stable Release Update for xorg-server has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
@Timo: Please explain what you tested, and for which releases. Don't
just flip the tag to v-done (this has bitten us several times in the
past already). Thanks!
** Tags removed: verification-done
** Tags added: verification-neededd
** Tags removed: verification-neededd
** Tags added: verification
Which Ubuntu version did that apply to? 2.4.67 is in both trusty- and
xenial-proposed. Also, if .67 is already on "the image" and does not fix
the bug, then this can't be verification of this SRU as this updates
*to* .67. Version 2.4.68 is only in yakkety.
--
You received this bug notification be
OK, thanks for the update. Releasing xenial, trusty still needs to be
tested.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1577735
Title:
Add missing SKL/BXT PCI-ID's
To manage notification
** Tags removed: verification-done
** Tags added: verification-done-xenial verification-needed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1577735
Title:
Add missing SKL/BXT PCI-ID's
To ma
I removed nvidia-graphics-drivers-340 340.96-0ubuntu3.16.04.1 from
xenial-proposed.
** Tags removed: verification-failed verification-needed
--
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.laun
Uploaded, thanks!
** Changed in: libxvmc (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxvmc in Ubuntu.
https://bugs.launchpad.net/bugs/1247502
Title:
Merge libxvmc 2:1.0.8-1 (main) from
The attached pm-suspend.log shows that quirks were not applied because
it detected the NVidia binary driver. Can you double-check with
/sys/power/state (see comment 12) to double-check?
But anyway, this was reported with the FGLRX and nvidia driver on
several systems, so this doesn't seem very har
s with both the proprietary NVidia
and FGLRX drivers (and possibly others).
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--
You received this bug notification because you are a member of Ubuntu-
** Changed in: fglrx-installer (Ubuntu)
Status: Opinion => Invalid
** No longer affects: pm-utils
** No longer affects: xubuntu-desktop
** Package changed: fglrx-installer (Ubuntu) => xscreensaver (Ubuntu)
** Changed in: xscreensaver (Ubuntu)
Status: Invalid => Triaged
--
You re
Thanks for this! Booting 12.04.2 in kvm or VB is indeed a real nuisance
(meaning: I didn't manage to get it to work at all), so this is highly
appreciated.
Sponsored, now needs ubuntu-sru to review. Removing sponsors
subscription.
** Changed in: libpciaccess (Ubuntu Precise)
Status: Triage
While Debian doesn't have arm64 yet, this patch would be harmless for
them and would allow us to stay in sync. Can you please forward it to
Debian? Thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.n
Sponsored the n-g-d precise patch into the SRU review queue. But please
update the SRU description how adding a desktop file in
/usr/share/applications is related to a missing libcuda1 and fixes build
failures. Thanks!
Unsubscribing sponsors.
** Changed in: nvidia-graphics-drivers (Ubuntu Precise
Jeremy, are you using logind now? If so, can you please re-test with the
very latest systemd and udev (175-0ubuntu24) from raring, as the latter
fixes ACLs on hotplugged devices?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-
Jeremy Bicha [2013-03-18 14:20 -]:
> I had manually installed systemd-services (libsystemd-daemon0) but not
> libpam-systemd. Removing systemd-services fixed my problem; an alternate
> fix that also worked was to install libpam-systemd.
Ah, thanks for confirming!
> pitti, should we have syste
oad
+ installing systemd-services without libpam-systemd loses device ACLs
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Also affects: systemd (Ubuntu Raring)
Importance: High
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) => (unassigned)
--
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
** Changed in: clutter-gtk-0.10 (Ubuntu Maverick)
Assignee: Canonical Desktop Team (canonical-desktop-team) => (unassigned)
** Changed in: clutter-gtk-0.10 (Ubuntu Maverick)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which
101 - 200 of 902 matches
Mail list logo
