[Bug 1903242] [NEW] Trying to install ubuntu wihtout sole btrfs-partition with MBR-table without EFI-boot partition (worked with 18.04)
Public bug reported: Trying to install ubuntu without sole btrfs-partition with MBR-table without EFI-boot partition (worked with 18.04), but i am not quite sure about the configurations i used then. But the old solely-btrfs system is up & running (no EFI partition). During the installation configuration windows the window asking for username, pc-name etc. didn't show up. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CasperVersion: 1.445.1 Date: Fri Nov 6 07:20:39 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903242 Title: Trying to install ubuntu wihtout sole btrfs-partition with MBR-table without EFI-boot partition (worked with 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1903242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814140] Re: Folders on `Desktop` cannot be opened when nautilus is launched from `Startup Applications`
Possibly integration problem of Btrfs & LVM I just check on another laptop (ACER, other is 'Schenker'). It's the same reproducable bug, that you cannot open folders directly form desktop when you have nautilus added to 'Startup Applications'. I may have a clue: These 18.10-installations are on Btrfs and the buggy 18.04 was on LVM file system. In the attached journal you will find the error in between and at the end when I tried to open a desktop folder: `Φεβ 01 18:54:55 drstoop-opc nautilus[2041]: can't init metadata tree /home/drstoop/.local/share/gvfs-metadata/home: open: Permission denied` gvgs-metadata of these file systems require root permissions. So this bug may be a integration lack of Btrfs and LVM. ** Attachment added: "journal log of buggy session with ACER-laptop" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1814140/+attachment/5235115/+files/jounral_all_ACER.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814140 Title: Folders on `Desktop` cannot be opened when nautilus is launched from `Startup Applications` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1814140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Aw: [Bug 1814140] Re: Folders on `Desktop` cannot be opened when nautilus is launched from `Startup Applications`
** Attachment added: "journal_all.log" https://bugs.launchpad.net/bugs/1814140/+attachment/5234987/+files/journal_all.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814140 Title: Folders on `Desktop` cannot be opened when nautilus is launched from `Startup Applications` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1814140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814140] [NEW] Folders on `Desktop` cannot be opened when nautilus is launched from `Startup Applications`
Public bug reported:
I experience already with 18.04, and now with the newly installed 18.10,
that at some point all folders on the Desktop couldn't be opened
anymore. One needs either open it from a regular nautilus window, or
needs to kill & relaunch nautilus-desktop. I don't understand why but I
finally found the trigger for the bug: It only occurs when nautilus is
launched during boot by `Startup Applications` (so you have a open file
manager window waiting already for you when you boot). If I remove the
nautilus boot-launch from `Startup Applications` the folders can be
opened again directly form the Desktop.
Please find the `/var/syslog` of Ub18.04 and Ub18.10 which I got right after
trying to open a folder:
```sh
# Ubuntu 18.04 /var/syslog
Jan 16 17:59:51 drstoop-pc kernel: [ 657.870793] [UFW BLOCK] IN=wlp112s0 OUT=
MAC=01:00:5e:00:00:01:c4:71:54:33:0a:b0:08:00 SRC=192.168.0.1 DST=224.0.0.1
LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
Jan 16 18:00:33 drstoop-pc signal-desktop.desktop[4016]:
{"name":"log","hostname":"drstoop-pc","pid":4016,"level":30,"msg":"Sending a
keepalive message","time":"2019-01-16T16:00:33.885Z","v":0}
Jan 16 18:00:34 drstoop-pc nautilus-deskto[4026]: cannot open folder on
desktop, freedesktop bus not ready
# Ubuntu 18.10 /var/syslog
Jan 31 18:26:40 drstoop-pc systemd[1]: Started Cleanup of Temporary Directories.
Jan 31 18:26:43 drstoop-pc usbmuxd[1076]: [18:26:43.402][1]
config_get_device_record: failed to read
'/var/lib/lockdown/719aba6e85c2a014e186e582e274284be21acc5c.plist': No such
file or directory
Jan 31 18:26:48 drstoop-pc usbmuxd[1076]: [18:26:48.403][1]
config_get_device_record: failed to read
'/var/lib/lockdown/719aba6e85c2a014e186e582e274284be21acc5c.plist': No such
file or directory
Jan 31 18:26:53 drstoop-pc usbmuxd[1076]: [18:26:53.407][1]
config_get_device_record: failed to read
'/var/lib/lockdown/719aba6e85c2a014e186e582e274284be21acc5c.plist': No such
file or directory
Jan 31 18:26:58 drstoop-pc usbmuxd[1076]: [18:26:58.398][1]
config_get_device_record: failed to read
'/var/lib/lockdown/719aba6e85c2a014e186e582e274284be21acc5c.plist': No such
file or directory
Jan 31 18:27:03 drstoop-pc usbmuxd[1076]: [18:27:03.403][1]
config_get_device_record: failed to read
'/var/lib/lockdown/719aba6e85c2a014e186e582e274284be21acc5c.plist': No such
file or directory
```
Thx & cheers!
Max
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: nautilus 1:3.26.4-0ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 31 18:36:24 2019
GsettingsChanges:
b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
b'org.gnome.nautilus.window-state' b'sidebar-width' b'254'
b'org.gnome.nautilus.window-state' b'geometry' b"'969x364+119+1112'"
InstallationDate: Installed on 2019-01-26 (4 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814140
Title:
Folders on `Desktop` cannot be opened when nautilus is launched from
`Startup Applications`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1814140/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813410] [NEW] Ubuntu18.10 installation on multi device Btrfs failed at installing bootloader
Public bug reported: Hi, I tried to install Ubunutu on a multi device Btfs file system. Before installation I created the Btrfs multi device system with the following command: ``` $ sudo mkfs.btrfs --force --data single --metadata single --label Ubuntu_Btrfs /dev/sda1 /dev/sdc1 $ sudo btrfs device scan ``` I checked the mount handle to be /dev/sda1 (& not /dev/sdc1) and tried to install Ubuntu with /dev/sda1 as root `/`. I suppose the error occurs due to the identical UUIDs of /dev/sda1 and /dev/sdc1 when trying to install the bootloader - but I don't know. Motivation for this was possibly another Btrfs-incompatibility: After installing Ubuntu18.10 on the Btrfs-/dev/sda1 I btrfs-device-added /dev/sdc1 to /dev/sda1. This caused the boot process and the login screen to be very 'freezy' having issues to wait for the screen to build up and the cursor movement and keyboard input to finally display on the screen... Thx & Greets! Max ProblemType: Bug DistroRelease: Ubuntu 18.10 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: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 Date: Sat Jan 26 17:50:05 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubiquity-18.10.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813410 Title: Ubuntu18.10 installation on multi device Btrfs failed at installing bootloader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1813410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812444] [NEW] The "Back"-button in the time zone, cannot go back, crashes on 'x'-button
Public bug reported: The "Back"-button in the time zone installation window is greyed out. As I wanted to go back but couldn't I tried to close the install window with the red "x"-button in the corner. But moving on it with the cursor let it change to a grey "_"-button to minimize the window. Pressing it let the window disappear in the desktop icon and never restored, restarted or reopened till it crashed... ProblemType: Bug DistroRelease: Ubuntu 18.10 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: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 Date: Fri Jan 18 23:27:02 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubiquity-18.10.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812444 Title: The "Back"-button in the time zone, cannot go back, crashes on 'x'-button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1812444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
