** Changed in: mesa (Ubuntu Focal)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: mesa (Ubuntu Hirsute)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
** Changed in: mesa (Ubuntu Focal)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: mesa (Ubuntu Hirsute)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Timo, please can you take care of this one, sounds like a regression?
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: xorg-server (Ubuntu Focal)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: xorg-server (Ubuntu
Sean, can you provide a debdiff for amdgpu please? I'm happy to sponsor
it if you do that, ping me on IRC or something.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Hello Mahmoud, or anyone else affected,
Accepted xserver-xorg-input-libinput into hirsute-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/xserver-xorg-input-libinput/0.30.0-1ubuntu1 in a few hours, and then in
the -proposed repository.
Please help
thanks. Timo, could you SRU this one please?
** Also affects: xserver-xorg-input-libinput (Ubuntu Hirsute)
Importance: High
Status: Triaged
** Changed in: xserver-xorg-input-libinput (Ubuntu Hirsute)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Tags removed:
assigning to timo for better tracking
** Changed in: mesa (Ubuntu Hirsute)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: ubiquity (Ubuntu Hirsute)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which
This came up on our tracking report for the desktop team, but we're not
clear what is required in libxcb/amdgpu vs. a fix in the WMs themselves.
Can someone clarify please?
** Changed in: libxcb (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: libxcb (Ubuntu Focal)
Status:
ACK, go for it (with 11 for now, I agree that switching to an RC
compiler feels dodgy)
** Changed in: mesa (Ubuntu)
Status: New => Triaged
** Changed in: mesa (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Tags removed: rls-ff-incoming
--
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/1873052
Title:
Showing two cursors after login
To manage notifications about this bug go to:
Already said on IRC, but mentioning here for other RT members:
I'd like to see (1) an analysis of the risks of this update, and (2) a
description of what testing you've done, please.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
** Changed in: xdg-desktop-portal-kde (Ubuntu)
Status: New => Fix Released
** Changed in: xdg-desktop-portal-gtk (Ubuntu)
Status: New => Fix Released
** Changed in: xdg-desktop-portal (Ubuntu)
Status: New => Fix Released
** Changed in: weston (Ubuntu)
Status: New =>
Yeah, makes sense. Happy to approve this.
--
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/1896475
Title:
[FFe] Migrate to pipewire-0.3
To manage notifications about this bug go to:
w
** Also affects: nvidia-graphics-drivers-440 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gdm3 (Ubuntu Focal)
Status: New => In Progress
** Changed in: gdm3 (Ubuntu Focal)
Assignee: (unassigned) => Iain Lane (laney)
** Changed in: gnome-session (Ubu
I've sponsored the debdiff to bionic's queue
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxau in Ubuntu.
https://bugs.launchpad.net/bugs/1559650
Title:
gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
To manage notifications
Thanks Timo. We've discussed this at the release sprint, and we think
it's a bit late for the release itself I'm afraid.
If you think this is something that should be in focal, please re-
purpose this bug as an SRU and re-upload.
Łukasz is looking at the packages in focal-proposed already
(also, ~ubuntu-release wasn't subscribed to this; done now)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to vulkan-validationlayers in Ubuntu.
https://bugs.launchpad.net/bugs/1871754
Title:
FFE: update vulkan to 1.2.135
To manage
Please give us some more information to be able to judge this freeze
exception request.
Like, what's the risk / impact, what testing have you done? Why do we
need this feature in 20.04?
I'm going to reject the pending packages in the queue for now. If
approved they can be re-synced.
--
You
Thanks for being diligent, but *feature* freeze exceptions are not
needed for bugfix releases.
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Also affects: mesa (Ubuntu Focal)
Importance: Undecided
Status: Confirmed
** Changed in: mesa (Ubuntu Focal)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Tags removed: champagne
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Rationale for high: if you hit this bug, you cannot log in to a desktop
system, since logind can't access the DRM device nodes
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The messages Daniel found in comment #4 indicate a systemd issue that I
fixed upstream a few months ago. I'm sorry, I thought we already had the
fix in Ubuntu but it seems we don't - it's in v245.
We need the commits
625077264ba01a108386eeea733ee244e6b7ff14
I was getting random freezes on a Dell Latitude E7450 with Intel HD
Graphics 5500, with no hints as to the cause in logs that I could find.
Freezes could happen multiple times a day when in heavy use, but often
more like once a week. I followed the advice in #42 a month ago and have
had no freezes
what testing has happened / what are the risks?
--
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/1818516
Title:
FFe: Mesa 19.0.x for disco
To manage notifications about this bug go to:
(Those tags just make the bug drop off our desktop team report, don't
worry about it)
** Tags added: rls-cc-notfixing rls-dd-notfixing
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Tags removed: rls-cc-incoming
--
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/1754693
Title:
Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from
** Also affects: mesa (Ubuntu Disco)
Importance: High
Status: Confirmed
** Also affects: xorg-server (Ubuntu Disco)
Importance: High
Assignee: Timo Aaltonen (tjaalton)
Status: Confirmed
** Also affects: mesa (Ubuntu Bionic)
Importance: Undecided
Status: New
**
** Changed in: mesa (Ubuntu Bionic)
Assignee: (unassigned) => 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/1770271
Title:
VegaM support
To manage notifications
** Changed in: mesa (Ubuntu Bionic)
Assignee: (unassigned) => 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/1714178
Title:
Triple 4K monitor display failed
** Changed in: mesa (Ubuntu Bionic)
Assignee: (unassigned) => 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/1798597
Title:
Backport packages for 18.04.2 HWE stack
** Tags added: rls-cc-incoming
--
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/1754693
Title:
Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from
** Tags removed: rls-cc-incoming
--
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 in Virtualbox on Bionic
To manage notifications
that mesa is now on the latest ISOs, and apparently doesn't fix it after
all
--
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/1792932
Title:
Cosmic Desktop fails to boot in vbox: Xorg
They're all uploaded now. To the SRU team - these are quite delicate
SRUs. I think they're right, but more eyes would be appreciated.
The essence is that when nux-tools is removed-not-purged at a buggy
version, the leftover conffile is harmful. So we picked a core package,
x11-common, and made it
** Changed in: xorg (Ubuntu Artful)
Status: Confirmed => In Progress
** Changed in: xorg (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
> Well, I just wanted to make sure this happened as early as possible,
since this is not related to what the package installs, I thought it was
better to handle this in preinst, so that this can be also just removed
at later times.
The thing about the preinst is that it runs super early, you
** Changed in: mesa (Ubuntu Bionic)
Assignee: (unassigned) => 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/1776499
Title:
Crash in libegl-mesa0 due to out of
Cheers!
My nux-tools review comments apply to x11-common too. The following are
for x11-common:
What's the reason for doing this in preinst rather than postinst
configure? It's fine in this case but usually we do things in postinst
where possible.
What about adding a "Breaks: nux-tools (<<
Marco, I don't think there is a solution that satisfies all the
requirements and doesn't involve nux cooperating in some way. I've given
you mostly-working debdiffs now - can we please move forward with them?
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Patch added: "mesa.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5152448/+files/mesa.debdiff
--
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/1768610
Title:
This is the solution that I proposed to you in private. It is a fix to
mesa (a "common" package) and a followup to nux-tools.
It needs some testing. In particular I don't think I picked the right
mesa package to use, and we also need to check with the mesa maintainer.
There are various version
** Patch added: "nux.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5152447/+files/nux.debdiff
--
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/1768610
Title:
(you can reassign that task from mesa to something else if it's going to
be fixed elsewhere)
--
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/1768610
Title:
leftover conffile forces GNOME is
I'm adding a mesa task, as this bug also needs to be fixed for people
who *already* removed the package without purging it. I suggest mesa,
because that's the package that LIBGL_ALWAYS_SOFTWARE=1 acts on
(mostly?) - so fixing it there will fix for everybody whereas ubuntu-
desktop or whatever
** Changed in: libglvnd (Ubuntu Bionic)
Assignee: (unassigned) => 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/1772607
Title:
Mesa 18.0.5 stable release
To
** Changed in: libglvnd (Ubuntu Bionic)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1770913
Title:
Software rendering is forced
That tag means we don't track this as a desktop team commitment, please
feel free to still fix the bug though if it's still relevant.
** Tags added: rls-bb-notfixing
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
** Also affects: mesa (Ubuntu Bionic)
Importance: Medium
Assignee: Timo Aaltonen (tjaalton)
Status: Triaged
** Also affects: wayland (Ubuntu Bionic)
Importance: Medium
Status: Invalid
** Also affects: gdm3 (Ubuntu Bionic)
Importance: Medium
Status: Invalid
**
For me this bug made xorg fail to start completely
--
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/1748926
Title:
From 1.19.6 on, X treats every device as an input device
To manage
02/10 15:15:18 GunnarHj: sorry about that - looks OK to me, feel
free to merge the pkg with Debian (that's the only change there)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
Uploaded the cherry-picked patch
** Changed in: libinput (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1715479
Title:
Touchpad won't stay
I'm really worried about doing this so late.
But if you're willing to take the risk, if you will keep a close eye on
incoming bug reports & errors.ubuntu.com and if you will upload very
soon, go ahead.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Ok apparently it's low risk, so go ahead.
--
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/1655782
Title:
[FFe] Elfdalian layout + merge with Debian 2.19-1
To manage notifications
s/something/someone/!
--
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/1655782
Title:
[FFe] Elfdalian layout + merge with Debian 2.19-1
To manage notifications about this bug go to:
Yeah, I can see the changes, I just don't know how to assess the impact
of them or likely regression potential. I'll ask Timo or something to
help me out. :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
I don't know what the regression potential of new xkeyboard-config
releases is... can you give a bit more detail? What's in the release and
how safe is it?
Assuming it is, I think it should be okay in principle. I didn't look at
this particular proposed package from a sponsorship POV to know if
Uploaded
** Changed in: nautilus (Ubuntu)
Status: Confirmed => In Progress
** Changed in: nautilus (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: nautilus (Ubuntu Yakkety)
Status: New => In Progress
--
You received this bug notification because you are a
** Description changed:
+ [ Description ]
+
+ Nautilus's wallpaper drawing doesn't respond to changes in monitor
+ configuration. Instead of your wallpaper you see black.
+
+ [ Fix ]
+
+ Inside nautilus, the wallpaper widget connects to GTK's "monitors-
+ changed" signal when it is
I'm fixing this by explicitly calling the signal handler once if the
widget is already realized when we connect the signal.
--
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/1626935
Title:
Yakkety)
Importance: Undecided
Status: New
** Also affects: compiz (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: nautilus (Ubuntu)
Assignee: (unassigned) => Iain Lane (laney)
** Changed in: nautilus (Ubuntu Yakkety)
Assignee: (unassigned) => Iai
Don't have the full dkms log any more, but this is from apt.
Setting up nvidia-304 (304.131-0ubuntu2) ...^M
update-alternatives: using /usr/lib/nvidia-304/ld.so.conf to provide
/etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto
mode^M
update-alternatives: using
Public bug reported:
I just installed "nvidia-current", which was probably an error (I'm now using
-352) but nevertheless it couldn't be loaded into my 4.3 kernel, on xenial.
Jan 05 12:10:54 raleigh.local kernel: mtrr: no MTRR for f100,e0 found
Jan 05 12:10:55 raleigh.local kernel:
Public bug reported:
problem happened after a software update. also now missing openGL
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx-core 2:15.200-0ubuntu0.3
ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
*** This bug is a duplicate of bug 1474154 ***
https://bugs.launchpad.net/bugs/1474154
** This bug has been marked a duplicate of bug 1474154
Update to 0.1.4
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-qxl in
This bug was fixed in the package x11proto-randr - 1.5.0-1
Sponsored for Artur Rona (ari-tczew)
---
x11proto-randr (1.5.0-1) unstable; urgency=medium
* New upstream release.
* control: Bump policy to 3.9.6, no changes.
* Add Dave Airlied's key to the keyring.
-- Timo Aaltonen
Hi Christopher, sorry for the delay, but I ended up ditching the
netbook, switching to a System76 laptop. It eventually reached the
point where I needed something more powerful to work on.
I can certainly try booting the machine again and loading on 15.04, but
that will take some time.
--
You
Public bug reported:
I noticed this morning that after I logged in unity-settings-daemon was
getting an assertion failure.
ERROR:gsd-rr-config.c:661:gsd_rr_config_load_current: assertion
failed: (gsd_rr_config_match (config, config))
** (unity-settings-daemon:2293): WARNING **: Attempted to
** Also affects: xserver-xorg-video-intel (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** No longer affects: xserver-xorg-video-intel (Ubuntu Utopic)
--
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/1447143
Title:
[SKL, i915_bpo] Rotation doesn't work
To manage
Thanks, I uploaded it to utopic-proposed.
There's another SRU (4.3) still awaiting verification, but tjaalton
tells me that it is fine. If you're an SRU team member reviewing this
upload and he hasn't fixed the tags yet, please poke him hard and then
you should be able to release that one and
Public bug reported:
I just restarted and now neither of these work. If I open up xev and
perform these actions on there then there's no output. I tried to toggle
the settings in unity-control-center too.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
Seems like it's some bug that they break after you interact with the
settings in the control centre
--
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/1438774
Title:
Tap to click and two finger
Public bug reported:
Screen locks up under certain scenarios.
May be a red herring but mostly seems to occur:
- Running a cpu or memory intensive process (Have 3.5GB RAM, 3.5GB Swap
on SSD. Freezes occur even when swap not in use, also has occurred
within minutes of booting up)
- Shortly
** Changed in: xserver-xorg-video-openchrome-lts-saucy (Ubuntu)
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/1205643
Title:
VIA
It sounds reasonable. Please could you subscribe to bug reports and
watch out for problems coming up. Ack.
** Changed in: mesa (Ubuntu)
Status: New = Triaged
** Changed in: mesa (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of
Thanks, I committed the e-d-s fix to bzr so it should be in the next
upload. Unsubscribing sponsors since there's nothing left here to
sponsor.
** Changed in: evolution-data-server (Ubuntu Trusty)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a
Public bug reported:
During latest alpha 14 update X11 dropped to shell half way through
installation and then froze. Rebooting resulted in cursor only with no
startup. Rebooted to recovery and ran dpkg which then carried on
installing the update packages, some issues over Nvidia driver/module
Public bug reported:
Screen tearing during high fps playback using latest 3.13Kernel update
with Nvidia 331.20. Not evident with 3.12Kernel. (Now running
3.12Kernel). No other system changes.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu7
ProcVersionSignature: Ubuntu
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = New
--
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/1234027
Title:
FFe: new upstream release
Seems bug fix only. Please go ahead.
--
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/1234027
Title:
FFe: new upstream release 2.99.903
To manage notifications about this bug
alternate build-depends don't really work - we always choose the first
one. So I removed your first option we'll use nvidia-current (please
file another request if this should be changed). I also fixed the PPA
version number. I'll now upload. Thanks!
--
You received this bug notification
On Wed, Aug 21, 2013 at 08:21:35AM -, Oibaf wrote:
Iain Lane, can you have a look at this? This is possibly related to your
last change to the package.
I don't think it is, but I can still fix this bug for you, sure.
assignee laney
status inprogress
--
Iain Lane
Uploaded a no-change rebuild of libx11 to precise, thanks
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/408903
Title:
Does not handle microphone mute button (KEY_MICMUTE)
To manage
Unsubscribing sponsors as Timo indicates he is handling this
--
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/1112147
Title:
gbm_dri_bo_create fails to initialize bo-base.base.format
To manage
Sounds totally sane to me. Get it uploaded before the weekend and
someone can push it through the freeze.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Visibility changed to: Public
--
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/1034944
Title:
Xorg crashed with SIGABRT in FreeResource()
To manage notifications about this
*** This bug is a duplicate of bug 993506 ***
https://bugs.launchpad.net/bugs/993506
Public bug reported:
Cannot build the module on 3.4 kernels using dkms
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: nvidia-current 295.49-0ubuntu1
ProcVersionSignature: Ubuntu
*** This bug is a duplicate of bug 993506 ***
https://bugs.launchpad.net/bugs/993506
--
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/999365
Title:
nvidia-current
*** This bug is a duplicate of bug 993506 ***
https://bugs.launchpad.net/bugs/993506
from make.log:
/var/lib/dkms/nvidia-current/295.49/build/nv-linux.h: At top level:
/var/lib/dkms/nvidia-current/295.49/build/nv-linux.h:114:75: fatal error:
asm/system.h: No such file or directory
I've indeed now seen this failure mode too. I'll try and get some time
over the next days to do some debugging.
My first thought is that the patch resets the state on suspend (when the
device is disabled). Perhaps there is a similar interaction when the lid
is opened and the device reenabled.
Is
Removed SUSPEND_MODULES hack, installed, rebooted and verified that it
all works correctly.
Thanks very much for the proper fix!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
** Also affects: xserver-xorg-input-synaptics (Ubuntu Precise)
Importance: High
Status: Triaged
--
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/968845
Title:
Do we have any chance of seeing this fixed in Precise? It's not really
great to break suspend for these users. Can the package (what package is
it?) ship a pm-config.d snippet for the SUSPEND_MODULES workaround to at
least make the situation tenable? We could release note the fact that
it's just
I get this on every third resume from suspend or so. I'll get debugging
output next time.
** Package changed: synaptic (Ubuntu) = xserver-xorg-input-synaptics
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics
Sorry, I failed. I tried evtest using
/dev/input/event5:Apple Inc. Apple Internal Keyboard / Trackpad
which seems like the only plausible option to me.
I need someone to tell me how to debug this. The laptop is a Macbook Pro
7.1.
** Also affects: linux (Ubuntu)
Importance: Undecided
apport information
** Attachment added: AcpiTables.txt
https://bugs.launchpad.net/bugs/976198/+attachment/3029679/+files/AcpiTables.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/976198/+attachment/3029680/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not
found.
DistroRelease: Ubuntu 12.04
HibernationDevice:
apport information
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/976198/+attachment/3029681/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: ArecordDevices.txt
https://bugs.launchpad.net/bugs/976198/+attachment/3029682/+files/ArecordDevices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
1 - 100 of 179 matches
Mail list logo