[Bug 1585332] Re: Graphical snaps don't honour the desktop theme

2018-07-27 Thread Grey Seeker
Seriously guys, this isn't that hard to fix.
A change can be made to the theming structure so that all GTK+ config files in 
each snap directory are linked to the user's to honor the theme. It doesn't 
even require each snap to be written differently. Just put it in the guidelines 
for developers to follow. In the meantime a separate snap daemon can be written 
to scan for independent GTK config files in snap directories and link them to 
the user's.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585332

Title:
  Graphical snaps don't honour the desktop theme

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1585332/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1634102] Re: Installer mistakenly mounts Btrfs root filesystem at /target/home, and crashes afterwards

2016-11-03 Thread Grey Seeker
I formatted the partition so no data was present. And the only mount
point was for /home, and somehow the / wasn't mounted on /target. I
checked with df and mount.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634102

Title:
  Installer mistakenly mounts Btrfs root filesystem at /target/home, and
  crashes afterwards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1634102/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1634102] Re: Installer mistakenly mounts Btrfs root filesystem at /target/home, and crashes afterwards

2016-10-17 Thread Grey Seeker
The error message makes sense, if /target does not lie on a separate
partition it would be on the live system, and thus showing the error.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634102

Title:
  Installer mistakenly mounts Btrfs root filesystem at /target/home, and
  crashes afterwards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1634102/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1634102] [NEW] Installer mistakenly mounts Btrfs root filesystem at /target/home, and crashes afterwards

2016-10-17 Thread Grey Seeker
Public bug reported:

This is a simple install on an SSD, with EFI system partition as sda2
and Btrfs root partition as sda8. When I ran lsblk I noted that sda8 was
mounted as /target/home, although I had specifically told the installer
to mount it at /. The installer crashed with:

 [Errno 28] No space left on the device

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.14 [modified: 
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CasperVersion: 1.379
Date: Mon Oct 17 13:03:35 2016
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed 
boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 TERM=unknown
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubiquity-16.10.14 ubuntu yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634102

Title:
  Installer mistakenly mounts Btrfs root filesystem at /target/home, and
  crashes afterwards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1634102/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs