ACCESS COMMAND
/dev/snd/controlC0: g 2519 F pulseaudio
Date: Tue Mar 10 08:08:02 2015
ErrorMessage: subprocess installed post-installation script returned error exit
status 2
HibernationDevice: RESUME=UUID=7361fc96-f667-45d4-8256-405a40271332
InstallationDate: Installed on 2013-12-25
ACCESS COMMAND
/dev/snd/controlC0: g 2519 F pulseaudio
Date: Tue Mar 10 08:08:02 2015
ErrorMessage: subprocess installed post-installation script returned error exit
status 2
HibernationDevice: RESUME=UUID=7361fc96-f667-45d4-8256-405a40271332
InstallationDate: Installed on 2013-12-25
Would like to refer to a similar but that I've reported:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904265
--
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/1904069
Title:
Thanks for pointing to the possible duplicate. These two bugs might be
related, still I think there are different. The one I've reported here
appears always after restarting the system or restarting the bluetooth
controller. However, the other requires a suspend/resume to get the
bluetooth
apport information
** Tags added: apport-collected focal
** Description changed:
Hello everyone,
a few months ago I upgraded from 18.04 to 20.04 and since then, I'm into
some bluetooth connection issues. I'm a KDE user currently using Ubuntu
5.4.0-53.59-generic 5.4.65, still the
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434305/+files/CRDA.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/1904265
Public bug reported:
Hello everyone,
a few months ago I upgraded from 18.04 to 20.04 and since then, I'm into
some bluetooth connection issues. I'm a KDE user currently using Ubuntu
5.4.0-53.59-generic 5.4.65, still the reported issue also appears with
plain ubuntu 20.04, even a clean live USB
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434312/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434314/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434315/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434307/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434309/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434308/+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/1904265
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434316/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434313/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434306/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434310/+files/Lsusb.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/1904265
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434311/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434317/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434319/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434318/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1904265/+attachment/5434320/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
For the avoidance of doubt I've just booted up `5.11.0-35-generic` from
-proposed (after previously running Hui's build) and audio is working
fine on my 9710.
** Tags removed: hirsute verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification
It's not in the commit log for -34: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/hirsute/log/?h=Ubuntu-5.11.0-34.36
It's in the log for the next kernel cycle -35:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/hirsute/log/?h=Ubuntu-5.11.0-35.37
--
You
Even though I reported this issue already a few years ago, unluckily it
is still present. I ignored it in the meanwhile, however I started to
locate the problem's cause again. My mouse is a multi-device, so I
paired it again using a live Linux (to avoid any inference with the
existing paring) but
It seems as I found a permanent fix. In case anyone having the same
issue, this approach fixed it for me:
1. Unpair the mouse in Windows, i.e. delete it inside the Bluetooth settings.
This will delete the respective keys in the Windows registry, too.
2. Unpair the mouse in Ubuntu, i.e. revoke
I can't really tell because my laptop was stolen a couple of months ago.
But as far as I remember, it wasn't an issue anymore, so you can close
it.. Not sure to what I should change the bug now.. Invalid?
--
You received this bug notification because you are a member of Kernel
Packages, which is
I have finally forced myself to go back to this bug. Tested with Linux
3.12 rc3 from mainline ppa. AMD C1E set to auto - can't boot. AMD C1E
set to disabled - boots normally.
I probably should send a mail to the maintainers, but last time I did
it, I got no response from them. Maybe I've screwed
Here is the link: http://marc.info/?l=linux-acpim=136069746628268w=2
--
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/1007508
Title:
[Gigabyte GA-870A-USB3] Unable to boot without
Post to the mailing list is from more than half of year ago. Should we
wait or repost?
--
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/1007508
Title:
[Gigabyte GA-870A-USB3] Unable to
I have changed to new hardware meanwhile. Since I don't see any
WONTFIX status, I'm changing the bug status to Invalid.
@ schwarzer adler: I hope this is okay for you. Otherwise, please just
change the status back.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
You
I checked on the Linux Bug Tracker (or something related) and it says a
patch is out.
Run sudo apt-get update sudo apt-get upgrade and if that doesn't
work,
install indicator-cpufreq: sudo apt-get install indicator-cpufreq, log
out, and login.
Look at your menu bar. A pic of a CPU will be
** Changed in: linux (Ubuntu)
Status: Triaged = 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/1290110
Title:
Fan stops after resume from suspend leading to
The problem is becaue its the daily build. Try a reinstall with stable.
--
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/1290110
Title:
Fan stops after resume from suspend leading to
For me, I have it working on every kernel.
--
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/1290110
Title:
Fan stops after resume from suspend leading to overheating; requires
reboot to
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Dhinak G (dhinak2004)
** Also affects: linux (Debian)
Importance: Undecided
Status: New
** No longer affects: linux (Debian)
--
You received this bug notification because you are a member of Kernel
Packages, which
@MicWit: I had problems even with 11.10, as you can see in the
automatically generated part of the description. Perhaps I should test
the newer kernels, but I totally got bored with it and I just use
workaround 2: disable AMD C1E. Maybe you should open a separate bug
report?
--
You received this
Public bug reported:
I recently installed 13.10 and immediately updated to the latest updates
via my ethernet work connection.
Got home and noted that linux-image-3.11.0-15-generic was only able to
transfer to my local media box via wifi at ~350kB/s (ie. Taking 10+
minutes for a 300Mb file)
The package doesn't seem to have pushed out yet - direct download link?
--
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/1270208
Title:
linux-image-3.11.0-15-generic appears to regress
The kernel still isn't public, but part of the issue appears to be my
router - Once a couple of failures have happened, i'm then unable to get
known 'good' configurations working.
Good:
3.11.0-12-generic using firmware:
[ 4679.763448] iwlwifi :03:00.0: loaded firmware version 9.221.4.1 build
Hi penalvch, I'm still awaiting on 3.11.0-17 to appear in the proposed
repository. I've enabled the proposed repo for Saucy.
https://www.google.com.au/search?q=site:http:%2F%2Farchive.ubuntu.com
+linux-image-3.11.0-17-generic isn't showing any results either.
--
You received this bug
I was following jsalisbury's instructions.
penalvch - I dont have a burner handy so testing using a bootable cd/dvd
is out. I'm happy to install and uninstall a kernel deb to test the
Trusty kernel if you can point me at the packages directly.
--
You received this bug notification because you
Ok, installed http://cdimage.ubuntu.com/daily-live/current/trusty-
desktop-amd64.iso onto a USB drive, booted and was able to get up to
3MB/s performing the same smb transfer to my media box as the original
post.
Impirically slower than 3.11.0-12, but seemed stable enough.
--
You received this
I'm not sure I understand the question.
The current Saucy kernel 3.11.0-15 is unusable for me, and i'm forced to
boot into 3.11.0-12.
That is clearly a regression and not Invalid surely?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
(In reply to comment #122)
I also get a mirrored output on VGA, however I could not extend to that
adapter. (it seems to be a hardware mirror, I only see one external display,
DP2, in XrandR...)
Same here. Switching to one external DP display now works like a charm.
Gets identified as DP2 in
(In reply to comment #125)
(In reply to comment #115)
I tried applying the two patches which you posted on intel-gfx[1], ported to
3.13.
[1] http://article.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/33737
Using a T540p and an Ultradock, connected to a Dell U2410 via a
(In reply to comment #128)
(In reply to comment #124)
There seems to be still a problem enumerating the devices connected to the
DP hub
We currently do not support MST (multistream) DP branch devices. If it works
for multiple monitors, great, but it's more or less by accident.
Thank you
(In reply to comment #131)
(In reply to comment #129)
It seems the hang is resolved with the dock firmware update (2.17) provided
by Lenovo. As far as I am concerned I think this bug can be closed.
From the kernel perspective it's fixed when we don't freeze the machine even
when a dock
(In reply to comment #118)
Just installed the firmware update. Now dock shows firmware version 2.17.
Firmware update utility required Intel display-driver installed on my
Windows 8.1 installation, otherwise it was unable to update to detect the
DP-hub.
It also required a least one display
(In reply to comment #117)
That is beta firmware.
The Lenovo guy in there said final firmware would likely be released next
week.
And I asked for a bootable CD update, and other people did so as well.
The Lenovo guy in there said he'd pass on the request for a bootable CD
update.
Just
*** This bug is a duplicate of bug 1332210 ***
https://bugs.launchpad.net/bugs/1332210
** This bug has been marked a duplicate of bug 1332210
Apple Magic Mouse battery life read as 0%
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
On my HP EliteBook 6930p, there are some soft buttons, the most
important being Mute, Volume Up, Volume Down.
Sometimes, these soft buttons don't work. Interesting: in those cases,
normal keyboard shortcuts (for example: Ctrl + Alt + T for opening a
terminal) also don't
Curiously, bug probably affects only car bluetooth devices.
My HarmanKardon BT Headset (with telephony) and my Garmin CAR GPS (with
telephony via BT) pairing fine with Aquaris 4.5...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
Hi Christopher, thank you for looking into this. I'm running Ubuntu MATE
15.04 at the moment, and the problem doesn't happen in that distro.
Maybe somebody else will be able to pick up this bug from where I left
off?
--
You received this bug notification because you are a member of Kernel
I also found it first in PySerial, but it affects everything down to the
underlying poll() implementation. Demo C code is attached (compile with
-Wall -std=gnu99). Under -63 the poll() call blocks for the 1 second
it's supposed to, a ping is sent once a second, and if you short pins
2-3 of the
Also affects me with a Lenovo Thinkpad E550 running KXstudio 14.04
Current workaround is an old Logitech UVC desktop webcam perched on top
of my laptop.
NOT Pretty! :P
Gary
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
While it's wonderful that a patch has been created, could someone out
there PLEASE wrap it up in a nice and simple .DEB package so the rest of
us idiots can install it without having to manually recompile the
kernel?
After all, most of us *buntu users are simpletons who can't work a BASH
shell if
I used version Core18 of the iwlwifi backports repository:
https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/backport-iwlwifi.git/log/?h=release/LinuxCore18
and the current ubuntu 4.4 kernel with the following dkms.conf:
MAKE="'make' -j 12 KERNELDIR=/lib/modules/${kernelver}/build"
I'm not sure I would say it worked well, but it did fix one of two
problems. The second was only fixed after both driver and firmware
upgrades. I'm no longer running the 19.ucode version. Would apport
data for the 21 version with the updated driver be useful?
--
You received this bug
It did indeed fix the problem I was seeing in this bug report. However,
I started having another less frequent issue shortly after (also
disconnects, but completely different errors). I was only able to solve
that one by getting the newest firmware (-21.ucode) AND rebuilding the
iwlwifi modules
Public bug reported:
This issue has been resolved upstream and is described in
https://bugzilla.kernel.org/show_bug.cgi?id=117391
The current Ubuntu Xenial Xerus kernel (4.4.0-21.37) is built with a
version of the iwlwifi driver which supports firmware version up to
iwlwifi-8000C-19.ucode.
Please see the upstream bug report for all of the necessary debugging
logs. However, the bug has already been identified and the issue here
is really just deciding how to package the fix.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
** Summary changed:
- Bluetooth will be disable after reusme from suspend on Xenial
+ Bluetooth will be disable after resume from suspend on Xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@tjaalton: Could you please elaborate what that means? Does that mean
that a fix will be available via the ubuntu updater soon? Or do we have
to wait till 16.10? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
The following changes was pulled into atleast the Ubuntu Xenail Kernel release.
http://kernel.ubuntu.com/git/kernel-ppa/mirror/ubuntu-xenial.git/commit/mm?id=b56d2a75e1daae6ff6eedfb732eadf3c13df6090
>From b56d2a75e1daae6ff6eedfb732eadf3c13df6090 Mon Sep 17 00:00:00 2001
** 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/1629260
Title:
drdb kernal 4 crash
Status in linux package in Ubuntu:
Incomplete
Bug
We had installed the mainline kernel on two machines and tested it again.
The issue still remains. One of the two machines get slow, lost the drdb
connection en begin to hang.
The other machine works fine (just like before).
** Attachment added: "drdb status.png"
** 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/1629260
Title:
drdb kernal 4 crash
Status in linux package in
We got two servers with deferent RAID cards.
Server 1 got this DRBD issue (3ware Inc 7xxx/8xxx-series PATA/SATA-RAID)
Server 2 dos not has this problem (Areca Technology Corp. ARC-1200 2-Port
PCI-Express to SATA II RAID Controller)
--
You received this bug notification because you are a member
I haven't had any problems since upgrading to yakkety:
4.8.0-30-generic #32-Ubuntu
driver: iwlwifi
version: 4.8.0-30-generic
firmware-version: 22.361476.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
apt wants to remove lubuntu-desktop if I try to install the linux-image-
generic. Is there any way to avoid that?
$ sudo apt-get install linux-image-generic/yakkety-proposed
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen
Confirm, broken again with 4.8.0-44. So as I assume 4.4.0-70 was also
fetched from xenial-proposed I set the tags back to verification-needed-
yakkety.
Summary:
4.4.0-69 worked (verified)
4.4.0-70 broken
4.8.0-43 worked (verified)
4.8.0-44 broken
** Tags removed:
Confirm fix works for yakkety. At least kernel does not panic anymore.
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I can confirm that the test kernel posted in comment #7 solved the issue for me.
See comment 5 of bug #1669815 (duplicate of this one).
Any information when the bugfix will be part of the 4.8.0 kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Yakkety 4.8.0-46 is broken.
@Muelli: 4.4.0-69 from the xenial proposed and 4.8.0-43 from the yakkety
proposed repository contained a patch that fixed the issue. For unknown
reasons this patch was reverted in 4.4.0-70 and 4.8.0-44. Several non
proposed kernel updates have been released since then,
For these kernel version you need to enable the proposed repository.
See here: https://wiki.ubuntu.com/Testing/EnableProposed how it's done.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I installed the kernel 4.4.0 provided by jsalisbury. This works for me:
$ uname -a
Linux media-desktop 4.4.0-64-generic #85~lp1666421 SMP Wed Feb 22 21:37:35 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
$ lsusb | grep "Edimax"
Bus 001 Device 002: ID 7392:7822 Edimax Technology Co., Ltd
$ ifconfig
** Summary changed:
- Kernel panic when plugging in USB Wifi USB Adapter
+ Kernel panic when plugging in USB Wifi USB adapter
** 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.
** Attachment added: "IMG_20170222_230239.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669815/+attachment/4830787/+files/IMG_20170222_230239.jpg
** Description changed:
Since updating my Lubuntu 16.10 system (linux-image-4.8.0-37-generic to
linux-image-4.8.0-38-generic) the
I can confirm that 4.8.0-47.50 from proposed does not freeze in Yakkety.
Should we set the tags to verification-done-* again? Or should we wait
for the next proposed version to see, if the patch remains there this
time...
--
You received this bug notification because you are a member of Kernel
I am also getting the same issue with ga kernel
Where we hav to set the hwe kernel?
We have to change the hwe kernel to maas node or to the deploying nodes?
And apparmor and hwe kernel is mandatory to set to deployment work?
--
You received this bug notification because you are a member of
Just updated to 4.8.0-49.61 from yakkety-updates. The issue is solved, there.
Thank you all!
--
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/1666421
Title:
kernel 4.4.0-63 with USB WLAN
This is after update to Linux 4.13.0.17
Computer will still not boot normally - the image attached shows part of
the screen that displays/flashes continuously.
Grub boot still ok.
** Attachment added: "Image showing error message"
Great thanks, it is working on my C1X5!
For those wondering what "remove i2c_801 from modules blacklist" means:
You should modify /etc/modprobe.d/blacklist.conf and comment the line with
"blacklist i2c_i801" (i.e. add a # at the beginning of the line).
--
You received this bug notification
This is an image of the line that is visible in the sequence between the Grub
menu and the Recovery Menu.
Hope that helps.
** Attachment added: "Image of line with ERROR in it"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+attachment/5011745/+files/20171120_152818.jpg
--
I'm affected by this too - using Proxmox 5.1 which uses Ubuntu's kernel.
If could get / compile the ZFS modules for 4.14, I could test kernels.
Let me see if I can track those down, or build them myself.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hi
Thank you for taking an interest in this. I am sorry, but the testing
you suggest seems to be too complicated for me.
However, I have watched the Grub boot up carefully - it scrolls past
quickly - but I have spotted, before the Recovery Menu, a line that I
think reads, in part,...
I tried - Temporary: Press 'Escape' key at the 3 second pause by Grub
bootloader - without sucess.
The motherboard is a Gigabyte MA74GMT-S2 with an AMD64 cpu, and onboard
graphics from an AMD740G.
During an attempt at a normal bootup, the system reaches the Ubuntu
screen with the five dots. The
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1730480/+attachment/5005476/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1730480/+attachment/5005467/+files/CRDA.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/1730480
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1730480/+attachment/5005473/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1730480/+attachment/5005468/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1730480/+attachment/5005475/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1730480/+attachment/5005469/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1730480/+attachment/5005470/+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/1730480
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1730480/+attachment/5005477/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1730480/+attachment/5005472/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1730480/+attachment/5005471/+files/Lsusb.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/1730480
apport information
** Tags added: apport-collected artful
** Description changed:
Problem after 17.04 to 17.10 upgrade - seven days ago.
I have to boot using Grub, in recovery mode. System works ok. During power
down, I get -
A Stop Job is Running for Session C3 of User GDM - which waits
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1730480/+attachment/5005474/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 1056 matches
Mail list logo
