This is fixed in mantic which just upgraded to the 0.13 release, but you
will also need to add amd_pstate=active to your kernel command line.
** Changed in: power-profiles-daemon (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
** Also affects: xserver-xorg-video-amdgpu (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-video-amdgpu (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: Fix Committed => Fix Released
** Chan
I believe this likely needs the VCN fixes from
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 backported.
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9728
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728
** Also affects: mesa (Ubuntu)
Importance: Undecided
** Also affects: mesa (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2 (Ubuntu
I think that this should be changed in gnome software not to try to
start fwupd then when in WSL2.
** Package changed: fwupd (Ubuntu) => gnome-software (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
ht
Mantic has 45~beta-1ubuntu1 which picks up the fix for this. Jammy is
still open.
** Changed in: gdm3 (Ubuntu Mantic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.la
** Description changed:
- The fbdev subsystem has been deprecated for a long time. We should drop
- it in favour of using simpledrm with fbdev emulation layer.
+ [ Impact ]
+ The fbdev subsystem has been deprecated for a long time. We should drop it in
favour of using simpledrm with fbdev emulat
Public bug reported:
[ Impact ]
VA-API decoding doesn't work on DCN 3.1.4.
Mesa 22.2.5 includes all the code to support it but is missing the chip ID.
The device ID was included in upstream mesa 22.3.1.
[ Test Plan ]
* Verify that VA-API works using "mpv" or a similar tool that uses VA-API
*
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xserver-xorg-video-amdgpu (Ubuntu Xenial)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Xenial)
Stat
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2017142
Title:
[jam
I believe the same thing can likely happen if llvm updates but mesa
stays the same. Can you embed both into the string?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
Title:
Afte
Public bug reported:
0.13
This release adds support for the AMD P-State driver that's been added to the
6.3 Linux kernel. This release also fixes mismatched profiles on some HP
laptops and some miscellaneous bug fixes.
** Affects: power-profiles-daemon (Ubuntu)
Importance: Undecided
Public bug reported:
In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
since upgrading to Noble I get the following trying to access it.
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
If I run this as root it wo
I managed to get it working as a user by manually starting pcscd.service
and with the following to force scdaemon to use it.
# cat ~/.gnupg/scdaemon.conf
card-timeout 5
disable-ccid
To me this seems to be a regression in behavior from 2.2.27-3ubuntu2.1
to 2.4.4-2ubuntu17.
** Bug watch added:
g
According to the upstream bug, this appears to be a new intended
behavior with newer gnupg2:
https://dev.gnupg.org/T6871
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/2061708
Title:
In this case the kernel is the "messenger" for the page fault. This is
more likely to be a mesa or application issue than a kernel issue.
Can you please raise a ticket to the upstream mesa bug tracker?
https://gitlab.freedesktop.org/mesa/mesa/
** Also affects: mesa (Ubuntu)
Importance: Undec
> NonfreeKernelModules: fglrx
Nothing that will be done in mesa for an issue with fglrx anyway these
days.
** Changed in: mesa (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubunt
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1987792
Title:
Totem and VLC crash when playing dvd with VAAPI radeon mesa dr
Random resets are "typically" triggered by mesa or application bugs.
Can you still trigger them in the latest mantic (which has a more up to
date mesa and kernel)?
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: New => Invalid
** Changed in: mesa (Ubuntu)
Status: New => In
Are you up to date on the current version of mesa in 23.10?
23.2.1-1ubuntu2?
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpa
I'd say that's very likely. That mesa upgrade just landed in the archive
a few days ago and the trace you reported looks more like how a mesa bug
manifests.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
You r
Also - can you still repro with mesa 23.2.1-1ubuntu2? This just landed
right after you reported this issue.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you ar
Ok in this case can you please open an upstream mesa bug?
** Changed in: mesa (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037641
Title:
The issue won't occur in Lunar. It's only specifically a problem with gdm when
a kernel has been configured this way.
It's not a problem in Jammy yet, but will be a problem when such a kernel gets
backported as HWE.
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Ne
Public bug reported:
[ Impact ]
When the kernel has been compiled with FB_EFI=n, FB_VESA=n, SIMPLEDRM=y a
series of events can occur that cause simpledrm to race with GDM. When GDM
loses the race then a user is left with a black screen.
This series of events doesn't currently happen in Jammy k
I've split up the GDM for Jammy change into
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2039757
** No longer affects: gdm3 (Ubuntu Jammy)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/
This is the upstream fix for this issue:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3324
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubunt
6.5.6 has the fix for preemption issue, it should get fixed when stable
updates come in Mantic.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2039868
Title:
amdgpu reset during usage of
*** This bug is a duplicate of bug 2034619 ***
https://bugs.launchpad.net/bugs/2034619
** This bug has been marked a duplicate of bug 2034619
[amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in
Wayland
--
You received this bug notification because you are a member
/+packages
I've also uploaded the mutter package into the proposed queue for SRU
team to look at.
** Changed in: mutter (Ubuntu Mantic)
Status: Fix Committed => In Progress
** Changed in: mutter (Ubuntu Mantic)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
conflict since they will be different binaries.
Please reject the *ubuntu4 version from the mantic-proposed queue and
accept the *ubuntu3.1 version (if it looks good).
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
You received this bug notific
#75
You can turn on proposed and then use ppa-purge command to remove my
PPA.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2034619
Title:
[amdgpu] gnome-shell gets SIGKILL'd when lo
Here is the upstream patch for this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent&id=38d54ecfe293ed8bb26d05e6f0270a0aaa6656c6
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=218003
Importance: Unknown
Status: Unknown
-
Please also take this fix at the same time for this same laptop. It
will fix s2idle for it.
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
drivers-x86.git/commit/?h=fixes&id=3bde7ec13c971445faade32172cb0b4370b841d9
** Changed in: libinput (Ubuntu)
Status: Confirmed => Inv
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2042054
Title:
22.04.3, zen 4 7840, screen turn white exception
Status in mesa package
It's unclear if this is a BIOS, mesa or kernel bug at this time, but
it's certainly not an Xorg bug as it was reproduced in Wayland.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2954
https://gitlab.free
From the upstream bug this is caused by PSR, so it's not a mesa issue.
** No longer affects: mesa (Ubuntu)
** No longer affects: mesa (Ubuntu Jammy)
** No longer affects: mesa (Ubuntu Lunar)
** No longer affects: mesa (Ubuntu Mantic)
** No longer affects: mesa (Ubuntu Noble)
--
You received
This should be a different issue than the mutter issue; please open it
up separately for investigation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2034619
Title:
[amdgpu] gnome-she
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Package changed: mutter (Ubuntu) => mesa (Ubuntu)
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
**
I've published a PPA here:
https://launchpad.net/~superm1/+archive/ubuntu/gitlab2971/+packages
This has builds both for 22.04 (Jammy) and 23.04 (Lunar). Please
upgrade to that, drop the module parameter and see if things improve.
# sudo add-apt-repository ppa:superm1/gitlab2971
# sudo apt upgrad
Can you please try to reproduce using a mainline upstream build?
https://kernel.ubuntu.com/mainline/v6.7-rc2/
If you can reproduce please share a new kernel log from a boot it
occurs.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xser
This is the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573
Here is a commit that fixes the issue by changing default pre-emption
policy since the kernel can't know about your mesa version.
https://github.com/torvalds/linux/commit/d6a57588666301acd9d42d3b00d74240964f07f
Is this happening possibly when there is a resolution change for the
eDP? If so, can you please try the latest linux-6.5.y kernel:
https://kernel.ubuntu.com/mainline/v6.5.13/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubun
OK thanks for clarifying. Can you please still try latest 6.5.13 and
6.6.6 and see if it happens in either of those?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amd
Public bug reported:
AMD testing of some Goodix MOC devices shows that this device fails to
work properly:
[ 208.586084] usb 1-2: New USB device found, idVendor=27c6,
idProduct=6496, bcdDevice= 1.00
The issue is specifically that there is a problem with the 'enroll create'
state.
It has been f
Closing it here as this is a firmware bug not a software bug.
** Changed in: power-profiles-daemon (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to power-profiles-daemon in Ubuntu.
https://bugs
This is a firmware or kernel bug, not a power profiles daemon bug.
Please report it to Lenovo to investigate the details.
** Changed in: power-profiles-daemon (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
Something I want to mention is that some drivers in the kernel and some
implementations of vendor's EC firmware internally handle AC vs battery
differently within a given platform profile. So you "automatically" get
a better power savings just going to battery compared to AC.
Thus I don't think t
Public bug reported:
The current version of power-profiles-daemon (0.13) has support both for
amd/intel pstate drivers as well as the ACPI platform profile drivers.
If the system supports both types of drivers then only the ACPI platform
profile driver gets used.
This doesn't do a great job as a
Do you have something in /usr/local perhaps? Or did you have a snap
installed for fwupd?
** Package changed: gnome-software (Ubuntu) => fwupd (Ubuntu)
** Changed in: fwupd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packag
https://launchpad.net/ubuntu/+source/power-profiles-daemon/0.20-1
** Changed in: power-profiles-daemon (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to power-profiles-daemon in Ubuntu.
https
It's marked failed to upload on all architectures right now:
INFOgir1.2-glib-2.0-dev_1.78.1-15_amd64.deb: Version older than that in the
archive. 1.78.1-15 <= 2.79.1-1
INFOgir1.2-glib-2.0_1.78.1-15_amd64.deb: Version older than that in the
archive. 1.78.1-15 <= 2.79.1-1
I guess that me
This should be fixed in Noble in power-profiles-daemon 0.20.
** Changed in: power-profiles-daemon (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to power-profiles-daemon in Ubuntu.
https://
Public bug reported:
Due to the "input deck" the Framework 16 has a "USB" internal keyboard.
This throws off heuristics for detection of keyboards to turn off when
you select disable touchpad when typing.
This is fixed in upstream libinput with the following change:
https://gitlab.freedesktop.org
Anyone still affected by this, can I please ask you to check the 0.21
release? It's been uploaded to Noble. I've also got it backported on a
PPA that can be used on Jammy or Mantic:
https://launchpad.net/~superm1/+archive/ubuntu/ppd
After upgrading if you're seeing this message still, can you p
That's great to hear!
I'll close this issue then since we have the newer version in Noble and a
wishlist bug to backport it to Jammy:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2008958
If anyone else encounters this again, please ensure you're on 0.21 and if you
are pl
I've updated the description to the SRU template. I do feel that this
meets the "other safe cases" section.
** Description changed:
+ [ Impact ]
+
+ power-profiles-daemon has the ability to make drastic improvements to
+ the power consumption of machines. This increases the likelihood of
+ th
At least from AMD's tests, backported mesa stack is working properly
with RDNA3. Adjusting tag accordingly.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of D
I tested 42.5-0ubuntu1 on a Z13 (which prompted the heuristics change)
and can confirm it's working with Wayland and the non-functional
resolutions are no longer offered.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
Yo
Public bug reported:
[Impact]
* Dell factory installed Linux systems are showing the partition "DIAGS" in
the Nautilus bar
* Also, Dell systems configured as a dual boot with Windows and Ubuntu 14.04.x
show the same behavior.
* This has been fixed in udisks2 upstream release 2.1.5
* This p
Yes, just added it. Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1455533
Title:
Dell systems showing "DIAGS" in Nautilus bar
Status in OEM Priority Project:
Incomplete
S
** Changed in: dell-sputnik
Status: New => Invalid
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1423415
T
** Changed in: dell-sputnik
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1416601
Title:
touchpad does not respond to t
The following two patches will resolve this issue:
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?h=for-next&id=e1e62b98ebddc3234f3259019d3236f66fc667f8
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?h=for-next&id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec
I reproduced this once, but it was while switching HDA and I2S modes, so
i'm suspecting that it might have been related to the default device
being selected. Are you still able to reproduce this on demand?
When I did reproduce it, xev did pick up keycodes, but no indicator in
the popup when they
Seth Forshee from Canonical has proposed a patch to LKML to fix this
behavior.
http://lkml.kernel.org/r/1424454311-70750-1-git-send-email-
seth.fors...@canonical.com
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification b
It's been merged upstream. Canonical, can you pull this in for vivid?
https://github.com/torvalds/linux/commit/6d00f37e49d95e640a3937a4a1ae07dbe92a10cb
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed t
I didn't do a proper bisect, but I have a variety of mainline kernels
from the mainline PPA I tried.
v3.16 works properly
v3.17 some rc's are using ps2 mode due to some i2c failure, others work properly
v3.18 works properly
v3.19-rc1 fails
v3.19-rc5 fails
v3.19-rc6 fails
Whenever someone does a p
Yes, nothing on 3.18
Originally I didn't test any of the stable releases for 3.18, it was the
standard 3.18, I believe the hash assigned to the tag 'v3.18'.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-vivid/
It would make sense to me if it was broken somewhere in between v3.18
and v3.18.
Based on posts at that community forum, it sounds like this should be
fixed in 3.16. Affected users can try to install linux-generic-lts-
utopic on 14.04 to see if it resolves the issue.
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
** Changed in: dell-sputnik
Status: New =>
*** This bug is a duplicate of bug 1286878 ***
https://bugs.launchpad.net/bugs/1286878
A patch for this was included in the factory image that hasn't yet been
merged into unity-greeter. I'll mark this as a duplicate of that bug.
** This bug has been marked a duplicate of bug 1286878
Doesn
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1170232
Title:
won't show login screen
Sta
For mythbuntu we're fine with removing those items, not needed in our
seed either.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1307485
Title:
Drop gnome-bluetooth to
I think it's likely the nvidia prime postrm script that did it.
snippet:
case "$1" in
purge|remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
# Remove the xorg.conf
if [ -f $xorg_conf ]; then
mv $xorg_conf $xorg_conf.$now
fi
** Also aff
Actually - nvidia-prime seems less likely now that I read gpu-manager
code. It's a "new" tool for upgrades, and consequently would run it's
enable_nvidia routine the first boot.
It checks how many cards are in the system, and if it only finds 1,
removes the old xorg.conf without making a new one.
** Package changed: nvidia-prime (Ubuntu) => ubuntu-drivers-common
(Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1307546
Title:
DPI really messed up after upgr
** Summary changed:
- DPI really messed up after upgrade
+ dist-upgrade from 12.04 -> 14.04 axes /etc/X11/xorg.conf
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is su
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => Confirmed
** Changed in: ubuntu-drivers-common (Ubuntu)
Milestone: None => ubuntu-14.04.1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ub
"Device0"
Monitor"Monitor0"
DefaultDepth24
Option "Stereo" "0"
Option "metamodes" "1920x1080 +0+0"
Option "SLI" "Off"
Option "MultiGPU" "O
bigwoof, Arjen: i'm encountering the same issue as you guys; I've filed a bug
here:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1308105
so that we can separate neuffer's issue and our issue.
Thanks!
--
You received this bug notification because you are a member o
For people on mythbuntu who encounter this with a mceusb remote, here's
how i'm working around it:
1) Save this file to /home/user/fix_tv_state.sh and make it executable
==
#!/bin/sh
#Fix TV state when HDMI link is lost.
#By Mario Limonciello
OUTP
"Stereo" "0"
- Option "metamodes" "1920x1080 +0+0"
- Option "SLI" "Off"
- Option "MultiGPU" "Off"
- Option "BaseMosaic" "off"
- SubSection
=
#!/bin/sh
#Fix TV state when HDMI link is lost.
#By Mario Limonciello
OUTPUT="HDMI-0"
BAD_MODE="1280x720"
GOOD_MODE="1920x1080"
for MODE in $BAD_MODE $GOOD_MODE; do
DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
sleep 2
done
** Patch added:
"0001-During-first-boot-don-t-remove-existing-xorg.conf.-L.patch"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1307546/+attachment/4087708/+files/0001-During-first-boot-don-t-remove-existing-xorg.conf.-L.patch
--
You received this bug notification be
I've come up with a patch for this and submitted a pull request.
https://github.com/tseliot/ubuntu-drivers-common/pull/8
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/130
Unfortunately that only means it was fixed in 14.10. It still needs to
be SRU'ed into 14.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1307546
Title:
dist-upgrade
** Description changed:
- Mythbuntu installs with an NVIDIA graphics card generally have a
- modified xorg.conf that sets the DPI to 100x100 so that it looks correct
- on a Television set.
+ [Impact]
+ * Upon upgrading to Ubuntu 14.04 from an earlier LTS release the user's
xorg.conf is renamed.
This appears to be fixed in libav in Trusty by now. The patch got
accidentally clobbered for mythtv, will add it back soon.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1263802
Title:
Before you reboot after doing the dist upgrade you should fetch that
package specifically from the proposed repository and install it. It will
run the first time you reboot after the upgrade.
On May 26, 2014 8:25 PM, "Michael Lueck" <1307...@bugs.launchpad.net> wrote:
> Based on #16, I submit the
Michael,
You can make an xorg.conf that doesn't functionally change anything for
example: http://askubuntu.com/questions/217758/how-to-make-an-xorg-conf-
file
After you make the xorg.conf and put it in place, reboot to make sure
the system still boots with it.
If it does, do the dist-upgrade, in
** Also affects: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1226101
Title:
12.04.3 Nvi
killed, it remains in the mode it was
previously running in.
Until this is fixed, this behavior can be worked around with a simple shell
script:
==
#!/bin/sh
#Fix TV state when HDMI link is lost.
#By Mario Limonciello
OUTPUT="HDMI-0"
BAD_MOD
** Changed in: gnome-session (Ubuntu)
Milestone: None => ubuntu-12.04-beta-2
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/936761
Title:
Mythbuntu upgrade from Lucid to Pre
Public bug reported:
Crashed when trying to do apt-get upgrade on a mythbuntu install
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: lightdm 1.1.4.is.1.1.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic i686
NonfreeKernelModules: nvidia
Ap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/947713
Title:
package lightdm 1.1.4.is.1.1.3-0ubuntu2 failed to install/upgrade:
subprocess installed post-installation script returned
The lightdm fix seems to have caused bug 947713.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working - two syndaemon instances
Are you calling /usr/lib/lightdm/lightdm-set-defaults in your postinst
for your lightdm theme? That's generally what needs to set the session
and greeter.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.la
** Changed in: mythtv (Ubuntu Quantal)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1013171
Title:
Many pack
Mythbuntu has transitioned to lightdm in the current development and
stable releases. We won't be fixing this in earlier releases. Won't
Fix for Mythbuntu task.
** Changed in: mythbuntu
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Deskto
At least to me this doesn't look like it's at all caused by a userspace
interpretation problem, it's caused only by this intel_backlight
interface. It's defaulting to the maximum value it can be set to
(4882).
* The button presses do actually translate into the values of
/sys/class/backlight/acpi
1 - 100 of 273 matches
Mail list logo
