[Bug 1179041] [NEW] Btrfs partition too small, upgrade from Quantal to Raring failed
Public bug reported: First off, I have fixed the problem myself and am using Raring Ringtail to write this report. I apologize if the information collected by Apport-bug is showing incorrect version information for ubuntu-release- upgrader-core. While using Quantal Quetzal installed onto a Btrfs partition, I executed do-release-update in the command line. The process failed about half way through, after which point my system became unusable. I investigated and found that the do-release-update program correctly identified Btrfs and created a subvolume for storing the updated OS. I assume the reason for doing this is to allow for an easy roll-back in the event of a failed update. Unfortunately, the Btrfs partition was small (about 24GB) and the update process (downloading so many files) quickly filled up the entire file system. This set the Btrfs file system into an unstable state where executing even rm /some-empty-file would report an error message no space left on device. I was able to roll-back the system, but I was NOT able to update my system at all using do-release-upgrade. I had to backup Quantal and reformat my system partition as Ext4, then restore Quantal from the backup. After that, running do-release-upgrade with a Quantal system installed on an Ext4 partition completed successfully, and I am running Raring now. It seems your do-release-upgrade software is not prepared to handle situations in which Btrfs is running short on space, which is definitely a bug. Do-release-upgrade should not create a separate subvolume if the available space on the file system is not enough to perform an update. A good heuristic might be to have space available for triple the space used by all installed packages. If there is not enough space, the Btrfs volume should be treated the same as it would for an Ext4 volume and update files in-place, rather than in a subvolume. Furthermore, the do-release-upgrade process ought to automatically roll-back a failed update, rather than leave the file system in an unstable, useless state. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.10 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CrashDB: ubuntu Date: Sun May 12 03:49:55 2013 MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to raring on 2013-04-30 (11 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: btrfs dist-upgrade do-release-upgrade quantal raring ** Description changed: First off, I have fixed the problem myself and am using Raring Ringtail to write this report. I apologize if the information collected by Apport-bug is showing incorrect version information for ubuntu-release- upgrader-core. While using Quantal Quetzal installed onto a Btrfs partition, I executed do-release-update in the command line. The process failed about half way through, after which point my system became unusable. I investigated and found that the do-release-update program correctly identified Btrfs and created a subvolume for storing the updated OS. I assume the reason for doing this is to allow for an easy roll-back in the event of a failed update. Unfortunately, the Btrfs partition was small (about 24GB) and the update process (downloading so many files) quickly filled up the entire file system. This set the Btrfs file system into an unstable state where executing even rm /some-empty-file would report an error message no space left on device. I was able to roll-back the system, but I was NOT able to update my system at all using do-release-upgrade. I had to backup Quantal and reformat my system partition as Ext4, then restore Quantal from the - backup. After that, running do-release-upgrade on an system installed - on an Ext4 partition completed successfully, and I am running Raring - now. + backup. After that, running do-release-upgrade with a Quantal system + installed on an Ext4 partition completed successfully, and I am running + Raring now. It seems your do-release-upgrade software is not prepared to handle situations in which Btrfs is running short on space, which is definitely a bug. Do-release-upgrade should not create a separate subvolume if the available space on the file system is not enough to perform an update. A good heuristic might be to have space available for triple the space used by all installed packages. If there is not enough space, the Btrfs volume should be treated the same as it would for an Ext4 volume and update files in-place, rather than in a subvolume. Furthermore, the do-release-upgrade process ought to automatically roll-back a failed update, rather than leave the file system in an unstable, useless state. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package:
[Bug 989847] [NEW] Problem between pulseaudio and ALSA, suddenly no sound
Public bug reported: After updating to 12.04, my sound was working fine. At some point within the past 24 hours, it very suddenly stopped working. I did execute an apt-get upgrade once, so this may have been the cause. I have not made any modifications to pulesaudio or ALSA's configuration, so Ubuntu's default configuration is set. I have been searching other bug reports with similar symptoms, but most of them are from back in 2008, so I assume this is a new issue. My sound card has only headphone output, so I must use headphones. % sudo lshw -C sound [sudo] password for ramin: *-multimedia description: Audio device product: 82801JD/DO (ICH10 Family) HD Audio Controller vendor: Intel Corporation physical id: 1b bus info: pci@:00:1b.0 version: 02 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:292 memory:fe6dc000-fe6d Symptoms: Pulseaudio works fine, I can use my laptop as a sink and hear sound played on my desktop (my desktop is the one with the problem). Alsamixer selects the correct sound card and I can unmute and turn-up the volume and PCM. When I fiddle with the volume in alsamixer, or in the Gnome Control Center, I can hear the usual white noise in my headphones become lounder and softer as I turn the volume up and down, so the alsamixer is certainly interfaced with the sound card. However, when I try to play a sound, either with aplay, paplay, or mplayer, nothing works. Although I was able to watch YouTube videos earlier today without any problems, I cannot remember if this was before or after I executed a software update. But when I sink audio output into my laptop, all three of these applications work correctly. One thing is curious: alsamixer has a headphone volume control right next to the master volume control, and the headphone volume control is unmuted, but I am unable to turn the volume up or down on this controller, it is fixed at a 0 value. I thought perhaps pulseaudio was trying to output to a non-existent port on the soundcard (like speakers instead of headphones), so I tried enabling simultaneous output, but this did not solve the problem. I tried executing alsactl restore and alsactl init but this did not solve the problem. I believe the problem may be with Pulseaudio, and how it has configured my sound card as a sink, but I am not sure. The sound card obviously is working (it was working earlier today), and so is Pulseaudio (it can sink sound into a networked sound card), but they don't seem to be connected together. Another possibility is that the sound card has not detected that my headphones are plugged in and has muted the output (although I can still hear the usual white noise when turning up the volume), but I don't know how to check for this with pacmd, and alsamixer is indicating that everything is UNmuted (except headphone output is fixed at 0 volume). PLEASE HELP!!! Here is the output of pacmd dump with my headphones plugged in: ### Configuration dump generated at Sat Apr 28 00:20:15 2012 load-module module-device-restore load-module module-stream-restore load-module module-card-restore load-module module-augment-properties load-module module-alsa-card device_id=0 name=pci-_00_1b.0 card_name=alsa_card.pci-_00_1b.0 namereg_fail=false tsched=yes ignore_dB=no deferred_volume=yes card_properties=module-udev-detect.discovered=1 load-module module-udev-detect load-module module-bluetooth-discover load-module module-esound-protocol-unix load-module module-native-protocol-unix load-module module-zeroconf-discover load-module module-gconf load-module module-default-device-restore load-module module-rescue-streams load-module module-always-sink load-module module-intended-roles load-module module-suspend-on-idle load-module module-console-kit load-module module-position-event-sounds load-module module-filter-heuristics load-module module-filter-apply load-module module-switch-on-port-available load-module module-cli-protocol-unix set-sink-volume alsa_output.pci-_00_1b.0.analog-stereo 0x7289 set-sink-mute alsa_output.pci-_00_1b.0.analog-stereo no suspend-sink alsa_output.pci-_00_1b.0.analog-stereo yes set-source-volume alsa_input.pci-_00_1b.0.analog-stereo 0x361a set-source-mute alsa_input.pci-_00_1b.0.analog-stereo no suspend-source alsa_input.pci-_00_1b.0.analog-stereo yes set-source-volume alsa_output.pci-_00_1b.0.analog-stereo.monitor 0x1 set-source-mute alsa_output.pci-_00_1b.0.analog-stereo.monitor no suspend-source alsa_output.pci-_00_1b.0.analog-stereo.monitor yes set-card-profile alsa_card.pci-_00_1b.0 output:analog-stereo+input :analog-stereo set-default-sink alsa_output.pci-_00_1b.0.analog-stereo set-default-source alsa_input.pci-_00_1b.0.analog-stereo ### EOF ProblemType: Bug DistroRelease: Ubuntu 12.04 Package:
[Bug 989847] Re: Problem between pulseaudio and ALSA, suddenly no sound
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/989847 Title: Problem between pulseaudio and ALSA, suddenly no sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/989847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915954] Re: Xen + Virt-Manager: Unable to connect to 'localhost:8000': Connection refused
If you have the same problem I had, that should fix it. You may want to do this command first: find /usr/lib64 -name qemu-dm And see if this output appears: /usr/lib64/xen-default/bin/qemu-dm If so, the then for /usr/lib64, it is probably the same problem. To fix it, execute this command as root: ln -s /usr/lib64/xen-default /usr/lib64/xen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915954 Title: Xen + Virt-Manager: Unable to connect to 'localhost:8000': Connection refused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/915954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915954] Re: Xen + Virt-Manager: Unable to connect to 'localhost:8000': Connection refused
I have found a workaround: In the /etc/xen/xend-config.sexp file, find and uncommont the lines: (xend-unix-server no) (xend-unix-path /var/lib/xend/xend-socket) and change the (xend-unix-server no) line to yes: (xend-unix-server yes) Then reboot. I request Ubuntu package maintainers add some kind of installation task to the libvirt or virt-manager package that automatically modifies the /etc/xen/xend-config.sexp file so long as the file has not been modified since the time it was installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915954 Title: Xen + Virt-Manager: Unable to connect to 'localhost:8000': Connection refused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/915954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915954] Re: Xen + Virt-Manager: Unable to connect to 'localhost:8000': Connection refused
Another problem I have discovered with the package installation: When I try to create a virtual machine instance, I get the error: Unable to complete install: 'POST operation failed: xend_post: error from xen daemon: (xend.err Error creating domain: device model '/usr/lib/xen/bin/qemu-dm' not found)' It appears the /usr/lib/xen symbolic link is called /usr/lib/xen/xen- default. I must manually create a symbolic link to the current version of Xen on my system. This should be done when I install virt-manager or libvirt with apt- get, that or the virt-manager and virsh programs must be configured to point to the correct location in /usr/lib. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915954 Title: Xen + Virt-Manager: Unable to connect to 'localhost:8000': Connection refused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/915954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915954] Re: Xen + Virt-Manager: Unable to connect to 'localhost:8000': Connection refused
** Summary changed: - Unable to connect to 'localhost:8000': Connection refused + Xen + Virt-Manager: Unable to connect to 'localhost:8000': Connection refused -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915954 Title: Xen + Virt-Manager: Unable to connect to 'localhost:8000': Connection refused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/915954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915954] Re: Unable to connect to 'localhost:8000': Connection refused
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915954 Title: Unable to connect to 'localhost:8000': Connection refused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/915954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915954] [NEW] Unable to connect to 'localhost:8000': Connection refused
Public bug reported:
The error message dialog contains this text:
Unable to open a connection to the Xen hypervisor/daemon.
Verify that:
- A Xen host kernel was booted
- The Xen service has been started
unable to connect to 'localhost:8000': Connection refused
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/connection.py, line 1146, in
_open_thread
self.vmm = self._try_open()
File /usr/share/virt-manager/virtManager/connection.py, line 1130, in
_try_open
flags)
File /usr/lib/python2.7/dist-packages/libvirt.py, line 102, in openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: unable to connect to 'localhost:8000': Connection refused
I have just used Aptitude to install Xen-4.1 and the Libvirt package. There are
two bugs here:
Bug #1. I must modify /etc/grub.d by hand:
mv 10_linux 20_linux
mv 20_linux_xen 10_linux_xn
update-grbu2
reboot
This should have been done by Apt-get, I had to do it by hand. Once this is
done, I can verify the hypervisor is running with the command:
xl info
Bug #2. Virt-manager does not work out of the box. I cannot use Virsh,
Virt-manager, or even Virt-install. Executing Virt-install returns this error:
ERRORunable to connect to 'localhost:8000': Connection refused
Can anyone please suggest to me a way to solve this issue?
In any case, the fact that Ubuntu's Apt-get installs a Xen/Virt-manager
configuration that does not function properly without tweaking, I
believe, is definitely a bug.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: virt-manager 0.9.0-1ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic-pae 3.0.9
Uname: Linux 3.0.0-14-generic-pae i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Fri Jan 13 20:10:40 2012
ExecutablePath: /usr/share/virt-manager/virt-manager.py
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: virt-manager
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (90 days ago)
** Affects: virt-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/915954
Title:
Unable to connect to 'localhost:8000': Connection refused
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/915954/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 877088] Re: Network proxy setting does not set apt.conf from the second time
I have the same problem. I had created my own (duplicate) bug for this problem at: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/879223 I am behind a corporate firewall using a McAfee web gateway, a content- filtering proxy server. Our DNS resolves IP addresses without any proxy settings, but HTTP, HTTPS, and FTP connections cannot be made to addresses beyond the firewall unless we connect through the proxy server. So when executing apt-get, it resolves my mirror's IP address OK, but times-out trying to download the Packages.gz file. The only way to make apt-get work correctly is to set the /etc/apt/apt.conf file, which should be done by gnome-control-center, but it doesn't. All I can do is write my own script to set /etc/apt/apt.conf to use the proxy, and execute it every time I want to run apt-get at the office. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/877088 Title: Network proxy setting does not set apt.conf from the second time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-service/+bug/877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 879207] [NEW] Alt key-press events are captured by Unity global menu, even after turning-off Show Menubar.
Public bug reported: After turning-off Show Menubar, key events with the Alt key pressed does not generate an Escape+Letter ASCII code on the TTY input stream. The Alt key-press event is still captured by the Unity global menu. To reproduce this issue: 1. Open a new gnome-terminal running Bash or Emacs. 2. Right-mouse-click the terminal window and un-check the menu option Show Menubar 3. Type a few words separated by spaces. 4. Press Ctrl-A to position the cursor at the beginning of the line. 5. Press Alt-F to move the cursor forward one word -- THIS FAILS. Instead the File menu pops-up. Work-around: You must instead press Esc and then F to generate the Escape-F ASCII code. This makes using the terminal very difficult. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Fri Oct 21 12:04:31 2011 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-10-14 (6 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric 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/879207 Title: Alt key-press events are captured by Unity global menu, even after turning-off Show Menubar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/879207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 879207] Re: Alt key-press events are captured by Unity global menu, even after turning-off Show Menubar.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/879207 Title: Alt key-press events are captured by Unity global menu, even after turning-off Show Menubar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/879207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 879223] Re: Network - Network Proxy - Apply System Wide does NOT update /etc/apt/apt.conf
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/879223 Title: Network - Network Proxy - Apply System Wide does NOT update /etc/apt/apt.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/879223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 879223] [NEW] Network - Network Proxy - Apply System Wide does NOT update /etc/apt/apt.conf
Public bug reported: When I bring my Ubuntu laptop to work, I must tell it to connect to the proxy server. To do this, I go to the Network pane, then the Network Proxy sub-pane. Under Method I select Automatic and enter the correct Configuration URL. Then I press Apply System wide. My web browser now can connect to the Internet. However, applications like Update Manager, and Ubuntu Software Center, and even apt-get in the command line fail to communicate with ANY package repository servers. Checking /etc/apt/apt.conf, I see the file is empty. To reproduce this issue: 1. With a computer that does not connect to the Internet via proxy, isolate the computer behind a firewall which forwards all Web traffic (HTTP, HTTPS, FTP) to a content-filtering proxy server. 2. In gnome-control-center, go to Network - Network Proxy, and set the method to Automatic, filling in the correct URL for the proxy configuration file. The same problem seems to occur if you configure the proxy settings manually. 3. Press the Apply system wide button. 4. Open Update Manager and press Check and/or Install Updates. FAILS -- package updates appear to begin to download, but eventually times-out and reports an error. 5. Check /etc/apt/apt.conf, it should be empty (or unchanged by gnome-control-center). Work-around: As a root user, modify /etc/apt/apt.conf by hand with content like: Acquire::http::proxy http://proxy.serv.org:8080/;; Acquire::https::proxy https://proxy.serv.org:8080/;; Acquire::ftp::proxy ftp://proxy.serv.org:8080/;; Acquire::socks::proxy socks://proxy.serv.org:8080/; ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Fri Oct 21 13:22:24 2011 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-10-14 (6 days ago) usr_lib_gnome-control-center: deja-dup 20.0-0ubuntu3 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric 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/879223 Title: Network - Network Proxy - Apply System Wide does NOT update /etc/apt/apt.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/879223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
