[Bug 1872908] Re: bcmwl kernel module does not build with kernel version 5.6 or 5.8
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) над (6.30.223.271+bdcom-0ubuntu7) ... Инсталиране на bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7~20.04.1) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-41-generic Building for architecture x86_64 Building initial module for 5.8.0-41-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-41-generic/updates/dkms/ depmod... DKMS: install completed. update-initramfs: deferring update (trigger activated) Обработка на тригерите за initramfs-tools (0.136ubuntu6.3) ... update-initramfs: Generating /boot/initrd.img-5.8.0-41-generic -- Everything works. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872908 Title: bcmwl kernel module does not build with kernel version 5.6 or 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1872908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
*** 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 solution here works up to kernel 5.8 (i.e. in 5.6 to 5.8 interval). For kernel 5.9 and up, you have to add one more patch yourself or wait for such to be added. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel or later
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 recent kernel changes might (better) be a object of new "bug". Isn't it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872908 Title: bcmwl kernel module does not build with 5.6.0 kernel or later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1872908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
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" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+attachment/5455170/+files/bcmwl_6.30.223.271+bdcom-0ubuntu5_6.30.223.271+bdcom-0ubuntu7~20.04.1.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
@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 find a way to put it in your directory or point the place explicitly, not just by name (whatever is more convenient for you). If needed, download on another device and transfer on the target device using alternative link (Bluetooth or flash stick for example). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910890] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit s
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 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/1910890 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910618] Re: bcmwl 6.30.223.271+bdcom build fails with kernel 5.8.0-34/36 Ubuntu 20.04.1 LTS
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 with the changes. 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/1910618 Title: bcmwl 6.30.223.271+bdcom build fails with kernel 5.8.0-34/36 Ubuntu 20.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910607] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: el subproceso instalado paquete bcmwl-kernel-source script post-installation devolvió el código de
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 bcmwl-kernel-source script post-installation devolvió el código de salida de error 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910572] Re: Ugprading to 5.8.0-34-generic kernel broke wifi (BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03))
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 with the changes. 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/1910572 Title: Ugprading to 5.8.0-34-generic kernel broke wifi (BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910697] Re: incapability with broadcom wifi driver - failed at dkms build
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 kernel 5.6 and later (including yours 5.8). 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/1910697 Title: incapability with broadcom wifi driver - failed at dkms build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910995] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
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 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910875] Re: Broadcom wireless driver failed to install with code 10 on focal 20.04
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 code 10 on focal 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
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 6.30.223.271+bdcom-0ubuntu5 and 6.30.223.271+bdcom-0ubuntu7 is the patch dealing with corresponding changes (/usr/src/bcmwl-6.30.223.271+bdcom/patches/0028-add-support-for-linux-5.6.patch), the one I mentioned before that have to be added (seems already done). The actual bug here is newer kernel letting in mainstream (5.8 > 5.6), without corresponding driver package version. Final solution will be simple enough - just adding latest bcmwl-kernel-source to Focal repository. I just installed it and: --- #dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb (Четене на базата данни ... 547141 файла или папки в момента са инсталирани.) Подготовка за разпакетиране на bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Разпакетиране на bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) над (6.30.223.271+bdcom-0ubuntu5) ... Инсталиране на bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-60-generic 5.8.0-36-generic Building for architecture x86_64 Building initial module for 5.4.0-60-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-60-generic/updates/dkms/ depmod... DKMS: install completed. Building initial module for 5.8.0-36-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-36-generic/updates/dkms/ depmod. DKMS: install completed. update-initramfs: deferring update (trigger activated) Обработка на тригерите за initramfs-tools (0.136ubuntu6.3) ... update-initramfs: Generating /boot/initrd.img-5.8.0-36-generic --- ...everything works perfectly fine. Canonical should be careful to releases all drivers packages no later then kernel (at least in future)! PROBLEM SOLVED. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
@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 luck... to all of us! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910555] [NEW] Driver build error on kernel 5.8, but works on 5.4
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. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-59-generic 5.8.0-34-generic Building for architecture x86_64 Building initial module for 5.4.0-59-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-59-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 5.8.0-34-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. --- As could be seen, the build for 5.4 completes successfully (and works on same kernel), but for 5.8 fails. Seems something is going wrong with missing function declaration - function "ioremap_nocache", as could be seen in attached make.log. I'm guessing, driver code may need be updated according to the new kernel headers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 17:13:05 2021 InstallationDate: Installed on 2020-06-22 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Log for driver build on kernel 5.8" https://bugs.launchpad.net/bugs/1910555/+attachment/5450291/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808079] Re: Downloads view in update manager can't resize properly
** 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 properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1808079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808079] Re: Downloads view in update manager can't resize properly
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 a look on the patch provided. Without the line, packages list size almost freezes. It's the same on both 18.04 and 20.04. I'm getting curious, am I the only experience this? 類 On fresh installed 20.04 keeps the same! If something else is needed, point out, please. 樂 -- 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 properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1808079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808079] Re: Downloads view in update manager can't resize properly
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 /usr/lib/python3/dist-packages/aptdaemon/gtk3widgets.py in the package python3-aptdaemon.gtk3widgets is not even touched. Why? Updated package just replace the fix (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/1808079 Title: Downloads view in update manager can't resize properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1808079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808079] [NEW] Downloads view in update manager can't resize properly
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 (especially when there are packages from different repositories). I made a little investigation and have found that the issue comes from AptDetailsExpander class in /usr/lib/python3/dist-packages/aptdaemon/gtk3widgets.py. There are 2 possible views: AptDownloadsView in ScrolledWindow and AptTerminal. AptTerminal seems to work fine, but the other view - no. More deep look shows that AptTerminal initialization calls set_vexpand(True), ScrolledWindow don't have such call! Adding such call for ScrolledWindow initialization fixes the issue for me. It's good idea this to be fixed in ubuntu repositories. Example patch is also here (at least as starting point). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3-aptdaemon.gtk3widgets 1.1.1+bzr982-0ubuntu19 [modified: usr/lib/python3/dist-packages/aptdaemon/gtk3widgets.py] ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: KDE Date: Wed Dec 12 03:55:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-12 (1613 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: aptdaemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: aptdaemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Patch added: "Add vertical resize ability." https://bugs.launchpad.net/bugs/1808079/+attachment/5221512/+files/gtk3widgets.patch -- 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 properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1808079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
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 a good practice (at least) everything in the system log to be explicitly clear where it comes from (as in most cases). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
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 supplementary groups. Maybe I miss something. The only workaround is commenting out both libraries in lightdm config. But this is only some workaround, no final fix! Would be fine needed changes to be made in corresponding modules and after that... everything done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
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 is going on. What is the actual reason. I take a look on the link in Your post #14. There is not clear description, again. Only strange standard error stream descriptor close is pointed as a reason. There are also other possible 'gaps' (not pointed there) - relying that buffer sized to length of c-string can safely keep all string (together with the terminator!, which will be there as result of 'strcpy()'). But this doesn't mater. Do You think that pointed there is enough for fixing the trouble? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
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 (officially). Here I want to ask somebody from Canonical to assign this bug! So, final solution (official) to be available soon (on regular bionic-update). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744722] Re: Unknown bad source brings up during 'zesty' to 'artful' upgrade and It break the process
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 upgrade to 17.10, can open a terminal window and run the command: do-release-upgrade --proposed Just to be clear. 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744722] Re: Unknown bad source brings up during 'zesty' to 'artful' upgrade and It break the process
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 help.
I am not sure, but here could be some test issue! Are You sure that in case of
'end of life' release, switching to 'proposed' could be consistent? ('end of
life' release repositories are unavailable)
The important thing is the archived tarball, so any such change could be
irrelevant to the actual test target! So, probably preliminary beta testing is
meaningless here. Actual test will happen in the final release, where is the
only case with same test condition. (any other is unreliable for particular
bug, I think)
--
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744722/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744722] Re: Unknown bad source brings up during 'zesty' to 'artful' upgrade and It break the process
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 'DistUpgradeController.py'. One possibility is to prepend lines from 733 to 748 (inclusive) with 4 spaces for every one. I used this approach and can confirm - it works. Another possibility is to insert proposed by @Julian Andres Klode 2 lines just before line 733. I suppose this also work, but I have not checked it. Third possibility is to download fixed version of the archived tarball which I provide here. That is exact files I used for the upgrade. I use in the proposed tarball the first correction variant (You don't have to fix anything). Does not matter what variant You choose, finally You should have a directory (created earlier with name of Your choice) where the unpacked and fixed files sits. It is time to open a terminal window. Change Your current working directory with that (created early) where sits prepared files. cd place/of/prepared/files !!!Note - It is important to be in exactly this directory! Otherwise incorrect library will be used. There is file named 'artful'. This file represent actual upgrade application. You should run it in super user context with correct parameters. Something like: sudo ./artful --mode=server --frontend=DistUpgradeViewText After entering Your password (need for 'sudo'), actual upgrade process will start (hopefully without issues). During upgrade, additional questions, related to upgrade process, can be set by application (in fact same like in graphical interface). Just answer, as appropriate, according to Your opinion. That's all. I hope I have helped. ** Attachment added: "workaround.tar.gz" https://bugs.launchpad.net/ubuntu/artful/+source/ubuntu-release-upgrader/+bug/1744722/+attachment/5048855/+files/workaround.tar.gz -- 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743995] Re: Upgrade 17.04 to 17.10 not possible
*** 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 available (with just push 'upgrade' in update manager as usual). -- 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: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1743995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744722] Re: Unknown bad source brings up during 'zesty' to 'artful' upgrade and It break the process
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 "DistUpgradeController.py". After that everything is done and I already have Ubuntu Artful (17.10) upgraded and working. At time of this post writing, upgrader version (timed 2017-10-31 17:48) is still the buggy one. It's time the path to be applied in "artful.tar.gz", so automatic upgrade to be possible through update manager (not by hand, like me, at least for other people). @Jean-Baptiste Lallement THANKS FOR YOUR WORK! -- 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744722] Re: Unknown bad source brings up during 'zesty' to 'artful' upgrade and It break the process
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. 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744722] Re: Unknown bad source brings up during 'zesty' to 'artful' upgrade and It break the process
@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 "http://archive.ubuntu.com/ubuntu/dists/artful-updates/main/dist-upgrader-all/current/artful.tar.gz;. Actual buggy code is not the local one, but is downloaded from "http://archive.ubuntu.com/ubuntu/dists/artful-updates/main/dist-upgrader-all/current/artful.tar.gz;. What time You think will be need? -- 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744722] Re: Unknown bad source brings up during 'zesty' to 'artful' upgrade and It break the process
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 "self.sources.add(entry.type, uri, entry.dist, entry.comps, comment)", erroneous value goes to take effect. Is it possible to insert one line just before noted method call and there to set correct value (just temporary as workaround)? Something like 'entry.dist = "artful"'? Can I rely that if this don't help me, at least will not disturb current installation? ** Attachment added: "DistUpgradeController.py" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744722/+attachment/5041145/+files/DistUpgradeController.py -- 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744722] Re: Unknown bad source brings up during 'zesty' to 'artful' upgrade and It break the process
@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 bad source brings up during 'zesty' to 'artful' upgrade and It break the process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744722] Re: Unknown bad source brings up during 'zesty' to 'artful' upgrade and It break the process
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 bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743995] Re: Upgrade 17.04 to 17.10 not possible
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 Ubuntu. https://bugs.launchpad.net/bugs/1743995 Title: Upgrade 17.04 to 17.10 not possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1743995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744722] [NEW] Unknown bad source brings up during 'zesty' to 'artful' upgrade and It break the process
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 Release' in my 'sources.list'. I have no idea where this entry comes from. During regular packages update try, only appears error messages directly related to 'end of life' release state. No error like above. I am not sure, but it seems like 'http://archive.ubuntu.com/ubuntu stable Release' is wrongly formatted and have no idea where this comes from as all. Here is my sources list (as is now). 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 issue. Thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubuntu-release-upgrader-core 1:17.04.10 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Mon Jan 22 15:56:24 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-12 (1289 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to zesty on 2018-01-20 (2 days ago) VarLogDistupgradeAptlog: Log time: 2018-01-20 03:20:51.814404 Log time: 2018-01-20 03:20:56.946483 Log time: 2018-01-20 03:21:25.049488 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful dist-upgrade third-party-packages zesty ** Attachment added: "sources.list" https://bugs.launchpad.net/bugs/1744722/+attachment/5041003/+files/sources.list -- 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743995] Re: Upgrade 17.04 to 17.10 not possible
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 issue. Should be some reason. @Jean-Baptiste Lallement Please Help me find this reason! What goes wrong? -- 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: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1743995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743995] Re: Upgrade 17.04 to 17.10 not possible
@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 updates, equivalent error message will bring up (together with messages related to end of life release). Such message does not appear! Do not be angry when someone goes wrong because of missed knowledge the interconnections between the packets, even when it has inadvertently raised the tone. I apologize on behalf of @Otto. Please be more careful with the final conclusion! -- 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: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1743995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743995] Re: Upgrade 17.04 to 17.10 not possible
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: ubuntu-release-upgrader (Ubuntu) Status: Invalid => 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1743995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740767] Re: after upgrading to 17.04 and, maybe, running out of disk space, a further upgrade fails
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, maybe, running out of disk space, a further upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1740767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743995] Re: Upgrade 17.04 to 17.10 not possible
** 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743995] Re: Upgrade 17.04 to 17.10 not possible
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743995] Re: Upgrade 17.04 to 17.10 not possible
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 my peripheral devices are without or buggy support. In
many cases additional components and/or additional configurations are
needed after install (done by hand). I don't want to repeat everything
again (which is error prone). My current settings (and installed
components) work well and I will try to keep this untouched, so clean
install will be the 'extreme' thing (the last one) I will do. I rely
that upgrade script fix ('/usr/bin/do-release-upgrade' - python script
and/or related data) will be much simpler thing to do with some help
here (probably one or few lines to be fixed).
Release file http://us.archive.ubuntu.com/ubuntu/dists/artful/Release is the
one needed for the new release (one from all). The error message show that
during upgrade (during prepare in fact) script rely to discover Release file in
place like 'http://archive.ubuntu.com/ubuntu/dists/stable/'. Such place does
not exist either on expected domain or on 'us.archive.ubuntu.com'. I am not
sure, but it seems like 'http://archive.ubuntu.com/ubuntu stable Release' is
wrongly formatted.
If someone have more experience - Please Help here!
--
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743995/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743995] Re: Upgrade 17.04 to 17.10 not possible
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 entry in my 'sources.list'. Probably this is some bug in distribution upgrade script, which seems add this. Such entry does not exist in repository and everything breaks, when script try to check it. -- 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
