Installing the new package:
--
Подготовка за разпакетиране на
bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7~20.04.1_amd64.deb ...
Removing all DKMS Modules
Done.
Разпакетиране на bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7~20.04.1) над
*** This bug is a duplicate of bug 1872908 ***
https://bugs.launchpad.net/bugs/1872908
Hi @supernoob3000,
The discussion here is related to kernel version up to 5.8! In kernel 5.9 are
additional changes affecting the driver, which needs to be added additional
patch for. That's why presented
Isn't more pragmatic before considering changes introduced with kernel
5.9, a backport to Focal be commited/released in advance (the kernel
there is 5.8)? 類 There is a proposal presented in Bug #1910555 comment
21! 樂 This Bug is related to kernel 5.6. New package changes (new patch)
related to
Let's hope somebody managing the package from Canonical, will take care
for attached patch (actually backport) to be applied on Focal's fork. 爛
So, no future confusions - everything automatic update!
** Patch added:
"bcmwl_6.30.223.271+bdcom-0ubuntu5_6.30.223.271+bdcom-0ubuntu7~20.04.1.diff"
@skrapshak, Did you put the driver package in your current working directory in
advance?! 樂 Seems, not! The error message is expressive enough.
You can download the package here:
https://launchpad.net/ubuntu/+archive/primary/+files/bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb
and
Hi @faccig,
Have you been upgrading your 'bcmwl-kernel-source' package recently? Its
version (6.30.223.271+bdcom-0ubuntu1~1.3) looks pretty old! Anyway... even
upgraded, the last version in Focal repository is out of date. In this context,
your bug seems duplicate of Bug #1910555. Take a look
Hi @paulwil,
Your bug seems duplicate of Bug #1910555. Take a look there for workaround till
Canonical fix gets released. Just a obsolete function ioremap_nocache (and
one more thing) together with delayed new release of bcmwl-kernel-source (who
knows why), where new patch has added, dealing
Gub #1910555
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910607
Title:
package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to
install/upgrade: el subproceso instalado paquete
Hi @kosson,
Your bug seems duplicate of Bug #1910555. Take a look there for workaround till
Canonical fix gets released. Just a obsolete function ioremap_nocache (and
one more thing) together with delayed new release of bcmwl-kernel-source (who
knows why), where new patch has added, dealing
Hi @mrinjamul,
Your bug seems duplicate of Bug #1910555. Take a look there for workaround till
Canonical fix gets released. Your findings don't represent a bug in the Linux
kernel, definitely! The problem is missing patch in current bcmwl-kernel-source
release dealing with API change in
Hi @faccig,
Your bug seems duplicate of Bug #1910555. Take a look there for workaround till
Canonical fix gets released.
Hope this helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910995
This bug looks more like a duplicate of Bug #1910555
Take a look there for workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910875
Title:
Broadcom wireless driver failed to install with
Seems Canonical have solved this inconsistency, but forgot release update!
Kernel changes, discussed here, gets came up in version 5.6 of the kernel and
are represented in the last versions of bcmwl-kernel-source
(6.30.223.271+bdcom-0ubuntu7). The only difference between
@milkey, Did you see all patches for adaptation to appropriate previous kernel
changes? Broadcom haven't updated provided code for more than 10 years. If you
think that "looks like a simple case of warnings now being treated as errors",
just add one more patch to already existing set.
Good
Public bug reported:
Recently kernel was updated on Focal from 5.4 to 5.8. From that moment on WiFi
doesn't work anymore. After a try rebuild (reconfigure) the result is:
---
# dpkg-reconfigure bcmwl-kernel-source
Removing all DKMS Modules
Done.
** Tags added: focal
** Changed in: aptdaemon (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808079
Title:
Downloads view in update manager can't resize
Hi @ravikantcool, can you point me out what exactly is incomplete???!
Whenever gtk3widgets gets updated, I have to patch it again and again, every
time, so be possible works (correctly visualizes, more precisely). That's it!
What's not clear?! Just a simple line seems missing in the code. Take
Is there any reason why this bug is ignored from Canonical side? If there are
need some additional info, could somebody tell something. For Ubuntu 18.4
(Bionic) there is new aptdaemon revision (LP: #1831981 ->
1.1.1+bzr982-0ubuntu19.1), but the file
Public bug reported:
When there are new updates and update-manager goes to download corresponding
packages, download list can't follow main window resize (more precise in
vertical direction). This is inconvenient (and ugly) when there are many
packages and I want to see as much as possible
I'm using 18.04, everything up to date.
ecryptfs is used for home encryption. Everything seems to work fine, but error
messages (as already noted above) appears. Not to repeat everything already
said, additional note could be that the messages are not tagged where they
really comes from. It is
I don't know why this happens, but seems to be something broken by the
way and update didn't fix anything in my case. There are still 2 calls
to 'setgroups(0, NULL)', one for libpam-kwallet and another for
pam_kwallet5 after my user and group are already set. Of course, this
drops all
Hi @tj,
Yes, I initially have try logout/login (I think should be enough) - no result.
After that full reboot - same thing.
So, currently command 'id' give me result:
uid=1000(zdravko) gid=1000(zdravko) групи=1000(zdravko)
that's all.
I can't see in this thread more deep discussions about what
Hi everyone,
I have similar problems. Updating to libpam-kwallet packages (libpam-
kwallet-common, libpam-kwallet4 and libpam-kwallet5) to version
4:5.12.7-0ubuntu0.1 from proposed repository didn't solve anything for
me. Probably the problem solving is still in progress or may be never
started
Hi @Julian Andres Klode,
It seems I didn't read carefully Your additions to the bug description.
Especially the line:
"Now run do-release-upgrade --proposed and check that it does not do
that."
Thanks to @Brian Murray for the note.
So, if there is someone still running Ubuntu 17.04 and want to
Hi @Brian Murray,
As I already noted in comment #12, my release is successfully upgraded and
currently I can not reproduce same conditions. Sorry, but it seems that I can
not help in such a way. ...
I'm sure that there are more people that are still waiting for "convenient way"
and they can
Hi @Stephan van Ingen and all other impatient to wait for convenience (like me
:). As I already noted above (comment #12) You can download the available buggy
version (noted in same comment) and after that to correct and run it by hand.
It needs a little change only in file
*** This bug is a duplicate of bug 1744722 ***
https://bugs.launchpad.net/bugs/1744722
Hi @Matti Viljanen. Just follow the linked bug report #1744722 (if You
are still interested). There You can see actual workflow. Fix is ready
in fact and I'm sure that very soon user-friendly way will be
Finally I can confirm, that the @Jean-Baptiste Lallement's idea work...
I have download the buggy artful upgrader from
"http://archive.ubuntu.com/ubuntu/dists/artful-updates/main/dist-upgrader-all/current/artful.tar.gz;,
manually extract its content and apply proposed path to
In context of my previous post, sorry for wrong attachment I made early
(about DistUpgradeController.py). It is the local one and is irrelevant
to the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Jean-Baptiste Lallement I just a moment ago made a try upgrade but no any
difference. Probably it's need more time, Your 'fix' to bring up on the web.
Actual buggy code do not persist locally, but is downloaded from
I am not very familiar with the Python language (prefer C/C++). It seems file
versions we are using are little bit different (lines I suppose You mean, are
shifted little up). That's why I attach my version here.
I suppose the wrong value sits in 'entry.dist' field. With method
@Otto usually this can't lead to such issue. I'm not sure but probably
this is some back compatibility fix or something like.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744722
Title:
Unknown
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744722
Title:
Unknown bad source brings up during 'zesty' to 'artful' upgrade and It
break the process
To manage notifications about this
Sorry @Jean-Baptiste Lallement I see Your last post after my previous
post. New bug report is available here:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1744722
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
During update after release 'zesty' 'end of life' strange error appear:
E:The repository 'http://archive.ubuntu.com/ubuntu stable Release' does
not have a Release file.
This error prevent upgrade process. There is no entry like
'http://archive.ubuntu.com/ubuntu stable
I want to add something else which could be base point (at least in my private
case and probably not only). As could be seen from the sources list my install
is from 2014. Over the years I make upgrade after 'end of life' release few
times without any problems. Now is the first time I have such
@Jean-Baptiste Lallement. Point 2 in Your answer is actually false! At least in
my sources.list there is NOT entry like 'http://archive.ubuntu.com/ubuntu
stable Release' and NO any third party installer or packages are adding this.
If Your supposition is true, then during regular check for
Here is my sources list (as is now). Please, If You can find anything
wrong just note it. Could be useful for many people.
** Attachment added: "sources.list"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1743995/+attachment/5040959/+files/sources.list
** Changed in:
Probably same problem: https://bugs.launchpad.net/ubuntu/+source/ubuntu-
release-upgrader/+bug/1743995
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740767
Title:
after upgrading to 17.04 and,
** Tags added: upgrade zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743995
Title:
Upgrade 17.04 to 17.10 not possible
To manage notifications about this bug go to:
** Also affects: ubuntu-release-upgrader (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/1743995
Title:
Upgrade 17.04 to 17.10 not possible
To
When all hardware available on (or accessible from) the system is
directly supported (either as free software or from supplier support),
the clean install is good solution. Unfortunately, my case is not like
this. In my configuration exist build-in components with partial support
and also some of
The last reported errors are because 'zesty' support is out of date. This
should not be a problem by self (I think).
I can't still understand where initial problem (E:The repository
'http://archive.ubuntu.com/ubuntu stable Release' does not have a Release
file.) comes from! There is no such
43 matches
Mail list logo
