[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

2019-10-14 Thread Jan Wester
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:

[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

2019-10-14 Thread Jan Wester
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

[Bug 1826159] Re: gsd-print-notifications assert failure: free(): invalid pointer

2019-04-24 Thread Jan Wester
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

[Bug 1826159] Re: gsd-print-notifications assert failure: free(): invalid pointer

2019-04-24 Thread Jan Wester
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

[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

2018-10-16 Thread Jan Wester
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

[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

2018-10-16 Thread Jan Wester
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.

[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

2018-10-16 Thread Jan Wester
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

[Bug 1774131] Re: update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed'

2018-06-08 Thread Jan Wester
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.

[Bug 1774131] Re: update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed'

2018-06-08 Thread Jan Wester
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():

[Bug 1774131] Re: update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed'

2018-06-05 Thread Jan Wester
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:

[Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-07 Thread Jan Wester
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

[Bug 1751005] Re: libreoffice cannot open a document not within $HOME

2018-02-22 Thread Jan Wester
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

[Bug 1751005] Re: libreoffice cannot open a document not within $HOME

2018-02-22 Thread Jan Wester
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

[Bug 1751005] Re: libreoffice cannot open a document not within $HOME

2018-02-22 Thread Jan Wester
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

[Bug 1751005] Re: libreoffice cannot open a document not within $HOME

2018-02-22 Thread Jan Wester
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

[Bug 1751005] Re: libreoffice cannot open a document not within $HOME

2018-02-22 Thread Jan Wester
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

[Bug 1751005] Re: libreoffice cannot open a document not within $HOME

2018-02-22 Thread Jan Wester
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

[Bug 1751005] Re: libreoffice cannot open a document not within $HOME

2018-02-22 Thread Jan Wester
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

[Bug 1751005] Re: libreoffice cannot open a document not within $HOME

2018-02-22 Thread Jan Wester
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

[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

2017-05-20 Thread Jan Wester
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

[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

2017-05-20 Thread Jan Wester
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

[Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

2016-02-03 Thread Jan Wester
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

[Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

2016-02-03 Thread Jan Wester
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

[Bug 1503647] Re: System hangs with kernel 3.19.0-31

2015-10-07 Thread Jan Wester
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:

[Bug 1503647] Re: System hangs with kernel 3.19.0-31

2015-10-07 Thread Jan Wester
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