[Bug 1677082] Re: after suspend and bg, normally running pipeline job labeled "unknown signal (core dumped)"
Fixed in upstream versions 5.4+ and debian-testing ** Changed in: zsh Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677082 Title: after suspend and bg, normally running pipeline job labeled "unknown signal (core dumped)" To manage notifications about this bug go to: https://bugs.launchpad.net/zsh/+bug/1677082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613751] Re: journald forwards to syslog with facility=KERN on everything
Ugh, I meant Zesty in my previous comment, not "Zenial." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613751 Title: journald forwards to syslog with facility=KERN on everything To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1613751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613751] Re: journald forwards to syslog with facility=KERN on everything
Same issue exists in Zenial. However, the fix has just been merged into upstream master. It's a trivial one-line change. ** Tags added: zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613751 Title: journald forwards to syslog with facility=KERN on everything To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1613751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677082] Re: after suspend and bg, normally running pipeline job labeled "unknown signal (core dumped)"
** Bug watch added: Debian Bug tracker #859070 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859070 ** Also affects: zsh via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859070 Importance: Unknown Status: Unknown ** No longer affects: zsh ** Also affects: zsh (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859070 Importance: Unknown Status: Unknown ** Also affects: zsh 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/1677082 Title: after suspend and bg, normally running pipeline job labeled "unknown signal (core dumped)" To manage notifications about this bug go to: https://bugs.launchpad.net/zsh/+bug/1677082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662137] Re: 16.04 recovery shell works only for two minutes
Although I couldn't reproduce it in a VM, this reliably happens on both of my hardware installs, an old Thinkpad and an Asus Z87-based desktop. The recovery shell is completely unusable. Luckily Ctrl+Alt+Del still reboots the system cleanly. The workaround seems to be to boot directly to the systemd rescue (or emergency) target, instead of recovery. This can be done simply by adding "rescue" or "emergency" to the default linux command line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662137 Title: 16.04 recovery shell works only for two minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1662137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671991] Re: systemctl rescue leaves system inaccessible unless run from within active desktop session
Debian stretch has the opposite issue: there, rescue only works if no desktop session is active. Otherwise, whether systemctl is run from within that session or not, the console is left completely unusable; not even Ctrl+Alt+Del works. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858162 exists for that, but the Xenial issue is completely different: the console never becomes unresponsive. Instead, the system is stuck in some intermediate state where the normal getty is stlil alive, but login is not allowed, and the actual rescue prompt is never reached. ** Bug watch added: Debian Bug tracker #858162 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858162 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671991 Title: systemctl rescue leaves system inaccessible unless run from within active desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671991] Re: systemctl rescue leaves system inaccessible unless run from within active desktop session
** Summary changed: - init 1 locks you out of system immediately when run from virtual console + systemctl rescue leaves system inaccessible unless run from within active desktop session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671991 Title: systemctl rescue leaves system inaccessible unless run from within active desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677027] Re: installer silently assumed EFI using removable drive's partition, breaking grub isoboot
** Summary changed: - installer silently assumed EFI using removable drive's partition + installer silently assumed EFI using removable drive's partition, breaking grub isoboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677027 Title: installer silently assumed EFI using removable drive's partition, breaking grub isoboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1677027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677082] [NEW] after suspend and bg, normally running pipeline job labeled "unknown signal (core dumped)"
Public bug reported:
When a pipeline job is suspended and then backgrounded, 'jobs -l'
incorrectly lists the status of all but the first command in the
pipeline.
For example:
% cp /dev/null /tmp/emptyfile && tail -F /tmp/emptyfile | fgrep hello | sed
's/^/received: /'
^Z
zsh: suspended tail -F /tmp/emptyfile | fgrep hello | sed 's/^/received: /'
% jobs -l
[1] + 8096 suspended tail -F /tmp/emptyfile |
8097 suspended fgrep hello |
8098 suspended sed 's/^/received: /'
The confusion begins after the 'bg' command:
% bg
[1] + continued tail -F /tmp/emptyfile | fgrep hello | sed 's/^/received: /'
% jobs -l
[1] + 8096 runningtail -F /tmp/emptyfile |
8097 unknown signal (core dumped) fgrep hello |
8098 unknown signal (core dumped) sed 's/^/received: /'
The status above is wrong; both fgrep and sed are in fact running fine:
% echo hello world >> /tmp/emptyfile
% kill 8096 # flush the pipeline
% received: hello world
[1] + terminated tail -F /tmp/emptyfile |
donefgrep hello | sed 's/^/received: /'
%
Note also that the final status, printed when the commands actually
exit, is correct ('done').
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: zsh 5.1.1-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
Uname: Linux 4.4.0-70-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Tue Mar 28 18:58:32 2017
InstallationDate: Installed on 2017-03-27 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: zsh
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: zsh (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677082
Title:
after suspend and bg, normally running pipeline job labeled "unknown
signal (core dumped)"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1677082/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677034] Re: superfluous unmount prompts before installation, especially with grub isoboot
Forgot to mention, this was observed with the 16.04.1 and .2 desktop amd64 isos. ** Description changed: + [edit: Observed with Ubuntu 16.04.1 and .2 desktop amd64 ISOs] + 1. When using grub isoboot and the iso-scan boot parameter, the partition containing the ISO file is mounted at /isodevice and then /isodevice/.../ubuntu-whatever.iso is loopback-mounted at /cdrom. However, the graphical installer asks if the user wants to unmount it before starting the partitioner. If "no" is selected, the installation proceeds with no problem. I'm not sure what would happen if "yes," but presumably nothing good. We should recognize that /isodevice is a special/required mountpoint and not ask about it... 2. I'm also prompted to unmount some random SD card that happened to be in my laptop (/dev/mmcblk0). It's irrelevant to the installation, so I don't think it matters whether I answer yes or no. Something mounted this automatically in the first place though; is there any good reason for that? Also, if #2 occurs, it is presented in the same dialog as #1. So there is no way to keep the required /isodevice filesystem *and* unmount the unrelated one (except at the command line). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677034 Title: superfluous unmount prompts before installation, especially with grub isoboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1677034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677034] [NEW] superfluous unmount prompts before installation, especially with grub isoboot
Public bug reported: [edit: Observed with Ubuntu 16.04.1 and .2 desktop amd64 ISOs] 1. When using grub isoboot and the iso-scan boot parameter, the partition containing the ISO file is mounted at /isodevice and then /isodevice/.../ubuntu-whatever.iso is loopback-mounted at /cdrom. However, the graphical installer asks if the user wants to unmount it before starting the partitioner. If "no" is selected, the installation proceeds with no problem. I'm not sure what would happen if "yes," but presumably nothing good. We should recognize that /isodevice is a special/required mountpoint and not ask about it... 2. I'm also prompted to unmount some random SD card that happened to be in my laptop (/dev/mmcblk0). It's irrelevant to the installation, so I don't think it matters whether I answer yes or no. Something mounted this automatically in the first place though; is there any good reason for that? Also, if #2 occurs, it is presented in the same dialog as #1. So there is no way to keep the required /isodevice filesystem *and* unmount the unrelated one (except at the command line). ** Affects: ubiquity (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/1677034 Title: superfluous unmount prompts before installation, especially with grub isoboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1677034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677027] [NEW] installer silently assumed EFI using removable drive's partition
Public bug reported:
This issue was seen with the Ubuntu 16.04.1 and .2 desktop amd64 ISOs.
When the installer boots in EFI mode on a legacy BIOS system, it
normally presents the user with the choice of installing in legacy mode
or creating a new EFI partition, etc.
However, if any existing EFI partition is found, this question is
skipped and it is silently assumed that the installed system should boot
EFI, using that partition, even if that partition is on a removable
(USB, /dev/sdb) drive. This means that:
1) The target's /etc/fstab contains an entry to mount the removable EFI
partition at /boot/efi
2) The Ubuntu EFI files are installed into that partition
3) Unless manual partitioning has been used (as in the attached log),
the bootloader is also installed to the removable drive instead of the
hard drive (observed in a previous install).
For me, this resulted in a target system that booted perfectly fine, as
long as that removable drive is present. Discovered in time, it was easy
to fix by installing the grub-pc-bin package, running grub-install
--target=i386-pc /dev/sda, and rebooting. The problem also does not
occur if the installer boots in BIOS mode, regardless of the presence of
that EFI partition. (So forcing BIOS boot, if possible, is also a good
workaround, assuming one is aware of the problem in advance.)
Why does this matter, and why do I have a removable drive with an EFI
partition on it? Well, that is actually the drive I'm installing from,
using the extremely useful ability of grub (and casper) to boot an ISO
file directly from a filesystem, like this:
menuentry "Ubuntu 16.04.1 Live Desktop amd64" --class ubuntu {
set isoname="ubuntu-16.04.1-desktop-amd64.iso"
set isofile="${isopath}/ubuntu/${isoname}"
echo "Using ${isoname}..."
loopback loop $isofile
linux (loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=${isofile}
quiet splash
initrd (loop)/casper/initrd.lz
}
Everything is on the removable drive: grub, the grub config, the ISO
file itself, and of course the EFI partition.
Note that casper seems to have special support for this: it mounts the
partition containing the .iso file at /isodevice, then loopback mounts
/isodevice/whatever/ubuntu-16.04.1-desktop-amd64.iso at /cdrom before
the installation commences. All that works perfectly; the only issue is
this EFI thing (and another very minor issue which I will file
separately.)
I'm not sure there's a clear solution to this, unless the installer can
determine that an EFI partition is the same one it itself used to boot.
We can't just ignore all partitions on the same drive as /isodevice,
because grub isoboot is also useful to boot from an ISO file on a hard
drive partition (in which case, the behavior is more or less correct.)
It might simply be incorrect for the installer to assume anything about
EFI partitions outside of the drives chosen to install to.
I'm attaching the output of 'ubuntu-bug --save ubiquity' from the end of
the installation; I can't seem to directly submit the file now that I've
booted the system and ubiquity is no longer installed. Unfortunately it
didn't seem to include all the active mountpoints, but the issue is easy
enough to reproduce.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "ubiquity.bug"
https://bugs.launchpad.net/bugs/1677027/+attachment/4849191/+files/ubiquity.bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677027
Title:
installer silently assumed EFI using removable drive's partition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1677027/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613751] Re: journald forwards to syslog with facility=KERN on everything
** No longer affects: network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613751 Title: journald forwards to syslog with facility=KERN on everything To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1613751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326536] Re: libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in odd resolution behaviour on the VM
Right, my hack is almost the same as --no-hosts, it just doesn't require patching libvirt. Do you need that entry in your /etc/hosts? If you have a real DNS name, you might not need it at all. If not, but you have a static IP address, you could use that in the hosts file instead of 127.0.1.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326536 Title: libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in odd resolution behaviour on the VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1326536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613751] Re: journald forwards to syslog with facility=KERN on everything
** Bug watch added: Debian Bug tracker #837893 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837893 ** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837893 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613751 Title: journald forwards to syslog with facility=KERN on everything To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1613751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613751] Re: journald forwards to syslog with facility=KERN on everything
** Summary changed: - NM and gnome-session seem to be syslogging with facility KERN + journald forwards to syslog with facility=KERN on everything ** Package changed: gnome-session (Ubuntu) => systemd (Ubuntu) ** Bug watch added: github.com/systemd/systemd/issues #5640 https://github.com/systemd/systemd/issues/5640 ** Also affects: systemd via https://github.com/systemd/systemd/issues/5640 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613751 Title: journald forwards to syslog with facility=KERN on everything To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1613751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613751] Re: NM and gnome-session seem to be syslogging with facility KERN
This is actually getting worse in Debian stretch, and there affects almost 2 dozen packages, so it might not even be the packages' (NetworkManager, gnome-session) fault. Anyway, https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=858399 ** Bug watch added: Debian Bug tracker #858399 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858399 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613751 Title: NM and gnome-session seem to be syslogging with facility KERN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1613751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326536] Re: libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in odd resolution behaviour on the VM
I had the same problem (on 16.04.02) and came up with a rather dirty, but quick and effective workaround. Simply remove the libvirt-dnsmasq user's ability to read /etc/hosts: sudo setfacl -m user:libvirt-dnsmasq:--- /etc/hosts The libvirt dnsmasq instances will syslog a complaint when they start or get HUP'd. Otherwise, it seems to work perfectly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326536 Title: libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in odd resolution behaviour on the VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1326536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671991] Re: init 1 locks you out of system immediately when run from virtual console
Oops, I ran ubuntu-bug on 'init' instead of '/bin/init'. If I need to redo it to get more detailed logs, please let me know and I will. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671991 Title: init 1 locks you out of system immediately when run from virtual console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671991] Re: init 1 locks you out of system immediately when run from virtual console
** Attachment added: "Ubuntu-init1-fail-2017-03-10_22:40:50.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671991/+attachment/4835768/+files/Ubuntu-init1-fail-2017-03-10_22%3A40%3A50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671991 Title: init 1 locks you out of system immediately when run from virtual console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671991] [NEW] init 1 locks you out of system immediately when run from virtual console
Public bug reported: I don't think it's just me, as I'm able to reproduce this on 2 physical systems as well as a vanilla qemu/kvm instance, immediately after fresh installs from both ubuntu-16.04.1-desktop-amd64.iso and ubuntu-16.04.2 -desktop-amd64.iso When I run 'sudo init 1' or 'sudo telinit 1' from any virtual console, the system never gets to single-user mode. Instead, I am presented with a non-functioning login prompt and no way to actually interact with the machine except Ctrl-Alt-Del, which luckily still works. The login prompts look normal, but only appear on two virtual consoles: tty1 always, plus the one I was using (if it wasn't tty1). All others are blank. Typing my username results in the message "System is going down," instead of a password prompt. After a couple of minutes, it will clear the screen and draw a fresh prompt, with the same results; otherwise, nothing changes until I give the three-fingered salute to reboot. I've attached a screenshot from the VM. This happens regardless of whether I first log out of my desktop, stop the lightdm service entirely, or neither. The truly bizarre part is that if I enter the command from inside a gnome-terminal running on the desktop, it works as expected. It's a little unbelievable, but seems to be reliably reproduceable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: init 1.29ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 10 22:10:34 2017 InstallationDate: Installed on 2017-03-11 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: init-system-helpers UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Package changed: init-system-helpers (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671991 Title: init 1 locks you out of system immediately when run from virtual console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671355] [NEW] Outdated gnome-session files break System Settings menu
Public bug reported: The System Settings menu stopped working since Trusty. The reason is that the included gnome-session files are out of date: they use gnome- settings-daemon, but the required gnome-control-center is no longer installed by default. While installing that package makes it "work," I believe the correct fix is to do exactly what gnome-session-metacity already does, and use unity-settings-daemon/unity-control-center instead. The two files that need updating appear to have been cloned from gnome- flashback-metacity at some point in the past, and not gotten updated since. It's easy to just overwrite them with new ones: cd /usr/share/gnome-session/sessions && sed 's/metacity/xmonad/g' gnome-flashback-metacity > gnome-flashback-xmonad sed 's/metacity/xmonad/g' /usr/lib/gnome-flashback/gnome-flashback- metacity > /usr/bin/gnome-flashback-xmonad With these two changes, it works perfectly: unity-settings-daemon is running, and the Systems Settings menu brings up unity-control-panel. As an aside, that second file belongs in /usr/lib/gnome-flashback/, not /usr/bin. If moving it, simply update /usr/share/xsessions/gnome- flashback-xmonad.desktop with the new location. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xmonad 0.12-1 [modified: usr/share/gnome-session/sessions/gnome-flashback-xmonad.session usr/share/xsessions/gnome-flashback-xmonad.desktop] ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Mar 8 22:42:37 2017 InstallationDate: Installed on 2017-02-19 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xmonad UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xmonad (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671355 Title: Outdated gnome-session files break System Settings menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmonad/+bug/1671355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670875] Re: "Fake" transparency, w/ Flashback session and non-compositing WM, no longer works
Nevermind, it looks like support for background images in terminal widgets has been removed altogether, as explained here- https://bugs.launchpad.net/terminator/+bug/1635704 ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670875 Title: "Fake" transparency, w/ Flashback session and non-compositing WM, no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1670875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670875] [NEW] "Fake" transparency, w/ Flashback session and non-compositing WM, no longer works
Public bug reported: In Ubuntu 14.04 and earlier, gnome-terminal's transparent background option works well with gnome-session-flashback and a non-compositing window manager. I actually use xmonad, but metacity --no-composite shows the same behavior: instead of real transparency, the portion of the desktop background corresponding to the terminal window's relative position is drawn as the background, and is updated when the window moves. The attached screenshot demonstrates what this looks like in 14.04 with metacity. In Ubuntu 16.04, this no longer works: a solid black background is displayed instead. However, if I downgrade gnome-terminal to the trusty packages, it works as before. To reproduce: 1. execute sudo apt-get install gnome-session-flashback 2. log in with 'GNOME Flashback (Metacity)' session 3. start gnome-terminal and set background to transparent 4. execute metacity --no-composite --replace ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Mar 7 14:52:53 2017 InstallationDate: Installed on 2017-02-19 (16 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Screenshot_ubutest-legacy-bios_2017-03-07_14:50:53.png" https://bugs.launchpad.net/bugs/1670875/+attachment/4833193/+files/Screenshot_ubutest-legacy-bios_2017-03-07_14%3A50%3A53.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670875 Title: "Fake" transparency, w/ Flashback session and non-compositing WM, no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1670875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612895] Re: Display freezes on 2nd+subsequent logins
Sorry for the delay. I've just installed the apparent latest kernel,
which is v4.9-rc1. So far, I haven't been able to reproduce the problem
with it, unlike previous kernels 4.8-rc2 and 4.4.0-{31,34,43}. Looks
like it might be fixed!
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612895
Title:
Display freezes on 2nd+subsequent logins
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612895/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1612895] Re: Display freezes on 2nd+subsequent logins
I'm traveling at the moment but I'll do that as soon as I can and report back... What to think about the fact that the 4.4 kernel works fine with trusty, though? I am afraid to install the newer xorg there, in case it's the true cause of the issue. Is it worth doing a new trusty install and then upgrading X (as well as the kernel)? On Thu, Sep 1, 2016, 11:41 Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > Nathan Dorfman, to keep this relevant to upstream, one would want to > test the latest mainline kernel (now 4.8-rc4) as it is released. > > Could you please advise? > > ** Tags added: bios-outdated-1.48 > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1612895 > > Title: > Display freezes on 2nd+subsequent logins > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > First boot after a fresh install of 16.04 from the 16.04.1 amd64 > desktop ISO, with 'download updates' enabled. This is alongside an > existing 14.04 installation, which continues to work flawlessly. In > particular, this issue cannot be reproduced there. (I've installed the > -lts-xenial kernel package there, so it's version 4.4.0.34.24, but NOT > the xorg ones.) > > The first login on the new system worked fine. After simply logging > out and in again, the display freezes just after drawing my user's > desktop. (This first time, everything was drawn, but on subsequent > attempts the background was black and the top Unity panel was empty.) > The mouse cursor is movable, but no button or key presses are > recognized. > > Eventually, I press Ctrl+Alt+F1. The mouse cursor disappears > immediately; the display stays frozen and otherwise unchanged. After > another two minutes or so of waiting, I am finally dumped to the > virtual tty, which works fine. At this point a couple of kernel stack > traces appear in dmesg (see below), with timestamps corresponding to > "just now," i.e. when the vty switch finally occurred. > > Switching back to the X vty via Alt+F7 brings me back to the still- > frozen display, at which point all I can do is Ctrl+Alt+F1 and wait ~2 > minutes again. Stopping, then starting the lightdm service brings me > back to a working login screen, but logging in just freezes right back > again. Finally, rebooting the system allows me to login to a working > desktop exactly once -- logging out and in again reproduces this > problem reliably. > > The full dmesg is attached, but the short version is that stack traces > appear in pairs, summarized by the following lines on the first > occurrence: > > [ 242.116429] WARNING: CPU: 2 PID: 2539 at > /build/linux-dcxD3m/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326 > drm_wait_one_vblank+0x1b5/0x1c0 [drm]() > [ 242.116498] CPU: 2 PID: 2539 Comm: Xorg Not tainted 4.4.0-31-generic > #50-Ubuntu > > and by the following, slightly different ones, on the second and > beyond: > > [ 380.232443] WARNING: CPU: 1 PID: 4173 at > /build/linux-dcxD3m/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:3963 > intel_crtc_wait_for_pending_flips+0x1e2/0x240 [i915]() > [ 380.232563] CPU: 1 PID: 4173 Comm: Xorg Tainted: GW > 4.4.0-31-generic #50-Ubuntu > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: > boot/vmlinuz-4.4.0-31-generic] > ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 > Uname: Linux 4.4.0-31-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.1 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: who3445 F pulseaudio > CurrentDesktop: Unity > Date: Fri Aug 12 19:51:28 2016 > HibernationDevice: RESUME=UUID=2065ee3e-d689-4432-a805-4a7822b06d0e > InstallationDate: Installed on 2016-08-13 (0 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: LENOVO 4236AR5 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic > root=UUID=093a7652-dfb2-4f9e-9ceb-23761b18c8ef ro quiet splash > RelatedPackageVersions: >linux-restricted-modules-4.4.0-31-generic N/A >linux-backports-modules-4.4.0-31-generic N/A >linux-firmware1.157.2 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/31/2011 > dmi.bios.vendor: LENOVO > dmi.bios.version: 83ET66WW (1.36 ) > dmi.
[Bug 1614263] [NEW] Laptop sometimes doesn't resume after suspend
Public bug reported: Most of the time, everything works fine, but every 5 or 10 suspends or so I can't resume. Normally the laptop resumes on any keypress. On these occasions, no keypresses, Ctrl-Alt-Dels, or power button presses have any effect. The power button continues to blink slowly indicating suspended state, and the indicator for plugged in status continues to respond. Other than that only the long power button press to force power-off does anything. On the plus side, this has been going on for a while but I have yet to have a dirty filesystem afterwards. I'm also pretty sure this was happening with the 3.19 kernel as well, but will set that as the default for the next few boots to try to confirm. I'm prepared to be told this is a hardware issue, but as the laptop works great with Ubuntu 14.04 aside from this one issue for about a year now, I'd love to know how to find out more about it at the very least. (16.04 is a different story altogether, but nothing susres-related, yet...) Lastly, I wasn't sure about the right way to report this. apport notices it on the next boot, and uploads a "crash report," but it doesn't go to launchpad by default. I know I can change this, but am I supposed to? The .crash file itself is attached. However, on casual/untrained inspection, it doesn't appear to be terribly useful? Despite calling itself a KernelOops, there doesn't seem to be anything from the kernel, there or in kern.log. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53~14.04.1 ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 17 13:38:31 2016 InstallationDate: Installed on 2015-11-22 (269 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "susres.2016-08-17_20:13:46.179455.crash" https://bugs.launchpad.net/bugs/1614263/+attachment/4722987/+files/susres.2016-08-17_20%3A13%3A46.179455.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614263 Title: Laptop sometimes doesn't resume after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1614263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612895] Re: Display freezes on 2nd+subsequent logins
Forgot to mention: in the kern.log attached above, there are some new messages with the 4.8.0-rc2 kernel that weren't present with 4.4.0-31: Aug 15 18:47:06 panzer kernel: [ 310.233191] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:26:pipe A] flip_done timed out These appear numerous times, in addition to the 'vblank timed out' messages and associated stack trace, which also appeared as before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612895 Title: Display freezes on 2nd+subsequent logins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613751] [NEW] NM and gnome-session seem to be syslogging with facility KERN
Public bug reported: NetworkManager's copious syslog output is for some reason making its way into my /var/log/kern.log file. This includes a couple dozen lines at startup and a similar amount when connecting to WiFi with DHCP. The NM man page states that the default facility should be DAEMON, as does the NM wiki -- see http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html and https://wiki.gnome.org/Projects/NetworkManager/Debugging Hopefully, it goes without saying that the KERN facility is reserved for the kernel and shouldn't be messed with by anything from userland. Nothing in the rsyslog configs references kern.log except the one expected line: /etc/rsyslog.d/50-default.conf:kern.* -/var/log/kern.log Nothing in NetworkManager.conf references syslog or its facilities. Oh, and these messages do also correctly make it to syslog.log. I've no idea how or why they also end up in kern.log, though. This doesn't happen on Ubuntu 14.04: % zgrep -cv kernel: /var/log/kern.log* /var/log/kern.log:0 /var/log/kern.log.1:0 /var/log/kern.log.2.gz:0 /var/log/kern.log.3.gz:0 /var/log/kern.log.4.gz:0 On Ubuntu 16.04.1, NM is the major culprit, although there were also a few lines from gnome-session: % zgrep -cv kernel: /mnt/var/log/kern.log* /mnt/var/log/kern.log:402 /mnt/var/log/kern.log.1:722 % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager 17 % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 'gnome-session-binary' 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 16 06:53:42 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-13 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 86180F 674c9d27-1bb1-4055-a6e4-07de9abbb586 /org/freedesktop/NetworkManager/ActiveConnection/0 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "kern.log" https://bugs.launchpad.net/bugs/1613751/+attachment/4721988/+files/kern.log ** Also affects: gnome-session (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/1613751 Title: NM and gnome-session seem to be syslogging with facility KERN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1613751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612895] Re: Display freezes on 2nd+subsequent logins
Thanks for the suggestion. Unfortunately, it's at least as bad with the new kernel; maybe worse. So first of all, "2nd login" doesn't reproduce the issue 100% reliably after all. I tested one last time with kernel 4.4.0-31, and the same exact problem occurred again, but on the 3rd, not 2nd login. I then rebooted into the new kernel 4.8.0-040800rc2, and was able to reproduce it, but it was after the 3rd *logout.* The machine froze on the black console screen that normally appears just momentarily after the desktop goes away but before the lightdm login screen reappears. After eventually regaining control, I logged in again and the display froze shortly before the desktop was completely drawn, more or less as expected. Unfortunately, this time Ctrl+Alt+F1 had no effect after any length of time. Having neglected to first install sshd, I had to hard reset the machine after 30 minutes or so of waiting. I haven't had that happen with the old kernel, but that could also just be luck. By the way, is it possible this bug should be against Xorg instead? The kernel version on my 14.04 installation is 4.4.0-34, or pretty close to the 4.4.0-31 kernel I'm having issues with. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612895/+attachment/4721919/+files/kern.log ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612895 Title: Display freezes on 2nd+subsequent logins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612895] Re: Display freezes on 2nd+subsequent logins
Forgot to mention: in the kern.log attached above, there are some new messages with the 4.8.0-rc2 kernel that weren't present with 4.4.0-31: Aug 15 18:47:06 panzer kernel: [ 310.233191] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:26:pipe A] flip_done timed out These appear numerous times, in addition to the 'vblank timed out' messages and associated stack trace, which also appeared as before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612895 Title: Display freezes on 2nd+subsequent logins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612901] Re: Slightly misleading warning after manual partition selection
Sorry, not sure how I managed to mark this as package linux. Hopefully I've correctly fixed it to fall under ubiquity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612901 Title: Slightly misleading warning after manual partition selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1612901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612901] [NEW] Slightly misleading warning after manual partition selection
Public bug reported: This might be too minor to even be worth mentioning, but I just happened to notice that it wasn't quite correct. When installing Ubuntu (using the 16.04.1 desktop amd64 ISO), I selected the 'something else' option for manual partitioning, then did only the following two things: 1. Marked existing partition /dev/sda7 for formatting as ext4 and mounting at / 2. Marked existing partition /dev/sda8 for use as swap The confirmation dialog that appears next correctly notes those two things, but first states that "the partition table on /dev/sda will be modified." I haven't changed the partition table at all, though. After finishing the installation, it doesn't appear to have been messed with, so I'm guessing the message is just wrong. I wonder if it actually meant to say, "the master boot record of /dev/sda will be modified?" ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612901 Title: Slightly misleading warning after manual partition selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1612901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612895] Re: Display freezes on 2nd+subsequent logins
I also took an ubuntu-bug --save of xorg. Trying to update this report with it didn't work (apport-cli -u tells me I must use apport-collect, which has no option to use an existing save file), but it is attached in its raw form. ** Attachment added: "bug2.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612895/+attachment/4720027/+files/bug2.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612895 Title: Display freezes on 2nd+subsequent logins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612895] [NEW] Display freezes on 2nd+subsequent logins
Public bug reported: First boot after a fresh install of 16.04 from the 16.04.1 amd64 desktop ISO, with 'download updates' enabled. This is alongside an existing 14.04 installation, which continues to work flawlessly. In particular, this issue cannot be reproduced there. (I've installed the -lts-xenial kernel package there, so it's version 4.4.0.34.24, but NOT the xorg ones.) The first login on the new system worked fine. After simply logging out and in again, the display freezes just after drawing my user's desktop. (This first time, everything was drawn, but on subsequent attempts the background was black and the top Unity panel was empty.) The mouse cursor is movable, but no button or key presses are recognized. Eventually, I press Ctrl+Alt+F1. The mouse cursor disappears immediately; the display stays frozen and otherwise unchanged. After another two minutes or so of waiting, I am finally dumped to the virtual tty, which works fine. At this point a couple of kernel stack traces appear in dmesg (see below), with timestamps corresponding to "just now," i.e. when the vty switch finally occurred. Switching back to the X vty via Alt+F7 brings me back to the still- frozen display, at which point all I can do is Ctrl+Alt+F1 and wait ~2 minutes again. Stopping, then starting the lightdm service brings me back to a working login screen, but logging in just freezes right back again. Finally, rebooting the system allows me to login to a working desktop exactly once -- logging out and in again reproduces this problem reliably. The full dmesg is attached, but the short version is that stack traces appear in pairs, summarized by the following lines on the first occurrence: [ 242.116429] WARNING: CPU: 2 PID: 2539 at /build/linux-dcxD3m/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326 drm_wait_one_vblank+0x1b5/0x1c0 [drm]() [ 242.116498] CPU: 2 PID: 2539 Comm: Xorg Not tainted 4.4.0-31-generic #50-Ubuntu and by the following, slightly different ones, on the second and beyond: [ 380.232443] WARNING: CPU: 1 PID: 4173 at /build/linux-dcxD3m/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:3963 intel_crtc_wait_for_pending_flips+0x1e2/0x240 [i915]() [ 380.232563] CPU: 1 PID: 4173 Comm: Xorg Tainted: GW 4.4.0-31-generic #50-Ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: boot/vmlinuz-4.4.0-31-generic] ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: who3445 F pulseaudio CurrentDesktop: Unity Date: Fri Aug 12 19:51:28 2016 HibernationDevice: RESUME=UUID=2065ee3e-d689-4432-a805-4a7822b06d0e InstallationDate: Installed on 2016-08-13 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 4236AR5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=093a7652-dfb2-4f9e-9ceb-23761b18c8ef ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET66WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236AR5 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET66WW(1.36):bd10/31/2011:svnLENOVO:pn4236AR5:pvrThinkPadT420:rvnLENOVO:rn4236AR5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4236AR5 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1612895/+attachment/4720010/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612895 Title: Display freezes on 2nd+subsequent logins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
I had this problem with the 16.04.1 desktop amd64 stick I made on my 14.04 system, but I just had to enter "live" at the prompt to boot into the live desktop and install as normal. After doing that and booting into the new live system, it was also easy to "fix" the USB stick permanently with the new syslinux available therein, as detailed here: https://askubuntu.com/questions/486602/ubuntu-14-04-lts-live-usb-boot- error-gfxboot-c32not-a-valid-com32r-image/746412#746412 As for the newer version of creator included with 16.04, its behavior was rather unexpected. Instead of copying files into the existing filesystem and installing syslinux nondestructively, it seems to simply write a raw binary image over the first 1.5GB of the disk. It warned me and all, but I didn't see any other option. It didn't have the COM32R error at boot, but I personally feel the destructive copying is much worse. Did I mess something up, or is that the intended behavior now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069793] Re: Can't install search engines (Tramples over window.external)
I ended up removing all four addons from my system (since they seem to be unmaintained and/or deprecated); here are the package names: xul-ext-ubufox - Ubuntu modifications for Firefox xul-ext-unity - Firefox extension: Unity Integration xul-ext-webaccounts - Ubuntu Online Accounts extension for firefox xul-ext-websites-integration - Firefox extension: Website Integration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069793 Title: Can't install search engines (Tramples over window.external) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-firefox-extension/+bug/1069793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069793] Re: Can't install search engines (Tramples over window.external)
Bug also exists in fresh installation of 14.04.3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069793 Title: Can't install search engines (Tramples over window.external) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-firefox-extension/+bug/1069793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491969] [NEW] Search extensions from addons.mozilla.org can't be installed
Public bug reported: This seems to be a bug in the Ubuntu version of Firefox -- started with a Mozilla ticket here https://bugzilla.mozilla.org/show_bug.cgi?id=1166508 The short version is that search extensions from addons.mozilla.org fail to install with the error "Sorry, you need a Mozilla-based browser (such as Firefox) to install a search plugin." This can be observed either by navigating directly to, e.g., https://addons.mozilla.org/en- US/firefox/addon/wolfram-alpha-searchextension/ OR by going to Preferences | Search | Add more search engines... in the Firefox menu. I just got a chance to try this immediately after a fresh install of 14.04.3 x64 desktop, fresh /home and everything, and got the same error. So, it seems to clearly be an Ubuntu bug. However, deleting the preinstalled plugins in /usr/lib/mozilla/plugins/ doesn't work around the issue. The only thing that does is restarting in safe mode (via the Firefox help menu). ** Affects: firefox (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/1491969 Title: Search extensions from addons.mozilla.org can't be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1491969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1001842] Re: No Audio from HDMI After Switching Monitor Off / On
I'm having the same problem in Ubuntu 14.04.1 LTS using on-board Intel graphics, no binary drivers in sight. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001842 Title: No Audio from HDMI After Switching Monitor Off / On To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1001842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349011] Re: nm-l2tp-service needs exception in ppp ip-up/down scripts
** Branch linked: lp:~ndorf/ubuntu/trusty/resolvconf/fix_lp_1349011 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349011 Title: nm-l2tp-service needs exception in ppp ip-up/down scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1349011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349011] Re: nm-l2tp-service needs exception in ppp ip-up/down scripts
** Changed in: resolvconf (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349011 Title: nm-l2tp-service needs exception in ppp ip-up/down scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1349011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349011] Re: nm-l2tp-service needs exception in ppp ip-up/down scripts
\o/ Thanks again :) That is in most cases the *desired* behavior, On today's systems, I don't think so. Debian and Ubuntu run a dnsmasq instance by default, with the only nameserver in /etc/resolv.conf being 127.0.1.1. Rather than overwrite this local caching server with any remote one, it makes more sense to reconfigure *it* to include/remove the new nameservers. Not only can you continue to benefit from the cache, but it's smart enough to route lookups to different servers depending on the domain. That's a benefit because: since only the VPN nameservers have name information about both the VPN and the Internet. Also, under what circumstances do you not trust the VPN with your DNS traffic? Well, if you work at home and connect to an employer's VPN, what earthly reason is there to send them all your Internet DNS lookups? It's far preferable to only use their nameservers just for employer.com and 99.10 .in-addr.arpa, or whatever. Not only that, but if you have a local nameserver that provides local names, you really don't want to wait for the remote to time out before querying those, either. That's exactly what NetworkManager does, simply by sending dnsmasq a DBus message with the new servers, and (optionally) what zones to use them for. However, it only works if the specific plugin in use is excluded from resolvconf's ppp/ip-up script. Come to think of it, there's a growing number of NM VPN plugins in the repos nowadays. There has to be a better way of handling this than excluding every one specifically... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349011 Title: nm-l2tp-service needs exception in ppp ip-up/down scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1349011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217407] Re: whoopsie spams the log with online messages
On an up to date 14.04 LTS system, I have what I guess is a mild remnant of the original bug? syslog.1:Nov 23 14:45:36 vane whoopsie[1280]: message repeated 73 times: [ offline] syslog.1:Nov 24 08:33:59 vane whoopsie[1280]: online syslog.1:Nov 24 08:34:01 vane whoopsie[1280]: message repeated 3 times: [ online] syslog.1:Nov 24 08:56:55 vane whoopsie[1280]: offline syslog.1:Nov 24 20:09:37 vane whoopsie[1280]: message repeated 3 times: [ offline] syslog.1:Nov 24 20:09:37 vane whoopsie[1280]: online No more log messages as of now, Tue Nov 25 11:46:47 EST, which is nice. The 73 redundant offline messages would seem to satisfy the definition of spamming syslog. I personally couldn't stomach reopening this bug myself though, at least not without the ability to also change importance to low. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217407 Title: whoopsie spams the log with online messages To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1217407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349011] Re: nm-l2tp-service needs exception in ppp ip-up/down scripts
** Description changed:
There is an actively maintained NetworkManager L2TP VPN plugin,
available as an Ubuntu package here: https://launchpad.net/~seriy-
pr/+archive/ubuntu/network-manager-l2tp. Hopefully it will be a part of
Ubuntu soon.
Like nm-pptp-service, it needs an exception in
/etc/ppp/ip-{up,down}.d/000resolvconf (part of the resolvconf package)
as follows:
- % diff /etc/ppp/ip-up.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-up
- 16c16
-nm-l2tp-service-*|nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
- ---
-nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
-
- % diff /etc/ppp/ip-down.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-down
+ % diff /etc/ppp/ip-up.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-up
16c16
nm-l2tp-service-*|nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
---
nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
Since that's how it works for the PPTP plugin, could we add the L2TP one
as well so that it can work out of the box on Ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349011
Title:
nm-l2tp-service needs exception in ppp ip-up/down scripts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1349011/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349011] Re: nm-l2tp-service needs exception in ppp ip-up/down scripts
Thanks Thomas, I see that your change has made it to vivid (Ubuntu 15.04). Could this fix be considered for trusty-updates? Without it, users of the L2TP plugin are faced with a rather subtle, but quite undesirable behavior: all DNS queries go to the VPN nameservers, even if the VPN is not a default route, in which case this could reasonably be considered a security violation (leaking of private information, namely all your Internet DNS lookups, no pun intended). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349011 Title: nm-l2tp-service needs exception in ppp ip-up/down scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1349011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217407] Re: whoopsie spams the log with online messages
Well, I guess it's a little better than before. Fresh install of 14.04: Jul 26 00:18:18 vane whoopsie[996]: whoopsie 0.2.24.6 starting up. Jul 26 00:18:18 vane whoopsie[996]: Using lock path: /var/lock/whoopsie/lock Jul 26 00:18:18 vane whoopsie[1041]: offline Jul 26 00:18:22 vane whoopsie[1041]: message repeated 2 times: [ offline] Jul 26 00:18:22 vane whoopsie[1041]: online Jul 26 00:35:38 vane whoopsie[1041]: message repeated 6 times: [ online] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217407 Title: whoopsie spams the log with online messages To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/1217407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264691] Re: Please add NM option for connecting to L2TP IPSEC VPN
The network-manager-l2tp package in #37 works very well for me, using Ubuntu 14.04 to connect to a Cisco L2TP/IPsec VPN. (Just a couple of minor tweaks needed to get the IPsec part working, for me.) This project works, is well-integrated with Network Manager, and has an active and helpful developer. It should be added to Ubuntu ASAP, IMO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/264691 Title: Please add NM option for connecting to L2TP IPSEC VPN To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/264691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349011] [NEW] nm-l2tp-service needs exception in ppp ip-up/down scripts
Public bug reported:
There is an actively maintained NetworkManager L2TP VPN plugin,
available as an Ubuntu package here: https://launchpad.net/~seriy-
pr/+archive/ubuntu/network-manager-l2tp. Hopefully it will be a part of
Ubuntu soon.
Like nm-pptp-service, it needs an exception in
/etc/ppp/ip-{up,down}.d/000resolvconf (part of the resolvconf package)
as follows:
% diff /etc/ppp/ip-up.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-up
16c16
nm-l2tp-service-*|nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
---
nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
% diff /etc/ppp/ip-down.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-down
16c16
nm-l2tp-service-*|nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
---
nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
Since that's how it works for the PPTP plugin, could we add the L2TP one
as well so that it can work out of the box on Ubuntu?
** Affects: resolvconf (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/1349011
Title:
nm-l2tp-service needs exception in ppp ip-up/down scripts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1349011/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1217407] Re: whoopsie spams the log with online messages
Huh. For me, it started happening immediately with a fresh install of 13.10. Networking is also vanilla -- just using the default Wired connection profile, DHCP everything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217407 Title: whoopsie spams the log with online messages To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/1217407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1217407] Re: whoopsie spams the log with online messages
Eh, my workaround was apt-get purge whoopsie. Very effective. :) I'd like to be a good citizen, though, so I'll reinstall it once I see it marked fixed. On Wed, Jan 29, 2014 at 12:01 PM, Romano Giannetti romano.gianne...@gmail.com wrote: @Brian: this is what you see if whoopsie is the only thing reporting on syslog. If any other thing report something, it breaks the repeated logic of the syslog daemon and you ends up with the thing reported here. What should happen is that whoopsie should log the online message only when it is BACK online (from offline or other statuses), not every few seconds of so. The logic would be something like (pseudo code). if status==ONLINE and last_syslog_message==ONLINE then do nothing else log ONLINE fi Meanwhile, a workaround is offered here: http://askubuntu.com/a/407935/16395: you can add this in /etc/rsyslog.d/00-whoopsie.conf and the messages won't be logged anymore: # whoopsie generates a lot of messages of online # these are worthless and can be filtered if $programname == 'whoopsie' and $msg == ' online' then ~ but that way you do not see even the first online which is arguably worth to be logged. -- You received this bug notification because you are subscribed to a duplicate bug report (1264798). https://bugs.launchpad.net/bugs/1217407 Title: whoopsie spams the log with online messages Status in Ubuntu error tracker client (whoopsie): Confirmed Status in “whoopsie” package in Ubuntu: Confirmed Bug description: It is mostly the online messages: $ grep whoopsie /var/log/syslog Aug 27 07:42:21 xango3 whoopsie[1832]: online Aug 27 07:42:27 xango3 whoopsie[1832]: online Aug 27 07:43:32 whoopsie[1832]: last message repeated 18 times Aug 27 07:44:50 whoopsie[1832]: last message repeated 17 times Aug 27 07:45:50 whoopsie[1832]: last message repeated 16 times Aug 27 07:46:50 whoopsie[1832]: last message repeated 16 times Aug 27 07:47:50 whoopsie[1832]: last message repeated 18 times Aug 27 07:48:50 whoopsie[1832]: last message repeated 15 times Aug 27 07:49:50 whoopsie[1832]: last message repeated 16 times Aug 27 07:50:50 whoopsie[1832]: last message repeated 21 times Aug 27 07:51:50 whoopsie[1832]: last message repeated 18 times Aug 27 07:52:50 whoopsie[1832]: last message repeated 20 times Aug 27 07:53:50 whoopsie[1832]: last message repeated 22 times Aug 27 07:54:50 whoopsie[1832]: last message repeated 15 times Aug 27 07:55:50 whoopsie[1832]: last message repeated 22 times Aug 27 07:56:50 whoopsie[1832]: last message repeated 20 times Aug 27 07:57:50 whoopsie[1832]: last message repeated 18 times Aug 27 07:58:51 whoopsie[1832]: last message repeated 16 times Aug 27 07:59:46 whoopsie[1832]: last message repeated 17 times Aug 27 07:59:47 xango3 whoopsie[1832]: online Aug 27 08:00:51 whoopsie[1832]: last message repeated 24 times Aug 27 08:01:51 whoopsie[1832]: last message repeated 24 times Aug 27 08:02:51 whoopsie[1832]: last message repeated 19 times Aug 27 08:03:51 whoopsie[1832]: last message repeated 19 times Aug 27 08:04:51 whoopsie[1832]: last message repeated 17 times Aug 27 08:05:51 whoopsie[1832]: last message repeated 19 times Aug 27 08:06:51 whoopsie[1832]: last message repeated 16 times Aug 27 08:07:51 whoopsie[1832]: last message repeated 18 times Aug 27 08:08:51 whoopsie[1832]: last message repeated 28 times Aug 27 08:09:51 whoopsie[1832]: last message repeated 21 times Aug 27 08:10:51 whoopsie[1832]: last message repeated 22 times Aug 27 08:11:51 whoopsie[1832]: last message repeated 20 times Aug 27 08:12:51 whoopsie[1832]: last message repeated 18 times Aug 27 08:13:51 whoopsie[1832]: last message repeated 16 times Aug 27 08:14:51 whoopsie[1832]: last message repeated 18 times Aug 27 08:15:51 whoopsie[1832]: last message repeated 18 times Aug 27 08:16:51 whoopsie[1832]: last message repeated 15 times Aug 27 08:17:01 whoopsie[1832]: last message repeated 2 times Aug 27 08:17:12 xango3 whoopsie[1832]: online Aug 27 08:18:21 whoopsie[1832]: last message repeated 22 times Aug 27 08:19:21 whoopsie[1832]: last message repeated 15 times Aug 27 08:19:44 whoopsie[1832]: last message repeated 5 times Aug 27 08:19:44 xango3 whoopsie[1832]: online Aug 27 08:20:48 whoopsie[1832]: last message repeated 29 times Aug 27 08:21:49 whoopsie[1832]: last message repeated 23 times Aug 27 08:22:50 whoopsie[1832]: last message repeated 24 times Aug 27 08:23:05 whoopsie[1832]: last message repeated 8 times Aug 27 08:23:10 xango3 whoopsie[1832]: online Aug 27 08:23:11 xango3 whoopsie[1832]: online Aug 27 08:23:15 xango3 whoopsie[1832]: online Aug 27 08:23:16 xango3 whoopsie[1832]: online Aug 27 08:24:17 whoopsie[1832]: last message repeated 22 times Aug 27 08:24:27 xango3 whoopsie[1832]: online Aug 27 08:24:28
[Bug 1221356] Re: hd-media installer rejects official raring ISO
It turns out that there's an even better way to install all versions of
Ubuntu, including 13.10, using a USB stick. It's easy, doesn't affect
any existing files on the USB drive, and offers maximum flexibility at
boot using grub. In my opinion it should be the first and foremost
recommended installation method. Here's what I just did to install saucy
on my previous raring machine:
1. Run the following command as root. This will install the bootloader
and create a /boot/grub directory on the drive, but won't touch any
other files. Very little space is required.
grub-install --no-floppy --boot-
directory=/media/$USER/$DISK_NAME/boot /dev/$DISK_DEVICE
2. Copy the Ubuntu installation ISO to a location of your choice on the
USB drive, for instance /isos. If you want to be able to boot other
versions of Ubuntu from the same drive, copy the corresponding ISOs as
well.
3. Create a /boot/grub/grub.cfg file on the drive, containing a
menuentry like the following for each ISO you want to boot:
set timeout=10
set default=0
menuentry Ubuntu 13.10 Saucy amd64 {
set iso=/isos/ubuntu-13.10-desktop-amd64.iso
loopback loop $iso
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$iso splash --
initrd (loop)/casper/initrd.lz
}
(If you have only one menuentry, you may want to set the timeout to 1-3
or even 0.)
That's it, you can now boot from the USB stick. This was much cleaner
than the usb-creator-gtk tool, which unpacked the ISO into the USB
drive's root directory. It also segfaulted about 5 times before
successfully completing, while this method worked on the first attempt
:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1221356
Title:
hd-media installer rejects official raring ISO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/installation-guide/+bug/1221356/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264798] [NEW] whoopsie spamming syslog
Public bug reported: Fresh install of saucy amd64 on a previously error-free raring machine. In /var/log/syslog: Dec 28 23:50:11 vane whoopsie[1098]: online Dec 28 23:51:12 whoopsie[1098]: last message repeated 5 times Dec 28 23:52:17 whoopsie[1098]: last message repeated 5 times Dec 28 23:53:39 whoopsie[1098]: last message repeated 5 times Dec 28 23:54:39 whoopsie[1098]: last message repeated 3 times Dec 28 23:55:39 whoopsie[1098]: last message repeated 3 times Dec 28 23:56:39 whoopsie[1098]: last message repeated 4 times Dec 28 23:57:39 whoopsie[1098]: last message repeated 6 times Dec 28 23:58:17 whoopsie[1098]: last message repeated 3 times and so on. I'm getting about 100 lines an hour. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: whoopsie 0.2.24.1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CrashReports: 600:108:114:0:2013-12-29 01:30:10.566606354 -0500:2013-12-29 01:30:10.566606354 -0500:/var/crash/_usr_lib_udisks2_udisksd.0.uploaded 640:0:114:1518146:2013-12-29 00:51:07.458631753 -0500:2013-12-29 01:30:09.674606364 -0500:/var/crash/_usr_lib_udisks2_udisksd.0.crash 644:0:114:0:2013-12-29 00:52:20.014631000 -0500:2013-12-29 00:52:20.014631000 -0500:/var/crash/_usr_lib_udisks2_udisksd.0.upload Date: Sun Dec 29 01:32:01 2013 InstallationDate: Installed on 2013-12-29 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1264798 Title: whoopsie spamming syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1264798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1221356] Re: hd-media installer rejects official raring ISO
Dmitrijs-- it's not as simple as you make it out to be. dding an image over the USB stick requires a stick dedicated to the install, since it will overwrite whatever filesystem was there before. The hd-media installer on the other hand lets you just add/remove ISO files to the existing filesystem at will, without overwriting anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221356 Title: hd-media installer rejects official raring ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/installation-guide/+bug/1221356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1221356] Re: hd-media installer rejects official raring ISO
Oh, we all agree that it doesn't work. :) I may have misread your comment, but it sounded to me like you were saying the dd method is just as good, which as I see it would just not be correct. Even if we (reasonably) conclude that one of the methods isn't worth supporting because of simple lack of interest, I think it'd be worth having the drawbacks on the record -- you never know when someone might show up willing and able to work on them. BTW, it never occurred to me to try the server ISO. I guess it may very well still work! I will give it a shot and report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221356 Title: hd-media installer rejects official raring ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/installation-guide/+bug/1221356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221356] Re: hd-media installer rejects official raring ISO
So what is the right way to install Ubuntu from a USB stick going forward? Or is only burning it to a disc supported now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221356 Title: hd-media installer rejects official raring ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/installation-guide/+bug/1221356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221356] Re: hd-media installer rejects official raring ISO
Nevermind, I see the GUI creator tool now. FWIW, this way had a nice advantage -- instead of overwriting the stick each time, you could have as many ISOs and installers as you wanted, all on the existing vfat filesystem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221356 Title: hd-media installer rejects official raring ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/installation-guide/+bug/1221356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221356] Re: hd-media installer rejects official raring ISO
Thanks. If there is anything else I can do, let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221356 Title: hd-media installer rejects official raring ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdrom-retriever/+bug/1221356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221356] Re: hd-media installer rejects official raring ISO
Well, I just discovered that the debian wheezy iso has those main /debian-installer files, so I bet their installer would work. I'll try it. This must have something to do with the old alternate install CD, no? I bet they used to have these files as well, and were needed to work with the hd-media installer. I could try with the 12.04 alternate iso. I guess either the desktop isos would need some more files to work with this method, or Ubuntu would need its own version of the hd-media initrd that could actually use the Ubiquity installer? That'd be pretty awesome. OTOH it could also just be removed from the install guide. At the end of the day, the netboot image works fine to boot from USB and install saucy. Personally I think it's pretty convenient to have the ISO there as well, but it doesn't look like anyone but me is using this method if it's been broken for this long. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221356 Title: hd-media installer rejects official raring ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdrom-retriever/+bug/1221356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221356] Re: hd-media installer rejects official raring ISO
Yep, the 12.04 alternate iso has these files: dists/precise% ls -lR main/debian-installer main/debian-installer: total 2 dr-xr-xr-x 1 root root 2048 Aug 20 18:46 binary-amd64 main/debian-installer/binary-amd64: total 47 -r--r--r-- 1 root root 47446 Aug 20 18:46 Packages.gz dists/precise% fgrep -c debian-installer Release 12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221356 Title: hd-media installer rejects official raring ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdrom-retriever/+bug/1221356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221356] Re: hd-media installer rejects official raring ISO
I just tried this with saucy beta1 (gnome edition, as the unity one isn't available yet), with the same result: Sep 5 22:40:11 iso-scan: ISOS_FOUND='[sdf1] /isos/ubuntu-gnome-13.10-beta1-desktop-amd64.iso (saucy - 13. 10)' Sep 5 22:40:11 iso-scan: Selected ISO: /isos/ubuntu-gnome-13.10-beta1-desktop-amd64.iso on /dev/sdf1 Sep 5 22:40:11 kernel: [ 13.982452] ISO 9660 Extensions: Microsoft Joliet Level 3 Sep 5 22:40:11 kernel: [ 13.984637] ISO 9660 Extensions: RRIP_1991A Sep 5 22:40:11 iso-scan: Detected ISO with 'saucy' (saucy) distribution Sep 5 22:40:11 iso-scan: Detected ISO with distribution 'saucy' (saucy) Sep 5 22:40:11 anna-install: Queueing udeb apt-mirror-setup for later installation Sep 5 22:40:11 anna-install: Queueing udeb apt-cdrom-setup for later installation Sep 5 22:40:11 anna-install: Queueing udeb saucy-support for later installation Sep 5 22:40:11 main-menu[298]: (process:1493): libkmod: kmod_lookup_alias_from_builtin_file: could not op en builtin file '/lib/modules/3.11.0-4-generic/modules.builtin.bin' Sep 5 22:40:11 main-menu[298]: (process:1493): [sdf1] isos/ubuntu-gnome-13.10-beta1-desktop-amd64.iso (saucy - 13.10) Sep 5 22:40:11 main-menu[298]: DEBUG: resolver (libc6-udeb): package doesn't exist (ignored) Sep 5 22:40:11 main-menu[298]: INFO: Menu item 'load-iso' selected Sep 5 22:40:34 cdrom-retriever: warning: Unable to find main/debian-installer/binary-amd64/Packages in /cdrom/dists/saucy/Release. Sep 5 22:40:34 cdrom-retriever: warning: Unable to find main/debian-installer/binary-amd64/Packages.gz in /cdrom/dists/saucy/Release. Sep 5 22:40:34 cdrom-retriever: warning: Unable to find restricted/debian-installer/binary-amd64/Packages in /cdrom/dists/saucy/Release. Sep 5 22:40:34 cdrom-retriever: warning: Unable to find restricted/debian-installer/binary-amd64/Packages.gz in /cdrom/dists/saucy/Release. Sep 5 22:40:34 cdrom-retriever: warning: Unable to find universe/debian-installer/binary-amd64/Packages in /cdrom/dists/saucy/Release. Sep 5 22:40:34 cdrom-retriever: warning: Unable to find universe/debian-installer/binary-amd64/Packages.gz in /cdrom/dists/saucy/Release. Sep 5 22:40:34 cdrom-retriever: warning: Unable to find multiverse/debian-installer/binary-amd64/Packages in /cdrom/dists/saucy/Release. Sep 5 22:40:34 cdrom-retriever: warning: Unable to find multiverse/debian-installer/binary-amd64/Packages.gz in /cdrom/dists/saucy/Release. Sep 5 22:40:34 anna[3006]: WARNING **: bad d-i Packages file Curiously, the saucy installer preferred the 13.04 iso over the 13.10 one when it could find both. In order to get it to even try the 13.10 iso, I had to rename the 13.04 one so it wouldn't be found, otherwise: Sep 5 22:16:57 iso-scan: ISOS_FOUND='[sdf1] /isos/ubuntu-13.04-desktop-amd64.iso (raring - 13.04), [sdf1] /isos/ubuntu-gnome-13.10-beta1-desktop-amd64.iso (saucy - 13.10)' Sep 5 22:16:57 iso-scan: Selected ISO: /isos/ubuntu-13.04-desktop-amd64.iso on /dev/sdf1 Sep 5 22:16:57 kernel: [ 34.274321] ISO 9660 Extensions: Microsoft Joliet Level 3 Sep 5 22:16:57 kernel: [ 34.276189] ISO 9660 Extensions: RRIP_1991A Sep 5 22:16:57 iso-scan: Detected ISO with 'raring' (raring) distribution Sep 5 22:16:57 iso-scan: Detected ISO with distribution 'raring' (raring) Sep 5 22:16:57 anna-install: Installing apt-mirror-setup Sep 5 22:16:57 anna[4607]: ERROR **: can't find packages file Sep 5 22:16:57 anna-install: Installing apt-cdrom-setup Sep 5 22:16:57 anna[4612]: ERROR **: can't find packages file Sep 5 22:16:57 anna-install: Installing raring-support Sep 5 22:16:57 anna[4617]: ERROR **: can't find packages file Sep 5 22:16:57 main-menu[299]: (process:3109): libkmod: kmod_lookup_alias_from_builtin_file: could not open builtin file '/lib/modules/3.11.0-4-generic/modules.builtin.bin' Sep 5 22:16:57 main-menu[299]: (process:3109): [sdf1] isos/ubuntu-13.04-desktop-amd64.iso (raring - 13.04) Sep 5 22:16:57 main-menu[299]: DEBUG: resolver (libc6-udeb): package doesn't exist (ignored) Sep 5 22:16:57 main-menu[299]: INFO: Menu item 'load-iso' selected Sep 5 22:16:57 cdrom-retriever: warning: Unable to find main/debian-installer/binary-amd64/Packages in /cdrom/dists/raring/Release. Sep 5 22:16:57 cdrom-retriever: warning: Unable to find main/debian-installer/binary-amd64/Packages.gz in /cdrom/dists/raring/Release. Sep 5 22:16:57 cdrom-retriever: warning: Unable to find restricted/debian-installer/binary-amd64/Packages in /cdrom/dists/raring/Release. Sep 5 22:16:57 cdrom-retriever: warning: Unable to find restricted/debian-installer/binary-amd64/Packages.gz in /cdrom/dists/raring/Release. Sep 5 22:17:12 anna[4628]: WARNING **: bad d-i Packages file Sep 5 22:17:12 main-menu[299]: INFO: Menu item 'load-iso' succeeded but requested to be left unconfigured. Just as a sanity check, I am once again including the sha1sums of the files I used. They match the published ones: 03af7edce38f39d25664eb89939660c6b73be633
[Bug 1084378] Re: [Feature] RDRAND enabling for rngd
Hello. Sorry to be the bearer of bad news, but this implementation is broken in a subtle but important way: When adding the data returned from rdrand to the system entropy pool, using the RNDADDENTROPY ioctl on /dev/random, it sets the entropy count equal to the buffer size. In other words, claiming that its data is 100% entropy. This is clearly wrong, as the rdrand instruction only gives access to a deterministic pseudo-random number generator. It's seeded by a built-in hardware source of true entropy, but the rdrand instruction doesn't give access to the output of the entropy source, only to the output of PRNG. The PRNG is reseeded often from this entropy source, so the output contains plenty of entropy, but nowhere near 100% (or even 1%). Intel states that you are guaranteed a reseed if you invoke the 64-bit rdrand instruction more than 1022 times (http://software.intel.com/en- us/articles/intel-digital-random-number-generator-drng-software- implementation-guide). A seed value is 256 bits. So in the worst case, we are providing 256 bits of entropy per almost 8KB of rdrand output. The problem is, when we pass it to the kernel, we claim that we provided 8KB of entropy: (from rngd_linux.c): entropy.ent_count = size * 8; entropy.size = size; The solution would be simple: per each ioctl(), make sure we've called rdrand64 more than 1022 times, and set the ent_count to 256. This can actually be done using command line options in the official (git://git.kernel.org/pub/scm/utils/kernel/rng-tools/rng-tools.git) rng- tools, but not the version in this Ubuntu package. They have a command line option -H that lets you specify the entropy per bit as a floating point, which we are missing. In conjunction with the random-step option -s, the correct behavior can be coaxed out of it by using -H 0.0039062500 -s 8192. Pretty klugy, though. I also found GPL code (I don't know the author) at https://github.com/bjencks/rngd-rdrand which cleanly and correctly does the right thing. It only supports rgrand, no other sources, so the whole thing is about 100 lines of C. It isn't productionized (doesn't fork into the background, doesn't have an init.d script, etc.) but I'm using it on my system almost as-is, and it is still fast enough to generate 2048-bit GPG key pairs nearly instantaneously on my system. The only change I made was to bump the number of rdrands per ioctl to 1024 from 1022, as the Intel docs linked above say *more* than 1022, not just 1022. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1084378 Title: [Feature] RDRAND enabling for rngd To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1084378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221356] [NEW] hd-media installer rejects official raring ISO
Public bug reported: Following the Ubuntu 13.04 Installation Guide's USB install instructions for amd64 at https://help.ubuntu.com/13.04/installation- guide/amd64/ch04s03.html#usb-copy-flexible doesn't work, it seems. I guess not many people are using the hd-media + ISO install method? The ISO is located and mounted successfully, then rejected due to missing items in the Packages file. What I did: 1) Downloaded vmlinuz and initrd.gz to a USB drive from http://archive.ubuntu.com/ubuntu/dists/raring/main/installer-amd64/current/images/hd-media/ 2) Set up syslinux to boot those two 3) Downloaded to the same flash drive ubuntu-13.04-desktop-amd64.iso 4) Booted from the flash drive. After the ISO is located and mounted, the installer errors out and is unable to proceed. The log says: Sep 2 17:24:55 iso-scan: ISOS_FOUND='[sdf1] /isos/ubuntu-13.04-desktop-amd64.iso (raring - 13.04)' Sep 2 17:24:55 iso-scan: Selected ISO: /isos/ubuntu-13.04-desktop-amd64.iso on /dev/sdf1 Sep 2 17:24:55 kernel: [ 50.033763] ISO 9660 Extensions: Microsoft Joliet Level 3 Sep 2 17:24:55 kernel: [ 50.036768] ISO 9660 Extensions: RRIP_1991A Sep 2 17:24:55 iso-scan: Detected ISO with 'raring' (raring) distribution Sep 2 17:24:55 iso-scan: Detected ISO with distribution 'raring' (raring) Sep 2 17:24:55 anna-install: Queueing udeb apt-mirror-setup for later installation Sep 2 17:24:55 anna-install: Queueing udeb apt-cdrom-setup for later installation Sep 2 17:24:55 anna-install: Queueing udeb raring-support for later installation Sep 2 17:24:55 main-menu[423]: (process:1616): libkmod: kmod_lookup_alias_from_builtin_file: could not open builtin file '/lib/modules/3.8.0-19-generic/modules.builtin.bin' Sep 2 17:24:55 main-menu[423]: (process:1616): [sdf1] isos/ubuntu-13.04-desktop-amd64.iso (raring - 13.04) Sep 2 17:24:55 main-menu[423]: DEBUG: resolver (libc6-udeb): package doesn't exist (ignored) Sep 2 17:24:55 main-menu[423]: INFO: Menu item 'load-iso' selected Sep 2 17:24:55 cdrom-retriever: warning: Unable to find main/debian-installer/binary-amd64/Packages in /cdrom/dists/raring/Release. Sep 2 17:24:55 cdrom-retriever: warning: Unable to find main/debian-installer/binary-amd64/Packages.gz in /cdrom/dists/raring/Release. Sep 2 17:24:55 cdrom-retriever: warning: Unable to find restricted/debian-installer/binary-amd64/Packages in /cdrom/dists/raring/Release. Sep 2 17:24:55 cdrom-retriever: warning: Unable to find restricted/debian-installer/binary-amd64/Packages.gz in /cdrom/dists/raring/Release. Sep 2 17:25:00 anna[3819]: WARNING **: bad d-i Packages file Sep 2 17:25:00 main-menu[423]: INFO: Menu item 'load-iso' succeeded but requested to be left unconfigured. ** Affects: debian-installer (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/1221356 Title: hd-media installer rejects official raring ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1221356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221356] Re: hd-media installer rejects official raring ISO
Sorry, I think this is the right package now, yes? ** Package changed: debian-installer (Ubuntu) = anna (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221356 Title: hd-media installer rejects official raring ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anna/+bug/1221356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221356] Re: hd-media installer rejects official raring ISO
Thanks. I'm pretty sure I'm using the right files, here the local sha1sums: 3eb9f59aab6e6c8714b98cb8553f9c8ac9a5bcbd boot/ubuntu/raring/amd64/hd-media/initrd.gz 552b3d59f14b0ec9787af84e4f9527bd1966d51a boot/ubuntu/raring/amd64/hd-media/vmlinuz ffed440f1dc1b43d9c170bd21e5ff669a59447f8 isos/ubuntu-13.04-desktop-amd64.iso -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221356 Title: hd-media installer rejects official raring ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdrom-retriever/+bug/1221356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804028] [NEW] No keyboard shortcuts to change Mode?
Public bug reported: I realize this isn't an Ubuntu issue. Please let me know if it is not appropriate to file upstream bugs here. Basically: using the keyboard, the fastest way to switch between Advanced, Programming and Financial modes seems to be Alt+M followed A, F or P. It would be nice to be able to do it in one step rather than two. For instance, Alt+B, Alt+A, Alt+F and Alt+P don't appear to be used for anything and so one idea could be to bind those to the four modes. The similar calculator utility shipped with Windows lets you use function keys to switch. Personally I think the Alt-key approach is more Ubuntu- like but I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gcalctool 6.0.1~git20110421-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Thu Jun 30 13:44:37 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: gcalctool UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gcalctool (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804028 Title: No keyboard shortcuts to change Mode? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/804028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804028] Re: No keyboard shortcuts to change Mode?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804028 Title: No keyboard shortcuts to change Mode? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/804028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 801765] [NEW] Launcher interferes with full-screen apps, shouldn't it hide instead?
Public bug reported: The basic problem is that the launcher doesn't auto-hide itself, the way it does for maximized apps, for apps such as gnome-terminal and firefox in full-screen mode. You can see this easily by creating a gnome-terminal profile with a (semi-)transparent background and pressing F11 to enter full screen mode. You'll see the launcher behind the terminal window. This may not be a problem in itself, however, any popup window will cause the launcher to return to the foreground as well. Once this happens, I can't find any way to get it back behind the full- screen window, other than to switch from full-screen to windowed mode, in the app, and then back again. Even closing the popup window does not return the full-screen window to the foreground. This can be easily reproduced. One way is to start with a full-screen gnome-terminal, and run any program which creates a window (such as xman). Another is to start with a full-screen firefox and bring up any popup window such as the bookmarks (Ctrl+Shift+O). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.14-0ubuntu1~natty1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,resize,mousepoll,regex,vpswitch,grid,animation,unitymtgrabhandles,shift,move,session,workarounds,wall,wobbly,expo,ezoom,staticswitcher,fade,scale,unityshell] Date: Fri Jun 24 16:44:41 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/801765 Title: Launcher interferes with full-screen apps, shouldn't it hide instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/801765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 801765] Re: Launcher interferes with full-screen apps, shouldn't it hide instead?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/801765 Title: Launcher interferes with full-screen apps, shouldn't it hide instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/801765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537499] Re: Conky hides itself behind nautilus desktop
Sorry for the status change, it was a misclick. A little too sensitive for me I guess ;) I found this bug because I'm having the issue, but the 'override' setting seems to work, transparency and all. The default configuration sets it to 'desktop.' Shouldn't it be changed to 'override' instead? The default setting makes it unusable on the default Ubuntu desktop. ** Changed in: conky (Ubuntu) Status: Invalid = Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/537499 Title: Conky hides itself behind nautilus desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/537499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537499] Re: Conky hides itself behind nautilus desktop
One more thing: I had to add 'own_window_hints below' to get it to work with Unity. How about the following changes to the default config (/etc/conky/conky.conf) as a starting point for a config that works okay out of the box on Natty? 1) Change alignment to bottom_right from top_left so we aren't hidden by the panel, launcher or desktop icons. 2) Change own_window_type to override from desktop, because the latter option only shows conky until the desktop is clicked. Also add 'own_window_hints below' -- without it, conky is drawn on top of all windows. (This doesn't happen in classic desktop, by the way.) 3) Maybe also enable transparency by default? It looks nicer, blending into the desktop. This one could be a matter of opinion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/537499 Title: Conky hides itself behind nautilus desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/537499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792201] [NEW] launcher leaves focus nowhere after Alt+F1, Esc
Public bug reported: Binary package hint: unity After using Alt+F1 to navigate the launcher with the keyboard, then pressing Esc to cancel this mode, the focus is left nowhere. The top panel is blank, and does not show any menus when rolled over. Keyboard input appears to go nowhere. It seems reasonable to expect focus to return to where it last was, before Alt+F1 was pressed. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.12-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] Date: Fri Jun 3 01:48:32 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792201 Title: launcher leaves focus nowhere after Alt+F1, Esc -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792201] Re: launcher leaves focus nowhere after Alt+F1, Esc
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792201 Title: launcher leaves focus nowhere after Alt+F1, Esc -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395425] Re: Installer silently crashed at the end. Not obvious - installed system works.
I've just reproduced yet again, with the broken drive removed. There are two good drives, and I've used 'Use entire disk' on sda. It looks like this is a duplicate of #260001 (ubiquity crashed with InstallStepError in configure_bootloader() ). However, unlike that bug, I'm using the 'Use entire disk' option. ** Attachment added: /var/log/installer/debug http://launchpadlibrarian.net/28716288/debug -- Installer silently crashed at the end. Not obvious - installed system works. https://bugs.launchpad.net/bugs/395425 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 395425] Re: Installer silently crashed at the end. Not obvious - installed system works.
I should also note that the crash notification appeared at least a minute into the live desktop session ... -- Installer silently crashed at the end. Not obvious - installed system works. https://bugs.launchpad.net/bugs/395425 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 395425] Re: Installer silently crashed at the end. Not obvious - installed system works.
ubu...@ubuntu:/var/log/installer$ sudo fdisk -l Disk /dev/sda: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00047255 Device Boot Start End Blocks Id System /dev/sda1 * 1 88241 708795801 83 Linux /dev/sda2 88242 91201237762005 Extended /dev/sda5 88242 9120123776168+ 82 Linux swap / Solaris Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0003af3d Device Boot Start End Blocks Id System /dev/sdb1 * 1 120858 970791853+ 83 Linux /dev/sdb2 120859 121601 5968147+ 5 Extended /dev/sdb5 120859 121601 5968116 82 Linux swap / Solaris -- Installer silently crashed at the end. Not obvious - installed system works. https://bugs.launchpad.net/bugs/395425 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 395425] [NEW] Installer silently crashed at the end. Not obvious - installed system works.
Public bug reported: Binary package hint: ubiquity At the end of the installation, I am taken to the live desktop. This strikes me as weird later, but now I simply reboot into a fully working new grub and karmic partition. Much later, I notice that ubiquity, casper, gparted and other packages that should have been removed at the end are on the system. Then, I discover that /var/log/installer doesn't exist. I've just reproduced this for the third time. I'm no longer certain there's a bug, because of two things I missed the first two times. Nonetheless, I decided it was worth entering, as I didn't realize there was a crash, even the second time! Only when I asked why the installer would exit to the live desktop instead of rebooting did it become clear what happened here. The new developments are: - Physical errors on a hard drive. These could have been there the entire time, and somehow caused the crash (the drive has been unused for a while and the graphical installer doesn't mention the errors -- I only noticed because I looked at the console this time). Is it worth doing it again after I replace that drive? - The crash notification. The first two times, I probably rebooted manually before it appeared. This time, I already had a terminal and ubuntu-bug ubiquity open before it appeared. The floating notification only says that some app has crashed (clicking it tells me that it was ubiquity). Is this the only intended notification that the installer crashed? This is the karmic alpha 2 amd64 desktop live installer, with Install Ubuntu rather than Try Ubuntu chosen at start all three times. I've tried reproducing this in VirtualBox on the same system and failed (the installer finished as it should). ProblemType: Bug Architecture: amd64 Date: Sat Jul 4 05:10:36 2009 DistroRelease: Ubuntu 9.10 LiveMediaBuild: Ubuntu 9.10 Karmic Koala - Alpha amd64 (20090610.1) Package: ubiquity 1.13.3 [modified: lib/partman/automatically_partition/question] ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.30-8.9-generic SourcePackage: ubiquity Uname: Linux 2.6.30-8-generic x86_64 ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Installer silently crashed at the end. Not obvious - installed system works. https://bugs.launchpad.net/bugs/395425 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 395425] Re: Installer silently crashed at the end. Not obvious - installed system works.
** Attachment added: Casper.gz http://launchpadlibrarian.net/28679562/Casper.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/28679563/Dependencies.txt ** Attachment added: UbiquityDebug.gz http://launchpadlibrarian.net/28679564/UbiquityDebug.gz ** Attachment added: UbiquityDm.gz http://launchpadlibrarian.net/28679565/UbiquityDm.gz ** Attachment added: UbiquityPartman.gz http://launchpadlibrarian.net/28679566/UbiquityPartman.gz ** Attachment added: UbiquitySyslog.gz http://launchpadlibrarian.net/28679567/UbiquitySyslog.gz -- Installer silently crashed at the end. Not obvious - installed system works. https://bugs.launchpad.net/bugs/395425 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 388909] Re: [karmic-alpha-2] gparted is accidentally installed by ubiquity
Hi, After a fresh install of Karmic Alpha 2, I've noticed a bunch of packages 'left behind' by the installer. These packages were *not* present on a second machine, which is running karmic but was upgraded twice from an intrepid install. Looking at /var/log/apt on both machines, it seems that intrepid's installer removed all of these packages, but the karmic one did not. On the intrepid-jaunty-karmic upgraded box, the log began with the removal of these packages (2009-04-01 was the installation date): -- Log ended: 2008-10-29 23:17:10 Log started: 2009-04-01 04:37:31 Log ended: 2009-04-01 04:37:31 Log started: 2009-04-01 04:40:44 Log ended: 2009-04-01 04:40:44 Log started: 2009-04-01 04:41:25 (Reading database ... 102341 files and directories currently installed.) Removing lupin-casper ... Removing casper ... Purging configuration files for casper ... Removing gparted ... Purging configuration files for gparted ... Removing ubiquity ... Purging configuration files for ubiquity ... Removing ubiquity-frontend-gtk ... -- By contrast, such a step is missing from the log on the freshly installed karmic system, and all of the above and more are installed on it. This seems clearly wrong, in particular as regards Ubiquity, whose own package description states: Installing this package on a normal system is unlikely to be useful. -- [karmic-alpha-2] gparted is accidentally installed by ubiquity https://bugs.launchpad.net/bugs/388909 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 375264] Re: [i965] GM965/GL960: video and compiz issues after jaunty upgrade
I am happy to report that almost everything works great after enabling UXA. The performance problems are gone, and no stability issues or memory leaks have surfaced. Suspend and hibernation work fine. Specifically, I added this single line to xorg.conf: Option AccelMethod UXA Driver version: ii xserver-xorg-video-intel 2:2.6.3-0ubuntu9 Also immediately noticeable is that the CPU usage of the Xorg process is dramatically reduced; even during playback of a 480p movie from Hulu, in full screen, it's around 10% or less, as opposed to 50-60% (and unwatchable results). Flash performance, of course, won't be mentioned in a family forum. The Reflection Compiz plugin is still broken; it will hang X shortly after being enabled, just as without UXA. At this point, this is the only issue I can detect with this configuration. Everything else seems to be working flawlessly so far. The Reflection hangs did not occur on the same machine running interpid, nor do they on a completely different system running jaunty today. That's all .. thanks, and let me know if I can be of any help. -- [i965] GM965/GL960: video and compiz issues after jaunty upgrade https://bugs.launchpad.net/bugs/375264 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 375264] Re: GM965/GL960: video and compiz issues after jaunty upgrade
Update: *significant* improvement after enabling UXA accel mode. I can now watch most Flash video in full screen; 3D Compiz plugins Rotate Cube and Shuffle Switcher work perfectly. I've kept UXA enabled and have not noticed and issues, with stability or otherwise. I'll continue to run it and report back. For completeness' sake: I tried the greedy migration heuristic in EXA mode first, and saw a marginal, barely noticeable performance improvement. I'll retest the hangs with other Compiz plugins once I can get into an environment where I can log into the machine remotely. -- GM965/GL960: video and compiz issues after jaunty upgrade https://bugs.launchpad.net/bugs/375264 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 375264] [NEW] GM965/GL960: video and compiz issues after jaunty upgrade
Public bug reported: Binary package hint: xserver-xorg-video-intel Like others, I began having issues with Intel graphics after upgrading intrepid to jaunty. I happen to be lucky in that mine are not severe compared to others. If I can in any way help speed the fixes along, by testing new code or whatever, great. I removed my card from the Compiz blacklist and have been using this Acer Aspire 5920 laptop constantly since upgrading two weeks ago. Since then, I have observed only the following issues: - Flash video is choppy and unplayable. This is the most serious issue. By comparison, a 700MB RIFF (little-endian) data, AVI, 720 x 304, 25.00 fps, video: XviD file plays fine in totem, including full screen. Do I need to compare with a better quality video? - Reflection Compiz plugin hangs X shortly into the session. No hangs have recurred since I disabled this plugin. - Rotate Cube and Shift Switcher Compiz plugins perform poorly, although still would have been impressive a few years back. 2D plugins like wobbly windows, transparency, animations appear to work fine. That's all. I hope the ubuntu-bug tool is attaching the right info, and I'll be glad to provide any more if it could help. Thanks, and have a good day! ProblemType: Bug Architecture: i386 Dependencies: DistroRelease: Ubuntu 9.04 Package: xserver-xorg-video-intel None ProcEnviron: LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersion: Linux version 2.6.28-11-generic (bui...@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 SourcePackage: xserver-xorg-video-intel Uname: Linux 2.6.28-11-generic i686 UnreportableReason: This is not a genuine Ubuntu package ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- GM965/GL960: video and compiz issues after jaunty upgrade https://bugs.launchpad.net/bugs/375264 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 375264] Re: GM965/GL960: video and compiz issues after jaunty upgrade
** Attachment added: LsHal.txt http://launchpadlibrarian.net/26620449/LsHal.txt ** Attachment added: LsMod.txt http://launchpadlibrarian.net/26620450/LsMod.txt ** Attachment added: LsPci.txt http://launchpadlibrarian.net/26620451/LsPci.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/26620452/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/26620453/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/26620454/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/26620455/Xrandr.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/26620456/glxinfo.txt ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/26620457/monitors.xml.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/26620458/setxkbmap.txt ** Attachment added: system.txt http://launchpadlibrarian.net/26620459/system.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/26620460/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/26620461/xkbcomp.txt -- GM965/GL960: video and compiz issues after jaunty upgrade https://bugs.launchpad.net/bugs/375264 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 375264] Re: GM965/GL960: video and compiz issues after jaunty upgrade
Oh, I had just tried to roll this package to the 2.4.1 version, as per this: https://wiki.ubuntu.com/ReinhardTartler/X/RevertingIntelDriverTo2.4 Interestingly, it didn't seem to have any perceptible effect. I'll move back to the jaunty 2.6.3 package now. I'd just realized this would affect any package info that ubuntu-bug attached. Sorry about that. To clarify, I have been running jaunty's 2.6.3 until an hour or two ago. -- GM965/GL960: video and compiz issues after jaunty upgrade https://bugs.launchpad.net/bugs/375264 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
