Public bug reported:
I installed Ubuntu Mate 19.10 on ZFS in Virtualbox on sdb, while sda has
Ubuntu 19.10 on ext4 with both zfsutils-linux and zfs-initramfs
installed. The installer refused to install a boot loader on both sda
and sdb, but after booting from ext4 and:
updating
I used the following commands on both systems;
sudo zpool export hp-data
sudo zfs list # the other command produces a lot of snap mounts
sudo umount -l /vms/vms #the only other mounted dataset
sudo rmdir /hp-data
sudo rmdir /vms/vms
Update and upgrade the system
sudo zpool import hp-data
sudo
Sorry, you were right about the meaning of import/export and rmdir, but
my excuse is, that it has been very early in the morning.
However I have the same update problem on an ext4 installation of Ubuntu
19.10 on the same laptop. It gives the same error on two zfs modules,
but of course without
Sorry, but this is ridiculous. After the upgrade to 19.10, the system
worked fine for a week. I should export/import ~700 GB of data to get an
standard update working? Why should your advice help this time? If I'm
stupid enough to move 700GB of data around, I will probably have the
same problem
Note that the system also refuses to mount my hp-data datapool a
datapool for all my data and only data, since the directory is not
empty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846424
Title:
Tried the change bu it did not work. tried it a second time after update-grub
still not working.
I forced zfs re-installation by removing a non-existing module zfs-dkms.
** Attachment added: "mountpoint-change"
The output related to the mountpoints, see attachment
** Attachment added: "mountpoints"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+attachment/5295259/+files/mountpoints
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Ignore the version numbers in the roots sub dataset, I did not change
the dataset names, but the system versions stored there is 19.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846424
Title:
What I expected is that those menu entries would work as said in that
menu line.
However the situation completely changed, because the Grub menu has been
"rolled back" by an update to a more classic view without the history menu
entry and only one classic recovery mode per Linux version in the
I boot from ZFS so that datapool will be root mounted. That same
datapool has been used in the past exclusively for Virtual Machines,
later I added the datasets for the host OSes to the same datapool,
because they were at the begin of my SSHD. So that datapool contains
datasets with Virtualbox VMs
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846424
Title:
19.10 ZFS Update failed on 2019-10-02
To manage
I think we have two bugs:
- one is about dmesg is reporting the wrong versions
- the other is about a failing zfs upgrade, if we boot from ZFS. Why mount the
system again? It has already been mounted during the boot and all other non-zfs
package updates have been completed without problems.
--
I have done a fresh install of zfsutils-linux on another system booted
from ext4. Ubuntu Mate 19.10. Also there the system is confused about
the module installed. See install and the result of dmesg.
** Attachment added: "zfs-update-bug3"
ON the system that I boot from ext4, the system is confused about which
zfs module is loaded, see attachment.
** Attachment added: "zfs-update-bug2"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+attachment/5293869/+files/zfs-update-bug2
--
You received this bug
I tried removing zfs-dkms, but in the VM with Ubuntu 19.10, it said module not
installed. In that system I boot from ext4.
On my laptop with Ubuntu Mate I boot from ZFS and there, it produced the
following errors, see attachment.
** Attachment added: "zfs-update-bug"
Public bug reported:
On all my systems the update from zfs-initrams_0.8.1-1ubuntu12_amd64.deb failed
the same is true for zfs-zed and zfsutils-linux.
The system still runs on 0.8.1-1ubuntu11_amd64.
The first error message was about a failing mount and at the end it announced
that all 3 modules
Some additional info from conky about the configuration:
** Attachment added: "Screenshot from 2019-09-26 12-09-32.png"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1843222/+attachment/5291518/+files/Screenshot%20from%202019-09-26%2012-09-32.png
--
You received this bug
Note that I only can use the datapools after I exported and re-imported
them again. But I have to do that on all boots, so I wrote a small
script for it. I did not upgrade the datapool itself, because 2 of the 3
systems still run Ubuntu 19.04 one also from the zfs systems datapool
and the other
OK I did upgrade one of my desktop OSes (ubuntu Mate 19.04). It has been
running on a Ryzen 3 2200G, but initially it has been installed on a
Phenom II X4 B97 with a GeForce 8400GS. So maybe you see some nvidea
related error too, I did not purge that module, I did forget all about
it. This
My laptop has been completely upgraded. I will try it on one of the two
systems on my Ryzen desktop both still running 19.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843222
Title:
Old Linux
An additional remark.
ZFS will change the ways we deal with multi-boot situation, since it will be
relatively simple to add or delete a Linux OS. You do not have to reorganize
all your partitions.
Currently I use VMs to test/try new versions of the Ubuntu flavors, however for
20.04 I consider
Public bug reported:
I have a triple boot:
- Ubuntu 19.10 on ext4
- Ubuntu Mate 19.10 on zfs
- Xubuntu 19.10 on zfs
All names for those 3 system in the boot menus are the same, which is
confusing. Only the ext4 system is recognizable because the system adds
"on sda1". Didier Roche did
I have removed Linux 5.0 everywhere, since it was using ZFS 0.7.12 and I
also removed the snapshots containing Linux 5.0. I now only have 5.2 and
5.3 in the system with one new snapshot, but all problems remain the
same.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I had a triple boot since April:
- Ubuntu 19.04 on ext4
- Ubuntu Mate 19.04 on zfs
- Xubuntu 19.04 on zfs
Each zfs based system is stored completely in its own dataset, all folders are
in that dataset; var; usr; home and all others.
I have upgraded all systems to 19.10 and
I have two datapools one in the begin of the HDD for the Host OSes and
Virtual Machines and one at the end for data, music, family videos and
relatively large old archives. The throughput at the begin of the HDD is
often twice the throughput at the end of the HDD, so I have a very good
reason to
I did add an entry with two /boot/grub/grub.cfg files and one did
include my 40_custom file. That file did include "This" but in the first
comment line as shown below:
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries
It has been an error during the upgrade itself, since a fresh install
solved my problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843222
Title:
Old Linux version booted after upgrade to
Public bug reported:
I have 2 systems installed on ZFS
- Ubuntu Mate 18.04.3
- Xubuntu 19.10
For the coming period I like to keep one ext4 installation, so I did do
a fresh install of Ubuntu 19.10 on the ext4 sda1 partition. I installed
zfsutils-linux and rebooted. Afterwards I did run
Two other relevant files from /boot/grub.
"grub.cfg" the one used with 5.0 and "grub.cfg.new" NOT used and with Linux 5.2.
** Attachment added: "grub.zip"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1843222/+attachment/5287546/+files/grub.zip
--
You received this bug
Public bug reported:
I have upgraded my dual boot laptop (Xubuntu 19.04 on ZFS) to 19.10, I
only had a minor problems:
The system started scrubbing the exisisting datapools.
In the scrub I have been notified, that my datapool did not support all new
features and that I had to upgrade the
Public bug reported:
I have upgraded my dual boot laptop (Xubuntu 19.04 on ZFS) to 19.10, I
only had a minor problem:
The system on boot did start scrub of all datapools automatically, that was
unexpected and it took a couple of minutes before I realized, why the system
was that effing
I did see a number of red error messages, but I did see the same or
almost the same error messages in the upgrade of my zfs based Xubuntu
and that one worked afterwards without any problem. So I probably
ignored those error messages.
On 9/9/19 2:35 a. m., Didier Roche wrote:
> Thanks for
Public bug reported:
I have a triple boot with the following systems:
- Xubuntu 19.10 from zfs 0.8.1
- Ubuntu Mate 18.04.3 from zfs 0.7.12
- Ubuntu 19.10 from ext4
Upgrading the first system Xubuntu to 19.10 worked fine and I was very happy
with the almost perfect result and the nice grub-menu.
OK It also happened on my 19.10 development branch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811479
Title:
wrapper-2.0 crashed with SIGSEGV in g_slice_alloc()
To manage notifications about
I also do not see the garbling in Ubuntu 19.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826053
Title:
Notify send is unreadable
To manage notifications about this bug go to:
No, at the moment I did the Ubuntu-bug, I did not remember the name of
the package, so I used the wrong package name.
However I did use notify-send to send a report of the boot time. See the
next script:
systemd-analyze | grep "=" | cut -c 20-80 | while read OUTPUT; do
notify-send -t 6000
OK! That solved my problem. Thank You
On 23/4/19 10:09 p. m., Daniel van Vugt wrote:
> Please try this as a workaround: edit /etc/gdm3/custom.conf and
> uncomment the line:
>
> #WaylandEnable=false
>
> Then reboot.
>
> ** Tags added: nvidia
>
> ** Changed in: gdm3 (Ubuntu)
> Status:
The nouveau driver does work with Ubuntu 19.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826061
Title:
gdm not displaying any graphics in Ubuntu 19.04
To manage notifications about this bug
Public bug reported:
My hardware: GT218 in a NVIDIA GeForce 8400GS rev 3.
Driver: Nvidia 340.107
Ubuntu 19.04 does not display any graphics, it stays at the display of
the CLI, after announcing the start of the gnome display manager.
I tried a fresh install of Ubuntu 19.04 and I tried to add
I had a power-fail during processing the bug, so probably some info is
lost.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826061
Title:
gdm not displaying any graphics in Ubuntu 19.04
To manage
Public bug reported:
Notify-send message are written to the screen using a white background
with randomly white or light-green fonts. Often they are completely
unreadable. see screenshots.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: notify-osd (not installed)
ProcVersionSignature:
And another screenshot
** Attachment added: "Screenshot at 2019-04-23 15-39-19.png"
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1826053/+attachment/5258342/+files/Screenshot%20at%202019-04-23%2015-39-19.png
--
You received this bug notification because you are a member of
SORRY Rebooting the system restores the correct display, restarting the
disk utility did not help. Any action in the extended partitions
distorts the display of those logical partitions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
See screenshot with comparison gparted and gnome-disk-utility, the
display of gparted is correct. The display of the gnome-disk utility was
distorted after I deleted the swap partition, recreating that partition
with gparted did not correct the display. Rebooting did not
If other partitions on the disk the display is correct, if only 2 zfs
partitions are on the disk the display is wrong. The disk have been
partitioned originally with the gnome-disk-utility.
** Attachment added: "Screenshot at 2019-04-23 14-30-29.png"
And now the complex SDD (boot-datapool, 2xlog and 2xcache partitions)
displayed correctly
** Attachment added: "Screenshot at 2019-04-23 14-35-16.png"
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1808421/+attachment/5258320/+files/Screenshot%20at%202019-04-23%2014-35-16.png
--
You
Public bug reported:
The song Waterloo of ABBA plays correct with
Windows Media Audio 9.1, VBR Quality 50, 44 kHz, stereo 1-pass VBR, but it
stutters badly with
Windows Media Audio 9.2, VBR Quality 50, 44 kHz, stereo 1-pass VBR
I use Quod Libet as audio payer.
The song plays for one second,
Formally it is not a bug, basically it is a user error. However to avoid
these type of bug reports in future, you might define it as a low
priority bug or change request. There are reasons to block photo folders
from access by the world for privacy reasons. Anybody using a photo from
such a
Using chmod 644 did fix the problem and the photo is now also displayed
in the login screen.
Setting the permission to 660 did restore the old situation, the photo
is not displayed in the login screen but in all other screens after login.
I assume the permissions did not really allow root read
I have done a fresh install from Xubuntu 18.04.2 and did notice it was
using zfs 0.7.9 with Linux 4.18. So probably you have to add those to
the upgrade of the HWE stack.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
WRAP UP
First my mistake:
I found a work-around. My 2008 HP dc5850 allows me to boot from the first disk
of the internal SATA-2 controller or from a SATA-3 PCIe card, I have added for
the SSD. I did boot in the BIOS from the SSD, but did forget all about it and
assumed during the installation
OK I installed again from CD on the real hardware on partition sdc5. I had the
same old problem, but than I detected, that I told the BIOS some time ago to
boot from the SSD. I did forget it completely and normally I have no problem,
since I install the boot loader on all disks after running
I tried to reconstruct the issue using Virtual Machines. I took an Ubuntu
18.04.2 VM with Linux 4.15 and added a second disk. I booted that VM from the
ISO with Xubuntu 18.04.2 and installed Xubuntu on that second disk and it
rebooted after install without any problem.
So I have to retry it on
I tried to reconstruct the issue using Virtual Machines. I took an Ubuntu
18.04.2 VM with Linux 4.15 and added a second disk. I booted that VM from the
ISO with Xubuntu 18.04.2 and installed Xubuntu on that second disk and it
rebooted after install without any problem.
So I have to retry it on
The boot loader is stored on sda since 2014 and used by all systems on sdc and
sdd. Up to now all 18.04.2 systems use Linux 4.15, since the 4.18 HWE upgrade
failed on the compilation of the ZFS-SPL module (another bug report).
I remember that after trying to repair the system by running
Public bug reported:
Try to install Xubuntu 18.04.2 on btrfs, it failed to boot because grub could
not find the kernel.
The partition did have two directories @ and @home, the @ one contained all the
root files, while the @home one contained the 'user' directory.
** Affects: gnome-disk-utility
Public bug reported:
I have 26GB free at the begin of the drive and create a extended partition in
that area and that went OK. While trying to create a 18GB ext4 partition in
that extended partition, that extended partition is completely f$$cked up.
See the collage of screenshots in the annex.
I think the collage of screenshots were missing.
** Attachment added: "collage.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1816206/+attachment/5238982/+files/collage.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just found out, that you can make Firefox play that video by pressing
'Pause' and afterwards 'Play', when it halts. I think, it looks like a
timing issue in Firefox itself. Still it is very confusing for a user
and I had the same problem trying to play voice maWhatsapp
--
You received this bug
Public bug reported:
After some update Firefox 65.0 does not play YouTube videos anymore in some
virtual machines of Virtualbox 6.04. The following VM were tested and found
wrong Xubuntu 18.04.2, Ubuntu Mate 18.04.2 both with Linux 4.18 and Ubuntu
16.04 with Linux 4.15. The same Firefox
Public bug reported:
I tried to upgrade the HWE stack but it failed. I used:
sudo apt-get install --install-recommends linux-generic-hwe-18.04
xserver-xorg-hwe-18.04
It failed with:
Setting up linux-headers-4.18.0-15-generic (4.18.0-15.16~18.04.1) ...
/etc/kernel/header_postinst.d/dkms:
Error!
Public bug reported:
I inserted the photo using the Users and Groups package and the photo is
accepted and displayed(see screenshot). It is also displayed in the
authentication screens and the logout screen, but NOT in the login
screen.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package:
Public bug reported:
See screenshot, synaptic cannot start due to "cannot open display"
problem. The problem does not exist in Xubuntu 19.04 nor in Ubuntu Mate
19.04
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: synaptic 0.84.5
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Public bug reported:
See screenshot, synaptic cannot start due to "cannot open display"
problem. The problem does not exist in Xubuntu 19.04 nor in Ubuntu Mate
19.04
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: synaptic 0.84.5
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Public bug reported:
See screenshot, synaptic cannot start due to "cannot open display"
problem. The problem does not exist in Xubuntu 19.04 nor in Ubuntu Mate
19.04
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: synaptic 0.84.5
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Public bug reported:
See screenshot, synaptic cannot start due to "cannot open display"
problem. The problem does not exist in Xubuntu 19.04 nor in Ubuntu Mate
19.04
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: synaptic 0.84.5
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Public bug reported:
Crashed after upgrade while running Ubuntu Cleaner
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: libxfce4panel-2.0-4 4.13.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu19
Public bug reported:
Happened during an upgrade from Xubuntu 18.04 to Xubuntu 18.10. But ZFS
did work OK after upgrade.
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: zfs-dkms 0.7.9-3ubuntu6
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic
Public bug reported:
I tried to install and it crashed while specifying user name and
passwords.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 18.10.12
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion:
Public bug reported:
The system crashed during the update of the virtualbox guest addition
drivers during the system upgrade from 4.17.0-7 to 4.17.0-9
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: apport-gtk 2.20.10-0ubuntu9
ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12
Paul White
I have no language problems with Ubuntu anymore, only sometimes in real
life.
BertN45
On 24/08/18 05:13, Paul White wrote:
> BertN45,
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. We are sorry that we do not always have
Why should I try an older version with more unsolved problems. I prefer
the one bug I know! For my use of Ubuntu 16.04 VM to support Banking and
PayPal, I can live with the problem.
Besides your last remark is somewhat stupid, I run a host OS and use 4
VMs for different purposes. I do not change
I had exactly the same problem with Ubuntu Mate 18.04. That problem
disappeared when I switched from the Compiz compositor to the Marco
Compton GPU compositor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can't reproduce the problem on Linux 4.15.0-13. I reinstalled
Lollypop, but no crashes. Only a completely other crash of Lollypop
itself, every time I change the album art.
I think, it might be one of those crashes, that occur once a week or so.
Sorry, I keep looking.
On 12/04/18 16:14,
Public bug reported:
Playing lollypop while lollypop is scanning its library for the first
time
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
I update the system each day, so I assume it has been introduced this
week.
On 27-03-18 17:39, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you
Yes, I update the system each day, so it has been introduced this week.
On 27-03-18 17:16, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to
Public bug reported:
Crash happened after booting the system
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
Annotation: Your system might become
Public bug reported:
Crash occured after booting, while downloading the updates with Software
Updater
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion:
Public bug reported:
Crash occured after reboot of the Saturday update.
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
Annotation: Your system
Public bug reported:
Since Tuesday 20-3-2018 Ubuntu Budgie 18.04 has a login loop. Before
that date everything worked fine. The login loop occurs in a Virtualbox
guest while 3D is enabled for the display.
On the same data Ubuntu 18.04 refused to show the login screen, but I
will file a seperate
Public bug reported:
After boot, while running Software Updater. That Updater nicely finished
its job.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.27.91-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
Public bug reported:
After boot tried to change wall paper, when the crash occured
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.2-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
OK. Thank you ads2. I think, it really complicates the system for a
home user. I'm completely happy with the restrictions per user. I know
many home users, who even run into problems with that.
At the moment I have some VMs running LibreOffice 5.1 and 6.0 and those
have no AppArmor issues.
OK, but where can I find, what the purpose is of this functionality? How
could it improve my security? Do you have any reading material?
--
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:
I hate these type of surprises, caused by badly designed and/or
published improvements. The professional way to introduce those changes,
is enabling the new intrusive function in the settings function of the
program introducing that change.
I store all my files in the Virtualbox Shared Folders on
** Description changed:
- It looks that the sequence of frames displayed at the screen is mixed up. The
display goes back say ¼ a second and that gives a very strange effect. You type
a letter, that letter is erased afterwards and reappears after ¼ of a second.
See the ATTACHED video. You see
Another video with an audio player and a progress bar and counter
sometimes going backwards
** Attachment added: "stutter1.mp4"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751191/+attachment/5060871/+files/stutter1.mp4
--
You received this bug notification because you are a member
Public bug reported:
It looks that the sequence of frames displayed at the screen is mixed up. The
display goes back say ¼ a second and that gives a very strange effect. You type
a letter, that letter is erased afterwards and reappears after ¼ of a second.
See the ATTACHED video. You see the
** Description changed:
Error message the virtual machine Ubuntu 17.10:
---
No protocol specified
Unable to init server: Could not connect: Connection refused
(nautilus:2377): Gtk-WARNING **: cannot open display: :0
---
- Note that it
The problem only occurs using Wayland, using Xorg it works normally.
That is why it works by default (Xorg) in 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/1750443
Title:
sudo nautilus or
bertadmin@vm-ubuntu-1804:~$ ls -la /media/sf_hp-data
total 1742512
drwxrwx--- 1 root vboxsf 4096 feb 20 18:26 .
drwxr-xr-x 4 root root 4096 dec 22 14:34 ..
drwxrwx--- 1 root vboxsf 4096 jan 28 00:31 Bert
-rwxrwx--- 1 root vboxsf 1726365696 feb 20 18:04 bionic-desktop-amd64.iso
** Description changed:
Error message: Access to /media/sf_hp-data/Bert/Documents/To Do.odt was
denied.
It happens only in Vbox Shared Folders and only using Ubuntu 17.10,
18.04 and Ubuntu Mate 17.10, which might be related to the LibreOffice
release 5.4.4.2 and 5.4.5.1 used. Other
** Description changed:
Error message: Access to /media/sf_hp-data/Bert/Documents/To Do.odt was
denied.
It happens only in Vbox Shared folders and only using Ubuntu 17.10,
18.04 and Ubuntu Mate 17.10, which might be related to the LibreOffice
release 5.4.4.2 and 5.4.5.1 used. Other
Public bug reported:
Error message: Access to /media/sf_hp-data/Bert/Documents/To Do.odt was
denied.
It happens only in Vbox Shared folders and only using Ubuntu 17.10,
18.04 and Ubuntu Mate 17.10, which might be related to the LibreOffice
release 5.4.4.2 and 5.4.5.1 used. Other files like
Public bug reported:
Happened directly after bug 1750690
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: mate-applet-brisk-menu 0.5.0-5ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture:
Public bug reported:
Moved terminal to dock and started the terminal from the dock, which
seemed to cause the crash.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: mate-dock-applet 0.81-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic
I have tried with Vbox 3D enabled and the 'sudo nautilus' works OK.
Disabling 3D again reintroduces the error. The error occurs with both
Vbox Guest Additions 5.2.7 and 5.2.4. Enabling 3D is not a good
workaround, because of bug Bug 1748729 related to 3D enabled.
--
You received this bug
Public bug reported:
Error message the virtual machine Ubuntu 17.10:
---
No protocol specified
Unable to init server: Could not connect: Connection refused
(nautilus:2377): Gtk-WARNING **: cannot open display: :0
---
Note that it works in Ubuntu
*** This bug is a duplicate of bug 1727279 ***
https://bugs.launchpad.net/bugs/1727279
Public bug reported:
Crashed during start up
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: chromium-browser 64.0.3282.167-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
201 - 300 of 506 matches
Mail list logo
