[Bug 2061140] Re: dropbear-initramfs package fails to install on Ubuntu 24.04 beta server
Indeed, looks like this issue is related to initramfs-tools, be that through an incompatibility introduced in either. I tested with the package in Debian Sid dropbear-initramfs (2024.84-1) and got the same error. Meanwhile, on a Debian Sid install, it works. Based on the above, I added initramfs-tools as affected package. ** Also affects: initramfs-tools (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/2061140 Title: dropbear-initramfs package fails to install on Ubuntu 24.04 beta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/2061140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061140] Re: dropbear-initramfs package fails to install on Ubuntu 24.04 beta server
The above was observed on a QEMU KVM VM using server installer defaults as well as with specific curtin storage definitions. I also reproduced the same on a QEMU KVM VM using desktop installer and clicking next on all questions (except user). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061140 Title: dropbear-initramfs package fails to install on Ubuntu 24.04 beta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/2061140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061140] [NEW] dropbear-initramfs package fails to install on Ubuntu 24.04 beta server
Public bug reported: dropbear-initramfs seems to fail on not figuring out what the root device is. This applies both to autoinstall and manual install and is observed on today's beta (ubuntu-24.04-beta-live-server-amd64.iso on 2024-04-12) ubuntu@ubuntu-server:~$ sudo apt install dropbear-initramfs [sudo] password for ubuntu: Reading package lists... Done Building dependency tree... Done Reading state information... Done dropbear-initramfs is already the newest version (2022.83-4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up initramfs-tools (0.142ubuntu24) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.142ubuntu24) ... update-initramfs: Generating /boot/initrd.img-6.8.0-22-generic dropbear: WARNING: Couldn't find ~root, SSH login to initramfs won't work! E: /usr/share/initramfs-tools/hooks/dropbear failed with return 1. update-initramfs: failed for /boot/initrd.img-6.8.0-22-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: dropbear (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/2061140 Title: dropbear-initramfs package fails to install on Ubuntu 24.04 beta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/2061140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
I can confirm the workaround by boxeus works on Ubuntu 20.04 LTS. To improve on that, the lines can be added to the /etc/dropbear- initramfs/config config file instead to avoid upgrade issues. It is loaded towards the end of /usr/share/initramfs-tools/scripts/init- bottom/dropbear anyway. Automation two-liner: echo -e "rm /run/net-*.conf\nrm /run/netplan/*.yaml" >> /etc/dropbear-initramfs/config update-initramfs -u After that, netplan actually works again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813394 Title: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
Which version of Mint (or which upstream Ubuntu it is based on?) I wonder if there is a way to get those rows into the configs rather than editing packaged files? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813394 Title: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878674] Re: apt purge snapd fails in LXD (on amd64)
In our case we decided to spend the same effort on orchestrating for images:ubuntu/focal/cloud (which comes without snapd) rather than working around issues with snap on the thicker default image. But the workaround above can be used, and I remember it was documented elsewhere on launchpad or maybe askubuntu. Going back on our git I can see the following (YMMV): # Remove snapd snap remove lxd snap remove core18 snap remove snapd umount /snap/ rm -rf ~/snap /snap /var/snap /var/lib/snapd apt-get purge snapd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878674 Title: apt purge snapd fails in LXD (on amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
It seems the workaround above does not work on Ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813394 Title: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880740] [NEW] Provide a straightforward way to reset networking after initramfs
Public bug reported: Since initramfs networking is rather limited, a simple flag to reset networking afterwards (or not to generate netplan files) would be valuable. The intended effect is to allow fully featured networking tools to set up the network afterwards. Use cases include the following, in comination with networking-enabled initramfs: * Multiple IPs on a single interface * Adding search domains * Unlocking root over SSH on a different network than will be used afterwards * Using DHCP for initramfs and static later There are numerous workarounds floating around, as well as questions on this behaviour. Netplan has made this even more difficult to get around, since it does not provide an equivalent to 'service networking restart'. As of Ubuntu 20.04, I have not even found any workaround that actually works. Related: dropbear-initramfs IFDOWN not working LP #1813394 Alternative approach with netplan in initramfs LP #1880717 What is creating /run/netplan/eth0.yaml? askubuntu #1228433 ** Affects: initramfs-tools (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/1880740 Title: Provide a straightforward way to reset networking after initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880717] [NEW] Support netplan in initramfs
Public bug reported: The first bullet point of Netplans' Key Goals is "Usable in initramfs (few dependencies and fast)". This is currently not supported in Ubuntu. A basic approach would be to use the same /etc/netplan/*.yaml whenever initramfs depends on networking. Supporting netplan in initramfs has the potential to go beyond the 'ip=' kernel command line / initramfs config. Initramfs-tools does generate a netplan config, that is not what this bug report is about. On the contrary, that feature actually limits the concerned interface to 'ip=' feature levels even after initramfs, since it effectively overrides said interface's config in /etc/netplan/. ** Affects: netplan.io (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/1880717 Title: Support netplan in initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1880717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
Digging even further back, it turns out that IFDOWN is in itself a workaround for an equal issue dating back to ~2012. As such, the core of the issue lies with how initramfs network setup overrides netplan. Adding that package. Given the very limited setup /etc/initramfs-tools/initramfs.conf allows (including the DHCP default mentioned in the description), there is a case to be made for allowing admins to rely on the full config rather than initramfs for their network setup. ** Also affects: initramfs-tools (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/1813394 Title: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
Investigating further reveals that the package is not adapted for netplan in the first place. The maintainer is not on launchpad and the package was imported from Debian Sid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813394 Title: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
This also applies when set up with static IP's in /etc/initramfs- tools/initramfs.conf. That case is most prominently noticed as lacking nameservers after boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813394 Title: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
I agree. I confirm this is still happening on Ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813394 Title: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876974] Re: Support multiple ESPs
The situation where this arose is in testing our Ubuntu 20.04 orchestration. Previously we used a script to ensure boot coherence. We use two mirrored system drives, mirroring everything to the extent that the system must be completely bootable after pulling a drive/having one drive fail completely. The situation where it becomes tempting to re-run grub-install, is when such a drive is replaced with an empty one. Our previous setup simply copies the ESP over, so when the partition exists and is mounted, it simply works. I am perfectly happy with doing this using dpkg. However, I do not see how it would recognize the new partition identifiers? 'dpkg-reconfigure grub-efi-amd64' only seems to offer existing GRUB EFI system partitions. Maybe documenting the intended workflow would help us admins in such cases. For some reason, the installer also records the drives differently (both are 850 EVO), but in essence, I am guessing simply getting the new drive's partition registered here should do the trick: $ sudo debconf-show grub-efi-amd64 | grep devices: * grub-efi/install_devices: /dev/disk/by-id/scsi-1ATA_Samsung_SSD_850_EVO_250GB_S2R6NXAH352264N-part1, /dev/disk/by-id/wwn-0x5002538d40c10167-part1 So the issue boils down to the same point I made above: making admins able to utilize this great feature. Do admins need to first manually install grub or copy over the contents on that new partition for it to be recognized in dpkg-reconfigure? Where is it documented or visible? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876974 Title: Support multiple ESPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868456] Re: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container
Container management seems to be the source of the error, sudo just suppresses it. So a potential fix is in LXD or related packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868456 Title: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1868456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868456] Re: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container
Workaround: echo "Set disable_coredump false" | sudo tee -a /etc/sudo.conf ** Also affects: lxd (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/1868456 Title: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1868456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878674] Re: apt purge snapd fails in LXD (on amd64)
I am seeing this as well. A workaround is to remove all snaps but core, then unmount the snap core before purging with apt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878674 Title: apt purge snapd fails in LXD (on amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876974] Re: Support multiple ESPs
** Changed in: grub2 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876974 Title: Support multiple ESPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878225] Re: snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64
OK, so for anyone hitting this error until there may be a fix: For cases where snapd is not needed (and perhaps purged later), and orchestration relies on cloud-init to finish, the workaround in the container is: systemctl stop snapd.seeded.service or on the host: lxc exec $CONTAINERNAME -- systemctl stop snapd.seeded.service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878225 Title: snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806070] Re: snapd.seeded.service never completes preventing full boot to default target
Chad, were you able to find the config that caused the effect? There is a similar issue open here: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878225 I am trying to find out if it is a regression or something in my config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806070 Title: snapd.seeded.service never completes preventing full boot to default target To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1806070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878225] Re: snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64
Have you tested this on amd64? I am seeing the same outputs on amd64 and trying to find out if it is a regression or something in my config. A similar report has suggestions it may be due to faulty network setup for the container: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1806070 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878225 Title: snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659719] Re: ssh can't call a binary from a snap without the full path
This is fairly problematic when core functionality that is orchestrated in the cloud moves from deb to snap. In our example, lxc (LXD command line tool) was assumed to be in the path when building the orchestration. Using the full path makes it less portable. It also makes managing multiple releases a pain since some hosts may run the snap, others installed by dpkg. Is there any update on the intended direction? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659719 Title: ssh can't call a binary from a snap without the full path To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876974] Re: Support multiple ESPs
I ran 'grub-install', and expected both efi to be updated. It updates only the primary ESP. Both 'dpkg-reconfigure grub-efi-amd64' and running 'grub-multi-install' directly update both ESPs. So on the package updates part it looks like we are good to go. The part that I am missing, is making it somehow the default out of the box action for admins when updating efi on such systems. Here are some approaches to illustrate: - put grub-multi-install in the path at the very least, - use dpkg's alternatives to point grub-install at grub-multi-install or - wrap grub-install with a warning if multiple ESP's are present, - put a note somewhere where admins will be looking when trying to figure it out, such as on /boot/efi if the specs allow it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876974 Title: Support multiple ESPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876974] [NEW] Support multiple ESPs
Public bug reported: Subiquity has the brilliant feature of supporting installing to multiple ESP's. See https://bugs.launchpad.net/subiquity/+bug/1817066 for details. grub-install does not mirror this feature this out of the box, but updates the ESP on /boot/efi only by default on such an installation. Whenever efi potentially changes, this leaves the backup ESP without the update. Adding this support would be coherent, since an admin may logically assume the install mode is supported beyond the installation phase. ** Affects: grub2 (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/1876974 Title: Support multiple ESPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819434] Re: tenshi installation fails
Removing the package after the failed install is not straight forward, here is a workarond: sudo systemctl stop tenshi.service; sudo killall tenshi; sudo apt purge tenshi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819434 Title: tenshi installation fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tenshi/+bug/1819434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819434] [NEW] tenshi installation fails
Public bug reported: Tested on three different Ubuntu 18.04 LTS systems. It seems something is broken in the packaging of tenshi. Installation stalls for several minutes and then fails. $ sudo apt install tenshi Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libio-bufferedselect-perl The following NEW packages will be installed: libio-bufferedselect-perl tenshi 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 36.7 kB of archives. After this operation, 173 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://helsinki-1.clouds.archive.ubuntu.com/ubuntu bionic/universe amd64 libio-bufferedselect-perl all 1.0-1 [7836 B] Get:2 http://helsinki-1.clouds.archive.ubuntu.com/ubuntu bionic/universe amd64 tenshi all 0.13-2+deb7u1 [28.8 kB] Fetched 36.7 kB in 0s (104 kB/s) Selecting previously unselected package libio-bufferedselect-perl. (Reading database ... 33410 files and directories currently installed.) Preparing to unpack .../libio-bufferedselect-perl_1.0-1_all.deb ... Unpacking libio-bufferedselect-perl (1.0-1) ... Selecting previously unselected package tenshi. Preparing to unpack .../tenshi_0.13-2+deb7u1_all.deb ... Unpacking tenshi (0.13-2+deb7u1) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for systemd (237-3ubuntu10.13) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Setting up libio-bufferedselect-perl (1.0-1) ... Setting up tenshi (0.13-2+deb7u1) ... Adding tenshi system user ... adduser: Warning: The home directory `/var/lib/tenshi' does not belong to the user you are currently creating. Adding user tenshi to group adm Job for tenshi.service failed because a timeout was exceeded. See "systemctl status tenshi.service" and "journalctl -xe" for details. invoke-rc.d: initscript tenshi, action "start" failed. ● tenshi.service - LSB: tenshi log monitoring and reporting tool Loaded: loaded (/etc/init.d/tenshi; generated) Active: failed (Result: timeout) since Mon 2019-03-11 10:06:35 UTC; 206ms ago Docs: man:systemd-sysv-generator(8) Process: 2792 ExecStart=/etc/init.d/tenshi start (code=killed, signal=TERM) Tasks: 3 (limit: 2320) CGroup: /system.slice/tenshi.service ├─2800 /usr/bin/perl /usr/sbin/tenshi -P /var/run/tenshi/tenshi.pid ├─2801 /usr/bin/tail -q --follow=name --retry -n 0 /var/log/syslog /var/log/auth.log └─2802 tenshi Mar 11 10:01:34 rodakorset systemd[1]: Starting LSB: tenshi log monitoring and reporting tool... Mar 11 10:06:35 rodakorset systemd[1]: tenshi.service: Start operation timed out. Terminating. Mar 11 10:06:35 rodakorset systemd[1]: tenshi.service: Failed with result 'timeout'. Mar 11 10:06:35 rodakorset systemd[1]: Failed to start LSB: tenshi log monitoring and reporting tool. dpkg: error processing package tenshi (--configure): installed tenshi package post-installation script subprocess returned error exit status 1 Processing triggers for systemd (237-3ubuntu10.13) ... Processing triggers for ureadahead (0.100.0-20) ... Errors were encountered while processing: tenshi E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: tenshi (Ubuntu) Importance: Undecided Status: New ** Description changed: - Tested on three different systems. It seems something is broken in the - packaging of tenshi. Installation stalls for several minutes and then - fails. + Tested on three different Ubuntu 18.04 LTS systems. It seems something + is broken in the packaging of tenshi. Installation stalls for several + minutes and then fails. $ sudo apt install tenshi Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following additional packages will be installed: - libio-bufferedselect-perl + libio-bufferedselect-perl The following NEW packages will be installed: - libio-bufferedselect-perl tenshi + libio-bufferedselect-perl tenshi 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 36.7 kB of archives. After this operation, 173 kB of additional disk space will be used. - Do you want to continue? [Y/n] + Do you want to continue? [Y/n] Get:1 http://helsinki-1.clouds.archive.ubuntu.com/ubuntu bionic/universe amd64 libio-bufferedselect-perl all 1.0-1 [7836 B] Get:2 http://helsinki-1.clouds.archive.ubuntu.com/ubuntu bionic/universe amd64 tenshi all 0.13-2+deb7u1 [28.8 kB] Fetched 36.7 kB in 0s (104 kB/s) Selecting previously unselected package libio-bufferedselect-perl. (Reading database ... 33410 files and directories currently installed.) Preparing to unpack .../libio-bufferedselect-perl_1.0-1_all.deb ... Unpacking libio-bufferedselect-perl (1.0-1) ... Selecting previously unselected package tenshi. Preparing to unpack .../tenshi_0.13-2+deb7u1_all.deb ... Unpacking tenshi
[Bug 1793301] Re: easy-rsa not working with openssl 1.1
Here is a one-line to work around the issue: sed -i 's#export KEY_CONFIG.*#export KEY_CONFIG="$EASY_RSA/openssl-1.0.0.cnf"#' /home/ubuntu/openvpn-ca/vars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793301 Title: easy-rsa not working with openssl 1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easy-rsa/+bug/1793301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779340] [NEW] systemd-networkd-wait-online.service Failed to start Wait for Network to be Configured with bridge
Public bug reported: The following simple netplan config results in a 2-minut unneccessary delay on boot. Everything works like it should in the end. The bridge has no interfaces due to a regression in Ubuntu migrating to netplan (see https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779341). ubuntu@molnix3:~$ cat /etc/netplan/01-netcfg.yaml # This file describes the network interfaces available on your system # For more information, see netplan(5). network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: yes dhcp6: yes ubuntu@molnix3:~$ cat /etc/netplan/br1.yaml network: version: 2 bridges: br1: addresses: [10.1.0.9/16] interfaces: [] ubuntu@molnix3:~$ cat /usr/lib/networkd-dispatcher/routable.d/tap0 #!/bin/sh set -e if [ "$IFACE" = tap0 ]; then brctl addif br1 tap0 ip link set tap0 promisc on ifmetric tap0 5 fi ubuntu@molnix3:~$ journalctl -u systemd-networkd-wait-online.service -b -- Logs begin at Thu 2018-06-28 10:07:29 UTC, end at Fri 2018-06-29 14:09:18 UTC. -- Jun 29 13:58:16 molnix3 systemd[1]: Starting Wait for Network to be Configured... Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:18 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:18 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:19 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:20 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:20 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:21 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 14:00:16 molnix3 systemd-networkd-wait-online[1468]: Event loop failed: Connection timed out Jun 29 14:00:16 molnix3 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Jun 29 14:00:16 molnix3 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Jun 29 14:00:16 molnix3 systemd[1]: Failed to start Wait for Network to be Configured. ubuntu@molnix3:~$ /lib/systemd/systemd-networkd-wait-online managing: br1 managing: enp4s0 ignoring: lo ubuntu@molnix3:~$ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp4s0 ether routableconfigured 3 br1 ether routableconfigured 4 tap0 ether routableunmanaged 4 links listed. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: The following simple netplan config results in a 2-minut unneccessary delay on boot. Everything works like it should in the end. The bridge has no interfaces due to a regression in Ubuntu migrating to netplan - (see separate bug). + (see https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779341). - ubuntu@molnix3:~$ cat /etc/netplan/01-netcfg.yaml + ubuntu@molnix3:~$ cat /etc/netplan/01-netcfg.yaml # This file describes the network interfaces available on your system # For more information, see netplan(5). network: - version: 2 - renderer: networkd - ethernets: - enp4s0: - dhcp4: yes - dhcp6: yes + version: 2 + renderer: networkd + ethernets: + enp4s0: + dhcp4: yes + dhcp6: yes - ubuntu@molnix3:~$ cat /etc/netplan/br1.yaml + ubuntu@molnix3:~$ cat /etc/netplan/br1.yaml network: - version: 2 - bridges: - br1: - addresses: [10.1.0.9/16] - interfaces: [] + version: 2 + bridges: + br1: + addresses: [10.1.0.9/16] + interfaces: [] - ubuntu@molnix3:~$ cat /usr/lib/networkd-dispatcher/routable.d/tap0 + ubuntu@molnix3:~$ cat /usr/lib/networkd-dispatcher/routable.d/tap0 #!/bin/sh set -e - if [ "$IFACE" = tap0 ]; then - brctl addif br1 tap0 - ip link set tap0 promisc on - ifmetric tap0 5 + if [ "$IFACE" = tap0 ]; then + brctl addif br1 tap0 + ip link set tap0 promisc on + ifmetric tap0 5 fi ubuntu@molnix3:~$ journalctl -u systemd-networkd-wait-online.service -b -- Logs begin at Thu 2018-06-28 10:07:29 UTC, end at Fri 2018-06-29 14:09:18 UTC. -- Jun 29 13:58:16 molnix3 systemd[1]: Starting Wait for Network to be Configured... Jun 29 13:58:16
[Bug 1779341] [NEW] Regression: netplan.io does not support managing OpenVPN bridges
Public bug reported: While systemd supports bringing up independent openvpn services, there is currently no way of declaring these in netplan like it was in /etc/network/interfaces. Critically, it is no longer feasible to have such a device in a bridge that is declared in netplan. Related bugs: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1718227 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779340 As a workaround, it is possible to install networkd-dispatcher and add a script in /usr/lib/networkd-dispatcher/routable.d/ with something like the following: #!/bin/sh set -e if [ "$IFACE" = tap0 ]; then brctl addif br1 tap0 ip link set tap0 promisc on ifmetric tap0 5 fi ** Affects: netplan.io (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/1779341 Title: Regression: netplan.io does not support managing OpenVPN bridges To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675349] Re: Dsid missing source on Finnish provider Nebula and RDO installs
I can verify the fix. However, rm -Rf /var/lib/cloud /var/log/cloud* will cause the SSH key to be reset, which is easily a bigger issue than getting a cloud-init warning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675349 Title: Dsid missing source on Finnish provider Nebula and RDO installs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1675349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612600] Re: backuppc 3.3.1-2ubuntu3 breaks pool graphs on the Status page
Can a maintainer please nominate this for xenial separately. The status is misleading since the fix is not in released in xenial, which is what this bug was filed against. The janitor does not act on tags. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612600 Title: backuppc 3.3.1-2ubuntu3 breaks pool graphs on the Status page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1612600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654311] [NEW] glustershd shows E [client-rpc-fops.c:5058:client3_3_getxattr] (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(syncop_getxattr+0x1a0) [0x7ff3ce972450] -->/usr/lib/x86_64-linux-gnu/
Public bug reported: On Xenial with glusterfs 3.7.6, running a volume heal full command works well but the glustershd log shows this repeated many times: [2017-01-05 15:26:20.138562] E [client-rpc- fops.c:5058:client3_3_getxattr] (-->/usr/lib/x86_64-linux- gnu/libglusterfs.so.0(syncop_getxattr+0x1a0) [0x7ff3ce972450] -->/usr/lib/x86_64-linux- gnu/glusterfs/3.7.6/xlator/protocol/client.so(client_getxattr+0x6f) [0x7ff3c8bebeff] -->/usr/lib/x86_64-linux- gnu/glusterfs/3.7.6/xlator/protocol/client.so(client3_3_getxattr+0x4e2) [0x7ff3c8c013f2] ) 0-: Assertion failed: 0 So far, I have not seen any symptoms connected to this, nor signs in other logs, so the impact is low. ** Affects: glusterfs (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/1654311 Title: glustershd shows E [client-rpc-fops.c:5058:client3_3_getxattr] (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(syncop_getxattr+0x1a0) [0x7ff3ce972450] -->/usr/lib/x86_64-linux- gnu/glusterfs/3.7.6/xlator/protocol/client.so(client_getxattr+0x6f) [0x7ff3c8bebeff] -->/usr/lib/x86_64-linux- gnu/glusterfs/3.7.6/xlator/protocol/client.so(client3_3_getxattr+0x4e2) [0x7ff3c8c013f2] ) 0-: Assertion failed: 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1654311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so
Yes this makes a lot of sense. The situation is the same for me, but I started automatically removing a list of packages from my lxd containers - including mdadm. That's why the problem disappeared. Mdadm could still make sense in a container (privileged with raw access to devices etc.) but considering what containers are typically used for that should be quite rare. So at least as a workaround when mdadm is not needed, removing mdadm is an option. So we have confirmed this. Is anyone on linux-raid? Lxd devs may also be interested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617919 Title: mdadm segfault error 4 in libc-2.23.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1617919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so
With the latest updates and a reboot and a few days of uptime, the message has not yet reappeared. This may have been fixed? linux-image 4.4.0-36-generic libc 2.23-0ubuntu3 mdadm 3.3-2ubuntu7.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617919 Title: mdadm segfault error 4 in libc-2.23.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1617919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589289] Re: fstrim: cannot open /dev/.lxd-mounts: Permission denied
** Description changed: - fstrun daily cronjob output in an unprivileged LXD container: + fstrun weekly cronjob output in an unprivileged LXD container: /etc/cron.weekly/fstrim: fstrim: cannot open /dev/.lxd-mounts: Permission denied fstrim: /dev/fuse: not a directory fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted - There is a github issue: https://github.com/lxc/lxd/issues/2030 - - The outcome is that it's purely an fstrim misbehaviour, it could be smarter. - + The outcome is that it's purely an fstrim misbehaviour, it could be + smarter. Stephane Graber comment: - - - As all of this is handled by the kernel, there isn't anything we can do about it in LXD. + As all of this is handled by the kernel, there isn't anything we can do + about it in LXD. I think fstrim should be made slightly more clever: * Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts) * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Jun 5 19:49:04 2016 ProcEnviron: - LANGUAGE=en_US:en - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US:en + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589289 Title: fstrim: cannot open /dev/.lxd-mounts: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1589289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617919] [NEW] mdadm segfault error 4 in libc-2.23.so
Public bug reported: On Ubuntu 16.04.1 LTS Xenial, mdadm segfaults every day on two machines. Everything works as normal though, and the RAID arrays are not degraded. [3712474.763430] mdadm[17665]: segfault at 0 ip 7fd0369bed16 sp 7fff8c5c9478 error 4 in libc-2.23.so[7fd036934000+1c] [3712474.949633] mdadm[17727]: segfault at 0 ip 7f2814111d16 sp 7ffca92fe168 error 4 in libc-2.23.so[7f2814087000+1c] [3798863.008741] mdadm[25359]: segfault at 0 ip 7fa6af198d16 sp 7ffc1b253e48 error 4 in libc-2.23.so[7fa6af10e000+1c] [3798863.190382] mdadm[25393]: segfault at 0 ip 7f72218a0d16 sp 7ffef918f118 error 4 in libc-2.23.so[7f7221816000+1c] [3885251.386711] mdadm[32081]: segfault at 0 ip 7f3d99ca2d16 sp 7ffe5e69a7a8 error 4 in libc-2.23.so[7f3d99c18000+1c] [3885251.402337] mdadm[32083]: segfault at 0 ip 7f770ccc1d16 sp 7ffe16074378 error 4 in libc-2.23.so[7f770cc37000+1c] [3971638.258574] mdadm[7936]: segfault at 0 ip 7fcacddb3d16 sp 7ffc062faff8 error 4 in libc-2.23.so[7fcacdd29000+1c] [3971638.410750] mdadm[8053]: segfault at 0 ip 7ff573757d16 sp 7fffd3cca398 error 4 in libc-2.23.so[7ff5736cd000+1c] The segfault message always appears twice in quick succession. It seems to be triggered by /etc/cron.daily/mdadm which essentially runs mdadm --monitor --scan --oneshot As such, the frequency is around every 85000 seconds or 24 hours give or take, depending on when the cron job was executed. It does not happen when running the command manually. There is one similar bug #1576055 concerning libc and a few cases elsewhere but further digging into this has yet to reveal anything conclusive. Note that these machines have almost exactly the same hardware (Xeon D-1518, 16GB ECC), so hardware design flaws cannot be ruled out. However, memory testing has not turned up any faults. That said, I know some segfaults can be difficult to find even when they are hardware issues. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Package changed: gvfs (Ubuntu) => mdadm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617919 Title: mdadm segfault error 4 in libc-2.23.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1617919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583765] [NEW] Mounting GlusterFS in LXD requires privileged container
Public bug reported: Maybe wishlist: it would be nice to have GlusterFS client mounts in an unprivileged container. Tested with LXD 2.0.0 and glusterfs 3.7.6 (i.e. Xenial without any PPA) on an LXD container with the same versions and fuse enabled in the profile. Currently, trying a mount in an unprivileged container results in the following: /usr/bin/fusermount-glusterfs: mount failed: Operation not permitted Mount failed. Please check the log file for more details. The log shows: [2016-05-19 19:29:47.683013] I [MSGID: 100030] [glusterfsd.c:2318:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.7.6 (args: /usr/sbin/glusterfs --volfile-server=10.1.0.3 --volfile-id=/backuppc /srv/backuppc) [2016-05-19 19:29:47.684158] E [mount.c:318:fuse_mount_sys] 0-glusterfs-fuse: ret = -1 [2016-05-19 19:29:47.684269] I [mount.c:365:gf_fuse_mount] 0-glusterfs-fuse: direct mount failed (Operation not permitted) errno 1, retry to mount via fusermount [2016-05-19 19:29:47.685970] E [mount.c:373:gf_fuse_mount] 0-glusterfs-fuse: mount of 10.1.0.3:/backuppc to /srv/backuppc (default_permissions,allow_other,max_read=131072) failed [2016-05-19 19:29:47.686509] E [MSGID: 100025] [glusterfsd.c:2141:daemonize] 0-daemonize: mount failed [2016-05-19 19:29:47.690507] I [MSGID: 101190] [event-epoll.c:632:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2016-05-19 19:29:47.711689] I [MSGID: 101190] [event-epoll.c:632:event_dispatch_epoll_worker] 0-epoll: Started thread with index 2 [2016-05-19 19:29:47.712298] I [MSGID: 114020] [client.c:2118:notify] 0-backuppc-client-0: parent translators are ready, attempting connect on transport [2016-05-19 19:29:47.713374] I [MSGID: 114020] [client.c:2118:notify] 0-backuppc-client-1: parent translators are ready, attempting connect on transport Final graph: +--+ 1: volume backuppc-client-0 2: type protocol/client 3: option ping-timeout 42 4: option remote-host gluster1 5: option remote-subvolume /srv/aec/backuppc 6: option transport-type socket 7: option send-gids true 8: end-volume 9: 10: volume backuppc-client-1 11: type protocol/client 12: option ping-timeout 42 13: option remote-host gluster2 14: option remote-subvolume /srv/aec/backuppc 15: option transport-type socket 16: option send-gids true 17: end-volume 18: 19: volume backuppc-replicate-0 20: type cluster/replicate [2016-05-19 19:29:47.714077] I [rpc-clnt.c:1847:rpc_clnt_reconfig] 0-backuppc-client-1: changing port to 49152 (from 0) 21: subvolumes backuppc-client-0 backuppc-client-1 22: end-volume [2016-05-19 19:29:47.714373] I [rpc-clnt.c:1847:rpc_clnt_reconfig] 0-backuppc-client-0: changing port to 49152 (from 0) 23: 24: volume backuppc-dht 25: type cluster/distribute 26: subvolumes backuppc-replicate-0 27: end-volume 28: 29: volume backuppc-write-behind 30: type performance/write-behind 31: subvolumes backuppc-dht 32: end-volume 33: 34: volume backuppc-read-ahead 35: type performance/read-ahead 36: subvolumes backuppc-write-behind 37: end-volume 38: 39: volume backuppc-readdir-ahead 40: type performance/readdir-ahead 41: subvolumes backuppc-read-ahead 42: end-volume 43: 44: volume backuppc-io-cache 45: type performance/io-cache 46: subvolumes backuppc-readdir-ahead 47: end-volume 48: 49: volume backuppc-quick-read 50: type performance/quick-read 51: subvolumes backuppc-io-cache 52: end-volume 53: 54: volume backuppc-open-behind 55: type performance/open-behind 56: subvolumes backuppc-quick-read 57: end-volume 58: 59: volume backuppc-md-cache 60: type performance/md-cache 61: subvolumes backuppc-open-behind 62: end-volume 63: 64: volume backuppc 65: type debug/io-stats 66: option latency-measurement off 67: option count-fop-hits off 68: subvolumes backuppc-md-cache 69: end-volume 70: 71: volume meta-autoload 72: type meta 73: subvolumes backuppc 74: end-volume 75: +--+ [2016-05-19 19:29:47.715475] I [MSGID: 114057] [client-handshake.c:1437:select_server_supported_programs] 0-backuppc-client-1: Using Program GlusterFS 3.3, Num (1298437), Version (330) [2016-05-19 19:29:47.715744] I [MSGID: 114046] [client-handshake.c:1213:client_setvolume_cbk] 0-backuppc-client-1: Connected to backuppc-client-1, attached to remote volume '/srv/aec/backuppc'. [2016-05-19 19:29:47.715800] I [MSGID: 114047] [client-handshake.c:1224:client_setvolume_cbk] 0-backuppc-client-1: Server and Client lk-version numbers are not same, reopening the fds [2016-05-19 19:29:47.715885] I [MSGID: 108005] [afr-common.c:3841:afr_notify] 0-backuppc-replicate-0: Subvolume 'backuppc-client-1' came back up;
[Bug 1582191] [NEW] Boot stalls for 90 seconds on mdadm
Public bug reported: On a fresh Ubuntu Xenial 16.04 LTS Server install, the boot stalls for exactly 90 seconds when using a fairly complex partitioning setup. After this, everything works as expected. The partitioning is as follows: /sda GPT /sda1 ESP (/boot/efi) /sda2 raid1 md0 ext4 (/boot) /sda3 raid1 md1 luks,passphrase ext4 (/) /sda4 raid1 md2 luks,key zfs /sdb GPT /sdb1 ESP (copy of /boot/efi) /sdb2 raid1 md0 ext4 (/boot) /sdb3 raid1 md1 luks,passphrase ext4 (/) /sdb4 raid1 md2 luks,key zfs /sdc GPT /sdc1 luks,key xfs /sdd GPT /sdd1 luks,key xfs /sdd2 luks,random swap This may be an installer or mdadm bug instead - I have not been able to exactly determine the cause of the bug. I have several identical servers, all showing the same symptom, so it should not be due to broken hardware (although design flaws are on the table). The key seems to be in these lines from journalctl: ... May 16 14:06:08 molnix kernel: bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. May 16 14:06:08 molnix kernel: device eno1 entered promiscuous mode May 16 14:06:08 molnix systemd-udevd[689]: Process '/lib/udev/hdparm' failed with exit code 5. May 16 14:06:08 molnix systemd-udevd[701]: Process '/lib/udev/hdparm' failed with exit code 5. May 16 14:06:08 molnix systemd-udevd[707]: Process '/lib/udev/hdparm' failed with exit code 5. May 16 14:06:08 molnix systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. May 16 14:06:08 molnix systemd-udevd[701]: Process '/sbin/mdadm --incremental /dev/sda2 --offroot' failed with exit code 1. May 16 14:06:08 molnix systemd-udevd[707]: Process '/sbin/mdadm --incremental /dev/sda3 --offroot' failed with exit code 1. May 16 14:06:08 molnix systemd[1]: Found device Samsung_SSD_850_EVO_250GB EFI\x20System\x20Partition. May 16 14:06:08 molnix systemd-udevd[708]: Process '/sbin/mdadm --incremental /dev/sda4 --offroot' failed with exit code 1. May 16 14:06:08 molnix systemd-udevd[689]: Process '/sbin/mdadm --incremental /dev/sdb3 --offroot' failed with exit code 1. May 16 14:06:08 molnix systemd[1]: Reached target Local File Systems (Pre). May 16 14:06:08 molnix systemd-udevd[701]: Process '/sbin/mdadm --incremental /dev/sdb4 --offroot' failed with exit code 1. May 16 14:06:08 molnix systemd-udevd[699]: Process '/sbin/mdadm --incremental /dev/sdb2 --offroot' failed with exit code 1. May 16 14:06:08 molnix systemd-udevd[706]: Process '/lib/udev/hdparm' failed with exit code 5. May 16 14:06:08 molnix kernel: ipmi_si IPI0001:00: The BMC does not support clearing the recv irq bit, compensating, but the BMC needs to be fixed. May 16 14:06:08 molnix kernel: ipmi_si IPI0001:00: Found new BMC (man_id: 0x002a7c, prod_id: 0x086d, dev_id: 0x20) ... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Mon May 16 14:17:31 2016 InstallationDate: Installed on 2016-05-15 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: Supermicro Super Server ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=0ca65308-3f70-4231-8f5f-e68583a6d5b3 ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10SDV-4C-TLN4F dmi.board.vendor: Supermicro dmi.board.version: 2.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd01/04/2016:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX10SDV-4C-TLN4F:rvr2.00:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Description changed: On a fresh Ubuntu Xenial 16.04 LTS Server install, the boot stalls for exactly 90 seconds when using a fairly complex partitioning setup. After this, everything works as expected. The partitioning is as follows: /sda GPT /sda1 ESP (/boot/efi) /sda2 raid1 md0 ext4 (/boot) /sda3 raid1 md1 luks,passphrase ext4 (/) /sda4 raid1 md2 luks,key zfs /sdb GPT /sdb1 ESP (copy of /boot/efi)
[Bug 1573639] Re: ownCloud Client system tray icon integration broken
I can also confirm the proposed package works nicely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573639 Title: ownCloud Client system tray icon integration broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1573639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111517] Re: javaws doesn't open Supermicro remote console (IP-KVM)
Still the case on 14.04 LTS. In Xenial, icedtea-8 works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/517 Title: javaws doesn't open Supermicro remote console (IP-KVM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528583] Re: [FFe] Please update to MySQL 5.7 series
** Description changed: - upgrade to MySQL 5.7.10 and above, ununtu 16.04 + upgrade to MySQL 5.7.10 and above, Ubuntu 16.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528583 Title: [FFe] Please update to MySQL 5.7 series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1528583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528583] Re: [FFe] Please update to MySQL 5.7 series
** Description changed: - upgrade to MySQL 5.7.10 and above, ununtu 16.04 + upgrade to MySQL 5.7.10 and above, Ubuntu 16.04 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1528583 Title: [FFe] Please update to MySQL 5.7 series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1528583/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
On my 14.04 LTS system the workaround was to add 'dns_v4_first on' to /etc/maas/maas-proxy.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1547640/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
On my 14.04 LTS system the workaround was to add 'dns_v4_first on' to /etc/maas/maas-proxy.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1547640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
I confirm the fix is effective. For large environments where hooks have failed,
here's a one-liner after running the fix to re-run all the failed hooks, which
should return the agents to normal (idle) state:
for i in `juju status --format tabular|grep failed|awk '{print $1;}'`;do echo
Fixing $i;juju resolved -r $i;done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516989] Re: juju status broken
I confirm the fix is effective. For large environments where hooks have failed,
here's a one-liner after running the fix to re-run all the failed hooks, which
should return the agents to normal (idle) state:
for i in `juju status --format tabular|grep failed|awk '{print $1;}'`;do echo
Fixing $i;juju resolved -r $i;done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397201] [NEW] Juju does not use constraints when deploying to a KVM container
Public bug reported: Running Juju 1.20.12-trusty-amd64 on MaaS. May be related to: https://code.launchpad.net/~thumper/juju-core/kvm-constraints/+merge/197815 Setting constraints does not affect the creation of KVM containers. johan@maas:~$ juju deploy --to kvm:2 --constraints mem=2G cpu-cores=2 ubuntu test-ubuntu Added charm cs:trusty/ubuntu-0 to the environment. johan@maas:~$ juju status test-ubuntu environment: maas machines: 2: agent-state: started agent-version: 1.20.12 dns-name: ajbwc.maas.molnix.com instance-id: /MAAS/api/1.0/nodes/node-2aadeb06-6a86-11e4-8be8-0021702cb7de/ series: trusty containers: 2/kvm/4: agent-state: pending instance-id: juju-machine-2-kvm-4 series: trusty hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M hardware: arch=amd64 cpu-cores=2 mem=6144M services: test-ubuntu: charm: cs:trusty/ubuntu-0 exposed: false units: test-ubuntu/0: agent-state: pending machine: 2/kvm/4 ** Affects: juju (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1397201 Title: Juju does not use constraints when deploying to a KVM container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1397201/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1397201] [NEW] Juju does not use constraints when deploying to a KVM container
Public bug reported: Running Juju 1.20.12-trusty-amd64 on MaaS. May be related to: https://code.launchpad.net/~thumper/juju-core/kvm-constraints/+merge/197815 Setting constraints does not affect the creation of KVM containers. johan@maas:~$ juju deploy --to kvm:2 --constraints mem=2G cpu-cores=2 ubuntu test-ubuntu Added charm cs:trusty/ubuntu-0 to the environment. johan@maas:~$ juju status test-ubuntu environment: maas machines: 2: agent-state: started agent-version: 1.20.12 dns-name: ajbwc.maas.molnix.com instance-id: /MAAS/api/1.0/nodes/node-2aadeb06-6a86-11e4-8be8-0021702cb7de/ series: trusty containers: 2/kvm/4: agent-state: pending instance-id: juju-machine-2-kvm-4 series: trusty hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M hardware: arch=amd64 cpu-cores=2 mem=6144M services: test-ubuntu: charm: cs:trusty/ubuntu-0 exposed: false units: test-ubuntu/0: agent-state: pending machine: 2/kvm/4 ** Affects: juju (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/1397201 Title: Juju does not use constraints when deploying to a KVM container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1397201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329145] [NEW] mencoder produces AVI with no audio if it is just above ODML chunk boundary
Public bug reported: Ubuntu 14.04 LTS mplayer 2:1.1+dfsg1-0ubuntu3 This bug is easy to reproduce. I noticed it while uncompressing scenes from my camera for editing. My projects have 1-100 clips and I stumble upon this about 1 in 15 uncompressed files, indicating that the concerned AVI files are around ODML chunk boundary to chunk+(chunk/15) in size, something like 1020-1080 MB for the first hit, next one at 2GB and so on. For example, one testfile I use for this bug report lands at 1122064044 bytes. Consider an input file with 1920x1080p at 3/1001 (~29.970) FPS video and with 48000 Hz 16 bit 2 channel audio. Format should not matter - when uncompressed to raw yv12 and PCM, at 12 seconds, it lands at the above size. Playing back the original works with audio: mplayer source.mp4 -endpos 00:00:12.000 Uncompressing the same clip and playing back results in no audio playback: mencoder -oac pcm -ovc raw source.mp4 -endpos 00:00:12.000 -o test.avi mplayer test.avi Chaging the end position earlier or later results in audio stream working like it should: mencoder -oac pcm -ovc raw source.mp4 -endpos 00:00:11.000 -o test.avi mplayer test.avi OR mencoder -oac pcm -ovc raw source.mp4 -endpos 00:00:13.000 -o test.avi mplayer test.avi Tests done to rule out other factors: - shifting starting position does not change result - changing source file does not change result - running on another computer does not change result (both 3rd gen Intel core, but uncompressed should not be algorithm related?) - running another version (12.04 LTS mplayer 2:1.0~rc4.dfsg1+svn34540-1) does not change result - playing back with VLC does not change result Workarounds: - splitting a scene in two clips - changing scene duration There are two specific rows to look for indicating the issue was triggered. Mencoder informs about the ODML chunk just before finishing the file (I think the number or MB varies between 1021 and 1023. Pos: 11.5s347f (39%) 23.47fps Trem: 0min 2615mb A-V:0.035 [741439:1536]] ODML: Starting new RIFF chunk at 1022MB. Pos: 12.0s361f (40%) 23.50fps Trem: 0min 2658mb A-V:0.046 [741607:1536] Flushing video frames. And mplayer informs about the audio stream missing: AVI file format detected. [aviheader] Video stream found, -vid 0 [aviheader] Audio stream found, -aid 1 AVI: ODML: Building ODML index (1 superindexchunks). Badly interleaved AVI file detected - switching to -ni mode... AVI: No audio stream found - no sound. VIDEO: [YV12] 1920x1080 12bpp 29.970 fps 741607.2 kbps (90528.2 kbyte/s) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mencoder 2:1.1+dfsg1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 12 10:32:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-05 (644 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) SourcePackage: mplayer UpgradeStatus: Upgraded to trusty on 2014-03-16 (87 days ago) ** Affects: mplayer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Description changed: Ubuntu 14.04 LTS mplayer 2:1.1+dfsg1-0ubuntu3 This bug is easy to reproduce. I noticed it while uncompressing scenes from my camera for editing. My projects have 1-100 clips and I stumble upon this about 1 in 15 uncompressed files, indicating that the concerned AVI files are around ODML chunk boundary to chunk+(chunk/15) in size, something like - 1.00-1.15 GB for the first hit, next one at 2GB and so on. For example, + 1.00-1.06 GB for the first hit, next one at 2GB and so on. For example, one testfile I use for this bug report lands at 1122064044 bytes. Consider an input file with 1920x1080p at 3/1001 (~29.970) FPS video and with 48000 Hz 16 bit 2 channel audio. Format should not matter - when uncompressed to raw yv12 and PCM, at 12 seconds, it lands at the above size. Playing back the original works with audio: mplayer source.mp4 -endpos 00:00:12.000 Uncompressing the same clip and playing back results in no audio playback: mencoder -oac pcm -ovc raw source.mp4 -endpos 00:00:12.000 -o test.avi mplayer test.avi Chaging the end position earlier or later results in audio stream working like it should: mencoder -oac pcm -ovc raw source.mp4 -endpos 00:00:11.000 -o test.avi mplayer test.avi OR mencoder -oac pcm -ovc raw source.mp4 -endpos 00:00:13.000 -o test.avi mplayer test.avi Tests done to rule out other factors: - shifting starting position does not change result - changing source file does not change result - running on another computer does not change result (both 3rd gen Intel core, but uncompressed should not be algorithm related?) - running another version (12.04 LTS mplayer 2:1.0~rc4.dfsg1+svn34540-1) does not change
[Bug 1329145] Re: mencoder produces AVI with no audio if it is just above ODML chunk boundary
** Description changed: Ubuntu 14.04 LTS mplayer 2:1.1+dfsg1-0ubuntu3 This bug is easy to reproduce. I noticed it while uncompressing scenes from my camera for editing. My projects have 1-100 clips and I stumble upon this about 1 in 15 uncompressed files, indicating that the concerned AVI files are around ODML chunk boundary to chunk+(chunk/15) in size, something like 1020-1080 MB for the first hit, next one at 2GB and so on. For example, one testfile I use for this bug report lands at 1122064044 bytes. Consider an input file with 1920x1080p at 3/1001 (~29.970) FPS video and with 48000 Hz 16 bit 2 channel audio. Format should not matter - when uncompressed to raw yv12 and PCM, at 12 seconds, it lands at the above size. Playing back the original works with audio: mplayer source.mp4 -endpos 00:00:12.000 Uncompressing the same clip and playing back results in no audio playback: mencoder -oac pcm -ovc raw source.mp4 -endpos 00:00:12.000 -o test.avi mplayer test.avi Chaging the end position earlier or later results in audio stream working like it should: mencoder -oac pcm -ovc raw source.mp4 -endpos 00:00:11.000 -o test.avi mplayer test.avi OR mencoder -oac pcm -ovc raw source.mp4 -endpos 00:00:13.000 -o test.avi mplayer test.avi Tests done to rule out other factors: - shifting starting position does not change result - changing source file does not change result - running on another computer does not change result (both 3rd gen Intel core, but uncompressed should not be algorithm related?) - running another version (12.04 LTS mplayer 2:1.0~rc4.dfsg1+svn34540-1) does not change result - playing back with VLC does not change result Workarounds: - splitting a scene in two clips - changing scene duration - There are two specific rows to look for indicating the issue was triggered. Mencoder informs about the ODML chunk just before finishing the file (I think the number or MB varies between 1021 and 1023. + There are two specific rows to look for indicating the issue was triggered. mencoder informs about the ODML chunk just before finishing the file (I think the number or MB varies between 1021 and 1023): Pos: 11.5s347f (39%) 23.47fps Trem: 0min 2615mb A-V:0.035 [741439:1536]] ODML: Starting new RIFF chunk at 1022MB. Pos: 12.0s361f (40%) 23.50fps Trem: 0min 2658mb A-V:0.046 [741607:1536] Flushing video frames. And mplayer informs about the audio stream missing: AVI file format detected. [aviheader] Video stream found, -vid 0 [aviheader] Audio stream found, -aid 1 AVI: ODML: Building ODML index (1 superindexchunks). Badly interleaved AVI file detected - switching to -ni mode... AVI: No audio stream found - no sound. VIDEO: [YV12] 1920x1080 12bpp 29.970 fps 741607.2 kbps (90528.2 kbyte/s) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mencoder 2:1.1+dfsg1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 12 10:32:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-05 (644 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) SourcePackage: mplayer UpgradeStatus: Upgraded to trusty on 2014-03-16 (87 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329145 Title: mencoder produces AVI with no audio if it is just above ODML chunk boundary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/1329145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329145] Re: mencoder produces AVI with no audio if it is just above ODML chunk boundary
Further testing shows that it actually only occurs just after the first chunk end. With the description's specifications, that is between 11.550-12.500 seconds of video or 1078431852-1165705924 bytes of output file size, tested with 0.05 second precision. ** Description changed: Ubuntu 14.04 LTS mplayer 2:1.1+dfsg1-0ubuntu3 This bug is easy to reproduce. I noticed it while uncompressing scenes from my camera for editing. My projects have 1-100 clips and I stumble upon this about 1 in 15 uncompressed files, indicating that the concerned AVI files are around ODML chunk boundary to chunk+(chunk/15) in size, something like - 1020-1080 MB for the first hit, next one at 2GB and so on. For example, - one testfile I use for this bug report lands at 1122064044 bytes. + 1020-1080 MB. For example, one testfile I use for this bug report lands + at 1122064044 bytes. Consider an input file with 1920x1080p at 3/1001 (~29.970) FPS video and with 48000 Hz 16 bit 2 channel audio. Format should not matter - when uncompressed to raw yv12 and PCM, at 12 seconds, it lands at the above size. Playing back the original works with audio: mplayer source.mp4 -endpos 00:00:12.000 Uncompressing the same clip and playing back results in no audio playback: mencoder -oac pcm -ovc raw source.mp4 -endpos 00:00:12.000 -o test.avi mplayer test.avi Chaging the end position earlier or later results in audio stream working like it should: mencoder -oac pcm -ovc raw source.mp4 -endpos 00:00:11.000 -o test.avi mplayer test.avi OR mencoder -oac pcm -ovc raw source.mp4 -endpos 00:00:13.000 -o test.avi mplayer test.avi Tests done to rule out other factors: - shifting starting position does not change result - changing source file does not change result - running on another computer does not change result (both 3rd gen Intel core, but uncompressed should not be algorithm related?) - running another version (12.04 LTS mplayer 2:1.0~rc4.dfsg1+svn34540-1) does not change result - playing back with VLC does not change result Workarounds: - splitting a scene in two clips - changing scene duration There are two specific rows to look for indicating the issue was triggered. mencoder informs about the ODML chunk just before finishing the file (I think the number or MB varies between 1021 and 1023): Pos: 11.5s347f (39%) 23.47fps Trem: 0min 2615mb A-V:0.035 [741439:1536]] ODML: Starting new RIFF chunk at 1022MB. Pos: 12.0s361f (40%) 23.50fps Trem: 0min 2658mb A-V:0.046 [741607:1536] Flushing video frames. And mplayer informs about the audio stream missing: AVI file format detected. [aviheader] Video stream found, -vid 0 [aviheader] Audio stream found, -aid 1 AVI: ODML: Building ODML index (1 superindexchunks). Badly interleaved AVI file detected - switching to -ni mode... AVI: No audio stream found - no sound. VIDEO: [YV12] 1920x1080 12bpp 29.970 fps 741607.2 kbps (90528.2 kbyte/s) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mencoder 2:1.1+dfsg1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 12 10:32:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-05 (644 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) SourcePackage: mplayer UpgradeStatus: Upgraded to trusty on 2014-03-16 (87 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329145 Title: mencoder produces AVI with no audio if it is just above ODML chunk boundary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/1329145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081307] Re: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed to build [merge request]
Running Ubuntu 12.04.2 LTS 64 bit on Windows XP 32 bit. When installing with the patch in #29 I am getting a bit further but compiling stops at CC [M] /var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/vfsmod.o /var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/vfsmod.c: In function ‘sf_evict_inode’: /var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/vfsmod.c:376:5: error: implicit declaration of function ‘end_writeback’ [-Werror=implicit-function-declaration] cc1: some warnings being treated as errors make[2]: *** [/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/vfsmod.o] Error 1 make[1]: *** [/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf] Error 2 make: *** [_module_/var/lib/dkms/virtualbox-guest/4.1.12/build] Error 2 make: Leaving directory `/usr/src/linux-headers-3.5.0-26-generic' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081307 Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed to build [merge request] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035647] [NEW] package initramfs-tools 0.103ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 on Toshiba AC100 with 12.10 alpha
Public bug reported: The post install trigger in /etc/initramfs/post-update.d/flash-kernel said no Android boot partition could be found. It seems caused by the removed abootimg through 'apt-get autoremove.' This was after a clean install followed by a 'apt-get dist-upgrade', so it should not happen. Likely it would make sense to have abootimg a dependency somewhere in what is installed by default. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: initramfs-tools 0.103ubuntu0.1 Uname: Linux 3.1.10-4-ac100 armv7l ApportVersion: 2.4-0ubuntu6 Architecture: armhf Date: Sat Aug 11 17:39:36 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035647 Title: package initramfs-tools 0.103ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 on Toshiba AC100 with 12.10 alpha To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1035647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035647] Re: package initramfs-tools 0.103ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 on Toshiba AC100 with 12.10 alpha
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035647 Title: package initramfs-tools 0.103ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 on Toshiba AC100 with 12.10 alpha To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1035647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214984] Re: keyboard layout broken if restart without usb keyboard
The bug is closed, but for future reference: It sound like the external keyboard turned and left Num Lock on, which on a laptop keyboard results in the right side of the keyboard to give numbers etc. Not all laptop keyboards have these marked, which may cause difficulties in noticing this. I checked and J - 1 is one of these mappings. To fix this simply turn off Num Lock. -- keyboard layout broken if restart without usb keyboard https://bugs.launchpad.net/bugs/214984 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574929] Re: Sundance Technology IPG Triple-Speed Ethernet: WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x1fe/0x210()
I tried linux-image-2.6.34-999-generic_2.6.34-999.201005061008_i386.deb and the problem no longer appears. I even reverted to stock 2.6.32-22-generic and reproduced the problem easily. A sure way of reproducing the problem is to access the host with unison through its external IP and NIC (even though the client is on the internal network where the host also has an IP and NIC). This may indicate that the bug appears only under full load or after a certain (2GB?) amount has been transferred. ** Changed in: linux (Ubuntu) Status: Incomplete = New ** Tags removed: needs-upstream-testing -- Sundance Technology IPG Triple-Speed Ethernet: WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x1fe/0x210() https://bugs.launchpad.net/bugs/574929 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574929] [NEW] Sundance Technology IPG Triple-Speed Ethernet: WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x1fe/0x210()
Public bug reported: I'm getting this repeatedly after a a day or so, after upgrading to Lucid. I have a Sundance Technology IPG Triple-Speed Ethernet (stops working when this happens, mentioned in the oops) and a 2001:3c05 D-Link Corp. [hex] DUB-E100 Fast Ethernet [asix] USB. Ifdown + ifup brings the interface on line again. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-21-generic 2.6.32-21.32 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: aplay: device_list:223: no soundcards found... Architecture: i386 ArecordDevices: arecord: device_list:223: no soundcards found... Date: Tue May 4 07:52:24 2010 PciMultimedia: ProcCmdLine: root=UUID=d312e3a5-5470-4c76-879b-82055700b284 ro ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux dmi.bios.date: 04/11/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: IG-80(Intel i915G-ICH6) dmi.board.vendor: http://www.abit.com.tw/ dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd04/11/2005:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnIG-80(Inteli915G-ICH6):rvr1.0:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid needs-upstream-testing networking regression-release -- Sundance Technology IPG Triple-Speed Ethernet: WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x1fe/0x210() https://bugs.launchpad.net/bugs/574929 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574929] Re: Sundance Technology IPG Triple-Speed Ethernet: WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x1fe/0x210()
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/47744401/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/47744402/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/47744403/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/47744404/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/47744405/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/47744406/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/47744407/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/47744408/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/47744409/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/47744410/UdevLog.txt -- Sundance Technology IPG Triple-Speed Ethernet: WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x1fe/0x210() https://bugs.launchpad.net/bugs/574929 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545443] Re: Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network
** Changed in: linux (Ubuntu) Assignee: (unassigned) = Ubuntu Kernel Network Team (ubuntu-kernel-network) -- Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network https://bugs.launchpad.net/bugs/545443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545443] Re: Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network
*** This bug is a duplicate of bug 496093 *** https://bugs.launchpad.net/bugs/496093 ** Changed in: linux (Ubuntu) Assignee: Ubuntu Kernel Network Team (ubuntu-kernel-network) = (unassigned) ** This bug has been marked a duplicate of bug 496093 [lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured wireless networks -- Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network https://bugs.launchpad.net/bugs/545443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545443] Re: Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network
Correction: any non-protected network works. After that, protected networks also seem to work mostly. Connecting to a protected network as the first network works as often/seldom as before. -- Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network https://bugs.launchpad.net/bugs/545443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545443] Re: Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network
With the latest updates today, I was able to connect to every network I managed to find (1 unprotected with WDA, 1 unprotected rather typical AP from TP-LINK, 1 unprotected in hotel mode with web authentication, 1 WPA/WPA2 protected private network). Rinsed and repeated each network a few times. Fingers crossed, this may be fixed. Can those of you who experience the same confirm? -- Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network https://bugs.launchpad.net/bugs/545443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559150] Re: Regression: Segfault with Radeon HD 3300
The latest version fixed this. ** Changed in: fglrx-installer (Ubuntu) Status: New = Fix Released -- Regression: Segfault with Radeon HD 3300 https://bugs.launchpad.net/bugs/559150 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545443] Re: Lucid on Asus EEE PC 901 Fails to connect to any wireless network
This still happens in Beta 2. Can we narrow it down to this specific PCI ID? RaLink RT2860 [1814:0781] with Subsystem: RaLink Device [1814:2790] ** Summary changed: - Lucid Beta 1 on Asus EEE PC 901 Fails to connect to any wireless network + Lucid on Asus EEE PC 901 Fails to connect to any wireless network ** Summary changed: - Lucid on Asus EEE PC 901 Fails to connect to any wireless network + Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network -- Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network https://bugs.launchpad.net/bugs/545443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559150] [NEW] Regression: Segfault with Radeon HD 3300
Public bug reported: Binary package hint: fglrx On a system upgraded from 9.10 to Lucid Beta 1, fglrx does not work and X.org crashes with a segfault. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: fglrx 2:8.721-0ubuntu8 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 CheckboxSubmission: e12cf30d2399f64fa5fe231c331b14d6 CheckboxSystem: fd6c484c0b5d20a2f1cd036ef0f63975 Date: Fri Apr 9 14:44:59 2010 DkmsStatus: fglrx, 8.721, 2.6.32-19-generic, x86_64: installed MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-19-generic root=/dev/mapper/sda6_crypt ro cryptopts=source=/dev/sda6,target=sda6_crypt quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fglrx-installer dmi.bios.date: 08/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A78T-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd08/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78T-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-19-generic ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Regression: Segfault with Radeon HD 3300 https://bugs.launchpad.net/bugs/559150 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559150] Re: Regression: Segfault with Radeon HD 3300
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/43537552/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/43537553/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/43537554/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/43537555/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/43537557/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/43537558/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/43537559/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/43537560/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/43537561/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/43537562/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/43537563/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/43537564/UdevLog.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/43537565/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/43537566/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/43537567/XorgLogOld.txt -- Regression: Segfault with Radeon HD 3300 https://bugs.launchpad.net/bugs/559150 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355279] Re: gst_pipeline_test crashed with GError in main()
Got this when I tried sound test in mythbuntu. -- gst_pipeline_test crashed with GError in main() https://bugs.launchpad.net/bugs/355279 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545443] Re: Lucid Beta 1 on Asus EEE PC 901 Fails to connect to any wireless network
We have confirmed this bug. I wonder how many affected EEE PC:s are being tested with lucid, because this could be pretty serious if it affects all 901 and 1000H (and other models?). ** Changed in: network-manager (Ubuntu) Status: New = Confirmed -- Lucid Beta 1 on Asus EEE PC 901 Fails to connect to any wireless network https://bugs.launchpad.net/bugs/545443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545443] Re: Lucid Beta 1 on Asus EEE PC 901 Fails to connect to any wireless network
I tried manually with iwconfig and dhclient to rule out NetworkManager, and confirmed it still happens. It seems setting the ESSID does not work correctly, only succeeding around one out of 5-10 times. Here's a quick test command that I used: sudo killall dhclient; sudo ifconfig wlan0 down; sleep 1; sudo ifconfig wlan0 up; sleep 1; sudo iwconfig wlan0 essid Wippies ap 0A:1D:19:AE:D2:B5; sleep 1; sudo iwconfig; sudo dhclient wlan0 - When the ESSID is not set the command exits normally but dhclient gets no address. - When the ESSID is set correctly, dhclient gets an address and everything else works. ** Package changed: network-manager (Ubuntu) = linux (Ubuntu) -- Lucid Beta 1 on Asus EEE PC 901 Fails to connect to any wireless network https://bugs.launchpad.net/bugs/545443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548679] Re: rhythmbox crashed with SIGSEGV in g_object_notify()
I get this too. ** Changed in: rhythmbox (Ubuntu) Status: New = Confirmed -- rhythmbox crashed with SIGSEGV in g_object_notify() https://bugs.launchpad.net/bugs/548679 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545443] [NEW] Lucid Beta 1 on Asus EEE PC 901 Fails to connect to any wireless network
Public bug reported: Binary package hint: network-manager This may also belong to linux. My Asus EEE PC 901 running lucid beta1 live cd from USB cannot connect to any WLAN network, protected or not. The same network works with the installed system (9.10), and with another computer running mythbuntu 10.04 beta1. Network manager tries to connect but fails after a timeout. ProblemType: Bug Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Tue Mar 23 22:47:22 2010 DistroRelease: Ubuntu 10.04 IfupdownConfig: auto lo iface lo inet loopback IpRoute: 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.110 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 10.0.0.1 dev eth0 proto static Keyfiles: Error: [Errno 2] No such file or directory LiveMediaBuild: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318) Package: network-manager 0.8-0ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SourcePackage: network-manager Uname: Linux 2.6.32-16-generic i686 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- Lucid Beta 1 on Asus EEE PC 901 Fails to connect to any wireless network https://bugs.launchpad.net/bugs/545443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545443] Re: Lucid Beta 1 on Asus EEE PC 901 Fails to connect to any wireless network
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/41770896/Dependencies.txt ** Attachment added: Gconf.txt http://launchpadlibrarian.net/41770897/Gconf.txt ** Attachment added: IpAddr.txt http://launchpadlibrarian.net/41770898/IpAddr.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/41770899/IwConfig.txt ** Attachment added: NetDevice.eth0.txt http://launchpadlibrarian.net/41770900/NetDevice.eth0.txt ** Attachment added: NetDevice.lo.txt http://launchpadlibrarian.net/41770901/NetDevice.lo.txt ** Attachment added: NetDevice.pan0.txt http://launchpadlibrarian.net/41770902/NetDevice.pan0.txt ** Attachment added: NetDevice.wlan0.txt http://launchpadlibrarian.net/41770903/NetDevice.wlan0.txt ** Attachment added: PciNetwork.txt http://launchpadlibrarian.net/41770904/PciNetwork.txt ** Attachment added: RfKill.txt http://launchpadlibrarian.net/41770905/RfKill.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/41770906/WifiSyslog.txt ** Attachment added: nm-system-settings.conf.txt http://launchpadlibrarian.net/41770907/nm-system-settings.conf.txt -- Lucid Beta 1 on Asus EEE PC 901 Fails to connect to any wireless network https://bugs.launchpad.net/bugs/545443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545443] Re: Lucid Beta 1 on Asus EEE PC 901 Fails to connect to any wireless network
I have to add that I did get it to connect once, but trying to connect again immediately after failed. I tried to reproduce this seemingly random success (simply boot from clean live USB with wired plugged in, and connect as soon as the desktop is available) but failed. -- Lucid Beta 1 on Asus EEE PC 901 Fails to connect to any wireless network https://bugs.launchpad.net/bugs/545443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
I tested Beta 1 and it now works fine out of the box. Good work, whoever did it! Closing the bug. ** Changed in: xserver-xorg-video-openchrome (Ubuntu) Status: Confirmed = Fix Released -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 460618] Re: GDI Metafile graphics get a Read Error and disappear after upgrading to Karmic
My setup is Ubuntu 9.10 with sun-java6 and at the time I was able to produce this with and without any custom settings. Today, I was unable to reproduce the bug. I am no longer actively working on the document in question, so I will not bump into it spontaneously. However, I'd be happy to help if I can. -- GDI Metafile graphics get a Read Error and disappear after upgrading to Karmic https://bugs.launchpad.net/bugs/460618 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
I have either an LCD over analog (=CRT in BIOS/xorg.conf) or PAL TV- Out (CRT+TV set in BIOS) but not both connected at the same time. The ActiveDevice option had no effect on the situation. However, this time, modeSwitch did. I tried a few different settings with Alpha 3: No xorg.conf (noxorg): failed as before disabled acceleration, no modeSwitch (xorg1): failed as well disabled acceleration, modeSwitch new (xorg2): worked! my optimal setup, now only missing TV-Out pars (xorg3): worked! I also tried removing DPMS and it still worked (I think it defaults to it anyway). Attaching confs and logs. ** Attachment added: crt-noxorg-log http://launchpadlibrarian.net/39956013/crt-noxorg-log -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
** Attachment added: crt-xorg1 http://launchpadlibrarian.net/39956025/crt-xorg1 -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
** Attachment added: crt-xorg1-log http://launchpadlibrarian.net/39956034/crt-xorg1-log -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
** Attachment added: crt-xorg2 http://launchpadlibrarian.net/39956048/crt-xorg2 -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
** Attachment added: crt-xorg2-log http://launchpadlibrarian.net/39956057/crt-xorg2-log -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
** Attachment added: crt-xorg3 http://launchpadlibrarian.net/39956061/crt-xorg3 -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
Bryce Harrington seems to have confirmed this bug, what hardware are you using? Maybe this new modeSwitch could be made the default for appropriate hardware? -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
** Attachment added: crt-xorg3-log http://launchpadlibrarian.net/39956087/crt-xorg3-log -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
You already suggested new mode switch, see results above. NoAccel did not help. -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
The hardware has a working TV-Out, yes. Mostly, I have tried using no xorg.conf (default) but all of the variations have likewise been in vain. I'll get back to you with some examples tomorrow from a daily build USB Live CD, as I have to recreate them. -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
This still happens on Alpha 3. I did a fresh re-install of 9.10 and it works well with the openchrome driver, so this seems to be a regression. I will continue testing 10.04 live CD builds from USB, get in touch with me if there is anything in specific you need tested. -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
The original setup was without xorg.conf. I created a simple xorg.conf and added the line you asked. Xorg says: (WW) CHROME(0): Option modeSwitch is not used There is no option to turn TV encoder off specifically as far as I know. It does not seem to matter what BIOS settings have been selected. -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
With the older via driver gone, and vesa not working with this chip for some reason, the only workaround available is fbdev. -- [CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] [NEW] Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome)
Public bug reported: When booting the live CD or USB, the screen goes blank when it starts xorg. Interestingly, the monitor stays on for a while and then seems to get power save commands normally. There is no picture, that's all. Going to a terminal works. Switching back does not help. The hardware is a VIA EPIA MII, using Chrome driver. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2951 F xfce4-volumed CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'V8235'/'VIA 8235 with VT1616i at 0xc000, irq 5' Mixer name : 'ICEnsemble VT1616i' Components : 'AC97a:49434552' Controls : 55 Simple ctrls : 33 DistroRelease: Ubuntu 10.04 IwConfig: lono wireless extensions. eth0 no wireless extensions. LiveMediaBuild: Mythbuntu 10.04 Lucid Lynx - Alpha i386 (20100113) Lsusb: Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0951:1600 Kingston Technology DataTraveler II Pen Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VIA Technologies, Inc. CLE266-8235 Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/mythbuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-10.14-generic Regression: Yes RelatedPackageVersions: linux-firmware 1.28 Reproducible: Yes RfKill: Tags: lucid needs-upstream-testing regression-potential TestedUpstream: No Uname: Linux 2.6.32-10-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 01/06/2004 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: 6.00 PG dmi.board.name: EPIA-M dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr6.00PG:bd01/06/2004:svnVIATechnologies,Inc.:pnCLE266-8235:pvr:rvn:rnEPIA-M:rvr:cvn:ct3:cvr: dmi.product.name: CLE266-8235 dmi.sys.vendor: VIA Technologies, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected -- Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Re: Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome)
apport information ** Tags added: apport-collected ** Description changed: When booting the live CD or USB, the screen goes blank when it starts xorg. Interestingly, the monitor stays on for a while and then seems to get power save commands normally. There is no picture, that's all. Going to a terminal works. Switching back does not help. The hardware is a VIA EPIA MII, using Chrome driver. + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 2951 F xfce4-volumed + CRDA: Error: [Errno 2] No such file or directory + Card0.Amixer.info: + Card hw:0 'V8235'/'VIA 8235 with VT1616i at 0xc000, irq 5' +Mixer name : 'ICEnsemble VT1616i' +Components : 'AC97a:49434552' +Controls : 55 +Simple ctrls : 33 + DistroRelease: Ubuntu 10.04 + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + LiveMediaBuild: Mythbuntu 10.04 Lucid Lynx - Alpha i386 (20100113) + Lsusb: + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 002: ID 0951:1600 Kingston Technology DataTraveler II Pen Drive + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: VIA Technologies, Inc. CLE266-8235 + Package: linux (not installed) + ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/mythbuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- + ProcEnviron: + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-10.14-generic + Regression: Yes + RelatedPackageVersions: linux-firmware 1.28 + Reproducible: Yes + RfKill: + + Tags: lucid needs-upstream-testing regression-potential + TestedUpstream: No + Uname: Linux 2.6.32-10-generic i686 + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare + dmi.bios.date: 01/06/2004 + dmi.bios.vendor: Award Software International, Inc. + dmi.bios.version: 6.00 PG + dmi.board.name: EPIA-M + dmi.chassis.type: 3 + dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr6.00PG:bd01/06/2004:svnVIATechnologies,Inc.:pnCLE266-8235:pvr:rvn:rnEPIA-M:rvr:cvn:ct3:cvr: + dmi.product.name: CLE266-8235 + dmi.sys.vendor: VIA Technologies, Inc. ** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/39368728/AlsaDevices.txt -- Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/39368734/BootDmesg.txt -- Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/39368735/Card0.Amixer.values.txt -- Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Card0.Codecs.codec97.0.ac97.0.0.txt
apport information ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt http://launchpadlibrarian.net/39368736/Card0.Codecs.codec97.0.ac97.0.0.txt -- Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Card0.Codecs.codec97.0.ac97.0.0.regs.txt
apport information ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt http://launchpadlibrarian.net/39368737/Card0.Codecs.codec97.0.ac97.0.0.regs.txt -- Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/39368738/CurrentDmesg.txt -- Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] Lspci.txt
apport information ** Attachment added: Lspci.txt http://launchpadlibrarian.net/39368739/Lspci.txt -- Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/39368729/AplayDevices.txt -- Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] ArecordDevices.txt
apport information ** Attachment added: ArecordDevices.txt http://launchpadlibrarian.net/39368731/ArecordDevices.txt -- Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/39368741/PciMultimedia.txt -- Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523911] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/39368743/ProcCpuinfo.txt -- Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII (Chrome) https://bugs.launchpad.net/bugs/523911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
