[Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
With upstart-sysv, I have now observed a spurious RAID1 verify following a reboot after an unrelated apt upgrade (libc stuff). It's the only spurious RAID1 verify that I have observed so far with upstart-sysv. So upstart-sysv is not perfect, but still better than systemd-sysv regarding these issues. Also, after one reboot, I got my ext4 rootfs mounted ro without any apparent reason (no errors in the logs). Everything came back to normal after another reboot. I think I will try Debian, CentOS, and maybe Windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
I still get the same issues with a fully updated Ubuntu Server 16.04.1 LTS (Linux 4.4.0-45-generic). The patch from https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1320402/comments/13 does not seem to have any effect on these issues. I have also tried the latest mainline kernel build from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D , as suggested in https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1320402 : Linux wssrv1 4.8.4-040804-generic #201610220733 SMP Sat Oct 22 11:35:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux With or without the patch indicated above, this kernel seems to fix the spurious verify issue (so far...), but not the hanging reboot and poweroff. This is an unmaintained kernel intended for debug purposes and not for production anyway. I attach a hanging reboot log with Linux 4.8.4-040804-generic and the patch indicated above, with dynamic debug enabled in drivers/md/*. It hangs when remounting '/' read-only, still in the md kworker. Then, I tried to install upstart-sysv to see if getting rid of systemd helps, and it does. With upstart-sysv, all the issues described here seem to be fixed with Linux 4.4.0-45-generic and no patches. This seems to confirm that these issues are caused by systemd. However, I don't know how reliable and tested upstart-sysv is on Ubuntu Server 16.04.1 LTS, so this might possibly be an issue for a production server. I would prefer to keep working with systemd. ** Attachment added: "reboot-md-dyn-debug-patch-4.8.4.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+attachment/4767751/+files/reboot-md-dyn-debug-patch-4.8.4.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582046] Re: Missing Lubuntu Plymouth logo
I confirm that plymouth-theme-lubuntu-logo 0.61.1 from xenial-proposed fixes this bug for me. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582046 Title: Missing Lubuntu Plymouth logo To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-artwork/+bug/1582046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587142] Re: Reboot hangs once RAID1 resynced
The shutdown now also hangs during a resync. So it behaves inconsistently. I update the subject and the description to reflect this. ** Summary changed: - Reboot hangs once RAID1 resynced + Shutdown hangs in md kworker after "Reached target Shutdown." ** Description changed: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). - If the RAID volume is recovering or resyncing for whatever reason, then - `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had - to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld - lvm2-monitor` in order to consistently get that). However, once the - recovery/resync is complete and clean, the reboot and poweroff commands - above hang forever after "Reached target Shutdown.". Note that issuing - `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not - help. + If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. + [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 from checkpoint. May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device /dev/md/Volume0 - I attach screenshots of the hanging shutdown log after a `sudo sh -c - 'echo 8 > /proc/sys/kernel/printk'`. The second screenshot shows that - the kernel has deadlocked in md_write_start(). Note that `sudo systemctl - start debug-shell` is unusable on this machine at this point because - Ctrl+Alt+F9 brings tty9 without any keyboard.
[Bug 1587142] Re: Reboot hangs once RAID1 resynced
** Attachment added: "shutdown-log-part2.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+attachment/4673088/+files/shutdown-log-part2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587142 Title: Reboot hangs once RAID1 resynced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587142] [NEW] Reboot hangs once RAID1 resynced
Public bug reported: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 from checkpoint. May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device /dev/md/Volume0 I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 > /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without any keyboard. I have also tried with much lower values for vm.dirty_background_ratio and vm.dirty_ratio, but to no avail. Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not help either. More information below: $ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 $ uname -a Linux wssrv1 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy systemd systemd: Installed: 229-4ubuntu6 Candidate: 229-4ubuntu6 Version table: *** 229-4ubuntu6 500 500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages $ cat /proc/mdstat Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sda[1] sdb[0] 976759808 blocks super external:/md127/0 [2/2] [UU]
[Bug 1582046] [NEW] Missing Lubuntu Plymouth logo
Public bug reported: Source package: lubuntu-artwork 0.61 Binary package: plymouth-theme-lubuntu-logo 0.61 Description:Ubuntu 16.04 LTS Release:16.04 There is an empty screen during boot instead of the Lubuntu logo. The cause of this issue is that the following files are not installed: /usr/share/plymouth/themes/lubuntu-logo/lubuntu_logo.png /usr/share/plymouth/themes/lubuntu-logo/password_field.png /usr/share/plymouth/themes/lubuntu-logo/progress_dot_off.png /usr/share/plymouth/themes/lubuntu-logo/progress_dot_on.png In order to fix this issue, in the source package, the files src/lib/plymouth/themes/lubuntu-logo/* should be moved to src/usr/share/plymouth/themes/lubuntu-logo/ . ** Affects: lubuntu-artwork (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582046 Title: Missing Lubuntu Plymouth logo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1582046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074468] Re: KDiff3 won't save its settings
Still broken in Ubuntu 15.10. The settings can be saved the first time KDiff3 is launched following install. The following times, they can no longer be saved. ** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074468 Title: KDiff3 won't save its settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/1074468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074468] Re: KDiff3 won't save its settings
Still broken in Ubuntu 15.04. ** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074468 Title: KDiff3 won't save its settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/1074468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
This appears to be fixed for me in Ubuntu 14.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074468] Re: KDiff3 won't save its settings
Still broken in Ubuntu 14.10. ** Tags added: utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074468 Title: KDiff3 won't save its settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/1074468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187885] Re: UBI volume autoresize fails
Good news: I can't reproduce this issue with Ubuntu 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187885 Title: UBI volume autoresize fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1187885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074468] Re: KDiff3 won't save its settings
Still broken in Ubuntu 14.04. ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074468 Title: KDiff3 won't save its settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/1074468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
Still broken in Ubuntu 14.04. ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
I have just tested again with your files, and I don't experience your issue. From your screenshot, you seem to be using a theme, a skin or something, and not the default Ubuntu layout. Maybe this disturbs KDiff3 a bit more, or there is something else specific to your machine triggering the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
So maybe it's your test files that allow to show the issue and not mine, or there is something depending on some machine settings. How many tabs or spaces are there before ab and ac in your test files? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
Hi Andrew, Are you sure about your font settings? On my 64-bit Ubuntu 13.10 machine, Monospace normal 10 is still a valid workaround for this issue with KDiff3 4.11.5 0.9.97-1ubuntu1. Regards, Benoît -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
With Ubuntu 13.10, all the issues described in this KDiff3 bug are back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187885] Re: UBI volume autoresize fails
Hi Joseph, I have just performed the test that you asked for, and the result is the same. I update the tags accordingly. BR ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187885 Title: UBI volume autoresize fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1187885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187885] [NEW] UBI volume autoresize fails
Public bug reported: Steps to reproduce: - Create some 'target' folder containing any files. - `mkfs.ubifs -e 0x1f800 -c 984 -m 0x800 -F -x lzo -d target -o rootfs.ubifs`. - Create the following 'ubinize.cfg' file: --- [ubifs] mode=ubi vol_id=0 vol_type=dynamic vol_name=rootfs vol_alignment=1 vol_flags=autoresize image=rootfs.ubifs --- - `ubinize -m 0x800 -p 0x2 -s 0x200 -o rootfs.ubi ubinize.cfg`. - `sudo modprobe nandsim first_id_byte=0x2c second_id_byte=0xf1 third_id_byte=0x80 fourth_id_byte=0x95`. - `sudo nandwrite -p /dev/mtd0 rootfs.ubi`. - `sudo modprobe ubi mtd=0`. Result: - After last command line: ERROR: could not insert 'ubi': No space left on device. - In dmesg: --- [47346.410763] [nandsim] warning: read_byte: unexpected data output cycle, state is STATE_READY return 0x0 [47346.410767] [nandsim] warning: read_byte: unexpected data output cycle, state is STATE_READY return 0x0 [47346.410769] [nandsim] warning: read_byte: unexpected data output cycle, state is STATE_READY return 0x0 [47346.410770] [nandsim] warning: read_byte: unexpected data output cycle, state is STATE_READY return 0x0 [47346.410774] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64 [47346.410789] flash size: 128 MiB [47346.410790] page size: 2048 bytes [47346.410792] OOB area size: 64 bytes [47346.410793] sector size: 128 KiB [47346.410794] pages number: 65536 [47346.410795] pages per sector: 64 [47346.410796] bus width: 8 [47346.410797] bits in sector size: 17 [47346.410799] bits in page size: 11 [47346.410800] bits in OOB size: 6 [47346.410801] flash size with OOB: 135168 KiB [47346.410802] page address bytes: 4 [47346.410803] sector address bytes: 2 [47346.410804] options: 0x8 [47346.410996] Scanning device for bad blocks [47346.411004] [nandsim] warning: write_byte: command (0x0) wasn't expected, expected state is STATE_READY, ignore previous states [47346.416700] Creating 1 MTD partitions on NAND 128MiB 3,3V 8-bit: [47346.416704] 0x-0x0800 : NAND simulator partition 0 [47365.434784] UBI: default fastmap pool size: 50 [47365.434791] UBI: default fastmap WL pool size: 25 [47365.434793] UBI: attaching mtd0 to ubi0 [47365.436872] UBI: scanning is finished [47365.437321] UBI error: autoresize: cannot auto-resize volume 0 [47365.437399] UBI error: ubi_init: cannot attach mtd0 [47365.437954] UBI error: ubi_init: UBI error: cannot initialize UBI, error -28 --- Expected result: no error, UBI probed successfully. This test worked fine with some previous Ubuntu versions. Note that the issue disappears if 'vol_flags=autoresize' is removed from ubinize.cfg, but setting vol_size instead is not an optimal solution. This looks very much like the issue described here: http://lists.infradead.org/pipermail/linux-mtd/2012-August/043108.html ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-23-generic 3.8.0-23.34 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bthebaudeau 2634 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Jun 5 20:11:42 2013 HibernationDevice: RESUME=UUID=7893e31d-56e2-480a-b91f-a5143a766ec0 InstallationDate: Installed on 2013-06-03 (2 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform MarkForUpload: True ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic root=UUID=d55977dd-09cd-4a6f-aa07-27a3b9272183 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-23-generic N/A linux-backports-modules-3.8.0-23-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu)
[Bug 1074468] Re: KDiff3 won't save its settings
This issue no longer exists in Ubuntu 13.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074468 Title: KDiff3 won't save its settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/1074468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
Hi Joachim, Here is the status for me on Ubuntu 13.04 with Monospace Regular 9.0: - The issue of overlapping colored characters in the diff view is fixed. - The issue of the cursor displayed at a wrong position is still present. - The issue of the wrong width displayed for tab characters with the text from my screenshot in comment #4 (the second line starts with 6 tabs and 1 space) is still a little bit present in the A/B/C views (there is an offset of about 2 pixels between both lines), but fixed in the Output view. - The issue of the black pixel left when blinking in the Output view is fixed. Best regards, Benoît -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074468] Re: KDiff3 won't save its settings
For some reason, this bug is now back in my Ubuntu 13.04. I don't know what may have changed since my first tests. Could it be that I have first tested from the launcher, then from the command line? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074468 Title: KDiff3 won't save its settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/1074468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1006027] Re: Meld fullscreen status bar is transparent
This is fixed in Ubuntu 12.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1006027 Title: Meld fullscreen status bar is transparent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meld/+bug/1006027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
Hi Joachim, This bug is still present in Ubuntu 12.10, for both KDiff3 and Kate. When will your fix be applied? Best regards, Benoît -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074468] [NEW] KDiff3 won't save its settings
Public bug reported: This is a consistent issue that occurs in my Ubuntu 12.10. The steps to reproduce the issue are: - launch kdiff3, - go to the menu Settings Configure kdiff3..., - change something, e.g. uncheck Directory Backup files (.orig), - click the OK button, - go to the menu Settings Configure kdiff3..., - check the changes made - OK, still there, - quit kdiff3, - launch kdiff3, - go to the menu Settings Configure kdiff3..., - check the changes made - KO, vanished, were not saved to file (e.g. Directory Backup files (.orig) is still checked). After these steps, the contents of ~/.kde/share/config/kdiff3rc (access rights: 0600) are unchanged. However, if this file is edited to apply manually the desired settings, and if kdiff3 is then launched, the new settings are taken into account. Hence, this is really a settings saving issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: kdiff3 0.9.96-4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Fri Nov 2 20:02:43 2012 InstallationDate: Installed on 2012-10-31 (2 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kdiff3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kdiff3 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074468 Title: KDiff3 won't save its settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/1074468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074468] Re: KDiff3 won't save its settings
Note that I've uncommented the line setting umask to 022 in my .profile, but I don't think that's related since chmod'ing ~/.kde/share/config/kdiff3rc to 0777 does not help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074468 Title: KDiff3 won't save its settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/1074468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
Thanks Joachim, everything is now fixed for me. Just some nit picking: When merging files, the cursor now leaves a black pixel when blinking. This pixel follows the cursor, so it's not a big problem. Best regards, Benoît -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
Hi Joachim, I've just tested your package with Monospace Regular 9.0. The issue of overlapping colored characters in the diff view is fixed. The issue of the cursor displayed at a wrong position is fixed. I still have an issue with the width displayed for tab characters with the text from my screenshot in comment #4 (the second line starts with 6 tabs and 1 space). I get exactly the same result as before. However, if I replace each tab with 8 spaces in this text, then the display is correct contrary to before. Your package still does not display tabs as exactly 8-space wide. Also, when you will have fixed tabs, can you do the same fix for Kate and Kdevelop? Best regards, Benoît -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
Yes, it's the same bug. It's what I explained in comment 4 about the cursor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
I'm affected by this bug too. I have also noticed that it depends on the font and on the font size. For me, it occurs whether Kdiff3 is run from Unity 2D/3D or Gnome Classic/Shell. My Ubuntu 12.04 is installed as a VMware Player guest within a Windows 7 host. The worst consequence of this bug for me is that if you edit a modification during a manual merge, the cursor is not showing where you are actually typing, but a few characters before. This is a nightmare to use. This bug may be common to all KDE applications: With Kate or Kdevelop, the same column is not painted at the same position for all lines (using mono fonts). E.g., you can see on the attached screenshot that int a and int b are not aligned albeit on the same column. It also depends on the font and on the font size. ** Attachment added: kdevelop_broken_mono.png https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+attachment/3168019/+files/kdevelop_broken_mono.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1006027] [NEW] Meld fullscreen status bar is transparent
Public bug reported: Package: meld Ubuntu release: 12.04 Package version: 1.5.3-1ubuntu1 Steps to reproduce: - Start meld in windowed mode - OK. - Set meld to fullscreen mode - OK. - Quit meld - OK. - Start meld - meld starts in fullscreen mode as expected, but its status bar is transparent instead of being painted (see attached screenshot). Cycling between windowed and fullscreen modes fixes the painting. My Ubuntu 12.04 is installed as a VMware Player guest within a Windows 7 host. ** Affects: meld (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1006027 Title: Meld fullscreen status bar is transparent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meld/+bug/1006027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1006027] Re: Meld fullscreen status bar is transparent
** Attachment added: meld_broken_fullscreen.png https://bugs.launchpad.net/bugs/1006027/+attachment/3168087/+files/meld_broken_fullscreen.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1006027 Title: Meld fullscreen status bar is transparent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meld/+bug/1006027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999925] Re: KDiff3 font rendering of changed text broken
According to the few tests I have performed, there seems to be one particular size specific to each font that makes this rendering bug invisible. For my configuration, this size is 10.0 for Monospace Regular, and 9.0 for Ubuntu Mono Regular. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/25 Title: KDiff3 font rendering of changed text broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdiff3/+bug/25/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
