Drat, I meant to add this too:
Search keywords: linux mint switch user wrong resolution
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1757202
Title:
xubuntu / bion
I just had this problem on a Mint-19.3 XFCE upgraded from 18.3. For me,
the fix was:
* `sudo nvidia-xconfig`
* `sudo vi /etc/X11/xorg.conf`
The 'Section "Files"..EndSection' block already existed but was empty. I added
this:
Section "Files"
ModulePath "/usr/lib/nvidia-340/xo
Release: 18.04
I have uploaded two different videos showing what I see here:
https://youtu.be/S49cEC5DRsk
https://youtu.be/zSfi5ko5nBY
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/de
pportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jp 5422 F pulseaudio
/dev/snd/controlC1: jp 5422 F pulseaudio
/dev/snd/controlC2: jp 5422 F pulseaudio
CurrentDesktop: ubuntu:G
n: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jp 5422 F pulseaudio
/dev/snd/controlC1: jp 5422 F pulseaudio
/dev/snd/controlC2: jp 5422 F pulseaudio
CurrentDesktop: ubuntu:GNOME
D
n: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jp 5422 F pulseaudio
/dev/snd/controlC1: jp 5422 F pulseaudio
/dev/snd/controlC2: jp 5422 F pulseaudio
CurrentDesktop: ubuntu:GNOME
D
DRsk
https://youtu.be/zSfi5ko5nBY
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jp 5422 F pulseaudio
/dev/snd/controlC1: jp 5422 F pulseaudio
/dev/snd/contro
pportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jp 5422 F pulseaudio
/dev/snd/controlC1: jp 5422 F pulseaudio
/dev/snd/controlC2: jp 5422 F pulseaudio
CurrentD
tu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jp 5422 F pulseaudio
/dev/snd/controlC1: jp 5422 F pulseaudio
/dev/snd/controlC2: jp 5422 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroR
SS COMMAND
+ /dev/snd/controlC0: jp 5422 F pulseaudio
+ /dev/snd/controlC1: jp 5422 F pulseaudio
+ /dev/snd/controlC2: jp 5422 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=84a04536-72b0-461c-99b3-6d
tu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jp 5422 F pulseaudio
/dev/snd/controlC1: jp 5422 F pulseaudio
/dev/snd/controlC2: jp 5422 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroR
n: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jp 5422 F pulseaudio
/dev/snd/controlC1: jp 5422 F pulseaudio
/dev/snd/controlC2: jp 5422 F pulseaudio
CurrentDesktop: ubuntu:GNOME
D
tu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jp 5422 F pulseaudio
/dev/snd/controlC1: jp 5422 F pulseaudio
/dev/snd/controlC2: jp 5422 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroR
tu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jp 5422 F pulseaudio
/dev/snd/controlC1: jp 5422 F pulseaudio
/dev/snd/controlC2: jp 5422 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroR
n: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jp 5422 F pulseaudio
/dev/snd/controlC1: jp 5422 F pulseaudio
/dev/snd/controlC2: jp 5422 F pulseaudio
CurrentDesktop: ubuntu:G
Am attaching alsa-info text file generated using:
wget http://www.alsa-project.org/alsa-info.sh -O alsa-info.sh && bash
alsa-info.sh
** Attachment added: "alsa-info.txt.eKB9iEeGZf"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813604/+attachment/5233726/+files/alsa-info.txt.eKB9iEeGZf
Adding to linux source package as suggested in
https://wiki.ubuntu.com/DebuggingSoundProblems
** Tags added: kernel-sound
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Hello,
I'm getting kernel panic on m3.large with these AMI:
- ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20160420.3
(ami-840910ee)
- ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20160516.1
(ami-13be557e)
"Kernel panic - not syncing: Attempted to kill init!
exitcode=0x
Public bug reported:
failed to build in a HP Stream x360,
followed this thread: http://ubuntuforums.org/showthread.php?t=2259382
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: bcmwl-kernel-source (not installed)
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-
This is fixed in Ubuntu 15.10, see comment above about kernel 4.2
merging Valve's fixes. It only took 21 months.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
Looks like Valve's fix for this has been merged into mainline kernel
4.2:
http://lkml.iu.edu/hypermail/linux/kernel/1507.0/02047.html
so this bug will be fixed in Ubuntu when a release that uses kernel
>=4.2 happens.
I wonder if this bug would have been marked "Wishlist" if it had been a
mouse o
Pavel Rojtberg wrote:
> use the update xpad driver from SteamOS
As I wrote in the initial bug report, over a year ago:
> As best I can tell, the version of the xpad driver in the mainline kernel
> hasn't been touched in a few years.
> Valve, creators of Steam and SteamOS, have done work on the d
Still occurs in 14.10.
50% of the over 15000 people who took this survey said that "gaming and driver
improvements" should be a focus of future development for Ubuntu:
http://www.omgubuntu.co.uk/2014/10/ubuntu-10-years-user-survey-results
Valve has already fixed this issue, it would make a lot of
Does anyone know if Valve's fixes will be in the 3.16.3 kernel that
Ubuntu 14.10 is using?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1272765
Title:
Xbox 360 wireless controller ligh
Finally, if I turn off " Lock screen when going for suspend/hibernate"
on xfce4-power-manager, the bug don't appear (neither the screen
locker). It seem that it's the interaction between power-manager and
light-locker that triggers the problem. Note that if I lock the screen
and then suspend, I can
This bug only happens when closing the lid. Menu-chosen Suspend works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1288994
Title:
[Acer AOD255] hibernate/resume failure
Status in “li
Tried 3.14-rc6-trusty and 3.13.6-trusty. Same issue happens on hibernate
AND suspend.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1288994
Title:
[Acer AOD255] hibernate/resume failure
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1288994
Title:
[Acer AOD255] hibernate/resume failure
Status in “linux” package in Ubuntu:
Inc
Public bug reported:
On resume, the password window appear. After entering the password, the
screen turns black. No response. Consoles (tty1-6) are active.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-15-generic 3.13.0-15.35
ProcVersionSignature: Ubuntu 3.13.0-1
There was some movement on this issue in the past week, as Greg Kroah-
Hartman submitted some patches for the kernel that fix this bug:
http://thread.gmane.org/gmane.linux.kernel.input/33971
One argument for making this higher priority than Wishlist is that
digital game distribution service Steam
30 matches
Mail list logo