[Touch-packages] [Bug 1713391] Re: glib-compile-schemas invalid free in per session override
It was only showing this core dump when installing package with apt before. but
after upgrade to latest packages today (apt update && apt full-upgrade), I
can't login to GDM (black screen).
The workaround is remove the package sogoupinyin, which provide this file
/usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override
but now I can't use the best Chinese pinyin IME on linux...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1713391
Title:
glib-compile-schemas invalid free in per session override
Status in glib2.0 package in Ubuntu:
Triaged
Bug description:
reinstall nautilus error with package sogoupinyin
# sudo nautilus
sys:1: PyGIWarning: Nautilus was imported without specifying a version
first. Use gi.require_version('Nautilus', '3.0') before import to
ensure that the right version gets loaded.
** Message: Init Stock Icons
(nautilus:10235): GLib-GIO-ERROR **: Settings schema
'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'
#sudo apt-get install --reinstall nautilus nautilus-share nautilus-data
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
正在读取软件包列表... 完成
正在分析软件包的依赖关系树
正在读取状态信息... 完成
升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
需要下载 0 B/3,298 kB 的归档。
解压缩后会消耗 0 B 的额外空间。
您希望继续执行吗？ [Y/n] y
(正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb ...
正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb ...
正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb ...
正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb ...
正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb ...
正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb ...
正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb ...
正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
*** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double
free or corruption (fasttop): 0x58242808 ***
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
/lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
/lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
=== Memory map:
5659b000-565a5000 r-xp 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
565a6000-565a7000 r--p a000 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
565a7000-565a8000 rw-p b000 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
58113000-5829 rw-p 00:00 0
[heap]
f6e0-f6e21000 rw-p 00:00 0
f6e21000-f6f0 ---p 00:00 0
f6f75000-f712b000 r--p 002da000 08:01 25170585
/usr/lib/locale/locale-archive
f712b000-f732b000 r--p 08:01 25170585
/usr/lib/locale/locale-archive
f732b000-f732d000 rw-p 00:00 0
f732d000-f7346000 r-xp 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7346000-f7347000 r--p 00018000 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7347000-f7348000 rw-p 00019000 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7348000-f734a000 rw-p 00:00 0
f734a000-f73c1000 r-xp 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c1000-f73c2000 r--p 00076000 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c2000-f73c3000 rw-p 00077000 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c3000-f7576000 r-xp 08:01 50856273
/lib/i386-linux-gnu/libc-2.24.so
f7576000-f7577000 ---p 001b3000
[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily
jarod@ubuntu-pc:~$ ll /etc/resolv.conf -rw-r--r-- 1 root root 78 Aug 28 09:38 /etc/resolv.conf jarod@ubuntu-pc:~$ cat /etc/resolv.conf # Generated by NetworkManager nameserver 114.114.114.114 # this entry is manually add by me nameserver 127.0.1.1 jarod@ubuntu-pc:~$ systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2017-08-28 09:44:24 CST; 1 day 3h ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Main PID: 3137 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 4915) CGroup: /system.slice/systemd-resolved.service └─3137 /lib/systemd/systemd-resolved Aug 28 09:44:24 ubuntu-pc systemd[1]: Starting Network Name Resolution... Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: Positive Trust Anchors: Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.i Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: Using system hostname 'ubuntu-pc'. Aug 28 09:44:24 ubuntu-pc systemd[1]: Started Network Name Resolution. -- 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/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Status in netcfg package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily
update to systemd (234-2ubuntu9) doesn't help, after reboot I still need manually add nameserver to /etc/resolve.conf -- 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/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Status in netcfg package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1674568] Re: depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory
same error. $ ls /boot/ abi-4.10.0-22-generic initrd.img-4.10.0-22-generic initrd.img-4.4.0-14-generic initrd.img-4.4.0-8-generic memtest86+_multiboot.bin config-4.10.0-22-generic initrd.img-4.4.0-10-generic initrd.img-4.4.0-15-generic initrd.img-4.4.0-9-generic System.map-4.10.0-22-generic efi initrd.img-4.4.0-12-generic initrd.img-4.4.0-2-generic memtest86+.bin vmlinuz-4.10.0-22-generic grub initrd.img-4.4.0-13-generic initrd.img-4.4.0-7-generic memtest86+.elf $ ls /var/lib/initramfs-tools/ 4.10.0-22-generic 4.4.0-12-generic 4.4.0-14-generic 4.4.0-2-generic 4.4.0-7-generic 4.4.0-9-generic 4.4.0-10-generic 4.4.0-13-generic 4.4.0-15-generic 4.4.0-4-generic 4.4.0-8-generic all kernel version except 4.10.0-22-generic already deleted -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1674568 Title: depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory Status in apt package in Ubuntu: Confirmed Bug description: Please affect that report to the real package; i've chosen apt by default as i've no idea about the faulty one. Doing some daily upgrades as usual, and have seen that curious error while setting 'initramfs': Setting up linux-firmware (1.164) ... update-initramfs: Generating /boot/initrd.img-4.10.0-14-generic update-initramfs: Generating /boot/initrd.img-4.10.0-13-generic update-initramfs: Generating /boot/initrd.img-4.8.0-25-generic WARNING: missing /lib/modules/4.8.0-25-generic Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0-0-generic WARNING: missing /lib/modules/4.8.0-0-generic Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-0-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.builtin: No such file or directory That ZZ installation indeed only has 4.10 kernels installed, and is often checked for cleaning (autoremove/bleachbit). Packages are always purged when removed. So i wonder why and which process/script has left a crappy /boot/ list of initrd.img-4.8* to produce the errors above. oem@u64:~$ ls -la /boot/ total 142448 drwxr-xr-x 4 root root 4096 Mar 21 06:24 . drwxr-xr-x 24 root root 4096 Mar 20 19:13 .. -rw-r--r-- 1 root root 1442575 Mar 9 14:16 abi-4.10.0-13-generic -rw-r--r-- 1 root root 1442782 Mar 9 21:30 abi-4.10.0-14-generic -rw-r--r-- 1 root root 204890 Mar 9 14:16 config-4.10.0-13-generic -rw-r--r-- 1 root root 204890 Mar 9 21:30 config-4.10.0-14-generic drwxr-xr-x 3 root root 4096 Mar 20 2016 efi drwxr-xr-x 5 root root 4096 Mar 20 19:17 grub -rw-r--r-- 1 root root 49676849 Mar 21 06:24 initrd.img-4.10.0-13-generic -rw-r--r-- 1 root root 49672961 Mar 21 06:23 initrd.img-4.10.0-14-generic -rw-r--r-- 1 root root 10017268 Mar 21 06:24 initrd.img-4.8.0-0-generic -rw-r--r-- 1 root root 10017066 Mar 21 06:24 initrd.img-4.8.0-25-generic -rw-r--r-- 1 root root 182704 Jan 28 2016 memtest86+.bin -rw-r--r-- 1 root root 184380 Jan 28 2016 memtest86+.elf -rw-r--r-- 1 root root 184840 Jan 28 2016 memtest86+_multiboot.bin -rw--- 1 root root 3715891 Mar 9 14:16 System.map-4.10.0-13-generic -rw--- 1 root root 3716749 Mar 9 21:30 System.map-4.10.0-14-generic -rw--- 1 root root 7558928 Mar 9 14:16 vmlinuz-4.10.0-13-generic -rw--- 1 root root 7563024 Mar 9 21:30 vmlinuz-4.10.0-14-generic ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-firmware 1.164 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 21 06:28:04 2017 Dependencies: PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Touch-packages] [Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial
Last night I ran into the same problem. I upgraded from 12.04 LTS to 16.04.1 LTS Server and got stuck at boot. The last message complained about a UUID not being present. It turned out it was the /usr FS. Doing an "lvm lvscan" from the initrd prompt showed all but one LVs inactive. The only one active was bootvg/root. I then booted via rescue system and added "lvm vgchange -ay" in /usr/share/initramfs-tools/scripts/local-top/lvm2 right before "exit 0". After running "update-initramfs -k all -c" and rebooting the server got up again. The bootvg is on a RAID1 disk controlled via mdadm. mdadm --detail /dev/md1 /dev/md1: Version : 1.2 Creation Time : Sat Dec 20 16:49:58 2014 Raid Level : raid1 Array Size : 971924032 (926.90 GiB 995.25 GB) Used Dev Size : 971924032 (926.90 GiB 995.25 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Update Time : Mon Jan 23 09:50:47 2017 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : XXX:1 UUID : :::814e Events : 21001 Number Major Minor RaidDevice State 0 8 190 active sync /dev/sdb3 2 831 active sync /dev/sda3 pvs PV VG Fmt Attr PSize PFree /dev/md1 bootvg lvm2 a-- 926.90g 148.90g The /boot FS is on sda1/sdb1 also via RAID1 sda2 and sda2 are swap fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x Device Boot StartEndSectors Size Id Type /dev/sda1 204810260471024000 500M fd Linux raid autodetect /dev/sda2 1026048941465583886084G 82 Linux swap / Solaris /dev/sda3 9414656 1953525167 1944110512 927G fd Linux raid autodetect lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 dpkg -l lvm2 ii lvm2 2.02.133-1ubuntu amd64Linux Logical Volume Manager -- 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/1573982 Title: LVM boot problem - volumes not activated after upgrade to Xenial Status in lvm2 package in Ubuntu: Confirmed Bug description: Soon after upgrade to Xenial (from 15.10) the boot process got broken. I'm using LVM for /root swap and other partitions. === The current behaviour is: When I boot short after the Grub login screen I'm getting log messages like: --- Scanning for Btrfs filesystems resume: Could not state the resume device file: '/dev/mapper/VolGroup' Please type in the full path... --- Then I press ENTER, for a few minutes some errors about floppy device access are raised (for some reason it tries to scan fd0 when floppy drive is empty). And then: --- Gave up waiting for root device. Common problems: ... ... ALERT! UUID=xxx-xxx does not exist. Dropping to a shell. --- From the BusyBox shell I managed to recover the boot by issuing "lvm vgchange -ay", then exit and then boot continues fine (all LVM file systems are successfully mounted). === One workaround so far is creating /etc/initramfs-tools/scripts/local-top/lvm2-manual script doing "lvm vgchange -ay". But I'm looking for cleaner solution. Boot used to work fine with 15.10. Actually the first boot after upgrading to Xenial actually worked OK too, I'm not sure what might changed meanwhile (I've been fixing some packages installation since mysql server upgrade has failed). === # lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1573982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
