[Bug 1847927] Re: Upgrading of 20191010 installed on ZFS will lead to "device-mapper: reload ioctl on osprober-linux-sda6 failed: Device or resource busy" and then to auto-removal of all zfs packages
Yes, just tested 20191014 and it seems okay. The reported things in this bug seems to be solved. Only thing remaining now: sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: vmlinuz-5.3.0-18-generic in rpool/ROOT/ubuntu_ylgjtz Found initrd image: initrd.img-5.3.0-18-generic in rpool/ROOT/ubuntu_ylgjtz Found memtest86+ image: /BOOT/ubuntu_ylgjtz@/memtest86+.elf Found memtest86+ image: /BOOT/ubuntu_ylgjtz@/memtest86+.bin device-mapper: reload ioctl on osprober-linux-sda6 failed: Enhet eller resurs upptagen Command failed. done but guess that is another bug and issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847927 Title: Upgrading of 20191010 installed on ZFS will lead to "device-mapper: reload ioctl on osprober-linux-sda6 failed: Device or resource busy" and then to auto-removal of all zfs packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847927] Re: Upgrading of 20191010 installed on ZFS will lead to "device-mapper: reload ioctl on osprober-linux-sda6 failed: Device or resource busy" and then to auto-removal of all zfs packages
I installed the 20191011 iso in a virtualbox. I used the zfs option. At installation. After installation system comes up fine. But as others here say it displays: janw@janw-VirtualBox:~$ sudo apt update Bra:1 http://se.archive.ubuntu.com/ubuntu eoan InRelease Bra:2 http://se.archive.ubuntu.com/ubuntu eoan-updates InRelease Bra:3 http://se.archive.ubuntu.com/ubuntu eoan-backports InRelease Bra:4 http://se.archive.ubuntu.com/ubuntu eoan-proposed InRelease Bra:5 http://security.ubuntu.com/ubuntu eoan-security InRelease Läser paketlistor… Färdig Bygger beroendeträd Läser tillståndsinformation… Färdig Alla paket är uppdaterade. janw@janw-VirtualBox:~$ sudo apt upgrade Läser paketlistor… Färdig Bygger beroendeträd Läser tillståndsinformation… Färdig Beräknar uppgradering… Färdig Följande paket har installerats automatiskt och är inte längre nödvändiga: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-initramfs zfs-zed zfsutils-linux Använd ”sudo apt autoremove” för att ta bort dem. 0 att uppgradera, 0 att nyinstallera, 0 att ta bort och 0 att inte uppgradera. apt update says all packages are installed. But nevertheless apt upgrade want me to run a destructive apt autoremove which will remove all zfs packages and after that break the booting of the system completely. I also tested the image from 20191012. That image does not boot after installation in the virtualbox.It gives a prompt initramfs> saying that it has problems finding the root partition. I also recognized during installation time that the image from 20191011 did some grub and kernel stuff at the end of installation which i could not see that the image from 20191012 did. Also a popup came during the installation talking about ext4 file systems, which is weird since I chose the zfs installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847927 Title: Upgrading of 20191010 installed on ZFS will lead to "device-mapper: reload ioctl on osprober-linux-sda6 failed: Device or resource busy" and then to auto-removal of all zfs packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826159] Re: gsd-print-notifications assert failure: free(): invalid pointer
I actually succeeded in getting this dump again. From the gnome settings up in the right corner, choose Test print. The printout went to the printer options and made a test print from the button in the left corner of the windows. That crash appeared in /var/crash despite it looks like everything works..This time I also got another crash at the same time: ** Attachment added: "_usr_bin_gnome-control-center.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1826159/+attachment/5258789/+files/_usr_bin_gnome-control-center.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826159 Title: gsd-print-notifications assert failure: free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1826159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826159] Re: gsd-print-notifications assert failure: free(): invalid pointer
For the moment I do not seem to be able to reproduce this. So I guess it happened when I tried to send the report bug thing in the popup since that popup came because of another crash: _usr_lib_x86_64-linux- gnu_cups-pk-helper-mechanism.125.crash. But since that failed I edited the crashdb conf file. So it CAN be that this doesnt happen anymore. But very uncertain That other crash seems to happen every time pressing adding printers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826159 Title: gsd-print-notifications assert failure: free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1826159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1
Tested comment #12. Yes, it works! And it displays Lightning 6.2.2.1. I add it as attachment ** Attachment added: "lightning-6.2.2.1.xpi" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+attachment/5201828/+files/lightning-6.2.2.1.xpi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797945 Title: Lightning incompatible with Thunderbird 60.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1
I update myself: I used #7 and used the swedish localization of instead. So now it says "Händelser och uppgifter" in the menu, which is correct Swedish. So 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/1797945 Title: Lightning incompatible with Thunderbird 60.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1
Solution in #6 worked for me. So thanks piraten-kris. I use swedish localization of thunderbird so it is not perfect since "Termine und Aufgaben" in the menu is definitively not Swedish but German. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797945 Title: Lightning incompatible with Thunderbird 60.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774131] Re: update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed'
I tested the tar-file and it looks like it is working without crashes. Looking forward to getting it into the repositories soon. I am running 18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774131 Title: update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1774131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774131] Re: update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed'
forgot to say i tested the update-manager-18.04.11.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774131 Title: update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1774131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774131] Re: update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed'
I agree with Brian Murray. I am running ubuntu 18.04 and have this crash all the time now. I did not see it before I switched to nvidia 390 drivers on this machine. But can not say for sure, if this happened at the same time doing the switch. ProblemType: Crash CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 5 08:47:05 2018 ExecutablePath: /usr/bin/update-manager ExecutableTimestamp: 1527516792 InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/bin/update-manager ProcCwd: /export/home/janw ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/tcsh ProcMaps: 0040-007c1000 r-xp 08:08 20978791 /usr/bin/python3.6 009c-009c1000 r--p 003c 08:08 20978791 /usr/bin/python3.6 009c1000-00a5d000 rw-p 003c1000 08:08 20978791 /usr/bin/python3.6 00a5d000-00a8f000 rw-p 00:00 0 023f9000-031c rw-p 00:00 0 [heap] 7f602000-7f602004b000 rw-p 00:00 0 7f602004b000-7f602400 ---p 00:00 0 7f602800-7f6028021000 rw-p 00:00 0 7f6028021000-7f602c00 ---p 00:00 0 7f602c00-7f602c021000 rw-p 00:00 0 7f602c021000-7f603000 ---p 00:00 0 7f6030394000-7f6030413000 r-xp 08:08 20972927 /usr/lib/x86_64-linux-gnu/libgmp.so.10.3.2 7f6030413000-7f6030613000 ---p 0007f000 08:08 20972927 /usr/lib/x86_64-linux-gnu/libgmp.so.10.3.2 7f6030613000-7f6030614000 r--p 0007f000 08:08 20972927 /usr/lib/x86_64-linux-gnu/libgmp.so.10.3.2 7f6030614000-7f6030615000 rw-p 0008 08:08 20972927 /usr/lib/x86_64-linux-gnu/libgmp.so.10.3.2 7f6030615000-7f6030648000 r-xp 08:08 20978824 /usr/lib/x86_64-linux-gnu/libhogweed.so.4.4 7f6030648000-7f6030847000 ---p 00033000 08:08 20978824 /usr/lib/x86_64-linux-gnu/libhogweed.so.4.4 7f6030847000-7f6030848000 r--p 00032000 08:08 20978824 /usr/lib/x86_64-linux-gnu/libhogweed.so.4.4 7f6030848000-7f6030849000 rw-p 00033000 08:08 20978824 /usr/lib/x86_64-linux-gnu/libhogweed.so.4.4 7f6030849000-7f603087d000 r-xp 08:08 20974610 /usr/lib/x86_64-linux-gnu/libnettle.so.6.4 7f603087d000-7f6030a7c000 ---p 00034000 08:08 20974610 /usr/lib/x86_64-linux-gnu/libnettle.so.6.4 7f6030a7c000-7f6030a7e000 r--p 00033000 08:08 20974610 /usr/lib/x86_64-linux-gnu/libnettle.so.6.4 7f6030a7e000-7f6030a7f000 rw-p 00035000 08:08 20974610 /usr/lib/x86_64-linux-gnu/libnettle.so.6.4 7f6030a7f000-7f6030a9 r-xp 08:08 20978826 /usr/lib/x86_64-linux-gnu/libtasn1.so.6.5.5 7f6030a9-7f6030c9 ---p 00011000 08:08 20978826 /usr/lib/x86_64-linux-gnu/libtasn1.so.6.5.5 7f6030c9-7f6030c91000 r--p 00011000 08:08 20978826 /usr/lib/x86_64-linux-gnu/libtasn1.so.6.5.5 7f6030c91000-7f6030c92000 rw-p 00012000 08:08 20978826 /usr/lib/x86_64-linux-gnu/libtasn1.so.6.5.5 7f6030c92000-7f6030e0c000 r-xp 08:08 20971768 /usr/lib/x86_64-linux-gnu/libunistring.so.2.1.0 7f6030e0c000-7f603100c000 ---p 0017a000 08:08 20971768 /usr/lib/x86_64-linux-gnu/libunistring.so.2.1.0 7f603100c000-7f603100f000 r--p 0017a000 08:08 20971768 /usr/lib/x86_64-linux-gnu/libunistring.so.2.1.0 7f603100f000-7f603101 rw-p 0017d000 08:08 20971768 /usr/lib/x86_64-linux-gnu/libunistring.so.2.1.0 7f603101-7f603102c000 r-xp 08:08 20971771 /usr/lib/x86_64-linux-gnu/libidn2.so.0.3.3 7f603102c000-7f603122b000 ---p 0001c000 08:08 20971771 /usr/lib/x86_64-linux-gnu/libidn2.so.0.3.3 7f603122b000-7f603122c000 r--p 0001b000 08:08 20971771 /usr/lib/x86_64-linux-gnu/libidn2.so.0.3.3 7f603122c000-7f603122d000 rw-p 0001c000 08:08 20971771 /usr/lib/x86_64-linux-gnu/libidn2.so.0.3.3 7f603122d000-7f6031347000 r-xp 08:08 20978832 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.3.0 7f6031347000-7f6031547000 ---p 0011a000 08:08 20978832 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.3.0 7f6031547000-7f6031551000 r--p 0011a000 08:08 20978832 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.3.0 7f6031551000-7f603155b000 rw-p 00124000 08:08 20978832 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.3.0 7f603155b000-7f603155c000 rw-p 00:00 0 7f603155c000-7f603155d000 ---p 00:00 0 7f603155d000-7f6031d9d000 rw-p 00:00 0 7f6031eb9000-7f6031f39000 rw-p 00:00 0 7f6031f39000-7f603209 r-xp 08:08 20978838
[Bug 1752053] Re: nvidia-390 fails to boot graphical display
I just tested the thing in #123 and I can only conclude: i am writing this note in 18.04 with nvidia-396 drivers on a Lenovo Y720. So I can only agree to what Thijs says. This sounds like a timing problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751005] Re: libreoffice cannot open a document not within $HOME
actually to avoid all of this: sudo add-apt-repository ppa:libreoffice/ppa sudo apt-get update sudo apt-get upgrade libreoffice starts without any tweaks and you are running the latest and greatest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751005] Re: libreoffice cannot open a document not within $HOME
setup is actually like this: user data is on an extra disk. that disk is mounted in fstab UUID=7707da2d-a878-40db-9311-f53ed74c821f /export ext4 defaults 0 1 then soft links for /home/janw to /export/home/janw is done. yes that is not standard i know.. but it makes reinstallations of OS much easier..with user data intact -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751005] Re: libreoffice cannot open a document not within $HOME
think i understand now. i guess what the apparmor_parser command does is to temporarily disable the profiles for libreoffice. and disable it permanently does not sound like a good idea. i guess. so: i guess the solution is to get a new version of libreoffice. right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751005] Re: libreoffice cannot open a document not within $HOME
as you said: this is temporary. how do i make it permanent? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751005] Re: libreoffice cannot open a document not within $HOME
okay. looks promising. i did this: sudo ppa-purge ppa:libreoffice/ppa. now libreoffice 5 installed again and gives the error. sudo apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.program.* libreoffice starts up and seems to be working.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751005] Re: libreoffice cannot open a document not within $HOME
i have to downgrade libreoffice first i guess.have no installation left with libreoffice 5 for the moment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751005] Re: libreoffice cannot open a document not within $HOME
olivier: i read your answer and is a bit confused. why does upgrading to libreoffice 6 not suffer from this problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751005] Re: libreoffice cannot open a document not within $HOME
I get the problem with system complaining about permissions on .config/libreoffice/4 since latest libreoffice upgrade on ubuntu 17.10. This problem has arrived on 3 installs up to now. Only solution I have found is to add the ppa on libreoffice and upgrade it to the latest libreoffice 6. Then it starts without any problems. Which proves to me that this is NOT a correct error description from libreoffice. The problem is not about permissions at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692175] Re: package grub-efi-amd64 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Adding a ; solved problem for me. Thanks guys -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692175 Title: package grub-efi-amd64 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1692175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692175] Re: package grub-efi-amd64 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
i also confirm this bug. it happens since morning 2017-05-20 when doing an apt upgrade. did not happen 2017-05-19. On 16.04LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692175 Title: package grub-efi-amd64 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1692175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
Just to be complete. Also this packages were updated: ii libnm-util2 0.9.8.8-0ubuntu7.3 amd64network management framework (shared library) ii libnm-glib4 0.9.8.8-0ubuntu7.3 amd64network management framework (GLib shared library) i libnm-glib-vpn1 0.9.8.8-0ubuntu7.3 amd64network management framework (GLib VPN shared library) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539634 Title: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
Tested the fix. For me it seems to work. This combos work: ii gir1.2-networkmanager-1.0 0.9.8.8-0ubuntu7.3 amd64GObject introspection data for NetworkManager ii libnl-3-200:amd64 3.2.21-1ubuntu1 amd64library for dealing with netlink sockets ii libnl-genl-3-200:amd643.2.21-1ubuntu1 amd64library for dealing with netlink sockets - generic netlink ii libnl-route-3-200:amd64 3.2.21-1ubuntu1 amd64library for dealing with netlink sockets - route interface -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539634 Title: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503647] Re: System hangs with kernel 3.19.0-31
The packages from henrix seems to fix it for me too! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1503647 Title: System hangs with kernel 3.19.0-31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503647] Re: System hangs with kernel 3.19.0-31
Had exactly the same problems as described here since this morning when kernel was updated to 3.19.0.31 via update-manager. My system is ubuntu 14.04 LTS. With the vivid kernel. Booting with the old kernel, 3.19.0.30, makes everything working again. But trying with 3.19.0.31 seems to totally hang everything after having logged in, unity doesnt display or actually i got it displayed one time but then i had no mouse and no control and ctrl alt f1 didnt work. So I guess there is something terribly wrong with the -31 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1503647 Title: System hangs with kernel 3.19.0-31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
