Here is an ACPI dump on a Dell Latitude 5590 with kernel 5.5.3.
** Attachment added: "ACPI dump"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806437/+attachment/5327674/+files/acpi-dump.bin
--
You received this bug notification because you are a member of Kernel
Packages, which is
The problem is still there in Ubuntu 20.04/focal:
$ grep CONFIG_IO_STRICT_DEVMEM /boot/config-5.*
/boot/config-5.4.0-21-generic:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-5.4.0-21-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-5.6.3-050603-generic:# CONFIG_IO_STRICT_DEVMEM is
** Bug watch added: Linux Kernel Bug Tracker #205121
https://bugzilla.kernel.org/show_bug.cgi?id=205121
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=205121
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
A similar bug still exists in the mainline 5.5.7 kernel:
[106491.771242] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio.
[106491.771247] iwlwifi :02:00.0: reporting RF_KILL (radio disabled)
[106491.771342] wlan0: deauthenticating from e4:aa:5d:e0:e5:60 by local choice
(Reason: 3=D
** Bug watch added: Linux Kernel Bug Tracker #204785
https://bugzilla.kernel.org/show_bug.cgi?id=204785
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=204785
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
** Tags added: disco eoan
--
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/1597415
Title:
systemd-udevd: Error calling EVIOCSKEYCODE on device node
'/dev/input/event9' (scan code 0x150,
I also see fq_codel used as default:
# cat /proc/sys/net/core/default_qdisc
fq_codel
# ip addr
[...]
2: eth0: mtu 1500 qdisc fq_codel state UP
group default qlen 1000
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are
** Bug watch added: Debian Bug tracker #898060
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898060
** Also affects: linux (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898060
Importance: Unknown
Status: Unknown
** Also affects: linux (Fedora) via
https://b
Public bug reported:
Hi,
page poising is currently disabled in Ubuntu kernels:
$ grep PAGE_POISON /boot/config-4.13.0-32-generic
# CONFIG_PAGE_POISONING is not set
It is also disabled in mainline kernels:
$ grep PAGE_POISON /boot/config-4.14.16-041416-generic
# CONFIG_PAGE_POISONING is not set
** Tags added: artful 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/1436945
Title:
devel: consider fq_codel as the default qdisc for networking
Status in linux package in Ubuntu
** Bug watch added: Debian Bug tracker #890343
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890343
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890343
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Package changed: systemd (Debian) => linux (Debian)
--
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/1436945
Title:
devel: consider fq_codel as the default qdisc for networking
Status
The error messages about the sap-server are not there any longer in Ubuntu
17.10.
Thanks for the fix!
** Changed in: bluez (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubunt
I am still seeing this error with the 4.10.1-041001-generic mainline
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/1597415
Title:
systemd-udevd: Error calling EVIOCSKEYCODE on d
On Ubuntu 16.10 with this bluez package:
Package: bluez
Version: 5.41-0ubuntu3with
I no longer see the "Not enough handles to register service" messages.
** Tags added: xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in U
Axil Therian, could you please tell us the bug number you got when you
reported this upstream?
** Tags added: xenial yakkety
--
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/1486316
Title:
I am still seeing those error messages in mainline kernel 4.10.1.
--
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/1486316
Title:
lpc_ich: Resource conflict(s) found affecting gpio_ich
St
I have not seen this bug while using mainline kernels from 4.9.1 to
4.9.13 and now 4.10.1.
--
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/1384342
Title:
kernel messages intel_crtc_wait_f
This bug still exists in zesty:
# journalctl -b | grep bluetoothd
Mar 20 11:29:29 xeelee bluetoothd[1113]: Bluetooth daemon 5.43
Mar 20 11:29:29 xeelee bluetoothd[1113]: Starting SDP server
Mar 20 11:29:29 xeelee bluetoothd[1113]: Bluetooth management interface 1.14
initialized
Mar 20 11:29:29 xe
According to this:
https://raspberrypi.stackexchange.com/questions/40839/sap-error-on-
bluetooth-service-status
the error messages about SAP can be avoided by starting bluetoothd with
the "--noplugin=sap" option.
Since SAP is probably of little use in Ubuntu and since it does not work
anyway,
This bug still exists in xenial with kernel 4.5:
$ uname -a
Linux xeelee 4.5.0-040500-lowlatency #201603140130 SMP PREEMPT Mon Mar 14
05:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ journalctl |grep bluetoothd
Apr 08 20:24:43 xeelee bluetoothd[929]: Bluetooth daemon 5.37
Apr 08 20:24:43 xeele
> All tests produced the "not enough handles" message from bluetoothd.
> Is anyone successfully using bluetooth with these later ubuntu kernels?
On both of my systems I get the "not enough handles" messages but I got BT to
work for both my use cases:
- using a BT mouse on a laptop
- streaming a
The bug is still there in trusty:
$ symlinks -r /usr/share/doc/linux-doc/ | grep dangling | wc
156 624 21778
--
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/661306
Title:
dangl
I cannot reproduce the problem with trusty, therefore I am going to
close this bug...
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Since my initial report I updated the BIOS of this laptop:
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A19
11/14/2013
and today (after 8 days of uptime and perhaps 20 suspend/resume cycles)
the bug reappeared:
# /usr/lib/checkbox/bin/frequency_governors_test
2014-01-
I changed the bug description to state the difficulty of reproducing
this bug.
** Description changed:
- After a suspend/resume using the ondemand governor the system is very slow to
answer some inputs. The text output pauses for several seconds while I am
typing this text. Trying to scroll a
> The slowdown doesn't always happen, but it does appear to happen after
sometimes resuming from standby.
In my case I suspect that the problem might be caused by a non-
compatible power adapter (I am using several ones). Since I reported
the problem I changed this power adapter and did not see t
> Could you please confirm this issue exists with the latest development
release of Ubuntu?
I am using this system as my main computing platform and therefore I
cannot do tests that span several days.
> It will allow additional upstream developers to examine the issue.
Unfortunately my kernel is
Public bug reported:
I have a laptop with this WiFi controller:
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260
Flags: bus master, fast devsel, latency 0, IRQ 47
Memory at e2d0 (64-bit, non-pr
> Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
I did not use this WiFi controller with a previous Ubuntu version.
> Would it be possible for you to test the latest upstream kernel? Refer to
> https://wiki.ubuntu.com/KernelMainlineBuilds .
> Please test the lates
With this kernel:
ii linux-image-extra-3.16.0-29-generic
3.16.0-29.39 amd64Linux kernel
extra modules for version 3.16.0 on 64 bit x86 SMP
and this updated firmware:
ii linux-firmware 1.138.1
all Firm
> the kernel warnings do not happen either.
I spoke too soon. I saw those warnings again with kernel 3.16.0-29.39.
Therefore this bug cannot be reproduced at any time.
Dec 21 10:06:44 vougeot kernel: [ 340.419664] iwlwifi :02:00.0: RF_KILL
bit toggled to disable radio.
Dec 21 10:06:44 vou
Public bug reported:
I just saw this error in the kernel log:
[171056.176336] iwlwifi :02:00.0: Microcode SW error detected. Restarting
0x200.
[171056.176341] iwlwifi :02:00.0: CSR values:
[171056.1
The bug is still there in utopic and getting worse:
$ symlinks -r /usr/share/doc/linux-doc/ | grep dangling | wc
159 636 22178
--
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/6613
** Bug watch added: Debian Bug tracker #714974
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714974
** Also affects: linux (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714974
Importance: Unknown
Status: Unknown
** Bug watch added: Red Hat Bugzilla #739222
ht
Public bug reported:
Here is the relevant kernel config:
$ grep STACKPROTECTOR /boot/config-3.16.0-22-generic
CONFIG_HAVE_CC_STACKPROTECTOR=y
CONFIG_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR_NONE is not set
CONFIG_CC_STACKPROTECTOR_REGULAR=y
# CONFIG_CC_STACKPROTECTOR_STRONG is not set
Sin
> Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
It is difficult to say because I have seen only one instance of this
problem.
The same machine is running since a week with kernel 3.19 and the
problem did
> Did this issue start happening after an update/upgrade?
No idea. I only saw this problem once and I cannot reproduce it.
Therefore I do not know if it occurs rarely or if it occurs with
specific kernel+FW versions.
--
You received this bug notification because you are a member of Kernel
Packa
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Confirmed
--
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/1405842
Title:
Microcode SW error detected.
Status
Public bug reported:
I got the following warning in the kernel log:
[82452.464382] [ cut here ]
[82452.464501] WARNING: CPU: 3 PID: 2121 at
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47
assert_device_not_suspended.isra.8+0x43/0x50 [i915]()
[82452.4645
Another instance of this bug:
https://bbs.archlinux.org/viewtopic.php?id=183835
** Bug watch added: Red Hat Bugzilla #1133123
https://bugzilla.redhat.com/show_bug.cgi?id=1133123
** Also affects: linux (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1133123
Importance: Unknow
Here is another data point:
- kernel: linux-image-4.8.12-040812-generic (Ubuntu mainline kernel)
- CPU/GPU : Core i7-2640M
This kind of event is quite rare with mainline kernels (I cannot say the
same of Ubuntu kernels and that's why I use mainline kernels).
[231716.438851] [ cut he
Public bug reported:
Hi,
here are are messages from the bluetooth daemon:
$ journalctl -b | grep bluetoothd
Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41
Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server
Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management in
This bug no longer exists on my system with raring and the following
kernel:
Linux vougeot 3.8.0-29-generic #42-Ubuntu SMP Tue Aug 13 19:40:39 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
The bug is still there in saucy and linux-doc 3.11.0-15-generic :
$ symlinks -r /usr/share/doc/linux-doc/ | grep dangling | wc
155 620 21642
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Running frequency_governors_test sheds some light on this bug because it
exposes this error:
ERROROn demand performance vs maximum of 380.0% is not within 10.0%
margin
# /usr/lib/checkbox/bin/frequency_governors_test
2013-12-26 18:15:54 INFO System Capabilites:
2013-12-26 18:15:54 INFO
This bug is similar to bug #326149 but I preferred to report a new one because
this other bug:
- is closed
- concerns a very old kernel
- concerns a very different processor
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Public bug reported:
On my laptop with this CPU:
model name : Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz
I am using the ondemand governor:
$ cat /sys/devices/system/cpu/c*/cpufreq/scaling_governor
ondemand
ondemand
ondemand
ondemand
and the system is very slow to answer some inputs:
- the
This bug still occurs in saucy when /sys/class/drm/card0/device/power_profile
contains "low". I have not seem any lockup with "high" or "mid".
I also tried dynpm in /sys/class/drm/card0/device/power_method and had
an immediate lockup that forced me to reboot my computer.
--
You received this bu
I am closing this bug because I never saw it again and kernel 3.16 is
very old by now.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
I am closing this bug because it seems to have been fixed in more recent
microcode versions.
** Changed in: linux-firmware (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware i
This "bug" is still there is wily:
$ grep STACKPROTECTOR /boot/config-4.2.0-13-generic
CONFIG_HAVE_CC_STACKPROTECTOR=y
CONFIG_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR_NONE is not set
CONFIG_CC_STACKPROTECTOR_REGULAR=y
# CONFIG_CC_STACKPROTECTOR_STRONG is not set
--
You received this bug no
I am closing this bug because it is fixed in recent kernel versions.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/
Thank you for the "fix"!
How about enabling CONFIG_CC_STACKPROTECTOR_STRONG also for mainline
builds ?
--
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/1380025
Title:
linux could use CONF
The same problem exists in lunar and this package version:
Package: thermald
Version: 2.5.2-1
** Tags added: lunar
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1993566
Title:
dbu
** Tags added: kinetic lunar
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency in Ubuntu.
https://bugs.launchpad.net/bugs/1971186
Title:
Suggests linux-lowlatency-tools instead of linux-tools-lowlatency
Status in
** Tags added: kinetic lunar
--
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/1959384
Title:
CONFIG_IO_STRICT_DEVMEM could be enabled
Status in linux package in Ubuntu:
Confirmed
Bug d
The bug is still there in lunar:
# dmesg | grep PPM
[5.477076] ucsi_acpi USBC000:00: PPM init failed (-110)
# uname -a
Linux vougeot 6.2.0-18-generic #18-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 16
00:09:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
** Summary changed:
- usci_acpi USBC000:00: PPM
This bug is very old, and I do not see it any longer on a newer Dell
laptop and a newer Ubuntu release.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
This problem still exists in noble:
# journalctl | grep ConfigurationDirectory
Apr 15 11:00:12 vougeot (uetoothd)[3112]: bluetooth.service:
ConfigurationDirectory 'bluetooth' already exists but the mode is different.
(File system: 755 ConfigurationDirectoryMode: 555)
** Tags added: noble
--
** Tags added: noble
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1993566
Title:
dbus-daemon: Unknown group "power" in message bus configuration file
Status in thermald package in
** Tags added: noble
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency in Ubuntu.
https://bugs.launchpad.net/bugs/1971186
Title:
Suggests linux-lowlatency-tools instead of linux-tools-lowlatency
Status in linux-si
In Ubuntu noble:
$ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
/boot/config-6.8.0-22-generic:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-6.8.0-7-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
** Tags removed: kinetic lunar
** Tags added: noble
--
You received this bug notification becau
This bug is no longer present in kernel 6.8.0-22-generic from Ubuntu noble.
Thanks for the fix!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode x
Public bug reported:
Hi,
the linux-image-*-lowlatency kernel package suggests the linux-
lowlatency-tools package:
$ apt show linux-image-5.15.0-27-lowlatency
Package: linux-image-5.15.0-27-lowlatency
Version: 5.15.0-27.28
[...]
Suggests: fdutils, linux-doc | linux-lowlatency-source-5.15.0,
lin
Public bug reported:
Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access
of active io-memory ranges.
This could impact kernel debugability. In that case, you may reboot with
iomem=relaxed on the kernel command line to override this setting.
This config option is recommended
*** This bug is a duplicate of bug 1959384 ***
https://bugs.launchpad.net/bugs/1959384
** This bug has been marked a duplicate of bug 1959384
CONFIG_IO_STRICT_DEVMEM could be enabled
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags added: jammy
--
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/1959384
Title:
CONFIG_IO_STRICT_DEVMEM could be enabled
Status in linux package in Ubuntu:
Confirmed
Bug descripti
My system displays the same error message:
- hardware: TUXEDO InfinityBook S 15 Gen6
- kernel: mainline 5.11.14
It has only one NVMe drive and no Nvidia GPU.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
Public bug reported:
Hi,
no mainline kernel builds have been published since a while, and
available builds are a few versions old.
Can you do something about this problem ?
Thanks!
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notificatio
I am closing this bug since the error messages are not displayed any longer.
Thanks!
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
** Tags added: mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1993566
Title:
dbus-daemon: Unknown group "power" in message bus configuration file
Status in thermald package in
The fix a now upstream according to last comment.
Thanks!
** Changed in: linux
Status: New => Fix Released
** Changed in: snapd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Tags added: mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency in Ubuntu.
https://bugs.launchpad.net/bugs/1971186
Title:
Suggests linux-lowlatency-tools instead of linux-tools-lowlatency
Status in linux-s
** Tags added: mantic
--
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/1959384
Title:
CONFIG_IO_STRICT_DEVMEM could be enabled
Status in linux package in Ubuntu:
Confirmed
Bug descript
** Tags added: mantic
--
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/1912509
Title:
ucsi_acpi USBC000:00: PPM init failed (-110)
Status in linux package in Ubuntu:
Confirmed
Bug desc
This bug is fixed in recent kernels.
Thanks:
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/1806437
Title:
acpi PN
Public bug reported:
Hi,
when my system boots it logs the following warning in the journal:
$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth'
already exists but the mode is different. (File system: 755
ConfigurationDirectory
Public bug reported:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 0
apport information
** Tags added: apport-collected
** Description changed:
Hi,
here is the problem:
# journalctl | grep loop4
Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
Jun 23
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623912/+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/1979633
Ti
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623915/+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/1979633
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623916/+files/Lspci-vt.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/19
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623914/+files/IwConfig.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/19
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623919/+files/Lsusb-v.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/1979
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623921/+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
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623918/+files/Lsusb-t.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/1979
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623917/+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/1979633
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623920/+files/PaInfo.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/1979633
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623931/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623913/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623937/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623936/+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/1979633
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623935/+files/RfKill.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/1979633
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623938/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, whic
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623933/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623932/+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: "PulseList.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623934/+files/PulseList.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/
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1979633/+attachment/5623922/+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
Public bug reported:
Hi,
I see the following error message in the logs:
# journalctl | grep 'Unknown group "power"'
Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in
message bus configuration file
Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in messa
1 - 100 of 104 matches
Mail list logo
