AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: jarl 5102 F wireplumber
- /dev/snd/controlC1: jarl 5102 F wireplumber
- /dev/snd/seq:jarl 5099 F pipewire
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: jarl 5102 F
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 5102 F wireplumber
/dev/snd
-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 7560 F wireplumber
/dev/snd/controlC1: jarl 7560 F
** Summary changed:
- Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission
denied (13)
+ FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I get "permission denied" on the chrome bug link
https://bugs.chromium.org/p/chromium/issues/detail?id=1459821. Is there
a public link for that bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu.
Public bug reported:
With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience
that google-chrome crashes.
It shows
```shell
[11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . :
Permission denied (13)
Trace/breakpoint trap (core dumped)".
```
To be
sion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jarl 2901 F pulseaudio
/dev/snd/controlC0: jarl 2901 F pulseaudio
CurrentDesktop: KDE
Date: Mon Jun 26 19:39:37 2017
HibernationDevice: RESUME=UUID=
A consequence of the design decision to prevent read-access for users is
that a bug has emerged in libguestfs:
https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1813662
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I change status to fixed released as per comment#11
** Changed in: grub2 (Ubuntu)
Status: Expired => Fix Released
** Changed in: linux (Ubuntu)
Status: Expired => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
After upgrading ubuntu to 18.04 I can no longer reproduce this problem
using unmodified package-installed grub files.
So if nobody else can reproduce this problem I suggest it is closed as
fixed in 18.04.
--
You received this bug notification because you are a member of Kernel
Packages, which
It works with VMware 14.
--
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/1715552
Title:
VMWare does not start
Status in linux package in Ubuntu:
Confirmed
Bug description:
Under
ionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1
1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jarl 2901 F pulseaudio
/dev/snd/controlC0: jarl 2901 F pulseaudio
CurrentDesktop: KDE
Date: Mon Jun 26 19:39:37 2017
HibernationDevice: RESUME=UUID=62c8a911-b76d
20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jarl 2901 F pulseaudio
/dev/snd/controlC0: jarl 2901 F pulseaudio
CurrentDesktop: KDE
Date: Mon Jun 26 19:39:37 2017
HibernationDevice: RESUME=UUID=62c8a9
.0-24-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jarl 2901 F pulseaudio
/dev/snd/controlC0: jarl 2901 F pulseaudio
CurrentDe
I have now tried with the latest rc5 kernel
`Linux hermes 4.4.0-040400rc5-generic #201512140221 SMP Mon Dec 14 02:23:36 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux`
The problem/symptoms are still the same.
Jarl
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You recei
x 3.16.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 4339 F pulseaudio
CurrentDesktop: KDE
Date: Sat Feb 21 21:27:53 2015
Ecryptf
d64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 4339 F pulseaudio
CurrentDesktop: KDE
Date: Sat Feb 21 21:27:53 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2
InstallationDate: Installed on 2013-11-27 (
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 4339 F pulseaudio
CurrentDesktop: KDE
Date: Sat Feb 21 21:27:53 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2
InstallationDate: Installed
:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 4339 F pulseaudio
CurrentDesktop: KDE
Date: Sat Feb 21 21:27:53 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2
InstallationDate: Installed on 2013-11-27 (450 days ago
:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 4339 F pulseaudio
CurrentDesktop: KDE
Date: Sat Feb 21 21:27:53 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2
InstallationDate: Installed on 2013-11-27 (450 days ago
3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 4339 F pulseaudio
CurrentDesktop: KDE
Date: Sat Feb 21 21:27:53 2015
EcryptfsInUse
and
connected without any problems to the access point. I wonder if the
installation process was using another kernel.
Jarl
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-24-generic 3.13.0-24.47
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
to the access point. I wonder if the
installation process was using another kernel.
Jarl
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-24-generic 3.13.0-24.47
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion
installation, the wifi was detected and
connected without any problems to the access point. I wonder if the
installation process was using another kernel.
Jarl
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-24-generic 3.13.0-24.47
ProcVersionSignature: Ubuntu
x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jarl 1860 F pulseaudio
/dev/snd/controlC0: jarl 1860 F pulseaudio
Date: Tue Dec 31 09:11:38 2013
I updated the BIOS, it doesn't help...
After BIOS update:
$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
68CPE Ver. F.24
10/18/2013
The problem seems to be introduced in kernel 3.11 and solved in 3.12.
Are there any plans on updating ubuntu official kernel to 3.12?
Jarl
: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jarl 1860 F pulseaudio
/dev/snd/controlC0: jarl 1860 F pulseaudio
Date: Tue Dec 31 09:11:38 2013
HibernationDevice: RESUME=UUID=92f3c741-1bd3-4762-a2c1-59d27eef756c
InstallationDate
from scratch the daily CD image to see
if that solves the problem.
It has been confirmed now by three sources that kernel 3.12 solves the
problem, isn't that sufficient information? I trust that if daily CD has
kernel 3.11 the problem is there, if it has kernel 3.12 the problem is
not there.
Jarl
-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jarl 1860 F pulseaudio
/dev/snd/controlC0: jarl 1860 F pulseaudio
Date: Tue Dec 31 09:11:38
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jarl 1860 F pulseaudio
/dev/snd/controlC0: jarl 1860 F pulseaudio
Date: Tue Dec 31 09:11:38 2013
HibernationDevice: RESUME=UUID
x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jarl 1860 F pulseaudio
/dev/snd/controlC0: jarl 1860 F pulseaudio
Date: Tue Dec 31 09:11:38 2013
Since this bug is about support for RT3290 and I have seen RT3290 to be
working fine in 13.04 I consider the support for RT3290 to be in place.
However In Ubuntu 13.10 there seems to be a bug introduced with kernel 3.11, so
I have created a separate bug for that at
33 matches
Mail list logo
