A victim of some other fix. This regression can be prevented by adding
amdgpu.dc=0 to the kernel command line.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1762818
Title:
** Attachment added: "Xorg log when booting with 18.04 kernel"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+attachment/5109717/+files/newkernel.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
Public bug reported:
Symptom: booting 18.04 kernel reduces resolution available while 17.10
kernel (on 18.04) does not
I have a 3 identical monitor setup - all at 2560x1600 native resolution.
If I boot the current 18.04 kernel 4.15.0-13-generic then the third
monitor does not have the native
Based on comments here I can get the Microsoft Arc Touch Bluetooth to
pair. But the Bluetooth manager doesn't think it is a mouse, or offer
connecting it to the input service. How does one get an actual working
mouse?
--
You received this bug notification because you are a member of Ubuntu
The mailing list eventually went nowhere, including someone helping me
out privately. He seemed to think it was a udev issue, which was highly
amusing as the udev (and systemd) binaries were running from the very
devices they believed weren't ready yet.
Here is the final scorecard. I have 3
Public bug reported:
/lib/udev/rules.d/64-btrfs.rules
This invokes btrfs ready $devnode. However that will always give a
usage error. The correct invocation is as follows (note added
device).
btrfs device ready $devnode
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: udev 219-7ubuntu5
Supposedly 'btrfs ready $devnode' is internal to udev and unrelated to
the similarly named btrfs device ready command
** Changed in: systemd (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I will ask on the mailing list. It is failing to mount /home. The
lines in /etc/fstab for root and /home are identical, except that one is
subvol=@ and one is subvol=@home.
Root mounts just fine. When it comes time to mount /home, systemd is
trying to check the filesystem but that isn't going
** Attachment added: systemctl status of * (everything)
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4405784/+files/status-all.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Attachment added: /proc/mounts
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4405783/+files/procmounts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Attachment added: systemctl output
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4405785/+files/systemctl.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Outputs from the root shell you get dumped to on an unsuccessful boot.
I did reboot back into it at one point because it kept saying that logs
had been rotated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Attachment added: systemctl status fsck services
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4405782/+files/systemd-fsck-star-service-status.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Message thread in mailing list at
http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/32245
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1447879
Title:
fscking
@pitti: please can you change the title to something that isn't so
misleading. That would let others realise this same bug affects them.
With btrfs if you make a filesystem consist of multiple partitions then
each of those partitions will get the same UUID because they are all
parts of the same
Apologies for misleading you - I thought you were more familiar with
btrfs. The summary change is incorrect and btrfs is doing the right
thing. Quite simply the filesystem is made up of more than one
partition, so more than one partition correctly has the same UUID. But
that also means looking
$ sudo btrfs fi show
Label: 'main' uuid: 3ff68715-0daa-4e44-8de2-0997f36d8ab6
Total devices 2 FS bytes used 408.16GiB
devid2 size 894.25GiB used 319.03GiB path /dev/sdb1
devid3 size 894.25GiB used 319.03GiB path /dev/sda1
Label: 'newspace' uuid:
I also got the status for dev-disk-by\x2duuid-
3ff68715\x2d0daa\x2d4e44\x2d8de2\x2d0997f36d8ab6.device/start which just
had messages about file/directory not found without saying which ones it
was looking for. (To be clear the status for that job was found just
fine - the contents of the status
The weird device= lines were me trying to work around a different
regression. I have two hard drive controllers on the motherboard - a 4
port one from Intel and a 4 port one from ASMedia. I also have 6
devices plugged in (8 at one point). Before 15.04 I placed the drives
randomly, and it turned
The problem is actually the mounting of /home not root. As you can see
from the fstab they are identical except for the subvol= parameter.
Note that I also tried removing the device= bits, updating the initramfs
and trying again. It made no difference.
** Attachment added: journal.txt
** Attachment added: fsckd-status.txt
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4383527/+files/fsckd-status.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Attachment added: fsck-root-status.txt
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4383526/+files/fsck-root-status.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
I have two SSDs in raid0 (striped) configuration with my root and home
as separate subvolumes. This setup has worked fine for several Ubuntu
releases, but fails with systemd on 15.04. systemd does manage to mount
root, but then looks like it is trying to fsck the disk for
23 matches
Mail list logo
