Re: [Bug 1838919] Re: Slow and lost keyboard and mouse events
Daniel I am Brian's wife, Jane I am devastated to let you know that Brian succumbed to his prostate cancer and died a few weeks ago Please let everyone know Thanks Jane Burch On 7/8/20 7:50 pm, Daniel van Vugt wrote: > Thank you for reporting this bug to Ubuntu. > Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020. > > See this document for currently supported Ubuntu releases: > https://wiki.ubuntu.com/Releases > > We appreciate that this bug may be old and you might not be interested > in discussing it any more. But if you are then please upgrade to the > latest Ubuntu version and re-test. If you then find the bug is still > present in the newer Ubuntu version, please add a comment here telling > us which new version it is in and change the bug status to Confirmed. > > ** Changed in: gnome-shell (Ubuntu) > Status: Incomplete => Won't Fix > > ** Changed in: mutter (Ubuntu) > Status: Incomplete => Won't Fix > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1838919/+attachment/5331424/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1838919/+attachment/5331422/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1838919] Re: Slow and lost keyboard and mouse events
On 24/2/20 3:12 pm, Daniel van Vugt wrote:
> Actually I should have just continued from comment #27. To do that
> please run:
>
>mv ~/.local/share/gnome-shell/extensions ~/old-extensions
Oops! I had already run the "dconf reset"!
Never mind, I was not aware of having changed the settings from their
original defaults. I presume they were residual from an earlier release.
> and then reboot. Any improvement?
The keyboard hang happens fairly frequently, but perhaps less often than
before the reset. Also, mouse hangs are rare and recover automatically,
so I can't be certain there is still a problem.
I will run the apport-collect, but I am content to live with the problem
and re-assess when 20.04 is available.
Thanks for caring!
Brian
> ** Changed in: gnome-shell (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: mutter (Ubuntu)
> Status: New => Incomplete
>
** Description changed:
This was a fresh amd64 installation with 18.10 desktop, upgraded to
19.04 as soon as available. It has been getting worse over the last few
weeks and is now so bad I can hardly type an email (or this bug report!)
without having to fix many typos.
journalctl shows many different gnome errors, so it is difficult to
figure out which is the underlying cause and which are simply collateral
damage.
There are two sequences that appear first after a reboot, and the first
of these has been reported many times on ubuntu releases going back for
years:-
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be
loaded.
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module
"canberra-gtk-module"
and
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG]
Registering StatusNotifierItem
:1.89/org/ayatana/NotificationItem/software_update_available
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable
to update overlay icon
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable
to update overlay icon
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error
from previous GL command
Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error
from previous GL command
Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-
Is this a recent regression? I know for sure the system wasn't this
unresponsive 3 weeks ago, but I cannot be sure when it started to go
wrong. My mouse/keyboard combo has a USB-wireless dongle and I've
fiddled around with distance and battery state until I was sure the
problem was somewhere else and started to check the system log.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-software 3.30.6-2ubuntu4.19.04.1
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 5 11:53:37 2019
InstalledPlugins:
[Bug 1838919] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1838919/+attachment/5331421/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1838919/+attachment/5331420/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1838919/+attachment/5331423/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
Sorry for the delay. The problem still exists under 19.10 desktop, but does not occur quite as often. However, it is slightly harder to escape from... I either need to wait 20+ seconds uselessly pressing keys I will have to subsequently delete, or tab to another command prompt, type something in easily, then return to the "stuck" prompt. My comment is only to bring the bug report up to date and keep it open. We are only a few weeks from the 20.04 release, where this bug will be much more important if still present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
Excellent news! The bluetooth dock battery status started working properly a couple of weeks ago. I can't be sure which update fixed the bug, but here is the latest system status:- ubuntu 19.10 eoan Desktop 5.3.0-26-generic x86_64 kernel Bluez-* 5.50-0ubuntu4 gnome-bluetooth 3.34.0-1 udev 242-7ubuntu3.2 libudev-1.0.0"amd64 1.233-1 The bug can finally be closed as fixed. Thanks very much everyone who contributed. Brian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
I upgraded both my Ubuntu Desktop and UbuntuStudio systems to 19.10 Eoan (with gnome mostly at 3.34). The symptoms have not changed... my desktop still hangs, loses keyboard events, and the log fills with the GTK 2/3 conflict messages. Meanwhile my Studio system behaves perfectly! The log messages are generated by nautilis, gnome terminal, thunderbird, and several other applications, but I do not think they are the culprits - just the victims of something unseen. The Studio system also has many GTK2 packages installed alongside the GTK3 ones, so there isn't a simple explanation for the difference in behaviour. I will do a side-by-side comparison of installed packages to see if there is some sort of clue. Meanwhile, I would be grateful if anyone could suggest how to identify the guilty component. I would love to purge it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
I didn't see any problems logging on with gnome on xorg, or starting the first terminal session. However, as soon as I started the second terminal, the GTK2/GTK3 error messages poured out. Opening a new tab on the same window does not generate the messages. This sounds like your gnome bug report - it doesn't look like a widget, or an application, but something more fundamental. I wonder why my system even has the i386 packages installed - were they pulled in by an application (such as wine) which isn't installed on my laptop? What is the best way to locate the culprit - I now know it isn't Chrome, thunderbird, nautilus or netbeans. It's hard to believe gnome- terminal is the root cause. ** Attachment added: "journalctl with xorg when starting a second terminal session" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5282548/+files/2019-08-15-xorg-gnome-second-terminal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1838919] Re: Slow and lost keyboard and mouse events
On 14/8/19 8:22 pm, Traumflug wrote: > Installed packages don't matter if their content isn't in use. It does > matter whether you run an X11 or a Wayland session. > > To switch between both, log out to get to the login screen. There is a > gears icon right above the password entry field, click on it. This > should open a menu allowing to choose between "Ubuntu on Xorg" and > "Ubuntu on Wayland". Having this choice done, log in, you'll be in the > selected type of session. I had forgotten the gear wheel.. the last time I used it was when unity came out as the new default and I preferred Gnome Classic. Thanks for reminding me. > Basically, all applications work in both session types, but there are a > number of smaller visual distinctions. For example, Firefox draws its > menu inside the window bar on Wayland, while it draws the menu under the > window bar on X11. Also, on X11 there's a process "Xorg" running, while > on Wayland there's a process "XWayland" (or similar). The default on the desktop system was "ubuntu", so I changed to "Gnome on Xorg". The presentation details are different (obviously) but don't bother me. However, I get exactly the same errors logged and slow input events:- Aug 15 07:21:43 schizo gnome-control-c[8320]: GTK+ module /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libgail.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Aug 15 07:21:43 schizo gnome-control-c[8320]: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. Aug 15 07:21:44 schizo gnome-control-c[8320]: GTK+ module /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Aug 15 07:21:44 schizo gnome-control-c[8320]: Failed to load module "canberra-gtk-module" Aug 15 07:21:44 schizo gnome-control-c[8320]: GTK+ module /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Aug 15 07:21:44 schizo gnome-control-c[8320]: Failed to load module "canberra-gtk-module" I will try again but this time only start a terminal session. I realise there is a lot of processes running to support a single graphical user session, but I'll keep Chrome and Thunderbird out of the variables. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
Thank you very much for your suggestion #21, Traumflug. I read the issue you quoted and to be honest, I was quite disappointed in the responses so far. The symptoms sound very similar to those I reported here. I compared the wayland packages on my desktop (slow or lost mouse and keyboard events) with those on my laptop (ubuntu studio), which works satisfactorily. I will attach a file containing the two dpkg lists for comparison. I really don't understand the wayland architecture, but was happy to use the recommended workaround when running sudo gui programs such as gparted. I notice two differences and wonder whether either of them might account for the diference between my two systems? 1. The desktop has three i386 old packages not installed on the laptop. Perhaps I should delete them? 2. The desktop has the xwayland package installed, but the laptop does not. What do you think? Is this helpful in tracking down the root cause of the problem? Is there anything I can do to assist with further diagnosis, given I have two systems side-by-side for comparison? ** Attachment added: "dpkg list comparison for wayland" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5282468/+files/2019-08-14-wayland-packages-compared -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
I had a bit of a brainwave this morning - or perhaps just awoke from my stupidity! I also have a laptop which runs ubuntu studio 19.04 amd64. At the moment, my desktop which is suffering has the 5.0.0-23-generic kernel. The laptop has the 5.0.0-21-lowlatency kernel, BUT does not have all these problems. The laptop also has gtk2 and gtk3 packages installed, although I haven't yet done a package-by-package diff. As far as I can remember, they both have mostly the same applications, although studio has a lot more. The laptop currently has upgrades waiting to be installed for the kernel, chromium, chrome and mutter (and quite a few more packages). Should I upgrade those packages on the laptop one at a time, to see whether the same problem appears? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
dpkg list next... ** Attachment added: "dpkg list" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281101/+files/schizo-2019-08-06-allpackages-txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
Hi Daniel, thanks for not giving up! First, here is snap list:- Name Version Rev Tracking Publisher Notes core 16-2.39.3 7270 stablecanonical✓ core core18201907231074 stablecanonical✓ base gnome-3-26-1604 3.26.0.20190705 90stable/… canonical✓ - gnome-3-28-1804 3.28.0-10-gaa70833.aa70833 67stablecanonical✓ - gnome-calculator 3.32.1 406 stable/… canonical✓ - gnome-characters v3.32.1+git2.3367201296 stable/… canonical✓ - gnome-logs3.32.0-4-ge8f3f37ca861stable/… canonical✓ - gnome-system-monitor 3.32.1-3-g0ea89b4922100 stable/… canonical✓ - gtk-common-themes 0.1-22-gab0a26b 1313 stable/… canonical✓ - pdftk-smoser 2.02-4 18stablesmoser - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
top on 4 second intervals rotates the same 5 or 6 threads, so I set the interval to 20 seconds and copied the output to a file, which I have attached. I have also attached the dpkg list. ** Attachment added: "top interval 20 seconds" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281100/+files/schizo-2019-08-06-top-d-20 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
What can I do to help you diagnose the problem further, Daniel? I think something changed recently, and that must have been an update. I do not believe I have installed any new packages that might have called for GTK2, so my guess is that it has been there since the clean 18.10 install and not been in conflict with GTK3 until recently. Searching on the conflict has not revealed anything helpful to me because this kind of error has popped up lots of times as far back as ubuntu 12.04. The packages recommended to be installed to "fix" these old problems all seem to be present on my system already. Is there an easy way to discover what is calling for GTK2, or is that being done by canberra on behalf of some applications, but not others? Is there any point in me booting recovery mode to see whether the errors (keyboard mapping too, don't forget) are logged from the simple tty console login? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
Also, I will attach journalctl -xb log taken as soon as I booted the system and logged on this morning. It seems to me that as soon as systemd started the gnome terminal server unit, related error messages began to be generated. Chrome/chromium had not been started at the time - it was autostarted by your apport command quite a while later. ** Attachment added: "cold boot journalctl" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281063/+files/schizo-2001908-06-xb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
Thanks for explaining Daniel #5. You will see I ran the command again. However... It is interesting to see that even the apport-collect command from a new terminal session triggered the canberra error. brian@schizo:~$ apport-collect 1838919 (apport-gtk:21631): Gtk-WARNING **: 08:30:48.771: GTK+ module /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libgail.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Gtk-Message: 08:30:48.771: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. (apport-gtk:21631): Gtk-WARNING **: 08:30:49.106: GTK+ module /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Gtk-Message: 08:30:49.106: Failed to load module "canberra-gtk-module" The authorization page: (https://launchpad.net/+authorize-token?oauth_token=t0cRSdJcr5xGQ4MLSbPG_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... brian@schizo:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1838919/+attachment/5281059/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1838919/+attachment/5281061/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1838919/+attachment/5281062/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
apport information
** Tags added: apport-collected
** Description changed:
This was a fresh amd64 installation with 18.10 desktop, upgraded to
19.04 as soon as available. It has been getting worse over the last few
weeks and is now so bad I can hardly type an email (or this bug report!)
without having to fix many typos.
journalctl shows many different gnome errors, so it is difficult to
figure out which is the underlying cause and which are simply collateral
damage.
There are two sequences that appear first after a reboot, and the first
of these has been reported many times on ubuntu releases going back for
years:-
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be
loaded.
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module
"canberra-gtk-module"
and
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG]
Registering StatusNotifierItem
:1.89/org/ayatana/NotificationItem/software_update_available
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable
to update overlay icon
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable
to update overlay icon
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error
from previous GL command
Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error
from previous GL command
Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-
Is this a recent regression? I know for sure the system wasn't this
unresponsive 3 weeks ago, but I cannot be sure when it started to go
wrong. My mouse/keyboard combo has a USB-wireless dongle and I've
fiddled around with distance and battery state until I was sure the
problem was somewhere else and started to check the system log.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-software 3.30.6-2ubuntu4.19.04.1
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 5 11:53:37 2019
InstalledPlugins:
gnome-software-plugin-flatpak 3.30.6-2ubuntu4.19.04.1
gnome-software-plugin-snap3.30.6-2ubuntu4.19.04.1
SourcePackage: gnome-software
UpgradeStatus: Upgraded to disco on 2019-04-28 (98 days ago)
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 19.04
+ Package: mutter
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
+ RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
+ Tags: disco
+ Uname: Linux 5.0.0-23-generic x86_64
+ UpgradeStatus: Upgraded to disco on 2019-04-28 (99 days ago)
+ UserGroups: adm audio cdrom dip disk floppy lp lpadmin plugdev sambashare
scans sudo video wireshark
+ _MarkForUpload: True
** Attachment added: "Dependencies.txt"
[Bug 1838919] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1838919/+attachment/5281060/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
Daniel post #2. That was exactly how I opened this bug report, so what exactly are you missing? Daniel post #3. I don't use Chromium, by preferred browser is stock vanilla Chrome from their own repository. I did not think Chrome was delivered as a snap - are you sure your comment is relevant? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] [NEW] Slow and lost keyboard and mouse events
Public bug reported: This was a fresh amd64 installation with 18.10 desktop, upgraded to 19.04 as soon as available. It has been getting worse over the last few weeks and is now so bad I can hardly type an email (or this bug report!) without having to fix many typos. journalctl shows many different gnome errors, so it is difficult to figure out which is the underlying cause and which are simply collateral damage. There are two sequences that appear first after a reboot, and the first of these has been reported many times on ubuntu releases going back for years:- Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module "canberra-gtk-module" and Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.89/org/ayatana/NotificationItem/software_update_available Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable to update overlay icon Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable to update overlay icon Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]: [4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]: [4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]: [4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- Is this a recent regression? I know for sure the system wasn't this unresponsive 3 weeks ago, but I cannot be sure when it started to go wrong. My mouse/keyboard combo has a USB-wireless dongle and I've fiddled around with distance and battery state until I was sure the problem was somewhere else and started to check the system log. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-software 3.30.6-2ubuntu4.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 11:53:37 2019 InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu4.19.04.1 gnome-software-plugin-snap3.30.6-2ubuntu4.19.04.1 SourcePackage: gnome-software UpgradeStatus: Upgraded to disco on 2019-04-28 (98 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
The system is now running 19.04 x64 desktop. The problem has not changed in any obvious manner, although reporting of battery status for its external logitech bluetooth mouse is now correct. Ca anyone suggest how to perform further problem determination, or perhaps even a circumvention. The 0% battery notifications appear every 10 minutes or so and are very tiresome to regularly delete (re the little boy who cried wolf). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
I installed the 5.0.0-15-generic kernel and removed iwlwifi from the /etc/modprobe.d/blacklist. The system was stable and ran very well for 4 or 5 hours. When I booted it (still generic kernel) this morning, it failed after about 20 minutes. I rebooted and teed journalctl for documentation. The failure occurred after only 4 or 5 minutes. I will attach the log from this crash. ** Attachment added: "generic kernel log during failure" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+attachment/5265227/+files/dell-inspiron-iwlwifi-7265D-29-generic-kernel-failure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1764450] Re: [needs-packaging] pdftk missing in 18.04 (bionic) and later releases
On 15/5/19 6:34 pm, Dylan Aïssi wrote: > ** Also affects: pdftk (Ubuntu Bionic) > Importance: Undecided > Status: New > > ** Changed in: pdftk (Ubuntu) > Status: Confirmed => Fix Released Thanks, Dylan I installed the pdftk package from the disco 19.04 repository and ran one of my "stock" scripts against a pdf. It worked perfectly. This doesn't constitute a full system test, but satisfies me. Given the bug was for the package being missing, rather than any specific broken behaviour when installed, I reckon you can close it as fixed. Regards, Brian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764450 Title: [needs-packaging] pdftk missing in 18.04 (bionic) and later releases To manage notifications about this bug go to: https://bugs.launchpad.net/pdftk/+bug/1764450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
On 17/5/19 1:14 am, Kai-Heng Feng wrote: > Sorry for the late reply. Does this happen on generic kernel? > It is so good to hear from anyone on this problem, so I welcome your "late reply"! My laptop runs ubuntu studio 19.04, but studio stopped including the linux-generic package many releases ago. By the way, /lib/firmware/iwlwifi-7265D-29.ucode is the latest on this 19.04 disco system, dated 18 May 2018, so I have confirmed it as broken with at least two earlier ubuntu releases and very many kernels. I suppose we should wish iwlwifi-7265D-29 a happy birthday??? In order to answer your question, there is no reason why I cannot install it, so I will try to find time in the next few days... unfortunately I have a broken desktop and other work commitments which need to be delivered using only this laptop, so I don't want to distract myself and accidentally break something! I'll get back to you in a day or two. I am very interested in the result of the test. Regards, Brian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
After upgrading to 19.04 disco, the system is still too unstable to be useful. The current kernel is 5.0.0-13-lowlatency (buildd@lcy01-amd64-020). I note the Intel driver has not changed after the upgrade from 18.10 cosmic, i.e. still iwlwifi-7265D-29.ucode, packaged within linux- firmware version 1.178. The details of the stack trace are different, but the outcome is the same (attached). The wifi connection is lost and kernel error messages spew out to the log. Stopping and restarting wifi makes no difference. The only "solution" is to shut down the system and reboot. Luckily I have a usb dongle that uses rtlwifi firmware, which works OK. ** Attachment added: "disco kernel log when intel driver hang is reported" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+attachment/5261968/+files/bacchus-iwlwifi-hang-log-disco-2019-04-27 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
I suspect I need to open a new bug for the ASUS docking station (detachable bluetooth keyboard with touchpad) under 18.04.1 LTS. This system is completely up to date, but it still reports 0% charge all the time. I checked the directory tree for /sys/class/power_supply/AC0 (the mouse is blah/BAT0), but it doesn't have entries for capacity or capacity_level! Comparing the mouse with the dock, I found the former has a type of battery, while the latter has one of mains! I don't feel this is a kernel problem any more - I suspect this is a udev issue. Can anyone advise me whether my suspicion is correct and, if so, how to create a quirk file to correct the device definition... please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
Oops! My post #56 should have said the other synaptics mouse is also OK on 18.04.1 LTS (not 17.10). I also got the release of cosmic wrong - it is 18.10, of course! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
Things are much improved now on cosmic 18.04 ubuntu studio:- /sys/class/power_supply/BAT0/capacity:100 /sys/class/power_supply/hid-34:88:5d:87:92:8c-battery/capacity:85 Linux 4.18.0-11-lowlatency #12-Ubuntu SMP PREEMPT Tue Oct 23 21:12:42 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [The mouse is OK again on 17.10, while the ASUS docking station is still not correct. I will update this bug report with details soon.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
Is anything happening with this bug report? Are you waiting for me to do something more, or provide more information. If it has been passed upstream as I anticipated, could you let me have details so that I can follow progress there, please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
Thanks for your comment, Kai-Heng, but I did try the latest upstrem kernel at the weekend. Please refer to my post #8. Is there a good reason to try a kernel more recent than:- linux-image- unsigned-4.17.0-041700-lowlatency_4.17.0-041700.201806041953_amd64.deb ... along with its associated headers and modules packages? If you think there is, then I'll certainly install another and test it - I would really like to get this bug pinned down quickly, even if it can't be fixed straight away. It takes me an hour or so and I am rather busy at the moment, so I don't want to waste time just to "test" a few extra but irrelevant changes... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
** Attachment added: "current bionic lowlatency log when driver hangs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+attachment/5155779/+files/bacchus-wifi-hang-log-13-unifi-xb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
I installed the latest upstream kernel, headers and modules. As far as I can tell, it suffers exactly the same failure as the latest released bionic lowlatency kernel. The stack ttrace seems very similar and the timeout message looks to be the same. My guess is still the intel iwlwifi version 29 firmware (although all the older versions which will load onto my 3165 wifi adapter have failed in similar but not identical ways). I will attach a couple of journalctl logs for anyone interested and knowledgeable enough to compare. ** Attachment added: "upstream kernel log while driver is loaded" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+attachment/5155777/+files/bacchus-wifi-hang-log-14-upstream-xb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
** Attachment added: "upstream kernel log when driver hang is reported" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+attachment/5155778/+files/bacchus-wifi-hang-log-14-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
Joseph... I also thought I had mentioned this a quite a new machine, so it doesn't have a lot of history. However, I had a similar wifi failure quite often with the latest 17.10 kernel before the upgrade to 18.04. I will look for a 17.10 log if you think it would be helpful, but I'm not sure I kept any. More importantly, and more hopefully, I will try to install an upstream kernel as you suggest. I am certain of two things: 1. I have tried every version of iwlwifi from 29 back to 17. I'm pretty sure the older firmware packages would not work with my hardware and kernel versions. 2. If I blacklist iwlwifi and use a dongle with Realtek wifi adapter, the problem does not occur. Although it is possible this is a kernel or driver bug, my guess is we are dealing with a firmware bug. The Intel support page for this driver says: "Having Wi-Fi and Bluetooth running at the same time is a challenge." I am sure you will let me know if I can collect any other useful information, either before the failure, or after. In the meantime, I will follow the instructions by marking this bug "confirmed". ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
I won't confuse the matter with details, but after I reproduced the problem (obviously) apport could not reach launchpad because the wifi adapter was out of action. I connected an ethernet cable, but then apport failed on three different attempts. I was under the impression I had attached a "journalctl -f" log of the failure, but I don't see it above. I will attach another copy next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
** Attachment added: "Most recent log with firmware register dump and driver stack trace" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+attachment/5152884/+files/bacchus-wifi-hang-log-12-unifi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
I'm pretty sure the same hardware adapter and firmware is supporting bluetooth for my logitech mouse. ** Tags added: wifi ** Tags added: intel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
brian@bacchus:~$ uname -a Linux bacchus 4.15.0-22-lowlatency #24-Ubuntu SMP PREEMPT Wed May 16 17:09:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux brian@bacchus:~$ lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic lspci:- 16:00.0 Network controller: Intel Corporation Wireless 3165 (rev 79) ii linux-firmware1.173.1 all Firmware for Linux kernel drivers brian@bacchus:/lib/firmware$ ls -l | grep iwlwifi | grep 7265D lrwxrwxrwx 1 root root 21 Nov 18 2017 iwlwifi-7265D-10.ucode -> iwlwifi-7265-10.ucode -rw-r--r-- 1 root root 1002800 Mar 30 2017 iwlwifi-7265D-12.ucode -rw-r--r-- 1 root root 1008692 Mar 30 2017 iwlwifi-7265D-13.ucode -rw-r--r-- 1 root root 1384500 Mar 30 2017 iwlwifi-7265D-16.ucode -rw-r--r-- 1 root root 1383604 Nov 18 2017 iwlwifi-7265D-17.ucode -rw-r--r-- 1 root root 1385368 Nov 18 2017 iwlwifi-7265D-21.ucode -rw-r--r-- 1 root root 1028376 Apr 25 00:23 iwlwifi-7265D-22.ucode -rw-r--r-- 1 root root 1032740 Dec 6 2017 iwlwifi-7265D-27.ucode -rw-r--r-- 1 root root 1036432 May 19 04:07 iwlwifi-7265D-29.ucode ** Attachment added: "Most recent log with firmware register dump and driver stack trace" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1776443/+attachment/5151672/+files/bacchus-wifi-hang-log-10-telstraAP-2-4g -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776443] [NEW] iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
Public bug reported: dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is down! Happens sometimes after a few minutes, never more than 30 minutes. Easy to capture journalctl when the network connection hangs. Intel fails on 2.4 GHz or 5 GHz, using several different AP's. The same system runs stable and perfect with a USB dongle Realtek RTL8188CUS, but I have to blacklist iwlwifi in /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network activity while simply scanning and not connected to an AP. I've had similar problems with this system under 17.10, but it has become more reproducible under 18.04. I've back-levelled the driver as far as possible, but they all hang the network. Because version 29 firmware is the latest in the bionic repository, and also on the intel support web site, I won't confuse matters by reporting earlier ubuntu kernels or iwlwifi versions ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1776443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
On 04/06/18 13:02, Daniel van Vugt wrote: > In comment #38 the original reporter confirms this bug did not exist up > to and including in kernel 4.14. It only exists in kernel 4.15 and > later. > > So on that basis any bug that does exist in 4.14 and earlier kernels > would not be a duplicate of this one. I think we have been talking at cross-purposes. My post #48 states "All three bluetooth devices reported credible power levels under their 17.10 systems they were running before upgrading to bionic." I used the term "17.10" because the artful kernels have been purged from these systems. I could not remember the exact version, so now I have checked and can refer accurately to them being OK when using 4.13 kernels. BUT I think you must have mis-read my post #48. I used the word "credible" to mean the reported power levels were probably correct under 4.13. Because they seemed to be reasonable at the time, I was happy with the reported power levels. However, a bluetooth mouse with brand new batteries under 4.15 and a reported level of zero percent power is definitely wrong! What next, Daniel? How can I help you? I really don't want to confuse you, or anyone else who might find this bug report. Brian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
On 04/06/18 11:57, Daniel van Vugt wrote: > Brian, it sounds like you should like a new bug. > > This bug is about a regression specifically in kernel 4.15, whereas 4.14 > works. Thanks for your quick reply, Daniel. Unfortunately, it has me confused! Both of my systems /are/ already running kernel 4.15, i.e. brian@bacchus:~$ uname -a Linux bacchus 4.15.0-22-lowlatency #24-Ubuntu SMP PREEMPT Wed May 16 17:09:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Am I missing your point? I'm happy to open a new bug, or even one for each machine if that helps. However, I don't want my new bug(s) to be immediately closed as a duplicate of 1769075. Could you explain, please? Brian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
I have the same problem with a Logitech M337 mouse and the 4.15.0-22-lowlatency kernel on my Dell Inspiron 15 laptop. I also with a different Logitech M337 on the 4.4.15.0-22-generic kernel on an Asus Transformer T300 Chi. Its bluetooth docking station reports zero battery, too. All three bluetooth devices reported credible power levels under their 17.10 systems they were running before upgrading to bionic. Is it a coincidence the two machines have Intel wifi/bluetooth adapters which use iwlwifi-7265D-29.ucode? I can run apport from these two machines if that would be helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584457] Re: gsd-backlight-helper spamming the logs since upate to 16.04
upgraded from 17.04 to 17.10 64-bit desktop. ASUS Transformer T300 CHI- FL005H. kernel 4.13.0-32-generic and gnome-settings-daemon 3.26.2-0ubuntu0.1 syslog and journalctl spammed exactly as described - gdm3 and gsd- backlight-helper --set-brightness I can confirm "systemctl stop iio-sensor-proxy" causes these messages to stop, but less frequent errors from org.gnome.Shell.desktop are logged repeatedly, e.g. Error.checkin_request.cc(211) failed to get checking response. Fetcher failed. Retrying. Followed by various other org.gnome.Shell.desktop messages. I can provide a log if they might be useful, but I suspect they are triggered by killing the iio-sensor-proxy and so are probably not very relevant to the original bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584457 Title: gsd-backlight-helper spamming the logs since upate to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1584457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683094] [NEW] Upgrade conflict DNS broken between Network Manager and systemd-resolved
Public bug reported: After upgrading my laptop from 16.10 ubuntu studio to 17.04, no DNS names could be resolved with either an ethernet or wifi connection. Something as simple as "ping myOtherHost" failed... The Zesty 17.04 release notes clearly state "The default DNS resolver is now systemd-resolved", but there is NO warning that this change will break many mature and working NetworkManager configurations. NetworkManager is still started by systemd, but it seems to be oblivious to the presence of systemd-resolved, which in my case had over-written the /etc/resolv.conf symlink created by NM. There is a lot of relevant but confusing posts out there, some for earlier releases of ubuntu. I managed to fight my way through the problem, but I suspect many people will be stuck and become angry. In particular, anyone who upgrades a working NM system with a configuration that is too complex for systemd-resolved (wifi seems to be the obvious problem area) won't even be able to search the internet for known problems unless he or she has access to a different computer! The circumvention is fairly simple and is documented elsewhere... the user MUST prevent systemd-resolved ever running and then repair Network Manager if it has been left damaged after the upgrade. First, prevent systemd-resolved from ever running: sudo systemctl stop systemd-resolved sudo systemctl disable systemd-resolved sudo systemctl mask systemd-resolved (yes, that is correct. Without the mask "something" re-enabled it on my system!) Second (belts and braces), get NetworkManager re-configured properly: sudo apt-get install --reinstall network-manager (I think this was the trigger that re-enabled systemd-resolved, but can't be sure). Third, fix NetworkManager if DNS names are still not resolved properly: dpkg -l dnsmasq-base (make sure its status is "ii" meaning properly installed) edit /etc/NetworkManager/NetworkManager.conf and make sure "dns=dnsmasq" is in the [Main] section. Reboot and confirm your NM connections work and DNS resolution is working properly. (/etc/resolv.conf should be a soft link to /var/run/NetworkManager/resolv.conf and "ps aux | grep dns" should confirm dnsmasq is running. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-lowlatency 4.10.8 Uname: Linux 4.10.0-19-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 16 11:28:13 2017 InstallationDate: Installed on 2016-06-04 (315 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:6417 Microdia Integrated Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Studio 1558 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-lowlatency root=UUID=5236cad2-f68b-4cf0-93d2-0f725e609514 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2017-04-14 (1 days ago) dmi.bios.date: 03/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0874P6 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd03/30/2011:svnDellInc.:pnStudio1558:pvrA12:rvnDellInc.:rn0874P6:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Studio 1558 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683094 Title: Upgrade conflict DNS broken between Network Manager and systemd- resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1683094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
Sorry to say this fix arrived much too late. The system affected is running xenial and doesn't experience these symptoms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630154] [NEW] Mouse unresponsive with menu in application title bar
Public bug reported: System Settings -> Appearance -> Behaviour Show the menus for a window -> in the window's title bar When the mouse hovers over the title bar, the application menu appears. However, left-clicking any of the top menu items does nothing. To be precise, the mouse pointer briefly disappears and reappears. After left clicking various parts of the individual menu item, or another item, the relevant drop-down sub-menu will appear and behave properly. Sometimes it helps to click the window title bar to the right of the application menu, and then click the "help" menu item as soon as it appears. After one of the sub-menus has appeared, moving the mouse left or right to the menu item that is really wanted will produce the correct sub-menu. There is no difference in sensitivity with Menu Visibility either setting: always displayed or mouse hovering. This behaviour is NOT observed when the application menu is displayed in the desktop menu bar. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: lvmetad is not active yet, using direct activation during sysinit /dev/mapper/lvmG4-xenial: clean, 320386/2949120 files, 2415013/11796480 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 4 17:29:11 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:677b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Caicos PRO [Radeon HD 7450] [1043:3027] MachineType: stem manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic root=/dev/mapper/lvmG4-xenial ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2002:bd08/28/2009:svnstemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: stem manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Oct 4 11:58:49 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 xserver.video_driver: radeon ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630154 Title: Mouse unresponsive with menu in application title bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1630154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571972] Re: systemd service not enabled on install
This bug applies to both shorewall and shorewall6. It is a known bug in the shorewall installer for debian. Proof: systemctl is-enabled shorewall (displays disabled) Circumvention: sudo systemctl enable shorewall The current package in the xenial repository is 5.0.4-1. The latest stable release of shorewall is 5.0.12. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571972 Title: systemd service not enabled on install To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1571972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581763] [NEW] Desktop installer does not detect existing raid0 array
Public bug reported: I have a machine which is succesfully running 32-bit 15.10 Desktop on several of raid0 arrays, containing swap, ext3, and lvm/ext3 file systems. I have released some space on one of the logical volumes, but not yet created a file system on it. I want to install 64-bit desktop into this free raid/lvm space so that I can dual boot the machine and migrate my existing applications and data to the new 16.04 system. When I boot the xenial live installer DVD it does not seem to detect the raid arrays. When I select the "something else" option for the installation target, it lists all the individual partitions but does not give me the option to activate my raid0 arrays, and so it does not detect the lvm volumes or the free space. The only choice is to over- write one of my existing and wanted partitions. When I run the live system without installing, mdadm is not in /sbin. In the past, I've used the "alternate installer" iso to activate raid support during installation, but I can't find an iso with this name on the current desktop downloads directory. I am unsure whether I can circumvent my problem by installing a no- options ubuntu server system and then manually installing the ubuntu- desktop meta-package over it. ** Affects: live-installer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581763 Title: Desktop installer does not detect existing raid0 array To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-installer/+bug/1581763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573351] Re: Unable to connect bluetooth keyboard with many different symptoms
bug creation dialogue did not save the correct package name - presumably I didn't do something properly. ** Package changed: usb-creator (Ubuntu) => bluez (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573351 Title: Unable to connect bluetooth keyboard with many different symptoms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1573351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573351] Re: Unable to connect bluetooth keyboard with many different symptoms
I'm puzzled about why this bug was attributed to usb-creator, when I specifically selected the bluez package when I opened it. I will try to update it, but if I don't have authority, will someone else do so soon? Also, it ought to be obvious my proposed solution is to upgrade xenial to use the 5.39 version, which is claimed by its developers to significantly less buggy than 5.37. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573351 Title: Unable to connect bluetooth keyboard with many different symptoms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1573351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573351] [NEW] Unable to connect bluetooth keyboard with many different symptoms
Public bug reported: I have been struggling to pair and connect the bluetooth docking station (keyboard and touchpad) to my Asus T300 Chi transformer notepad. I run xenial 16.04 64-bit on this system, built from the beta 2 distribution and fully up-to-date at the tiime of the release candidtae freeze. I've managed to work on the system with a usb keyboard and mouse, as well as the touch-sensitive screen. The latest version of bluez from the repository was 5.37.0ubuntu5. Running various compinations of actions under the gui and also bluetoothctl, I tried to analyse the failures with syslog and btmon. This was very frustrating because I eventually realised the software and hardware state could be corrupted, leading to unrepeatability in my tests. I still experienced what are probably timing bugs when I started from a power-off and reboot. The keyboard would sometimes fail to pair, sometimes say it was paired when it wasn't, sometimes pair and then get into a connected/disconnected loop. Sometimes it would connect, but the keys were dead. It was too confusing to list all the different failure symptoms. On the other hand, I had no problems connecting my android phone to the system over bluetooth, so this eliminated a lot of possibilities. Initially, I thought my symptoms were related to https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349, but I eventually concluded this was not the case. I tried repeating my tests with a bluetooth usb dongle, a different machine, and several different ubuntu releases, but didn't have a system old enough to test with something that others reported to be working. btmon traces showed the keyboard reports its capabilities included Secure Simple Pairing, but every pairing attempt which got far enough would require a pin, often without saying what it was! I currently have the original windows 10 image and so could boot it under grub2. Even though the keyboard had previously been paired to the latest windows driver, it failed to connect. I suspected the failed ubuntu attempts had replaced the pairing credentials because both operating systems use the same bluetooth adapters on the computer and keyboard. (At least this new experience meant I couldn't make the usual claim "it works with windows!) It took many attempts to get the keyboard paired. The windows driver doesn't use SSP either, because it requires its automatically- generated pin to be entered on the keyboard. I found I could force the old credentials to be deleted by powering-off the keyboard and tablet, then booting windows without the keyboard. Then hold the keyboard switch hard to the right while windows detected it, then initiate pairing and let the switch spring to its normal middle position. Windows would then display a new pin and I had to enter it on the keyboard fairly quickly, or the attempt would fail. I wrote down the pin in case I could use it with ubuntu (I later found I couldn't). I followed bluez upwards along its distribution path. Even debian unstable ships the 5.37 package, but the latest version from the developers is 5.39. 5.38 was a large bug fix release, and 5.39 fixes some more bugs. I did a manual build and install. I used bluetoothctl and had to start the default agent before starting the pairing process. Pairing failed and I wasn't prompted for the windows pin. I erased the windows pin on the keyboard and issued the pair command - bluez gave me a new pin and after typed it on the keyboard the pairing was successful. The info command showed it had used legacy pairing (like windows), rather than SSP. The keyboard connected and disconnected a coule of times, then stayed disconnected. I tried issuing the trust command and the device status changed to paired and trusted. I despondently type a few letters on the keyboard and was astonished when they appeared on the screen! bluetoothctl displayed the connected:on message. The keyboard is now working perfectly. The blue LED seldom comes on as I expected - it stays solidly blue with windows, but only flicks on briefly when reconnecting after inactivity. I can even use it to trigger a system resume from suspend state from the keyboard or touchpad. Obviously, grub2 does not support bluetooth or touchscreen devices, so ubuntu is my default boot system. I can only get to windows with a usb keyboard connected. ** Affects: usb-creator (Ubuntu) Importance: Undecided Status: New ** Tags: bluez legacy pairing xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573351 Title: Unable to connect bluetooth keyboard with many different symptoms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1573351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start
On 15/04/16 03:19, Laurent Bonnaud wrote: >> All tests produced the "not enough handles" message from bluetoothd. >> Is anyone successfully using bluetooth with these later ubuntu kernels? > > On both of my systems I get the "not enough handles" messages but I got BT to > work for both my use cases: > - using a BT mouse on a laptop > - streaming audio from my phone to my HTPC That is useful to know, Laurent. I am pleased to know it works somewhere! I successfully paired my android phone to the T300, so this shows the hardware and software is capable of recognising and using the "just works" agent for a Simple Simple Pairing exchange (i.e. without requiring user entry of a pin). I can't be sure, but I think this is what happened when I paired the keyboard with windows 10. Incidentally, I just tried connecting my wife's phone, which is newer but almost identical. It paired but would not connect. I will run some more btmon traces later today to look for significant differences. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10: bluetoothd reports "Not enough handles to register service" at start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start
I also true using an old bluetooth usb dongle. I used it on the asus T300, but that made no difference. I also tried it on my dell 1558 laptop, with 16.04 (64-bit) and 15.10 (32-bit with bluez 5.35). The 16.04 test was basically the same as on the asus. The 15.10 test was different in detail, but still showed the docking station briefly connecting, but disconnecting a second or so later. All tests produced the "not enough handles" message from bluetoothd. Is anyone successfully using bluetooth with these later ubuntu kernels? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10: bluetoothd reports "Not enough handles to register service" at start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start
Following a suggestion from jbmacbrodie to minimise the blueman device manager after pairing, I tried again. This time, I used the command-line bluetoothctl program as sudo: the "paired-devices" command showed the device was already paired from my previous session. "info [mac addr]" showed it was not legacy-paired and not currently connected. I flicked the switch on the docking unit (a bluetooth keyboard with touchpad) so it would try to establish a connection. I then issued the "connect [mac addr]", and bluetoothctl briefly showed it was connected and the blue LED on the keyboard changed from blinking, to solid on, then back to solid off in a matter of a few seconds. syslog showed: Apr 8 15:28:39 Muscat bluetoothd[610]: Can't get HIDP connection info Apr 8 15:28:40 Muscat kernel: [ 1066.735075] hid-generic 0005:0B05:8502.0004: unknown main item tag 0x0 Apr 8 15:28:40 Muscat kernel: [ 1066.735354] input: ASUS T300CHI DOCKING as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:0B05:8502.0004/input/input16 Apr 8 15:28:40 Muscat kernel: [ 1066.735950] hid-generic 0005:0B05:8502.0004: input,hidraw3: BLUETOOTH HID v0.01 Keyboard [ASUS T300CHI DOCKING] on 60:57:18:59:0a:64 Apr 8 15:28:40 Muscat bluetoothd[610]: No agent available for request type 0 Apr 8 15:28:40 Muscat bluetoothd[610]: device_request_pin: Operation not permitted I had just rebooted the latest (4.4.0-17-generic) kernel and bluetoothd logged the "not enough handles" message again when starting. I don't know whether this is a symptom of the kernel bug, or something completely different! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10: bluetoothd reports "Not enough handles to register service" at start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start
Following a suggestion from jbmacbrodie to minimise the blueman device manager after pairing, I tried again. This time, I used the command-line bluetoothctl program as sudo: the "paired-devices" command showed the device was already paired from my previous session. "info [mac addr]" showed it was not legacy-paired and not currently connected. I flicked the switch on the docking unit (a bluetooth keyboard with touchpad) so it would try to establish a connection. I then issued the "connect [mac addr]", and bluetoothctl briefly showed it was connected and the blue LED on the keyboard changed from blinking, to solid on, then back to solid off in a matter of a few seconds. syslog showed: Apr 8 15:28:39 Muscat bluetoothd[610]: Can't get HIDP connection info Apr 8 15:28:40 Muscat kernel: [ 1066.735075] hid-generic 0005:0B05:8502.0004: unknown main item tag 0x0 Apr 8 15:28:40 Muscat kernel: [ 1066.735354] input: ASUS T300CHI DOCKING as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:0B05:8502.0004/input/input16 Apr 8 15:28:40 Muscat kernel: [ 1066.735950] hid-generic 0005:0B05:8502.0004: input,hidraw3: BLUETOOTH HID v0.01 Keyboard [ASUS T300CHI DOCKING] on 60:57:18:59:0a:64 Apr 8 15:28:40 Muscat bluetoothd[610]: No agent available for request type 0 Apr 8 15:28:40 Muscat bluetoothd[610]: device_request_pin: Operation not permitted I had just rebooted the latest (4.4.0-17-generic) kernel and bluetoothd logged the "not enough handles" message again when starting. I don't know whether this is a symptom of the kernel bug, or something completely different! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10: bluetoothd reports "Not enough handles to register service" at start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start
Same messages for me with 16.04 beta2, running with bluez 5.37-0ubuntu5 on 4.4.0-15-generic amd64 kernel. Running on Asus T300 CHI notepad with bluetooth keyboard/touchpad docking unit. It pairs OK, but connection comes up briefly and then drops again. bluetoothctl log extract follows: [CHG] Device 08:62:66:DB:F3:AA Paired: yes Pairing successful [CHG] Device 08:62:66:DB:F3:AA Connected: no [CHG] Device 08:62:66:DB:F3:AA Class: 0x0005c0 [CHG] Device 08:62:66:DB:F3:AA Connected: yes [CHG] Device 08:62:66:DB:F3:AA Icon is nil -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10: bluetoothd reports "Not enough handles to register service" at start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557894] Re: Strange usb device format and failure to boot on UEFI system
Finally, I realised that the USB stick was probably getting "lost" at the same time as my USB keyboard. However, I didn't need to pop the stick because I could manually mount it under busybox. Unfortunately, I didn't know how to make casper restart once it had given up! Now for the good news - how I installed ubuntu 16.04 beta2 (only useful for stubborn people!)... First, I re-enabled the CSM (Compatibility Support Manager component of the UEFI BIOS) by accessing BIOS from windows (you really need to keep windows until ubuntu is properly installed!) I then booted my legacy- bios knoppix 7.0 USB system. I used gparted to create four new partitions on the solid state disk - I had previously shrunk the windows partiton using its disk manager. My new partitions were for linux-swap, / and /boot (both ext4), and a 2GB unformatted partition. I then used knoppix to DD the ubuntu live iso image onto the new unmounted unformatted partition. When I rebooted the machine to windows I found that I was able to restart using the "device" which was my live iso from its new SDD partition. The system BIOS (not sure whether the CSM or UEFI component was responsible) was happy to recognise the hybrid iso on the SDD, and process its contents. It apparently found the grub2 efi file in my partition, because I hadn't already copied it to /dev/sda1/EFI/BOOT/. The presence of a grub menu proved the BIOS had booted the efi "personality" of the live iso. I selected the "install ubuntu" menu option, and the installer started running. I told it to use the boot, root and swap partitions I had already prepared and installation ran OK. I crossed my fingers when I was prompted to restart the system, and was very relieved to find my new ubuntu system booted successfully. The wifi connection came up (no ethernet port on my machine) and I ran apt-get update and upgrade without a hitch. I then installed gparted to examine the disk - the three original partitions were intact (EFI, windows recovery and windows C:). I was very impressed to see that ubuntu had automatically mounted the /dev/sda1 EFI partition on its own /boot/efi/ path, and grub had been installed into the "real" EFI partition. The default grub installation had successfully created a directory structure on sda1 which allowed me to boot windows and the BIOS. I changed grub.cfg (on sda1) to not hide its menu and use a long timeout. I then confirmed I could use grub to boot windows, ubuntu (again!) and even the system BIOS menu. I disabled the CSM and rebooted to grub and then into ubuntu. Everything was working normally with minimal effort, so a lot of hard work from others has made the 16.04 installation process work brilliantly with EFI and co-existence with windows. The only hurdle is bypassing this problem of running the live iso from a usb stick. I still can't do that! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557894 Title: Strange usb device format and failure to boot on UEFI system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1557894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557894] Re: Strange usb device format and failure to boot on UEFI system
This has proved to be a very frustrating bug and I worry that less
knowledgeable and persistent users will encounter the same situation and
give ubuntu a bad name. After all, EFI is here to stay and we all want
ubuntu to used more widely with each new release. 16.04 is to be the
next LTS and my short experience with both betas has convinced me that
it is a huge improvement over 14.04.
The good news it that I have installed 16.04 beta2 on the Asus T300 chi
transformer notebook. I will write more about this later. The bad news
is that I found it impossible to install directly from a usb.
The internet is littered with dead-ends, bad advice and out-of-date
instructions when dealing with the initramfs message "unable to find a
medium containing a live file system"... and not just for ubuntu.
In my case (and perhaps many others), I found the message was issued by
the script casper, when ${livefs_root} has not been set by the function
mountroot(). This function calls find_livefs(), which is also in the
casper script. I even tried setting the casper kernel boot parameter
ignore_uuid in grub.cfg, but the message was still generated. I then
deleted the quiet boot option and changed splash to nosplash. Now I
could see the console log as it was generated.
My problem determination was made much more difficult by the fact that
busybox would not read from my keyboard (PS/2 into a USB dongle).
Eventually, I tried popping the keyboard dongle out and back into the
USB hub port - the log showed the device was recognised and then I could
enter commands to see what was going on!
Most importantly, the ubuntu live iso usb device was NOT mounted at the
time casper had given up looking for the live filesystem.squashfs. No
wonder it gave up!
I spent a long time messing around - trying different manufacturers usb
sticks, manually mounting the device on /cdrom, pre-unsquashing the live
system, and even trying to satisfy the unsquashed symlinks for
/initrd.img and /vmlinuz. Nothing worked because I was unable to find a
way to resume initialisation of the final stage of the bootstrap
process. (Perhaps someone more knowledgeable could tell me?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557894
Title:
Strange usb device format and failure to boot on UEFI system
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1557894/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557894] Re: Strange usb device format and failure to boot on UEFI system
More knowledge acquired... I used simple dd to create a usb from debian- live-8.3.0-amd64-gnome-desktop.iso. This image has NO EFI structure or files at all, so it can only boot in legacy bios mode. When the asus bios has CSM enabled this live image boots perfectly. I think the evidence is pointing to something wrong with the EFI content of the ubuntu iso. Even when it starts off with CSM being asked to boot the legacy content, the presence of the EFI stuff is confusing the bios later, probably when it is asked to boot the live linux kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557894 Title: Strange usb device format and failure to boot on UEFI system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1557894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557894] Re: Strange usb device format and failure to boot on UEFI system
I have discovered the "strange" device format of the image is a hybrid iso, and gparted simply does not recognise this as meaningful. I was able to mount the iso as follows: sudo mount -o loop ./image.iso iso-contents/ ... and then the mounted directory allows me read-only access to the file system within the image. As I said above, the Asus EFI CSM BIOS detects and executes the hybridiso's bootloader. However, something goes wrong further into the process. Perhaps this is because the hybrid iso's file system also contains efi files and their presence confuses the BIOS. I will continue to investigate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557894 Title: Strange usb device format and failure to boot on UEFI system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1557894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557894] Re: Strange usb device format and failure to boot on UEFI system
I forgot to say the initramfs message occurs when the external usb mouse and keyboard have become unresponsive, so I cannot use busybox to inspect the state of the system. I have no alternative except to power off the machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557894 Title: Strange usb device format and failure to boot on UEFI system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1557894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557894] [NEW] Strange usb device format and failure to boot on UEFI system
Public bug reported: I want to run 16.04 on a new ASUS T300 Chi transformer notebook, which is pre-installed with windows 10. I started by making a DVD iso from the beta distribution, then booted and installed it on a spare partition of my old Dell 1558 Studio laptop. The system runs fine in 64-bit mode, but the BIOS is non-EFI. I then applied the latest updates to the Dell HDD 16.04 system before running usb-creator. I've done this several times, always starting by DD-ing zeros over the first 200MB of the target 8mb usb stick. The creator reports successful completion, but gparted doesn't like the contents of the usb stick after the image has been created. The partition table has been changed from type=msdos to type=mac, and the sector size from 512 to 2048. The capacity changed from 7.7GB to 57GB! There are two partitions: sdb1 is called "Ubuntu Gnome 16.04 LTS, with an "unknown" file system type and a size of ONLY 4KB; 1.22GB unallocated; sdb2 is fat16 and its 2.31 MB extent is almost full. No flags are set on either partition. Whenever I interact with gparted it throws a pop-up that says "The driver descriptor says the physical blocksize is 2048, but linux says it is 512 - cancel or ignore". I am amazed to report this image boots successfully on my Dell with its "legacy" BIOS. The ubuntu live/install options page displays and it eventually boots the live system, which superficially seems to run OK. The ASUS uses American Megatrends UEFI BIOS, which I have updated to the latest version 207. I have enabled the CSM (Compatibility Support Module - legacy BIOS) and disabled both fast start and secure boot. It boots the usb stick in non-EFI mode as desired (proved by not getting the grub2 efi menu). The "man=keyboard" splash panel appears, then it drops to a tty login briefly before the new ubuntu "circling logo" appears. After several minutes, it drops back to a tty screen with the following: (initramfs) Unable to find a medium containing a live system. I also have a usb stick with knoppix 7.0 which successfully boots in 64-bit non-efi mode on both the Dell and the Asus, so I am reluctant to blame the Asus legacy bios at this stage. Why is gparted reporting such a strange format after creating the usb image? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: usb-creator-gtk 0.3.2 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 16 16:11:25 2016 InstallationDate: Installed on 2016-03-14 (2 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) SourcePackage: usb-creator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: usb-creator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557894 Title: Strange usb device format and failure to boot on UEFI system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1557894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
Just a personal update. I've been using a manually patched version of the i386 driver for several months, but I only use up to 0014-null-pointer-crash.patch. I currently have the trusty 3.13.0.-63.103-lowlatency kernel on a dell 1558 and the BCM4315. I haven't seen another null pointer crash since I applied the patch, but have suffered random loss of wifi synchronisation, sometimes after a day or so, but other times every hour or even less. I didn't expect to see a difference, but I thought it was worth saying that I successfully applied the just-released wily package bcmwl-kernel- source_6.30.223.248+bdcom-0ubuntu4.1_i386.deb to my trusty system. The build was clean (logged "using CFG80211 API") and the driver loads without a problem. I haven't been using it long enough to say whether it is better, but it is definitely no worse! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
Thanks for your helpful comment Christopher. However, I am inclined to believe the symptoms I've reported here are not connected to my original bug report (https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1360783). I continue to think my symptoms are either related to this current bug, or represent yet another bug. Given the fact that we are patching a version of bcmwl-kernel-source that has not yet been officially released for a production version of ubuntu, I will stay out of this discussion for the moment. If my symptoms prove to be relevant, then at least they are documented here (already) for the developers to consider. As a lower priority task, I will also set up a test vivid system and see what happens in my particular environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
I need advice on whether I should be opening a new bug, or is it OK to stay with this one? On further investigation, I have noticed three things: 1. The current trusty repository bcmwl-kernel-source 6.30.223.141+bdcom- 0ubuntu2 is used on my wife's laptop. This system is not experiencing null pointer crashes OR Scan_results errors. This evidence strongly suggests both problems were introduced with 6.30.223.248+bdcom-0ubuntu1. 2. On checking syslog carefully, the Scan_results errors are often associated with the system running slowly and [TTM] Out of kernel memory messages being logged. The victim is the ATI radeon drm driver, but I suspect the bcmwl scan errors are causing the driver to not release kernel memory it has used for its wlan scan. Usually, I have to reboot the system to restore normal performance. I have attached an appropriate syslog extract. (note: when searching for these display- related messages I hit very old bugs that were never explicitly resolved). 3. I turned wifi off 12 hours ago and have been running the system via its ethernet adapter (incidentally, also from Broadcom). Syslog doesn't contain ANY out of kernel memory errors and system performance is back to normal and stable. ** Attachment added: syslog extract showing kernel memory depletion https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4311752/+files/bcmwl-radeon-ttm-outOfKernelMemory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415880] Re: bcmwl-kernel source: fix for null pointer crash
I have been running 6.30.223.248+bdcom-0ubuntu1 on trusty 14.04.1 LTS for several weeks. I applied the patch suggested by Andre yesterday, and haven't seen any kernel crashes yet. However, I am still seeing occasional (once per hour approx) loss of connectivity. A typical syslog extract is below: Feb 2 23:47:12 bacchus wpa_supplicant[1287]: message repeated 25 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ] Feb 2 23:48:50 bacchus wpa_supplicant[1287]: wlan0: WPA: Group rekeying completed with 00:12:0e:54:e9:a4 [GTK=CCMP] Feb 2 23:49:12 bacchus wpa_supplicant[1287]: wlan0: CTRL-EVENT-SCAN-STARTED Feb 3 00:03:12 bacchus kernel: [ 3848.216125] ERROR @wl_notify_scan_status : wlan0 Scan_results error (-22) Feb 3 00:07:12 bacchus kernel: [ 4088.258526] ERROR @wl_notify_scan_status : wlan0 Scan_results error (-22) I have just checked the syslog and the error was also being logged prior to applying the patch. I wonder whether this error is relevant to this bug - sorry if it isn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: bcmwl-kernel source: fix for null pointer crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360783] Re: 14e4:4315 [Dell Studio 1558] Broadcom wifi crash in bcmwl-kernel-source cfg80211
Andre... thank you very much for letting me know about the patch. I have applied it because I have been suffering from occasional random loss of connectivity to my own wifi routers. I have not yet encountered another router that triggers the original crash that I reported in this particular bug, so I am unable to test it fully. However, I hope it fixes the loss of connection problems at home. I will report my experiences against your bug after a few days of testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360783 Title: 14e4:4315 [Dell Studio 1558] Broadcom wifi crash in bcmwl-kernel- source cfg80211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1360783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415262] [NEW] dtv-scan-tables wrong for Queensland Sunshine Coast
Public bug reported: There appear to have been a lot of changes to the Sunshine Coast Digital TV transmitters in this broadcast area over the last couple of years. The official status is that the reorganisation is now complete and stabilised. Apparently frequencies have been released to facilitate the roll out of 4G mobile, so all five of the DVB-T multiplexes have been assigned to very high frequencies. I have attached a patch file against a recent version taken from the debian unstable repository. (Apologies to Jonathon for not providing one against the original git head). ** Affects: dtv-scan-tables (Ubuntu) Importance: Undecided Status: New ** Patch added: patch to au-SunshineCoast https://bugs.launchpad.net/bugs/1415262/+attachment/4306899/+files/au-SunshineCoast-patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415262 Title: dtv-scan-tables wrong for Queensland Sunshine Coast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dtv-scan-tables/+bug/1415262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1360783] Re: 14e4:4315 [Dell Studio 1558] Broadcom wifi crash in bcmwl-kernel-source cfg80211
On 06/12/14 07:54, Christopher M. Penalver wrote: Brian Burch, without an offending router to test against to identify the root cause (which may not be a driver version issue as evident by it working with your five different routers) releasing an updated driver would be premature at this point. That was definitely not my intention... I have NO evidence whatsoever that the new driver would fix my problem, i.e. kernel crashes in certain unidentified kinds of wifi hotspots. However, I have good evidence that the new driver installs and runs OK on the 14.04 LTS 3.13.0-40-lowlatency kernel. My suggestion is that it would be good from many aspects (especially support) to accelerate testing so the new driver could be added to the 14.04 repository without making anything worse. The advantage would be to have the same driver on several releases to shake out any remaining bugs. If my bug happened to be fixed as a side-effect, that would be nice. However, the main issue would be the standardisation of the latest driver across current ubuntu releases. Regards, Brian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360783 Title: 14e4:4315 [Dell Studio 1558] Broadcom wifi crash in bcmwl-kernel- source cfg80211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1360783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360783] Re: 14e4:4315 [Dell Studio 1558] Broadcom wifi crash in bcmwl-kernel-source cfg80211
I haven't been lucky enough to find a wifi hotspot that triggers the crash yet. I decided to install bcmwl-kernel-source from the utopic repository, 6.30.223.248+bdcom-0ubuntu1. It installed on my 14.04 LTS lowlatency system without a problem, and is working fine on my home wifi network. I will use it for a couple of days and then install the new version on a notepad that runs 14.05 with the generic kernel. Even though I haven't been able to find a delinquent wifi router yet, it think the be -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360783 Title: 14e4:4315 [Dell Studio 1558] Broadcom wifi crash in bcmwl-kernel- source cfg80211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1360783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360783] Re: 14e4:4315 [Dell Studio 1558] Broadcom wifi crash in bcmwl-kernel-source cfg80211
oops! Even though I haven't been able to find a delinquent wifi router yet, it think the best overall approach will be to test the .248 driver and then release it on 14.10. Perhaps this new driver will resolve the problem... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360783 Title: 14e4:4315 [Dell Studio 1558] Broadcom wifi crash in bcmwl-kernel- source cfg80211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1360783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393280] [NEW] dtv-scan-tables wrong for Brisbane SBS and Channel31
Public bug reported: I could not tune the Australian SBS and 31 Digital channel groups for Brisbane using the latest /usr/share/dvb/dvb-t/au-Brisbane file dated 15 January 2014, shipped in package 0+git20140107.1850cf8-1. I used wscan to find out the best values and confirmed them with the relevant transmitter information for Mount Coot-tha. Once I changed the file, my Hauppauge PCTV-DTB2 found all the channels properly. I have downloaded the latest debian unstable source file and have attached a patch file against that version, which is still wrong (note the file format has changed and the patch works against the new format - only the two frequencies require updating). ** Affects: ubuntu Importance: Undecided Status: New ** Patch added: patch for au-Brisbane transmitter frequencies https://bugs.launchpad.net/bugs/1393280/+attachment/4262122/+files/au-Brisbane-patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393280 Title: dtv-scan-tables wrong for Brisbane SBS and Channel31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1393280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360783] Re: Broadcom wifi crash in bcmwl-kernel-source cfg80211
Thanks, Christopher... I hope the following helps! brian@bacchus:~$ lspci -vvnn | grep -A 11 Network 04:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01) Subsystem: Dell Wireless 1397 WLAN Mini-Card [1028:000c] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 17 Region 0: Memory at f050 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: wl 07:00.0 SD Host controller [0805]: Ricoh Co Ltd MMC/SD Host Controller [1180:e822] (rev 01) Subsystem: Dell Device [1028:0413] brian@bacchus:~$ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 brian@bacchus:~$ uname -a Linux bacchus 3.13.0-37-lowlatency #64-Ubuntu SMP PREEMPT Mon Sep 22 22:00:49 UTC 2014 i686 i686 i686 GNU/Linux brian@bacchus:~$ apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installed: 6.30.223.141+bdcom-0ubuntu2 Candidate: 6.30.223.141+bdcom-0ubuntu2 Version table: *** 6.30.223.141+bdcom-0ubuntu2 0 500 http://ubuntu.mirror.serversaustralia.com.au/ubuntu/ trusty/restricted i386 Packages 100 /var/lib/dpkg/status brian@bacchus:~$ sudo sudo dmidecode -s bios-version A12 brian@bacchus:~$ sudo dmidecode -s bios-release-date 03/30/2011 brian@bacchus:~$ sudo dmidecode -s baseboard-product-name 0874P6 brian@bacchus:~$ sudo dmidecode -s baseboard-manufacturer Dell Inc. brian@bacchus:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360783 Title: Broadcom wifi crash in bcmwl-kernel-source cfg80211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1360783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360783] Re: 14e4:4315 [Dell Studio 1558] Broadcom wifi crash in bcmwl-kernel-source cfg80211
Q1: Is this reproducible on your home WiFI network? I have 4 different home wifi routers (different hardware and firmware), and access to a 5th. It does not happen on any of them, which is a pity! Q2: Does b43 provide a WORKAROUND as outlined in... I regret not having seem that particular page before. Thanks, I will read it carefully in preparation for the next failure. Q3: Did this happen in a prior Ubuntu/wl version? I started using this driver version under ubuntu 13.10. I encountered the same external symptoms, but I had not done sufficient problem determination to know whether the same kernel crash was occurring. In other words, I can't be certain. The crash has certainly occurred with several different releases of the 3.13.0 low-latency kernel. Q4: Which WiFi hotspot would be most convenient for you to do testing on? None, I am sorry to say. All those I can be certain about are more than 10,000 miles away from me at the moment! However, I will look hard for one nearer - I will be travelling over the next few days, so I hope I can find one which is more convenient to test against. Q5: At the most convenient WiFi hotspot, could you please test the later version of wl in Utopic... Yes, but unfortunately I won't have time to download it before I leave. Thanks again, Christopher. I will let you know as soon as I have some new information. Brian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360783 Title: 14e4:4315 [Dell Studio 1558] Broadcom wifi crash in bcmwl-kernel- source cfg80211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1360783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360783] Re: Broadcom wifi crash in bcmwl-kernel-source cfg80211
I have just re-executed the command apport-collect 1360783 while the broadcom adapter was active, without sudo permission. It failed with a popup window titled Updating Problem Report and the text No additional information collected. Here is the console log: brian@bacchus:~$ apport-collect 1360783 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=dt1ZkgdmKbTwz5wW096Wallow_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Press any key to continue or wait (5) seconds... Waiting to hear from Launchpad about your decision... Created new window in existing browser session. Package bcmwl not installed and no hook available, ignoring brian@bacchus:~$ It doesn't look very helpful to me! In case you are wondering, here are the relevant package details: brian@bacchus:~$ dpkg -l | grep bcmwl ii bcmwl-kernel-source6.30.223.141+bdcom-0ubuntu2 i386 Broadcom 802.11 Linux STA wireless driver source brian@bacchus:~$ dpkg -l | grep apport ii apport 2.14.1-0ubuntu3.5 all automatically generate crash reports for debugging ii apport-gtk 2.14.1-0ubuntu3.5 all GTK+ frontend for the apport crash report system ii apport-symptoms0.20 all symptom scripts for apport ii python-apport 2.14.1-0ubuntu3.5 all Python library for Apport crash report handling ii python3-apport 2.14.1-0ubuntu3.5 all Python 3 library for Apport crash report handling brian@bacchus:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360783 Title: Broadcom wifi crash in bcmwl-kernel-source cfg80211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1360783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360783] Re: Broadcom wifi crash in bcmwl-kernel-source cfg80211
Sorry Chris, but your suggested command failed because it was looking for a package called bcmwl. The package installed, as quoted in my bug subject, is bcmwl-kernel-source. This is because it is installed as a dkms module that has to be compiled against the appropriate kernel headers. I don't know how to run apport-collect against this bug reference number, and yet make it collect from the valid ubuntu package name. Could you tell me, please? Thanks, Brian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360783 Title: Broadcom wifi crash in bcmwl-kernel-source cfg80211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1360783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1359477] Re: package openjdk-7-jdk 7u65-2.5.1-4ubuntu1~0.14.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/jvm/java-7-openjdk-i386/src.zip', which is also in package openjdk-7-sour
My initial workaround seemed to be good enough... sudo mv /usr/lib/jvm/java-1.7.0-openjdk-i386/src.zip /usr/lib/jvm/java-1.7.0-openjdk-i386/src.zip-oldSymlink sudo apt-get install --reinstall openjdk-7-source I notice that /usr/lib/jvm/openjdk-7/src.zip seems to have been updated, and that a new symlink was not created. I'm not sure (at this time) whether I should now rename the old symlink, or whether it is redundant. I hope this early information helps! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1359477 Title: package openjdk-7-jdk 7u65-2.5.1-4ubuntu1~0.14.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/jvm/java-7-openjdk-i386/src.zip', which is also in package openjdk-7-source 7u55-2.4.7-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1359477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360783] Re: Broadcom wifi crash in bcmwl-kernel-source cfg80211
brian@bacchus:~/scratch$ dpkg -l | grep bcmwl ii bcmwl-kernel-source6.30.223.141+bdcom-0ubuntu2 i386 Broadcom 802.11 Linux STA wireless driver source -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360783 Title: Broadcom wifi crash in bcmwl-kernel-source cfg80211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1360783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360783] [NEW] Broadcom wifi crash in bcmwl-kernel-source cfg80211
Public bug reported: lspci shows: Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) lsb_release: Ubuntu 14.04.1 LTS (actually UbuntuStudio) Linux version 3.13.0-34-lowlatency Dell Studio 1558 with Intel CPU in i386 mode and four CPUs. Most of the time wifi works perfectly. Occasionally, when using wifi hotspots away from home, the system never makes a connection. Usually I see similar stack traces in the syslog, but the attached extract is the only example I have to hand. The system is resuming after suspend, but I do not believe that aspect is relevant. I have seen similar crashes after powering on, and (to repeat myself) in more than one hot spot. I suspect there is an edge case in negotiating with some wifi routers that is not handled properly. (Perhaps I am prejudiced, but I get the feeling that the problem routers are in iPhone-friendly environments). ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Attachment added: Syslog extract including kernel stack trace https://bugs.launchpad.net/bugs/1360783/+attachment/4185818/+files/wifi-crash-westHants-syslog-extract -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360783 Title: Broadcom wifi crash in bcmwl-kernel-source cfg80211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1360783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360783] Re: Broadcom wifi crash in bcmwl-kernel-source cfg80211
I don't know how the package name was over-ridden by the last bug I had worked on! It has nothing to do with openjdk!! ** Package changed: openjdk-7 (Ubuntu) = bcmwl (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360783 Title: Broadcom wifi crash in bcmwl-kernel-source cfg80211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1360783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285312] Re: Setting up mdadm (3.2.5-5ubuntu3) freezes after calling grub1's update-grub from postinst
After manually updating to grub2 (the grub-pc package) and removing legacy grub, I installed the proposed mdadm on my development trusty system. I haven't looked at the SRU verification tests yet. I realise the cryptsetup warning is not directly related to mdadm, but sdb is the second disk in my soft raid array and I don't have ANY encrypted volumes. This would make me nervous about upgrading my production system! Here is the console log: brian@schizo:/etc/apt$ sudo apt-get install mdadm/trusty-proposed Reading package lists... Done Building dependency tree Reading state information... Done Selected version '3.2.5-5ubuntu4.1' (Ubuntu:14.04/trusty-proposed [i386]) for 'mdadm' The following packages will be upgraded: mdadm 1 to upgrade, 0 to newly install, 0 to remove and 95 not to upgrade. Need to get 362 kB of archives. After this operation, 1,024 B of additional disk space will be used. Get:1 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-proposed/main mdadm i386 3.2.5-5ubuntu4.1 [362 kB] Fetched 362 kB in 1s (258 kB/s) Preconfiguring packages ... (Reading database ... 340057 files and directories currently installed.) Preparing to unpack .../mdadm_3.2.5-5ubuntu4.1_i386.deb ... * Stopping MD monitoring service mdadm --monitor [ OK ] Unpacking mdadm (3.2.5-5ubuntu4.1) over (3.2.5-5ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for doc-base (0.10.5) ... Processing 6 changed doc-base files... Registering documents with scrollkeeper... Processing triggers for ureadahead (0.100.0-16) ... ureadahead will be reprofiled on next reboot Setting up mdadm (3.2.5-5ubuntu4.1) ... Removing any system startup links for /etc/init.d/mdadm-raid ... update-initramfs: deferring update (trigger activated) Generating grub configuration file ... File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30372: /usr/sbin/grub-probe File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30372: /usr/sbin/grub-probe File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30423: /usr/sbin/grub-probe File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30423: /usr/sbin/grub-probe File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30474: /usr/sbin/grub-probe File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30474: /usr/sbin/grub-probe File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30525: /usr/sbin/grub-probe File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30525: /usr/sbin/grub-probe File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30701: /usr/sbin/grub-probe File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30701: /usr/sbin/grub-probe Found linux image: /boot/vmlinuz-3.13.0-24-generic Found initrd image: /boot/initrd.img-3.13.0-24-generic Found linux image: /boot/vmlinuz-3.11.0-19-generic Found initrd image: /boot/initrd.img-3.11.0-19-generic File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 31336: /usr/sbin/grub-probe File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 31336: /usr/sbin/grub-probe Found memtest86+ image: /memtest86+.elf Found memtest86+ image: /memtest86+.bin File descriptor 3 (pipe:[112701]) leaked on lvs invocation. Parent PID 31926: /bin/sh done * Starting MD monitoring service mdadm --monitor [ OK ] Processing triggers for initramfs-tools (0.103ubuntu4) ... update-initramfs: Generating /boot/initrd.img-3.13.0-24-generic cryptsetup: WARNING: failed to detect canonical device of /dev/sda2 brian@schizo:/etc/apt$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285312 Title: Setting up mdadm (3.2.5-5ubuntu3) freezes after calling grub1's update-grub from postinst To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1285312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285312] Re: Setting up mdadm (3.2.5-5ubuntu3) freezes at Found kernel: when upgrading from Saucy to Trusty
Yes for me, but only because the step by step upgrades on this system over many years have never replaced it... brian@schizo:~$ dpkg -l | grep grub ii grub 0.97-29ubuntu66 i386 GRand Unified Bootloader (Legacy version) ii grub-common2.02~beta2-9 i386GRand Unified Bootloader (common files) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285312 Title: Setting up mdadm (3.2.5-5ubuntu3) freezes at Found kernel: when upgrading from Saucy to Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1285312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 563774] Re: Invalid EDID for Dell SP2309W in VGA mode
On 09/01/14 01:35, Christopher M. Penalver wrote: Brian Burch, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . The only machine I could test with normally runs headless, so it took a while to schedule some maintenance time - sorry for the delay. I booted the 14.04 iso from DVD (too big for a CD and the machine's BIOS would not boot from a USB stick). The Dell screen displayed the splash screen and normal desktop approx 1 inch shifted to the right, exactly as originally reported. I was disappointed, and was about to give up. Something made me think to perform the screen auto-adjust function... the image wiggled around for a moment, and then displayed PERFECTLY! That machine normally runs ubuntu 12.04 LTS, and has recently been updated with the latest fixes. I booted the production 12.04 system where the desktop was misaligned and deliberately set to a low resolution so the entire image would be visible. I changed the screen resolution settings to the optimal value and it was aligned perfectly because the screen had already adjusted and memorised this SVGA resolution alignment. I presume the quirk for my display was incorporated in a 12.04 repository update at some time in the past, but I had overlooked the notice and so continued using the sub-optimal resolution. Thank you for suggesting that I run this test. You can close the bug for 12.04, 14.04, and any other releases it might apply to. Regards, Brian If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p xserver-xorg-video-nouveau REPLACE-WITH-BUG-NUMBER Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided = Low ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Confirmed = Incomplete ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Assignee: Chris Halse Rogers (raof) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/563774 Title: Invalid EDID for Dell SP2309W in VGA mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/563774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156138] Re: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock']
I upgraded my dell laptop to 13.10 ubuntu-studio about 2 weeks ago, which uses kernel 3.11.0-15.8-lowlatency. I just assumed that dkms was building and using my locally-patched driver. I have just checked and discovered I was mistaken... it is using the distro package bcmwl-kernel-source version 6.30.223.141+bdcom- 0ubuntu1. I can see 0001-MODULE_LICENSE.patch still defines a Mixed/Proprietary License, so it seems someone has altered the GPL kernel source restrictions. My thanks to whoever did that! It has released quite a few users from having to maintain their own dkms source. As far as I am concerned, this bug can be marked as fixed in 13.10. Good news! Brian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156138 Title: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1156138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156138] Re: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock']
Thanks for your thoughts, Bernardo. I've lost and can't find the links any more, but I previously found Alberto Milone was communicating with the kernel devs about the problem where rcu_read_unlock_special is not useable, even though it is apparently defined in the low latency symbol table. I actually hacked a lot of the kernel source into my own bcmwl source, but this was my final sticking point. Given that Alberto knows what he is doing and I'm just feeling my way, anything I had to say would have just been duplication. This is a wider issue than just broadcom's proprietary driver. I also found someone with a similar problem compiling the ati video driver under the low latency kernel. There was also someone blogging about gpl hell and proprietary drivers. I think most linux users (including me) are completely unaware of the politics behind this issue. We bought our hardware and want to run linux - why deny us that? Do the linux devs want to drive us back to windoze Should I go back to the 3.5 kernel, which happily co-exists with these drivers, and then never upgrade? And anyway, what is so special about the low latency kernel - the generic supports the latest bcmwl driver without a murmer of disapproval! I don't think this is a case of a conspiracy, just the usual c#*k up alternative theory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156138 Title: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1156138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156138] Re: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock']
I've done a lot of work trying to get the patch to work, including trying to resolve the subsequent problem where the wl.ko module builds but fails to load because rcu_read_unlock_special cannot be used on the current 3.8.0-30-lowlatency kernel. This issue is reported in https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1154036. Exasperated after digging around and finding far more knowledgeable people than me were stumped, I gave up. I edited my local copy of 0001-MODULE_LICENSE.patch to replace the string Mixed/Proprietary with GPL. The broadcom wireless driver is now working on my system. I look forward to removing the kludge as soon as this bug is fixed properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156138 Title: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1156138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1207934] Re: Newest kernel on Precise or Saucy causes USB to take 5-min to mount
Agreed. Working nicely again under 3.8.0-30-generic. Not sure if it is relevant, but I noticed earlier releases that were taking a long time to mount my camera and several usb sticks were able to mount the file system properly for my android 4 phone. I had given up trying to get this feature to work last year, and got into the habit of using adb to transfer files. I was pleasantly surprised to see android working, although this coincided with the annoying 10 minute mounts for devices that had worked fine for ever! One of the suspicious syslog messages was mtp-probe: bus: 1, device: 2 was not an MTP device, but that message still appears on the new kernel. I wonder whether fixing android usb originally broke mounting of older device types? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207934 Title: Newest kernel on Precise or Saucy causes USB to take 5-min to mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1207934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156138] Re: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock']
I changed my mind after a trip away. When trying to use bcmwl_6.20.155 under the generic kernel, the system was very unreliable and often just froze. I noticed the 6.30.223.30 link you gave me was for the amd46 deb, so I found bcmwl-kernel-source_6.30.223.30+bdcom-0ubuntu3_i386.deb and installed that version (despite the worrying warning it would replace 6.20.155). I was very disappointed to see the install failed with the usual GPL-incompatible symbol __rcu_read_unblock. I rebooted to the generic kernel (not really necessary) and dkms status showed the new module had been added already. I ran a dkms install against only the generic kernel and that worked fine. After rebooting, the wifi is working, although I haven't been using it long enough to comment on its stability. I feel this is progress. Even though I haven't moved forward, I've learnt a lot and am now running the latest source. I think I will try making an 0010 patch file for the low latecy changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156138 Title: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1156138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092724] Re: xtables-addons-dkms 1.47.1-1: xtables-addons kernel module failed to build
Thanks for the info, jth. It is crazy for the repos associated with kernels 3.8.0 and above to still show xtables 1.47.1 as the latest version and available, when the package install scripts are explicitly written to fail their kernel version tests. Version 2.2 or above is the only xtables-addons which is compatible with these later kernels. The bzr source worked for me on two different systems, one with i386 kernels low-latency and generic, the other running a custom non-pae i386 kernel. However, I encountered a couple of issues along the way: 1. the common and dkms debs will not install and subsequently must be removed if the system does not already have the iptables-dev and dh- autoreconf packages installed. These ought to be specified in the deb pre-requisites. 2. the debs did not download and build the xt_geoip csv files automatically, so I had to run the command: sudo /usr/lib/xtables-addons/xt_geoip_dl 3. then the command: sudo /usr/lib/xtables-addons/xt_geoip_build -D /usr/share/xt_geoip *.csv .. failed until I set up my perl5 environment and installed the CPAN module Text::CSV_XS 4. finally, the build command failed until I created the target directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092724 Title: xtables-addons-dkms 1.47.1-1: xtables-addons kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1092724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156138] Re: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock']
Thanks Bernardo. Your link was basically the same as where I had already downloaded from. Never having worked with it before, I am struggling to rapidly understand the maintenance, packaging and build structures of ubuntu dkms. I failed to find a patch file of the correct name, but I can now see the content of what will become it within the bcmwl_6.30.223.30 +bdcom-0ubuntu3.diff file, so I have something to work with - even though I don't actually have the patch file used during the dkms install of the bcmwl module. bcmwl_6.20.155 running under my generic kernel is the only way I can use the wifi adapter at the moment. My low-latency and custom kernels are installed on the same system and share the same package. I don't want to risk breaking the only combination that currently works, and I can't see a safe and easy way to have both versions of bcmwl on the same system. I will stick with slow and painful source file comparisons for the moment - unless you tell me a quicker way... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156138 Title: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1156138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156138] Re: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock']
Bernardo - I apologise for confusing you with the author of the patch - please disregard my comment! I spent some time learning about the bcmwl patch referred to in #18 above. I tried a lot os things that frustratingly made no difference, but here is what counts as partial success:- 1. Backup the unpacked distro version of /usr/src/bcmwl-6.20.155.1+bdcom/patches/0006-add-support-for-linux-3.8.0.patch. 2. Move the new patch file to replace the original. A diff shows the patches have a lot in common, but also a lot of new conditional compile blocks that apply to the 3.8.0 kernels and alter the use of the gpl symbol. 3. sudo dkms status confirms bcmwl was already installed against my three kernels: generic, low-latency ans custom low-latency. 4. sudo dkms build bcmwl/6.20.155.1+bdcom -k 3.8.0-27-lowlatency and my custom kernel ran successfully (i.e. no failure due to invalid use of gpl symbol). 5. sudo dkms install bcmwl/6.20.155.1+bdcom -k 3.8.0-27-lowlatency passes the sanity check, installs wl.ko and rens depmod successfully. 6. /var/lib/dkms/bcmwl/kernel-3.8.0-27-lowlatency-i686/log/make.log shows the five compiles are ok, but the last stage issues the message WARNING: rcu_read_unlock_special [/var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/wl.ko] undefined! before creating the wl.ko module. I don't know whether this warning is important or not - perhaps the patch is not complete? Unfortunately, when I reboot the bcmwl driver does not load. I guess there is another step I need to make (update-initramfs perhaps?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156138 Title: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1156138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156138] Re: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock']
I don't know whether update-initramfs was necessary, but it certainly didn't do any harm! The low-latency dmesg now shows the wl and cfg80211 modules are being loaded, but there is a problem: [ 24.624284] wl: module license 'MIXED/Proprietary' taints kernel. [ 24.624290] Disabling lock debugging due to kernel taint [ 24.626241] wl: Unknown symbol rcu_read_unlock_special (err 0) The unlnown symbol is the same as in the warning I noticed in the dkms install log, so it is important after all... Also, once the system has booted lsmod does not show the wl module any more, and the eth1 interface does not exist. I will do some research on that symbol in the bcmwl patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156138 Title: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1156138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
