** Changed in: ubuntu-gnome
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644781
Title:
Sushi-start fails with 16.10 upgrade, both Unity and Mate
To manage
I think I would like to mark this as 'closed'. It was a valid bug, at
the time, and @fjkong managed a good fix for Unity.
Looking back, I don't think it could ever have been fixed for Ubuntu
Mate. The architecture is too different. It would need a load of code,
not just a tweak or two.
**
Public bug reported:
Except from Package description (Eoan):
"For scanning to work, a virus database is needed. There are two options
for getting it:
- clamav-freshclam: updates the database from Internet. This is
recommended with Internet access.
- clamav-data: for users without Internet
I have now marked this as 'fix-released' as Ubuntu Mate 19.04 contains
the upgraded files and I can confirm that this works for me.
Hopefully other people are finding similar.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: caja (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787242
Title:
Caja: segfault 4 from usb drive unmount
To manage notifications
So, 4 weeks later, after my previous comments, and now running stably:
Upgraded to 5.0.0-15 today via command line with 'do-release-upgrade'.
The triggers looping error still happens but this gets mopped up by
dpkg --configure -a which the upgrade script autoruns for you.
The 'system error
Update to 2 hours ago:
Started getting segfault problems with libglib. Again re-install fixed
that but then I was getting segfaults elsewhere too.
I have now reverted to a full system backup of 18.10 that I made earlier
&& will probably stay on that for a bit longer.
--
You received this bug
I noticed that the OP had VirtualBox installed, same for me. This taints
the kernel ...
Are people who posted about going back to the old kernel using VBox?
So, re-installing 'VirtualBox' and ubuntu package 'menu' worked for me,
and keeping the new kernel
Suggest "dmesg | grep vbox" (YMMV)
I
@drstevebrule & others,
We now have a new Caja release which includes fixes for this issue:
https://github.com/mate-desktop/caja/releases (1.20.3)
Refs:
https://github.com/mate-desktop/caja/pull/1084
https://github.com/mate-
desktop/caja/commit/df49a00d53e7b874f8146a73329b6f0a0a88e5df
I
Paste from [ https://github.com/mate-
desktop/caja/issues/1046#issuecomment-431685452 ]
"@emanuele-f Yes, this works for me. Well spotted. Places > Computer >
right click. At last the correct 'safely remove' behaviour and no
corrupted usb file system. Finally.
Small observation, I am seeing
:( Just did the upgrade with libmount1, mount, libblkid1, uuid-runtime,
fdisk and others. Even after a machine restart, the problem is still
present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Woo! Not at my desktop but good work. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787242
Title:
Caja: segfault 4 from usb drive unmount
To manage notifications about this bug go to:
12 matches
Mail list logo
