This just in, given that I currently use Linux 4.10.17-041017-generic
(x86_64), here is my situation as of now:
1. I was in Twitter.
2. I was trying to type my tweet
3. The up button temporarily does not work but other buttons do work
4. And when I press other keys and mouse, **the up button works
Yes, tests are ok for me.
Thanks.
--
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/1779830
Title:
vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
Status in linux package i
Well, I just applied a firmware upgrade from A08 (very first firmware
revision of the Dell Latitude E6420) to A25 (released just this year, 27
March 2018).
SOURCE:
https://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverId=JP0YK
I am yet to see the results of the firmware upgrade.
Sorry if I missed the point all this whole time.
But, this is just in. I saw a warning in the BIOS settings when
switching between AHCI and RAID. There was a warning that actually
threatens the installation that says:
"SATA Operation is being changed!
Attention! Changing this setting may preven
Despite my efforts, I still do (as of this writing, I experienced two of
these sudden keyboard shut offs). And it is kind of unpredictable.
--
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/17
I have the same problem as Steve Dodd and MV, it worked fine until
4.15.0-24-generic #26-Ubuntu, now my network will not resume after
suspend.
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 11)
modprobe -r r8169
modprobe -i r816
So is there any progress so far? Or is this more likely a hardware issue
rather than a driver issue?
--
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/1775016
Title:
[Dell Latitude E6420] U
To be clear, I wish to send this video. It happens unpredictably. Even
after a reformat it still happens like this.
So, is it possible this is a bug or this is more likely a hardware issue
rather than a bug or is it possibly both?
(Because of necessity, I had to change the laptop keyboard for the
Checked.
Linux loki 4.4.0-132-generic #158-Ubuntu SMP Thu Aug 2 09:08:04 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux
Thanks.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which
** 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/1755384
Title:
hot-add memory can't be recognized for ubuntu-16
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: kernel-package (Ubuntu)
--
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/1755393
Title:
h
Public bug reported:
Request to pull this patch from upstream into the next 4.15 kernel
update:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b2adf22fdfba85a6701c481faccdbbb3a418ccfc
This fixes a regression in SMB 2/3 reconnect detection. The fix has been
backported
I can reproduce the issue with ethernet failing on the r8169 on resume
from suspend with the current kernel. This is a regression since a
previous kernel on 18.04 since the symptoms occur after installing
updates.
I can also confirm that Kai's kernel seems to fix ethernet after suspend
on at leas
I have confirmation from a user who has done verification for this
kernel. Changing to verification-done-bionic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Hi Joe,
Can we put some debug in sata_down_spd_limit() and see some of the values
for spdlimit, sstatus, spd, mask, right before the change to not force the mask.
Also, can we track the exact path of calling sata_down_spd_limit().
The the intent of the patch was not to force the speed down before
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1813141
Title:
Webcam Syntek doesn't work with Cheese or Camorama
Sta
Public bug reported:
Computer : ASUS Z53JM
Webcam : Syntek 1125 ID 05e1:0501
When I start Cheese or Camorama, the webcam light switch on and then switch off
immediately. No image on Cheese (black image) and static colored lines on
Camorama.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package:
dmesg output when launching Cheese
** Attachment added: "Capture d’écran de 2019-01-24 09-57-37.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813141/+attachment/5232077/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202019-01-24%2009-57-37.png
--
You received this bug notification b
apport-collect 1813141 : error : connecting to Launchpad failed...
--
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/1813141
Title:
Webcam Syntek doesn't work with Cheese or Camorama
Statu
Public bug reported:
There was a previous request in bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
the IO scheduler to NOOP in linux-azure. The other schedulers were
turned off and NOOP was made the default.
However with new upstream releases, new schedulers where adde
I also experience this bug on Dell Inspiron 7370
--
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/1784152
Title:
i2c_hid_get_input floods system logs
Status in linux package in Ubuntu:
This bug might be related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813543
--
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/1813831
Title:
Oops: NULL pointer dereference intel
Public bug reported:
I am running Ubuntu 18.04 LTS on a HP EliteBook 840 G5 with docking station and
two screens attached via DisplayPort.
Reproducibly, when I close the lid of my notebook, the kernel
4.15.0-44.47-generic crashes with a Oops in i915 / intel_ddi_post_disable.
The previous kernel
*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663
This bug is also related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813745
This kernel works fine for me too:
> Please test this k
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1811394/+attachment/5234638/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1811394/+attachment/5234632/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Tags added: apport-collected
** Description changed:
When running the following script:
https://github.com/DevelopersPL/pkgbuild/blob/master/ipset-nuclear/ipset-nuclear
on the 4.15.0-43-generic kernel it leads to a kernel panic.
Tested the same with 17.10 (4.13 kernel
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1811394/+attachment/5234635/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1811394/+attachment/5234630/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1811394/+attachment/5234637/+files/UdevDb.txt
--
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/1811394
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1811394/+attachment/5234633/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1811394/+attachment/5234634/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1811394/+attachment/5234636/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1811394/+attachment/5234631/+files/Lspci.txt
--
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/1811394
@overlord: AFAIK, there is no simple reproducer test case for this
issue. The ideal testing scenario for a bug and fix like this one would
be for each user who reported this issue to use a test kernel with the
fix in their environment and report back if the issue still manifests or
not after some t
Hi overlord. An easy way to check the updates included in released
kernels is to look at the "-changes" mailing list for your Ubuntu
release.
In this situation it would be https://lists.ubuntu.com/archives/xenial-
changes/
And you can find that new kernel here:
https://lists.ubuntu.com/archives/
You can clone the ubuntu-xenial kernel:
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git
And then grep for the commit you're looking for. There's a few different
ways to do it, I do:
git log --oneline | grep "Expose SMT control init function"
--
You received this bug notification bec
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1811394
Title:
ipset kernel error: 4.15.0-43-generic
Status in linux
[VERIFICATION BIONIC]
I can modprobe the mq-deadline, kyber and bfq schedulers but it looks
like doing a modprobe of the cfq and deadline schedulers doesn't list
them as choices in the available schedulers:
# uname -r
4.18.0-1009-azure
# modprobe bfq
# modprobe cfq-iosched
# modprobe mq-deadline
@lazamarius1: Just to clarify, the fix is scheduled to go in the 4.15
kernel in Bionic which is the same kernel as the Xenial HWE kernel. So
there's no need to add anything to the Affects section. You will see a
new linux-hwe 4.15 kernel in xenial-proposed once this is ready to test.
Thanks!
--
Y
Public bug reported:
Host changes have altered how the PCI GUID is presented to the guest and
the patches for PCI IDs in 4.15.0-1037 do not properly handle the new
condition.
Impact:
Instances with multiple GPUs are only seeing one.
Workaround:
4.15.0-1036 does not have this behavior.
Additiona
I will try to do that. I've narrowed down the versions for now (using
mainline kernel). The bug appeared sometime between 4.13.16 and 4.14.0
and was fixed between 4.15.18 and 4.16.0.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
@Guillaume: I am Eric's colleague from comment #21. I was able to
reproduce the issue in Azure with your reproducer in comment #5. I'll
show Eric how I reproduced the issue and he'll be able to follow up with
you. Thanks!
--
You received this bug notification because you are a member of Kernel
Pa
Ubuntu is customizable from the moment you install it. The latest
version uses the GNOME desktop environment which allows you to
personalize virtually every single element of your UI/UX, from your
notification sounds, popup style, fonts, system animations, and
workspaces. https://www.asussupportnum
Also on ThinkPad X1 Carbon 5th
Linux x1-cosmic 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Synaptics touchpad
xinput
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4
They both sound awfully "generic" (pun intended), but I can't really
come up with an example for a bad match, so lets just try it I guess.
That said, isn't the "deeper" problem that these metapackages can be
removed easily even through they are important to keep the kernel up-to-
date (and hence s
Hi Guillaume, would it be possible to provide step-by-step instructions
to reproduce this issue?
--
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/1796376
Title:
Bug #1739107 fix causes lin
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1793430
Title:
Page leaking in cachefiles_read_backing_
I can reproduce the issue in Azure with Ubuntu 18.04 and the kernel
linux-azure-edge 4.18.0.1004.5 from bionic-proposed.
I use an instance of type "Standard F4s_v2 (4 vcpus, 8 GB memory)"
I launch the instance and get the 4.15.0-1030-azure kernel:
$ lsb_release -a
No LSB modules are available.
D
Hi Chris. I spoke to Joseph and I think we have everything we need to
start the bisect. We'll get started and keep you posted.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477
Hi Joseph,
Is there a special way I should install these? I tried:
sudo dpkg -i *
But I get:
Selecting previously unselected package linux-azure-cloud-tools-4.17.0-1001.
(Reading database ... 56547 files and directories currently installed.)
Preparing to unpack
linux-azure-cloud-tools-4.17.0-1
These are the packages I see installed out of the box in the instance:
ubuntu@lp1794477:~/41701001$ dpkg -l | grep 4.15.0-1030.31 | sort
ii linux-azure-cloud-tools-4.15.0-1030 4.15.0-1030.31
amd64Linux kernel version specific cloud tools for version
4.15.0-
I can see the Mellanox devices with that 4.17.0-1001-azure kernel.
I installed the new kernel:
sudo dpkg -i linux-
modules-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb linux-
modules-extra-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb linux-
image-unsigned-4.17.0-1001-azure_4.17.0-10
4.18.0-1002:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1002-azure #3~lp1794477 SMP Wed Nov 21 16:41:12 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.723350] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.751281] mlx4_ib_add: mlx4_ib:
4.18.0-1001:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1001-azure #2~lp1794477 SMP Wed Nov 21 16:06:45 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.701988] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.730013] mlx4_ib_add: mlx4_ib:
4.18.0-1003:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1003-azure #4~lp1794477 SMP Wed Nov 21 18:32:18 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.701478] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.732267] mlx4_ib_add: mlx4_ib:
4.18.0-1004:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1004-azure #5~lp1794477 SMP Wed Nov 21 19:19:16 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[6.009608] mlx4_core: Mellanox ConnectX core driver v4.0-0
[6.045063] mlx4_ib_add: mlx4_ib:
bionic-tree/4.18.0-1004:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1004-azure #4~18.04.1 SMP Wed Nov 21 20:07:48 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[6.337786] mlx4_core: Mellanox ConnectX core driver v4.0-0
[6.374260] mlx4_ib_add
bionic-tree/4.18.0-1004 with all the packages:
$ sudo dpkg -i
linux-modules-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb \
linux-modules-extra-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb
\
linux-image-unsigned-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64
Hi Marcelo,
Maybe I'm doing something wrong but I still don't see the Mellanox
devices with this 4.18.0-1005 kernel from the CKT PPA:
ubuntu@lp1794477:~$ sudo add-apt-repository ppa:canonical-kernel-team/ppa
ubuntu@lp1794477:~$ sudo apt install linux-azure-edge
ubuntu@lp1794477:~$ sudo update-gru
I encountered this iwlwifi failure while testing the Intel 9260 with the
AMD Ryzen 7 2700x (8 core, 16 thread). By bisecting the kernel, I was
able to narrow it down to the same commit. I can also verify that
setting maxcpus=15, fixes wifi (at the cost of performance).
This is a really important
I experienced the problem 100% of the time on 4.4.0-139. However, unlike
Jan, I just tried 4.4.0-140 and the problem is gone. I will continue
monitoring my system to see if it reappears.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
Public bug reported:
Steps to reproduce:
On a Thinkpad X1 Carbon running 18.04 bionic
Attempt to suspend (using the the 'manual suspend' option from Gnome settings,
hold down 'power' until changes to 'pause' symbol')
Expected behaviour:
machine goes into suspend state, display off, fans off, po
OK, false alarm -- 4.4.0-140 is now crashing for me as well. As far as I
know nothing has changed between now and yesterday. Same computer, same
drives, everything. Back to 4.4.0-138 for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
There isn't yet a new kernel in *bionic* -proposed to solve this issue,
so I can't test it.
I have verified that building the 4.15.0-42.45 kernel with the patch
(https://patchwork.kernel.org/patch/10382693/) applied fixes wifi for
16+ threaded systems on bionic.
--
You received this bug notifica
Kai-Heng Feng: I did the bisection and the culprit is
[9021f2295af1af93416aea20c7b72390919f122d] xhci: Fix use-after-free in
xhci_free_virt_device
This commit exists upstream, and the problem has already been fixed upstream:
https://www.spinics.net/lists/linux-usb/msg168861.html
--
You received
I built 4.4.0-141.167 with the one-line patch from
https://www.spinics.net/lists/linux-usb/msg168861.html and it does
indeed fix this problem.
--
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
Public bug reported:
In Linux Mint MATE 19 with kernel 4.15.0-39, Asus F5N webcam works with
Camorama but not with Cheese.
USB webcam : 174f:6a31, sensor MT9M112, module gspca_stk1135
Module is in linux-modules-extra
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
*
** Attachment added: "lsmod, lsusb, cheese"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807538/+attachment/5220440/+files/Capture%20du%202018-12-08%2023-30-44.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
Public bug reported:
I have this bug with a couple of different kernels including a locally
built version dmesg output follows
[ 15.126210] BUG: unable to handle kernel paging request at 2d18
[ 15.126213] PGD 0 P4D 0
[ 15.126216] Oops: [#1] PREEMPT SMP PTI
[ 15.126219]
10-0ubuntu13
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: david 1847 F pulseaudio
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2018-12-07 (2 days ago)
+ InstallationMedia: Ubuntu-Studio 18.10 "
buntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18.10 "C
buntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18.10 "C
ion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18
buntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18.10 "C
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedi
ion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18
ion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubunt
ion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18
ion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18
ion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18
ion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18
buntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18.10 "C
ion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubunt
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedi
buntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18.10 "C
buntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18.10 "C
buntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18.10 "C
buntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18.10 "C
ion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubunt
buntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18.10 "C
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubunt
st Controller
(rev 04)
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationD
ion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18
ion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18
buntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18.10 "C
ion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1847 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18
apport information
** Tags added: apport-collected tara
** Description changed:
In Linux Mint MATE 19 with kernel 4.15.0-39, Asus F5N webcam works with
Camorama but not with Cheese.
USB webcam : 174f:6a31, sensor MT9M112, module gspca_stk1135
Module is in linux-modules-extra
+ ---
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1807538/+attachment/5220570/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
501 - 600 of 2593 matches
Mail list logo
