[Kernel-packages] [Bug 1798400]
Noticed that in the forthcoming LibO 24.2, the "remote" is being given prominence, by moving its settings from the Tools ▸ Options ▸ LibreOffice Impress configuration dialog to the Slide Show ▸ Slide Show Settings menu. IMHO this makes it quite important to have this feature working as intended on all the supported platforms. The remote is meant to work either with a WIFI connection or a Bluetooth one. The current bug is about the Bluetooth connection. Bluetooth Connection As of today, because of the issue at hand, the Bluetooth connection is completely unusable on standard Linux distributions that use Pulseaudio (a detailed discussion why is in the previous comments). Notwithstanding the fact that this but is about the Bluetooth connection, I am providing also a few notes about the Wifi connection to highlight why the Bluetooth connection is so important and should be fixed. WIFI Connection --- Unfortunately, the WIFI option is practically unusable in almost every professional working environment, including universities and conferencing sites. This is because in all these environments the network is completely out of the user control, restricted in any possible way, heavily firewalled, with the wifi framework consisting of multiple access points under the same SSID. In a similar arrangement the possibility of the remote to reach LibO at a non-standard TCP port is erratic if not negligible. The impossibility to use the WIFI connection precisely in those real world environments where the usage of the remote would be most important is the reason why a working Bluetooth connection is needed. Note that in practice the WIFI connection situation could be improved by suggesting the possibility to let the presenter laptop connect to the internet via the mobile phone hotspot. This would need the remote app to try to connect to LibO not just via the phone default interface, but also on the network used for the hotspot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook
[Kernel-packages] [Bug 2013027] Re: Issues over broadcom brcmfmac43455 firmware
As mentioned it does not here. My system looks for the file `brcmfmac43455-sdio.clm_blob` not for `rcmfmac43455-sdio..clm_blob`, with being the same as for the `brcmfmac43455-sdio..txt`. Maybe the system firmware has a role in this... -- 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/2013027 Title: Issues over broadcom brcmfmac43455 firmware Status in linux-firmware package in Ubuntu: Expired Status in linux-firmware-raspi2 package in Ubuntu: Invalid Bug description: Hi, I have a Kodlix Z83-II minicomputer that employs a broadcom chipset for WIFI. The only way to make wifi on that PC work is to use the firmware from the windows image, even if that chipset is apparently managed in ubuntu. With the firmware files provided by ubuntu you get no 5GHz for wifi. The problem is that every time ubuntu updates the firmware package, firmware files dropped in /lib/firmware get overwritten, linking to some file in the cypress sub-directory. - Ideally, Ubuntu should provide all the firmware files that might be needed. Maybe this is not possible as there is a too large variety of different firmwares for broadcom chipsets or licesing issues preventing distribution. - As a second possibility, there should be a way to drop files in /lib/firmware 'side to side' to the distro ones, without having the risk of finding the manually added files rewritten. This implies that different pieces of hardware use firmware files with different filenames. Don't know if this is truly possible, as I do not know how the linux kernel decides the name of the firmware to load. - In cases like mine, it seems that the ubuntu firmware package puts in place symlinks to have brcmfmac43455 files point to the corresponding cypress cyfmac43455 files. Possibly, the package could avoid creating the symlinks if a brcmfmac43455 file is manually placed in lib/firmware. - As a last resort, I think that the documentation in `/usr/share/doc/linux-firmware` should be augmented to describe the most appropriate way to prevent custom firmware files from being rewritten: marking files not-writable? introducing diversions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013027] Re: Issues over broadcom brcmfmac43455 firmware
I have diagnosed the problem as follows.
My broadcom 43455 adapter needs:
1. a different brcm43455-sdio.txt file from the one supplied in ubuntu,
which is a cypress provided version.
2. a different brcm43455-sdio.bin file from the one supplied in ubuntu,
that again is a cypress provided version
3. a different brcm43455-sdio.clm_blob file from the one supplied in
ubuntu
Now, 1 and 2 are no issue: I can supply the files needed by my hardware and put
them side to side to the ubuntu supplied ones. This is because the system will
seek `brcm43455-sdio.AZW-Z83 II.{txt, bin} first.
Incidentally, the txt file can be easily taken from the nvram of my system,
while the bin file is the one that is supplied in armbian, libreelec etc, that
for some reason is not the same as the cypress one found in ubuntu.
The real problem is 3. And this is because without the file made for my
hardware, the wifi will work in the 2.4 GHz band, but not in the 5GHz
band. However the file name for this does not appear to be adapted to my
system. Namely, if I put a 'brcm43455-sdio.AZW-Z83 II.clm_blob' file
side to side to 'brcm43455-sdio.clm_blob' that will be ignored.
This makes it impossible to place board specific brcm files *side to
side* the those currently specified by the distro (unless I miss
something). If this is the case, then there are two possible
workarounds:
1. Make a deb file with a diversion for the clm_blob file
2. Use the brcmfmac module option `alternative_fw_path` to specify and
alternative firmware path for my brcm hardware and put my bin, txt and clm_blob
files there
However, I really tend to think that these are just ugly workarounds for
what is ultimately an issue with the brcmfmac kernel module. If the
module can determine that for by board the filename should be
`brcm43455-sdio.AZW-Z83 II.{txt,bin}` for the txt and bin pieces of the
firmware, then why cannot it look at `brcm43455-sdio.AZW-Z83
II.clm_blob` before falling back to `brcm43455-sdio.clm_blob`? That
would make it easy to put different firmwares in the the brcm firmware
directory side by side and make the framework that is already there for
the txt and bin files actually useful.
Please consider reopening the issue, passing it to the brcmfmac
maintainers.
--
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/2013027
Title:
Issues over broadcom brcmfmac43455 firmware
Status in linux-firmware package in Ubuntu:
Incomplete
Status in linux-firmware-raspi2 package in Ubuntu:
Invalid
Bug description:
Hi, I have a Kodlix Z83-II minicomputer that employs a broadcom
chipset for WIFI.
The only way to make wifi on that PC work is to use the firmware from
the windows image, even if that chipset is apparently managed in
ubuntu.
With the firmware files provided by ubuntu you get no 5GHz for wifi.
The problem is that every time ubuntu updates the firmware package,
firmware files dropped in /lib/firmware get overwritten, linking to
some file in the cypress sub-directory.
- Ideally, Ubuntu should provide all the firmware files that might be
needed. Maybe this is not possible as there is a too large variety of
different firmwares for broadcom chipsets or licesing issues
preventing distribution.
- As a second possibility, there should be a way to drop files in
/lib/firmware 'side to side' to the distro ones, without having the
risk of finding the manually added files rewritten. This implies that
different pieces of hardware use firmware files with different
filenames. Don't know if this is truly possible, as I do not know how
the linux kernel decides the name of the firmware to load.
- In cases like mine, it seems that the ubuntu firmware package puts
in place symlinks to have brcmfmac43455 files point to the
corresponding cypress cyfmac43455 files. Possibly, the package could
avoid creating the symlinks if a brcmfmac43455 file is manually placed
in lib/firmware.
- As a last resort, I think that the documentation in
`/usr/share/doc/linux-firmware` should be augmented to describe the
most appropriate way to prevent custom firmware files from being
rewritten: marking files not-writable? introducing diversions?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013027/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013027] Re: Issues over broadcom brcmfmac43455 firmware
Hope that now all what is needed to identify the issue is available. -- 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/2013027 Title: Issues over broadcom brcmfmac43455 firmware Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: New Bug description: Hi, I have a Kodlix Z83-II minicomputer that employs a broadcom chipset for WIFI. The only way to make wifi on that PC work is to use the firmware from the windows image, even if that chipset is apparently managed in ubuntu. With the firmware files provided by ubuntu you get no 5GHz for wifi. The problem is that every time ubuntu updates the firmware package, firmware files dropped in /lib/firmware get overwritten, linking to some file in the cypress sub-directory. - Ideally, Ubuntu should provide all the firmware files that might be needed. Maybe this is not possible as there is a too large variety of different firmwares for broadcom chipsets or licesing issues preventing distribution. - As a second possibility, there should be a way to drop files in /lib/firmware 'side to side' to the distro ones, without having the risk of finding the manually added files rewritten. This implies that different pieces of hardware use firmware files with different filenames. Don't know if this is truly possible, as I do not know how the linux kernel decides the name of the firmware to load. - In cases like mine, it seems that the ubuntu firmware package puts in place symlinks to have brcmfmac43455 files point to the corresponding cypress cyfmac43455 files. Possibly, the package could avoid creating the symlinks if a brcmfmac43455 file is manually placed in lib/firmware. - As a last resort, I think that the documentation in `/usr/share/doc/linux-firmware` should be augmented to describe the most appropriate way to prevent custom firmware files from being rewritten: marking files not-writable? introducing diversions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013027] Re: Issues over broadcom brcmfmac43455 firmware
** Attachment added: "My brcmfmac43455-sdio.txt" https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/2013027/+attachment/5681293/+files/4345r6nvram.txt -- 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/2013027 Title: Issues over broadcom brcmfmac43455 firmware Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: New Bug description: Hi, I have a Kodlix Z83-II minicomputer that employs a broadcom chipset for WIFI. The only way to make wifi on that PC work is to use the firmware from the windows image, even if that chipset is apparently managed in ubuntu. With the firmware files provided by ubuntu you get no 5GHz for wifi. The problem is that every time ubuntu updates the firmware package, firmware files dropped in /lib/firmware get overwritten, linking to some file in the cypress sub-directory. - Ideally, Ubuntu should provide all the firmware files that might be needed. Maybe this is not possible as there is a too large variety of different firmwares for broadcom chipsets or licesing issues preventing distribution. - As a second possibility, there should be a way to drop files in /lib/firmware 'side to side' to the distro ones, without having the risk of finding the manually added files rewritten. This implies that different pieces of hardware use firmware files with different filenames. Don't know if this is truly possible, as I do not know how the linux kernel decides the name of the firmware to load. - In cases like mine, it seems that the ubuntu firmware package puts in place symlinks to have brcmfmac43455 files point to the corresponding cypress cyfmac43455 files. Possibly, the package could avoid creating the symlinks if a brcmfmac43455 file is manually placed in lib/firmware. - As a last resort, I think that the documentation in `/usr/share/doc/linux-firmware` should be augmented to describe the most appropriate way to prevent custom firmware files from being rewritten: marking files not-writable? introducing diversions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013027] Re: Issues over broadcom brcmfmac43455 firmware
** Attachment added: "dmesg with the correct firmware" https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/2013027/+attachment/5681292/+files/dmesg-new.log -- 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/2013027 Title: Issues over broadcom brcmfmac43455 firmware Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: New Bug description: Hi, I have a Kodlix Z83-II minicomputer that employs a broadcom chipset for WIFI. The only way to make wifi on that PC work is to use the firmware from the windows image, even if that chipset is apparently managed in ubuntu. With the firmware files provided by ubuntu you get no 5GHz for wifi. The problem is that every time ubuntu updates the firmware package, firmware files dropped in /lib/firmware get overwritten, linking to some file in the cypress sub-directory. - Ideally, Ubuntu should provide all the firmware files that might be needed. Maybe this is not possible as there is a too large variety of different firmwares for broadcom chipsets or licesing issues preventing distribution. - As a second possibility, there should be a way to drop files in /lib/firmware 'side to side' to the distro ones, without having the risk of finding the manually added files rewritten. This implies that different pieces of hardware use firmware files with different filenames. Don't know if this is truly possible, as I do not know how the linux kernel decides the name of the firmware to load. - In cases like mine, it seems that the ubuntu firmware package puts in place symlinks to have brcmfmac43455 files point to the corresponding cypress cyfmac43455 files. Possibly, the package could avoid creating the symlinks if a brcmfmac43455 file is manually placed in lib/firmware. - As a last resort, I think that the documentation in `/usr/share/doc/linux-firmware` should be augmented to describe the most appropriate way to prevent custom firmware files from being rewritten: marking files not-writable? introducing diversions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013027] Re: Issues over broadcom brcmfmac43455 firmware
** Attachment added: "my brcmfmac43455-sdio.clm_blob" https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/2013027/+attachment/5681265/+files/brcmfmac43455-sdio.clm_blob -- 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/2013027 Title: Issues over broadcom brcmfmac43455 firmware Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: New Bug description: Hi, I have a Kodlix Z83-II minicomputer that employs a broadcom chipset for WIFI. The only way to make wifi on that PC work is to use the firmware from the windows image, even if that chipset is apparently managed in ubuntu. With the firmware files provided by ubuntu you get no 5GHz for wifi. The problem is that every time ubuntu updates the firmware package, firmware files dropped in /lib/firmware get overwritten, linking to some file in the cypress sub-directory. - Ideally, Ubuntu should provide all the firmware files that might be needed. Maybe this is not possible as there is a too large variety of different firmwares for broadcom chipsets or licesing issues preventing distribution. - As a second possibility, there should be a way to drop files in /lib/firmware 'side to side' to the distro ones, without having the risk of finding the manually added files rewritten. This implies that different pieces of hardware use firmware files with different filenames. Don't know if this is truly possible, as I do not know how the linux kernel decides the name of the firmware to load. - In cases like mine, it seems that the ubuntu firmware package puts in place symlinks to have brcmfmac43455 files point to the corresponding cypress cyfmac43455 files. Possibly, the package could avoid creating the symlinks if a brcmfmac43455 file is manually placed in lib/firmware. - As a last resort, I think that the documentation in `/usr/share/doc/linux-firmware` should be augmented to describe the most appropriate way to prevent custom firmware files from being rewritten: marking files not-writable? introducing diversions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013027] Re: Issues over broadcom brcmfmac43455 firmware
Reopened as I see the issue again... ** Changed in: linux-firmware-raspi2 (Ubuntu) Status: Invalid => New ** Changed in: linux-firmware (Ubuntu) Status: Expired => New ** Attachment added: "dmesg with ubuntu firmware" https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/2013027/+attachment/5681264/+files/dmesg-ubuntu.log -- 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/2013027 Title: Issues over broadcom brcmfmac43455 firmware Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: New Bug description: Hi, I have a Kodlix Z83-II minicomputer that employs a broadcom chipset for WIFI. The only way to make wifi on that PC work is to use the firmware from the windows image, even if that chipset is apparently managed in ubuntu. With the firmware files provided by ubuntu you get no 5GHz for wifi. The problem is that every time ubuntu updates the firmware package, firmware files dropped in /lib/firmware get overwritten, linking to some file in the cypress sub-directory. - Ideally, Ubuntu should provide all the firmware files that might be needed. Maybe this is not possible as there is a too large variety of different firmwares for broadcom chipsets or licesing issues preventing distribution. - As a second possibility, there should be a way to drop files in /lib/firmware 'side to side' to the distro ones, without having the risk of finding the manually added files rewritten. This implies that different pieces of hardware use firmware files with different filenames. Don't know if this is truly possible, as I do not know how the linux kernel decides the name of the firmware to load. - In cases like mine, it seems that the ubuntu firmware package puts in place symlinks to have brcmfmac43455 files point to the corresponding cypress cyfmac43455 files. Possibly, the package could avoid creating the symlinks if a brcmfmac43455 file is manually placed in lib/firmware. - As a last resort, I think that the documentation in `/usr/share/doc/linux-firmware` should be augmented to describe the most appropriate way to prevent custom firmware files from being rewritten: marking files not-writable? introducing diversions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012520] Re: USB3 to ethernet adapter stops working (ax88179)
Just a quick note to inform that the issue is also present with the ubuntu 6.1.0-1008-oem kernel which should be extra close to the tip of mainline. Thus, the issue is most likely still present in mainline. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2012520 Title: USB3 to ethernet adapter stops working (ax88179) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: On a machine with the ax88179 USB3 ethernet adapter, the adapter works poorly. As long as there is a moderate usage of the ethernet connection everything seems to work fine. As soon as the usage pattern changes and a continuous throughput is required (typical case teleconferencing via teams, skype, etc) the adapter stops working and the following line gets repeated many many times in the system logs: ax88179_178a 4-1.4:2.0 eth1: Failed to write reg index 0x0001: -32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 22 15:35:38 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (1130 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-06-03 (292 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2012520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013027] Re: Issues over broadcom brcmfmac43455 firmware
>apport-collect 2013027' and attach dmesg from both when using the original ubuntu and the windows firmware. I'll add dmesg after re-install of of the original linux-firmware from ubuntu which should be close to what original ubuntu does but might not be totally equivalent to it in case some non-ubuntu file is not overwritten/removed. Hope it'll be OK. -- 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/2013027 Title: Issues over broadcom brcmfmac43455 firmware Status in linux-firmware package in Ubuntu: Incomplete Status in linux-firmware-raspi2 package in Ubuntu: Invalid Bug description: Hi, I have a Kodlix Z83-II minicomputer that employs a broadcom chipset for WIFI. The only way to make wifi on that PC work is to use the firmware from the windows image, even if that chipset is apparently managed in ubuntu. With the firmware files provided by ubuntu you get no 5GHz for wifi. The problem is that every time ubuntu updates the firmware package, firmware files dropped in /lib/firmware get overwritten, linking to some file in the cypress sub-directory. - Ideally, Ubuntu should provide all the firmware files that might be needed. Maybe this is not possible as there is a too large variety of different firmwares for broadcom chipsets or licesing issues preventing distribution. - As a second possibility, there should be a way to drop files in /lib/firmware 'side to side' to the distro ones, without having the risk of finding the manually added files rewritten. This implies that different pieces of hardware use firmware files with different filenames. Don't know if this is truly possible, as I do not know how the linux kernel decides the name of the firmware to load. - In cases like mine, it seems that the ubuntu firmware package puts in place symlinks to have brcmfmac43455 files point to the corresponding cypress cyfmac43455 files. Possibly, the package could avoid creating the symlinks if a brcmfmac43455 file is manually placed in lib/firmware. - As a last resort, I think that the documentation in `/usr/share/doc/linux-firmware` should be augmented to describe the most appropriate way to prevent custom firmware files from being rewritten: marking files not-writable? introducing diversions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012520] Re: USB3 to ethernet adapter stops working (ax88179)
Following trace is also obtained: [18818.672366] [ cut here ] [18818.672374] NETDEV WATCHDOG: enxf8e43b7bdd6c (ax88179_178a): transmit queue 0 timed out [18818.672422] WARNING: CPU: 3 PID: 38259 at net/sched/sch_generic.c:529 dev_watchdog+0x21f/0x230 [18818.672437] Modules linked in: cdc_mbim cdc_wdm cdc_ncm cdc_ether tls snd_seq_dummy ccm nft_masq nft_chain_nat nf_nat nvme_fabrics bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt cmac algif_hash algif_skcipher af_alg bnep ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_comment xt_recent xt_multiport nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack snd_hda_codec_hdmi nf_defrag_ipv6 snd_sof_pci_intel_cnl nf_defrag_ipv4 snd_sof_intel_hda_common nft_compat soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_hda_codec_realtek snd_soc_acpi soundwire_bus snd_hda_codec_generic ledtrig_audio snd_soc_core [18818.672556] snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg intel_rapl_msr snd_intel_sdw_acpi intel_rapl_common snd_hda_codec intel_tcc_cooling nf_tables snd_hda_core x86_pkg_temp_thermal intel_powerclamp btusb coretemp nfnetlink binfmt_misc snd_hwdep btrtl snd_pcm btbcm iwlmvm uvcvideo btintel kvm_intel snd_seq_midi btmtk mei_hdcp mei_pxp snd_seq_midi_event mac80211 videobuf2_vmalloc kvm libarc4 snd_rawmidi videobuf2_memops bluetooth videobuf2_v4l2 snd_seq videobuf2_common rapl snd_seq_device videodev ecdh_generic intel_cstate nls_iso8859_1 snd_timer input_leds mc joydev ecc iwlwifi snd cmdlinepart serio_raw intel_wmi_thunderbolt spi_nor mei_me mtd cfg80211 soundcore mei intel_pch_thermal intel_hid mac_hid sparse_keymap acpi_pad sch_fq_codel msr parport_pc ppdev lp parport ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid ax88179_178a usbnet mii i915 drm_bud dy [18818.672677] i2c_algo_bit ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt rtsx_pci_sdmmc nvme i2c_i801 spi_intel_pci fb_sys_fops crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd xhci_pci psmouse nvme_core r8169 i2c_smbus spi_intel realtek thunderbolt rtsx_pci drm ahci libahci xhci_pci_renesas wmi video [18818.672720] CPU: 3 PID: 38259 Comm: skypeforlinux Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu [18818.672726] Hardware name: SCHENKER SCHENKER_SLIM14_SSL14L19/N141CU , BIOS 1.07.04RTR1 10/02/2019 [18818.672729] RIP: 0010:dev_watchdog+0x21f/0x230 [18818.672738] Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 ef ac 70 01 01 e8 c6 9d f8 ff 44 89 f1 4c 89 e6 48 c7 c7 a8 da d0 b0 48 89 c2 e8 89 e3 1b 00 <0f> 0b e9 22 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 [18818.672741] RSP: :a020869bbdb0 EFLAGS: 00010246 [18818.672746] RAX: RBX: 8e955101a4c8 RCX: [18818.672749] RDX: RSI: RDI: [18818.672751] RBP: a020869bbdd8 R08: R09: [18818.672754] R10: R11: R12: 8e955101a000 [18818.672756] R13: 8e955101a41c R14: R15: [18818.672759] FS: 7f5bfb1b9640() GS:8e96706c() knlGS: [18818.672762] CS: 0010 DS: ES: CR0: 80050033 [18818.672765] CR2: 0e0819391000 CR3: 000199538006 CR4: 003706e0 [18818.672768] Call Trace: [18818.672771] [18818.672776] ? pfifo_fast_reset+0x170/0x170 [18818.672784] call_timer_fn+0x29/0x160 [18818.672789] ? pfifo_fast_reset+0x170/0x170 [18818.672795] __run_timers.part.0+0x1e9/0x290 [18818.672799] ? ktime_get+0x43/0xc0 [18818.672805] ? lapic_next_deadline+0x2c/0x50 [18818.672811] ? clockevents_program_event+0xb2/0x140 [18818.672818] run_timer_softirq+0x2a/0x60 [18818.672822] __do_softirq+0xd5/0x32a [18818.672827] ? hrtimer_interrupt+0x12b/0x240 [18818.672832] __irq_exit_rcu+0x8d/0xd0 [18818.672839] irq_exit_rcu+0xe/0x20 [18818.672845] sysvec_apic_timer_interrupt+0x43/0xb0 [18818.672851] asm_sysvec_apic_timer_interrupt+0x1b/0x20 [18818.672858] RIP: 0033:0x7f5c198a5a75 [18818.672862] Code: 3c 45 31 c0 90 0f b6 14 16 48 83 c1 01 41 83 c0 01 48 83 c6 01 41 0f af d1 41 89 d7 0f b6 56 ff 41 0f af d2 44 01 fa c1 fa 10 <88> 51 ff 48 63 57 3c 44 39 c2 7f cf 4c 8b 87 a8 00 00 00 41 83 c5 [18818.672866] RSP: 002b:7f5bfb1b81b8 EFLAGS: 0206 [18818.672869] RAX: 018ad4f2 RBX: 0001 RCX: 0e08104959d1
[Kernel-packages] [Bug 2012520] [NEW] USB3 to ethernet adapter stops working (ax88179)
Public bug reported: On a machine with the ax88179 USB3 ethernet adapter, the adapter works poorly. As long as there is a moderate usage of the ethernet connection everything seems to work fine. As soon as the usage pattern changes and a continuous throughput is required (typical case teleconferencing via teams, skype, etc) the adapter stops working and the following line gets repeated many many times in the system logs: ax88179_178a 4-1.4:2.0 eth1: Failed to write reg index 0x0001: -32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 22 15:35:38 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (1130 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-06-03 (292 days ago) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2012520 Title: USB3 to ethernet adapter stops working (ax88179) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: On a machine with the ax88179 USB3 ethernet adapter, the adapter works poorly. As long as there is a moderate usage of the ethernet connection everything seems to work fine. As soon as the usage pattern changes and a continuous throughput is required (typical case teleconferencing via teams, skype, etc) the adapter stops working and the following line gets repeated many many times in the system logs: ax88179_178a 4-1.4:2.0 eth1: Failed to write reg index 0x0001: -32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 22 15:35:38 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (1130 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-06-03 (292 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2012520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007158] [NEW] kernel oops with external usb-c hub with ethernet port
Public bug reported: Using an external USB-C hub with hdmi, usb and ethernet ports, I constantly see the following after ~ a couple of hours of usage: CPU: 7 PID: 137 Comm: irq/122-pciehp Tainted: P OE 5.15.0-60-generic #66-Ubuntu [37914.942824] Hardware name: SCHENKER SCHENKER_SLIM14_SSL14L19/N141CU , BIOS 1.07.04RTR1 10/02/2019 [37914.942825] RIP: 0010:ring_interrupt_active+0x1fe/0x270 [thunderbolt] [37914.942849] Code: 4c 89 4d c8 44 89 45 d4 e8 6f 71 e9 d0 4c 8b 4d c8 44 8b 45 d4 4c 89 e1 48 89 c6 4c 89 f2 48 c7 c7 d8 b8 40 c0 e8 c0 21 32 d1 <0f> 0b e9 0c ff ff ff 41 0f b6 47 78 d3 e0 41 09 c5 e9 cb fe ff ff [37914.942851] RSP: :b4048078ba90 EFLAGS: 00010086 [37914.942853] RAX: RBX: RCX: 0027 [37914.942854] RDX: 8abf707e0588 RSI: 0001 RDI: 8abf707e0580 [37914.942856] RBP: b4048078bad8 R08: 0003 R09: a9a0 [37914.942857] R10: R11: 0001 R12: c040a44b [37914.942858] R13: 00038200 R14: 8abc01b834c0 R15: 8abc038ac3c0 [37914.942859] FS: () GS:8abf707c() knlGS: [37914.942861] CS: 0010 DS: ES: CR0: 80050033 [37914.942862] CR2: 555aaf675f14 CR3: 00014f948004 CR4: 003706e0 [37914.942864] Call Trace: [37914.942865] [37914.942869] tb_ring_start+0x192/0x360 [thunderbolt] [37914.942880] tb_ctl_start+0x1d/0xb0 [thunderbolt] [37914.942892] tb_domain_runtime_resume+0x1a/0x40 [thunderbolt] [37914.942907] nhi_runtime_resume+0x64/0x70 [thunderbolt] [37914.942918] pci_pm_runtime_resume+0xb2/0xd0 [37914.942922] ? pci_pm_freeze_noirq+0x110/0x110 [37914.942924] __rpm_callback+0x4a/0x130 [37914.942928] ? pci_pm_freeze_noirq+0x110/0x110 [37914.942930] rpm_callback+0x67/0x70 [37914.942932] ? pci_pm_freeze_noirq+0x110/0x110 [37914.942933] rpm_resume+0x519/0x7c0 [37914.942936] ? pde_put+0x7c/0xb0 [37914.942939] __pm_runtime_resume+0x52/0x90 [37914.942942] __device_release_driver+0x2f/0x2a0 [37914.942945] device_release_driver+0x29/0x40 [37914.942948] pci_stop_bus_device+0x74/0xa0 [37914.942954] pci_stop_bus_device+0x30/0xa0 [37914.942956] pci_stop_bus_device+0x41/0xa0 [37914.942958] pci_stop_and_remove_bus_device+0x13/0x30 [37914.942960] pciehp_unconfigure_device+0x7e/0x140 [37914.942964] pciehp_disable_slot+0x6c/0x100 [37914.942967] pciehp_handle_presence_or_link_change+0xb7/0x110 [37914.942970] pciehp_ist+0x19a/0x1b0 [37914.942973] ? irq_forced_thread_fn+0x90/0x90 [37914.942977] irq_thread_fn+0x25/0x70 [37914.942980] irq_thread+0xdc/0x1b0 [37914.942983] ? irq_thread_fn+0x70/0x70 [37914.942986] ? irq_thread_check_affinity+0x100/0x100 [37914.942989] kthread+0x127/0x150 [37914.942992] ? set_kthread_struct+0x50/0x50 [37914.942995] ret_from_fork+0x1f/0x30 [37914.942999] [37914.943000] ---[ end trace 3d6e16cc93f67574 ]--- [37914.943004] [ cut here ] [37914.943004] thunderbolt :03:00.0: interrupt for RX ring 0 is already enabled [37914.943030] WARNING: CPU: 7 PID: 137 at drivers/thunderbolt/nhi.c:111 ring_interrupt_active+0x1fe/0x270 [thunderbolt] [37914.943043] Modules linked in: cdc_mbim cdc_wdm cdc_ncm usbhid ax88179_178a snd_seq_dummy hid_generic hidp hid r8153_ecm cdc_ether usbnet r8152 mii ccm veth nft_masq nvme_fabrics nft_chain_nat nf_nat bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cmac algif_hash algif_skcipher af_alg bnep ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_comment xt_recent xt_multiport nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nft_counter snd_hda_codec_hdmi snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc _core [37914.943081] snd_hda_codec_realtek snd_hda_codec_generic snd_compress ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec nf_tables snd_hda_core snd_hwdep nfnetlink binfmt_misc iwlmvm(OE) snd_pcm intel_rapl_msr snd_seq_midi intel_rapl_common mac80211(OE) intel_tcc_cooling x86_pkg_temp_thermal snd_seq_midi_event uvcvideo mei_hdcp btusb intel_powerclamp videobuf2_vmalloc libarc4 snd_rawmidi btrtl videobuf2_memops coretemp snd_seq btbcm videobuf2_v4l2 videobuf2_common btintel snd_seq_device iwlwifi(OE) snd_timer nls_iso8859_1 videodev bluetooth snd cfg80211(OE) joydev kvm_intel ecdh_generic mc ecc kvm rapl intel_cstate input_leds serio_raw intel_wmi_thunderbolt soundcore compat(OE) mei_me
[Kernel-packages] [Bug 1798400]
Noticed that among the many tips of the day, LibO also suggests to use Android or IPhone to remotely control an Impress presentation. The "more info" page then excplicitly declares that the feature is cross platform "GNU/Linux, Windows or macOS." either via Bluetooth or Wifi. However to use the feature with bluetooth on linux has been impossible for the last 5 years, because the feature is broken on this platform (this bug provides a diagnosis of the underlying issue). Using the feature with wifi is equally problematic, because those places where you need to deliver a presentation are typically those very places where you do not control the wifi network that may make it impossible for the computer and the phone to communicate. As a consequence, this tip of the day looks inappropriate on linux, making many users waste a significant amount of time trying to use a feature that simply cannot work. May I suggest removing this tip of the day on linux? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1977526] Re: Regression: upgrade to ubuntu 22.04 broke wifi access to infrastructure access point
*** This bug is a duplicate of bug 1958267 *** https://bugs.launchpad.net/bugs/1958267 In fact a duplicate, sorry for the noise ** This bug has been marked a duplicate of bug 1958267 wpa can't connect to servers using TLS 1.1 or older -- 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/1977526 Title: Regression: upgrade to ubuntu 22.04 broke wifi access to infrastructure access point Status in linux package in Ubuntu: Confirmed Bug description: Today I have updated from 20.04 to 22.04. Now it is impossible to connect to ALMAWIFI that is my university wifi network. Being this part of EDUROAM, I strongly suspect that EDUROAM has been broken as well. The system seems to be able to connect to regular wifi networks, such as my mobile phone hotspot. However the connection to this site using WPA2 enterprise, PEAP and MSCHAP2 has now become impossible. The network manager applet keeps asking for the network password without being able to establish a connection. On the dmesg log I see: send auth to 34:62:88:c9:44:8e (try 1/3) [ 322.806267] wlan0: authenticated [ 322.806853] wlan0: VHT capa missing/short, disabling VHT/HE/EHT [ 322.807003] wlan0: associate with 34:62:88:c9:44:8e (try 1/3) [ 322.911089] wlan0: associate with 34:62:88:c9:44:8e (try 2/3) [ 322.913192] wlan0: RX AssocResp from 34:62:88:c9:44:8e (capab=0x101 status=12 aid=0) [ 322.913208] wlan0: 34:62:88:c9:44:8e denied association (code=12) [ 333.076375] wlan0: authenticate with 34:62:88:c9:44:8e [ 333.076416] wlan0: bad VHT capabilities, disabling VHT [ 333.076421] wlan0: Invalid HE elem, Disable HE [ 333.080260] wlan0: send auth to 34:62:88:c9:44:8e (try 1/3) [ 333.110076] wlan0: authenticated [ 333.110537] wlan0: VHT capa missing/short, disabling VHT/HE/EHT [ 333.114179] wlan0: associate with 34:62:88:c9:44:8e (try 1/3) [ 333.117425] wlan0: RX AssocResp from 34:62:88:c9:44:8e (capab=0x111 status=0 aid=3) [ 333.126642] wlan0: associated [ 333.152883] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 34:62:88:c9:44:8e [ 348.360075] wlan0: deauthenticating from 34:62:88:c9:44:8e by local choice (Reason: 3=DEAUTH_LEAVING) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.35.38 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1592 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jun 3 15:54:17 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (838 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eth0 no wireless extensions. wlan0 no wireless extensions. MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-35-generic N/A linux-backports-modules-5.15.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-06-03 (0 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977526] [NEW] Regression: upgrade to ubuntu 22.04 broke wifi access to infrastructure access point
Public bug reported: Today I have updated from 20.04 to 22.04. Now it is impossible to connect to ALMAWIFI that is my university wifi network. Being this part of EDUROAM, I strongly suspect that EDUROAM has been broken as well. The system seems to be able to connect to regular wifi networks, such as my mobile phone hotspot. However the connection to this site using WPA2 enterprise, PEAP and MSCHAP2 has now become impossible. The network manager applet keeps asking for the network password without being able to establish a connection. On the dmesg log I see: send auth to 34:62:88:c9:44:8e (try 1/3) [ 322.806267] wlan0: authenticated [ 322.806853] wlan0: VHT capa missing/short, disabling VHT/HE/EHT [ 322.807003] wlan0: associate with 34:62:88:c9:44:8e (try 1/3) [ 322.911089] wlan0: associate with 34:62:88:c9:44:8e (try 2/3) [ 322.913192] wlan0: RX AssocResp from 34:62:88:c9:44:8e (capab=0x101 status=12 aid=0) [ 322.913208] wlan0: 34:62:88:c9:44:8e denied association (code=12) [ 333.076375] wlan0: authenticate with 34:62:88:c9:44:8e [ 333.076416] wlan0: bad VHT capabilities, disabling VHT [ 333.076421] wlan0: Invalid HE elem, Disable HE [ 333.080260] wlan0: send auth to 34:62:88:c9:44:8e (try 1/3) [ 333.110076] wlan0: authenticated [ 333.110537] wlan0: VHT capa missing/short, disabling VHT/HE/EHT [ 333.114179] wlan0: associate with 34:62:88:c9:44:8e (try 1/3) [ 333.117425] wlan0: RX AssocResp from 34:62:88:c9:44:8e (capab=0x111 status=0 aid=3) [ 333.126642] wlan0: associated [ 333.152883] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 34:62:88:c9:44:8e [ 348.360075] wlan0: deauthenticating from 34:62:88:c9:44:8e by local choice (Reason: 3=DEAUTH_LEAVING) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.35.38 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1592 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jun 3 15:54:17 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (838 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eth0 no wireless extensions. wlan0 no wireless extensions. MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-35-generic N/A linux-backports-modules-5.15.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-06-03 (0 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1977526 Title: Regression: upgrade to ubuntu 22.04 broke wifi access to infrastructure access point Status in linux package in Ubuntu: Confirmed Bug description: Today I have updated from 20.04 to 22.04. Now it is impossible to connect to ALMAWIFI that is my university wifi network. Being this part of EDUROAM, I strongly suspect that EDUROAM has been broken as well. The system seems to be able to connect to regular wifi networks, such as my mobile phone hotspot. However the connection to this site using WPA2 enterprise, PEAP and MSCHAP2 has now become impossible. The network manager applet keeps asking for the network password without being able to establish a connection. On the dmesg log I see: send auth to 34:62:88:c9:44:8e (try 1/3) [ 322.806267] wlan0: authenticated [ 322.806853] wlan0: VHT capa missing/short, disabling VHT/HE/EHT [ 322.807003] wlan0: associate with 34:62:88:c9:44:8e (try 1/3) [ 322.911089] wlan0: associate with 34:62:88:c9:44:8e (try 2/3) [ 322.913192] wlan0: RX AssocResp from 34:62:88:c9:44:8e (capab=0x101
[Kernel-packages] [Bug 1798400]
The bug is still there as of LibO 7.3.x. Up in comment 12 (https://bugs.documentfoundation.org/show_bug.cgi?id=120663#c12) there is a nice analysis of the underlying problem why the remote cannot work. Established that, I think that most users go used to the fact that the remote functionality does not work in linux. Personally, I have uninstalled the android app on the phone so I do not have an unfortunate reminder about it. In fact, the real issue is probably the advertisement of a functionality that is not there. For the time being I suggest disabling the remote-via-bluetooth functionality in linux and closing the bug by simply saying that the remote via bluetooth cannot be supported on linux where there are evidently issues that span other software pieces such as the bluetooth stack and pulse audio. To the best of my understanding, these involve the hijacking of the default rfcomm channel by pulse audio before it even needs it and the lack of a standard approach to let other applications find a free channel to use and advertise it to their counterparts. Alternatively (but I would not consider this a good solution), the configuration options could be enhanced to add the possibility to choose a bluetooth channel in libreoffice and in the mobile phone application, so that the user can manually work around the fact that the predefined channel is locked by some other application. As a final point, note that even if the remote-via-wifi may seem a good alternative, in fact in most cases it is practically useless. In most cases, presentations will not be given at a place where you control the network, but at sites with site-provided wifi, such as universities, schools, conference places, business sites, etc. All these locations tend to have wifi deployments that block stuff on the ports used by impress remote. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version:
[Kernel-packages] [Bug 1798400] Re: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic
Bug still there. In most situations the remote cannot be used at all. Not via bluetooth (because of this issue), neither via wifi (because you typically do presentations at sites where you do not control the wifi network and traffic to the relevant ports gets blocked). Suggested upstream some possible solutions including stop advertising the functionality. Consider closing as Wontfix because I think there is really nothing that downstream can do about it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953166] [NEW] Kernel bugs out with packet writing on DVD RW, system remains unable to shutdown cleanly and needs power cycling
Public bug reported: Hi, trying to use packet writing on a DVD RW media with ubuntu 20.04 I see a kernel bug. This is what I am doing: 1) Preparing a dvdrw with the udf filesystem with mkudffs --media- type=dvdrw --spartable=2 /dev/pktcdvd/pktcdvd0 after having erased it with growisofs -Z /dev/sr0=/dev/zero. 2) Mouting the filesystem 3) Trying to write some files on it I see the writeback cache getting dirty and then staying dirty forever, while the kernel says [ cut here ] [ 1738.892880] kernel BUG at drivers/block/pktcdvd.c:2411! [ 1738.892894] invalid opcode: [#1] SMP NOPTI [ 1738.892902] CPU: 0 PID: 8493 Comm: kworker/u16:5 Tainted: G OE 5.11.0-41-generic #45~20.04.1-Ubuntu [ 1738.892909] Hardware name: SCHENKER SCHENKER_SLIM14_SSL14L19/N141CU , BIOS 1.07.04RTR1 10/02/2019 [ 1738.892913] Workqueue: writeback wb_workfn (flush-252:0) [ 1738.892927] RIP: 0010:pkt_submit_bio+0x39d/0x4b0 [pktcdvd] [ 1738.892939] Code: 41 3b 45 40 7c 0b 41 83 7d 44 01 0f 84 cd 00 00 00 4c 89 ff c6 07 00 0f 1f 40 00 4c 89 e7 c6 07 00 0f 1f 40 00 e9 08 ff ff ff <0f> 0b 0f 0b 4c 89 c8 31 c9 e9 96 fe ff ff 48 c7 c2 e0 17 44 c1 be [ 1738.892945] RSP: 0018:b84c43bd3728 EFLAGS: 00010283 [ 1738.892950] RAX: 17a8 RBX: 97508f66f800 RCX: 17a7 [ 1738.892955] RDX: 1980 RSI: 17c0 RDI: 0040 [ 1738.892958] RBP: b84c43bd37a0 R08: 0200 R09: ffc0 [ 1738.892962] R10: 1780 R11: R12: 974fd2412800 [ 1738.892966] R13: R14: 97513f5f2800 R15: 9751584f9f50 [ 1738.892970] FS: () GS:97533060() knlGS: [ 1738.892975] CS: 0010 DS: ES: CR0: 80050033 [ 1738.892979] CR2: 039f9000 CR3: 0003dfe10005 CR4: 003726f0 [ 1738.892984] Call Trace: [ 1738.892987] ? ktime_get+0x3e/0xa0 [ 1738.892997] ? blk_queue_enter+0x18d/0x240 [ 1738.893005] ? submit_bio_checks+0x1d0/0x5d0 [ 1738.893011] ? mempool_alloc_slab+0x17/0x20 [ 1738.893017] ? mempool_alloc+0x64/0x180 [ 1738.893023] submit_bio_noacct+0x112/0x4f0 [ 1738.893030] submit_bio+0x51/0x1a0 [ 1738.893036] ? bio_add_page+0x3b/0x90 [ 1738.893045] __mpage_writepage+0x7fe/0x8f0 [ 1738.893052] ? find_get_pages_range_tag+0x26c/0x300 [ 1738.893057] ? __mod_memcg_lruvec_state+0x25/0xe0 [ 1738.893063] ? clear_page_dirty_for_io+0xdb/0x1b0 [ 1738.893071] write_cache_pages+0x190/0x430 [ 1738.893078] ? clean_buffers+0x70/0x70 [ 1738.893085] ? udf_block_map+0xf0/0xf0 [udf] [ 1738.893099] mpage_writepages+0x77/0x100 [ 1738.893104] ? udf_block_map+0xf0/0xf0 [udf] [ 1738.893114] ? udf_time_to_disk_stamp+0x52/0x140 [udf] [ 1738.893129] udf_writepages+0x15/0x20 [udf] [ 1738.893140] do_writepages+0x43/0xd0 [ 1738.893147] ? udf_update_inode+0x36f/0x830 [udf] [ 1738.893158] __writeback_single_inode+0x44/0x2b0 [ 1738.893165] writeback_sb_inodes+0x22d/0x4c0 [ 1738.893173] __writeback_inodes_wb+0x56/0xf0 [ 1738.893179] wb_writeback+0x1ea/0x2a0 [ 1738.893186] wb_workfn+0x31b/0x490 [ 1738.893193] ? __update_idle_core+0x9b/0xb0 [ 1738.893201] process_one_work+0x220/0x3c0 [ 1738.893207] worker_thread+0x4d/0x3f0 [ 1738.893212] ? process_one_work+0x3c0/0x3c0 [ 1738.893217] kthread+0x12b/0x150 [ 1738.893224] ? set_kthread_struct+0x40/0x40 [ 1738.893231] ret_from_fork+0x1f/0x30 [ 1738.893242] Modules linked in: udf crc_itu_t pktcdvd usb_storage hid_generic hidp hid ccm vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm cmac algif_hash algif_skcipher af_alg vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep binfmt_misc snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_sof_intel_hda snd_hda_codec_realtek snd_sof_intel_byt snd_sof_intel_ipc snd_hda_codec_generic snd_sof snd_sof_xtensa_dsp snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec snd_hda_core snd_hwdep soundwire_bus snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_pcm snd_seq_midi snd_seq_midi_event intel_rapl_msr mei_hdcp snd_rawmidi nls_iso8859_1 intel_rapl_common x86_pkg_temp_thermal intel_powerclamp iwlmvm coretemp snd_seq snd_seq_device uvcvideo kvm_intel mac80211 videobuf2_vmalloc btusb videobuf2_memops kvm btrtl btbcm [ 1738.893354] videobuf2_v4l2 btintel libarc4 snd_timer videobuf2_common rapl intel_cstate bluetooth input_leds videodev snd joydev iwlwifi serio_raw mc efi_pstore cfg80211 intel_wmi_thunderbolt ecdh_generic ecc soundcore mei_me intel_pch_thermal mei intel_hid sparse_keymap acpi_pad mac_hid nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_comment xt_recent xt_multiport xt_limit xt_addrtype xt_tcpudp xt_conntrack sch_fq_codel nf_conntrack nf_defrag_ipv6
[Kernel-packages] [Bug 1889137] Re: HWE kernel is missing firmwares
>From the warnings, this seems to be happening again on 20.04 with the latest HWE kernel (5.11) and i915 related firmware files. -- 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/1889137 Title: HWE kernel is missing firmwares Status in linux-firmware package in Ubuntu: Confirmed Bug description: After install linux-generic-hwe-18.04: update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915 cd /lib/firmware/rtl_nicroot@h2:~# cd /lib/firmware/rtl_nic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-18.04 (not installed) ProcVersionSignature: Ubuntu 5.4.0-7634.38~1595345317~20.04~a8480ad-generic 5.4.41 Uname: Linux 5.4.0-7634-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Jul 28 10:43:18 2020 HibernationDevice: #RESUME=UUID=9926e754-5beb-4353-ab1b-8e22f798efc6 RESUME=UUID=aa434b5f-9af6-4b25-986e-216eb0e20a2e InstallationDate: Installed on 2018-06-28 (760 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N551JK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-7634-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-7634-generic N/A linux-backports-modules-5.4.0-7634-generic N/A linux-firmware 1.187.2 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-30 (58 days ago) dmi.bios.date: 10/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JK.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JK.203:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N551JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1889137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901505] Re: upgrade to 20.10 broke haswell laptop (no regular boot, no /dev/dri/card0)
Unable to provide the logs, because when the bug hits, I cannot get to a login prompt. If there is a way to get some logs, I'd like to try to help, but I need further instructions. ** 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/1901505 Title: upgrade to 20.10 broke haswell laptop (no regular boot, no /dev/dri/card0) Status in linux package in Ubuntu: Confirmed Bug description: Laptop installed with kubuntu focal is not booting after upgrade to 20.10 (that apparently went smooth without any error). - laptop hangs on boot - no splash screen is displayed - laptop can boot in recovery mode - in this case you do not get /dev/dri/card0 - if X is started it starts on llvmpipe - i915 driver is loaded, no error about it in journal or dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400]
The premise is that my ignorance on BT is complete. After some investigation, it is my understanding that RFCOMM channels are to RFCOMM communication a bit like ports in TCP and UDP, with the main difference that while there are really a lot of TCP/UDP ports and some of them are reserved as "well known ports", the number of channels in RFCOMM is extremely limited, so that there cannot be well known ports. Furthermore, I understand that no one should "hardwire" RFCOMM channels and that channels should be released whenever not strictly needed. If this understanding from myself is correct, there may be issues both in LibO and in PA. >From my understanding: - LibO and the Impress remote should not hardwire RFCOMM channel 3. I understand that they should dynamically allocate a channel and make it discoverable via SDP. - Impress should not keep binded to an RFCOMM channel all the time. There should be a visible option to switch on and off the binding (probably there should be a couple of impress remote related options in the "Slide Show -> Slide Show Settings" window, including one to fire up the BT rfcomm binding). - PA should probably similarly not hardwire channel 3 for its HSP role, but here the situation seems more complex, because it may be the case that PA needs to strive for compatibility with devices that do not play to the rules. - PA should probably have a DBUS interface to switch on and off the RFCOMM binding, so that to use an application needing RFCOMM channel 3, one does not need to take down the whole of PA. I have opened a bug on PA too. See it at https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/827. That report is bad, because when I made it my understanding of BT was even poorer than it is now. In any case, it seems to me that the current issue could be fixed completely on the LibO side, by dynamically allocating the channel and by letting the app running on the phone discover it via SDP. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable
[Kernel-packages] [Bug 1798400]
Thanks for the analysis! >From it, I still wonder whether this is a pulseaudio bug, though. Why is pulseaudio ever binding to RFCOMM channel 3 *before* there is any need to do so? That is, until I am not connected to any device using channel 3, why is pulseaudio already using it up? In other words, it seems reasonable to me to have the laptop connected to the phone as a headset and in this case not to have the impress remote working. But in case I start impress before setting up a bluetooth connection to the phone, why should be the pulseaudio binding already there? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400]
Andrzej, I am CC-ing you on this, because I believe that you were one of the original corder of the BT code for the impress remote on linux. I hope that you may able to provide some advice on this. If I'm wrong, please take my apology for the noise. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400]
The bug is also confirmed in the ubuntu launchpad at https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400. Users there are reporting that they are experiencing the issue in ubuntu (from bionic, I think) and gentoo. This adds to the reports in fedora and to the confirmation here on arch linux. I think that this is enough to mark as "NEW" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400]
Issue still present in LibO 6.4.3.1. I see the bug as still unconfirmed after more than one year. I wonder if it could be confirmed, given that the same issue has also been reported for redhat (https://bugzilla.redhat.com/show_bug.cgi?id=1581879) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
@John Poole Can you please indicate that you are also experiencing the issue in the issue tracker at the document foundation at https://bugs.documentfoundation.org/show_bug.cgi?id=120663 ? The issue is still "unconfirmed" there, and until it is "confirmed" by multiple reporters, there is little chance that it can be dealt with. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400]
Issue persists with current LibO 6.3.1.2 and most likely due to the fact that the bluetooth stack on linux (bluez) has changed in the past years and impress has not cought up. Problem is now more visible due to the startup tooltips in Impress 6.3.x which explicitly introduce the impress remote functionality inviting the users to test it. Goes like: start Impress -> see tooltip -> get interested -> download and install phone app -> try -> fail -> get disappointed and remove phone app. Because the phone based remote is one of those little things with a great wow factor that makes LibO really shine out and amaze people when used in front of an audience, it would really be great if the functionality could be restored. It is literally a little big thing helping getting a foot in the door. In fact, I suppose that if one could also add a "spotlight" and "zoom" functionality in it (in addition to the pointer) and the ability to use the phone accelerometers for moving the pointer (in place of the finger on the screen) it would make LibO a serious contender for all those coveting the "Logitech spotlight" that is currently the hot thing in presentations selling for over $100. See also https://github.com/jahnf/Projecteur . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1798400]
Wonder if it could be useful to kindly ask Andrzej Hunt if he can look into the issue. If I am not wrong he is the author of the current bluez 5 code in Impress. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837440] Re: linux firmware 1.178.3 seems to break WPA enterprise
I have investigated a bit further. - Using a USB wifi adapter (took me some time to force one to use only the 2.4 GHz band as my laptop wifi adapter) I can always connect properly, so the issue is restricted to the intel card I have in my laptop. This should exclude wpasupplicant and network-manager. - The card in the laptop occasionally works correctly. This is why I originally got the impression that downgrading the linux-firmware package was restoring correct behavior (in fact, it was just by chance that I probably got the correct behavior). - When the card misfunctions, I get wild oscillations in the reported signal quality. Specifically, while the card is just scanning the nearby APs, I see a good quality for the WPA enterprise AP. During the connection attempt, the quality starts to fluctuate close to 0. My guess is that most likely something is starting to fail in the wifi module or that there is an issue with its power saving control. The latter could be kernel dependent, but given the update history, it seems unlikely to me. I'll check better. In the meantime, thanks for the help and advice. -- 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/1837440 Title: linux firmware 1.178.3 seems to break WPA enterprise Status in linux package in Ubuntu: Incomplete Bug description: Seen on intel Wireless-N 2230 BGN (rev c4). After the update to said linux firmware version I had issues in connecting to the WPA enterprise wifi networks EDUROAM and ALMAWIFI. EDUROAM is the European universities Wi-Fi network. Ability to connect to non enterprise network is unaffected. Downgrading to 1.178 seems to restore proper functionality. In the next days I'll try further checks to see if the firmware is really the sole trigger for the issue. In the meantime, I am tentatively opening the bug in case others have my same issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-firmware 1.178 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 22 19:27:16 2019 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (2047 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to disco on 2019-06-12 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837440] Re: linux firmware 1.178.3 seems to break WPA enterprise
Yes, that is probably the case and it was probably just by chance that after downgrading the firmware I managed connecting for a couple of times consecutively. Now, I cannot connect again and the only reliable way of connecting seems to be by letting the mobile phone connect and using cable or bluetooth tethering from android :-< The problem is that the messages from Network manager are pure nonsense: The applet hangs on "configuring the interface" for some time (which I believe means it cannot complete the association and then it errors out with "The interface cannot be found" or "No secrets were provided". Also the systems log do not seem to provide any information on what part of the negotiation is going wrong. All this has started in the week beginning with Jul 15th and the local network administrators here say that nothing has changed on their side (also phones, window and apple computers can connect properly), so the issue must be on my side and must follow some package update on my system or some fault in my wifi card (but this seems strange because I can connect to regular/non enterprise networks). Any hint at trying to debug? -- 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/1837440 Title: linux firmware 1.178.3 seems to break WPA enterprise Status in linux-firmware package in Ubuntu: New Bug description: Seen on intel Wireless-N 2230 BGN (rev c4). After the update to said linux firmware version I had issues in connecting to the WPA enterprise wifi networks EDUROAM and ALMAWIFI. EDUROAM is the European universities Wi-Fi network. Ability to connect to non enterprise network is unaffected. Downgrading to 1.178 seems to restore proper functionality. In the next days I'll try further checks to see if the firmware is really the sole trigger for the issue. In the meantime, I am tentatively opening the bug in case others have my same issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-firmware 1.178 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 22 19:27:16 2019 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (2047 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to disco on 2019-06-12 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1837440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837440] [NEW] linux firmware 1.178.3 seems to break WPA enterprise
Public bug reported: Seen on intel Wireless-N 2230 BGN (rev c4). After the update to said linux firmware version I had issues in connecting to the WPA enterprise wifi networks EDUROAM and ALMAWIFI. EDUROAM is the European universities Wi-Fi network. Ability to connect to non enterprise network is unaffected. Downgrading to 1.178 seems to restore proper functionality. In the next days I'll try further checks to see if the firmware is really the sole trigger for the issue. In the meantime, I am tentatively opening the bug in case others have my same issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-firmware 1.178 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 22 19:27:16 2019 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (2047 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to disco on 2019-06-12 (40 days ago) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1837440 Title: linux firmware 1.178.3 seems to break WPA enterprise Status in linux-firmware package in Ubuntu: New Bug description: Seen on intel Wireless-N 2230 BGN (rev c4). After the update to said linux firmware version I had issues in connecting to the WPA enterprise wifi networks EDUROAM and ALMAWIFI. EDUROAM is the European universities Wi-Fi network. Ability to connect to non enterprise network is unaffected. Downgrading to 1.178 seems to restore proper functionality. In the next days I'll try further checks to see if the firmware is really the sole trigger for the issue. In the meantime, I am tentatively opening the bug in case others have my same issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-firmware 1.178 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 22 19:27:16 2019 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (2047 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to disco on 2019-06-12 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1837440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400]
Cannot test daily builds right now, but 6.3.0 beta 1 still has the issue. Launching impress reports: bluetoothd[1386]: RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) in the system logs and then the remote app cannot contact the host. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400]
Still present in 6.2.0 RC 1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
I think that the issue can be either a bug in the bluetooth stack or merely something that has /changed/ in the bluetooth stack, that libreoffice has not tracked properly. Hence, I have also opened a bug upstream for LibO, mentioning this one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
I have stayed a long time without trying impress remote, so I do not know exactly when the issue started. However, I am sure that last year at this time (aka on 16.04) the issue did not exist. Just tried latest non-RC kernel from mainline 4.18.x and the issue is still there. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
See https://bugzilla.redhat.com/show_bug.cgi?id=1581879 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in bluez package in Ubuntu: New Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400] [NEW] Regression: cannot use impress remote over bluetooth with ubuntu bionic
Public bug reported: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Bug watch added: Red Hat Bugzilla #1581879 https://bugzilla.redhat.com/show_bug.cgi?id=1581879 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in bluez package in Ubuntu: New Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM
[Kernel-packages] [Bug 1773906] Re: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick
In general, it is hard to test modern kernels on artful because of the header dependence on libssl1.1 (is it really a hard requirement?) In any case, the fact that 2.16 is OK makes me hope that on the upgrade to bionic, the issue will automatically be over. -- 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/1773906 Title: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick Status in linux package in Ubuntu: Incomplete Bug description: On insertion of a Huawei E173 mobile internet USB stick the artful kernel now oopses: BUG: unable to handle kernel NULL pointer dereference at 03d0 [ 633.710837] IP: pkt_setup_dev+0x2af/0x650 [pktcdvd] Issue seems to be related to the setup of the cdrom-like device hosted on the stick together with the UMTS modem. May possibly be due to some race as the usb stick configuration keeps changing until the device is properly switched to operate as a modem. Some of the times, UMTS modem remains detected notwithstanding the issue. After the issue, the system has problems in shutting down, though. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.13.0.43.46 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2654 F pulseaudio /dev/snd/controlC1: callegar 2654 F pulseaudio CurrentDesktop: KDE Date: Tue May 29 08:27:52 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c7dd5aac-abad-4cd0-9cac-552d49960853 InstallationDate: Installed on 2013-12-12 (1628 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-26 (214 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773906] Re: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick
I only use the internet key rarely, so it is hard for me to give any precise indication about when the issue was introduced. I would say that at the release of artful the issue was not there. Tested mainline 2.16 and it is OK. Correctly reports "setup of pktcdvd device failed" rather than oopsing. -- 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/1773906 Title: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick Status in linux package in Ubuntu: Incomplete Bug description: On insertion of a Huawei E173 mobile internet USB stick the artful kernel now oopses: BUG: unable to handle kernel NULL pointer dereference at 03d0 [ 633.710837] IP: pkt_setup_dev+0x2af/0x650 [pktcdvd] Issue seems to be related to the setup of the cdrom-like device hosted on the stick together with the UMTS modem. May possibly be due to some race as the usb stick configuration keeps changing until the device is properly switched to operate as a modem. Some of the times, UMTS modem remains detected notwithstanding the issue. After the issue, the system has problems in shutting down, though. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.13.0.43.46 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2654 F pulseaudio /dev/snd/controlC1: callegar 2654 F pulseaudio CurrentDesktop: KDE Date: Tue May 29 08:27:52 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c7dd5aac-abad-4cd0-9cac-552d49960853 InstallationDate: Installed on 2013-12-12 (1628 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-26 (214 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773906] [NEW] Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick
Public bug reported: On insertion of a Huawei E173 mobile internet USB stick the artful kernel now oopses: BUG: unable to handle kernel NULL pointer dereference at 03d0 [ 633.710837] IP: pkt_setup_dev+0x2af/0x650 [pktcdvd] Issue seems to be related to the setup of the cdrom-like device hosted on the stick together with the UMTS modem. May possibly be due to some race as the usb stick configuration keeps changing until the device is properly switched to operate as a modem. Some of the times, UMTS modem remains detected notwithstanding the issue. After the issue, the system has problems in shutting down, though. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.13.0.43.46 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2654 F pulseaudio /dev/snd/controlC1: callegar 2654 F pulseaudio CurrentDesktop: KDE Date: Tue May 29 08:27:52 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c7dd5aac-abad-4cd0-9cac-552d49960853 InstallationDate: Installed on 2013-12-12 (1628 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-26 (214 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1773906 Title: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick Status in linux package in Ubuntu: New Bug description: On insertion of a Huawei E173 mobile internet USB stick the artful kernel now oopses: BUG: unable to handle kernel NULL pointer dereference at 03d0 [ 633.710837] IP: pkt_setup_dev+0x2af/0x650 [pktcdvd] Issue seems to be related to the setup of the cdrom-like device hosted on the stick together with the UMTS modem. May possibly be due to some race as the usb stick configuration keeps changing until the device is properly switched to operate as a modem. Some of the times, UMTS modem remains detected notwithstanding the issue. After the issue, the system has problems in shutting down, though. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.13.0.43.46 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2654 F pulseaudio /dev/snd/controlC1: callegar 2654 F pulseaudio CurrentDesktop: KDE Date: Tue May 29 08:27:52 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c7dd5aac-abad-4cd0-9cac-552d49960853 InstallationDate: Installed on 2013-12-12 (1628 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-26 (214 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9
[Kernel-packages] [Bug 1738761] Re: Please document how to build a patched version of the current (non mainline) ubuntu kernel in a PPA
Question expired. Can we reopen the bug as an enhancement request? -- 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/1738761 Title: Please document how to build a patched version of the current (non mainline) ubuntu kernel in a PPA Status in linux package in Ubuntu: Invalid Bug description: In order to resolve some bugs, to workaround some hardware quirk, or to help developers test some bug-fixing patch it would be able to: - Get the sources of the *current* (non mainline) ubuntu kernel - Apply some patch - Rebuild the kernel in a PPA (so that it can be made available to multiple people for testing). Unfortunately, there is no documentation on how to do this. In fact, to the best of my understanding there is no documentation on how to build patched kernels in PPAs at all. This seems to be both possible and involving some special recipes, because in some occasions I've been pointed by ubuntu developers to try some specially patched version of the current kernel made available via a PPA. Specifically, at the present time, I would like to try and help trying the patch in git://github.com/vsyrjala/linux.git plane_assert_v4.13 which is not yet available in mainline. In other occasions I had similar situations with other patches. Please let me remark again that I am not looking for ways of building patched versions of the mainline kernel in a PPA (for this I have found some informal instructions in https://askubuntu.com/questions/784796/ppa-upload-of-custom-kernel- package/841981#841981 (incidentally, this too should in my opinion be officially documented). I am looking for ways to build a patched current kernel, so that: - systems needing proprietary drivers can be supported - patches can be tested with the current ubuntu kernel - as new versions of the ubuntu kernel for some distro come out, it is easy to bring forward the patch if needed. Thanks! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-source (not installed) ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 20848 F pulseaudio CurrentDesktop: KDE Date: Mon Dec 18 11:42:45 2017 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Precision WorkStation T5400 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g mtrr_chunk_size=2g resume=/dev/sdc3 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-25 (53 days ago) WpaSupplicantLog: dmi.bios.date: 04/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T5400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738761] [NEW] Please document how to build a patched version of the current (non mainline) ubuntu kernel in a PPA
Public bug reported: In order to resolve some bugs, to workaround some hardware quirk, or to help developers test some bug-fixing patch it would be able to: - Get the sources of the *current* (non mainline) ubuntu kernel - Apply some patch - Rebuild the kernel in a PPA (so that it can be made available to multiple people for testing). Unfortunately, there is no documentation on how to do this. In fact, to the best of my understanding there is no documentation on how to build patched kernels in PPAs at all. This seems to be both possible and involving some special recipes, because in some occasions I've been pointed by ubuntu developers to try some specially patched version of the current kernel made available via a PPA. Specifically, at the present time, I would like to try and help trying the patch in git://github.com/vsyrjala/linux.git plane_assert_v4.13 which is not yet available in mainline. In other occasions I had similar situations with other patches. Please let me remark again that I am not looking for ways of building patched versions of the mainline kernel in a PPA (for this I have found some informal instructions in https://askubuntu.com/questions/784796 /ppa-upload-of-custom-kernel-package/841981#841981 (incidentally, this too should in my opinion be officially documented). I am looking for ways to build a patched current kernel, so that: - systems needing proprietary drivers can be supported - patches can be tested with the current ubuntu kernel - as new versions of the ubuntu kernel for some distro come out, it is easy to bring forward the patch if needed. Thanks! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-source (not installed) ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 20848 F pulseaudio CurrentDesktop: KDE Date: Mon Dec 18 11:42:45 2017 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Precision WorkStation T5400 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g mtrr_chunk_size=2g resume=/dev/sdc3 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-25 (53 days ago) WpaSupplicantLog: dmi.bios.date: 04/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T5400 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug artful -- 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/1738761 Title: Please document how to build a patched version of the current (non mainline) ubuntu kernel in a PPA Status in linux package in Ubuntu: Confirmed Bug description: In order to resolve some bugs, to workaround some hardware quirk, or to help developers test some bug-fixing patch it would be able to: - Get the sources of the *current* (non mainline) ubuntu kernel - Apply some patch - Rebuild the kernel in a PPA (so that it can be made available to multiple people for testing). Unfortunately, there is no documentation on how to do this. In fact, to the best of my understanding there is no documentation on how to build patched kernels in PPAs at all. This seems to be both possible and involving some special recipes, because in some occasions I've been pointed by ubuntu developers to try some specially patched version of the current kernel made available via a PPA. Specifically, at the present time, I would like to try and help trying the patch in git://github.com/vsyrjala/linux.git plane_assert_v4.13 which is not yet available in mainline. In other occasions I had similar situations with other patches. Please let me remark again that I am not looking for ways of building patched versions of the mainline kernel in a PPA (for this I have found some informal instructions in https://askubuntu.com/questions/784796/ppa-upload-of-custom-kernel- package/841981#841981 (incidentally, this too should in my opinion be officially documented). I am looking for ways to build a patched current kernel, so that: - systems needing proprietary drivers can be supported - patches can be tested with the current ubuntu
[Kernel-packages] [Bug 405294] Re: a2dp skips terribly
I have occasionally seen this too, in kubuntu 17.04. What is weird is that it happens only sometimes, and I cannot recognize what triggers the issue. Last time it went away with a reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: a2dp skips terribly Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574125] Re: suspend not working after upgrade
*** This bug is a duplicate of bug 1566302 *** https://bugs.launchpad.net/bugs/1566302 Same issue here: DELL Precision T5400 with nvidia graphics cannot suspend anymore after upgrade to xenial. -- 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/1574125 Title: suspend not working after upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After upgrade, putting machine in suspend turns the monitor black and everything seem to be off, though the fan still spins, the power light is on and the battery is trained. Nothing seem to wake it up (Meaning different key combinations - trying to get a shell by Ctrl+Alt+F1, for example; pressing power, any other key). Unsure how to try to get it working since I have to kill the power by pressing down the power button, then restarting it (it then does a drive scan for errors). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maria 2076 F pulseaudio /dev/snd/controlC1: maria 2076 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 24 00:07:49 2016 HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa InstallationDate: Installed on 2016-01-31 (83 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20351 ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.name: 20351 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16
Same issue here: DELL Precision T5400 with nvidia graphics cannot suspend anymore after upgrade to xenial. -- 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/1566302 Title: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16 Status in linux package in Ubuntu: Confirmed Bug description: I'm using ubuntu 16.04 on a XPS 15 9550. Suspend/resume worked flawlessly with linux image 4.4.0-15, and after standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16, the system freezes when attempting a suspend. I get no response from the system (nor keyboard, nor screen, nor touchpad), but it gets very hot, so that it must be running something. Booting with 4.4.0-15 makes the suspend to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: macias 1770 F pulseaudio CurrentDesktop: X-Cinnamon Date: Tue Apr 5 14:56:17 2016 HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743 InstallationDate: Installed on 2016-03-07 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic->vivid upgrade with Iomega Zip drive (IDE)
Hi, I forgot to report: the Wily kernel does not have the issue. Only the Vivid kernel has it. As a matter of fact, according to conversation I had with one of the kernel developers, the issue may be due to a race. The more modern kernels do not seem to trigger the problem. I cannot test the most recent ubuntu kernel in the live image right now because the machine where I have the issue is currently packed in a box in view of a relocation. But I'll test as soon as it is up again. -- 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/1451277 Title: Extremely high IOWait and processes hungs after utopic->vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525254] Re: The r8188eu driver shipped with wily is broken, new working driver exists
** Description changed: After update to wily, I have continuous disconnections with a tplink 725N wifi usb dongle that uses the r8188eu driver to the point that the dongle is completely useless. In vivid, the driver driver shipped with the kernel was problematic but working a bit better (some disconnections, and incorrect link quality reporting, but OK for the rest) so we definitely have a REGRESSION. - Furthermore, on the tplink driver the *source* or a driver that works + Furthermore, on the tplink website the *source* or a driver that works fine is available: http://www.tp-link.us/res/down/soft/TL-WN725N_V2_150911.zip Porting to a format consistent with the pristine kernel has been done, see https://github.com/lwfinger/rtl8188eu/issues/152 and https://www.dropbox.com/s/znp5munr03oow0b/rtl8188eu-linux- driver.zip?dl=0 The thing still does not compile cleanly against the 4.2 kernel shipped in wily, because the interface of cfg80211_disconnected has changed, but the fix is trivial diff -r rtl8188eu-linux-driver/os_dep/linux/ioctl_cfg80211.c rtl8188eu-linux-driver2/os_dep/linux/ioctl_cfg80211.c 907c907 < cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, GFP_ATOMIC); --- > cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, false, GFP_ATOMIC); Furthermore there is a re-definition that needs removing diff -r rtl8188eu-linux-driver/hal/hal_com_phycfg.c rtl8188eu-linux-driver2/hal/hal_com_phycfg.c 2578c2578 < char file_path[PATH_LENGTH_MAX]; --- > //charfile_path[PATH_LENGTH_MAX]; Once that is done, the tplink driver works perfectly. Please update wily to use the new driver. It may be worth informing the upstream kernel maintainer and Greg K.H. about the new opensource driver for possible inclusion in the upstream kernel staging tree in place of the troublesome driver that is currently there. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-generic 4.2.0.19.21 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: callegar 2596 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: callegar 2596 F pulseaudio CurrentDesktop: KDE Date: Fri Dec 11 14:50:16 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c50b4249-43ed-49ef-a3d8-ec7aa9718265 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic root=/dev/mapper/DISK00-root ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: - linux-restricted-modules-4.2.0-19-generic N/A - linux-backports-modules-4.2.0-19-generic N/A - linux-firmware1.149.3 + linux-restricted-modules-4.2.0-19-generic N/A + linux-backports-modules-4.2.0-19-generic N/A + linux-firmware1.149.3 SourcePackage: linux StagingDrivers: r8188eu UpgradeStatus: Upgraded to wily on 2015-11-28 (12 days ago) WpaSupplicantLog: - + dmi.bios.date: 04/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: N68-S dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- 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/1525254 Title: The r8188eu driver shipped with wily is broken, new working driver exists Status in linux package in Ubuntu: Invalid Bug description: After update to wily, I have continuous disconnections with a tplink 725N wifi usb dongle that uses the r8188eu driver to the point that the dongle is completely useless. In vivid, the driver driver shipped with the kernel was problematic but working a bit better (some disconnections, and incorrect link quality reporting, but OK for the rest) so we definitely have a REGRESSION. Furthermore, on the tplink website the *source* or a driver that works fine is available: http://www.tp-link.us/res/down/soft/TL-WN725N_V2_150911.zip Porting to a format consistent with the pristine kernel has been done, see https://github.com/lwfinger/rtl8188eu/issues/152 and https://www.dropbox.com/s/znp5munr03oow0b/rtl8188eu-linux- driver.zip?dl=0 The
[Kernel-packages] [Bug 1525254] Re: The r8188eu driver shipped with wily is broken, new working driver exists
Since it is anyway easy to install the driver in http://www.tp- link.us/res/down/soft/TL-WN725N_V2_150911.zip, please ignore ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1525254 Title: The r8188eu driver shipped with wily is broken, new working driver exists Status in linux package in Ubuntu: Invalid Bug description: After update to wily, I have continuous disconnections with a tplink 725N wifi usb dongle that uses the r8188eu driver to the point that the dongle is completely useless. In vivid, the driver driver shipped with the kernel was problematic but working a bit better (some disconnections, and incorrect link quality reporting, but OK for the rest) so we definitely have a REGRESSION. Furthermore, on the tplink driver the *source* or a driver that works fine is available: http://www.tp-link.us/res/down/soft/TL-WN725N_V2_150911.zip Porting to a format consistent with the pristine kernel has been done, see https://github.com/lwfinger/rtl8188eu/issues/152 and https://www.dropbox.com/s/znp5munr03oow0b/rtl8188eu-linux- driver.zip?dl=0 The thing still does not compile cleanly against the 4.2 kernel shipped in wily, because the interface of cfg80211_disconnected has changed, but the fix is trivial diff -r rtl8188eu-linux-driver/os_dep/linux/ioctl_cfg80211.c rtl8188eu-linux-driver2/os_dep/linux/ioctl_cfg80211.c 907c907 < cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, GFP_ATOMIC); --- > cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, false, GFP_ATOMIC); Furthermore there is a re-definition that needs removing diff -r rtl8188eu-linux-driver/hal/hal_com_phycfg.c rtl8188eu-linux-driver2/hal/hal_com_phycfg.c 2578c2578 < char file_path[PATH_LENGTH_MAX]; --- > //charfile_path[PATH_LENGTH_MAX]; Once that is done, the tplink driver works perfectly. Please update wily to use the new driver. It may be worth informing the upstream kernel maintainer and Greg K.H. about the new opensource driver for possible inclusion in the upstream kernel staging tree in place of the troublesome driver that is currently there. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-generic 4.2.0.19.21 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2596 F pulseaudio CurrentDesktop: KDE Date: Fri Dec 11 14:50:16 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c50b4249-43ed-49ef-a3d8-ec7aa9718265 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic root=/dev/mapper/DISK00-root ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 SourcePackage: linux StagingDrivers: r8188eu UpgradeStatus: Upgraded to wily on 2015-11-28 (12 days ago) WpaSupplicantLog: dmi.bios.date: 04/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: N68-S dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492939] Re: Enhancement request: please document how to build kernel in PPA
I see the bug marked as invalid. How does one report a problem with the launchpad infrastructure? ** Description changed: Hi, - In the process of working around an issue that has appeared in the linux - kernel after the patch series "convert host_busy to atomic_t" (see bug - 1451277), I would like to compile kernel deb packages that work around - the issue in a PPA, using patches that appeared on the LKML. + It is unclear to me how to build an ubuntu kernel kernel in a PPA and + instructions are missing both in the kernel package and in launchpad. - Unfortunately, it is unclear to me how to build a kernel in a PPA. + Particularly, I have not been able to find any up to date instruction on + how to create a kernel source package with just a trivial patch on top + of the current ubuntu kernel and build it in a PPA. Simply taking the kernel source package, applying the patch, rebuilding - the source package and uploading to the PPA fails to build in the PPA + the source package and uploading it to the PPA fails to build in the PPA (due to ABI checks, I believe). - - I have not been able to find any up to date instruction on how to create - a kernel source package with just a trivial patch on top of the current - ubuntu kernel and build it in a PPA. - Instructions in https://wiki.ubuntu.com/Kernel/Dev/KernelBuildScripts do not seem recent and appear to involve much more than what is needed for my case. Most important, they fail at the invocation of the build- mkppa command. - Instructions in http://ubuntuforums.org/showthread.php?t=1682345 seem to work, but they are very unofficial and look like black magic. Specifically, what are those parameters supposed to do and why are they needed? Why do these parameter make the built kernel a very different size than the original one? A minor patch should not make this difference. Altogether, can up to date, official instructions for building the Ubuntu kernel + a patch in a PPA be added somewhere? 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/1492939 Title: Enhancement request: please document how to build kernel in PPA Status in linux package in Ubuntu: Invalid Bug description: Hi, It is unclear to me how to build an ubuntu kernel kernel in a PPA and instructions are missing both in the kernel package and in launchpad. Particularly, I have not been able to find any up to date instruction on how to create a kernel source package with just a trivial patch on top of the current ubuntu kernel and build it in a PPA. Simply taking the kernel source package, applying the patch, rebuilding the source package and uploading it to the PPA fails to build in the PPA (due to ABI checks, I believe). - Instructions in https://wiki.ubuntu.com/Kernel/Dev/KernelBuildScripts do not seem recent and appear to involve much more than what is needed for my case. Most important, they fail at the invocation of the build-mkppa command. - Instructions in http://ubuntuforums.org/showthread.php?t=1682345 seem to work, but they are very unofficial and look like black magic. Specifically, what are those parameters supposed to do and why are they needed? Why do these parameter make the built kernel a very different size than the original one? A minor patch should not make this difference. Altogether, can up to date, official instructions for building the Ubuntu kernel + a patch in a PPA be added somewhere? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525254] [NEW] The r8188eu driver shipped with wily is broken, new working driver exists
Public bug reported: After update to wily, I have continuous disconnections with a tplink 725N wifi usb dongle that uses the r8188eu driver to the point that the dongle is completely useless. In vivid, the driver driver shipped with the kernel was problematic but working a bit better (some disconnections, and incorrect link quality reporting, but OK for the rest) so we definitely have a REGRESSION. Furthermore, on the tplink driver the *source* or a driver that works fine is available: http://www.tp-link.us/res/down/soft/TL-WN725N_V2_150911.zip Porting to a format consistent with the pristine kernel has been done, see https://github.com/lwfinger/rtl8188eu/issues/152 and https://www.dropbox.com/s/znp5munr03oow0b/rtl8188eu-linux- driver.zip?dl=0 The thing still does not compile cleanly against the 4.2 kernel shipped in wily, because the interface of cfg80211_disconnected has changed, but the fix is trivial diff -r rtl8188eu-linux-driver/os_dep/linux/ioctl_cfg80211.c rtl8188eu-linux-driver2/os_dep/linux/ioctl_cfg80211.c 907c907 < cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, GFP_ATOMIC); --- > cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, > false, GFP_ATOMIC); Furthermore there is a re-definition that needs removing diff -r rtl8188eu-linux-driver/hal/hal_com_phycfg.c rtl8188eu-linux-driver2/hal/hal_com_phycfg.c 2578c2578 < char file_path[PATH_LENGTH_MAX]; --- > //charfile_path[PATH_LENGTH_MAX]; Once that is done, the tplink driver works perfectly. Please update wily to use the new driver. It may be worth informing the upstream kernel maintainer and Greg K.H. about the new opensource driver for possible inclusion in the upstream kernel staging tree in place of the troublesome driver that is currently there. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-generic 4.2.0.19.21 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2596 F pulseaudio CurrentDesktop: KDE Date: Fri Dec 11 14:50:16 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c50b4249-43ed-49ef-a3d8-ec7aa9718265 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic root=/dev/mapper/DISK00-root ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 SourcePackage: linux StagingDrivers: r8188eu UpgradeStatus: Upgraded to wily on 2015-11-28 (12 days ago) WpaSupplicantLog: dmi.bios.date: 04/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: N68-S dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug staging wily -- 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/1525254 Title: The r8188eu driver shipped with wily is broken, new working driver exists Status in linux package in Ubuntu: New Bug description: After update to wily, I have continuous disconnections with a tplink 725N wifi usb dongle that uses the r8188eu driver to the point that the dongle is completely useless. In vivid, the driver driver shipped with the kernel was problematic but working a bit better (some disconnections, and incorrect link quality reporting, but OK for the rest) so we definitely have a REGRESSION. Furthermore, on the tplink driver the *source* or a driver that works fine is available: http://www.tp-link.us/res/down/soft/TL-WN725N_V2_150911.zip Porting to a format consistent with the pristine kernel has been done, see https://github.com/lwfinger/rtl8188eu/issues/152 and https://www.dropbox.com/s/znp5munr03oow0b/rtl8188eu-linux- driver.zip?dl=0 The thing still does not compile cleanly against the 4.2 kernel shipped in wily, because the interface of cfg80211_disconnected has changed, but the fix is trivial diff -r rtl8188eu-linux-driver/os_dep/linux/ioctl_cfg80211.c rtl8188eu-linux-driver2/os_dep/linux/ioctl_cfg80211.c 907c907 < cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, GFP_ATOMIC);
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic->vivid upgrade with Iomega Zip drive (IDE)
>From LKML conversation, fix https://lkml.org/lkml/2014/11/20/581 is not likely to be applied upstream, because it probably just papers over the real bug. The real issue appears with the patch series "scsi: convert host_busy to atomic_t" that causes regressions on some hardware configurations. Might not be due to this series either, but to some other race that this change helps triggering. I wonder if papering over can be acceptable downstream. -- 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/1451277 Title: Extremely high IOWait and processes hungs after utopic->vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Confirmed Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492939] [NEW] Enhancement request: please document how to build kernel in PPA
Public bug reported: Hi, In the process of working around an issue that has appeared in the linux kernel after the patch series "convert host_busy to atomic_t" (see bug 1451277), I would like to compile kernel deb packages that work around the issue in a PPA, using patches that appeared on the LKML. Unfortunately, it is unclear to me how to build a kernel in a PPA. Simply taking the kernel source package, applying the patch, rebuilding the source package and uploading to the PPA fails to build in the PPA (due to ABI checks, I believe). I have not been able to find any up to date instruction on how to create a kernel source package with just a trivial patch on top of the current ubuntu kernel and build it in a PPA. - Instructions in https://wiki.ubuntu.com/Kernel/Dev/KernelBuildScripts do not seem recent and appear to involve much more than what is needed for my case. Most important, they fail at the invocation of the build- mkppa command. - Instructions in http://ubuntuforums.org/showthread.php?t=1682345 seem to work, but they are very unofficial and look like black magic. Specifically, what are those parameters supposed to do and why are they needed? Why do these parameter make the built kernel a very different size than the original one? A minor patch should not make this difference. Altogether, can up to date, official instructions for building the Ubuntu kernel + a patch in a PPA be added somewhere? Thanks! ** 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/1492939 Title: Enhancement request: please document how to build kernel in PPA Status in linux package in Ubuntu: New Bug description: Hi, In the process of working around an issue that has appeared in the linux kernel after the patch series "convert host_busy to atomic_t" (see bug 1451277), I would like to compile kernel deb packages that work around the issue in a PPA, using patches that appeared on the LKML. Unfortunately, it is unclear to me how to build a kernel in a PPA. Simply taking the kernel source package, applying the patch, rebuilding the source package and uploading to the PPA fails to build in the PPA (due to ABI checks, I believe). I have not been able to find any up to date instruction on how to create a kernel source package with just a trivial patch on top of the current ubuntu kernel and build it in a PPA. - Instructions in https://wiki.ubuntu.com/Kernel/Dev/KernelBuildScripts do not seem recent and appear to involve much more than what is needed for my case. Most important, they fail at the invocation of the build-mkppa command. - Instructions in http://ubuntuforums.org/showthread.php?t=1682345 seem to work, but they are very unofficial and look like black magic. Specifically, what are those parameters supposed to do and why are they needed? Why do these parameter make the built kernel a very different size than the original one? A minor patch should not make this difference. Altogether, can up to date, official instructions for building the Ubuntu kernel + a patch in a PPA be added somewhere? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492939] Re: Enhancement request: please document how to build kernel in PPA
No logs should be required as this is a wishlist regarding kernel/launchpad documentation. ** 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/1492939 Title: Enhancement request: please document how to build kernel in PPA Status in linux package in Ubuntu: Confirmed Bug description: Hi, In the process of working around an issue that has appeared in the linux kernel after the patch series "convert host_busy to atomic_t" (see bug 1451277), I would like to compile kernel deb packages that work around the issue in a PPA, using patches that appeared on the LKML. Unfortunately, it is unclear to me how to build a kernel in a PPA. Simply taking the kernel source package, applying the patch, rebuilding the source package and uploading to the PPA fails to build in the PPA (due to ABI checks, I believe). I have not been able to find any up to date instruction on how to create a kernel source package with just a trivial patch on top of the current ubuntu kernel and build it in a PPA. - Instructions in https://wiki.ubuntu.com/Kernel/Dev/KernelBuildScripts do not seem recent and appear to involve much more than what is needed for my case. Most important, they fail at the invocation of the build-mkppa command. - Instructions in http://ubuntuforums.org/showthread.php?t=1682345 seem to work, but they are very unofficial and look like black magic. Specifically, what are those parameters supposed to do and why are they needed? Why do these parameter make the built kernel a very different size than the original one? A minor patch should not make this difference. Altogether, can up to date, official instructions for building the Ubuntu kernel + a patch in a PPA be added somewhere? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE)
Bisected. Bug seen after commit 045065d8a300a37218c548e9aa7becd581c6a0e8 [SCSI] fix qemu boot hang problem. Actually, the problem is not with that commit that is perfectly fine. That commit merely lets the real bug be triggered. Real bug is with scsi host lock and likely to be triggered by mixing a slow and a fast device on the same IDE/SATA channel. Bug is also biting other distros. See https://bbs.archlinux.org/viewtopic.php?id=189324 Bug is known to kernel developers. https://lkml.org/lkml/2015/8/16/44 https://bugzilla.kernel.org/show_bug.cgi?id=87581 Bug is fixed by following patch by Christoph Hellwig, that unfortunately is not yet applied upstream https://lkml.org/lkml/2014/11/20/581 ** Bug watch added: Linux Kernel Bug Tracker #87581 http://bugzilla.kernel.org/show_bug.cgi?id=87581 ** 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Confirmed Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE)
Please ignore my previous message. Did not wait enough. Bug is present in 3.17 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE)
I have tried to look into the issue, but I am encountering a situation that is extremely weird. Hence I hope that someone might be able to help. The latest kernel that works from the ubuntu mainline ppa repo is 3.16.7-031607_3.16.7-031607.201410301735 Kernel 3.17.0-031700_3.17.0-031700.201410060605 already shows the issue. However, if I try to compile myself 3.17 from Linus following the instructions in https://wiki.ubuntu.com/KernelTeam/GitKernelBuild I get: - a kernel that is clearly completely different in configuration from that in the ubuntu ppa mainline (different package names, much much larger kernel image package) and, most important, - a kernel that apparently does not show the IOWAIT issue. At the same time, I am recently experiencing all sort of issues with nvidia 304 and kde plasma 5 causing continuous hangs in plasmashell even if compositing is off, so it is quite difficult to properly test for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE)
Also hdparm -i /dev/sda hangs when the iowait goes high. Note that the issue happens with the drive unmounted. -- 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE)
Bug present with 3.17.8 mainline -- 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE)
** Summary changed: - Extremely high IOWait and processes hungs after utopic-vivid upgrade + Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE) -- 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE)
I would also rise priority, since the issue - makes it often impossible to shut down the machine cleanly, requiring a hard reset which may result in data loss; - I imagine that it can make it quite hard to install security updates from ubuntu as any update of the kernel package tends to result in the system hanging at the make initramfs phase, that probably queries all system drives. -- 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE)
Installed python-pyqt5 as reported in bug 1439784 to make apport-collect work. Still getting error apport-collect crashing though. dpkg-query: no packages found matching linux Traceback (most recent call last): File /usr/share/apport/apport-kde, line 530, in module sys.exit(UserInterface.run_argv()) File /usr/lib/python2.7/dist-packages/apport/ui.py, line 652, in run_argv return self.run_update_report() File /usr/lib/python2.7/dist-packages/apport/ui.py, line 568, in run_update_report response = self.ui_present_report_details(allowed_to_report) File /usr/share/apport/apport-kde, line 367, in ui_present_report_details desktop_info) File /usr/share/apport/apport-kde, line 184, in __init__ self.ui.ui_update_view(self) File /usr/share/apport/apport-kde, line 358, in ui_update_view QTreeWidgetItem(keyitem, [str(line)]) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 21: ordinal not in range(128) -- 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE)
Given that apport collect fails, can the incomplete tag be removed anyway? -- 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE)
3.17.0 impossible to test because, for some reason, it fails to boot to X with the nvidia proprietary driver, so it is hard to test in realistic conditions. In any case, I would say that the issue has been introduced in the 3.16 - 3.17 transition. Can this be reported 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade
Please disregard my previous message. The bug is definitely there. In some cases it does not manifest immediately. Conversely, it is quite frequent to see the IOWAIT close to zero at system startup. Then after a while the system is up, the IOWAIT jumps for no reason at about 50% and stays there. When this happens, nothing is initially reported in dmesg/syslog. However the system starts showing some issues. 1) Trying to mount the zip drive, namely sudo mount /dev/sda /mnt/tmp hangs forever. The process cannot be interrupted. Interestingly, this happens even if there is no disk in the drive, a situation that the kernel should see immediately, even before trying the mount action. When the hang occurs, the kernel starts complaining in dmesg about a hung process: [11877.606063] INFO: task mount:14652 blocked for more than 120 seconds. [11877.606077] Tainted: P C OE 3.19.0-18-generic #18-Ubuntu [11877.606082] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [11877.606088] mount D 88006ad038f8 0 14652 14651 0x [11877.606099] 88006ad038f8 880062ecebf0 00014200 88006ad03fd8 [11877.606108] 00014200 88011a818000 880062ecebf0 88011fcd4200 [11877.606115] 88006ad03a50 7fff 88006ad03a48 880062ecebf0 [11877.606121] Call Trace: [11877.606139] [817c4f99] schedule+0x29/0x70 [11877.606149] [817c857c] schedule_timeout+0x20c/0x280 [11877.606161] [8109ed1d] ? ttwu_do_activate.constprop.94+0x5d/0x70 [11877.606169] [810a1c19] ? try_to_wake_up+0x1e9/0x340 [11877.606178] [817c6954] wait_for_completion+0xa4/0x170 [11877.606183] [810a1de0] ? wake_up_state+0x20/0x20 [11877.606191] [8108ef1a] flush_work+0xea/0x1c0 [11877.606200] [8108bb10] ? destroy_worker+0xa0/0xa0 [11877.606206] [8108f0f8] __cancel_work_timer+0x98/0x1b0 [11877.606214] [813949f1] ? exact_lock+0x11/0x20 [11877.606223] [81509d72] ? kobj_lookup+0x112/0x170 [11877.606230] [813939f0] ? disk_map_sector_rcu+0x80/0x80 [11877.606237] [8108f243] cancel_delayed_work_sync+0x13/0x20 [11877.606243] [81395991] disk_block_events+0x81/0x90 [11877.606252] [8122d64b] __blkdev_get+0x5b/0x490 [11877.606259] [8122dac1] blkdev_get+0x41/0x390 [11877.606266] [8122de70] ? blkdev_get_by_dev+0x60/0x60 [11877.606273] [8122decf] blkdev_open+0x5f/0x90 [11877.606281] [811f0d82] do_dentry_open+0x1d2/0x330 [11877.606288] [811f1049] vfs_open+0x49/0x50 [11877.606296] [81201b47] do_last+0x227/0x12c0 [11877.606305] [812041e8] path_openat+0x88/0x610 [11877.606313] [8120598a] do_filp_open+0x3a/0xb0 [11877.606320] [81212777] ? __alloc_fd+0xa7/0x130 [11877.606328] [811f299a] do_sys_open+0x12a/0x280 [11877.606334] [810963ef] ? __put_cred+0x3f/0x60 [11877.606341] [811f1e70] ? SyS_access+0x1c0/0x210 [11877.606348] [811f2b0e] SyS_open+0x1e/0x20 [11877.606356] [817c990d] system_call_fastpath+0x16/0x1b 2) It is impossible to cleanly shutdown the machine. The shutdown operation hungs and the machine needs to be reset or switched off 3) It is impossible to install a kernel, since something hangs in the process at the update-initramfs stage. Point 3) makes it nasty to test new kernels for the 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade
3.16.7-031607-generic seems to have no issue. 3.19.0-18-generic has the issue 4.0.4-040004-generic cannot be tested because it is impossible for me to use X with it (the nvidia proprietary driver 304 does not work with it and Kwin does not work on my hardware without it). This is already good news since staying with the utopic kernel seems to be a workable workaround. In the future I'll try 3.17 and 3.18 if possible. Will take some time since the machine is only rarely used after the vivid upgrade as plasma 5 is too immature for regular use. -- 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade
3.18.14-031814-generic seems to have the 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade
After tons of testing, I strongly suspect that the issue was with a failing SATA cable, passing next to the IDE cable of the ZIP disk. Whenever detaching the ZIP, I was probably bending the SATA cable in such a way that made it work more reliably. Now the cable has failed altogether and, after replacement, the high IOWAIT seems to be gone, even with the ZIP disk attached. Sorry for the noise -- 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade
** Changed in: linux (Ubuntu) Status: Incomplete = 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade Status in linux package in Ubuntu: New Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade
Brad, I cannot provide log files: - If I boot with the zip disk the machine goes to 60% iowait and processes dealing with I/O start hunging. I do not want to risk my data just to try running apport (that would likely fail anyway). - If I boot without the zip disk, the log files cannot report anything because the machine works. I have already spent one whole night, diagnosing this issue down to the ATAPI zip drive. So I reset the bug as new. Please confirm it is propagated 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade Status in linux package in Ubuntu: New Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade
apport-collect 1451277 ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore Please do not ask things that are clearly beyond the possibilities of kubuntu vivid after the plasma 5 transition. ** 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/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade Status in linux package in Ubuntu: Confirmed Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic-vivid upgrade
After more research, I can confirm the bug and I hope I have also determined the cause... 1) Bug also happens when booting from the vivid iso image... so it is not dependent from leftovers due to the utopic-vivid upgrade. 2) Bug stops manifesting if I detach the IOMEGA ZIP drive (with ide connection) that I have in this machine I understand that the piece of hardware is obsolete, but it was working just fine with utopic. It is still not clear too me if the bug is in the kernel itself or in something in the system that causes it to be polled too frequently. Please, propagate upstream. ** Package changed: ubuntu = linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1451277 Title: Extremely high IOWait and processes hungs after utopic-vivid upgrade Status in linux-meta package in Ubuntu: New Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1451277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1058725] Re: XHCI (USB 3.0) kernel Module Prevents Hibernate
Hack in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/522998/comments/61
seems to work around the 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/1058725
Title:
XHCI (USB 3.0) kernel Module Prevents Hibernate
Status in linux package in Ubuntu:
Confirmed
Bug description:
On a system with an ASROCK N68S motherboard and a VIA VL800/801 PCI
USB3 adapter, the system, which is a 64 bit kubuntu precise with a 3.2
kernel cannot hibernate.
When you ask the system to hibernate, the OS does everything it should
and also appears to shut down the system (the fans stop). However,
after half a second the system restarts by itself, resuming from the
hibernation.
If you unbind the xhci_hcd driver from the usb card on the pci bus,
before hibernation then the system hibernates and resumes in the
correct way.
So, the very same hack proposed in bug report 522998 at comment 61
seem to (hackishly) fixes the issue.
IMHO this looks like a bug in the xhci driver. Please report upstream.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: NVidia [HDA NVidia], device 0: ALC662 rev1 Analog [ALC662 rev1
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: callegar 7430 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xfbef8000 irq 22'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,18493662,00100101'
Controls : 31
Simple ctrls : 18
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=c50b4249-43ed-49ef-a3d8-ec7aa9718265
IwConfig:
lono wireless extensions.
usb0 no wireless extensions.
eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-31-generic
root=/dev/mapper/DISK00-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
RelatedPackageVersions:
linux-restricted-modules-3.2.0-31-generic N/A
linux-backports-modules-3.2.0-31-generic N/A
linux-firmware1.79.1
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: precise
Uname: Linux 3.2.0-31-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-05-09 (143 days ago)
UserGroups: adm admin cdrom dialout fax floppy fuse lpadmin plugdev
sambashare scanner staff sudo syslog vboxusers
WpaSupplicantLog:
dmi.bios.date: 04/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.10
dmi.board.name: N68-S
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058725/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1058725] Re: XHCI (USB 3.0) kernel Module Prevents Hibernate
Marking the bug as confirmed, since there is a known working workaround,
proving that the bug exists.
** Changed in: linux (Ubuntu)
Status: New = 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/1058725
Title:
XHCI (USB 3.0) kernel Module Prevents Hibernate
Status in linux package in Ubuntu:
Confirmed
Bug description:
On a system with an ASROCK N68S motherboard and a VIA VL800/801 PCI
USB3 adapter, the system, which is a 64 bit kubuntu precise with a 3.2
kernel cannot hibernate.
When you ask the system to hibernate, the OS does everything it should
and also appears to shut down the system (the fans stop). However,
after half a second the system restarts by itself, resuming from the
hibernation.
If you unbind the xhci_hcd driver from the usb card on the pci bus,
before hibernation then the system hibernates and resumes in the
correct way.
So, the very same hack proposed in bug report 522998 at comment 61
seem to (hackishly) fixes the issue.
IMHO this looks like a bug in the xhci driver. Please report upstream.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: NVidia [HDA NVidia], device 0: ALC662 rev1 Analog [ALC662 rev1
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: callegar 7430 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xfbef8000 irq 22'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,18493662,00100101'
Controls : 31
Simple ctrls : 18
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=c50b4249-43ed-49ef-a3d8-ec7aa9718265
IwConfig:
lono wireless extensions.
usb0 no wireless extensions.
eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-31-generic
root=/dev/mapper/DISK00-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
RelatedPackageVersions:
linux-restricted-modules-3.2.0-31-generic N/A
linux-backports-modules-3.2.0-31-generic N/A
linux-firmware1.79.1
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: precise
Uname: Linux 3.2.0-31-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-05-09 (143 days ago)
UserGroups: adm admin cdrom dialout fax floppy fuse lpadmin plugdev
sambashare scanner staff sudo syslog vboxusers
WpaSupplicantLog:
dmi.bios.date: 04/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.10
dmi.board.name: N68-S
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058725/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1058725] Re: XHCI (USB 3.0) kernel Module Prevents Hibernate
Bug is still present as of utopic. Now also verified trying the same
USB3 pci card on an DELL Precision T5400 Server.
Unable to test upstream kernel, but it is extremely likely that the bug
is also present there.
Please, propagate to Sarah Sharp (who said me once Ubuntu doesn't forward me
bugs relating to xHCI, although I wish they
would) at linux-usb or linux-pm.
** Changed in: linux (Ubuntu)
Status: Expired = 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/1058725
Title:
XHCI (USB 3.0) kernel Module Prevents Hibernate
Status in linux package in Ubuntu:
Confirmed
Bug description:
On a system with an ASROCK N68S motherboard and a VIA VL800/801 PCI
USB3 adapter, the system, which is a 64 bit kubuntu precise with a 3.2
kernel cannot hibernate.
When you ask the system to hibernate, the OS does everything it should
and also appears to shut down the system (the fans stop). However,
after half a second the system restarts by itself, resuming from the
hibernation.
If you unbind the xhci_hcd driver from the usb card on the pci bus,
before hibernation then the system hibernates and resumes in the
correct way.
So, the very same hack proposed in bug report 522998 at comment 61
seem to (hackishly) fixes the issue.
IMHO this looks like a bug in the xhci driver. Please report upstream.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: NVidia [HDA NVidia], device 0: ALC662 rev1 Analog [ALC662 rev1
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: callegar 7430 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xfbef8000 irq 22'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,18493662,00100101'
Controls : 31
Simple ctrls : 18
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=c50b4249-43ed-49ef-a3d8-ec7aa9718265
IwConfig:
lono wireless extensions.
usb0 no wireless extensions.
eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-31-generic
root=/dev/mapper/DISK00-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
RelatedPackageVersions:
linux-restricted-modules-3.2.0-31-generic N/A
linux-backports-modules-3.2.0-31-generic N/A
linux-firmware1.79.1
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: precise
Uname: Linux 3.2.0-31-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-05-09 (143 days ago)
UserGroups: adm admin cdrom dialout fax floppy fuse lpadmin plugdev
sambashare scanner staff sudo syslog vboxusers
WpaSupplicantLog:
dmi.bios.date: 04/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.10
dmi.board.name: N68-S
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058725/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1286552] Re: No wifi after suspend
I see it on a laptop that does not connect automatically to the wireless network after wakeup. But I have the same issue also with a desktop with wired ethernet. So a more appropriate title would be 'network manager fails to reconnect after resume', because the issue is not wifi specific. After a suspend/resume cycle, network manager does not reconnect. For the desktop, given that this used to be a machine going to sleep when unused and being waken from the lan, the issue is pretty bad. The machine wakes... but with no network. Network manager stays there for ever, with the connection ready and selected for automatic connection, but does not even try to start the connection. Since it completely breaks the usability of wol, please rise priority. This is something recent. I have also started to see it about November. Furthermore, it used to work just fine with 14.04. -- 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/1286552 Title: No wifi after suspend Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: After suspending ubuntu the wifi doesn't work. The solution given here (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re- connecting-after-suspend) worked for me but when I have updated my Ubuntu now it won't work. I have tried to test mainline kernel but it won't to boot with it. To reproduce the bug : just suspend the computer and then power it. There's no wifi network until you restart the computer. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-release-upgrader-core 1:0.205.4 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 CrashDB: ubuntu Date: Sat Mar 1 15:20:39 2014 InstallationDate: Installed on 2013-12-30 (61 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131017) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradi 1503 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf InstallationDate: Installed on 2013-12-30 (61 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131017) MachineType: Hewlett-Packard HP Compaq 6830s MarkForUpload: True Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=3eaae47b-7485-4723-8b3e-9f6dac7a01e4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116.2 Tags: saucy Uname: Linux 3.11.0-15-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: Mar 1 15:34:33 meradi-HP-Compaq-6830s kernel: [ 4581.474196] perf samples too long (5002 5000), lowering kernel.perf_event_max_sample_rate to 25000 dmi.bios.date: 03/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZD Ver. F.0C dmi.board.name: 30E9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 95.1C dmi.chassis.asset.tag: CNU91609Y2 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZDVer.F.0C:bd03/12/2009:svnHewlett-Packard:pnHPCompaq6830s:pvrF.0C:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6830s dmi.product.version: F.0C dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1286552] Re: No wifi after suspend
As a further note, the script by aztecjoe works around the issue just fine. I would recommend delivering it via an updated network manager package and not waiting for network manager to have the issue fixed. If and when the issue is fixed in network manager, the redundant restart should not be a big 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/1286552 Title: No wifi after suspend Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: After suspending ubuntu the wifi doesn't work. The solution given here (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re- connecting-after-suspend) worked for me but when I have updated my Ubuntu now it won't work. I have tried to test mainline kernel but it won't to boot with it. To reproduce the bug : just suspend the computer and then power it. There's no wifi network until you restart the computer. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-release-upgrader-core 1:0.205.4 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 CrashDB: ubuntu Date: Sat Mar 1 15:20:39 2014 InstallationDate: Installed on 2013-12-30 (61 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131017) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradi 1503 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf InstallationDate: Installed on 2013-12-30 (61 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131017) MachineType: Hewlett-Packard HP Compaq 6830s MarkForUpload: True Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=3eaae47b-7485-4723-8b3e-9f6dac7a01e4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116.2 Tags: saucy Uname: Linux 3.11.0-15-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: Mar 1 15:34:33 meradi-HP-Compaq-6830s kernel: [ 4581.474196] perf samples too long (5002 5000), lowering kernel.perf_event_max_sample_rate to 25000 dmi.bios.date: 03/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZD Ver. F.0C dmi.board.name: 30E9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 95.1C dmi.chassis.asset.tag: CNU91609Y2 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZDVer.F.0C:bd03/12/2009:svnHewlett-Packard:pnHPCompaq6830s:pvrF.0C:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6830s dmi.product.version: F.0C dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1388991] [NEW] kernel postinst scripts errors
Public bug reported: During a normal sudo apt-get dist-upgrade my utopic system reported the need to upgrade the kernel package. During the process, I saw Setting up linux-image-3.16.0-24-generic (3.16.0-24.32) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-24-generic /boot/vmlinuz-3.16.0-24-generic run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-24-generic /boot/vmlinuz-3.16.0-24-generic sed: -e expression #1, char 6: unknown command: `m' so something must be wrong in some postinst script. I cannot evaluate the impact that this may have on the correct installation of the new kernel. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-generic 3.16.0.24.25 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 3469 F pulseaudio CurrentDesktop: KDE Date: Mon Nov 3 22:34:47 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c50b4249-43ed-49ef-a3d8-ec7aa9718265 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic root=/dev/mapper/DISK00-root ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8188eu UpgradeStatus: Upgraded to utopic on 2014-10-28 (6 days ago) WpaSupplicantLog: dmi.bios.date: 04/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: N68-S dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug staging utopic -- 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/1388991 Title: kernel postinst scripts errors Status in “linux” package in Ubuntu: New Bug description: During a normal sudo apt-get dist-upgrade my utopic system reported the need to upgrade the kernel package. During the process, I saw Setting up linux-image-3.16.0-24-generic (3.16.0-24.32) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-24-generic /boot/vmlinuz-3.16.0-24-generic run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-24-generic /boot/vmlinuz-3.16.0-24-generic sed: -e expression #1, char 6: unknown command: `m' so something must be wrong in some postinst script. I cannot evaluate the impact that this may have on the correct installation of the new kernel. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-generic 3.16.0.24.25 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 3469 F pulseaudio CurrentDesktop: KDE Date: Mon Nov 3 22:34:47 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c50b4249-43ed-49ef-a3d8-ec7aa9718265 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic root=/dev/mapper/DISK00-root ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8188eu UpgradeStatus: Upgraded to utopic on 2014-10-28 (6 days ago) WpaSupplicantLog: dmi.bios.date: 04/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: N68-S dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M.
[Kernel-packages] [Bug 1318837] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
Started to see this on an eeepc after upgrade to utopic, that basically made the wifi so fragile that the laptop cannot be used. -- 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/1318837 Title: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Status in “linux” package in Ubuntu: Invalid Bug description: In Trusty, happens continuously 100% of the time after boot/reboot, finally fails, followed by authentication failure. This doesn't happen with 12.04 Precise. --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kit284 2043 F pulseaudio /dev/snd/controlC1: kit284 2043 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=8bc3362d-e136-453f-bb6c-284013a5dd11 InstallationDate: Installed on 2014-04-02 (40 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) MachineType: CLEVO D900K NonfreeKernelModules: nvidia Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=e838aadc-8afe-436a-a3cb-a2908622ffc4 ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2005 dmi.bios.vendor: Phoenix dmi.bios.version: 4.06CJ15 dmi.board.name: D900K dmi.board.vendor: CLEVO dmi.board.version: VT8341B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd12/06/2005:svnCLEVO:pnD900K:pvrVT8341B:rvnCLEVO:rnD900K:rvrVT8341B:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: D900K dmi.product.version: VT8341B dmi.sys.vendor: CLEVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1318837] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
Actually happens with queue 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/1318837 Title: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Status in “linux” package in Ubuntu: Invalid Bug description: In Trusty, happens continuously 100% of the time after boot/reboot, finally fails, followed by authentication failure. This doesn't happen with 12.04 Precise. --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kit284 2043 F pulseaudio /dev/snd/controlC1: kit284 2043 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=8bc3362d-e136-453f-bb6c-284013a5dd11 InstallationDate: Installed on 2014-04-02 (40 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) MachineType: CLEVO D900K NonfreeKernelModules: nvidia Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=e838aadc-8afe-436a-a3cb-a2908622ffc4 ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2005 dmi.bios.vendor: Phoenix dmi.bios.version: 4.06CJ15 dmi.board.name: D900K dmi.board.vendor: CLEVO dmi.board.version: VT8341B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd12/06/2005:svnCLEVO:pnD900K:pvrVT8341B:rvnCLEVO:rnD900K:rvrVT8341B:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: D900K dmi.product.version: VT8341B dmi.sys.vendor: CLEVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1326092] Re: [Haswell i915] WARNING: CPU 0: at ... i915 intel_ddi.c intel_ddi_pll_mode_set
Bug is also present in 3.16.x See also https://bugzilla.kernel.org/show_bug.cgi?id=59321 Please assure that the relevant patches are applied on the trusty (lts) and utopic (current) kernels. IMHO this issue is particularly serious because in most cases the system appears to resume from hibernation (the oopses are not seen unless you explicitly look at the system messages) and the machine appears to work for some minutes before freezing. This means that there is the opportunity for severe data loss. ** Bug watch added: Linux Kernel Bug Tracker #59321 http://bugzilla.kernel.org/show_bug.cgi?id=59321 -- 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/1326092 Title: [Haswell i915] WARNING: CPU 0: at ... i915 intel_ddi.c intel_ddi_pll_mode_set Status in “linux” package in Ubuntu: Confirmed Bug description: I get this whenever I resume from hibernation. When googling for WARNING intel_ddi_pll_mode_set there are countless other bug reports of this sort for other projects (Redhat, ChromeOS, ...), so this seems to be a popular Haswell issue. ACPI: Waking up from system sleep state S4 PM: noirq restore of devices complete after 7.267 msecs dmar: DRHD: handling fault status reg 2 dmar: INTR-REMAP: Request device [[00:14.0] fault index 15 INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear PM: early restore of devices complete after 0.074 msecs usb usb3: root hub lost power or was reset usb usb4: root hub lost power or was reset snd_hda_intel :00:03.0: irq 42 for MSI/MSI-X xhci_hcd :00:14.0: irq 46 for MSI/MSI-X mei_me :00:16.0: irq 47 for MSI/MSI-X usb usb1: root hub lost power or was reset usb usb2: root hub lost power or was reset snd_hda_intel :00:1b.0: irq 48 for MSI/MSI-X ehci-pci :00:1a.0: cache line size of 64 is not supported ehci-pci :00:1d.0: cache line size of 64 is not supported i8042 kbd 00:09: System wakeup disabled by ACPI [ cut here ] WARNING: CPU: 0 PID: 28002 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_ddi.c:784 intel_ddi_pll_mode_set+0x871/0x8b0 [i915]() SPLL already enabled Modules linked in: btrfs raid6_pq xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cfg80211 pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) bnep rfcomm bluetooth snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi x86_pkg_temp_thermal intel_powerclamp snd_seq coretemp kvm_intel snd_seq_device snd_timer kvm mac_hid snd serio_raw shpchp lpc_ich mei_me mei soundcore intel_smartconnect parport_pc ppdev lp parport dm_crypt hid_generic usbhid hid crct10dif_pclmul mxm_wmi crc32_pclmul ghash_clmulni_intel aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper ahci drm r8169 libahci mii wmi video CPU: 0 PID: 28002 Comm: kworker/u8:2 Tainted: GF W O 3.13.0-27-generic #50-Ubuntu Hardware name: MSI MS-7817/B85M-E45 (MS-7817), BIOS V10.2 09/25/2013 Workqueue: events_unbound async_run_entry_fn 0009 88020f1c38d0 817199c4 88020f1c3918 88020f1c3908 810676bd 88020dbdc000 0001 00024414 88020d7f8000 88020f1c3968 Call Trace: [817199c4] dump_stack+0x45/0x56 [810676bd] warn_slowpath_common+0x7d/0xa0 [8106772c] warn_slowpath_fmt+0x4c/0x50 [a01318f1] intel_ddi_pll_mode_set+0x871/0x8b0 [i915] [8136be79] ? snprintf+0x39/0x40 [a0046577] ? drm_vblank_get+0x77/0x280 [drm] [81720202] ? mutex_lock+0x12/0x2f [a011f92b] haswell_crtc_mode_set+0x3b/0x460 [i915] [a01234ab] __intel_set_mode+0x67b/0x9d0 [i915] [8136187f] ? idr_get_empty_slot+0x16f/0x3c0 [a0126346] intel_set_mode+0x16/0x30 [i915] [a0126bfb] intel_crtc_set_config+0x7ab/0x9a0 [i915] [a004ee9d] drm_mode_set_config_internal+0x5d/0xe0 [drm] [a00b7f41] drm_fb_helper_set_par+0x71/0xf0 [drm_kms_helper] [a004dcc2] ? drm_modeset_unlock_all+0x52/0x60 [drm] [a00b7ec5] drm_fb_helper_hotplug_event+0x105/0x110 [drm_kms_helper] [a016044c] intel_fbdev_output_poll_changed+0x1c/0x20 [i915] [a00b3de7] drm_kms_helper_hotplug_event+0x27/0x30 [drm_kms_helper] [a00b45b8] drm_helper_hpd_irq_event+0x148/0x160 [drm_kms_helper] [a00e634c] __i915_drm_thaw+0x1dc/0x210 [i915] [a00e63dc] i915_resume+0x5c/0x90 [i915] [a00e6496] i915_pm_resume+0x16/0x20 [i915] [813a5ecd] pci_pm_restore+0x7d/0xd0 [813a5e50] ? pci_pm_suspend_noirq+0x1a0/0x1a0 [8149a049] dpm_run_callback+0x49/0xa0 [8149a1a6] device_resume+0xc6/0x1f0
[Kernel-packages] [Bug 1300386] Re: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty
apport information ** Tags added: apport-collected trusty ** Description changed: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled + --- + ApportVersion: 2.14.1-0ubuntu3.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: callegar 2789 F pulseaudio + callegar 3227 F pulseaudio + /dev/snd/controlC0: callegar 2789 F pulseaudio + callegar 3227 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 14.04 +
[Kernel-packages] [Bug 1300386] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1300386/+attachment/4175737/+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/bugs/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux” package in Ubuntu: Incomplete Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion:
[Kernel-packages] [Bug 1300386] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1300386/+attachment/4175728/+files/BootDmesg.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/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux” package in Ubuntu: Incomplete Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion: 2.14.1-0ubuntu3.3
[Kernel-packages] [Bug 1300386] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1300386/+attachment/4175738/+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/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux” package in Ubuntu: Incomplete Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion: 2.14.1-0ubuntu3.3
[Kernel-packages] [Bug 1300386] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1300386/+attachment/4175729/+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/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux” package in Ubuntu: Incomplete Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion: 2.14.1-0ubuntu3.3
[Kernel-packages] [Bug 1300386] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1300386/+attachment/4175740/+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/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux” package in Ubuntu: Incomplete Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion: 2.14.1-0ubuntu3.3
[Kernel-packages] [Bug 1300386] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1300386/+attachment/4175736/+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.net/bugs/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux” package in Ubuntu: Incomplete Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion:
[Kernel-packages] [Bug 1300386] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1300386/+attachment/4175733/+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/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux” package in Ubuntu: Incomplete Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion: 2.14.1-0ubuntu3.3
[Kernel-packages] [Bug 1300386] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1300386/+attachment/4175730/+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/bugs/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux” package in Ubuntu: Incomplete Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion:
[Kernel-packages] [Bug 1300386] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1300386/+attachment/4175731/+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/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux” package in Ubuntu: Incomplete Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion: 2.14.1-0ubuntu3.3
[Kernel-packages] [Bug 1300386] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1300386/+attachment/4175734/+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/bugs/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux” package in Ubuntu: Incomplete Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion:
[Kernel-packages] [Bug 1300386] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1300386/+attachment/4175742/+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/bugs/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux” package in Ubuntu: Incomplete Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion: 2.14.1-0ubuntu3.3
[Kernel-packages] [Bug 1300386] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1300386/+attachment/4175732/+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/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux” package in Ubuntu: Incomplete Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion: 2.14.1-0ubuntu3.3
[Kernel-packages] [Bug 1300386] Re: Network manager fails to find bluetooth 'modem' for dun connection in saucy
Same issue in trusty. This is in fact a kernel bug: see https://lkml.org/lkml/2014/2/9/316. Tried mainline (e.g. 3.15.6) and works fine. There is also another bug in modemmanager/networkmanager. This keeps rfcomm0 open when the connection is dropped and causes modemmanager to keep asking the bluetooth phone about the signal quality. When you try to connect again, the connection fails. However, this is easily worked around by service modemmanager restart. So the main issue is with the kernel. The relevant patches should be backported to the saucy and trusty kernels. ** Summary changed: - Network manager fails to find bluetooth 'modem' for dun connection in saucy + Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty ** Package changed: network-manager (Ubuntu) = linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux-meta” package in Ubuntu: New Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: disconnected - prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: prepare - config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: info Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: config - failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: warn Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: info (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE
[Kernel-packages] [Bug 1165433] Re: Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect
To Jussi... as the original reporter of this bug, I think it has no hope of being fixed even if you provide all the relevant kernel commits. Which is bad, because the crash is serious and happens 'late' when may kernel data structures may have been written over, with potential data loss. I tried to provide pointers to all the relevant LKML entries and the only replies I got was that I should have run apport-collect, which was a bit frustrating. I hope that your list, that is much more organized than my posts, has a better success. Besides that, the bad news is that even on trusty (that has kernel 3.14), bluetooth dun is broken. At least here the issue is mere lack of functionality, no crashes. This is due to: - another kernel bug (it is probably http://lists.openwall.net/linux- kernel/2014/02/10/54). This prevents modemmanager from seeing rfcomm0 as a modem. Tried mainline 3.15.6 and works fine. - a bug in modemmanager/networkmanager. This keeps rfcomm0 open when the connection is dropped and causes modemmanager to keep asking the bluetooth phone about the signal quality. When you try to connect again, the connection fails. This is easily worked around by service modemmanager restart. Probably a new bug should be opened on launchpad against the kernel, wrt the issue of parenting rfcomm0. This fix should be easy to backport. But I am a bit discouraged. -- 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/1165433 Title: Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect Status in “linux” package in Ubuntu: Incomplete Bug description: Issue is obviously in the kernel that should not panic in any circumnstances. This bug is seen on quantal using the kernel from PPA mainline. Tested with 3.8.0 to 3.8.6. Since 3.8.x is going to be the raring kernel I believe that this should definitely be fixed before raring is shipped. Seen on: DELL E6500 with kubuntu quantal 12.10 64 bit and as said, kernel 3.8.6 from the mainline ppa. The machine has a Dell Computer Corp. Wireless 370 Bluetooth Mini-card (connected via an internal usb connection). The issue is shown when connecting to the internet via a Samsung Galaxy S plus phone, using a bluetooth DUN connection. It is reproducible every time. How to reproduce: 1) Use the bluetooth applet to discover the phone and associate to it. 2) Use network manager to setup a DUN connection with the phone through your APN 3) Connect to the internet via bluetooth DUN (connection works perfectly) 4) Disconnect from the network manager. At the same time you disconnect, the GUI session is terminated and the kernel panics, briefly showing a panic log on the screen. Note that: a) The issue is not present using the standard ubuntu quantal kernel b) The issue is not present using kernels from the mainline ppa before 3.8 (e.g., 3.7.x is fine for all x) c) The issue is not present when connecting to the internet using a USB mobile dongle (e.g. Huawei usb key) This looks pretty serious to me: kernel does not sync when panicing and there is a serious risk of data loss; connecting to the internet via a smart phone using bluetooth DUN seems to be something that one should take for granted on any modern OS. Furthermore, points a) and b) above show that this is a *regression* over previous kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 778236] Re: bluetooth adapter not found after wakeup
I see this in kubuntu 14.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/778236 Title: bluetooth adapter not found after wakeup Status in “bluez” package in Ubuntu: Confirmed Bug description: Kubuntu 11.04 amd64 Microstar GX623 When laptop wakes up from sleep mode it cannot see the bluetooth adapter anymore and bluetooth mouse does not work. This worked with Kubuntu 9.04, 9.10, 10.10 and does not work after upgrade to 11.04. After wake up the bluetooth adapter is on, when I do 'lsusb' I can see: ... Bus 007 Device 002: ID 0db0:a97a Micro Star International Bluetooth EDR Device ... but the graphic configurator tells No bluetooth adapter found. Bluetooth works well after normal boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/778236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1218547] Re: 8086:0416 [Clevo W350ST] brightness keys don't work on Kubuntu
Same issue here with a Schenker S413, identical to clevo W740SU, Sager NP240 and System 76 Galago ultrapro. Probem is worse than described, though. If you attach an external monitor and xrandr --ouptput HDMI2 --auto --output eDP1 --off (i.e. switch on external monitor, off internal one) then going back to xrandr --output eDP1 --auto leaves the laptop screen at brightness 0 (black). Since the brightness keys are not working, the only way to go back to a usable laptop is to reboot. The system 76 package in the system76 ppa may have a fix for this, but cannot be setup on machines that do not include the system76 signature in the bios. -- 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/1218547 Title: 8086:0416 [Clevo W350ST] brightness keys don't work on Kubuntu Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: The Fn+F8 and Fn+F9 keys are not working on my Clevo W350ST with Kubuntu Raring to change screen brightness of the internal laptop screen. I installed linux-headers-3.11.0-4, linux- headers-3.11.0-4-generic, linux-image-3.11.0-4-generic and linux- image-extra-3.11.0-4-generic from Saucy packages repository but the problem persists. Edit: Bug persists with v3.13-rc6-trusty. When trying the following event codes appear correctly: xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 36 = (keysym 0xff0d, Return), state = 0x10 keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x10 keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x10 And changing: /sys/class/backlight/intel_backlight/brightness changes the brightness of the screen, but pressing the key combination does not. I believe this happens because the key combination is, in fact, changing the value of: /sys/class/backlight/acpi_video0/brightness I have in my package sources: http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu http://ppa.launchpad.net/bumblebee/stable/ubuntu WORKAROUND: acpi_backlight=vendor (but this breaks autoswitch to external monitor when connecting one to VGA port) --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: silvio 2689 F pulseaudio /dev/snd/pcmC1D0p: silvio 2689 F...m pulseaudio /dev/snd/controlC0: silvio 2689 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=58f7acf2-4914-4b11-a2ac-e641cb4b39fd InstallationDate: Installed on 2013-08-18 (57 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Notebook W350STQ/W370ST MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=f0bca002-701a-49bb-befc-7343bac2e245 ro locale=pt_BR quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 RelatedPackageVersions: linux-restricted-modules-3.11.0-9-generic N/A linux-backports-modules-3.11.0-9-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: raring Uname: Linux 3.11.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 04/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W350STQ/W370ST dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/11/2013:svnNotebook:pnW350STQ/W370ST:pvrNotApplicable:rvnNotebook:rnW350STQ/W370ST:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W350STQ/W370ST dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1218547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1165433] Re: Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect
There is no activity from me because I have unsubscribed from the bug... it is just by chance that I am reading this now. This bug has been investigated and fixed in recent linux ages ago and Jussi, eccerr0r and I have provided all the relevant information and pointers in this thread. It has also been clarified in LKML that due to the type of bug it is quite meaningless to provide traces and that this bug may cause data loss due to corruption of the kernel data structures. Yet, dangerous as it is, and regardless of the many users confirmig the issue, the bug remains unconfirmed because there is no apport-collect that is considered much more important than all the other info. And since the bug is not confirmed, the ubuntu kernel developers are just ignoring the report and all the useful pointers to upstream discussion. And not surprisingly ubuntu remains unfixed months after the upstream fix. Similarly not surprisingly duplicate bug reports spring out without being recognized as such. Unfortunately, I must say that I really find it a waste of time to report bugs and spend time in checking the LKML and provide pointers to the root relevant discussion there and pointers to upstream patches that fix the issue in this condition. And this is why I gave in. Also it is a bit sad that eccerr0r is invited not stay out of the discussion in the duplicate 1256811 just because his main OS is gentoo. I am also really sorry to say that the management of this bug report seems to me as all rules and bureaucracy and zero substance, but I hope that this can be accepted as constructive criticism, since I'm also taking the time to try to explain why I'm getting this impression. -- 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/1165433 Title: Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect Status in “linux” package in Ubuntu: Incomplete Bug description: Issue is obviously in the kernel that should not panic in any circumnstances. This bug is seen on quantal using the kernel from PPA mainline. Tested with 3.8.0 to 3.8.6. Since 3.8.x is going to be the raring kernel I believe that this should definitely be fixed before raring is shipped. Seen on: DELL E6500 with kubuntu quantal 12.10 64 bit and as said, kernel 3.8.6 from the mainline ppa. The machine has a Dell Computer Corp. Wireless 370 Bluetooth Mini-card (connected via an internal usb connection). The issue is shown when connecting to the internet via a Samsung Galaxy S plus phone, using a bluetooth DUN connection. It is reproducible every time. How to reproduce: 1) Use the bluetooth applet to discover the phone and associate to it. 2) Use network manager to setup a DUN connection with the phone through your APN 3) Connect to the internet via bluetooth DUN (connection works perfectly) 4) Disconnect from the network manager. At the same time you disconnect, the GUI session is terminated and the kernel panics, briefly showing a panic log on the screen. Note that: a) The issue is not present using the standard ubuntu quantal kernel b) The issue is not present using kernels from the mainline ppa before 3.8 (e.g., 3.7.x is fine for all x) c) The issue is not present when connecting to the internet using a USB mobile dongle (e.g. Huawei usb key) This looks pretty serious to me: kernel does not sync when panicing and there is a serious risk of data loss; connecting to the internet via a smart phone using bluetooth DUN seems to be something that one should take for granted on any modern OS. Furthermore, points a) and b) above show that this is a *regression* over previous kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1165433] Re: Kernel 3.8.x panics on bluetooth DUN disconnect
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Summary changed: - Kernel 3.8.x panics on bluetooth DUN disconnect + Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect -- 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/1165433 Title: Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect Status in “linux” package in Ubuntu: Confirmed Bug description: Issue is obviously in the kernel that should not panic in any circumnstances. This bug is seen on quantal using the kernel from PPA mainline. Tested with 3.8.0 to 3.8.6. Since 3.8.x is going to be the raring kernel I believe that this should definitely be fixed before raring is shipped. Seen on: DELL E6500 with kubuntu quantal 12.10 64 bit and as said, kernel 3.8.6 from the mainline ppa. The machine has a Dell Computer Corp. Wireless 370 Bluetooth Mini-card (connected via an internal usb connection). The issue is shown when connecting to the internet via a Samsung Galaxy S plus phone, using a bluetooth DUN connection. It is reproducible every time. How to reproduce: 1) Use the bluetooth applet to discover the phone and associate to it. 2) Use network manager to setup a DUN connection with the phone through your APN 3) Connect to the internet via bluetooth DUN (connection works perfectly) 4) Disconnect from the network manager. At the same time you disconnect, the GUI session is terminated and the kernel panics, briefly showing a panic log on the screen. Note that: a) The issue is not present using the standard ubuntu quantal kernel b) The issue is not present using kernels from the mainline ppa before 3.8 (e.g., 3.7.x is fine for all x) c) The issue is not present when connecting to the internet using a USB mobile dongle (e.g. Huawei usb key) This looks pretty serious to me: kernel does not sync when panicing and there is a serious risk of data loss; connecting to the internet via a smart phone using bluetooth DUN seems to be something that one should take for granted on any modern OS. Furthermore, points a) and b) above show that this is a *regression* over previous kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
