[Bug 2059853] [NEW] apt amd64 2.7.14 is missing on Ubuntu Noble?
Public bug reported: I can not find the apt amd64 version 2.7.14 on Ubuntu Noble. It seems apt only exists for non-amd64 architecture: https://packages.ubuntu.com/search?suite=noble=apt noble (admin): commandline package manager 2.7.14: arm64 armhf i386 ppc64el riscv64 s390x I can not find any docs stating this. Is it a bug or ? Thank you very much. Steven ** Affects: apt (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/2059853 Title: apt amd64 2.7.14 is missing on Ubuntu Noble? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2059853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955446] [NEW] incompatible library version - /usr/lib/libdislocker.so on Ubuntu Jammy
Public bug reported: The latest version of dislocker on Ubuntu Jammy is 0.7.3-2ubuntu1: # dpkg -l dislocker Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--> ii dislocker 0.7.3-2ubuntu1 amd64read/write encrypted BitLocker v> However, when running "dislocker-find", it gives: Traceback (most recent call last): 2: from /usr/bin/dislocker-find:26:in `' 1: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': incompatible library version - /usr/lib/libdislocker.so (LoadError) There is no such issue when running dislocker-find (from dislocker 0.7.3-2) on Ubuntu Impish (21.10), it gives the result correctly: # dislocker-find No BitLocker volume found. ** Affects: dislocker (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/1955446 Title: incompatible library version - /usr/lib/libdislocker.so on Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dislocker/+bug/1955446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829331] Re: Grub regexp command does not work in secure boot mode
Thank you very much. I confirmed it's working on Ubuntu 20.04, and the grub is 2.04-1ubuntu26. Steven -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829331 Title: Grub regexp command does not work in secure boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-efi-amd64-signed/+bug/1829331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854438] [NEW] Debootstrap Ubuntu Focal fails due to an issue in console-common 0.7.91
Public bug reported: Dear maintainer, The package console-common 0.7.91 causes debootstrap failing to bootstrap a basic Focal system. Here is how to reproduce this issue: $ debootstrap --verbose --arch=amd64 --components=main,universe --include=console-common focal focal-chroot http://free.nchc.org.tw/ubuntu ... I: Unpacking console-common... W: Failure while installing base packages. This will be re-attempted up to five times. W: See /home/steven/tmp/focal-chroot/debootstrap/debootstrap.log for details (po ssibly the package /var/cache/apt/archives/console-common_0.7.91_all.deb is at fault) ... I tried to manually install the package with debuging option in the chroot environment. Here is the result: # dpkg -i --debug=72200 /var/cache/apt/archives/console-common_0.7.91_all.deb (Reading database ... 11993 files and directories currently installed.) Preparing to unpack .../console-common_0.7.91_all.deb ... D02: trigproc_activate_packageprocessing pkg=console-common:all locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory dpkg: error processing archive /var/cache/apt/archives/console-common_0.7.91_all.deb (--install): new console-common package pre-installation script subprocess returned error exit status 10 D02: post_script_tasks - ensure_diversions D02: post_script_tasks - trig_incorporate D02: post_script_tasks - ensure_diversions D02: post_script_tasks - trig_incorporate D01: trigproc_run_deferred Errors were encountered while processing: /var/cache/apt/archives/console-common_0.7.91_all.deb Let me know if you need more info. Thank you very much. Steven ** Affects: console-common (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/1854438 Title: Debootstrap Ubuntu Focal fails due to an issue in console-common 0.7.91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-common/+bug/1854438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
I have tested Ubuntu Focal with systemd 243-3ubuntu1: https://launchpad.net/ubuntu/+source/systemd/243-3ubuntu1 and the issue I have reported in Bug 1849608, which is marked as the duplicate of this bug, is gone now. Hence I confirmed the fix works here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849608] Re: systemd resolv should separate the output of stdout and stderr
BTW, forgot to mention, after applying the patch in my system, I have to reboot the system then run "dhclient -v" so that the stale status of previous dhclient won't confuse it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849608 Title: systemd resolv should separate the output of stdout and stderr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1849608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849608] [NEW] systemd resolv should separate the output of stdout and stderr
Public bug reported: The file /etc/dhcp/dhclient-enter-hooks.d/resolved provided by systemd (242-7ubuntu3) causes the dhclient failing to get DNS due to systemd-resolved is not run. This issue can be reproduced on Ubuntu Eoan: == root@eoan:~# dhclient -v Internet Systems Consortium DHCP Client 4.4.1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/ens224/00:0c:29:92:d4:da Sending on LPF/ens224/00:0c:29:92:d4:da Listening on LPF/ens192/00:0c:29:92:d4:d0 Sending on LPF/ens192/00:0c:29:92:d4:d0 Listening on LPF/ens160/00:0c:29:92:d4:c6 Sending on LPF/ens160/00:0c:29:92:d4:c6 Sending on Socket/fallback DHCPDISCOVER on ens224 to 255.255.255.255 port 67 interval 3 (xid=0x6d9fb33d) DHCPDISCOVER on ens192 to 255.255.255.255 port 67 interval 3 (xid=0xeb8fda26) DHCPREQUEST for 192.168.120.4 on ens160 to 255.255.255.255 port 67 (xid=0x6d39545d) DHCPACK of 192.168.120.4 from 192.168.120.254 (xid=0x5d54396d) RTNETLINK answers: File exists d41d8cd98f00b204e9800998ecf8427e /run/systemd/resolved.conf.d/isc-dhcp-v4-ens160.conf md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens160.conf: No such file or directory 5025823d750dda1f3f15e306c4a0afce /run/systemd/resolved.conf.d/isc-dhcp-v4-ens160.conf md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens160.conf: No such file or directory bound to 192.168.120.4 -- renewal in 111 seconds. root@eoan:~# resolvectl status |grep DNS MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no == Attached please find the patch for this. The output for md5sum in the hook file resolv should separate the stdout and stderr so it won't compare the wrong data. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Patch added: "resolved.patch" https://bugs.launchpad.net/bugs/1849608/+attachment/5299633/+files/resolved.patch ** Package changed: grub-efi-amd64-signed (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849608 Title: systemd resolv should separate the output of stdout and stderr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1849608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829331] Re: Grub regexp command does not work in secure boot mode
OK, for ubuntu-19.04-live-server-amd64.iso booting in secure boot mode, I found more commands are not working, at least including: lspci probe md5sum play sha1sum tr usb videoinfo While the following are working: ls cat echo help reboot I am wondering is this due to some purpose about security? Or? Thank you very much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829331 Title: Grub regexp command does not work in secure boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-efi-amd64-signed/+bug/1829331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829331] Re: Grub regexp command does not work in secure boot mode
I repeated the above steps for ubuntu-18.04.2-live-server-amd64.iso, and got the same result. The regexp command in the grub shell does not work in secure boot mode. However, it does work in non-secure boot mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829331 Title: Grub regexp command does not work in secure boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-efi-amd64-signed/+bug/1829331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829331] Re: Grub regexp command does not work in secure boot mode
** Attachment added: "Grub command regexp works in the non-secure boot mode" https://bugs.launchpad.net/ubuntu/+source/grub-efi-amd64-signed/+bug/1829331/+attachment/5264191/+files/grub-working.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829331 Title: Grub regexp command does not work in secure boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-efi-amd64-signed/+bug/1829331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829331] [NEW] Grub regexp command does not work in secure boot mode
Public bug reported: Dear maintainer, The grub command "regexp" on Ubuntu 19.04 does not work in the secure boot mode, yet it works in the non-secure boot mode. Attached please find the screenshots about that. How to reproduce it? 1. Download Ubuntu 19.04 sever ISO file: https://www.ubuntu.com/download/server/thank-you?version=19.04=amd64 2. Boot in a machine with secure boot mode is enabled 3. In the grub menu, press "c" to enter grub shell 4. Run command: regexp --help and regexp -h Nothing is shown. Normally the usage about regexp will be prompted. However, if the above steps were repeated in the secure boot mode is DISABLED, it works. The usage prompt about regexp is shown. To compare that, I downloaded https://cdimage.debian.org/mirror/cdimage/buster_di_rc1-live/amd64/iso-hybrid/debian-live-buster-DI-rc1-amd64-standard.iso Then repeated the above steps in the secure boot mode enabled machine, it was working. The regexp usage prompt was shown. ** Affects: grub-efi-amd64-signed (Ubuntu) Importance: Undecided Status: New ** Attachment added: "The screenshot about grub command regexp NOT working in the grub shell in secure boot mode" https://bugs.launchpad.net/bugs/1829331/+attachment/5264190/+files/grub-not-working-sb.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829331 Title: Grub regexp command does not work in secure boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-efi-amd64-signed/+bug/1829331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586923] [NEW] Parted crashes with "Error in `parted': realloc(): invalid next size"
Public bug reported: I am using the parted from Xenial. When the command "paretd -s /dev/sda print" is run on my Macmini15, it crashes. If you need more info, please let me know. The details: # dpkg -l |grep parted ii libparted-fs-resize0:amd64 3.2-15 amd64disk partition manipulator - shared FS resizing library ii libparted2:amd64 3.2-15 amd64disk partition manipulator - shared library ii parted 3.2-15 amd64disk partition manipulator # parted -s /dev/sda print Model: ATA APPLE HDD HTS541 (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: *** Error in `parted': realloc(): invalid next size: 0x55fba192b660 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7feb41c77725] /lib/x86_64-linux-gnu/libc.so.6(+0x82bfa)[0x7feb41c82bfa] /lib/x86_64-linux-gnu/libc.so.6(realloc+0x179)[0x7feb41c83db9] /lib/x86_64-linux-gnu/libparted.so.2(xrealloc+0x16)[0x7feb42467fe6] parted(table_render+0xb6)[0x55fba09e2506] parted(+0x790d)[0x55fba09dc90d] parted(non_interactive_mode+0x92)[0x55fba09e2102] parted(main+0x1238)[0x55fba09db028] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7feb41c20830] parted(_start+0x29)[0x55fba09db1d9] === Memory map: 55fba09d5000-55fba09e7000 r-xp 07:00 8694 /sbin/parted 55fba0be7000-55fba0be8000 r--p 00012000 07:00 8694 /sbin/parted 55fba0be8000-55fba0be9000 rw-p 00013000 07:00 8694 /sbin/parted 55fba192-55fba19d rw-p 00:00 0 [heap] 7feb3800-7feb38021000 rw-p 00:00 0 7feb38021000-7feb3c00 ---p 00:00 0 7feb3f92f000-7feb3f945000 r-xp 07:00 8224 /lib/x86_64-linux-gnu/libgcc_s.so.1 7feb3f945000-7feb3fb44000 ---p 00016000 07:00 8224 /lib/x86_64-linux-gnu/libgcc_s.so.1 7feb3fb44000-7feb3fb45000 rw-p 00015000 07:00 8224 /lib/x86_64-linux- gnu/libgcc_s.so.1 7feb3fb45000-7feb4079d000 r--p 07:00 10189 /usr/lib/locale/locale-archive 7feb4079d000-7feb407a r-xp 07:00 8206 /lib/x86_64-linux-gnu/libdl-2.23.so 7feb407a-7feb4099f000 ---p 3000 07:00 8206 /lib/x86_64-linux-gnu/libdl-2.23.so 7feb4099f000-7feb409a r--p 2000 07:00 8206 /lib/x86_64-linux-gnu/libdl-2.23.so 7feb409a-7feb409a1000 rw-p 3000 07:00 8206 /lib/x86_64-linux-gnu/libdl-2.23.so 7feb409a1000-7feb40a0f000 r-xp 07:00 8305 /lib/x86_64-linux-gnu/libpcre.so.3.13.2 7feb40c0f000-7feb40c1 r--p 0006e000 07:00 8305 /lib/x86_64-linux-gnu/libpcre.so.3.13.2 7feb40c1-7feb40c11000 rw-p 0006f000 07:00 8305 /lib/x86_64-linux-gnu/libpcre.so.3.13.2 7feb40c11000-7feb40d19000 r-xp 07:00 8250 /lib/x86_64-linux-gnu/libm-2.23.so 7feb40d19000-7feb40f18000 ---p 00108000 07:00 8250 /lib/x86_64-linux-gnu/libm-2.23.so 7feb40f18000-7feb40f19000 r--p 00107000 07:00 8250 /lib/x86_64-linux-gnu/libm-2.23.so 7feb40f19000-7feb40f1a000 rw-p 00108000 07:00 8250 /lib/x86_64-linux-gnu/libm-2.23.so 7feb40f1a000-7feb40f32000 r-xp 07:00 8314 /lib/x86_64-linux-gnu/libpthread-2.23.so 7feb40f32000-7feb41131000 ---p 00018000 07:00 8314 /lib/x86_64-linux-gnu/libpthread-2.23.so 7feb41131000-7feb41132000 r--p 00017000 07:00 8314 /lib/x86_64-linux-gnu/libpthread-2.23.so 7feb41132000-7feb41133000 rw-p 00018000 07:00 8314 /lib/x86_64-linux-gnu/libpthread-2.23.so 7feb41133000-7feb41137000 rw-p 00:00 0 7feb41137000-7feb41156000 r-xp 07:00 8326 /lib/x86_64-linux-gnu/libselinux.so.1 7feb41156000-7feb41355000 ---p 0001f000 07:00 8326 /lib/x86_64-linux-gnu/libselinux.so.1 7feb41355000-7feb41356000 r--p 0001e000 07:00 8326 /lib/x86_64-linux-gnu/libselinux.so.1 7feb41356000-7feb41357000 rw-p 0001f000 07:00 8326 /lib/x86_64-linux-gnu/libselinux.so.1 7feb41357000-7feb41359000 rw-p 00:00 0 7feb41359000-7feb4136 r-xp 07:00 8322 /lib/x86_64-linux-gnu/librt-2.23.so 7feb4136-7feb4155f000 ---p 7000 07:00 8322 /lib/x86_64-linux-gnu/librt-2.23.so 7feb4155f000-7feb4156 r--p 6000 07:00 8322 /lib/x86_64-linux-gnu/librt-2.23.so 7feb4156-7feb41561000 rw-p 7000 07:00 8322 /lib/x86_64-linux-gnu/librt-2.23.so 7feb41561000-7feb4159d000
[Bug 1448164] Re: runit cannot be installed (Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused)
I have similar issue on Ubuntu 16.04 beta 2 (updated on Apr/5/2016): $ sudo apt-get install runit Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: socklog-run The following NEW packages will be installed: runit 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/102 kB of archives. After this operation, 503 kB of additional disk space will be used. Selecting previously unselected package runit. (Reading database ... 179854 files and directories currently installed.) Preparing to unpack .../runit_2.1.2-3ubuntu1_amd64.deb ... Unpacking runit (2.1.2-3ubuntu1) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up runit (2.1.2-3ubuntu1) ... start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused dpkg: error processing package runit (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for ureadahead (0.100.0-19) ... Errors were encountered while processing: runit E: Sub-process /usr/bin/dpkg returned an error code (1) $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" Even I followed https://bugs.launchpad.net/ubuntu/+source/runit/+bug/406621/comments/5 to remove git-all, the issue still remains. Steven -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448164 Title: runit cannot be installed (Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528861] Re: cryptsetup can not coexist with console-common
The final beta for Xenial will be released recently. However, this issue still remains. Package console-common still conflicts with plymouth and cryptsetup. Therefore if plymouth and cryptsetup are installed, there is no way "dpkg-reconfigure console-data" can be used to tune the keymap. Is that possible at least to make it like Debian that console-common can coexist with cryptsetup? Thanks. Steven -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528861 Title: cryptsetup can not coexist with console-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1528861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528861] Re: cryptsetup can not coexist with console-common
I found a side effect if console-common is not installed. There is a problem to run "dpkg-reconfigure console-data", i.e. when it's run, after selecting "Select keymap from arch list", nothing happens. Normally it should ask the "Keyboard layout family", then "Keyboard layout". This is how to reproduce it: 1. bootstrap an Ubuntu xenial environment: debootstrap --verbose --arch=amd64 --components=main,universe --exclude=console-common --include=console-data xenial xenial-chroot http://free.nchc.org.tw/ubuntu 2. chroot xenial-chroot 3. dpkg-reconfigure console-data 4. Select "Select keymap from arch list", then it just quits without asking "Keyboard layout family", and "Keyboard layout". Nothing happens. Any comments about this? Thanks. Steven. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528861 Title: cryptsetup can not coexist with console-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1528861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528861] Re: cryptsetup can not coexist with console-common
OK, got it. Thank you very much. Steven. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528861 Title: cryptsetup can not coexist with console-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1528861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528861] Re: cryptsetup can not coexist with console-common
Thanks. The reason we need to use install-keymap is it's easier to do that in unattended mode, i.e. e.g. to set the French keyboard, just use: install-keymap /usr/share/keymaps/i386/azerty/fr-latin9.kmap.gz So if console-common is obsolete, is that possible to use console-setup and keyboard-configuration to configure the keymap in unattended, non-interactive way? If so, that would be great. Appreciate. Steven. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528861 Title: cryptsetup can not coexist with console-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1528861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528861] [NEW] cryptsetup can not coexist with console-common
Public bug reported: The package cryptsetup can not coexist with console-common due to cryptsetup depends on plymouth. However, plymouth conflicts with console-common, so this makes the cryptsetup can not coexist with console-common. This does not happen on Debian Sid because cryptsetup on Debian does not depend on plymouth. We need console-common is because we need the program install-keymap from console-common for the live CD we want to create. # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" # apt-get install cryptsetup console-common Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: cryptsetup : Depends: plymouth but it is not going to be installed E: Unable to correct problems, you have held broken packages. Thanks. Steven. ** Affects: cryptsetup (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/1528861 Title: cryptsetup can not coexist with console-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1528861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] Re: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11
Somehow my bug report sent to intel-wired-...@lists.osuosl.org is never shown on the list. I sent twice, both of them just disappeared. I have successfully joined the mailing list a few days ago, and have received many emails from the list. Anyway, I did another test with Linux kernel 4.0.0-04-generic (from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/), and still has the same issue: === [1.615923] Modules linked in: psmouse e1000e(+) ptp pps_core mptsas(+) mptscsih mptbase scsi_transport_sas e1000(+) ahci libahci pata_acpi floppy [1.616113] CPU: 0 PID: 104 Comm: systemd-udevd Not tainted 4.0.0-04-generic #201504121935 [1.616211] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 05/20/2014 [1.616317] task: 880036919400 ti: 88003692c000 task.ti: 88003692c000 [1.616428] RIP: 0010:[c0103af4] [c0103af4] e1000e_cyclecounter_read+0xa4/0xc0 [e1000e] [1.616556] RSP: 0018:88003692fa68 EFLAGS: 00010246 [1.616678] RAX: RBX: 880036207860 RCX: [1.616998] RDX: RSI: RDI: 880036207848 [1.617130] RBP: 88003692fa68 R08: 0032 R09: [1.617265] R10: 0007 R11: 000f R12: 880036207848 [1.617405] R13: 13d49a0e5c5cbe0f R14: R15: [1.617547] FS: 7f26eb31e880() GS:88003fc0() knlGS: [1.617694] CS: 0010 DS: ES: CR0: 80050033 [1.617845] CR2: 7f26ec5d12d8 CR3: 36924000 CR4: 001407f0 [1.618024] Stack: [1.618178] 88003692fa98 810f0c4a 8800362048c0 8800362048c0 [1.618342] 880036204e38 88003692faf8 c010cff3 [1.618508] 000f 82fd5c48 88003692fad8 01a0c00eede6 [1.618678] Call Trace: [1.618858] [810f0c4a] timecounter_init+0x2a/0x60 [1.619621] [c010cff3] e1000e_config_hwtstamp+0x1d3/0x310 [e1000e] [1.620020] [c010d46f] e1000e_reset+0x1bf/0x550 [e1000e] [1.620200] [c010e55b] e1000_probe+0xa3b/0xc80 [e1000e] [1.620383] [81403c8e] local_pci_probe+0x4e/0xa0 [1.620566] [81404df5] ? pci_match_device+0xe5/0x110 [1.620958] [81404f19] __pci_device_probe+0xb9/0xf0 [1.621145] [81404f8a] pci_device_probe+0x3a/0x60 [1.621336] [8150fec1] really_probe+0x91/0x380 [1.621526] [81510337] driver_probe_device+0x47/0xa0 [1.621720] [8151043b] __driver_attach+0xab/0xb0 [1.621915] [81510390] ? driver_probe_device+0xa0/0xa0 [1.622112] [8150e21e] bus_for_each_dev+0x5e/0x90 [1.622311] [8150fa6e] driver_attach+0x1e/0x20 [1.622513] [8150f5f4] bus_add_driver+0x124/0x260 [1.622717] [81510d14] driver_register+0x64/0xf0 [1.622922] [c0128000] ? 0xc0128000 [1.623129] [8140400c] __pci_register_driver+0x4c/0x50 [1.623342] [c0128041] e1000_init_module+0x41/0x1000 [e1000e] [1.623556] [81002157] do_one_initcall+0xd7/0x200 [1.623773] [811c3605] ? __vunmap+0xa5/0xf0 [1.623991] [811df30d] ? kmem_cache_alloc_trace+0x19d/0x210 [1.624214] [817d8f8e] do_init_module+0x61/0x1ce [1.624971] [8110169e] load_module+0x49e/0x5f0 [1.625198] [810fe610] ? show_initstate+0x50/0x50 [1.625427] [8110194e] SyS_finit_module+0xae/0xd0 [1.625653] [817efccd] system_call_fastpath+0x16/0x1b [1.625877] Code: f8 d5 ff ff 8b 92 00 b6 00 00 89 d2 48 8b 8f f8 d5 ff ff 8b 89 04 b6 00 00 48 c1 e1 20 48 09 d1 31 d2 48 89 ce 48 29 c6 48 89 f0 49 f7 f1 48 89 c8 48 85 d2 75 c1 4c 39 d6 77 bc 5d c3 66 2e 0f [1.626368] RIP [c0103af4] e1000e_cyclecounter_read+0xa4/0xc0 [e1000e] [1.626595] RSP 88003692fa68 [1.626832] ---[ end trace d229bb7d4080d888 ]--- === -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] Re: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11
I just did a test with http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc7-vivid/linux-image-4.0.0-04rc7-generic_4.0.0-04rc7.201504061936_amd64.deb The e1000e issue still remains. The output of dmesg was attached. ** Attachment added: e1000e kernel oops with linux kernel 4.0.0-04rc7-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+attachment/4368076/+files/rc7.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] Re: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11
Same problem for the updated linux kernel 3.19.0-12.12-generic in Vivid repository. The output of dmesg was attached. ** Attachment added: e1000e kernel oops for linux kernel 3.19.0-12.12-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+attachment/4368088/+files/3.19.0-12.12-generic.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] Re: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11
I have reported this to e1000-devel: http://sourceforge.net/p/e1000/mailman/e1000-devel/thread/55234954.8030600%40nchc.org.tw/#msg33737691 Steven. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] Re: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11
OK, I will wait for another rc deb in http://kernel.ubuntu.com/~kernel-ppa/mainline/ then I will do a test again. Thanks. Steven. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] Re: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11
apport information ** Tags added: apport-collected ** Description changed: When I booted the daily build vivid iso from http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/ vivid-desktop-amd64.iso 31-Mar-2015 03:41 1.0G Desktop image for 64-bit PC (AMD64) computers (standard download) I got a kernel oops. The virtual machine is on VMware Workstation 11.1.0 for Linux with MS Windows 8.1 client, therefore the chipset for ethernet0 is e1000e shown in the *.vmx file: ethernet0.virtualDev = e1000e The oops is attached. + --- + ApportVersion: 2.17-0ubuntu1 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: + DistroRelease: Ubuntu 15.04 + HibernationDevice: RESUME=UUID=0baa6e3a-8e6d-4d98-ab8f-4e51eabedba0 + InstallationDate: Installed on 2015-04-02 (0 days ago) + InstallationMedia: Ubuntu-Desktop-Next 15.04 Vivid Vervet - Beta amd64 (20150331) + IwConfig: + eth0 no wireless extensions. + + lono wireless extensions. + MachineType: VMware, Inc. VMware Virtual Platform + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-11-generic root=UUID=e71f1bf7-4309-4bd0-9dec-a16504f7e181 ro nomodeset vga=791 + ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.19.0-11-generic N/A + linux-backports-modules-3.19.0-11-generic N/A + linux-firmware 1.143 + RfKill: + + SystemImageInfo: + current build number: 0 + device name: + channel: daily + last update: Unknown + Tags: vivid + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 3.19.0-11-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/20/2014 + 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:bd05/20/2014: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. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1438562/+attachment/4363900/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] Re: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11
The mainline kernel does not fix this bug. It still exist in linux-image-4.0.0-04rc6-generic, i.e. using this: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc6-vivid/linux-image-4.0.0-04rc6-generic_4.0.0-04rc6.201503291935_amd64.deb The dmesg for kernel oops with e1000e was added. ** Tags added: kernel-bug-exists-upstream ** Attachment added: e1000e kernel oops in Linux kernel 4 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+attachment/4363919/+files/linux-image-v4.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1438562/+attachment/4363911/+files/WifiSyslog.txt ** 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/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1438562/+attachment/4363908/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1438562/+attachment/4363909/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1438562/+attachment/4363904/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1438562/+attachment/4363906/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] JournalErrors.txt
apport information ** Attachment added: JournalErrors.txt https://bugs.launchpad.net/bugs/1438562/+attachment/4363903/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1438562/+attachment/4363905/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1438562/+attachment/4363907/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1438562/+attachment/4363901/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1438562/+attachment/4363902/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1438562/+attachment/4363910/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] Re: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11
Christopher, did you mean to follow the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel then send to https://lists.sourceforge.net/lists/listinfo/e1000-devel ? Otherwise I can not find any e1000-devel list on vger.kernel.org. The most related one I found is net...@vger.kernel.org. Please advise. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438562] [NEW] e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11
Public bug reported: When I booted the daily build vivid iso from http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/ vivid-desktop-amd64.iso 31-Mar-2015 03:41 1.0G Desktop image for 64-bit PC (AMD64) computers (standard download) I got a kernel oops. The virtual machine is on VMware Workstation 11.1.0 for Linux with MS Windows 8.1 client, therefore the chipset for ethernet0 is e1000e shown in the *.vmx file: ethernet0.virtualDev = e1000e The oops is attached. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: Kernel oops for e1000e https://bugs.launchpad.net/bugs/1438562/+attachment/4361661/+files/e1000e-crash-db.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438562 Title: e1000e of 3.19.0-10-generic got kernel oops in vmware ws 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391405] Re: Service statd not started after rebooting on Ubuntu 14.10
** Attachment added: The installation of nfs-kernel-server package https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391405/+attachment/4258025/+files/nfs-kernel-server-installation.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391405 Title: Service statd not started after rebooting on Ubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391405] Re: Service statd not started after rebooting on Ubuntu 14.10
** Attachment added: Output crreated by ubuntu-bug for nfs-common https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391405/+attachment/4258028/+files/14.10-nfs-common-environment.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391405 Title: Service statd not started after rebooting on Ubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391405] [NEW] Service statd not started after rebooting on Ubuntu 14.10
Public bug reported: I just did a fresh installation for Ubuntu 14.10 i386 release, and nfs-kernel-server was installed correctly. During the installation of nfs-kernel-server package, I can see statd service was started successfully. I confirmed it's running: steven@utopic:~$ ps -ef |grep statd statd 2973 1 0 14:55 ?00:00:00 rpc.statd -L However, when I reboot the system, statd service is never started automatically. In Ubuntu 14.04, there is no such issue, and it exists on Ubuntu 14.10 now. Is is a bug? Or anything changes which I do not follow? How could I fix it? Thanks. Steven. ** Affects: nfs-utils (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/1391405 Title: Service statd not started after rebooting on Ubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372802] [NEW] plymouth-theme-text not working on Utopic
Public bug reported: I installed a text mode Utopic i386 via network. All works fine, except the plymouth is not working. Instead of plymouth-theme-ubuntu-text, I manually installed plymouth-theme-text, and make sure the boot parameters has splash: $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=/dev/mapper/utopic32--vg-root ro quiet splash When booting, there is no splash on the screen, and the booting messages are still shown on the screen. If you need more info, please let me know. Thanks. Steven. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: plymouth-theme-text 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 BootLog: * Restoring resolver state... [100G [94G[ OK ] * Starting uuid generator uuidd [100G [94G[ OK ] CurrentDmesg: [ 27.297632] systemd-logind[1120]: Watching system buttons on /dev/input/event0 (Power Button) [ 27.301140] systemd-logind[1120]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 27.301216] systemd-logind[1120]: Failed to start user service: Unknown unit: user@1000.service [ 27.304119] systemd-logind[1120]: New session 1 of user steven. [ 1395.975880] dm-0: WRITE SAME failed. Manually zeroing. Date: Tue Sep 23 15:53:28 2014 DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1: Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=/dev/mapper/hostname--vg-root ro quiet splash ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=/dev/mapper/hostname--vg-root ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/text/text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2013 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/31/2013: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: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372802 Title: plymouth-theme-text not working on Utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1372802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1324399] [NEW] apt-get failing to show progress with yes command
Public bug reported: When running this command on Ubuntu 14.04 amd64 release: yes | apt-get -y install tftpd-hpa It never finishes... Only shows black screen on the terminal. I know it's weird to use yes for this command. However, just to show it does make any sense the command can not be finished. This issue does not occur on Ubuntu 13.10, nor on Debian Sid. The following is some info about this system: ProblemType: Bug ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Thu May 29 15:06:52 2014 Dependencies: dpkg 1.17.5ubuntu5.2 gcc-4.8-base 4.8.2-19ubuntu1 gcc-4.9-base 4.9-20140406-0ubuntu1 gnupg 1.4.16-1ubuntu2 gpgv 1.4.16-1ubuntu2 libacl1 2.2.52-1 libapt-pkg4.12 1.0.1ubuntu2 libattr1 1:2.4.47-1ubuntu1 libbz2-1.0 1.0.6-5 libc6 2.19-0ubuntu6 libgcc1 1:4.9-20140406-0ubuntu1 liblzma5 5.1.1alpha+20120614-2ubuntu2 libpcre3 1:8.31-2ubuntu2 libreadline6 6.3-4ubuntu2 libselinux1 2.2.2-1ubuntu0.1 libstdc++6 4.8.2-19ubuntu1 libtinfo5 5.9+20140118-1ubuntu1 libusb-0.1-4 2:0.1.12-23.3ubuntu1 multiarch-support 2.19-0ubuntu6 readline-common 6.3-4ubuntu2 tar 1.27.1-1 ubuntu-keyring 2012.05.19 zlib1g 1:1.2.8.dfsg-1ubuntu1 DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 SourcePackage: apt Tags: trusty Uname: Linux 3.13.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True ** Affects: plymouth (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/1324399 Title: apt-get failing to show progress with yes command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1324399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1324399] Re: apt-get failing to show progress with yes command
BTW, forgot to mention if the command is run as: yes | apt-get -y install tftpd-hpa /dev/null It finishes successfully. ** Description changed: When running this command on Ubuntu 14.04 amd64 release: yes | apt-get -y install tftpd-hpa It never finishes... Only shows black screen on the terminal. - I know it's weird to use yes for this command. However, just to show it does make any sense the command can not be finished. + I know it's weird to use yes for this command. However, just to show it does not make any sense the command can not be finished. This issue does not occur on Ubuntu 13.10, nor on Debian Sid. The following is some info about this system: ProblemType: Bug ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Thu May 29 15:06:52 2014 Dependencies: - dpkg 1.17.5ubuntu5.2 - gcc-4.8-base 4.8.2-19ubuntu1 - gcc-4.9-base 4.9-20140406-0ubuntu1 - gnupg 1.4.16-1ubuntu2 - gpgv 1.4.16-1ubuntu2 - libacl1 2.2.52-1 - libapt-pkg4.12 1.0.1ubuntu2 - libattr1 1:2.4.47-1ubuntu1 - libbz2-1.0 1.0.6-5 - libc6 2.19-0ubuntu6 - libgcc1 1:4.9-20140406-0ubuntu1 - liblzma5 5.1.1alpha+20120614-2ubuntu2 - libpcre3 1:8.31-2ubuntu2 - libreadline6 6.3-4ubuntu2 - libselinux1 2.2.2-1ubuntu0.1 - libstdc++6 4.8.2-19ubuntu1 - libtinfo5 5.9+20140118-1ubuntu1 - libusb-0.1-4 2:0.1.12-23.3ubuntu1 - multiarch-support 2.19-0ubuntu6 - readline-common 6.3-4ubuntu2 - tar 1.27.1-1 - ubuntu-keyring 2012.05.19 - zlib1g 1:1.2.8.dfsg-1ubuntu1 + dpkg 1.17.5ubuntu5.2 + gcc-4.8-base 4.8.2-19ubuntu1 + gcc-4.9-base 4.9-20140406-0ubuntu1 + gnupg 1.4.16-1ubuntu2 + gpgv 1.4.16-1ubuntu2 + libacl1 2.2.52-1 + libapt-pkg4.12 1.0.1ubuntu2 + libattr1 1:2.4.47-1ubuntu1 + libbz2-1.0 1.0.6-5 + libc6 2.19-0ubuntu6 + libgcc1 1:4.9-20140406-0ubuntu1 + liblzma5 5.1.1alpha+20120614-2ubuntu2 + libpcre3 1:8.31-2ubuntu2 + libreadline6 6.3-4ubuntu2 + libselinux1 2.2.2-1ubuntu0.1 + libstdc++6 4.8.2-19ubuntu1 + libtinfo5 5.9+20140118-1ubuntu1 + libusb-0.1-4 2:0.1.12-23.3ubuntu1 + multiarch-support 2.19-0ubuntu6 + readline-common 6.3-4ubuntu2 + tar 1.27.1-1 + ubuntu-keyring 2012.05.19 + zlib1g 1:1.2.8.dfsg-1ubuntu1 DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2 PackageArchitecture: amd64 ProcEnviron: - TERM=screen - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 SourcePackage: apt Tags: trusty Uname: Linux 3.13.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1324399 Title: apt-get failing to show progress with yes command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1324399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284514] [NEW] mdadm.postinst should run update-grub only when grub is configured.
Public bug reported: When mdadm (3.2.5-5ubuntu3) is installed in a bootstrap/live Trusty environment, it fails. It's because update-grub is run. However, in a bootstrap/live system, although grub is installed, actually it's not use for the boot loader. Therefore update-grub fails. Attached please find the patch to fix this error. My 2 cents. Steven. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Patch added: Patch for mdadm.postinst https://bugs.launchpad.net/bugs/1284514/+attachment/3995814/+files/mdadm.postinst.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284514 Title: mdadm.postinst should run update-grub only when grub is configured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1284514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212138] Re: uvesafb not working on Saucy
This issue still exists on the released saucy, i.e. linux kernel 3.11.0-12-generic. Apparently the issue is about vmwgfx, so a workaround is to disable vmwgfx by adding a boot parameter like vmwgfx.enable_fbdev=no because if vmwgfx.enable_fbdev=0 is used, vmwgfx module is still loaded. The boot parameter vmwgfx.enable_fbdev=no makes kernel complain vmwgfx: `no' invalid for parameter `enable_fbdev' so it won't be loaded. Ugly workaround but it works. It would be better that KMS mode could work with uvesafb. Steven. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212138 Title: uvesafb not working on Saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1212138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
