Hello Sebastien,
I agree with you.
The value 2147483642 is the value purposed by TKG kernel, but as
mentioned in my report, if the value is > 200k well issues in game is
over.
I think, the fedora value is a good approach because we already have
return of their experience, and there is no
** Changed in: ubuntu
Status: Fix Released => Confirmed
** Summary changed:
- Certains jeux crashent liés à un vm_max_map_count trop faible
+ Some Games are crashing linked to a vm_max_map_count too low
--
You received this bug notification because you are a member of Kernel
Packages,
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/2057792
Title:
Some Games are crashing linked to a
So this wasn't related to the linux-firmware package, I'm now running
1.197.2 with working sound.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1934868
Title:
Sound now longer
No, this is the sound from the headphone jack, not the monitor. I agree
it's not immediately apparent how those commits could affect the sound.
When I go into the sound settings it shows my headphones as plugged in.
But even when I try to use the "test left" and "test right" buttons
nothing comes
Public bug reported:
After upgrading to 1.197.2 from 1.197 my sound stopped working. I spent
some time following the "sound troubleshooting procedure" but nothing
worked. Eventually I downgraded the package and now my sound is working
again.
Obviously there isn't much info here, but if it's
Thanks Eric, this also fixed it for me. :)
--
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/1879989
Title:
"Failed to play sound: No such driver" ubuntu 20.04
Status in linux package in
OK, so I booted up with the mouse in USB3 port. All good.
Put mouse in USB2 port. Problem appears (as expected).
output from dmesg attached
** Attachment added: "dm.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+attachment/5281540/+files/dm.log
--
You received this bug
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] RS780 Host
Bridge [1022:9600]
00:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI
bridge (ext gfx port 0) [1022:9603]
00:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI
to PCI
I just tested 5.0.0-23-lowlatency kernel with the mouse plugged into a
USB3 port, and everything seems to be okay. So it does seem to be USB2
specific (I dont have any USB1 ports to test it on, sorry)
--
You received this bug notification because you are a member of Kernel
Packages, which is
yes. Output from lscpu if that helps:
Architecture:x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 48 bits physical, 48 bits virtual
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s):
Okay. Just burned that to USB and booted from USB live image (didn't install).
Issue is still present :-(
--
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/1787857
Title:
USB mouse cursor
@kaihengfeng - How do I find and install that Kernel? Sorry, I'm used to
just using the gui and command line tools to upgrade, not sure how I
find and install that kernel manually. I am used to using apt for
installing general packages, just this scenario is new to me and I can't
find any
Note that this became 100% consistent. As in every time I booted I got the
issue, rather than just most of the time.
Also, that it's now in release 5.0.0.20-lowlatency, 64 bit version.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
*** This bug is a duplicate of bug 1787857 ***
https://bugs.launchpad.net/bugs/1787857
fair enough - but my update is that it became 100% consistent. As in every
time I booted I got the issue.
Also, that it's now in 5.0xxx
On Wed, 24 Jul 2019 at 16:50, Erich Eickmeyer
I have the same issue.
At the login screen, I select my user, enter the password, the mouse works fine
at this point.
Click on login, wait, screen comes up then at random, the mouse either
works fine (about 1 time in 5) or it goes really really slow (4 times out of 5).
Only way I'm working
This was not helpful. When I enter it I'm asked for a password. I don't
have a password and I have no idea what the program is actually asking
for
Sent from my iPhone
> On Jun 5, 2017, at 7:20 AM, Joseph Salisbury
> wrote:
>
> You may need to run the following
Public bug reported:
i have no idea what this is even about. you need to make installation of
upgrades easy and seamless. I am not a computer programmer and have no
desire to become one
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-53-generic (not installed)
+ /dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
+ /dev/snd/controlC0: vince 2727 F pulseaudio
+ /dev/snd/seq:timidity 1561 F timidity
+ DistroRelease: Ubuntu 14.10
+ HibernationDevice: RESUME=UUID=dc29efba-2e6b-4375-b894-d5a0f60cd103
+ InstallationDate: Installed
:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
/dev/snd/controlC0: vince 2727 F pulseaudio
/dev/snd/seq:timidity 1561 F timidity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=dc29efba-2e6b-4375-b894-d5a0f60cd103
:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
/dev/snd/controlC0: vince 2727 F pulseaudio
/dev/snd/seq:timidity 1561 F timidity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=dc29efba-2e6b-4375-b894
:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
/dev/snd/controlC0: vince 2727 F pulseaudio
/dev/snd/seq:timidity 1561 F timidity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=dc29efba-2e6b-4375-b894
PID ACCESS COMMAND
/dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
/dev/snd/controlC0: vince 2727 F pulseaudio
/dev/snd/seq:timidity 1561 F timidity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=dc29efba-2e6b-4375-b894-d5a0f60cd103
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
/dev/snd/controlC0: vince 2727 F pulseaudio
/dev/snd/seq:timidity 1561 F timidity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=dc29efba-2e6b-4375-b894
:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
/dev/snd/controlC0: vince 2727 F pulseaudio
/dev/snd/seq:timidity 1561 F timidity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=dc29efba-2e6b-4375-b894
:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
/dev/snd/controlC0: vince 2727 F pulseaudio
/dev/snd/seq:timidity 1561 F timidity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=dc29efba-2e6b-4375-b894-d5a0f60cd103
PID ACCESS COMMAND
/dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
/dev/snd/controlC0: vince 2727 F pulseaudio
/dev/snd/seq:timidity 1561 F timidity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=dc29efba-2e6b-4375-b894-d5a0f60cd103
PID ACCESS COMMAND
/dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
/dev/snd/controlC0: vince 2727 F pulseaudio
/dev/snd/seq:timidity 1561 F timidity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=dc29efba-2e6b-4375-b894-d5a0f60cd103
PID ACCESS COMMAND
/dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
/dev/snd/controlC0: vince 2727 F pulseaudio
/dev/snd/seq:timidity 1561 F timidity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=dc29efba-2e6b-4375-b894-d5a0f60cd103
PID ACCESS COMMAND
/dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
/dev/snd/controlC0: vince 2727 F pulseaudio
/dev/snd/seq:timidity 1561 F timidity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=dc29efba-2e6b-4375-b894-d5a0f60cd103
: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
/dev/snd/controlC0: vince 2727 F pulseaudio
/dev/snd/seq:timidity 1561 F timidity
DistroRelease: Ubuntu 14.10
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/pcmC0D0p: vince 2727 F...m pulseaudio
- /dev/snd/controlC0: vince 2727 F pulseaudio
- /dev/snd/seq:timidity 1561 F timidity
+ USERPID ACCESS COMMAND
+ /dev/snd/pcmC0D0p: vince
Public bug reported:
After upgrading from 14.04 to 14.10 my screen goes black at random times.
The sound keeps playing so I know it's still running.
The only way I can get the screen back is by pressing the power button, which
will show the shutdown selection window and unblackens the screen.
My
I just tested out a few prior trusty kernels, ended up back at my latest
(3.13.0-36-generic). This time I couldn't reproduce my issue on any of
my installed kernel versions...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Same issue here on System76 Lemu2, 14.04.1 with Kernel
3.13.0-36-generic.
On boot:
[ 12.763185] psmouse serio4: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10
00 64
After reload
[ 469.161313] psmouse serio4: synaptics: Touchpad model: 1, fw: 7.2, id:
0x1c0b1, caps:
Hello there,
Trying to set up my good old Tascam US-122L again on a fresh Ubuntu Studio.
I got it running with older Ubuntus, but it seems that the bug is back again
with Linux 3.x
Actually this is 3.13.0-34-lowlatency, I've apt-installed alsa-firware-
loader, snd-usb-122l is available, but
I see the same firmware loading issue. I assumed the problem was in
tuner_xc2028, as I don't see any related messages in dmesg after the
firmware blob fails to load:
Mar 26 22:03:20 localhost kernel: [ 11.567369] xc2028 0-0061: Loading
firmware for type=BASE F8MHZ (3), id 0
000.
Not seeing the issue on linux-image-generic-lts-raring v3.8.0.37.37 .
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1291459
Title:
ioctl FE_GET_INFO hangs with DViCO
Hi again,
There is finally a working patch for this hardware available at
http://marc.info/?l=linux-inputm=138235576025208w=1
I tested it on my A512 and everything works fine. It looks like the patch was
also tested on other hardware by Fedora testers and works fine (see
: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: vince 2009 F pulseaudio
/dev/snd/pcmC0D0p: vince 2009 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfbd0 irq 48'
Mixer name : 'Intel IbexPeak HDMI'
Components
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: vince 2009 F pulseaudio
/dev/snd/pcmC0D0p: vince 2009 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfbd0 irq 48'
Mixer name : 'Intel IbexPeak HDMI'
Components : 'HDA
Public bug reported:
Related to: Bug - 1224069
Was attempting:
sudo apt-get install -f
this resulted in:
$ sudo apt-get install -f
[sudo] password for vince:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0
Hi Christopher, from my current knowledge the bug still exists in
upstream kernels (this laptop unfortunately has a Dolphin v2
touchpad)... You added a cherry-pick tag, do you have a patch ready
that I could test ?
--
You received this bug notification because you are a member of Kernel
43 matches
Mail list logo