[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

2014-12-05 Thread MegaBrutal
I've had a backup of my old Trusty system, and I've built an initrd for 3.16.0-23-generic in that environment. With that initrd, the kernel booted properly. Note, still it takes several minutes for the VG to activate, but it eventually comes up if the kernel waits enough with rootdelay=300. Now,

[Touch-packages] [Bug 1432899] Re: VESA error: Cannot read int vect

2015-03-16 Thread MegaBrutal
** Also affects: xserver-xorg-driver-vesa (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification

[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

2015-03-18 Thread MegaBrutal
Now I have some more info about this. What actually makes the VG activation so long is that I have a snapshot. Activating the snapshot takes very long, and bringing up the entire VG takes about 5 minutes. This wouldn't be such a big problem, as I could just patiently wait for the activation (with

[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

2015-03-19 Thread MegaBrutal
With the knowledge that the hang is caused by snapshots, some googling has brought up some duplicates: https://bugs.launchpad.net/lvm2/+bug/360237 https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/995645 It seems the issue was hanging around since 2009 or earlier. In Trusty (or probably even

[Touch-packages] [Bug 995645] Re: udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y''

2015-03-19 Thread MegaBrutal
*** This bug is a duplicate of bug 1396213 *** https://bugs.launchpad.net/bugs/1396213 ** This bug has been marked a duplicate of bug 1396213 LVM VG is not activated during system boot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 360237] Re: cannot boot root on lvm2 with (largish) snapshot

2015-03-19 Thread MegaBrutal
*** This bug is a duplicate of bug 1396213 *** https://bugs.launchpad.net/bugs/1396213 ** This bug is no longer a duplicate of bug 995645 udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y'' ** This bug has been marked a duplicate of bug 1396213 LVM VG

[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

2015-03-19 Thread MegaBrutal
Got an interesting reply from the Red Hat LVM mailing list: https://www.redhat.com/archives/linux-lvm/2015-March/msg00022.html Haven't tested the suggestion yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in

[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

2015-03-19 Thread MegaBrutal
Turns out, the suggested --setactivationskip option is not present in Utopic, as Utopic comes with an LVM version which dates back to 2012 (2.02.98(2) (2012-10-15)), while the feature was implemented in 2013. Vivid will come with a newer LVM: 2.02.111(2) (2014-09-01). Activation skip could be a

[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

2015-03-20 Thread MegaBrutal
@Astara: Now, I've noticed when I am booting, it *does* take a bit of time to mount bring up and mount all of the lvs, but you can the root mount is NOT in an VG/LV -- It's on a regular device (numbers on left are w/kernel time printing turned on -- so they are in seconds after boot): [

[Touch-packages] [Bug 1432899] Re: VESA error: Cannot read int vect

2015-03-19 Thread MegaBrutal
Today's update of xserver-xorg-core has fixed the issue. xorg-server (2:1.17.1-0ubuntu3) vivid; urgency=medium * Add a patch to fix vesa int10 failure. (LP: #1433198) -- Maarten Lankhorst maarten.lankho...@ubuntu.com Thu, 19 Mar 2015 10:13:08 +0100 ** Changed in: xorg-server (Ubuntu)

[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

2015-03-19 Thread MegaBrutal
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu.

[Touch-packages] [Bug 1437536] Re: Screen corruption under KVM

2015-03-28 Thread MegaBrutal
** Summary changed: - Screen corruption under KVM with Spice display + Screen corruption under KVM -- 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/1437536 Title: Screen

[Touch-packages] [Bug 1437536] Re: Screen corruption under KVM

2015-03-28 Thread MegaBrutal
** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-driver-vesa/+bug/1437536/+attachment/4359299/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 1437536] Re: Screen corruption under KVM with Spice display

2015-03-28 Thread MegaBrutal
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-driver-vesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1428952] Re: strings in UI incorrectly displayed with lots of spacing

2015-03-26 Thread MegaBrutal
This bug seems to be very prominent with beta versions of Vivid, recently I encountered it on a virtual machine during Ubuntu MATE installation. I'd suggest to triage it asap and increase its priority. ** Tags added: utopic vivid -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1428952] Re: strings in UI incorrectly displayed with lots of spacing

2015-03-26 Thread MegaBrutal
This is another example of the display bug. ** Attachment added: Screenshot_UbuntuMATE_2015-03-27_05:19:14.png https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1428952/+attachment/4357560/+files/Screenshot_UbuntuMATE_2015-03-27_05%3A19%3A14.png -- You received this bug

[Touch-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time

2015-02-20 Thread MegaBrutal
** Description changed: - I'm experiencing with Vivid Vervet on a virtual machine and tried a new + I'm experimenting with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot

[Touch-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time

2015-02-20 Thread MegaBrutal
** Tags added: vivid ** Description changed: I'm experiencing with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After

[Touch-packages] [Bug 1437536] [NEW] Screen corruption under KVM with Spice display

2015-03-27 Thread MegaBrutal
Public bug reported: I was experimenting with Ubuntu MATE, and I found severe screen corruption whenever I run the image under a KVM virtual machine. I attached a screenshot. I don't think the problem is Ubuntu MATE specific. I also found it doesn't depend on the display manager. (It can be

[Touch-packages] [Bug 1444268] Re: [Lenovo ThinkPad T400] Screen corruption

2015-04-23 Thread MegaBrutal
I used the Trusty 14.04.0 Live CD for like half a day and didn't experience the issue. -- 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/1444268 Title: [Lenovo ThinkPad T400]

[Touch-packages] [Bug 1444268] Re: [Lenovo ThinkPad T400] Screen corruption

2015-04-23 Thread MegaBrutal
I experience the exact same problems with the most recent Vivid Vervet Live CD build. -- 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/1444268 Title: [Lenovo ThinkPad T400]

[Touch-packages] [Bug 1444268] Re: [Lenovo ThinkPad T400] Screen corruption

2015-04-23 Thread MegaBrutal
To be honest, I don't remember. It appeared around the time when Utopic was released, but I don't know whether it was before or after the upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 1444268] [NEW] [Lenovo ThinkPad T400] Screen corruption

2015-04-14 Thread MegaBrutal
Public bug reported: I often perceive massive screen corruption, most prominently in Firefox / GMail, but it may happen with any application, including terminals. Sometimes oversized letters appear. I run video stress tests, but they run without errors. I suspect the problem presents when many

[Touch-packages] [Bug 1444268] Re: [Lenovo ThinkPad T400] Screen corruption

2015-04-14 Thread MegaBrutal
** Attachment added: Képernyőkép – 2015-04-15 07:39:27.png https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+attachment/4375900/+files/K%C3%A9perny%C5%91k%C3%A9p%20%E2%80%93%202015-04-15%2007%3A39%3A27.png -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1444268] Re: [Lenovo ThinkPad T400] Screen corruption

2015-04-14 Thread MegaBrutal
** Attachment added: Képernyőkép – 2014-12-06 15:04:50.png https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+attachment/4375901/+files/K%C3%A9perny%C5%91k%C3%A9p%20%E2%80%93%202014-12-06%2015%3A04%3A50.png -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1509717] [NEW] Wily LVM-RAID1 – md: personality for level 1 is not loaded

2015-10-24 Thread MegaBrutal
Public bug reported: After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was

[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2015-10-24 Thread MegaBrutal
I can't collect logs on non-booting system. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title:

[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2015-10-24 Thread MegaBrutal
** Tags added: regression-release wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in

[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2015-10-25 Thread MegaBrutal
Reproducible: upgraded another Ubuntu installation in VM and got the same result. Since the bug prevents booting, I suggest to increase priority to High. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu.

[Touch-packages] [Bug 1511875] Re: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container

2015-10-30 Thread MegaBrutal
** Description changed: When I try to upgrade from 15.10 Wily to 16.04 Xenial (actual development version) within an LXC container, the upgrade script hangs at the message „Calculating the changes”. Steps to reproduce: 1. Make an LXC container with Wily (quickest option is to use

[Touch-packages] [Bug 1511875] [NEW] Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container

2015-10-30 Thread MegaBrutal
Public bug reported: When I try to upgrade from 15.10 Wily to 16.04 Xenial (actual development version) within an LXC container, the upgrade script hangs at the message „Calculating the changes”. Steps to reproduce: 1. Make an LXC container with Wily (quickest option is to use lxc-create -t

[Touch-packages] [Bug 1503979] Re: ubuntu-support-status throws exeption No date tag found (regression)

2015-11-07 Thread MegaBrutal
Same here: $ ubuntu-support-status Traceback (most recent call last): File "/usr/bin/ubuntu-support-status", line 135, in pkg.name, support_tag) File "/usr/bin/ubuntu-support-status", line 51, in get_maintenance_status raise Exception("No date tag found") Exception: No date tag

[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2016-01-22 Thread MegaBrutal
Thanks for the workaround! It seems adding raid1 is enough. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not

[Touch-packages] [Bug 1574833] [NEW] setkey is not run automatically on system start

2016-04-25 Thread MegaBrutal
Public bug reported: The „setkey” service should run at system startup to add keys defined in /etc/ipsec-tools.conf. However, no keys are defined after system boot: root@ReThinkCentre:~# setkey -D No SAD entries. After inquiring systemd, I learn this: root@ReThinkCentre:~# systemctl status

[Touch-packages] [Bug 1770940] [NEW] Kexec reboot doesn't work on 18.04 non-EFI system

2018-05-13 Thread MegaBrutal
Public bug reported: Unclear whether to report it against kexec-tools or systemd. After upgrading to Ubuntu 18.04, the „systemctl kexec” command gives the following error message: Cannot find the ESP partition mount point. What's interesting is that strace shows that systemctl tries to find

[Touch-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade

2018-05-19 Thread MegaBrutal
** Attachment added: "Xorg log from ~/.local/share/xorg/" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+attachment/5141626/+files/Xorg.1.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade

2018-05-19 Thread MegaBrutal
I don't know why, but apport attached wrong (outdate) Xorg logs to my report. Probably it's a gdm feature that it puts logs elsewhere instead of the usual /var/log/Xorg.0.log. The actual logs made by my X11 server are located here: /var/lib/gdm3/.local/share/xorg/Xorg.0.log /home/megabrutal

[Touch-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade

2018-05-19 Thread MegaBrutal
I've made a live bootable pendrive to test the issue. I've found that it's not present when I boot a live OS, so something must have gone wrong during the upgrade. I've attached glxinfo outputs. thinkpad-glxinfo-livecd.txt: How it looks like when I boot from USB drive. It's normal. OpenGL

[Touch-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade

2018-05-19 Thread MegaBrutal
** Attachment added: "thinkpad-glxinfo-normalboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+attachment/5141597/+files/thinkpad-glxinfo-normalboot.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade

2018-05-19 Thread MegaBrutal
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1770913 Title: Software rendering is forced

[Touch-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)

2018-05-22 Thread MegaBrutal
I'm not using oibaf. I used to use it, but uninstalled it with ppa-purge, but this problem is present regardless of oibaf is installed. ** Changed in: mesa (Ubuntu) Status: Invalid => New ** Changed in: xorg-server (Ubuntu) Status: Invalid => New -- You received this bug

[Touch-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade

2018-05-18 Thread MegaBrutal
** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1770913 Title: Software rendering is forced after

[Touch-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)

2018-05-20 Thread MegaBrutal
How can I switch to Wayland? Contrary to the articles those tell otherwise, I have no option to select it on the login screen. Anyway, 17.10 worked fine with Wayland, so switching back to Wayland might probably help. -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)

2018-06-02 Thread MegaBrutal
# LANG=C apt-cache policy libnvidia-gl-390 libnvidia-gl-390: Installed: 390.48-0ubuntu3 Candidate: 390.48-0ubuntu3 Version table: *** 390.48-0ubuntu3 500 500 http://hu.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages 100 /var/lib/dpkg/status # LANG=C dpkg -l

[Touch-packages] [Bug 1798840] Re: Night Light is not functioning

2019-11-04 Thread MegaBrutal
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1798840 Title: Night Light is not functioning Status in gnome-control-center package in Ubuntu:

[Touch-packages] [Bug 1798840] Re: Night Light is not functioning

2019-11-04 Thread MegaBrutal
Now I found out that it depends on whether I login with Xorg or Wayland. Night Light works with Xorg, but doesn't with Wayland. I honestly don't remember whether I was running Disco with Xorg or Wayland, most probably I just went with the default. My guess is that Disco used Xorg by default and

[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-21 Thread MegaBrutal
Hi Steve, Julian, Łukasz, everyone, Sorry that I didn't test the package on time – my life circumstances have significantly changed since I reported this bug, nowadays I don't have enough free time to do as much testing as I did back in the day. I've been using the workaround ever since then,

[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-22 Thread MegaBrutal
Sorry, I didn't actually test Focal and Groovy. Xenial will be supported for about a year, so I think it worth to fix it there as well; however it's relative what worth to fix and what not, as most users probably left Xenial behind already or applied a workaround if they were ever affected by