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
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.
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.
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
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.
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.
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
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
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
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
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
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
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)
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
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.
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 stable
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"
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
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
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+
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.
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
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.
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!)
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.
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?
--
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
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%
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
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
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
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
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
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.
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
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
** 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
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
** 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
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
** 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
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
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
** 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,
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
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
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
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
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
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
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
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
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
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
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
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
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.
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
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
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
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
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
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
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]
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 -
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
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
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
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
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
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
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
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
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:
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,
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
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
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
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
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
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+
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
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
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
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
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
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
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.
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
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
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
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
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
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
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
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
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
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
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
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
1 - 100 of 224 matches
Mail list logo
