Bug#1058670: python3-poetry: fail with Can't instantiate abstract class IsolatedEnv with abstract methods executable, scripts_dir
Package: python3-poetry Version: 1.7.1+dfsg-1 Severity: normal Tags: upstream X-Debbugs-Cc: george.shuk...@gmail.com poetry fails to install packages (`poetry install` for an existing lock file) or to update it (`poetry update`): Can't instantiate abstract class IsolatedEnv with abstract methods executable, scripts_dir at /usr/lib/python3/dist-packages/poetry/installation/chef.py:131 in _prepare 127│ ) -> Path: 128│ from subprocess import CalledProcessError 129│ 130│ with ephemeral_environment(self._env.python) as venv: → 131│ env = IsolatedEnv(venv, self._pool) 132│ builder = ProjectBuilder.from_isolated_env( 133│ env, directory, runner=quiet_subprocess_runner 134│ ) 135│ env.install(builder.build_system_requires) According to github bug: https://github.com/python-poetry/poetry/issues/8458 it is caused by conflict (interactions?) with python3-build package. python3-build 0.10.0-1 -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/20 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-poetry depends on: ii python3 [python3-supported-min] 3.11.6-1 ii python3-build0.10.0-1 ii python3-cachecontrol 0.13.1-1 ii python3-cleo 2.1.0-2 ii python3-crashtest0.4.1-1 ii python3-dulwich 0.21.6-1+b1 ii python3-fastjsonschema 2.19.0-1 ii python3-importlib-metadata 4.12.0-1 ii python3-installer0.7.0+dfsg1-2 ii python3-keyring 24.3.0-1 ii python3-lockfile 1:0.12.2-3 ii python3-packaging23.2-1 ii python3-pexpect 4.8.0-4 ii python3-pkginfo 1.8.2-2 ii python3-platformdirs 4.1.0-1 ii python3-poetry-core 1.8.1-1 ii python3-pyproject-hooks 1.0.0-2 ii python3-requests 2.31.0+dfsg-1 ii python3-requests-toolbelt1.0.0-2 ii python3-shellingham 1.5.4-1 ii python3-tomli2.0.1-2 ii python3-tomlkit 0.12.1-1 ii python3-trove-classifiers2023.9.19-1 ii python3-virtualenv 20.25.0+ds-1 python3-poetry recommends no packages. python3-poetry suggests no packages. -- no debconf information
Bug#1055979: fwupd hangs on XPS 15 9530 with external monitor connected
Package: fwupd Version: 1.9.8-1 Severity: normal X-Debbugs-Cc: george.shuk...@gmail.com fwupd is haging (and is killed with timeout). Laptop: XPS 15 9530 with external monitor connected via USB-C -> DP. Logs: Starting fwupd.service - Firmware update daemon... FuUsbDevice failed to parse platform capability BOS descriptor: no supported platform version: did not find magic FuEngine failed to add device /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-2/drm_dp_aux2: failed to add device using on synaptics_mst: failed to enable remote control: failure writing data register: failed to write 0x5 bytes on layer:0, relative_addr:0x0 fwupd.service: start operation timed out. Terminating. fwupd.service: Failed with result 'timeout'. Failed to start fwupd.service - Firmware update daemon. strace on the hanged service shows: [pid 4203] lseek(14, 1208, SEEK_SET) = 1208 [pid 4203] write(14, "\4\0\0\0", 4)= 4 [pid 4203] lseek(14, 1202, SEEK_SET) = 1202 [pid 4203] write(14, "\244", 1)= 1 [pid 4203] lseek(14, 1202, SEEK_SET) = 1202 [pid 4203] read(14, "\0\0", 2) = 2 [pid 4203] lseek(14, 1216, SEEK_SET) = 1216 [pid 4203] write(14, "\262", 1)= 1 (in a long loop) fd 14 is /dev/drm_dp_aux5 If external monitor is disconnected, it works as expected. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/20 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fwupd depends on: ii adduser3.137 ii libarchive13 3.7.2-1 ii libc6 2.37-12 ii libcbor0.100.10.2-1.1 ii libcurl3-gnutls8.4.0-2 ii libflashrom1 1.3.0-2.1 ii libfwupd2 1.9.8-1 ii libglib2.0-0 2.78.1-4 ii libgnutls303.8.1-4+b1 ii libgudev-1.0-0 238-3 ii libgusb2 0.4.5-1.1 ii libjcat1 0.1.9-1 ii libjson-glib-1.0-0 1.8.0-2 ii liblzma5 5.4.4-0.1 ii libmbim-glib4 1.30.0-1 ii libmbim-proxy 1.30.0-1 ii libmm-glib01.22.0-1 ii libpolkit-gobject-1-0 123-3 ii libprotobuf-c1 1.4.1-1+b1 ii libqmi-glib5 1.34.0-2 ii libqmi-proxy 1.34.0-2 ii libsqlite3-0 3.44.0-1 ii libsystemd0254.5-1 ii libtss2-esys-3.0.2-0 4.0.1-3 ii libxmlb2 0.3.14-2 ii shared-mime-info 2.2-1 ii zlib1g 1:1.2.13.dfsg-3 Versions of packages fwupd recommends: ii bolt 0.9.6-1 ii dbus 1.14.10-3 ii fwupd-amd64-signed [fwupd-signed] 1:1.4+1 ii jq 1.7-1 ii python33.11.4-5+b1 pn secureboot-db ii udisks22.10.1-2 Versions of packages fwupd suggests: pn gir1.2-fwupd-2.0 -- Configuration Files: /etc/fwupd/fwupd.conf [Errno 13] Permission denied: '/etc/fwupd/fwupd.conf' -- no debconf information
Bug#1055161: linux-image-6.1.55-1-amd64: Dell R650xs hangs on reboot if ipxe.efi initialized network (tg3 driver bug)
Package: linux-image-6.1.55-1-amd64 Version: 6.1.38-4 Severity: normal Tags: patch upstream X-Debbugs-Cc: george.shuk...@gmail.com When Dell R660xs server is booting using ipxe.efi (in UEFI mode), reboots are hanging because of tg3 driver. Steps to reproduce: 1. Switch server to EFI mode 2. Enable PXE on any interfaces 3. Enable PXE as first in boot order 4. Configure external dhcp/tftp server with ipxe.efi (of any version) 5. Boot. ipxe.efi will try to get loading parameters and exit, a normal linux is loaded 6. Assure tg3 driver is loaded (rmmod tg3; modprobe tg3) 7. Reboot Expected behaivor: reboot Actual behavior: system hanging after message `ACPI: PM: Preparing to enter system sleep state S5`. I belive this problem was present present for long time, but in 6.0 there was introduced commit 2ca1c94ce0b which changed the tg3_shutdown function. - if (system_state == SYSTEM_POWER_OFF) - tg3_power_down(tp); + tg3_power_down(tp); Because of that tg3_power_down now is called even when SYSTEM_RESTART. (I confirmed that it causes hangs on older kernels during power off, but it's less of the problem, because for servers it's expected to get server working back after reboot, not so much for poweroff). (ipxe.efi is important to reproduce this bug). Any network card can be used, just a presence of tg3 driver and embedded Broadcom Inc. and subsidiaries BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller is enough to trigger it. Restoring back this behavior is solving reboot problem. I've reported it to the Dell community forum: https://www.dell.com/community/en/users/647c085ec3b1ef2541ca0c64, but it's unknown if they fix EFI network driver or not. Patch to fix hanging is attached. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-3-amd64 (SMP w/20 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Dell R650xs has embbedded network card with tg3 driver. If network was initialized by ipxe.efi in PXE/UEFI mode, server hangs during reboot. This is partial revert of upstream commit 2ca1c94ce0b. --- linux-6.1.38.orig/drivers/net/ethernet/broadcom/tg3.c +++ linux-6.1.38/drivers/net/ethernet/broadcom/tg3.c @@ -18082,7 +18082,8 @@ static void tg3_shutdown(struct pci_dev if (netif_running(dev)) dev_close(dev); - tg3_power_down(tp); + if (system_state == SYSTEM_POWER_OFF) + tg3_power_down(tp); rtnl_unlock();
Bug#1053454: anki: Trace under Gnome3/wayland if press settings
Package: anki
Version: 2.1.15+dfsg-3
Severity: normal
X-Debbugs-Cc: george.shuk...@gmail.com
Configuration: Gnome3/wayland (Intel GPU).
When run anki and press tools->settings, following trace is captured, and no
settings are displayed.
Anki 2.1.15 (442df9d6) Python 3.11.5 Qt 5.15.10 PyQt 5.15.9
Platform: Linux
Flags: frz=False ao=False sv=2
Caught exception:
File "/usr/share/anki/aqt/main.py", line 882, in onPrefs
aqt.dialogs.open("Preferences", self)
File "/usr/share/anki/aqt/__init__.py", line 82, in open
instance = creator(*args)
^^
File "/usr/share/anki/aqt/preferences.py", line 25, in __init__
self.setupCollection()
File "/usr/share/anki/aqt/preferences.py", line 80, in setupCollection
f.lrnCutoff.setValue(qc['collapseTime']/60.0)
: setValue(self, val: int): argument 1 has unexpected type
'float'
-- System Information:
Debian Release: trixie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-1-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages anki depends on:
ii libjs-jquery3.6.1+dfsg+~3.5.14-1
ii libjs-jquery-flot 4.2.1+dfsg-6
ii libjs-jquery-ui 1.13.2+dfsg-1
ii libjs-mathjax 2.7.9+dfsg-1
ii libqt5core5a5.15.10+dfsg-3
ii python3 3.11.4-5+b1
ii python3-bs4 4.12.2-2
ii python3-decorator 5.1.1-5
ii python3-distro 1.8.0-1
ii python3-distutils 3.11.5-1
ii python3-jsonschema 4.10.3-2
ii python3-markdown3.4.4-1
ii python3-pyaudio 0.2.13-1+b1
ii python3-pyqt5 5.15.9+dfsg-2
ii python3-pyqt5.qtwebchannel 5.15.9+dfsg-2
ii python3-pyqt5.qtwebengine 5.15.6-1
ii python3-requests2.31.0+dfsg-1
ii python3-send2trash 1.8.2-1
Versions of packages anki recommends:
ii python3-matplotlib 3.6.3-1+b1
Versions of packages anki suggests:
pn dvipng
pn lame
ii mpv 0.36.0-1
-- no debconf information
Bug#1052615: gnome-shell: Keyboard layout indicator does not change when switch layouts
Package: gnome-shell Version: 44.5-1 Severity: normal X-Debbugs-Cc: george.shuk...@gmail.com Steps to reproduce: 1. Configure layout switching using Gnome tweaks as 'Caps to first layout', 'Shift-caps to second layout' 2. Switch layout Expected behavior: layout indicator displays current layout (language of layout) Actual behavior: 1. Layout switches as expected 2. Layout indicator does not change Note: Selecting language via indicator changes both layout and icon, whist keyboard shortcut does not. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/20 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 ii gir1.2-accountsservice-1.0 23.13.9-4 ii gir1.2-adw-1 1.4.0-1 ii gir1.2-atk-1.0 2.50.0-1 ii gir1.2-atspi-2.0 2.50.0-1 ii gir1.2-freedesktop 1.78.1-1 ii gir1.2-gcr-3 3.41.1-3 ii gir1.2-gdesktopenums-3.0 45.0-1 ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1 ii gir1.2-gdm-1.0 45.0.1-1 ii gir1.2-geoclue-2.0 2.7.1-1 ii gir1.2-glib-2.0 1.78.1-1 ii gir1.2-gnomebg-4.0 44.0-2 ii gir1.2-gnomebluetooth-3.042.6-1 ii gir1.2-gnomedesktop-4.0 44.0-2 ii gir1.2-graphene-1.0 1.10.8-1 ii gir1.2-gstreamer-1.0 1.22.5-1 ii gir1.2-gtk-4.0 4.12.2+ds-1 ii gir1.2-gweather-4.0 4.4.0-1 ii gir1.2-ibus-1.0 1.5.29~rc1-1 ii gir1.2-mutter-12 44.5-1 ii gir1.2-nm-1.01.44.0-1 ii gir1.2-nma4-1.0 1.10.6-1 ii gir1.2-pango-1.0 1.51.0+ds-2 ii gir1.2-polkit-1.0123-1 ii gir1.2-rsvg-2.0 2.54.7+dfsg-2 ii gir1.2-soup-3.0 3.4.3-1 ii gir1.2-upowerglib-1.01.90.2-4 ii gir1.2-webkit2-4.1 2.42.0-1 ii gnome-backgrounds45.0-1 ii gnome-settings-daemon45.0-1 ii gnome-shell-common 44.5-1 ii gsettings-desktop-schemas45.0-1 ii gstreamer1.0-pipewire0.3.80-2 ii libatk-bridge2.0-0 2.50.0-1 ii libatk1.0-0 2.50.0-1 ii libc62.37-10 ii libcairo21.18.0-1 ii libecal-2.0-23.50.0-1 ii libedataserver-1.2-273.50.0-1 ii libgcr-base-3-1 3.41.1-3 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libgirepository-1.0-11.78.1-1 ii libgjs0g 1.76.2-4 ii libgles2 1.6.0-1 ii libglib2.0-0 2.78.0-2 ii libglib2.0-bin 2.78.0-2 ii libgnome-autoar-0-0 0.4.4-2 ii libgnome-desktop-4-2 44.0-2 ii libgraphene-1.0-01.10.8-1 ii libgtk-3-0 3.24.38-5 ii libgtk-4-1 4.12.2+ds-1 ii libical3 3.0.16-1+b1 ii libjson-glib-1.0-0 1.8.0-1 ii libmutter-12-0 44.5-1 ii libnm0 1.44.0-1 ii libpango-1.0-0 1.51.0+ds-2 ii libpolkit-agent-1-0 123-1 ii libpolkit-gobject-1-0123-1 ii libpulse-mainloop-glib0 16.1+dfsg1-2+b1 ii libpulse016.1+dfsg1-2+b1 ii libsecret-1-00.21.1-1 ii libsystemd0 254.4-1 ii libx11-6 2:1.8.6-1 ii libxfixes3 1:6.0.0-2 ii python3 3.11.4-5+b1 Versions of packages gnome-shell recommends: ii bolt 0.9.6-1 ii chrome-gnome-shell 42.1-4 ii
Bug#1029941: unattended-upgrades: unattended-upgrade hangs with 100% CPU usage
Package: unattended-upgrades
Version: 2.9.1+nmu3
Severity: normal
X-Debbugs-Cc: george.shuk...@gmail.com
Dear Maintainer,
I found that unattended-upgrade process consumed more than 37 hours (took me a
while to notice).
In strace there is an endless loop:
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_sid_non-free_binary-
all_Packages.zst", 0x7ffdbcd64c70, 0) = -1 ENOENT (No such file or directory)
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_sid_non-free_binary-
all_Packages.uncompressed", 0x7ffdbcd64c70, 0) = -1 ENOENT (No such file or
directory)
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_sid_non-
free_i18n_Translation-en", {st_mode=S_IFREG|0644, st_size=624211, ...}, 0) = 0
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_sid_non-
free_i18n_Translation-en", {st_mode=S_IFREG|0644, st_size=624211, ...}, 0) = 0
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_experimental_main_source_Sources",
{st_mode=S_IFREG|0644, st_size=2313105, ...}, 0) = 0
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_experimental_contrib_source_Sources",
{st_mode=S_IFREG|0644, st_size=3188, ...}, 0) = 0
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_experimental_non-
free_source_Sources", {st_mode=S_IFREG|0644, st_size=24493, ...}, 0) = 0
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_experimental_main_binary-
amd64_Packages", {st_mode=S_IFREG|0644, st_size=2503499, ...}, 0) = 0
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_experimental_main_binary-
amd64_Packages", {st_mode=S_IFREG|0644, st_size=2503499, ...}, 0) = 0
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_experimental_main_binary-i386_Packages",
{st_mode=S_IFREG|0644, st_size=2359788, ...}, 0) = 0
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_experimental_main_binary-i386_Packages",
{st_mode=S_IFREG|0644, st_size=2359788, ...}, 0) = 0
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_experimental_main_binary-
all_Packages", 0x7ffdbcd64c70, 0) = -1 ENOENT (No such file or directory)
[pid 633721] newfstatat(AT_FDCWD,
"/var/lib/apt/lists/debian.otenet.gr_debian_dists_experimental_main_binary-
all_Packages.xz", 0x7ffdbcd64c70, 0) = -1 ENOENT (No such file or directory)
There is no specific log entires in the journal (just start event) and this is
the last message in the logs:
2023-01-29 00:08:26,889 INFO Starting unattended upgrades script
2023-01-29 00:08:26,889 INFO Allowed origins are:
origin=Debian,codename=bookworm,label=Debian,
origin=Debian,codename=bookworm,label=Debian-Security,
origin=Debian,codename=bookworm-security,label=Debian-Security
2023-01-29 00:08:26,889 INFO Initial blacklist:
2023-01-29 00:08:26,889 INFO Initial whitelist (not strict):
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (500, 'oldstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages unattended-upgrades depends on:
ii debconf [debconf-2.0] 1.5.82
ii lsb-base 11.5
ii lsb-release12.0-1
ii python33.10.6-3+b1
ii python3-apt2.5.0
ii python3-dbus 1.3.2-4
ii python3-distro-info1.3
ii sysvinit-utils [lsb-base] 3.06-2
ii ucf3.0043
ii xz-utils 5.4.1-0.0
Versions of packages unattended-upgrades recommends:
ii anacron 2.3-36
ii cron [cron-daemon] 3.0pl1-156
ii systemd-sysv252.4-1
Versions of packages unattended-upgrades suggests:
pn bsd-mailx
ii needrestart3.6-3
ii nullmailer [mail-transport-agent] 1:2.2-3+b1
ii powermgmt-base 1.37
ii python3-gi 3.42.2-3
-- debconf-show failed
Bug#1025025: ImportError: cannot import name 'Application' from 'cleo'
close 1025025 I've used debian:bookworm Docker image. I rechecked it now, and problem seems to be solved: docker run --rm -ti debian:bookworm # apt update && apt install -y python3-poetry # /usr/bin/poetry config virtualenvs.create false # Thank you very much for help. On 12/14/22 19:49, Emmanuel Arias wrote: Hi George, Thanks for the report. I assume that you are in testing. Please can you try again? python-cleo was migrated to testing yesterday [0] [0] https://tracker.debian.org/news/1398131/python-cleo-100a5-3-migrated-to-testing/ Please, let me know. Cheers, Emmanuel On Fri, Dec 9, 2022 at 2:21 PM George Shuklin wrote: Unfortunately, 1.2.2+dfsg-1didn't fixed the problem: dpkg -l|grep poetr ii python3-poetry 1.2.2+dfsg-1 /usr/bin/poetry config virtualenvs.create false Traceback (most recent call last): File "/usr/bin/poetry", line 5, in from poetry.console.application import main File "/usr/lib/python3/dist-packages/poetry/console/application.py", line 13, in from cleo.events.console_events import COMMAND ModuleNotFoundError: No module named 'cleo.events'
Bug#1025025: ImportError: cannot import name 'Application' from 'cleo'
Unfortunately, 1.2.2+dfsg-1didn't fixed the problem: dpkg -l|grep poetr ii python3-poetry 1.2.2+dfsg-1 /usr/bin/poetry config virtualenvs.create false Traceback (most recent call last): File "/usr/bin/poetry", line 5, in from poetry.console.application import main File "/usr/lib/python3/dist-packages/poetry/console/application.py", line 13, in from cleo.events.console_events import COMMAND ModuleNotFoundError: No module named 'cleo.events'
Bug#1016548: linux-image-5.19.0-rc6-amd64: Corrupted cursor and broken resume with amdgpu driver with Radeon RX 6600
Package: linux-image-5.19.0-rc6-amd64 Version: 5.19~rc6-1~exp1 Severity: important X-Debbugs-Cc: george.shuk...@gmail.com Dear Maintainer, After upgrade from 5.18.0-3-amd64 to 5.19.0-rc6-amd64 video subsystem start misbehave: * Visual artefacts after cursor * Hangs when X is active * Unable to show anything after resume on DisplayPort monitor (but working otherwise, like ssh). Following kernel trace was observed: [ 193.941836] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! [ 199.061275] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! [ 199.071242] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=3956, emitted seq=3958 [ 199.071340] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 2028 thread Xorg:cs0 pid 3062 [ 199.071424] amdgpu :0a:00.0: amdgpu: GPU reset begin! [ 199.491788] amdgpu :0a:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) [ 199.491863] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ disable failed [ 199.767776] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx [ 199.781910] [drm] free PSP TMR buffer [ 199.827452] CPU: 11 PID: 81 Comm: kworker/u64:7 Not tainted 5.19.0-rc6-amd64 #1 Debian 5.19~rc6-1~exp1 [ 199.827454] Hardware name: System manufacturer System Product Name/PRIME X570-P, BIOS 3405 02/01/2021 [ 199.827455] Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched] [ 199.827460] Call Trace: [ 199.827461] [ 199.827463] dump_stack_lvl+0x45/0x5e [ 199.827467] amdgpu_do_asic_reset+0x28/0x434 [amdgpu] [ 199.827576] amdgpu_device_gpu_recover_imp.cold+0x628/0x8fc [amdgpu] [ 199.827672] amdgpu_job_timedout+0x153/0x190 [amdgpu] [ 199.827765] drm_sched_job_timedout+0x76/0x110 [gpu_sched] [ 199.827767] process_one_work+0x1e5/0x3b0 [ 199.827770] worker_thread+0x50/0x3a0 [ 199.827772] ? rescuer_thread+0x390/0x390 [ 199.827773] kthread+0xe8/0x110 [ 199.827774] ? kthread_complete_and_exit+0x20/0x20 [ 199.827775] ret_from_fork+0x22/0x30 [ 199.827778] [ 199.827779] amdgpu :0a:00.0: amdgpu: MODE1 reset [ 199.827781] amdgpu :0a:00.0: amdgpu: GPU mode1 reset [ 199.827855] amdgpu :0a:00.0: amdgpu: GPU smu mode1 reset [ 200.341240] amdgpu :0a:00.0: amdgpu: GPU reset succeeded, trying to resume [ 200.341406] [drm] PCIE GART of 512M enabled (table at 0x00800030). [ 200.341430] [drm] VRAM is lost due to GPU reset! [ 200.341435] [drm] PSP is resuming... ... [ 200.897511] amdgpu :0a:00.0: amdgpu: GPU reset(2) succeeded! [ 200.906284] amdgpu_cs_ioctl: 16 callbacks suppressed [ 200.906286] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 200.906954] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 200.907311] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Xorg log is clean (no errors observed). Reverting back to 5.18.0-3-amd64 fix the problem. GPU details: Radeon 6600. lspci data: 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 23 [Radeon RX 6600/6600 XT/6600M] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ SERR-
Bug#988560: Package should be in contrib, as it depends on non-free software
Package: pygithub Version: 1.43.7-1 Severity: normal Pygithub is completely dependent on Github API, which is a proprietary software. I believe this package must be in contrib section (instead of main). Debian Policy chapter2.2.2 says that 'wrapper packages or other sorts of free accessories for non-free programs' should be in contrib section of the Archive. pygithub is clearly 'free accessory' for 'non free' Github server.
Bug#971591: Please update testinfra to 5.3.0
Package: testinfra Version: 3.2.0-1 Current upstream version of testinfra is 5.3, and there aren't any breaking changes compare to 3.2. Please, consider upgrading it. Thanks!
Bug#950031: Please provide metapackage without 'python' in name
Package: python-diskimage-builder Version: 2.27.1-3 Diskimage builder is used as a command line utility, so it should have a package name without 'python' prefix. The need to specify python version during installation complicates everything (including migration from Py2 to Py3). The usual approach is to use metapackage or virtual package with no version (f.e. Provides: diskimage-builder for both python-diskimage-builder and python3-diskimage-builder). By using virtual package name user can install any version which fits into python environment on the host.
Bug#933090: openhab2 packaging
Source: openhab Version: 2.4 Severity: wishlist OpenHAB is a home automation software available under Eclipse Public License - v 1.0, which is approved free license for Debian. Their homepage is https://www.openhab.org and they already provide debian packages, I believe the inclusion of this package into Debian will benefit everyone.
Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering
Package: nvidia-driver Version: 390.59-1 Followup-For: Bug #900248 I confirm this problem. I got it at upgrade from sid to sid, unfortunately, I lost exact version change. Now I can reproduce it with upgrade between testing and sid. 390.48-3 is working 390.59-1 is broken 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 00 [VGA controller]) ... Kernel driver in use: nvidia Kernel modules: nvidia -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nvidia-driver depends on: ii nvidia-alternative 390.59-1 ii nvidia-driver-bin 390.59-1 ii nvidia-driver-libs 390.59-1 ii nvidia-installer-cleanup 20151021+8 ii nvidia-kernel-dkms [nvidia-kernel-390.59] 390.59-1 ii nvidia-legacy-check390.59-1 ii nvidia-support 20151021+8 ii nvidia-vdpau-driver390.59-1 ii xserver-xorg-video-nvidia 390.59-1 Versions of packages nvidia-driver recommends: ii nvidia-persistenced 390.25-1 ii nvidia-settings 390.48-2 Versions of packages nvidia-driver suggests: ii nvidia-kernel-dkms 390.59-1 Versions of packages nvidia-driver-libs:amd64 depends on: ii libgl1-nvidia-glvnd-glx 390.59-1 ii nvidia-egl-icd 390.59-1 Versions of packages nvidia-driver-libs:amd64 recommends: ii libgles-nvidia2 390.59-1 ii libglx-nvidia0 390.59-1 ii libnvidia-cfg1 390.59-1 ii libopengl0 1.0.0+git20180308-2 pn nvidia-driver-libs-i386 ii nvidia-egl-wayland-icd 390.59-1 ii nvidia-vulkan-icd390.59-1 Versions of packages xserver-xorg-video-nvidia depends on: ii libc6 2.27-3 ii libnvidia-glcore 390.59-1 ii nvidia-alternative 390.59-1 ii nvidia-installer-cleanup 20151021+8 ii nvidia-legacy-check390.59-1 ii nvidia-support 20151021+8 ii xserver-xorg-core [xorg-video-abi-24] 2:1.20.0-2 Versions of packages xserver-xorg-video-nvidia recommends: ii nvidia-kernel-dkms [nvidia-kernel-390.59] 390.59-1 ii nvidia-settings390.48-2 ii nvidia-vdpau-driver390.59-1 Versions of packages xserver-xorg-video-nvidia suggests: ii nvidia-kernel-dkms 390.59-1 Versions of packages nvidia-alternative depends on: ii dpkg1.19.0.5+b1 ii glx-alternative-nvidia 0.8.3 ii nvidia-legacy-check 390.59-1 Versions of packages nvidia-kernel-dkms depends on: ii dkms 2.3-3 ii nvidia-installer-cleanup 20151021+8 ii nvidia-kernel-support [nvidia-kernel-support--v1] 390.59-1 nvidia-kernel-dkms recommends no packages. Versions of packages glx-alternative-nvidia depends on: ii dpkg 1.19.0.5+b1 ii glx-alternative-mesa 0.8.3 ii glx-diversions0.8.3 ii update-glx0.8.3 glx-alternative-nvidia suggests no packages. Versions of packages xserver-xorg-video-intel depends on: ii libc6 2.27-3 ii libdrm-intel1 2.4.92-1 ii libdrm22.4.92-1 ii libpciaccess0 0.14-1 ii libpixman-1-0 0.34.0-2 ii libudev1 238-5 ii libx11-6 2:1.6.5-1 ii libx11-xcb12:1.6.5-1 ii libxcb-dri2-0 1.13-1 ii libxcb-dri3-0 1.13-1 ii libxcb-sync1 1.13-1 ii libxcb-util0 0.3.8-3+b2 ii libxcb11.13-1 ii libxcursor11:1.1.15-1 ii libxdamage11:1.1.4-3 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxinerama1 2:1.1.3-1+b3 ii libxrandr2 2:1.5.1-1 ii libxrender11:0.9.10-1 ii libxshmfence1 1.3-1 ii libxss11:1.2.2-1+b2 ii libxtst6 2:1.2.3-1 ii libxv1 2:1.0.11-1 ii libxvmc1 2:1.0.10-1 ii
Bug#885522: apparmor breaks thunderbird's open link in firefox (quantum)
Package: apparmor
Version: 2.11.1-4
Severity: normal
Tags: patch
New firefox get rid of firefox.sh script and use binary
/usr/lib/firefox/firefox.
Apparmor profile for firefox is obsolete and prevents opening links in
thunderbird.
Dec 27 18:44:46 home audit[8966]: AVC apparmor="DENIED" operation="exec"
profile="thunderbird" name="/usr/lib/firefox/firefox" pid=8966
comm="thunderbird" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
Dec 27 18:44:46 home kernel: audit: type=1400 audit(1514393086.417:68):
apparmor="DENIED" operation="exec" profile="thunderbird"
name="/usr/lib/firefox/firefox" pid=8966 comm="thunderbird" requested_mask="x"
denied_mask="x" fsuid=1000 ouid=0
To fix this problem /etc/apparmor.d/abstractions/ubuntu-browsers should allow
FF run:
(add line)
/usr/lib/firefox/firefox Cx -> sanitized_helper
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages apparmor depends on:
ii debconf [debconf-2.0] 1.5.65
ii libc6 2.25-5
ii lsb-base 9.20170808
ii python33.6.4~rc1-2
apparmor recommends no packages.
Versions of packages apparmor suggests:
pn apparmor-profiles
pn apparmor-profiles-extra
pn apparmor-utils
-- Configuration Files:
/etc/apparmor.d/abstractions/ubuntu-browsers changed:
/usr/bin/arora Cx -> sanitized_helper,
/usr/bin/conkeror Cx -> sanitized_helper,
/usr/bin/dillo Cx -> sanitized_helper,
/usr/bin/Dooble Cx -> sanitized_helper,
/usr/bin/epiphany Cx -> sanitized_helper,
/usr/bin/epiphany-browser Cx -> sanitized_helper,
/usr/bin/epiphany-webkit Cx -> sanitized_helper,
/usr/lib/fennec-*/fennec Cx -> sanitized_helper,
/usr/bin/galeon Cx -> sanitized_helper,
/usr/bin/kazehakase Cx -> sanitized_helper,
/usr/bin/konqueror Cx -> sanitized_helper,
/usr/bin/midori Cx -> sanitized_helper,
/usr/bin/netsurf Cx -> sanitized_helper,
/usr/bin/prism Cx -> sanitized_helper,
/usr/bin/rekonq Cx -> sanitized_helper,
/usr/bin/seamonkey Cx -> sanitized_helper,
/usr/bin/sensible-browser Pixr,
/usr/bin/chromium-browser Cx -> sanitized_helper,
/usr/lib/chromium-browser/chromium-browser Cx -> sanitized_helper,
# this should cover all firefox browsers and versions (including shiretoko
# and abrowser)
/usr/bin/firefox Cxr -> sanitized_helper,
/usr/lib/firefox*/firefox*.sh Cx -> sanitized_helper,
/usr/lib/firefox/firefox Cx -> sanitized_helper,
/usr/lib/firefox-esr/firefox* Cx -> sanitized_helper,
# Iceweasel
/usr/bin/iceweasel Cxr -> sanitized_helper,
/usr/lib/iceweasel/iceweasel Cx -> sanitized_helper,
# some unpackaged, but popular browsers
/usr/lib/icecat-*/icecat Cx -> sanitized_helper,
/usr/bin/opera Cx -> sanitized_helper,
/opt/google/chrome{,-beta}/google-chrome{,-beta} Cx -> sanitized_helper,
-- debconf-show failed
Bug#833507: same thing
I got this bug after upgrading wpasupplicant from version 2:2.4-1.1 to version 2:2.6-11. None of my attempts to bring wifi back wasn't successful, until I rolled back wpasupplicant to 2.4. I use Broadcom Limited BCM4352 802.11ac Wireless Network Adapter (rev 03) (14e4:43b1) with broadcom-sta-dkms driver (wl.ko).
Bug#863468: IndexError: deque index out of range
Package: xonsh Version: 0.5.10+dfsg-1 Severity: normal Tags: upstream xonsh tracing if bg process is exited by Ctrl-C. Steps to reproduce: top Ctrl-Z bg Press enter few times Ctrl-C Trace: xonsh: To log full traceback to a file set: $XONSH_TRACEBACK_LOGFILE = Traceback (most recent call last): File "/usr/lib/python3/dist-packages/xonsh/__amalgam__.py", line 13061, in run redirect_stdout(STDOUT_DISPATCHER), \ File "/usr/lib/python3/dist-packages/xonsh/__amalgam__.py", line 12883, in proxy_two def proxy_two(f, args, stdin, stdout, stderr, spec): File "/usr/lib/python3/dist-packages/xonsh/__amalgam__.py", line 9633, in bg res = fg(args, stdin) IndexError: deque index out of range -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xonsh depends on: ii python3-ply 3.9-1 ii python3-venv 3.5.3-1 pn python3:any Versions of packages xonsh recommends: ii python3-prompt-toolkit 1.0.9-1 ii python3-pygments2.2.0+dfsg-1 ii python3-setproctitle1.1.10-1 Versions of packages xonsh suggests: pn xonsh-doc -- debconf-show failed
Bug#860996: uuid does not support nor --help nor --version
Package: uuid Version: 1.6.2-1.5+b4 Severity: minor Every utility should support --help (-h) and --version parameters. uuid itility use -v in a very novel way (asking for uuids version, not reporting own version), and there is no way to see help or version of utility. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages uuid depends on: ii libc6 2.24-10 ii libossp-uuid16 1.6.2-1.5+b4 uuid recommends no packages. uuid suggests no packages. -- debconf-show failed
Bug#858889: nbd-server ignores listenaddr in configuration file
Package: nbd-server Version: 1:3.15.2-2 Severity: important nbd-server silently ignores listenaddr in configuration file and listen on '*'. Steps to reproduce: 1. Set up configuration with listenaddr = 127.0.0.1 (see example below) 2. Run nbd-server Expected result: `netstat -lnp|grep nbd` should show nbd listening on 127.0.0.1 Actual result: tcp6 0 0 :::10809 :::*LISTEN 27452/nbd-server Example of configuration file /etc/nbd-server/config: [generic] # If you want to run everything as root rather than the nbd user, you # may either say "root" in the two following lines, or remove them # altogether. Do not remove the [generic] section, however. user = nbd group = nbd includedir = /etc/nbd-server/conf.d # What follows are export definitions. You may # create as much of them as # you want, but the section header has to be # unique. [backup] exportname = /backup.img listenaddr = 127.0.0.1 -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nbd-server depends on: ii adduser3.115 ii debconf [debconf-2.0] 1.5.59 ii libc6 2.24-6 ii libglib2.0-0 2.50.2-2 ii libgnutls303.5.6-7 ii ucf3.0036 nbd-server recommends no packages. nbd-server suggests no packages. -- debconf information: * nbd-server/filename: /backup.img * nbd-server/number: 1 * nbd-server/name: backup
Bug#824269: cinnamon: Cinnamon crashes with assertion Clutter:ERROR:x11/clutter-stage-x11.c:1290:clutter_x11_get_stage_window
Package: cinnamon
Version: 2.8.7-1
Severity: critical
Justification: breaks the whole system
Cinnamon crashes after recent update. It cause whole system unusable.
Crash:
**
Clutter:ERROR:x11/clutter-stage-x11.c:1290:clutter_x11_get_stage_window:
assertion failed: (CLUTTER_IS_STAGE_X11 (impl))
Aborted
tail of strace:
uname({sysname="Linux", nodename="home", ...}) = 0
futex(0x7f93c859d428, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f93c859d428, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getpid()= 3143
getpid()= 3143
getpid()= 3143
getpid()= 3143
getpid()= 3143
poll([{fd=6, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=6, revents=POLLOUT}])
writev(6,
[{"\26\0\4\0\r\0\300\3v\1\0\0\0072\f\0N\0\4\0\32\0\300\3\226\2\0\0\272\0\0\0"...,
756}, {NULL, 0}, {"", 0}], 3) = 756
poll([{fd=6, events=POLLIN}], 1, -1)= 1 ([{fd=6, revents=POLLIN}])
recvmsg(6, {msg_name(0)=NULL,
msg_iov(1)=[{"W\0\265\1\1\0\300\3\r\0\300\3v\1\0\0\t2\f\0\0072\f\0\0\0\0\0\0\0\0\0"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 268
recvmsg(6, 0x7ffe6da1b160, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=6, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=6, revents=POLLOUT}])
writev(6, [{"+\0\1\0", 4}, {NULL, 0}, {"", 0}], 3) = 4
poll([{fd=6, events=POLLIN}], 1, -1)= 1 ([{fd=6, revents=POLLIN}])
recvmsg(6, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\1\316\1\0\0\0\0\23\0\300\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(6, 0x7ffe6da1b1f0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(6, 0x7ffe6da1b1f0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
getpid()= 3143
getpid()= 3143
futex(0x7f93c859d428, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f93c859d428, FUTEX_WAKE_PRIVATE, 2147483647) = 0
write(2, "**\nClutter:ERROR:x11/clutter-sta"..., 124**
Clutter:ERROR:x11/clutter-stage-x11.c:1290:clutter_x11_get_stage_window:
assertion failed: (CLUTTER_IS_STAGE_X11 (impl))
) = 124
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(3143, 3143, SIGABRT) = 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=3143, si_uid=1000} ---
+++ killed by SIGABRT +++
Aborted
backtrace under gdb:
#0 0x75ef1458 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#1 0x75ef28da in __GI_abort () at abort.c:89
#2 0x764eed75 in g_assertion_message () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#3 0x764eee0a in g_assertion_message_expr () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#4 0x770ec557 in clutter_x11_get_stage_window () from /usr/lib/x86_64
-linux-gnu/libclutter-1.0.so.0
#5 0x7789ffcd in meta_compositor_manage_screen () from /usr/lib/x86_64
-linux-gnu/libmuffin.so.0
#6 0x778b4ea4 in ?? () from /usr/lib/x86_64-linux-gnu/libmuffin.so.0
#7 0x778c189e in meta_run () from /usr/lib/x86_64-linux-
gnu/libmuffin.so.0 #8
0x5817 in main
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages cinnamon depends on:
ii caribou 0.4.20-1
ii cinnamon-common 2.8.7-1
ii cinnamon-control-center 2.8.1-1
ii cinnamon-desktop-data2.8.1-1
ii cinnamon-screensaver 2.8.0-1
ii cinnamon-session 3.0.0-1
ii cinnamon-settings-daemon 2.8.4-2
ii cjs 3.0.1-1
ii cups-pk-helper 0.2.5-2+b1
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1
ii gir1.2-accountsservice-1.0 0.6.40-3
ii gir1.2-caribou-1.0 0.4.20-1
ii gir1.2-clutter-1.0 1.26.0-2
ii gir1.2-cmenu-3.0 3.0.0-1
ii gir1.2-cogl-1.0 1.22.0-2
ii gir1.2-gconf-2.0 3.2.6-3
ii gir1.2-gdkpixbuf-2.0 2.34.0-1
ii gir1.2-gkbd-3.0 3.6.0-1
ii gir1.2-glib-2.0 1.48.0-2
ii gir1.2-gnomedesktop-3.0 3.20.2-1
ii gir1.2-gtk-3.0 3.20.4-1
ii gir1.2-gtkclutter-1.01.8.0-1
ii gir1.2-javascriptcoregtk-3.0 2.4.11-1
ii gir1.2-keybinder-3.0
Bug#820125: mkvtoolnix-gui: Add ability to see command line for mkvmerge
Package: mkvtoolnix-gui Version: 9.0.1-1 Severity: wishlist mkvmerge-gui is very nice for a single file, but for automation command line is more comfortable. To move from mkvmerge-gui to command line it would be nice to have come kind of 'command line' info window somewhere in the job information to help users with automation. I've got my options by polling ps aux|grep mkv to see content of the --gui-mode @/tmp/file to reconstruct command line, but it's really strange to fight with opensource software to grab information 'how to do this'. -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mkvtoolnix-gui depends on: ii libboost-filesystem1.58.0 1.58.0+dfsg-5+b1 ii libboost-regex1.58.0 1.58.0+dfsg-5+b1 ii libboost-system1.58.0 1.58.0+dfsg-5+b1 ii libc6 2.22-5 ii libcurl3-gnutls7.47.0-1 ii libebml4v5 1.3.3-1 ii libgcc11:5.3.1-13 ii libmagic1 1:5.25-2 ii libmatroska6v5 1.4.4-1 ii libqt5core5a 5.5.1+dfsg-16 ii libqt5gui5 5.5.1+dfsg-16 ii libqt5network5 5.5.1+dfsg-16 ii libqt5widgets5 5.5.1+dfsg-16 ii libstdc++6 5.3.1-13 ii mkvtoolnix 9.0.1-1 ii zlib1g 1:1.2.8.dfsg-2+b1 mkvtoolnix-gui recommends no packages. mkvtoolnix-gui suggests no packages. -- debconf-show failed
Bug#813234: apt-listchanges with package name traces
Package: apt-listchanges Version: 2.85.14 Severity: minor If apt-listchanges called with package name (not *.deb file) it traces. Example: apt-listchanges gcc dpkg-deb: error: failed to read archive 'gcc': No such file or directory Traceback (most recent call last): File "/usr/bin/apt-listchanges", line 254, in main() File "/usr/bin/apt-listchanges", line 112, in main pkg = DebianFiles.Package(deb) File "/usr/share/apt-listchanges/DebianFiles.py", line 134, in __init__ self.binary = pkgdata.Package AttributeError: ControlStanza instance has no attribute 'Package' -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt-listchanges depends on: ii apt1.2.1 ii debconf [debconf-2.0] 1.5.58 ii debianutils4.7 ii python 2.7.11-1 ii python-apt 1.1.0~beta1 pn python:any ii ucf3.0033 apt-listchanges recommends no packages. Versions of packages apt-listchanges suggests: ii chromium [www-browser] 48.0.2564.82-2 ii dillo [www-browser]3.0.5-2 ii exim4-daemon-light [mail-transport-agent] 4.86-7+b2 ii iceweasel [www-browser]44.0-1 ii konqueror [www-browser]4:15.08.3-1 ii python-glade2 2.24.0-4 ii python-gtk22.24.0-4 ii w3m [www-browser] 0.5.3-26 ii xfce4-terminal [x-terminal-emulator] 0.6.3-2 ii xterm [x-terminal-emulator]322-1 -- debconf-show failed
Bug#805700: qemu-system-x86: wrong filename in man page for qemu-system-x86_64
Package: qemu-system-x86 Version: 1:2.4+dfsg-4 Severity: minor On x86_64 system qemu has qemu-system-x86_64 file, but man page says: SYNOPSIS usage: qemu-system-i386 [options] [disk_image] -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qemu-system-x86 depends on: ii ipxe-qemu 1.0.0+git-20150424.a25a16d-1 ii libaio1 0.3.110-2 ii libasound2 1.0.29-1 ii libbluetooth3 5.36-1 ii libbrlapi0.65.2~20141018-5+b2 ii libc6 2.19-22 ii libfdt1 1.4.0+dfsg-2 ii libgcc1 1:5.2.1-23 ii libglib2.0-02.46.2-1 ii libgnutls-deb0-28 3.3.18-1 ii libjpeg62-turbo 1:1.4.1-2 ii libncurses5 6.0+20151024-2 ii libnettle6 3.1.1-4 ii libnspr42:4.10.10-1 ii libnspr4-0d 2:4.10.10-1 ii libnss3 2:3.20.1-1 ii libnss3-1d 2:3.20.1-1 ii libpixman-1-0 0.33.4-1 ii libpng12-0 1.2.50-2+b2 ii libpulse0 7.1-2 ii libsasl2-2 2.1.26.dfsg1-14+b1 ii libsdl1.2debian 1.2.15-12 ii libseccomp2 2.2.3-2 ii libspice-server10.12.6-4 ii libtinfo5 6.0+20151024-2 ii libusb-1.0-02:1.0.20-1 ii libusbredirparser1 0.7-1 ii libuuid12.27.1-1 ii libvdeplug2 2.3.2+r586-2+b1 ii libx11-62:1.6.3-1 ii libxen-4.4 4.4.1-9+deb8u1 ii libxenstore3.0 4.6.0-1 ii qemu-system-common 1:2.4+dfsg-4 ii seabios 1.8.2-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages qemu-system-x86 recommends: ii qemu-utils 1:2.4+dfsg-4 Versions of packages qemu-system-x86 suggests: ii kmod 21-1 pn ovmf pn qemu-block-extra pn samba pn sgabios pn vde2 -- debconf-show failed
Bug#795150: aptitude: Aptitude displays garbage on screen during resolving
Package: aptitude Version: 0.7-1+b1 Severity: important Dear Maintainer, After recent update aptitude starts to display garbage instead of the packet names during 'resolving' stage. Here example of output: http://snag.gy/qNCPY.jpg Clearing /var/cache/aptitude does not helps. -- Package-specific info: Terminal: xterm $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.7 compiled at Aug 7 2015 19:34:17 Compiler: g++ 5.2.1 20150730 Compiled against: apt version 4.16.0 NCurses version 5.9 libsigc++ version: 2.4.1 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 5.9.20150516 cwidget version: 0.5.17 Apt version: 4.16.0 aptitude linkage: linux-vdso.so.1 (0x7ffc47967000) libapt-pkg.so.4.16 = /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.16 (0x7f80c4a17000) libncursesw.so.5 = /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7f80c47e1000) libtinfo.so.5 = /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f80c45b6000) libsigc-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x7f80c43b) libcwidget.so.3 = /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x7f80c40b1000) libsqlite3.so.0 = /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7f80c3de3000) libboost_iostreams.so.1.58.0 = /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.58.0 (0x7f80c3bca000) libxapian.so.22 = /usr/lib/libxapian.so.22 (0x7f80c37c8000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f80c35aa000) libstdc++.so.6 = /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f80c322f000) libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f80c2f2e000) libgcc_s.so.1 = /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f80c2d17000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f80c296e000) libutil.so.1 = /lib/x86_64-linux-gnu/libutil.so.1 (0x7f80c276b000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f80c2566000) libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f80c234b000) libbz2.so.1.0 = /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7f80c213b000) liblzma.so.5 = /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f80c1f17000) librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7f80c1d0f000) libuuid.so.1 = /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f80c1b09000) /lib64/ld-linux-x86-64.so.2 (0x563211923000) -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages aptitude depends on: ii aptitude-common 0.7-1 ii libapt-pkg4.161.0.10.1 ii libboost-iostreams1.58.0 1.58.0+dfsg-3 ii libc6 2.19-19 ii libcwidget3v5 0.5.17-3.1+b1 ii libgcc1 1:5.2.1-14 ii libncursesw5 5.9+20150516-2 ii libsigc++-2.0-0v5 2.4.1-2 ii libsqlite3-0 3.8.11.1-1 ii libstdc++65.2.1-14 ii libtinfo5 5.9+20150516-2 ii libxapian22v5 1.2.21-1.2 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc] 0.7-1 ii libparse-debianchangelog-perl 1.2.0-5 ii sensible-utils 0.0.9 Versions of packages aptitude suggests: pn apt-xapian-index none pn debtags none ii tasksel 3.33 -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784204: xserver-xorg-core: Segfault when --map-to-output for keyboard
Package: xserver-xorg-core Version: 2:1.16.4-1 Severity: normal I have following config: DVI-I-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ (skip) HDMI-0 connected 1920x1080+2560+0 (normal left inverted right x axis y axis) 293mm x 165mm 1920x1080 60.00*+ (skip) If I trying to map keyboard via xinput it crashes X server: xinput --create-master second xinput --map-to-output 'second keyboard' HDMI-0 I understand that 'map-to-output' for keyboard is stupid, but server crash is not good too. (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7f4fb63f2d46] (EE) 1: /usr/bin/X (0x7f4fb623c000+0x1baf29) [0x7f4fb63f6f29] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f4fb3f2d000+0x35180) [0x7f4fb3f62180] (EE) 3: /usr/bin/X (0x7f4fb623c000+0x50456) [0x7f4fb628c456] (EE) 4: /usr/bin/X (XIChangeDeviceProperty+0x21f) [0x7f4fb638b46f] (EE) 5: /usr/bin/X (0x7f4fb623c000+0x150278) [0x7f4fb638c278] (EE) 6: /usr/bin/X (0x7f4fb623c000+0x573f7) [0x7f4fb62933f7] (EE) 7: /usr/bin/X (0x7f4fb623c000+0x5b596) [0x7f4fb6297596] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f4fb3f4eb45] (EE) 9: /usr/bin/X (0x7f4fb623c000+0x4590e) [0x7f4fb628190e] (EE) (EE) Segmentation fault at address 0x20 (EE) -- Package-specific info: X server symlink status: lrwxrwxrwx 1 amarao root 13 Apr 25 2014 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 11 02:35 /usr/bin/Xorg Diversions concerning libGL are in place diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.so by glx-diversions diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by
Bug#783132: /usr/bin/disk-image-create: No man page for disk-image-create
Package: python-diskimage-builder Version: 0.1.30-1 Severity: minor File: /usr/bin/disk-image-create disk-image-create has no man page. According to Debian Policy Manual ch. 12: Each program, utility, and function should have an associated manual page included in the same package. (https://www.debian.org/doc/debian-policy/ch-docs.html) -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-diskimage-builder depends on: ii debootstrap 1.0.67 ii dpkg 1.17.25 ii kpartx0.5.0-6 ii python2.7.9-1 ii python-babel 1.3+dfsg.1-5 ii qemu-utils1:2.1+dfsg-11 python-diskimage-builder recommends no packages. python-diskimage-builder suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776880: lightdm: black border on login screen with multi-monitor configuration with different resolitions
Package: lightdm Version: 1.10.3-3 Severity: minor When computer has two or more monitors with different resolition, login screen shows debian logo stretched to size of the smallest available resolition. All area around (on monitor with larger resolution) is black, and looks ugly. Proposal: use jessie color (greeny) for that area or stretch image to largest available resolution. Position of login window will not change, but all process will looks better. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lightdm depends on: ii adduser3.113+nmu3 ii consolekit 0.4.6-5 ii dbus 1.8.14-1 ii debconf [debconf-2.0] 1.5.55 ii libc6 2.19-14 ii libgcrypt201.6.2-4+b1 ii libglib2.0-0 2.42.1-1 ii libpam-systemd 215-11 ii libpam0g 1.1.8-3.1 ii libxcb11.10-3+b1 ii libxdmcp6 1:1.1.1-1+b1 ii lightdm-gtk-greeter [lightdm-greeter] 1.8.5-2 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+7 Versions of packages lightdm suggests: ii accountsservice 0.6.37-3+b1 ii upower 0.99.1-3.1 -- Configuration Files: /etc/apparmor.d/lightdm-guest-session b51cea1a1248cf9bf45f2e9024c7734f [Errno 2] No such file or directory: u'/etc/apparmor.d/lightdm-guest-session b51cea1a1248cf9bf45f2e9024c7734f' -- debconf information: * shared/default-x-display-manager: lightdm lightdm/daemon_name: /usr/sbin/lightdm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776518: bitcoin-qt: Syncronization stuck at 322082 (No block source available)
Package: bitcoin-qt Version: 0.9.3-1 Severity: normal Tags: patch bitcoin-qt stuck at initial syncronization at block 322082 (18 weeks behind). According to bugtracker it has something to do with libssl and was fixed in version 0.9.4. Please bump version. Thanks. Github link: https://github.com/bitcoin/bitcoin/issues/5645 -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bitcoin-qt depends on: ii libboost-chrono1.55.0 1.55.0+dfsg-3 ii libboost-filesystem1.55.0 1.55.0+dfsg-3 ii libboost-program-options1.55.0 1.55.0+dfsg-3 ii libboost-system1.55.0 1.55.0+dfsg-3 ii libboost-thread1.55.0 1.55.0+dfsg-3 ii libc6 2.19-13 ii libdb5.3++ 5.3.28-9 ii libgcc1 1:4.9.2-10 ii libminiupnpc10 1.9.20140610-2 ii libprotobuf92.6.1-1 ii libqrencode33.4.3-1 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libssl1.0.0 1.0.2-1 ii libstdc++6 4.9.2-10 bitcoin-qt recommends no packages. bitcoin-qt suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573483: 3.18
Now 3.18 headers are lonely. Please build linux-kbuild-3.18. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773333: fonts-droid: droid sans fallback incorrectly displays CJK characters (too long)
Package: fonts-droid Version: 1:4.4.4r2-4 Severity: normal Characters from CJK range (3300—33FF) displays incorrectly. F.e. u (㌳) should be square, no 'linear text'. It looks like: http://snag.gy/Nif4R.jpg It should looks like: http://unicode-table.com/en/3334/ When fallback happens instead of console monospace font it completely screw with console output. -- Package-specific info: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===-==-==- ii fontconfig 2.11.0-6.3 amd64 generic font configuration library - support binaries ii libfreetype6:amd64 2.5.2-2 amd64 FreeType 2 font engine, shared library files ii libfreetype6:i386 2.5.2-2 i386 FreeType 2 font engine, shared library files ii libxft2:amd64 2.3.2-1 amd64 FreeType-based font drawing library for X -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fonts-droid depends on: ii dpkg 1.17.22 fonts-droid recommends no packages. fonts-droid suggests no packages. -- Configuration Files: /etc/fonts/conf.avail/65-droid-sans-fonts.conf fd72bca3218e0bd96e83fb21e4d73385 [Errno 2] No such file or directory: u'/etc/fonts/conf.avail/65-droid-sans-fonts.conf fd72bca3218e0bd96e83fb21e4d73385' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772767: i2c-tools: i2c* tools accept any letter instead 'Y'
Package: i2c-tools
Version: 3.1.1-1
Severity: normal
i2c-tools asking for confirmation ('Y/n') before reading from i2c, but any
letter (except 'n') is threated as 'yes'.
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages i2c-tools depends on:
ii adduser 3.113+nmu3
ii libc62.19-13
ii perl 5.20.1-3
ii udev 215-8
Versions of packages i2c-tools recommends:
ii read-edid 3.0.1-2
Versions of packages i2c-tools suggests:
pn libi2c-devnone
pn python-smbus none
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771946: lightdm: When dbus service restarted lightdm terminates and leave desktop in unworking state
Package: lightdm Version: 1.10.3-3 Severity: normal When dbus is restarted (service dbus restart) or during update, lightdm crashes (or just terminate?) and leave desktop in unresponsive state. If PC have PS/2 keyboard, it works, but USB keyboard does not and user can not longer even restart lightdm from local machine. Steps to reproduce: service dbus restart Expected behavior: Reconnect to dbus Actual behavior: crash -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lightdm depends on: ii adduser3.113+nmu3 ii consolekit 0.4.6-5 ii dbus 1.8.12-1 ii debconf [debconf-2.0] 1.5.54 ii libc6 2.19-13 ii libgcrypt201.6.2-4 ii libglib2.0-0 2.42.1-1 ii libpam-systemd 215-7 ii libpam0g 1.1.8-3.1 ii libxcb11.10-3+b1 ii libxdmcp6 1:1.1.1-1 ii lightdm-gtk-greeter [lightdm-greeter] 1.8.5-2 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+7 Versions of packages lightdm suggests: pn accountsservice none ii upower 0.99.1-3.1 -- Configuration Files: /etc/apparmor.d/lightdm-guest-session b51cea1a1248cf9bf45f2e9024c7734f [Errno 2] No such file or directory: u'/etc/apparmor.d/lightdm-guest-session b51cea1a1248cf9bf45f2e9024c7734f' -- debconf information: lightdm/daemon_name: /usr/sbin/lightdm * shared/default-x-display-manager: lightdm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771036: geeqie: delete confirmation is invisible in full-screen mode
Package: geeqie Version: 1:1.2-3+b1 Severity: normal If geeqie run in full screen, after pressing 'del' button confirmation dialogue is invisible, but active. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages geeqie depends on: ii geeqie-common1:1.2-3 ii libatk1.0-0 2.14.0-1 ii libc62.19-13 ii libcairo21.14.0-2.1 ii libexiv2-13 0.24-4 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-2 ii libgcc1 1:4.9.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-0 2.24.25-1 ii libjpeg62-turbo 1:1.3.1-10 ii liblcms2-2 2.6-3+b3 ii liblircclient0 0.9.0~pre1-1.1 ii liblua5.1-0 5.1.5-7.1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-01.36.8-3 ii libstdc++6 4.9.2-2 ii libtiff5 4.0.3-10+b3 Versions of packages geeqie recommends: ii exiftran 2.09-1+b1 ii exiv20.24-4 ii imagemagick 8:6.8.9.9-3 ii librsvg2-common 2.40.5-1 ii lpr 1:2008.05.17.1 ii ufraw-batch 0.20-1 ii zenity 3.14.0-1 Versions of packages geeqie suggests: pn geeqie-dbg none ii gimp 2.8.14-1+b1 pn libjpeg-progs none pn ufraw none pn xpaint none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766931: AttributeError: 'NoneType' if window moved with alt+stylus
Package: mypaint
Version: 1.1.0-3
Severity: minor
If mypaint window moved by holding alt + stylus move, mypaint displays trace
(non-damaging), see below.
Steps to reproduce:
1. Attach wacom tablet to PC
2. Run mypaint
3. Hold Alt key.
4. Touch anywhere on canvas.
This bug does not appear if window moved by alt+mouse.
TRACE:
Traceback (most recent call last):
File /usr/share/mypaint/gui/document.py, line 76,
button_press_cb(self=gui.document.Document object, tdw=TiledDrawWidget
object at 0x7fdf0886d460 (GtkEventBox at 0x207c8b0), event=gtk.gdk.Event at
0x7fdf07e59328: GDK_BUTTON_PRESS x=577.78, y=356.24, button=1)
result = self.modes.top.button_press_cb(tdw, event)
self.__update_last_event_info(tdw, event)
variables: {'event': ('local', gtk.gdk.Event at 0x7fdf07e59328:
GDK_BUTTON_PRESS x=577.78, y=356.24, button=1), 'tdw': ('local',
TiledDrawWidget object at 0x7fdf0886d460 (GtkEventBox at 0x207c8b0)),
'result': (None, []), 'self.modes.top.button_press_cb': ('local', bound method
SwitchableFreehandMode.button_press_cb of
gui.canvasevent.SwitchableFreehandMode object at 0x7fdf07ec8b90)}
File /usr/share/mypaint/gui/canvasevent.py, line 580,
button_press_cb(self=gui.canvasevent.SwitchableFreehandMode object,
tdw=TiledDrawWidget object at 0x7fdf0886d460 (GtkEventBox at 0x207c8b0),
event=gtk.gdk.Event at 0x7fdf07e59328: GDK_BUTTON_PRESS x=577.78, y=356.24,
button=1)
if action_name is not None:
return self._dispatch_named_action(None, tdw, event,
action_name)
variables: {'None': ('builtin', None), 'action_name': ('local',
u'ColorPickMode'), 'tdw': ('local', TiledDrawWidget object at 0x7fdf0886d460
(GtkEventBox at 0x207c8b0)), 'event': ('local', gtk.gdk.Event at
0x7fdf07e59328: GDK_BUTTON_PRESS x=577.78, y=356.24, button=1),
'self._dispatch_named_action': ('local', bound method
SwitchableFreehandMode._dispatch_named_action of
gui.canvasevent.SwitchableFreehandMode object at 0x7fdf07ec8b90)}
File /usr/share/mypaint/gui/canvasevent.py, line 647,
_dispatch_named_action(self=gui.canvasevent.SwitchableFreehandMode object,
win=None, tdw=TiledDrawWidget object at 0x7fdf0886d460 (GtkEventBox at
0x207c8b0), event=gtk.gdk.Event at 0x7fdf07e59328: GDK_BUTTON_PRESS x=577.78,
y=356.24, button=1, action_name=u'ColorPickMode')
else:
return mode.button_press_cb(tdw, event)
elif handler_type == 'popup_state':
variables: {'tdw': ('local', TiledDrawWidget object at 0x7fdf0886d460
(GtkEventBox at 0x207c8b0)), 'event': ('local', gtk.gdk.Event at
0x7fdf07e59328: GDK_BUTTON_PRESS x=577.78, y=356.24, button=1),
'mode.button_press_cb': ('local', bound method ColorPickMode.button_press_cb
of gui.colorpicker.ColorPickMode object at 0x7fdf05127850)}
File /usr/share/mypaint/gui/colorpicker.py, line 72,
button_press_cb(self=gui.colorpicker.ColorPickMode object,
tdw=TiledDrawWidget object at 0x7fdf0886d460 (GtkEventBox at 0x207c8b0),
event=gtk.gdk.Event at 0x7fdf07e59328: GDK_BUTTON_PRESS x=577.78, y=356.24,
button=1)
self._button_press_seen = True
self.doc.app.pick_color_at_pointer(self.doc.tdw, self.PICK_SIZE)
return super(ColorPickMode, self).button_press_cb(tdw, event)
AttributeError: 'NoneType' object has no attribute 'app'
wacom details:
Wacom Bamboo Connect Pen stylus id: 12 type: STYLUS
Wacom Bamboo Connect Pen eraser id: 13 type: ERASER
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mypaint depends on:
ii libatk1.0-0 2.14.0-1
ii libc6 2.19-12
ii libcairo2 1.14.0-2
ii libfontconfig1 2.11.0-6.1
ii libfreetype62.5.2-2
ii libgcc1 1:4.9.1-19
ii libgdk-pixbuf2.0-0 2.31.1-2+b1
ii libglib2.0-02.42.0-2
ii libgomp14.9.1-19
ii libgtk2.0-0 2.24.25-1
ii libjson00.11-4
ii liblcms2-2 2.6-3+b2
ii libpango1.0-0 1.36.8-2
ii libpng12-0 1.2.50-2
ii libpython2.72.7.8-11
ii libstdc++6 4.9.1-19
ii mypaint-data1.1.0-3
ii python 2.7.8-2
ii python-gtk2 2.24.0-4
ii python-numpy1:1.8.2-2
ii python2.7 2.7.8-11
Versions of packages mypaint recommends:
ii shared-mime-info 1.3-1
Versions of packages mypaint suggests:
pn mypaint-data-extras none
-- debconf-show failed
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759508: mypaint: Mypaint does not ask confirmation for 'new' and silently drops current unsaved work
Package: mypaint Version: 1.1.0-3 Severity: normal If something already drawn and unsaved, and user press 'new' or Ctrl-N, mypaint silently replace current work with empty canvas. This operation is irreversable and did not ask for confirmation. And is happily discards all hard work by single misstype. I think this is a bug. Mypaint should or ask confirmation to replace unsaved work with empty canvas, or allow to undo 'new' operation. Steps to reproduce: 1. Start drawing something beautiful, spend half of hour of work 2. Accidentially press Ctrl-N 3. Feel frustration -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mypaint depends on: ii libatk1.0-0 2.12.0-1 ii libc6 2.19-9 ii libcairo2 1.12.16-2 ii libfontconfig1 2.11.0-6 ii libfreetype62.5.2-1.1 ii libgcc1 1:4.9.1-7 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-02.40.0-4 ii libgomp14.9.1-7 ii libgtk2.0-0 2.24.24-1 ii libjson00.11-4 ii liblcms2-2 2.6-3 ii libpango1.0-0 1.36.6-1 ii libpng12-0 1.2.50-2 ii libpython2.72.7.8-5 ii libstdc++6 4.9.1-7 ii mypaint-data1.1.0-3 ii python 2.7.8-1 ii python-gtk2 2.24.0-3+b1 ii python-numpy1:1.8.2-1 ii python2.7 2.7.8-5 Versions of packages mypaint recommends: ii shared-mime-info 1.3-1 Versions of packages mypaint suggests: pn mypaint-data-extras none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758771: xfce4-power-manager conflicts with default settings of systemd/logind
Package: xfce4-power-manager Version: 1.2.0-5 Severity: normal xfce4-power-manager unable to perform some of it operations due default systemd/logind settings. Example: if power-button is set up to 'suspend' and default logind.conf is commented #HandlePowerKey=, than computer will shutdown if power-button pressed, ignoring xfce4-power-manager settings. If logind settings is changed to HandlePowerKey=ignore, all works fine. This is not xfce4-power-manager problem, but I think it should at least show warning about incompatible settings in systemd. Systemd gonna be default init service in future debian version so that problem gonna hit many users. And it really hard to debug. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfce4-power-manager depends on: ii libc6 2.19-9 ii libdbus-1-3 1.8.6-2 ii libdbus-glib-1-2 0.102-1 ii libgdk-pixbuf2.0-02.30.7-1 ii libglib2.0-0 2.40.0-4 ii libgtk2.0-0 2.24.24-1 ii libnotify40.7.6-2 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.2-1 ii libxfce4ui-1-04.10.0-5 ii libxfce4util6 4.10.1-1 ii libxfconf-0-2 4.10.0-2 ii libxrandr22:1.4.2-1 ii upower0.99.0-3 ii xfce4-power-manager-data 1.2.0-5 Versions of packages xfce4-power-manager recommends: ii libpam-systemd 208-7 ii systemd-shim6-5 ii systemd-sysv208-7 Versions of packages xfce4-power-manager suggests: pn udisks none pn xfce4-power-manager-plugins none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755730: libgl1-nvidia-glx:i386: trying to overwrite shared '/usr/share/doc/libgl1-nvidia-glx/changelog.Debian.gz'
Package: libgl1-nvidia-glx Version: 340.24-2 Severity: serious Justification: Policy 7.6.1 When both :amd64 and :i386 packages installing (as nvidia-driver suggests), dpkg reports: Preparing to unpack .../libgl1-nvidia-glx_340.24-2_i386.deb ... Unpacking libgl1-nvidia-glx:i386 (340.24-2) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-nvidia- glx_340.24-2_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgl1-nvidia- glx/changelog.Debian.gz', which is different from other instances of package libgl1-nvidia-glx:i386 Errors were encountered while processing: /var/cache/apt/archives/libgl1-nvidia-glx_340.24-2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: dpkg: dependency problems prevent configuration of libgl1-nvidia-glx-i386: libgl1-nvidia-glx-i386 depends on libgl1-nvidia-glx; however: Package libgl1-nvidia-glx:i386 is not installed. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725389: thunar: Repeated FS name in disks list with multidisk btrfs
Package: thunar Version: 1.6.3-1 Severity: minor When multidisk btrfs volume is available in system, thunar display volume name many times (as many as number of disks in btrfs). Here small preview of thunar with 8 disk btrfs file system named 'JBOD': http://s15.postimg.org/8nrgkzerf/thunar.png -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages thunar depends on: ii desktop-file-utils 0.22-1 ii exo-utils 0.10.2-2 ii libatk1.0-0 2.10.0-2 ii libc6 2.17-93 ii libcairo2 1.12.16-2 ii libdbus-1-3 1.6.14-1 ii libdbus-glib-1-20.100.2-1 ii libexo-1-0 0.10.2-2 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libglib2.0-02.36.4-1 ii libgtk2.0-0 2.24.21-1 ii libgudev-1.0-0 204-5 ii libice6 2:1.0.8-2 ii libnotify4 0.7.6-1 ii libpango1.0-0 1.32.5-5+b1 ii libsm6 2:1.2.1-2 ii libthunarx-2-0 1.6.3-1 ii libxfce4ui-1-0 4.10.0-4 ii libxfce4util6 4.10.1-1 ii libxfconf-0-2 4.10.0-2 ii shared-mime-info1.0-1+b1 ii thunar-data 1.6.3-1 Versions of packages thunar recommends: ii dbus-x111.7.4-1 ii gvfs1.16.3-1+b1 ii libfontconfig1 2.10.2-2 ii libfreetype62.4.9-1.1 ii thunar-volman 0.8.0-2 ii tumbler 0.1.29-2 ii xdg-user-dirs 0.15-1 ii xfce4-panel 4.10.1-1 Versions of packages thunar suggests: ii thunar-archive-plugin 0.3.1-2 ii thunar-media-tags-plugin 0.2.1-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724951: btrfs-tools: btrfs device stats show error (no such device) for newly added disk until FS remount
Package: btrfs-tools Version: 0.19+20130705-2 Severity: normal When new disk added to btrfs volume, right after adding 'btrfs device stats' failing: ERROR: ioctl(BTRFS_IOC_GET_DEV_STATS) on /dev/sdg1 failed: No such device home:/home/amarao# btrfs device remove /dev/sdg1 /media/JBOD/ If filesystem after device adding is unmounted and mounted back everything is ok. Log to reproduce: # btrfs device add /dev/sdg1 /media/JBOD/ # btrfs device stats /media/JBOD/ [/dev/sdb1].write_io_errs 0 [/dev/sdb1].read_io_errs0 [/dev/sdb1].flush_io_errs 0 [/dev/sdb1].corruption_errs 0 [/dev/sdb1].generation_errs 0 [/dev/sdc1].write_io_errs 0 [/dev/sdc1].read_io_errs0 [/dev/sdc1].flush_io_errs 0 [/dev/sdc1].corruption_errs 0 [/dev/sdc1].generation_errs 0 [/dev/sdd1].write_io_errs 0 [/dev/sdd1].read_io_errs0 [/dev/sdd1].flush_io_errs 0 [/dev/sdd1].corruption_errs 0 [/dev/sdd1].generation_errs 0 [/dev/sde1].write_io_errs 0 [/dev/sde1].read_io_errs0 [/dev/sde1].flush_io_errs 0 [/dev/sde1].corruption_errs 0 [/dev/sde1].generation_errs 0 [/dev/sdf1].write_io_errs 0 [/dev/sdf1].read_io_errs0 [/dev/sdf1].flush_io_errs 0 [/dev/sdf1].corruption_errs 0 [/dev/sdf1].generation_errs 0 ERROR: ioctl(BTRFS_IOC_GET_DEV_STATS) on /dev/sdg1 failed: No such device # btrfs device delete /dev/sdg1 /media/JBOD/ # btrfs device add /dev/sdg1 /media/JBOD/ # umount /media/JBOD/ # mount /dev/sdb1 /media/JBOD/ # btrfs device stats /media/JBOD/ [/dev/sdb1].write_io_errs 0 [/dev/sdb1].read_io_errs0 [/dev/sdb1].flush_io_errs 0 [/dev/sdb1].corruption_errs 0 [/dev/sdb1].generation_errs 0 [/dev/sdc1].write_io_errs 0 [/dev/sdc1].read_io_errs0 [/dev/sdc1].flush_io_errs 0 [/dev/sdc1].corruption_errs 0 [/dev/sdc1].generation_errs 0 [/dev/sdd1].write_io_errs 0 [/dev/sdd1].read_io_errs0 [/dev/sdd1].flush_io_errs 0 [/dev/sdd1].corruption_errs 0 [/dev/sdd1].generation_errs 0 [/dev/sde1].write_io_errs 0 [/dev/sde1].read_io_errs0 [/dev/sde1].flush_io_errs 0 [/dev/sde1].corruption_errs 0 [/dev/sde1].generation_errs 0 [/dev/sdf1].write_io_errs 0 [/dev/sdf1].read_io_errs0 [/dev/sdf1].flush_io_errs 0 [/dev/sdf1].corruption_errs 0 [/dev/sdf1].generation_errs 0 [/dev/sdg1].write_io_errs 0 [/dev/sdg1].read_io_errs0 [/dev/sdg1].flush_io_errs 0 [/dev/sdg1].corruption_errs 0 [/dev/sdg1].generation_errs 0 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages btrfs-tools depends on: ii e2fslibs1.42.8-1 ii libblkid1 2.20.1-5.5 ii libc6 2.17-93 ii libcomerr2 1.42.8-1 ii liblzo2-2 2.06-1.2 ii libuuid12.20.1-5.5 ii zlib1g 1:1.2.8.dfsg-1 btrfs-tools recommends no packages. btrfs-tools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#723885: phpbb3: Uninstallation dialog provide no option 'ignore' for database (un)configuration
Package: phpbb3 Severity: normal When phpbb3 is installed and configuration is not happens properly during installation dialog, it contains option 'ignore' for unaccessible or broken mysql. But uninstallation process (purge) had no that option, which cause endless 'repeat' or 'cancel'. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722575: linux-image-3.10-3-amd64: kernel BUG at /build/linux-BPzSEt/linux-3.10.11/mm/slab.c:3005!
Package: src:linux Version: 3.10.11-1 Severity: normal During new HBA test found nasty bug: Caused my following command line: mdadm --create /dev/md10 --level=10 --raid-devices=4 --chunk=4K /dev/sd*2 --assume-clean mdadm: /dev/sda2 appears to be part of a raid array: level=raid1 devices=2 ctime=Thu Sep 12 15:52:18 2013 Segmentation fault dmesg: [ 95.301415] [ cut here ] [ 95.301474] kernel BUG at /build/linux-BPzSEt/linux-3.10.11/mm/slab.c:3005! [ 95.301531] invalid opcode: [#1] SMP [ 95.301668] Modules linked in: nfsd auth_rpcgss oid_registry nfs_acl nfs lockd dns_resolver fscache sunrpc linear loop coretemp kvm_intel kvm crc32c_intel iTCO_wdt iTCO_vendor_support snd_hda_intel microcode snd_hda_codec psmouse serio_raw snd_hwdep pcspkr snd_pcm snd_page_alloc snd_timer snd i2c_i801 soundcore i2c_core lpc_ich mfd_core evdev i7core_edac ioatdma edac_core dca acpi_cpufreq mperf button processor thermal_sys ext4 crc16 jbd2 mbcache raid0 sr_mod cdrom raid1 md_mod usb_storage sg hid_generic usbhid hid sd_mod crc_t10dif ahci libahci e1000e ehci_pci uhci_hcd ehci_hcd ptp pps_core usbcore usb_common pm80xx libsas libata scsi_transport_sas scsi_mod [ 95.305146] CPU: 13 PID: 3294 Comm: mdadm Tainted: GW 3.10-3-amd64 #1 Debian 3.10.11-1 [ 95.305234] Hardware name: Supermicro X8DTL/X8DTL, BIOS 2.0a 09/04/10 [ 95.305306] task: 8801b83ba040 ti: 8801b820c000 task.ti: 8801b820c000 [ 95.305392] RIP: 0010:[810f93e1] [810f93e1] cache_alloc+0x11c/0x290 [ 95.305529] RSP: 0018:8801b820da10 EFLAGS: 00010086 [ 95.305597] RAX: 88023ccec2c8 RBX: 88023b162000 RCX: 00023b760fff [ 95.305668] RDX: 000c RSI: RDI: [ 95.305740] RBP: 88023ccec2c0 R08: 88023b093a00 R09: 88023cd47000 [ 95.305811] R10: 8801b6a90040 R11: R12: 88023b49c540 [ 95.305881] R13: R14: 88023b093a00 R15: 001b [ 95.305954] FS: 7f4f813e5700() GS:88023fca() knlGS: [ 95.306041] CS: 0010 DS: ES: CR0: 8005003b [ 95.306109] CR2: 0040ccb0 CR3: 00023c30e000 CR4: 07e0 [ 95.306180] DR0: DR1: DR2: [ 95.306251] DR3: DR6: 0ff0 DR7: 0400 [ 95.306322] Stack: [ 95.306383] 88023cdba8f0 8021 8801b6bf0158 88023b49c540 [ 95.306641] 8020 0046 8020 88023cca4000 [ 95.306897] 810fa4e9 8801b6bf0158 8801b6bf0158 8801b79aa400 [ 95.307154] Call Trace: [ 95.307220] [810fa4e9] ? kmem_cache_alloc+0x47/0xfd [ 95.307295] [a0028317] ? sas_alloc_task+0x14/0x34 [libsas] [ 95.307370] [a002f4dd] ? sas_ata_qc_issue+0x6a/0x204 [libsas] [ 95.307444] [811d60db] ? swiotlb_map_sg_attrs+0xf8/0x112 [ 95.307521] [a004ec8d] ? ata_qc_issue+0x288/0x2f3 [libata] [ 95.307598] [a00546a8] ? atapi_qc_complete+0x2c1/0x2c1 [libata] [ 95.307675] [a005548a] ? __ata_scsi_queuecmd+0x15d/0x1b7 [libata] [ 95.307750] [a002e19e] ? sas_queuecommand+0x88/0x1df [libsas] [ 95.307827] [a0001d19] ? scsi_dispatch_cmd+0x180/0x23f [scsi_mod] [ 95.307903] [a00073f8] ? scsi_request_fn+0x4c8/0x4f4 [scsi_mod] [ 95.307978] [811a8804] ? __blk_run_queue_uncond+0x1e/0x26 [ 95.308049] [811a88da] ? queue_unplugged+0x54/0x78 [ 95.308120] [811a93ed] ? blk_flush_plug_list+0x1b1/0x1c8 [ 95.308191] [811a940f] ? blk_finish_plug+0xb/0x2a [ 95.308265] [810c99fa] ? __do_page_cache_readahead+0x192/0x1b3 [ 95.308337] [810c9c6f] ? ra_submit+0x18/0x1b [ 95.308406] [810c1f0a] ? generic_file_aio_read+0x238/0x5b6 [ 95.308481] [81108f2e] ? do_sync_read+0x52/0x79 [ 95.308551] [811099c2] ? vfs_read+0x91/0xef [ 95.308620] [81109b38] ? SyS_read+0x5a/0x8b [ 95.308692] [8138b529] ? system_call_fastpath+0x16/0x1b [ 95.308761] Code: 20 48 8b 5d 28 48 8d 55 28 c7 45 60 01 00 00 00 48 39 d3 75 0c 41 8b 06 48 29 45 38 e9 b9 00 00 00 41 8b 54 24 18 39 53 20 72 2d 0f 0b 8b 7b 24 41 8b 74 24 0c ff c2 89 53 20 0f af f7 8b 54 bb [ 95.311714] RIP [810f93e1] cache_alloc+0x11c/0x290 [ 95.311827] RSP 8801b820da10 [ 95.311892] ---[ end trace 8dcf0b2c0131e7ac ]--- Hardware: CPU: vendor_id : GenuineIntel cpu family : 6 model : 44 model name : Intel(R) Xeon(R) CPU L5630 @ 2.13GHz Base Board Information: Manufacturer: Supermicro Product Name: X8DTL Version: 2.01 Serial Number: VM08S55596 Asset Tag: To Be Filled By O.E.M. Features: Board is a hosting board Board is replaceable Location In
Bug#721913: procps: w.procps does not understand --ip-addr switch
Package: procps Version: 1:3.3.8-2 Severity: minor Man page and built-in help says 'w' support -i or --ip-addr switch, but /usr/bin/w.procps refuses long version: $ w --ip-addr w: unrecognized option '--ip-addr' $ w -i 16:35:31 up 9 days, 12:08, 22 users, load average: 0,56, 0,79, 0,89 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages procps depends on: ii initscripts 2.88dsf-43 ii libc6 2.17-92+b1 ii libncurses5 5.9+20130608-1 ii libncursesw5 5.9+20130608-1 ii libprocps11:3.3.8-2 ii libtinfo5 5.9+20130608-1 ii lsb-base 4.1+Debian12 Versions of packages procps recommends: ii psmisc 22.20-1 procps suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719287: nilfs-tools: nilfs-clean should support for loop devices
Package: nilfs-tools Version: 2.1.5-1 Severity: wishlist Dear Maintainer, If nilfs2-based image is mounted with -o loop option nilfs-clean refuse to work because mounted file is not block device. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nilfs-tools depends on: ii libblkid1 2.20.1-5.5 ii libc6 2.17-92 ii libmount1 2.20.1-5.5 ii libuuid1 2.20.1-5.5 ii multiarch-support 2.17-92 nilfs-tools recommends no packages. nilfs-tools suggests no packages. -- debconf-show failed -- debsums errors found: sh: /usr/sbin/dpkg-divert: Нет такого файла или каталога -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704004: /usr/bin/xsetwacom: xsetwacom: MapToOutput does not work with proprientary nvidia drivers
Package: xserver-xorg-input-wacom Version: 0.15.0+20120515-2 Severity: normal File: /usr/bin/xsetwacom After switching from nouveau to nvidia driver xsetwacom MapToOutput stop working. xsetwacom set Wacom Bamboo Connect Pen stylus MapToOutput DVI-I-2 Unable to find an output 'DVI-I-2' xrandr output: xrandr Screen 0: minimum 8 x 8, current 5120 x 1440, maximum 8192 x 8192 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) DVI-I-2 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 60.0*+ 1920x1200 59.9 1680x1050 60.0 1600x1200 60.0 1280x1024 75.0 60.0 1280x800 59.8 1152x864 75.0 1024x768 75.0 60.0 800x60075.0 60.3 640x48075.0 59.9 DVI-I-3 connected 2560x1440+2560+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 60.0*+ 1920x1200 59.9 1680x1050 60.0 1600x1200 60.0 1280x1024 75.0 60.0 1280x800 59.8 1152x864 75.0 1024x768 75.0 60.0 800x60075.0 60.3 640x48075.0 59.9 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-input-wacom depends on: ii libc6 2.17-0experimental2 ii libx11-6 2:1.5.0-1 ii libxi6 2:1.6.1-1 ii libxinerama1 2:1.1.2-1 ii libxrandr2 2:1.3.2-2 ii xserver-xorg-core [xorg-input-abi-16] 2:1.12.4-5 xserver-xorg-input-wacom recommends no packages. Versions of packages xserver-xorg-input-wacom suggests: ii xinput 1.6.0-1 -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697167: ValueError: invalid literal for int() with base 10: '768i'
Package: arandr Version: 0.1.6-1 Severity: important After upgrading from linux-3.5 to linux-3.7 arandr broken: $ arandr Traceback (most recent call last): File /usr/bin/arandr, line 42, in module main() File /usr/lib/python2.7/dist-packages/screenlayout/gui.py, line 318, in main force_version=options.force_version File /usr/lib/python2.7/dist-packages/screenlayout/gui.py, line 159, in __init__ self.filetemplate = self.widget.load_from_x() File /usr/lib/python2.7/dist-packages/screenlayout/widget.py, line 93, in load_from_x self._xrandr.load_from_x() File /usr/lib/python2.7/dist-packages/screenlayout/xrandr.py, line 150, in load_from_x o.modes.append(Size(int(a) for a in d.strip().split( )[0].split(x))) File /usr/lib/python2.7/dist-packages/screenlayout/auxiliary.py, line 53, in __new__ arg = tuple(arg) File /usr/lib/python2.7/dist-packages/screenlayout/xrandr.py, line 150, in genexpr o.modes.append(Size(int(a) for a in d.strip().split( )[0].split(x))) ValueError: invalid literal for int() with base 10: '768i' -- Package-specific info: Output of /usr/share/bug/arandr: $ xrandr --version xrandr program version 1.3.5 Server reports RandR version 1.3 $ xrandr --query --current Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 DVI-I-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 60.0*+ 1920x1440 60.0 1856x1392 60.0 1792x1344 75.0 60.0 2048x1152 60.0 1920x1200 84.9 74.9 60.0 1920x1080 60.0 1600x1200 85.0 75.0 70.0 65.0 60.0 1680x1050 84.9 74.9 59.9 1680x945 60.0 1400x1050 85.0 74.9 59.9 1600x900 60.0 1280x1024 85.0 75.0 60.0 1440x900 84.8 75.0 59.9 1280x960 85.0 60.0 1366x768 60.0 1360x768 60.0 1280x800 84.9 74.9 59.9 1152x864 75.0 1280x768 84.8 74.9 60.0 1024x768 85.0 75.1 70.1 60.0 1024x768i 43.5 1024x576 60.0 800x60085.1 72.2 75.0 60.3 56.2 848x48060.0 640x48085.0 72.8 75.0 60.0 720x40085.0 70.1 640x40085.1 640x35085.1 DVI-I-2 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 60.0*+ 1920x1440 60.0 1856x1392 60.0 1792x1344 75.0 60.0 2048x1152 60.0 1920x1200 84.9 74.9 60.0 1920x1080 60.0 1600x1200 85.0 75.0 70.0 65.0 60.0 1680x1050 84.9 74.9 59.9 1680x945 60.0 1400x1050 85.0 74.9 59.9 1600x900 60.0 1280x1024 85.0 75.0 60.0 1440x900 84.8 75.0 59.9 1280x960 85.0 60.0 1366x768 60.0 1360x768 60.0 1280x800 84.9 74.9 59.9 1152x864 75.0 1280x768 84.8 74.9 60.0 1024x768 85.0 75.1 70.1 60.0 1024x768i 43.5 1024x576 60.0 800x60085.1 72.2 75.0 60.3 56.2 848x48060.0 640x48085.0 72.8 75.0 60.0 720x40085.0 70.1 640x40085.1 640x35085.1 $ xrandr --query --current --verbose Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 DVI-I-1 connected 2560x1440+0+0 (0x63) normal (normal left inverted right x axis y axis) 597mm x 336mm Identifier: 0x61 Timestamp: 19730 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 000010ac55a04c4b3930 1c140103803c2278ea8e05ad4f33b026 0d5054a54b008100b300d100714fa940 818001010101565e00a0a0a029503020 35005550211a00ff00473630 365430373730394b4c0a00fc0044 454c4c2055323731310a202000fd 0031561d711c000a202020202026 dithering depth:auto supported: auto 6 bpc8 bpc dithering mode: auto supported: auto off static 2x2 dynamic 2x2 scaling mode: Full supported: None Full Center Full aspect color vibrance: 150 (0x0096)range: (0,200) vibrant hue: 90 (0x005a)range: (0,180) underscan vborder: 0 (0x) range:
Bug#694885: deluge: general protection in libtorrent-rasterbar.so.6.0.0[7f605b6fc000+28b000]
Package: deluge Version: 1.3.3-2 Severity: normal Deluge crashes with following message in dmesg: /usr/bin/deluge[9875] general protection ip:7f605b7ff0ad sp:7f60337fd7e0 error:0 in libtorrent-rasterbar.so.6.0.0[7f605b6fc000+28b000] -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages deluge depends on: ii deluge-gtk 1.3.3-2 ii python 2.7.3-3 ii python-libtorrent 0.15.10-1+b1 deluge recommends no packages. deluge suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692869: deluge freeze completely with bad state dir
Package: deluge Version: 1.3.3-2 Severity: normal Dear Maintainer, Under heavy usage with some crashes, unexpected reboots and so on deluge starts to freeze completely. 1) No changes on screen 2) Gray window (after minimizing and maximizing back) 3) Ignore all signals (except KILL ans STOP) 4) strace shows sudo strace -fp 12526 Process 12526 attached with 8 threads - interrupt to quit [pid 12543] futex(0x220bd40, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 12544] futex(0x5313990, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 12542] futex(0x2045730, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 12541] futex(0x7f3d8f7eae34, FUTEX_WAIT_PRIVATE, 73, NULL unfinished ... [pid 12540] futex(0x7f3d857f9e34, FUTEX_WAIT_PRIVATE, 591, NULL unfinished ... [pid 12538] futex(0x209f9ec, FUTEX_WAIT_PRIVATE, 257741, NULL unfinished ... [pid 12526] futex(0x209f520, FUTEX_WAIT_PRIVATE, 2, NULL^C unfinished ... I've got it few days ago (previous time it was about 2yr ago). This time I save 'bad' state directory prior to purging it. Purge helps, Here the state file: http://desunote.ru/pub/state.bad.tar.gz (rename from state.bad to state and put to ~/.config/deluge dir) The best way to get freeze is wait until deluge finish loading and try to exit via menu (File-Quit), but the bug appears after some time on normal workflow too. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages deluge depends on: ii deluge-gtk 1.3.3-2 ii python 2.7.3-3 ii python-libtorrent 0.15.10-1+b1 deluge recommends no packages. deluge suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682202: xcp-squeezed: race between xenstore initialization and sqeezed
Package: xcp-squeezed Version: 1.3.2-11 Followup-For: Bug #682202 ÐI found race condtion between xcp-sqeezed and /etc/init.d/xen scripts. If sleep 10 added to xcp-sqeezed host (xcp-sqeezed and xapi) initialize normally, and if not with some probability sqeezed/xapi failed to start with message: Oct 9 16:45:57 xenhost-1 xapi: [ warn|xenhost-1|0 thread_zero|server_init D:1691a70e8b4a|startup] task [Setting up domain 0 xenstore keys] exception: Xs.Failed_to_connect Oct 9 16:45:57 xenhost-1 xapi: [error|xenhost-1|0 thread_zero||xapi] Caught exception at toplevel: 'Xs.Failed_to_connect' Oct 9 16:45:57 xenhost-1 xcp-fe: 2567 (/usr/sbin/xapi -nowatchdog -writereadyfile /var/run/xapi_startup.cookie -writ...) exitted with code 2 Oct 9 16:45:57 xenhost-1 xapi: [ info|xenhost-1|0 thread_zero||watchdog] received exit code 2 Oct 9 16:45:57 xenhost-1 xapi: [ info|xenhost-1|0 thread_zero||watchdog] Received bad exit, retrying Oct 9 16:45:57 xenhost-1 xapi: [ info|xenhost-1|0 thread_zero||watchdog] (Re)starting xapi... Oct 9 16:45:57 xenhost-1 xapi: [ warn|xenhost-1|0 thread_zero|server_init D:8448f2bcf925|startup] task [Setting up domain 0 xenstore keys] exception: Xs.Failed_to_connect Oct 9 16:45:57 xenhost-1 xapi: [error|xenhost-1|0 thread_zero||xapi] Caught exception at toplevel: 'Xs.Failed_to_connect' Oct 9 16:45:57 xenhost-1 xcp-fe: 2571 (/usr/sbin/xapi -nowatchdog -writereadyfile /var/run/xapi_startup.cookie -writ...) exitted with code 2 Oct 9 16:45:57 xenhost-1 xapi: [ info|xenhost-1|0 thread_zero||watchdog] received exit code 2 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-squeezed depends on: ii libc6 2.13-35 ii libxen-4.1 4.1.3-3 ii lsb-base 4.1+Debian7 ii xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1] 4.1.3-3 ii xen-utils-common 4.1.3-3 xcp-squeezed recommends no packages. xcp-squeezed suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688961: xcp-xapi: xe host-set-hostname-live fails (debian is not centos!)
Package: xcp-xapi Version: 1.3.2-11 Severity: normal xe host-set-hostname-live host-uuid=68878163-7c93-17af-7911-5a2726fefc66 host-name=xapi-xh3 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Subprocess exitted with unexpected code 2; stdout = [ ]; stderr = [ sed: can't read /etc/sysconfig/network: No such file or directory -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xapi depends on: ii hwdata 0.234-1 ii libc6 2.13-35 ii libpam0g 1.1.3-7.1 ii libuuid1 2.20.1-5.1 ii libvhd02.0.90-1 ii libxen-4.1 4.1.3-2 ii libxenstore3.0 4.1.3-2 ii lsb-base 4.1+Debian7 ii pciutils 1:3.1.9-5 ii python 2.7.3-2 ii python-xenapi 1.3.2-11 ii stunnel4 [stunnel] 3:4.53-1 ii xcp-eliloader 0.1-4 ii xcp-fe 0.5.2-3+b1 ii xcp-networkd 1.3.2-11 ii xcp-squeezed 1.3.2-11 ii xcp-storage-managers 0.1.1-2 ii xcp-v6d1.3.2-11 ii xcp-xe 1.3.2-11 ii xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1] 4.1.3-2 ii xen-utils-4.1 4.1.3-2 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages xcp-xapi recommends: ii cifs-utils 2:5.5-1 ii xcp-guest-templates 0.1-4 ii xcp-vncterm 0.1-2 xcp-xapi suggests no packages. -- Configuration Files: /etc/xcp/pool.conf changed: master -- debconf information: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = en_US:en, LC_ALL = (unset), LC_TIME = ru_RU.UTF-8, LC_MONETARY = ru_RU.UTF-8, LC_ADDRESS = ru_RU.UTF-8, LC_TELEPHONE = ru_RU.UTF-8, LC_NAME = ru_RU.UTF-8, LC_MEASUREMENT = ru_RU.UTF-8, LC_IDENTIFICATION = ru_RU.UTF-8, LC_NUMERIC = ru_RU.UTF-8, LC_PAPER = ru_RU.UTF-8, LANG = en_US.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). locale: Cannot set LC_ALL to default locale: No such file or directory -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678723: vif added as pif to database
Good day. Few month ago I reported bug when vif was added as PIF to database. Now I found way to reproduce this: xe vif-create network-uuid=$NET_UUID vm-uuid=$DOM0_UUID device=1 mac=f4:03:02:01:00:01 xe vif-plug uuid=$NEWVIF_UUID xe pif-scan host-uuid=$HOST_UUID xe pif-list root@lab-xh4:~# xe pif-list uuid ( RO) : 62cdddc5-89ad-38e0-e9af-879df66e409d device ( RO): eth0 currently-attached ( RO): true VLAN ( RO): -1 network-uuid ( RO): 7c83b83f-c356-a22f-3e94-36361d769853 uuid ( RO) : b953d1a0-6031-6ed5-1025-886fd9735b23 device ( RO): vif0.1 currently-attached ( RO): false VLAN ( RO): -1 network-uuid ( RO): 7f5d8a62-8074-0944-cb24-2624d6b2b1b6 uuid ( RO) : 77aa1871-a3ca-890f-651f-6967c9e598f2 device ( RO): eth1 currently-attached ( RO): false VLAN ( RO): -1 network-uuid ( RO): a382a1b9-8614-c4d0-1195-d0e9a9da6aed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682233: (no subject)
I think this commit is somehow related to that problem: commit 14216561e164671ce147458653b1fea06a4ada1e Author: James Bottomley jbottom...@parallels.com Date: Wed Jul 25 23:55:55 2012 +0400 [SCSI] Fix 'Device not ready' issue on mpt2sas This is a particularly nasty SCSI ATA Translation Layer (SATL) problem. SAT-2 says (section 8.12.2) if the device is in the stopped state as the result of processing a START STOP UNIT command (see 9.11), then the SATL shall terminate the TEST UNIT READY command with CHECK CONDITION status with the sense key set to NOT READY and the additional sense code of LOGICAL UNIT NOT READY, INITIALIZING COMMAND REQUIRED; mpt2sas internal SATL seems to implement this. The result is very confusing standby behaviour (using hdparm -y). If you suspend a drive and then send another command, usually it wakes up. However, if the next command is a TEST UNIT READY, the SATL sees that the drive is suspended and proceeds to follow the SATL rules for this, returning NOT READY to all subsequent commands. This means that the ordering of TEST UNIT READY is crucial: if you send TUR and then a command, you get a NOT READY to both back. If you send a command and then a TUR, you get GOOD status because the preceeding command woke the drive. This bit us badly because -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687936: xcp-xe: 'xe console' command undocumented
Package: xcp-xe Version: 1.3.2-11 Severity: minor xe did not prove help in autocomplete for xe console command. Steps to reproduce: xe console[tab] Output (help) does not contains xe console command. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xe depends on: ii libc6 2.13-35 xcp-xe recommends no packages. xcp-xe suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682233: mpt2sas: kernel crash under load with hanged disks
We've tested it with vanilla 3.2.12, problem was same. On 03.09.2012 06:01, Jonathan Nieder wrote: Hi George, George Shuklin wrote: Tags: upstream Which upstream version did you test? [...] That bug found in 3.2 and 3.3 versions of kernel, but not reproducing in 3.0. [...] 1) Set up large raid10. 2) Start it rebuild 3) run addition io on raid (dd if=/dev/md0 of=/dev/md0) 4) Somehow make to slow down IO on two or more disks. We found that bug in wild with normal load, but following scripts allows to see it in few minutes: [...] end_request: I/O error, dev sdf, sector 729088 [ cut here ] kernel BUG at [...]/linux-3.4.4/drivers/scsi/scsi_lib.c:1154! [...] Pid: 343, comm: kworker/5:1 Not tainted 3.4-trunk-amd64 #1 Supermicro X8DTN+-F/X8DTN+-F [...] Call Trace: [a00dbafa] ? sd_prep_fn+0x2e9/0xb8e [sd_mod] [811ace28] ? cfq_dispatch_requests+0x722/0x880 [81196589] ? create_io_context+0x5a/0x5a [811993dd] ? blk_peek_request+0xcf/0x1ac [...] Code: 85 c0 74 1d 48 8b 00 48 85 c0 74 15 48 8b 40 48 48 85 c0 74 0c 48 89 ee 48 89 df ff d0 85 c0 75 44 66 83 bd e0 00 00 00 00 75 020f 0b 48 89 ee 48 89 df e8 62 ec ff ff 48 85 c0 48 89 c2 74 20 RIP [a0076104] scsi_setup_fs_cmnd+0x45/0x83 [scsi_mod] Thanks for a clear report, and sorry for the slow reply. This is BUG_ON(!req-nr_phys_segments). Smells similar to [1], which bisected to v3.1-rc1~131^2~31 and was fixed by v3.2.2~91 (md/raid1: perform bad-block tests for WriteMostly devices too, 2012-01-09), aka v3.3-rc3~3^2~2. But that wouldn't explain triggering the same trace in a 3.4.y kernel. Is this reproducible with 3.5.2 or newer from experimental? Which 3.2.y kernel did you use to experience it? Curious, Jonathan [1] http://thread.gmane.org/gmane.linux.raid/36732 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682233: mpt2sas: kernel crash under load with hanged disks
I think that problem is specific to LSI drivers, not to linux-raid, because same tests with Adaptec (aacraid) and few onboard HBAs show no signs of crashing (hanged disks is just marked as 'failed' and all systems behave as expected). I'll try to bisect it at 3.5, but I think it's kinda simple to say where problem is: linux-3.0 do have mpt2sas 08.100.00.02 and linux-3.2 do have 10.100.00.00 And note, that mpt2sas do have strange behavior in linux-2.6.32 (version 02.100.03.00) under highload. On 03.09.2012 06:30, Jonathan Nieder wrote: George Shuklin wrote: We've tested it with vanilla 3.2.12, problem was same. Thanks for the quick feedback. Please send a summary of symptoms to linux-r...@vger.kernel.org, cc-ing Neil Brownne...@suse.de and either me or this bug log so we can track it. Be sure to mention: - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple enough --- the summary you sent here would work fine) - which kernel versions you have tested and what happened with each - full dmesg output from booting and reproducing the bug, as an attachment - any other weird symptoms or observations - what you would be able to do to track it down (can you run commands if provided? try patches? bisect to find which commit introduced the regression?) If we're lucky, the symptoms will ring a bell for Neil or someone else on-list or someone will have an idea for a test to try to track it down further. Otherwise, the best we can do is probably to bisect to find which specific change introduced the bug, as described at [1]. Regards, Jonathan [1] http://kernel-handbook.alioth.debian.org/ch-bugs.html#s9.2.1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685254: mypaint: Two options with different meaning but same name [Russian]
Package: mypaint Version: 1.0.0-1 Severity: minor Tags: l10n Dear Maintainer, In mypaint options dialog there is two options to hide menus from screen in fullscreen mode. One of them hide horizontal menu, and second is hiding floating dialogs (like brush selection). Both of them are named identically in Russian localization: Скрывать панель инструментов (hide instrumental panel). I think first one should be named Скрывать горизонтальную панель (hide horizontal panel) and second Скрывать диалоги (hide dialogs) - that translation is not exact, but really distinct one from other. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mypaint depends on: ii libc6 2.13-35 ii libgcc1 1:4.7.1-6 ii libglib2.0-02.32.3-1 ii libpng12-0 1.2.49-2 ii libpython2.72.7.3-2 ii libstdc++6 4.7.1-6 ii mypaint-data1.0.0-1 ii python 2.7.3-2 ii python-gtk2 2.24.0-3 ii python-numpy1:1.6.2-1 ii python-support 1.0.15 ii python2.7 2.7.3-2 mypaint recommends no packages. mypaint suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680099: klogd: consumes 100 % of CPU
Package: klogd Version: 1.5-6.2 Followup-For: Bug #680099 Got same problem. strace shows endless and very fast loop: read(0, , 4095) = 0 read(0, , 4095) = 0 read(0, , 4095) = 0 And that FD points to /run/klogd/kmsg file -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages klogd depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-31 ii libc6 2.13-35 ii lsb-base 4.1+Debian7 ii sysklogd [system-log-daemon] 1.5-6.2 klogd recommends no packages. klogd suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684189: wget: Please add DELETE method
Package: wget Version: 1.13.4.79-1 Severity: wishlist Dear Maintainer, wget currently provides vast set of options, but sadly do not provide DELETE method. This makes wget inferior to curl in area of RESTful API scripting. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages wget depends on: ii dpkg 1.16.8 ii install-info 4.13a.dfsg.1-10 ii libc6 2.13-35 ii libgcrypt111.5.0-3 ii libgnutls262.12.20-1 ii libgpg-error0 1.10-3 ii libidn11 1.25-2 ii libuuid1 2.20.1-5.1 ii zlib1g 1:1.2.7.dfsg-13 wget recommends no packages. wget suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682517: ocfs2console: DeprecationWarning at start prevent usage
Package: ocfs2console Version: 1.6.4-1 Severity: grave Justification: renders package unusable At start: ocfs2console Gtk-Message: Failed to load module canberra-gtk-module Traceback (most recent call last): File /usr/sbin/ocfs2console, line 38, in module from ocfs2interface.console import main File /usr/lib/pymodules/python2.7/ocfs2interface/console.py, line 23, in module from menu import Menu File /usr/lib/pymodules/python2.7/ocfs2interface/menu.py, line 23, in module from pushconfig import pushconfig_ok File /usr/lib/pymodules/python2.7/ocfs2interface/pushconfig.py, line 22, in module import o2cb_ctl File /usr/lib/pymodules/python2.7/ocfs2interface/o2cb_ctl.py, line 20, in module from process import Process File /usr/lib/pymodules/python2.7/ocfs2interface/process.py, line 20, in module import popen2 File /usr/lib/python2.7/popen2.py, line 13, in module DeprecationWarning, stacklevel=2) DeprecationWarning: The popen2 module is deprecated. Use the subprocess module. That warning stop ocfs2console execution. ls -la /usr/bin/python lrwxrwxrwx 1 root root 9 Jun 30 22:36 /usr/bin/python - python2.7 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4-trunk-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ocfs2console depends on: ii libblkid1 2.20.1-5.1 ii libc6 2.13-34 ii libcomerr2 1.42.4-3 ii libglib2.0-02.32.3-1 ii libuuid12.20.1-5.1 ii ocfs2-tools 1.6.4-1 ii python 2.7.3-1 ii python-gtk2 2.24.0-3 ii python-support 1.0.15 ocfs2console recommends no packages. ocfs2console suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682231: reportbug reacts to ctrl-c only after filling asked fields
Package: reportbug Version: 6.4 Severity: wishlist reportbug exits on Ctrl-C only after user press Enter in bug title field. I think exititng instantly is more rational: if user press ctrl-C, found reportbug does not exit and continue to fill bugreport, all entered data will be lost _after_ user done. -- Package-specific info: ** Environment settings: INTERFACE=text ** /root/.reportbugrc: reportbug_version 6.4 mode advanced ui text realname George Shuklin email george.shuk...@gmail.com no-check-uid smtphost cvt-cm1.obl.selectel.org -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4-trunk-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages reportbug depends on: ii apt 0.9.7.2 ii python2.7.3-1 ii python-reportbug 6.4 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail none pn debconf-utils none pn debsumsnone pn dlocatenone pn emacs22-bin-common | emacs23-bin-commonnone ii exim4 4.80-4 ii exim4-daemon-light [mail-transport-agent] 4.80-4 ii file 5.11-2 ii gnupg 1.4.12-4+b1 pn python-gtk2none pn python-gtkspellnone pn python-urwid none pn python-vte none pn xdg-utils none Versions of packages python-reportbug depends on: ii apt 0.9.7.2 ii python2.7.3-1 ii python-debian 0.1.21 ii python-debianbts 1.11 ii python-support1.0.15 python-reportbug suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681343: xcp-xapi: wait_for_xapi() function in init.d script does not work
Package: xcp-xapi
Version: 1.3.2-9
Severity: normal
Function wait_for_xapi in /etc/init.d/xcp-xapi does not work as intented.
Symptoms:
(on slave)
/etc/init.d/xcp-xapi restart
[] Restarting The XenAPI server: xapiThe host toolstack is still
initialising. Please wait.
Cause:
Line 'xe pif-scan host-uuid=${INSTALLATION_UUID}' called before xapi is fully
synced with master.
wait_for_xapi function in init.d script waiting for XAPI_STARTUP_COOKIE, but
this is good only for
master initialization. If host is slave, it cannot perform any (non-emergency)
operations with
database without established connection with master.
I can't see normal solution here:
1) If we will wait master connection, script can hangs if master is down.
2) We can not remove pif-scan (AFAIK).
But pif-scan should happens only if host is master (if host is slave it already
do have
properly initialized pif database and working management interface, at least in
the past).
Propose: check if host is master (/etc/xcp/pool.conf), and skip pif-scan and
template creation if
host is slave.
Patch:
root@lab-xh3:~# vim /etc/init.d/xcp-xapi
root@lab-xh3:~# diff -u /etc/init.d/xcp-xapi.old /etc/init.d/xcp-xapi
--- /etc/init.d/xcp-xapi.old2012-07-12 17:27:46.0 +0400
+++ /etc/init.d/xcp-xapi2012-07-12 17:32:52.0 +0400
@@ -104,16 +104,20 @@
# on this one. As a last resort, sleep for some time.
wait_for_xapi
- # Do some standard setup, e.g. pif-scan, template creation (maybe)
+ # Do some standard setup, e.g. pif-scan, template creation (maybe),
only if host is master
+ grep master /etc/xcp/pool.conf /dev/null
+ if [ $? -eq 0 ];
+ then
. /etc/xcp/inventory
- xe pif-scan host-uuid=${INSTALLATION_UUID}
+ xe pif-scan host-uuid=${INSTALLATION_UUID}
- # Check whether the md5 of the create-templates binary matches the one
- # used previously. If not, recreate the templates.
- if [ -e /usr/lib/xcp/lib/create_templates ]; then
- if ! md5sum -c --status $TEMPLATES_MD5_STAMP ; then
+ # Check whether the md5 of the create-templates binary matches
the one
+ # used previously. If not, recreate the templates.
+ if [ -e /usr/lib/xcp/lib/create_templates ]; then
+ if ! md5sum -c --status $TEMPLATES_MD5_STAMP ; then
/usr/lib/xcp/lib/regenerate-templates start
- md5sum /usr/lib/xcp/lib/create_templates
$TEMPLATES_MD5_STAMP
+ md5sum /usr/lib/xcp/lib/create_templates
$TEMPLATES_MD5_STAMP
+ fi
fi
fi
}
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xcp-xapi depends on:
ii hwdata 0.234-1
ii libc6 2.13-34
ii libpam0g 1.1.3-7.1
ii libuuid1 2.20.1-5.1
ii libvhd02.0.90-1
ii libxen-4.1 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii libxenstore3.0 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii lsb-base 4.1+Debian7
ii pciutils 1:3.1.9-5
ii python 2.7.3-1
ii python-xenapi 1.3.2-9
ii stunnel4 [stunnel] 3:4.53-1
ii xcp-eliloader 0.1-4
ii xcp-fe 0.5.2-3+b1
ii xcp-networkd 1.3.2-9
ii xcp-squeezed 1.3.2-9
ii xcp-storage-managers 0.1.1-2
ii xcp-v6d1.3.2-9
ii xcp-xe 1.3.2-9
ii xen-hypervisor-4.1-amd64 [xen-hypervi 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii xen-utils-4.1 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages xcp-xapi recommends:
ii cifs-utils 2:5.5-1
ii xcp-guest-templates 0.1-3
ii xcp-vncterm 0.1-2
xcp-xapi suggests no packages.
-- Configuration Files:
/etc/init.d/xcp-xapi changed:
XAPI_INIT_COMPLETE_COOKIE=/var/run/xapi_init_complete.cookie
XAPI_STARTUP_COOKIE=/var/run/xapi_startup.cookie
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC=The XenAPI server
NAME=xapi
DAEMON=/usr/sbin/$NAME
DAEMON_ARGS=-daemon -writereadyfile $XAPI_STARTUP_COOKIE -writeinitcomplete
$XAPI_INIT_COMPLETE_COOKIE -onsystemboot
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME
TEMPLATES_MD5_STAMP=/var/lib/xcp/templates.md5
[ -x $DAEMON ] || exit 0
grep hypervisor
Bug#680102: More fixes for xen-api in Wheezy
On 08.07.2012 00:22, Mike McClurg wrote: (CC'ing George Shulkin, and the #680102 bug list) On Sat, Jul 7, 2012 at 4:37 PM, Thomas Goirand tho...@goirand.fr wrote: Hi Mike and Jon, It would be really nice if you could have a look at these 3 pending issues in the Debian bug tracker: #675052: xe vm-memory-target-set does not write target to xenstore #678723: vif-interfaces added to database as PIF's #680102: xcp fails eject host from pool (no /etc/firstboot.d found) It be great to have it fix asap, before the deep freeze of Wheezy. I've been able to fix others already. Other than that, only #680102 is a concern. So 680102 is due to there not being an /etc/firstboot.d/ directory (as the ticket explains). I think we can fix this issue simply by mkdir'ing the directory /etc/firstboot.d/data at some point in xapi's installation. This would allow the pool-eject to proceed, but I think that there might be problems when the host reboots: since none of the firstboot scripts will be called, the host might not reinitialise properly. I think at this point that's all we can hope for. George, can you test that creating the /etc/firstboot.d/data directory gets you past the current exception your having? If this works good enough, let's make this the fix for now. Jon, do you have any other thoughts on this bug? Mike Here results: # mkdir /etc/firstboot.d/ # mkdir /etc/firstboot.d/data # xe pool-eject host-uuid=a6806a39-442d-f17d-b7a0-59161d18f562 WARNING: Ejecting a host from the pool will reinitialise that host's local SRs. WARNING: Any data contained with the local SRs will be lost. Type 'yes' to continue yes The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Failure(Error while calling xen-cmdline script) log snippet: [20120707T21:55:24.695Z|debug|lab-xh3|699 INET 127.0.0.1:80|pool.eject R:a16c35a5d1d4|xapi] Raised at forkhelpers.ml:181.30-76 - pervasiveext.ml:22.2-9 [20120707T21:55:24.695Z|debug|lab-xh3|699 INET 127.0.0.1:80|pool.eject R:a16c35a5d1d4|backtrace] Raised at pervasives.ml:22.22-33 - list.ml:57.20-23 - xapi_pool.ml:830.9-125 - rbac.ml:229.16-23 [20120707T21:55:24.697Z|debug|lab-xh3|699 INET 127.0.0.1:80|pool.eject R:a16c35a5d1d4|backtrace] Raised at rbac.ml:238.10-15 - server_helpers.ml:72.10-22 [20120707T21:55:24.697Z|debug|lab-xh3|699 INET 127.0.0.1:80|pool.eject R:a16c35a5d1d4|dispatcher] Server_helpers.exec exception_handler: Got exception INTERNAL_ERROR: [ Failure(Error while calling xen-cmdline script) My opinion about 'eject' on debian: 1) Clear running VM's 2) Unplug all VBD 3) Unplug all PIF's but management 4) Wipe /var/lib/xcp/state.db 5) Wipe /var/lib/xcp/local.db 6) Keep only management interface data in /var/xcp/network.db 7) restart all xcp services. During playing with bug lack of '-onsystemboot' flag for xcp I've done that operation many times, seems it working without specific problems. It even works fine without host reboot. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680102: More fixes for xen-api in Wheezy
On 08.07.2012 01:57, Mike McClurg wrote: On Sat, Jul 7, 2012 at 10:40 PM, Thomas Goirandtho...@goirand.fr wrote: On 07/08/2012 04:22 AM, Mike McClurg wrote: So 680102 is due to there not being an /etc/firstboot.d/ directory (as the ticket explains). I think we can fix this issue simply by mkdir'ing the directory /etc/firstboot.d/data at some point in xapi's installation. This would allow the pool-eject to proceed, but I think that there might be problems when the host reboots: since none of the firstboot scripts will be called, the host might not reinitialise properly. Well, writing in /etc dynamically is *forbidden* by the Debian policy. The /etc folder is for configuration, not something else! If you were using /var/lib/xcp-xapi, ok, but not /etc. Could you think about a better way to fix? Sure, we can change what xapi thinks is the firstboot directory. See ocaml/xapi/xapi_globs.ml:593 : let first_boot_dir = /etc/firstboot.d/ We could change that to /var/lib/xcp/firstboot.d. I'd like to know whether creating the /etc/firstboot.d directory will solve the problem though, before we make that change. Very naive question: Why xcp wants to preserve original database? Isn't leaving pool same as 'fresh install' (means db creation). I think situation is somehow differ from XCP ISO where some magic settings was putted by installer inside 'initial database'. For xcp-xapi it is kinda easy, because host is still operational even without xapi. If we preserve networkd settings for management interface, this will allow to perform that operations via ssh without risks to go offline. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680102: More fixes for xen-api in Wheezy
On 08.07.2012 01:57, Mike McClurg wrote: On Sat, Jul 7, 2012 at 10:40 PM, Thomas Goirand tho...@goirand.fr wrote: On 07/08/2012 04:22 AM, Mike McClurg wrote: So 680102 is due to there not being an /etc/firstboot.d/ directory (as the ticket explains). I think we can fix this issue simply by mkdir'ing the directory /etc/firstboot.d/data at some point in xapi's installation. This would allow the pool-eject to proceed, but I think that there might be problems when the host reboots: since none of the firstboot scripts will be called, the host might not reinitialise properly. Well, writing in /etc dynamically is *forbidden* by the Debian policy. The /etc folder is for configuration, not something else! If you were using /var/lib/xcp-xapi, ok, but not /etc. Could you think about a better way to fix? Sure, we can change what xapi thinks is the firstboot directory. See ocaml/xapi/xapi_globs.ml:593 : let first_boot_dir = /etc/firstboot.d/ We could change that to /var/lib/xcp/firstboot.d. I'd like to know whether creating the /etc/firstboot.d directory will solve the problem though, before we make that change. Mike ok, here. note that previous attempt kick away host from pool, but without proper local initialization. Here logs of second attempt (with /etc/firstboot.d/data manually created directory): --- [20120707T22:13:09.973Z| info|lab-xh3|43 UNIX /var/lib/xcp/xapi||cli] xe pool-eject host-uuid=a6806a39-442d-f17d-b7a0-59161d18f562 username=root password=null [20120707T22:13:09.976Z| info|lab-xh3|43 UNIX /var/lib/xcp/xapi|session.login_with_password D:763ae6ae1551|xapi] Session.create trackid=a17abf27963b50ace679a372020f2b32 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120707T22:13:09.979Z|error|lab-xh3|43 UNIX /var/lib/xcp/xapi|session.login_with_password D:763ae6ae1551|http] Failed to parse HTTP response status line [] [20120707T22:13:09.998Z| info|lab-xh3|43 UNIX /var/lib/xcp/xapi|session.login_with_password D:763ae6ae1551|xapi] stunnel pid: 19543 (cached = true) connected to 31.186.98.97:443 [20120707T22:13:09.998Z| info|lab-xh3|43 UNIX /var/lib/xcp/xapi|session.login_with_password D:763ae6ae1551|xapi] with_recorded_stunnelpid task_opt=None s_pid=19543 [20120707T22:13:10.001Z| info|lab-xh3|43 UNIX /var/lib/xcp/xapi|session.login_with_password D:763ae6ae1551|xapi] stunnel pid: 19543 (cached = true) returned stunnel to cache [20120707T22:13:10.008Z| info|lab-xh3|43 UNIX /var/lib/xcp/xapi||xapi] stunnel pid: 19546 (cached = false) connected to 31.186.98.97:443 [20120707T22:13:10.008Z| info|lab-xh3|43 UNIX /var/lib/xcp/xapi||xapi] with_recorded_stunnelpid task_opt=None s_pid=19546 [20120707T22:13:11.928Z|debug|lab-xh3|44 INET 127.0.0.1:80||dummytaskhelper] task dispatch:pool.eject D:a101a30f25d9 created by task R:95b3dab5eab2 [20120707T22:13:11.930Z| info|lab-xh3|44 INET 127.0.0.1:80|dispatch:pool.eject D:a101a30f25d9|taskhelper] task pool.eject R:95b3dab5eab2 forwarded (trackid=32a7c19154041cc8c5cfcc3729a5bcab) [20120707T22:13:11.935Z|debug|lab-xh3|44 INET 127.0.0.1:80|pool.eject R:95b3dab5eab2|xapi] Pool.eject: unplugging PBDs [20120707T22:13:11.941Z|error|lab-xh3|44 INET 127.0.0.1:80|pool.eject R:95b3dab5eab2|http] Failed to parse HTTP response status line [] [20120707T22:13:11.959Z| info|lab-xh3|44 INET 127.0.0.1:80|pool.eject R:95b3dab5eab2|xapi] stunnel pid: 19551 (cached = true) connected to 31.186.98.97:443 [20120707T22:13:11.959Z| info|lab-xh3|44 INET 127.0.0.1:80|pool.eject R:95b3dab5eab2|xapi] with_recorded_stunnelpid task_opt=None s_pid=19551 [20120707T22:13:11.989Z|debug|lab-xh3|45 INET 127.0.0.1:80||dummytaskhelper] task dispatch:PBD.unplug D:94efb9464e1f created by task R:65c1b9f31a96 [20120707T22:13:11.991Z| info|lab-xh3|45 INET 127.0.0.1:80|dispatch:PBD.unplug D:94efb9464e1f|taskhelper] task PBD.unplug R:65c1b9f31a96 forwarded (trackid=ec8fd1171c5d74b5ccf47e1f08e5f11e) [20120707T22:13:12.007Z| info|lab-xh3|45 INET 127.0.0.1:80|PBD.unplug R:65c1b9f31a96|storage_impl] SR.detach task:OpaqueRef:65c1b9f3-1a96-27c9-5c16-9ead496f8b5b sr:b9b15e78-c79b-f9b7-4238-d36be14b8075 [20120707T22:13:12.007Z|debug|lab-xh3|45 INET 127.0.0.1:80|PBD.unplug R:65c1b9f31a96|dummytaskhelper] task SR.detach D:cc70741477f6 created by task R:65c1b9f31a96 [20120707T22:13:12.011Z|debug|lab-xh3|45 INET 127.0.0.1:80|SR.detach D:cc70741477f6|sm] SM nfs sr_detach sr=OpaqueRef:a1dda990-6715-497f-2b77-7c52a836c9d0 [20120707T22:13:12.017Z| info|lab-xh3|45 INET 127.0.0.1:80|sm_exec D:0d924d490917|xapi] Session.create trackid=71411412d4436f7fc5c9514d7eee2ea9 pool=false uname= is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120707T22:13:12.038Z| info|lab-xh3|45 INET 127.0.0.1:80|sm_exec D:0d924d490917|xapi] stunnel pid: 19556 (cached = true) connected to 31.186.98.97:443 [20120707T22:13:12.038Z| info|lab-xh3|45 INET 127.0.0.1:80|sm_exec
Bug#680499: xcp-xapi: Http_client.Http_request_rejected during upgrade
Package: xcp-xapi
Version: 1.3.2-8
Severity: minor
During upgrade from 1.3.2-7 to 1.3.2-8 got follwing message on slave host
(upgrade was simulatanious on slave and master):
...
Setting up xcp-xapi (1.3.2-8) ...
The server failed to handle your request, due to an internal error. The given
message may give details useful for debugging the problem.
message: INTERNAL_ERROR: [ Http_client.Http_request_rejected({ frame = false;
method = POST; uri = /; query = [ ]; content_length = [ ]; transfer encoding
= ; version = 1.0; cookie = [ ]; task = ; subtask_of = ; content-type = ;
user_agent = xen-api-libs/1.0 }) ]
Processing triggers for menu ...
...
This message was generated bacause xapi takes some time to reinitialize and
resync with slave after restart.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xcp-xapi depends on:
ii hwdata 0.233-1
ii libc6 2.13-34
ii libpam0g 1.1.3-7.1
ii libuuid1 2.20.1-5.1
ii libvhd02.0.90-1
ii libxen-4.1 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii libxenstore3.0 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii lsb-base 4.1+Debian7
ii pciutils 1:3.1.9-5
ii python 2.7.3-1
ii python-xenapi 1.3.2-8
ii stunnel4 [stunnel] 3:4.53-1
ii xcp-eliloader 0.1-4
ii xcp-fe 0.5.2-3+b1
ii xcp-networkd 1.3.2-8
ii xcp-squeezed 1.3.2-8
ii xcp-storage-managers 0.1.1-2
ii xcp-v6d1.3.2-8
ii xcp-xe 1.3.2-8
ii xen-hypervisor-4.1-amd64 [xen-hypervi 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii xen-utils-4.1 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages xcp-xapi recommends:
ii cifs-utils 2:5.5-1
ii xcp-guest-templates 0.1-3
ii xcp-vncterm 0.1-2
xcp-xapi suggests no packages.
-- Configuration Files:
/etc/xcp/pool.conf changed:
slave:31.186.98.97
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680500: xcp-xe: Tab in autocomple of params for 'xe pif-list params=' erase some arguments
Package: xcp-xe
Version: 1.3.2-8
Severity: minor
When autocomplete for bash is activated following misbehavior happens:
xe pif-list params=device,m[Tab]
expected behavior:
autocomplete to xe pif-list params=device,management
actual behavior:
xe pif-list params=management
('device' removed)
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xcp-xe depends on:
ii libc6 2.13-34
xcp-xe recommends no packages.
xcp-xe suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680511: xcp-xe: autocomplete for sr-probe type=nfs does not provide hints for device-config
Package: xcp-xe Version: 1.3.2-8 Severity: minor XCP 0.5,1.0 and 1.1 provides hints for device-config depends on type field in sr-probe, xcp-xapi (xcp-xe) does not. Difference: XCP 1.1 behavior: xe sr-probe type=nfs device-config:[Tab] device-config: device-config:serverpath= device-config:server= xcp-xe behavior: xe sr-probe type=nfs device-config:[Tab] (nothing) Other arguments (outside device-config) is hinted: xe sr-probe type=[Tab] dummy ext fileiso nfs -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xe depends on: ii libc6 2.13-34 xcp-xe recommends no packages. xcp-xe suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678923: [Pkg-xen-devel] Bug#678923: Acknowledgement (xcp-xapi: host-disable and host-reboot make host disable forever)
On 05.07.2012 20:55, Mike McClurg wrote: On Thu, Jul 5, 2012 at 3:21 AM, George Shuklin george.shuk...@gmail.com wrote: I've done some additional research on that bug. Brief bug description: xe host-disable; xe host-reboot make host disabled endlessly after reboot without chances to be enabled: Okay, I think that the problem is that we forgot to call xapi with the -onsystemboot flag in the xcp-xapi.init script. Here is an untested patch that you should be able to manually apply (as in edit the init file by hand) to test if this fixes the issue. I'll push a proper patch to my github soon. Mike diff --git a/debian/xcp-xapi.init b/debian/xcp-xapi.init index 055e17b..b3c5959 100755 --- a/debian/xcp-xapi.init +++ b/debian/xcp-xapi.init @@ -23,7 +23,7 @@ PATH=/sbin:/usr/sbin:/bin:/usr/bin DESC=The XenAPI server NAME=xapi DAEMON=/usr/sbin/$NAME -DAEMON_ARGS=-daemon -writereadyfile $XAPI_STARTUP_COOKIE -writeinitcomplete $XAPI_INIT_COMPLETE_COOKIE +DAEMON_ARGS=-daemon -writereadyfile $XAPI_STARTUP_COOKIE -writeinitcomplete $XAPI_INIT_COMPLETE_COOKIE -onsystemboot PIDFILE=/var/run/$NAME.pid SCRIPTNAME=/etc/init.d/$NAME TEMPLATES_MD5_STAMP=/var/lib/xcp/templates.md5 Yes, this patch fixes the problem. Thank you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680528: xcp-xapi: /etc/init.d/xendomains cause xapi to hand during boot
Package: xcp-xapi
Version: 1.3.2-8
Severity: important
During startup /etc/init.d/xendomains script is called. That script is installed
with xen-utils-common witch xcp-xapi is depends on.
That script calls /usr/sbin/xen
as
xen list /dev/null
This 'xen' seems to call xapi:
xen list
^Z
[1]+ Stopped xen list
root@lab-xh3:~# ps f
PID TTY STAT TIME COMMAND
3940 pts/6Ss 0:00 -bash
3982 pts/6T 0:00 \_ /usr/sbin/xapi list
That call is never ends.
I think this is not desired behavior:
1) Script xendomains is provided by xen-utils-common
2) /usr/sbin/xen is provided by xen-utils-common
3) 'list' seems be addressed to xm/xl toolstack (not sure)
4) TOOLSTACK is pointing to xapi.
5) XAPI is not ready to serve 'list' domains and start like it expect to be
'initialized', not queried.
6) Boot process do not finish.
I think disabling of xendomains should be noted in README.Debian, or, better,
checked during installation.
Future, it can be fix to xendomains script to exit if toolstack is xapi.
Not sure is should be reported to xen package as well.
PS Everyone, who affects this problem:
update-rc.d xendomains remove
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xcp-xapi depends on:
ii hwdata 0.233-1
ii libc6 2.13-34
ii libpam0g 1.1.3-7.1
ii libuuid1 2.20.1-5.1
ii libvhd02.0.90-1
ii libxen-4.1 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii libxenstore3.0 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii lsb-base 4.1+Debian7
ii pciutils 1:3.1.9-5
ii python 2.7.3-1
ii python-xenapi 1.3.2-8
ii stunnel4 [stunnel] 3:4.53-1
ii xcp-eliloader 0.1-4
ii xcp-fe 0.5.2-3+b1
ii xcp-networkd 1.3.2-8
ii xcp-squeezed 1.3.2-8
ii xcp-storage-managers 0.1.1-2
ii xcp-v6d1.3.2-8
ii xcp-xe 1.3.2-8
ii xen-hypervisor-4.1-amd64 [xen-hypervi 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii xen-utils-4.1 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages xcp-xapi recommends:
ii cifs-utils 2:5.5-1
ii xcp-guest-templates 0.1-3
ii xcp-vncterm 0.1-2
xcp-xapi suggests no packages.
-- Configuration Files:
/etc/init.d/xcp-xapi changed:
XAPI_INIT_COMPLETE_COOKIE=/var/run/xapi_init_complete.cookie
XAPI_STARTUP_COOKIE=/var/run/xapi_startup.cookie
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC=The XenAPI server
NAME=xapi
DAEMON=/usr/sbin/$NAME
DAEMON_ARGS=-daemon -writereadyfile $XAPI_STARTUP_COOKIE -writeinitcomplete
$XAPI_INIT_COMPLETE_COOKIE -onsystemboot
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME
TEMPLATES_MD5_STAMP=/var/lib/xcp/templates.md5
[ -x $DAEMON ] || exit 0
grep hypervisor /proc/cpuinfo /dev/null || exit 0
[ -r /etc/default/$NAME ] . /etc/default/$NAME
[ -r /etc/default/xen ] . /etc/default/xen
. /lib/init/vars.sh
. /lib/lsb/init-functions
if [ ${TOOLSTACK} != xapi ]; then
log_failure_msg Xen toolstack is not set to xapi! Exiting.
exit 0
fi
if [ -f /var/run/xend.pid ]; then
log_failure_msg /var/run/xend.pid exists; ${NAME} conflicts with xend
exit 1
fi
wait_for_xapi() {
MAX_RETRIES=50
RETRY=0
while [ ${RETRY} -lt ${MAX_RETRIES} ]; do
if [ -e ${XAPI_STARTUP_COOKIE} ]; then
return 0
fi
sleep 1
RETRY=$(( ${RETRY} + 1 ))
done
return 1
}
do_start()
{
# Return
# 0 if daemon has been started
# 1 if daemon was already running
# 2 if daemon could not be started
modprobe xen-netback
modprobe xen-blkback
modprobe blktap
mkdir -p /var/run/xend/boot
mkdir -p /usr/share/xcp/packages/iso
export OCAMLRUNPARAM=b
rm -f $XAPI_STARTUP_COOKIE $XAPI_INIT_COMPLETE_COOKIE
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON
--test /dev/null \
|| return 1
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
$DAEMON_ARGS \
|| return 2
# Add code here, if necessary, that waits for the process to be ready
# to handle requests from services started subsequently which depend
# on this one. As a last
Bug#680588: xcp-xapi: startup race condition between xcp-xapi and xcp-networkd on slave
Package: xcp-xapi
Version: 1.3.2-8
Severity: important
Tags: patch
Found race condition (specific only to slave hosts):
xcp-xapi can start earlier than xcp-networkd due lack of dependency in init.d
script.
Syptoms:
After reboot slave's xcp does not work:
xe (anything):
The host failed to acquire an IP address on its management interface and
therefore cannot contact the master.
log:
/var/log/xcp-xapi.log:[20120707T01:36:51.361Z| warn|lab-xh3|0
thread_zero|bringing up management interface D:065e1b39b653|xapi] Failed to
acquire a management IP address
That bug appears only on slave host.
Patch:
--- /tmp/xcp-xapi 2012-07-07 06:13:47.0 +0400
+++ /etc/init.d/xcp-xapi2012-07-07 06:08:05.0 +0400
@@ -1,7 +1,7 @@
#! /bin/sh
### BEGIN INIT INFO
# Provides: xcp-xapi
-# Required-Start:$remote_fs $syslog xcp-squeezed xcp-v6d xcp-fe
+# Required-Start:$remote_fs $syslog xcp-squeezed xcp-v6d xcp-fe
xcp-networkd
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
(after applying exec 'update-rc.d xcp-xapi defaults')
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xcp-xapi depends on:
ii hwdata 0.233-1
ii libc6 2.13-34
ii libpam0g 1.1.3-7.1
ii libuuid1 2.20.1-5.1
ii libvhd02.0.90-1
ii libxen-4.1 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii libxenstore3.0 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii lsb-base 4.1+Debian7
ii pciutils 1:3.1.9-5
ii python 2.7.3-1
ii python-xenapi 1.3.2-8
ii stunnel4 [stunnel] 3:4.53-1
ii xcp-eliloader 0.1-4
ii xcp-fe 0.5.2-3+b1
ii xcp-networkd 1.3.2-8
ii xcp-squeezed 1.3.2-8
ii xcp-storage-managers 0.1.1-2
ii xcp-v6d1.3.2-8
ii xcp-xe 1.3.2-8
ii xen-hypervisor-4.1-amd64 [xen-hypervi 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii xen-utils-4.1 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages xcp-xapi recommends:
ii cifs-utils 2:5.5-1
ii xcp-guest-templates 0.1-3
ii xcp-vncterm 0.1-2
xcp-xapi suggests no packages.
-- Configuration Files:
/etc/init.d/xcp-xapi changed:
XAPI_INIT_COMPLETE_COOKIE=/var/run/xapi_init_complete.cookie
XAPI_STARTUP_COOKIE=/var/run/xapi_startup.cookie
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC=The XenAPI server
NAME=xapi
DAEMON=/usr/sbin/$NAME
DAEMON_ARGS=-daemon -writereadyfile $XAPI_STARTUP_COOKIE -writeinitcomplete
$XAPI_INIT_COMPLETE_COOKIE -onsystemboot
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME
TEMPLATES_MD5_STAMP=/var/lib/xcp/templates.md5
[ -x $DAEMON ] || exit 0
grep hypervisor /proc/cpuinfo /dev/null || exit 0
[ -r /etc/default/$NAME ] . /etc/default/$NAME
[ -r /etc/default/xen ] . /etc/default/xen
. /lib/init/vars.sh
. /lib/lsb/init-functions
if [ ${TOOLSTACK} != xapi ]; then
log_failure_msg Xen toolstack is not set to xapi! Exiting.
exit 0
fi
if [ -f /var/run/xend.pid ]; then
log_failure_msg /var/run/xend.pid exists; ${NAME} conflicts with xend
exit 1
fi
wait_for_xapi() {
MAX_RETRIES=50
RETRY=0
while [ ${RETRY} -lt ${MAX_RETRIES} ]; do
if [ -e ${XAPI_STARTUP_COOKIE} ]; then
return 0
fi
sleep 1
RETRY=$(( ${RETRY} + 1 ))
done
return 1
}
do_start()
{
# Return
# 0 if daemon has been started
# 1 if daemon was already running
# 2 if daemon could not be started
modprobe xen-netback
modprobe xen-blkback
modprobe blktap
mkdir -p /var/run/xend/boot
mkdir -p /usr/share/xcp/packages/iso
export OCAMLRUNPARAM=b
rm -f $XAPI_STARTUP_COOKIE $XAPI_INIT_COMPLETE_COOKIE
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON
--test /dev/null \
|| return 1
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
$DAEMON_ARGS \
|| return 2
# Add code here, if necessary, that waits for the process to be ready
# to handle requests from services started subsequently which depend
# on this one. As a last resort, sleep for some time.
wait_for_xapi
# Do some standard
Bug#675052: Problem with dynamic memory
Good day. Continue to research that issue. Current state: PV guest, static_min=500MiB, static_max=1GiB, dynamic=800MiB, domid=2 manually create /local/domain/2/control/feature_balloon. Do xe vm-memory-target-set uuid=... target=650MiB squeezed debug: 20120707T03:00:57Z Request for squeezed/balance-memory/3c46cc6a-c1df-deab-1aed-0b0ad939961b 20120707T03:00:57Z listdir /squeezed/rpc/request/balance-memory/3c46cc6a-c1df-deab-1aed-0b0ad939961b [430.86] change_host_free_memory required_mem = 9216 KiB [430.86] total_range = 0 gamma = 1.00 gamma' = inf [430.86] Total additional memory over dynamic_min = 22547476 KiB; will set gamma = 1.00 (leaving unallocated 0 KiB) [430.86] Maximum possible free memory if all active domains balloon down to dynamic_min = 22556692 [430.86] current host free mem = 22556692 KiB (aiming for 9216 KiB);; all domain targets reached; however about to adjust targets; allocation phase [430.86] F22556692 S0 R0 T25156584; 0 T1641472 A1641472 M0 Bxx; 2 T614400 A614400 M614400 Bx^ [430.86] Xenctrl.domain_setmaxmem domid=2 max=665600 (was=614400) [431.87] total_range = 0 gamma = 1.00 gamma' = inf [431.87] Total additional memory over dynamic_min = 22496276 KiB; will set gamma = 1.00 (leaving unallocated 0 KiB) [431.87] Maximum possible free memory if all active domains balloon down to dynamic_min = 22505492 [431.87] current host free mem = 22505492 KiB (aiming for 9216 KiB); cannot allocate enough; all domain targets reached; allocation phase [431.87] F22505492 S0 R0 T25156584; 0 T1641472 A1641472 M0 Bxx; 2 T665600 A665600 M665600 Bxx [431.87] Failed to free 9216 KiB of memory: operation impossible within current dynamic_min limits of balloonable domains [431.87] balance memory caught: Squeeze.Cannot_free_this_much_memory(_, _) I've not completely understand last lines. Host contains more than enough memory: xentop shows 22505492k free for host memory. dom0_mem is about 1.5GiB. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678923: Acknowledgement (xcp-xapi: host-disable and host-reboot make host disable forever)
I've done some additional research on that bug. Brief bug description: xe host-disable; xe host-reboot make host disabled endlessly after reboot without chances to be enabled: xe host-enable uuid= The specified host is disabled and cannot be re-enabled until after it has rebooted What I found: 1) That settings (host_disabled_until_reboot) is stored in /var/lib/xcp/local.db. Stopping xcp-xapi, removing that file and starting xcp-xapi back works . But ugly hack. 2) That attribute is written during reboot, initiated by xe host-reboot. Question is: what change that value in XCP? xapi or some other startup script? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678923: (no subject)
I was wrong, that bug persists in 1.3.2-7 I've recheck it on clean installation: xe host-disable; xe host-reboot After reboot do not enable host back and manual attempt is rejected: xe host-enable uuid=6510efef-2063-b32c-2169-870bde43406a The specified host is disabled and cannot be re-enabled until after it has rebooted. host: unknown -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680102: xcp-xapi: xcp fails eject host from pool (no /etc/firstboot.d found)
Package: xcp-xapi Version: 1.3.2-7 Severity: normal xcp-xapi fails to eject host from pool with following error: xe pool-eject host-uuid=a6806a39-442d-f17d-b7a0-59161d18f56f WARNING: Ejecting a host from the pool will reinitialise that host's local SRs. WARNING: Any data contained with the local SRs will be lost. Type 'yes' to continue yes The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Unix.Unix_error(20, open, /etc/firstboot.d/data/a8de56d0-b2f1-1e07-d2d3-a67d83b69ff3) ls -lad /etc/firstboot.d ls: cannot access /etc/firstboot.d: No such file or directory -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xapi depends on: ii hwdata 0.233-1 ii libc6 2.13-34 ii libpam0g 1.1.3-7.1 ii libuuid1 2.20.1-5.1 ii libvhd02.0.90-1 ii libxen-4.1 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4 ii libxenstore3.0 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4 ii lsb-base 4.1+Debian7 ii pciutils 1:3.1.9-5 ii python 2.7.3-1 ii python-xenapi 1.3.2-7 ii stunnel4 [stunnel] 3:4.53-1 ii xcp-eliloader 0.1-4 ii xcp-fe 0.5.2-3+b1 ii xcp-networkd 1.3.2-7 ii xcp-squeezed 1.3.2-7 ii xcp-storage-managers 0.1.1-2 ii xcp-v6d1.3.2-7 ii xcp-xe 1.3.2-7 ii xen-hypervisor-4.1-amd64 [xen-hypervi 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4 ii xen-utils-4.1 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages xcp-xapi recommends: ii cifs-utils 2:5.5-1 ii xcp-guest-templates 0.1-3 ii xcp-vncterm 0.1-2 xcp-xapi suggests no packages. -- Configuration Files: /etc/xcp/pool.conf changed: slave:31.186.98.97 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679636: rawtherapee: Crash with std::bad_alloc
Package: rawtherapee Version: 4.0.9-3 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** After switching to any directory with images crashes with following messages: (rawtherapee:12249): glibmm-ERROR **: unhandled exception (type std::exception) in signal handler: what: std::bad_alloc In gdb: Program received signal SIGTRAP, Trace/breakpoint trap. [Switching to Thread 0x7fffe6112700 (LWP 12482)] 0x77220341 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 bt: #0 0x77220341 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x772204d2 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x76da3bcb in Glib::exception_handlers_invoke() () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #3 0x76daa123 in ?? () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #4 0x7723c5f2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7723bdf5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x73b4cb50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x738976dd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x in ?? () -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages rawtherapee depends on: ii libatkmm-1.6-1 2.22.6-1 ii libbz2-1.0 1.0.6-3 ii libc6 2.13-33 ii libcairomm-1.0-11.10.0-1 ii libexpat1 2.1.0-1 ii libgcc1 1:4.7.1-2 ii libglib2.0-02.32.3-1 ii libglibmm-2.4-1c2a 2.32.0-1 ii libgomp14.7.1-2 ii libgtk2.0-0 2.24.10-1 ii libgtkmm-2.4-1c2a 1:2.24.2-1 ii libiptcdata01.0.4-3 ii libjpeg88d-1 ii liblcms2-2 2.2+git20110628-2.2 ii libpangomm-1.4-12.28.4-1 ii libpng12-0 1.2.49-1 ii libsigc++-2.0-0c2a 2.2.10-0.2 ii libstdc++6 4.7.1-2 ii libtiff43.9.6-5 ii rawtherapee-data4.0.9-3 rawtherapee recommends no packages. rawtherapee suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679636:
Found the reason: no free space in /home. More exact bugreport: rawtherapee crashes if no free disk space (not sure home or directory opened). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678923: xcp-xapi: host-disable and host-reboot make host disable forever
Package: xcp-xapi Version: 1.3.2-6 Severity: important I done normal reboot: xe host-disable host=this_host xe host-reboot host=this_host After reboot host stays in 'disable' state and when I've tried to make it enable I got: xe host-enable uuid=ab523ee3-0546-5400-e2db-32f340292fff The specified host is disabled and cannot be re-enabled until after it has rebooted. host: unknown I've reboot host again, but again it stays 'disabled' no matter what I do (xcp restart, master restart and so on). (this_host is a slave in two hosts pool). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xapi depends on: ii hwdata 0.233-1 ii libc6 2.13-33 ii libpam0g 1.1.3-7.1 ii libuuid1 2.20.1-5 ii libvhd02.0.90-1 ii libxen-4.1 4.1.2-6 ii libxenstore3.0 4.1.2-6 ii lsb-base 4.1+Debian7 ii pciutils 1:3.1.9-4 ii python 2.7.3~rc2-1 ii python-xenapi 1.3.2-6 ii stunnel4 [stunnel] 3:4.53-1 ii xcp-eliloader 0.1-4 ii xcp-fe 0.5.2-3+b1 ii xcp-networkd 1.3.2-6 ii xcp-squeezed 1.3.2-6 ii xcp-storage-managers 0.1.1-2 ii xcp-v6d1.3.2-6 ii xcp-xe 1.3.2-6 ii xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1] 4.1.2-6 ii xen-utils-4.1 4.1.2-6 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages xcp-xapi recommends: ii cifs-utils 2:5.5-1 ii xcp-guest-templates 0.1-3 ii xcp-vncterm 0.1-2 xcp-xapi suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678723: xcp-xapi: vif-interfaces added to database as PIF's
Package: xcp-xapi Version: 1.3.2-6 Severity: normal After some time of rebooting and toolstack restart found very funny output in 'xe pif-lis': xe pif-list params=currently-attached,device device ( RO): vif2.0 currently-attached ( RO): false device ( RO): vif211.0 currently-attached ( RO): false device ( RO): eth1 currently-attached ( RO): true device ( RO): eth1 currently-attached ( RO): true device ( RO): eth0 currently-attached ( RO): true device ( RO): eth0 currently-attached ( RO): true device ( RO): vif9.0 currently-attached ( RO): false I've done some additional research and found it happens on host with incorrect network configuration: ip address configured in /etc/network/interfaces with brutils and network backed was openvswitch. This cause errors with vif plugging to bridge, but same time cause xapi marks those vif's as PIF (physical interfaces). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xapi depends on: ii hwdata 0.233-1 ii libc6 2.13-33 ii libpam0g 1.1.3-7.1 ii libuuid1 2.20.1-5 ii libvhd02.0.90-1 ii libxen-4.1 4.1.2-6 ii libxenstore3.0 4.1.2-6 ii lsb-base 4.1+Debian7 ii pciutils 1:3.1.9-4 ii python 2.7.3~rc2-1 ii python-xenapi 1.3.2-6 ii stunnel4 [stunnel] 3:4.53-1 ii xcp-eliloader 0.1-4 ii xcp-fe 0.5.2-3+b1 ii xcp-networkd 1.3.2-6 ii xcp-squeezed 1.3.2-6 ii xcp-storage-managers 0.1.1-2 ii xcp-v6d1.3.2-6 ii xcp-xe 1.3.2-6 ii xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1] 4.1.2-6 ii xen-utils-4.1 4.1.2-6 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages xcp-xapi recommends: ii cifs-utils 2:5.5-1 ii xcp-guest-templates 0.1-3 ii xcp-vncterm 0.1-2 xcp-xapi suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677509: Acknowledgement (xcp-xapi: migration of PV linux does not produce grace ARP)
On 14.06.2012 15:48, Debian Bug Tracking System wrote: After migration of 'idle' (doning nothing) virtual machine it stops to reply to ping for long time. OK, sorry, it was error in second host configuration. Migration works fine with linux-3.2 Bug may (should?) be closed as invalid. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676873: nouveau: VM: trapped read at 0x0000000000 on ch 4 [0x0000a9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT
В Вск, 10/06/2012 в 04:32 -0500, Jonathan Nieder пишет: George Shuklin wrote: Package: linux-2.6 Version: 3.0.0-6 Is this the same machine as bug#676704? (If so, I prefer to track all symptoms in one place.) Do the VM: trapped read errors happen in 3.0.y only? That kernel is not maintained in Debian --- supported versions are 2.6.32.y, 3.2.y, and 3.4.y at the moment. Symptoms are differ. That time (676704) it was clear kernel panic with blinking LEDs on PS/2 keyboard and trace. This but is differ: system continue to run (even mouse pointer is moving), just picture is completely frozen. I don't know is this same bug or different. And I was able to see it in 3.2.19-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677509: xcp-xapi: migration of PV linux does not produce grace ARP
Package: xcp-xapi Version: 1.3.2-6 Severity: important Configuration: Two xcp-xapi hosts (default sid/xcp-xapi installation) in single pool. Network backend is bridge. After migration of 'idle' (doning nothing) virtual machine it stops to reply to ping for long time. AFAIK that caused by mac-learning table on upper level (hardware) switch, which route all frames to wrong port (ignoring migration). Usually this solved by sending 'grace ARP', allowing switch to learn new port for same MAC address. I'm not sure if guest kernel or virtualization toolstack is response for this. Tested with template 'Debian Squeeze 32', upgraded to sid. Guest kernel: linux-image-3.2.0-2-686-pae -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xapi depends on: ii hwdata 0.233-1 ii libc6 2.13-33 ii libpam0g 1.1.3-7.1 ii libuuid1 2.20.1-5 ii libvhd02.0.90-1 ii libxen-4.1 4.1.2-6 ii libxenstore3.0 4.1.2-6 ii lsb-base 4.1+Debian7 ii pciutils 1:3.1.9-3 ii python 2.7.3~rc2-1 ii python-xenapi 1.3.2-6 ii stunnel4 [stunnel] 3:4.53-1 ii xcp-eliloader 0.1-4 ii xcp-fe 0.5.2-3+b1 ii xcp-networkd 1.3.2-6 ii xcp-squeezed 1.3.2-6 ii xcp-storage-managers 0.1.1-2 ii xcp-v6d1.3.2-6 ii xcp-xe 1.3.2-6 ii xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1] 4.1.2-6 ii xen-utils-4.1 4.1.2-6 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages xcp-xapi recommends: ii cifs-utils 2:5.5-1 ii xcp-guest-templates 0.1-3 ii xcp-vncterm 0.1-2 xcp-xapi suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677395: xcp-xapi: xe pif-configure-ip does not remove old ip from interface
Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream If xe pif-configure-ip called twice with different IP, it did not remove old IP from interface (but didn't store both addresses in database). (Checked for management interface) Steps to reproduce: xe pif-reconfigure-ip uuid=... ip=IP1 xe pif-reconfigure-ip uuid=(same) ip=IP2 ... 'ip addr show' shows both addresses, and after reboot only IP2 is used. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xapi depends on: ii hwdata 0.233-1 ii libc6 2.13-33 ii libpam0g 1.1.3-7.1 ii libuuid1 2.20.1-5 ii libvhd02.0.90-1 ii libxen-4.1 4.1.2-6 ii libxenstore3.0 4.1.2-6 ii lsb-base 4.1+Debian7 ii pciutils 1:3.1.9-3 ii python 2.7.3~rc2-1 ii python-xenapi 1.3.2-6 ii stunnel4 [stunnel] 3:4.53-1 ii xcp-eliloader 0.1-4 ii xcp-fe 0.5.2-3+b1 ii xcp-networkd 1.3.2-6 ii xcp-squeezed 1.3.2-6 ii xcp-storage-managers 0.1.1-2 ii xcp-v6d1.3.2-6 ii xcp-xe 1.3.2-6 ii xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1] 4.1.2-6 ii xen-utils-4.1 4.1.2-6 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages xcp-xapi recommends: ii cifs-utils 2:5.5-1 ii xcp-guest-templates 0.1-3 ii xcp-vncterm 0.1-2 xcp-xapi suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676873: nouveau: VM: trapped read at 0x0000000000 on ch 4 [0x0000a9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT
Package: linux-2.6 Version: 3.0.0-6 Severity: normal Periodically X-server stops to work: 1) No screen updated 2) No switching to text console (Mouse cursor is moving) dmesg shows: [111463.425953] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on ch 4 [0xa9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT [111463.425961] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH FAULT [111463.425966] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH 00f0 fe0c [111463.425968] [drm] nouveau :01:00.0: PGRAPH - TRAP [111463.425971] [drm] nouveau :01:00.0: PGRAPH - ch 4 (0x000a9ac000) subc 5 class 0x8297 mthd 0x0f04 data 0x3d10812e [111467.695915] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH FAULT [111467.695923] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH 00f0 fe0c [111467.695926] [drm] nouveau :01:00.0: PGRAPH - TRAP [111467.695931] [drm] nouveau :01:00.0: PGRAPH - ch 4 (0x000a9ac000) subc 5 class 0x8297 mthd 0x15f0 data 0x009c0099 [111467.695942] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on ch 4 [0xa9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT [111467.695952] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH FAULT [111467.695958] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH 00f0 fe0c [111467.695962] [drm] nouveau :01:00.0: PGRAPH - TRAP [111467.695966] [drm] nouveau :01:00.0: PGRAPH - ch 4 (0x000a9ac000) subc 5 class 0x8297 mthd 0x15f0 data 0x009c0099 [111467.695974] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on ch 4 [0xa9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT [111467.695984] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH FAULT [111467.695990] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH 00f0 fe0c [111467.695992] [drm] nouveau :01:00.0: PGRAPH - TRAP [111467.695996] [drm] nouveau :01:00.0: PGRAPH - ch 4 (0x000a9ac000) subc 5 class 0x8297 mthd 0x15f0 data 0x009c0099 [111467.696010] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on ch 4 [0xa9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT [111467.696020] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH FAULT [111467.696027] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH 00f0 fe0c [111467.696029] [drm] nouveau :01:00.0: PGRAPH - TRAP [111467.696033] [drm] nouveau :01:00.0: PGRAPH - ch 4 (0x000a9ac000) subc 5 class 0x8297 mthd 0x15f0 data 0x009c0099 [111467.696048] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on ch 4 [0xa9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT [111467.696057] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH FAULT [111467.696062] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH 00f0 fe0c [111467.696064] [drm] nouveau :01:00.0: PGRAPH - TRAP [111467.696068] [drm] nouveau :01:00.0: PGRAPH - ch 4 (0x000a9ac000) subc 5 class 0x8297 mthd 0x15f0 data 0x009c0099 [111467.696076] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on ch 4 [0xa9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT (repeated many times) -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: System manufacturer product_name: System Product Name product_version: System Version chassis_vendor: Chassis Manufacture chassis_version: Chassis Version bios_vendor: American Megatrends Inc. bios_version: 1406 board_vendor: ASUSTeK Computer INC. board_name: P5Q board_version: Rev 1.xx ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:82d3] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied 00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset PCI Express Root Port [8086:2e21] (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: a000-afff Memory behind bridge: fa00-fe8f Prefetchable memory behind bridge: d000-dfff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:1a.0 USB controller [0c03]: Intel
Bug#676704: linux-image-3.2.0-2-amd64: GPF in nouveau module
Package: linux-2.6 Version: 3.2.19-1 Severity: normal After switching from nvidia to noveau linux sometime panic. I've made some screenshots of that crash, here (handwritten) begin of crash: general protection fault: [#1] SMP CPU 0 ... Call Trace: IRQ nv50_display_isr+0x1ae/0x2b4 [nouveau] arch_local_irq_save+0x11/0x17 nouveau_irq_handler+0x7a/0x116 [nouveau] handle_irq_event_percpu+0x50/0x180 paravirt_read_tsc+0x5/0x8 timekeeping_get_ns+0xd/0x2a handle_irq_event+0x34/0x53 arch_local_irq_save+0x11/0x17 handle_fasteoi_irq+0x7c/0xaf handle_irq+0x1d/0x21 do_IRQ+0x42/0x98 common_interrupt+0x6e/0x6 EOI arch_local_rq_enable+0x4/0x8 [processor] acpi_idle_enter_simple+0xc6/0x102 [processor] cputeidle_idle_call+0xec/0x179 Here screenshot: http://desunote.ru/s/nouveau_panic1.jpg http://desunote.ru/s/nouveau_panic2.jpg -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.19-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Fri Jun 1 17:49:08 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 root=UUID=0d8d9d81-e17b-4146-a045-098982bd8f4e ro quiet ** Not tainted ** Kernel log: [ 14.430422] EXT4-fs (dm-9): ext4_orphan_cleanup: deleting unreferenced inode 24822347 [ 14.774761] EXT4-fs (dm-9): ext4_orphan_cleanup: deleting unreferenced inode 24821156 [ 14.774785] EXT4-fs (dm-9): 72 orphan inodes deleted [ 14.774787] EXT4-fs (dm-9): 1 truncate cleaned up [ 14.774789] EXT4-fs (dm-9): recovery complete [ 14.920830] EXT4-fs (dm-9): mounted filesystem with ordered data mode. Opts: (null) [ 15.023042] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 15.023739] SGI XFS Quota Management subsystem [ 15.024512] XFS (dm-6): Mounting Filesystem [ 15.205017] XFS (dm-6): Starting recovery (logdev: internal) [ 15.386546] XFS (dm-6): Ending recovery (logdev: internal) [ 15.394884] XFS (dm-0): Mounting Filesystem [ 15.551416] XFS (dm-0): Starting recovery (logdev: internal) [ 15.774776] XFS (dm-0): Ending recovery (logdev: internal) [ 15.817604] XFS (dm-4): Mounting Filesystem [ 15.949340] XFS (dm-4): Starting recovery (logdev: internal) [ 16.013137] XFS (dm-4): Ending recovery (logdev: internal) [ 16.946120] ip_tables: (C) 2000-2006 Netfilter Core Team [ 16.955010] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 17.052739] r8169 :05:01.0: eth2: link down [ 17.052745] r8169 :05:01.0: eth2: link down [ 17.053873] ADDRCONF(NETDEV_UP): eth2: link is not ready [ 17.071098] r8169 :05:00.0: eth3: link down [ 17.07] r8169 :05:00.0: eth3: link down [ 17.072094] ADDRCONF(NETDEV_UP): eth3: link is not ready [ 18.649756] r8169 :05:01.0: eth2: link up [ 18.650690] ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready [ 18.702780] r8169 :05:00.0: eth3: link up [ 18.703712] ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready [ 22.990637] fuse init (API version 7.17) [ 24.449117] tun: Universal TUN/TAP device driver, 1.6 [ 24.449119] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com [ 25.603710] Bluetooth: Core ver 2.16 [ 25.603740] NET: Registered protocol family 31 [ 25.603742] Bluetooth: HCI device and connection manager initialized [ 25.603745] Bluetooth: HCI socket layer initialized [ 25.603747] Bluetooth: L2CAP socket layer initialized [ 25.603752] Bluetooth: SCO socket layer initialized [ 25.676850] Bluetooth: RFCOMM TTY layer initialized [ 25.676857] Bluetooth: RFCOMM socket layer initialized [ 25.676859] Bluetooth: RFCOMM ver 1.11 [ 25.696809] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 25.696812] Bluetooth: BNEP filters: protocol multicast [ 29.568018] eth3: no IPv6 routers present [ 29.933407] colord[4063]: segfault at 8 ip 0040bc6d sp 7fff7c1e2be0 error 4 in colord[40+2] [ 126.008604] sd 9:0:0:0: [sdj] 15659008 512-byte logical blocks: (8.01 GB/7.46 GiB) [ 126.016217] sd 9:0:0:0: [sdj] No Caching mode page present [ 126.016221] sd 9:0:0:0: [sdj] Assuming drive cache: write through [ 126.030214] sd 9:0:0:0: [sdj] No Caching mode page present [ 126.030218] sd 9:0:0:0: [sdj] Assuming drive cache: write through [ 126.032614] sdj: sdj1 [ 126.273370] FAT-fs (sdj1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! ** Model information sys_vendor: System manufacturer product_name: System Product Name product_version: System Version chassis_vendor: Chassis Manufacture chassis_version: Chassis Version bios_vendor: American Megatrends Inc. bios_version: 1406 board_vendor: ASUSTeK Computer INC. board_name: P5Q board_version: Rev 1.xx ** Loaded modules: nls_utf8 nls_cp437 vfat fat bnep rfcomm acpi_cpufreq bluetooth mperf cpufreq_userspace rfkill cpufreq_stats cpufreq_conservative cpufreq_powersave tun snd_hrtimer binfmt_misc fuse ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack
Bug#630908: deluge: Crash if column header is dragged under fluxbox WM
I've check it with deluge --version deluge: 1.3.3 libtorrent: 0.15.10.0 Problem is no longer exists. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675157: /etc/init.d/mdadm: 428: /lib/lsb/init-functions: FANCYTTY: parameter not set
Package: mdadm Version: 3.2.4-1 Severity: normal Got following during upgrade: Preparing to replace mdadm 3.2.4-1 (using .../mdadm_3.2.5-1_i386.deb) ... /etc/init.d/mdadm: 428: /lib/lsb/init-functions: FANCYTTY: parameter not set invoke-rc.d: initscript mdadm, action stop failed. dpkg: warning: subprocess old pre-removal script returned error exit status 2 dpkg - trying script from the new package instead ... /etc/init.d/mdadm: 428: /lib/lsb/init-functions: FANCYTTY: parameter not set invoke-rc.d: initscript mdadm, action stop failed. -- Package-specific info: --- mdadm.conf DEVICE partitions CREATE owner=root group=disk mode=0660 auto=yes HOMEHOST system MAILADDR root ARRAY /dev/md/101 metadata=1.2 UUID=2e027406:57ace60e:4aeb04e1:8fce72e0 name=lab-xh3:101 --- /etc/default/mdadm INITRDSTART='all' AUTOSTART=true AUTOCHECK=true START_DAEMON=true DAEMON_OPTIONS=--syslog VERBOSE=false --- /proc/mdstat: Personalities : [raid10] md101 : active (auto-read-only) raid10 sdb[0] sdc[1] 976761344 blocks super 1.2 2 near-copies [2/2] [UU] unused devices: none --- /proc/partitions: major minor #blocks name 8 32 976762584 sdc 8 16 976762584 sdb 80 976762584 sda 81 970692608 sda1 82 1 sda2 856067200 sda5 9 101 976761344 md101 25208388608 tda --- LVM physical volumes: --- mount output udev on /dev type devtmpfs (rw,relatime,size=430348k,nr_inodes=107587,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=88688k,mode=755) /dev/disk/by-uuid/4bbe3509-887c-4f61-ba06-e357e0bfc8c3 on / type ext3 (rw,relatime,errors=remount-ro,barrier=1,data=ordered) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,size=177376k) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,relatime,size=177376k) rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) xenfs on /proc/xen type xenfs (rw,relatime) 31.186.98.100:/mnt/4c15ea03-5d70-938e-8265-d5424c0fda5e on /run/sr-mount/4c15ea03-5d70-938e-8265-d5424c0fda5e type nfs4 (rw,relatime,sync,vers=4,rsize=131072,wsize=131072,namlen=255,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,soft,noac,proto=tcp,port=0,timeo=133,retrans=2147483647,sec=sys,clientaddr=31.186.98.100,minorversion=0,local_lock=none,addr=31.186.98.100) --- initrd.img-3.2.0-2-686-pae: 51527 blocks c88568471781f4400db5448321a78a28 ./sbin/mdadm 052c312261576cc3cd64f84fb3dc8cf6 ./lib/modules/3.2.0-2-686-pae/kernel/drivers/md/raid10.ko 1a1cdcc1bb7f02b0604014d5061251e5 ./lib/modules/3.2.0-2-686-pae/kernel/drivers/md/dm-region-hash.ko 5f4399c057201152b4a7331397c2408f ./lib/modules/3.2.0-2-686-pae/kernel/drivers/md/dm-mirror.ko f38c8d3ae566bcb5f805773662224818 ./lib/modules/3.2.0-2-686-pae/kernel/drivers/md/dm-snapshot.ko 94ec110b145106714fa944b5bb4e2af0 ./lib/modules/3.2.0-2-686-pae/kernel/drivers/md/linear.ko e0be1bb135dae82606e44962d54d9566 ./lib/modules/3.2.0-2-686-pae/kernel/drivers/md/multipath.ko eaf60b434276b32c5cf5689dd82fa7ec ./lib/modules/3.2.0-2-686-pae/kernel/drivers/md/dm-mod.ko b378c3ae3cad3763c0071d41c7511cb4 ./lib/modules/3.2.0-2-686-pae/kernel/drivers/md/raid0.ko b08537a674673ef7c9499f31bcb871ac ./lib/modules/3.2.0-2-686-pae/kernel/drivers/md/raid456.ko d1b762d41413a646eb49d1cd70ed6a74 ./lib/modules/3.2.0-2-686-pae/kernel/drivers/md/dm-log.ko 505e0ede5bfbd1971cbc35a8a356396c ./lib/modules/3.2.0-2-686-pae/kernel/drivers/md/md-mod.ko 97da324d9c36199206eedfca436812ca ./lib/modules/3.2.0-2-686-pae/kernel/drivers/md/raid1.ko f4fbd9099399ab08ba9b9f6c71d77595 ./scripts/local-top/mdadm 1cebd054281e57824a0f15d3abaf9ad9 ./etc/mdadm/mdadm.conf --- initrd's /conf/conf.d/md: MD_HOMEHOST='lab-xh3' MD_DEVPAIRS='/dev/md/101:raid10' MD_LEVELS='raid10' MD_DEVS=all MD_MODULES='raid10' --- /proc/modules: dm_mod 57278 0 - Live 0xf66a3000 raid10 30331 1 - Live 0xf66d1000 md_mod 85719 1 raid10, Live 0xf000 --- /var/log/syslog: --- volume detail: /dev/sda: MBR Magic : aa55 Partition[0] : 1941385216 sectors at 2048 (type 83) Partition[1] : 12134402 sectors at 1941389310 (type 05) -- /dev/sda1 is not recognised by mdadm. /dev/sda2: MBR Magic : aa55 Partition[0] : 12134400 sectors at2 (type 82) -- /dev/sda5 is not recognised by mdadm. /dev/sdb: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 2e027406:57ace60e:4aeb04e1:8fce72e0 Name : lab-xh3:101 (local to host lab-xh3) Creation Time : Mon Mar 19 13:44:16 2012 Raid Level : raid10 Raid Devices : 2 Avail Dev Size : 1953523120 (931.51 GiB 1000.20 GB) Array Size : 976761344 (931.51 GiB 1000.20 GB)
Bug#675050: Acknowledgement (xcp-xapi: /usr/lib/xcp/lib/bin/xe-edit-bootloader uses wrong path to the 'xe')
same for xe-xentrace - wrong xe path. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675190: BUG: unable to handle kernel paging request at 27c97000 during reboot under xen
Package: linux-2.6 Version: 3.2.18-1 Severity: minor linux 3.22 Ñcrashing during reboot when ran under xcp-xapi toolstack. VM configuration is default, installation is default (netinst) too. -- Package-specific info: ** Version: Linux version 3.2.0-2-686-pae (Debian 3.2.18-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 SMP Mon May 21 18:24:12 UTC 2012 ** Command line: root=UUID=7f4ef707-a7d8-4c30-9932-421bc2ef6b54 ro console=hvc0 quiet -- quiet console=hvc0 ** Not tainted ** Kernel log: [0.038070] installing Xen timer for CPU 7 [0.004000] Initializing CPU#7 [0.038193] NMI watchdog disabled (cpu7): hardware events not enabled [0.038212] Brought up 8 CPUs [0.038322] devtmpfs: initialized [0.038322] Grant table initialized [0.038322] print_constraints: dummy: [0.038322] NET: Registered protocol family 16 [0.344043] SMP alternatives: switching to UP code [0.362591] PCI: setting up Xen PCI frontend stub [0.362594] PCI: pci_cache_line_size set to 64 bytes [0.363041] bio: create slab bio-0 at 0 [0.363092] ACPI: Interpreter disabled. [0.363109] xen/balloon: Initialising balloon driver. [0.377597] xen-balloon: Initialising balloon driver. [0.377597] vgaarb: loaded [0.377597] PCI: System does not support PCI [0.377597] PCI: System does not support PCI [0.377597] Switching to clocksource xen [0.377597] pnp: PnP ACPI: disabled [0.377597] PnPBIOS: Disabled [0.378807] PCI: max bus depth: 0 pci_try_num: 1 [0.378834] NET: Registered protocol family 2 [0.378876] IP route cache hash table entries: 32768 (order: 5, 131072 bytes) [0.379015] TCP established hash table entries: 131072 (order: 8, 1048576 bytes) [0.379244] TCP bind hash table entries: 65536 (order: 7, 524288 bytes) [0.379346] TCP: Hash tables configured (established 131072 bind 65536) [0.379348] TCP reno registered [0.379350] UDP hash table entries: 512 (order: 2, 16384 bytes) [0.379356] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [0.379414] NET: Registered protocol family 1 [0.379420] PCI: CLS 0 bytes, default 64 [0.379451] Unpacking initramfs... [0.425522] Freeing initrd memory: 23440k freed [0.428807] platform rtc_cmos: registered platform RTC device (no PNP device found) [0.428991] audit: initializing netlink socket (disabled) [0.429000] type=2000 audit(1338378007.137:1): initialized [0.449369] highmem bounce pool size: 64 pages [0.449374] HugeTLB registered 2 MB page size, pre-allocated 0 pages [0.449469] VFS: Disk quotas dquot_6.5.2 [0.449495] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [0.449551] msgmni has been set to 1296 [0.449671] alg: No test for stdrng (krng) [0.449689] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [0.449692] io scheduler noop registered [0.449693] io scheduler deadline registered [0.449699] io scheduler cfq registered (default) [0.449743] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [0.449764] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [0.449766] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.449856] isapnp: Scanning for PnP cards... [0.801949] isapnp: No Plug Play device found [0.802193] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [0.802432] Linux agpgart interface v0.103 [0.802539] i8042: PNP: No PS/2 controller found. Probing ports directly. [0.803350] i8042: No controller found [0.803404] mousedev: PS/2 mouse device common for all mice [0.843197] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [0.843230] rtc_cmos: probe of rtc_cmos failed with error -38 [0.843389] TCP cubic registered [0.843406] NET: Registered protocol family 10 [0.843758] Mobile IPv6 [0.843760] NET: Registered protocol family 17 [0.843764] Registering the dns_resolver key type [0.843776] Using IPI No-Shortcut mode [0.843853] PM: Hibernation image not present or could not be loaded. [0.843861] registered taskstats version 1 [0.843886] XENBUS: Device with no driver: device/vbd/51712 [0.843888] XENBUS: Device with no driver: device/vif/0 [0.843898] /build/buildd-linux-2.6_3.2.18-1-i386-rwdM7y/linux-2.6-3.2.18/debian/build/source_i386_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [0.843929] Initializing network drop monitor service [0.844180] Freeing unused kernel memory: 412k freed [0.844923] Write protecting the kernel text: 2844k [0.845190] Write protecting the kernel read-only data: 1112k [0.845192] NX-protecting the kernel data: 3300k [0.878430] udevd[88]: starting version 175 [0.903142] Initialising Xen virtual ethernet driver. [0.919416] blkfront: xvda: barrier or flush: disabled [0.920670] xvda: xvda1 xvda2 xvda5 [1.078589] PM: Starting manual resume from disk [
Bug#675190: BUG: unable to handle kernel paging request at 27c97000 during reboot under xen
On 30.05.2012 17:31, Ben Hutchings wrote: A log of the crash would be useful. oops, sorry, forgot to attach. Here: [ ok ] Deactivating swap...done. [info] Will now restart. [ 280.608079] WARNING: g.e. still in use! [ 280.608088] WARNING: g.e. still in use! [ 280.608104] sysfs: kobject eth0 without dirent [ 280.608220] sysfs: kobject eth0 without dirent [ 280.608316] sysfs: kobject eth0 without dirent [ 280.608438] BUG: unable to handle kernel paging request at 27c97000 [ 280.608448] IP: [c1229e86] linkwatch_do_dev+0x8e/0x94 [ 280.608460] *pdpt = 02a8a027 *pde = [ 280.608470] Oops: 0002 [#1] SMP [ 280.608476] Modules linked in: fuse btrfs crc32c libcrc32c zlib_deflate ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs ext4 crc16 jbd2 ext2 dm_mod nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop evdev snd_pcm snd_page_alloc snd_timer snd soundcore pcspkr ext3 mbcache jbd xen_blkfront xen_netfront [ 280.608088] WARNING: g.e. still in use! [ 280.608104] sysfs: kobject eth0 without dirent [ 280.608220] sysfs: kobject eth0 without dirent [ 280.608316] sysfs: kobject eth0 without dirent [ 280.608438] BUG: unable to handle kernel paging request at 27c97000 [ 280.608448] IP: [c1229e86] linkwatch_do_dev+0x8e/0x94 [ 280.608460] *pdpt = 02a8a027 *pde = [ 280.608470] Oops: 0002 [#1] SMP [ 280.608476] Modules linked in: fuse btrfs crc32c libcrc32c zlib_deflate ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs ext4 crc16 jbd2 ext2 dm_mod nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop evdev snd_pcm snd_page_alloc snd_timer snd soundcore pcspkr ext3 mbcache jbd xen_blkfront xen_netfront [ 280.608526] [ 280.608530] Pid: 60, comm: kworker/0:1 Tainted: GW 3.2.0-2-686-pae #1 [ 280.608538] EIP: 0061:[c1229e86] EFLAGS: 00010246 CPU: 0 [ 280.608544] EIP is at linkwatch_do_dev+0x8e/0x94 [ 280.608548] EAX: EBX: c2958000 ECX: c295826c EDX: e8d1 [ 280.608554] ESI: EDI: c2958000 EBP: e8d11f68 ESP: e8d11f5c [ 280.608559] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069 [ 280.608565] Process kworker/0:1 (pid: 60, ti=e8d1 task=e8d05620 task.ti=e8d1) [ 280.608572] Stack: [ 280.608575] e8d11f02 c295826c c122a0c3 e8d11f68 e8d11f68 e8c9bdc0 c140ff8c e91165c0 [ 280.608587] e91166c0 c122a110 c1049aef e911b400 c122a0f8 e911b405 e8c9bdc0 [ 280.608598] e91165c0 e8c9bdd0 e8d05620 c104a7fa e8c9bdd0 e8c71f34 e8c9bdc0 c104a751 [ 280.608609] Call Trace: [ 280.608614] [c122a0c3] ? __linkwatch_run_queue+0xe2/0x117 [ 280.608621] [c122a110] ? linkwatch_event+0x18/0x1d [ 280.608628] [c1049aef] ? process_one_work+0x112/0x1fa [ 280.608634] [c122a0f8] ? __linkwatch_run_queue+0x117/0x117 [ 280.608641] [c104a7fa] ? worker_thread+0xa9/0x122 [ 280.608648] [c104a751] ? manage_workers.isra.23+0x13d/0x13d [ 280.608654] [c104d13b] ? kthread+0x63/0x68 [ 280.608660] [c104d0d8] ? kthread_worker_fn+0x101/0x101 [ 280.608667] [c12c5c7e] ? kernel_thread_helper+0x6/0x10 [ 280.608672] Code: f6 83 ec 00 00 00 01 74 1c 8b 43 44 a8 04 89 d8 75 07 e8 b5 7b 00 00 eb 05 e8 99 7d 00 00 89 d8 e8 24 47 ff ff 8b 83 58 02 00 00 64 ff 08 58 5b c3 56 31 d2 53 8b 48 44 80 e1 04 75 29 8b 98 04 [ 280.608729] EIP: [c1229e86] linkwatch_do_dev+0x8e/0x94 SS:ESP 0069:e8d11f5c [ 280.608737] CR2: 27c97000 [ 280.608747] ---[ end trace e490ba182b5fd8cc ]--- [ 280.608774] BUG: unable to handle kernel paging request at fffc [ 280.608781] IP: [c104d2da] kthread_data+0x6/0xa [ 280.608788] *pdpt = 02405027 *pde = [ 280.608796] Oops: [#2] SMP [ 280.608800] Modules linked in: fuse btrfs crc32c libcrc32c zlib_deflate ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs ext4 crc16 jbd2 ext2 dm_mod nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop evdev snd_pcm snd_page_alloc snd_timer snd soundcore pcspkr ext3 mbcache jbd xen_blkfront xen_netfront [ 280.608848] [ 280.608852] Pid: 60, comm: kworker/0:1 Tainted: G D W 3.2.0-2-686-pae #1 [ 280.608861] EIP: 0061:[c104d2da] EFLAGS: 00010002 CPU: 0 [ 280.608867] EIP is at kthread_data+0x6/0xa [ 280.608871] EAX: EBX: e8d057d0 ECX: e911aa04 EDX: [ 280.608877] ESI: EDI: e8d05754 EBP: e8d05620 ESP: e8d11dac [ 280.608883] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069 [ 280.608889] Process kworker/0:1 (pid: 60, ti=e8d1 task=e8d05620 task.ti=e8d1) [ 280.608896] Stack: [ 280.608899] c104aabb e8d057d0 e911a9c0 e8d05754 c12bfa76 e8d11def 000d c13762b7 [ 280.608910] 003c c14839c0 e8d057d0 c14839c0 0001baec e8ce7da4 c105d519 [ 280.608921] e8d60580 e8c00040 e8d60580 c107a6fd c107aee1 e8d05620 e8d05620 [ 280.608933] Call Trace: [ 280.608938] [c104aabb] ? wq_worker_sleeping+0xa/0x5d [ 280.608944] [c12bfa76] ? __schedule+0x101/0x55b [ 280.608950] [c105d519] ? arch_local_irq_disable+0x6/0x7 [ 280.608957]
Bug#675050: xcp-xapi: /usr/lib/xcp/lib/bin/xe-edit-bootloader uses wrong path to the 'xe'
Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream Builin utility for lowlevel vm boot repairment xe-edit-bootloader contains wrong path to xe. IS: XE=/usr/lib/xcp/bin/xe MUST BE: XE=/usr/bin/xe -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xapi depends on: ii hwdata 0.233-1 ii libc6 2.13-32 ii libpam0g 1.1.3-7.1 ii libuuid1 2.20.1-5 ii libvhd02.0.90-1 ii libxen-4.1 4.1.2-6 ii libxenstore3.0 4.1.2-6 ii lsb-base 4.1+Debian4 ii pciutils 1:3.1.9-3 ii python 2.7.2-10 ii python-xenapi 1.3.2-6 ii stunnel4 [stunnel] 3:4.52-1 ii xcp-eliloader 0.1-4 ii xcp-fe 0.5.2-3+b1 ii xcp-networkd 1.3.2-6 ii xcp-squeezed 1.3.2-6 ii xcp-storage-managers 0.1.1-2 ii xcp-v6d1.3.2-6 ii xcp-xe 1.3.2-6 ii xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1] 4.1.2-6 ii xen-utils-4.1 4.1.2-6 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages xcp-xapi recommends: ii cifs-utils 2:5.4-2 ii xcp-guest-templates 0.1-3 ii xcp-vncterm 0.1-2 xcp-xapi suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675052: xcp-xapi: xe vm-memory-target-set does not write target to xenstore
Package: xcp-xapi Version: 1.3.2-6 Severity: important Tags: upstream xe vm-memory-target-set does not write new target to /local/domain/ID/memory/target. Balloon in guest domain is expecting this value to be changed to do selfballooning. This breaks 'dynamic memory control' feature. Steps to reproduce: 1) Setup any PV virtual machine with static-memory-min static-memory-max 2) Run it 3) change value of memory target via xe vm-memory-target-set Expected behavior: xenstore /local/domain/X/memory/target set to passed value Actual behavior: no changes in xenstore (compare to boot time values) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xapi depends on: ii hwdata 0.233-1 ii libc6 2.13-32 ii libpam0g 1.1.3-7.1 ii libuuid1 2.20.1-5 ii libvhd02.0.90-1 ii libxen-4.1 4.1.2-6 ii libxenstore3.0 4.1.2-6 ii lsb-base 4.1+Debian4 ii pciutils 1:3.1.9-3 ii python 2.7.2-10 ii python-xenapi 1.3.2-6 ii stunnel4 [stunnel] 3:4.52-1 ii xcp-eliloader 0.1-4 ii xcp-fe 0.5.2-3+b1 ii xcp-networkd 1.3.2-6 ii xcp-squeezed 1.3.2-6 ii xcp-storage-managers 0.1.1-2 ii xcp-v6d1.3.2-6 ii xcp-xe 1.3.2-6 ii xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1] 4.1.2-6 ii xen-utils-4.1 4.1.2-6 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages xcp-xapi recommends: ii cifs-utils 2:5.4-2 ii xcp-guest-templates 0.1-3 ii xcp-vncterm 0.1-2 xcp-xapi suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675055: xcp-xapi: xe-edit-bootloader does not compatible with new /dev/sm
Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream /usr/lib/xcp/bin/xe-edit-bootloader failing with following message: /usr/lib/xcp/bin/xe-edit-bootloader -u 19f66083-e776-70d1-1808-3712688ad138 Creating dom0 VBD: 0fdb952e-92ff-4b53-dd49-8d54b2268787 Plugging VBD: Waiting for /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e0: . done Mounting filesystem: failed Partitions in the VDI are: brw--- 1 root root 252, 0 May 29 19:13 /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e0 You can use the -p option to specify a partition number to mount. Unplugging VBD: . done root@lab-xh3:~# /usr/lib/xcp/bin/xe-edit-bootloader -u 19f66083-e776-70d1-1808-3712688ad138 -p 1 Creating dom0 VBD: 445a1179-a947-b884-8cbe-06ea1515ee38 Plugging VBD: Waiting for /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e01: .Device /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e01 not found. Reason is that older model creates /dev/xvd* devices (see message history for bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674088 ) and xe-edit-bootloader just add partition number to device (/dev/xvdb - /dev/xvdb1). With new sm model this is not true: script must call kpartx to probe partition table of attached VDI. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xapi depends on: ii hwdata 0.233-1 ii libc6 2.13-32 ii libpam0g 1.1.3-7.1 ii libuuid1 2.20.1-5 ii libvhd02.0.90-1 ii libxen-4.1 4.1.2-6 ii libxenstore3.0 4.1.2-6 ii lsb-base 4.1+Debian4 ii pciutils 1:3.1.9-3 ii python 2.7.2-10 ii python-xenapi 1.3.2-6 ii stunnel4 [stunnel] 3:4.52-1 ii xcp-eliloader 0.1-4 ii xcp-fe 0.5.2-3+b1 ii xcp-networkd 1.3.2-6 ii xcp-squeezed 1.3.2-6 ii xcp-storage-managers 0.1.1-2 ii xcp-v6d1.3.2-6 ii xcp-xe 1.3.2-6 ii xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1] 4.1.2-6 ii xen-utils-4.1 4.1.2-6 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages xcp-xapi recommends: ii cifs-utils 2:5.4-2 ii xcp-guest-templates 0.1-3 ii xcp-vncterm 0.1-2 xcp-xapi suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674161: [Xen-API] Bug#674161: xcp-xapi: 'the device disappeared from xenstore' message during vbd-plug (vm-start)
On 23.05.2012 23:24, George Shuklin wrote: On 23.05.2012 22:44, Dave Scott wrote: xenstore-write /local/domain/0/vm hello Yes, it plugged successfully (at least no error messages). I saw that code in device.ml (where exception was raised), it seems be checking that path in xenstore: (* Sanity check: ensure the backend domain exists *) let _ = try let (_: string) = t.Xst.read (sprintf /local/domain/%d/vm device.backend.domid) in () with Xenbus.Xb.Noent - raise (Device_backend_vanished device) in But even I was successfull, I unable to perform any IO in guest domain (I've get into initrd but I see no /dev/xvd* devices and no messages in dmesg related to new device). I was wrong about this. Workaround 'xenstore-write /local/domain/0/vm something' works and new device is available in guest domain. There is a separate problem with networking I'll report separately. Now but description is looking like this: xcp-xapi package does not write dom0 uuid in xenstore upon startup. This prevents normal device initialization. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674161: xcp-xapi: 'the device disappeared from xenstore' message during vbd-plug (vm-start)
Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream vbd plug to PV domain cause following error: The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd | devid=51760)) (same error occur during normal vm installation/running, but this is too long way and I cut some edges by creating a 'diskless' VM, wich just boot and stops inside in initramfs). Operation log: (preparation - not related to bug) # mkdir /boot/guest # cp /boot/vmlinuz-3.2.0-2-amd64 /boot/initrd.img-3.2.0-2-amd64 /boot/guest/ #(prepare external kernels) # xe vm-install template=Other\ install\ media new-name-label=raw 8a6f56a7-3511-650e-d14b-4dd2a3d9c75d # export vm=8a6f56a7-3511-650e-d14b-4dd2a3d9c75d # xe vm-param-set uuid=$vm HVM-boot-policy= #(disable HVM mode == switch to PV) # xe vm-param-set uuid=$vm PV-bootloader= #(disable eliloader/pygrub - use external kernel) # xe vm-param-set uuid=$vm PV-kernel=/boot/guest/vmlinuz-3.2.0-2-amd64 # xe vm-param-set uuid=$vm PV-ramdisk=/boot/guest/initrd.img-3.2.0-2-amd64 # xe vm-param-set uuid=$vm PV-args=root=/ #(kerel cmdline - to go to initrd) # xe vm-start uuid=$vm (now we got clean vm without network or block devices and we can easily repeat but conditions) # xe sr-create type=file name-label=fileSR device-config:location=/mnt 319f3eaa-d1ba-a81d-acb3-493ecbdaab17 #xe vdi-create type=user virtual-size=2GiB name-label=test sr-uuid=319f3eaa-d1ba-a81d-acb3-493ecbdaab17 8cc62479-e620-4561-a057-2eff0e0b8f8d here bug part starts: xe vbd-create vm-uuid=8a6f56a7-3511-650e-d14b-4dd2a3d9c75d vdi-uuid=8cc62479-e620-4561-a057-2eff0e0b8f8d device=0 716880c9-d6cb-44a8-e5cd-6a68f708c1f9 root@lab-xh3:~# xe vbd-plug uuid=716880c9-d6cb-44a8-e5cd-6a68f708c1f9 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=2 | kind=vbd | devid=51712); backend (domid=0 | kind=vbd | devid=51712)) Log file content: [20120523T14:00:23.276Z| info|lab-xh3|74 UNIX /var/lib/xcp/xapi||cli] xe vbd-plug uuid=716880c9-d6cb-44a8-e5cd-6a68f708c1f9 username=root password=null [20120523T14:00:23.278Z| info|lab-xh3|74 UNIX /var/lib/xcp/xapi|session.login_with_password D:0661f1729b93|xapi] Session.create trackid=094bbc269cc3c3ff4fe8b0faadef2ef1 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120523T14:00:23.278Z|debug|lab-xh3|74 UNIX /var/lib/xcp/xapi|session.login_with_password D:0661f1729b93|xapi] Attempting to open /var/lib/xcp/xapi [20120523T14:00:23.279Z|debug|lab-xh3|75 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:f3e45d1e1222 created by task D:0661f1729b93 [20120523T14:00:23.285Z|debug|lab-xh3|74 UNIX /var/lib/xcp/xapi|VBD.plug R:4b5db3df62d8|audit] VBD.plug: VBD = '716880c9-d6cb-44a8-e5cd-6a68f708c1f9' [20120523T14:00:23.289Z|debug|lab-xh3|74 UNIX /var/lib/xcp/xapi|VBD.plug R:4b5db3df62d8|locking_helpers] Acquired lock on VM OpaqueRef:714e30c2-f627-1df7-db85-f543eccca324 with token 3 [20120523T14:00:23.289Z|debug|lab-xh3|74 UNIX /var/lib/xcp/xapi|VBD.plug R:4b5db3df62d8|xapi] vbd_plug: attempting to attach vbd [20120523T14:00:23.289Z|debug|lab-xh3|74 UNIX /var/lib/xcp/xapi|VBD.plug R:4b5db3df62d8|xapi] Attempting to dynamically attach VBD to domid 2 [20120523T14:00:23.290Z|debug|lab-xh3|74 UNIX /var/lib/xcp/xapi|VBD.plug R:4b5db3df62d8|xapi] VBD device name 0 interpreted as Xen(0, 0) (hvm = false) [20120523T14:00:23.290Z|debug|lab-xh3|74 UNIX /var/lib/xcp/xapi|VBD.plug R:4b5db3df62d8|sm] SM file sr_content_type sr=OpaqueRef:90cbfca8-ffca-554a-4809-d85a71dd826c [20120523T14:00:23.292Z| info|lab-xh3|74 UNIX /var/lib/xcp/xapi|sm_exec D:e2722ffdc310|xapi] Session.create trackid=d1fe239f7a7942262e1e1b0d73c8f9dc pool=false uname= is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120523T14:00:23.293Z|debug|lab-xh3|74 UNIX /var/lib/xcp/xapi|sm_exec D:e2722ffdc310|xapi] Attempting to open /var/lib/xcp/xapi [20120523T14:00:23.293Z|debug|lab-xh3|76 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:ca1bcfee9e48 created by task D:e2722ffdc310 [20120523T14:00:23.374Z|debug|lab-xh3|77 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:host.get_other_config D:f8b4e61f4b2d created by task R:4b5db3df62d8 [20120523T14:00:23.376Z|debug|lab-xh3|77 UNIX /var/lib/xcp/xapi||http_critical] Premature termination of connection! [20120523T14:00:23.382Z| info|lab-xh3|74 UNIX /var/lib/xcp/xapi|sm_exec D:e2722ffdc310|xapi] Session.destroy trackid=d1fe239f7a7942262e1e1b0d73c8f9dc [20120523T14:00:23.383Z| info|lab-xh3|74 UNIX /var/lib/xcp/xapi|VBD.plug R:4b5db3df62d8|storage_impl] VDI.attach
Bug#674161: Acknowledgement (xcp-xapi: 'the device disappeared from xenstore' message during vbd-plug (vm-start))
Found same problem with vif: xe vif-plug uuid=08e34a92-a973-e61d-1d41-2165a3d51073 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=5 | kind=vif | devid=0); backend (domid=0 | kind=vif | devid=0)) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674161: [Xen-API] Bug#674161: xcp-xapi: 'the device disappeared from xenstore' message during vbd-plug (vm-start)
Some more data: Done clean reinstall (now with i386 in dom0), got exactly same error. After some digging around got this (new uuids, same problem): Key logs entries: [20120523T17:50:08.602Z|debug|lab-xh3|249 UNIX /var/lib/xcp/xapi|VM.start R:1c6c2941c565|xenops] Device.Vbd.add (device_number=Xen(0, 0) | params=/dev/sm/backend/357e7a73-ec60-6ae6-fe0d-56ca87d228b2/741cb833-b2c3-4bf7-b724-1295e984f097 | phystype=vhd) [20120523T17:50:08.602Z|debug|lab-xh3|249 UNIX /var/lib/xcp/xapi|VM.start R:1c6c2941c565|xenops] adding device B0[/local/domain/0/backend/vbd/4/51712] F4[/local/domain/4/device/vbd/51712] H[/xapi/4/hotplug/vbd/51712] [20120523T17:50:08.603Z|debug|lab-xh3|249 UNIX /var/lib/xcp/xapi|VM.start R:1c6c2941c565|backtrace] Raised at device.ml:65.10-42 - xst.ml:52.18-23 - xst.ml:55.9-12 - device.ml:497.1-60 - vbdops.ml:102.37-229 - storage_access.ml:516.14-317 - xapi_xenops_errors.ml:79.4-8 [20120523T17:50:08.603Z|debug|lab-xh3|249 UNIX /var/lib/xcp/xapi|VM.start R:1c6c2941c565|xapi] Converting xenops exception (INTERNAL_ERROR: [ Device_common.Device_backend_vanished(_) ]) into nice API internal error I've checked - when I plug vbd to dom0 it works fine, but I can't do it with other domains. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674161: [Pkg-xen-devel] Bug#674161: [Xen-API] Bug#674161: xcp-xapi: 'the device disappeared from xenstore' message during vbd-plug (vm-start)
On 23.05.2012 22:46, Mike McClurg wrote:
On Wed, May 23, 2012 at 7:10 PM, George Shuklin
george.shuk...@gmail.com wrote:
Some more data:
Done clean reinstall (now with i386 in dom0), got exactly same error.
What SR type are you using? If you are using something other than the
FileSr, can you also attach SMlog from the relevant time period?
Mike
SM is 'file'. SMLog seems be so clean I've thought it is not relevant.
But anyway here it is:
[11241] 2012-05-23 22:54:56.348313 SUCCESS
[11241] 2012-05-23 22:54:56.349302 vdi_attach {'sr_uuid':
'357e7a73-ec60-6ae6-fe0d-56ca87d228b2', 'subtask_of':
'DummyRef:|75bad4bb-a459-1750-e4df-bffd787db49a|VDI.attach', 'vdi_ref':
'OpaqueRef:e893c151-fca2-c408-81be-e0c06fef0139', 'vdi_on_boot':
'persist', 'args': ['true'], 'vdi_location':
'00048fc5-9764-408a-801d-9d9442974c9d', 'host_ref':
'OpaqueRef:2e64a8c9-81be-f152-503b-200861cff9e6', 'session_ref':
'OpaqueRef:546b5c70-209a-8a95-1bfe-b3d268256f8e', 'device_config':
{'SRmaster': 'true', 'location': '/mnt'}, 'command': 'vdi_attach',
'vdi_allow_caching': 'false', 'sr_ref':
'OpaqueRef:ee16513a-2dd5-0306-6ad6-73d9ef2a958d', 'vdi_uuid':
'00048fc5-9764-408a-801d-9d9442974c9d'}
[11241] 2012-05-23 22:54:56.349595 lock: creating lock file
/var/lock/sm/00048fc5-9764-408a-801d-9d9442974c9d/vdi
[11241] 2012-05-23 22:54:56.349816 lock: closed
/var/lock/sm/00048fc5-9764-408a-801d-9d9442974c9d/vdi
[11241] 2012-05-23 22:54:56.349934 lock: released
/var/lock/sm/357e7a73-ec60-6ae6-fe0d-56ca87d228b2/sr
[11241] 2012-05-23 22:54:56.350233 lock: closed
/var/lock/sm/357e7a73-ec60-6ae6-fe0d-56ca87d228b2/sr
[11247] 2012-05-23 22:54:56.439703 lock: acquired
/var/lock/sm/357e7a73-ec60-6ae6-fe0d-56ca87d228b2/sr
[11247] 2012-05-23 22:54:56.439853 ['/usr/sbin/td-util', 'query',
'vhd', '-vpf', '/mnt/00048fc5-9764-408a-801d-9d9442974c9d.vhd']
[11247] 2012-05-23 22:54:56.444958 SUCCESS
[11247] 2012-05-23 22:54:56.445908 lock: released
/var/lock/sm/357e7a73-ec60-6ae6-fe0d-56ca87d228b2/sr
[11247] 2012-05-23 22:54:56.446066 vdi_activate {'sr_uuid':
'357e7a73-ec60-6ae6-fe0d-56ca87d228b2', 'subtask_of':
'DummyRef:|722c4aac-53a1-f480-cb35-4278ae467486|VDI.activate',
'vdi_ref': 'OpaqueRef:e893c151-fca2-c408-81be-e0c06fef0139',
'vdi_on_boot': 'persist', 'args': ['true'], 'vdi_location':
'00048fc5-9764-408a-801d-9d9442974c9d', 'host_ref':
'OpaqueRef:2e64a8c9-81be-f152-503b-200861cff9e6', 'session_ref':
'OpaqueRef:87181fc8-c932-7929-240b-7a2595b8b11f', 'device_config':
{'SRmaster': 'true', 'location': '/mnt'}, 'command': 'vdi_activate',
'vdi_allow_caching': 'false', 'sr_ref':
'OpaqueRef:ee16513a-2dd5-0306-6ad6-73d9ef2a958d', 'vdi_uuid':
'00048fc5-9764-408a-801d-9d9442974c9d'}
[11247] 2012-05-23 22:54:56.446328 blktap2.activate
[11247] 2012-05-23 22:54:56.446418 lock: acquired
/var/lock/sm/00048fc5-9764-408a-801d-9d9442974c9d/vdi
[11247] 2012-05-23 22:54:56.446512 Adding tag to:
00048fc5-9764-408a-801d-9d9442974c9d
[11247] 2012-05-23 22:54:56.460867 Activate lock succeeded
[11247] 2012-05-23 22:54:56.494658 ['/usr/sbin/td-util', 'query',
'vhd', '-vpf', '/mnt/00048fc5-9764-408a-801d-9d9442974c9d.vhd']
[11247] 2012-05-23 22:54:56.499583 SUCCESS
[11247] 2012-05-23 22:54:56.532880
PhyLink(/dev/sm/phy/357e7a73-ec60-6ae6-fe0d-56ca87d228b2/00048fc5-9764-408a-801d-9d9442974c9d)
- /mnt/00048fc5-9764-408a-801d-9d9442974c9d.vhd
[11247] 2012-05-23 22:54:56.537025 ['/usr/sbin/tap-ctl', 'allocate']
[11247] 2012-05-23 22:54:56.540947 = 0
[11247] 2012-05-23 22:54:56.545753 ['/usr/sbin/tap-ctl', 'spawn']
[11247] 2012-05-23 22:54:56.551907 = 0
[11247] 2012-05-23 22:54:56.552088 ['/usr/sbin/tap-ctl', 'attach',
'-p', '11282', '-m', '0']
[11247] 2012-05-23 22:54:56.556115 = 0
[11247] 2012-05-23 22:54:56.556339 ['/usr/sbin/tap-ctl', 'open',
'-p', '11282', '-m', '0', '-a',
'vhd:/mnt/00048fc5-9764-408a-801d-9d9442974c9d.vhd']
[11247] 2012-05-23 22:54:56.577555 = 0
[11247] 2012-05-23 22:54:56.582410 tap.activate: Launched
Tapdisk(vhd:/mnt/00048fc5-9764-408a-801d-9d9442974c9d.vhd, pid=11282,
minor=0, state=R)
[11247] 2012-05-23 22:54:56.582743
DeviceNode(/dev/sm/backend/357e7a73-ec60-6ae6-fe0d-56ca87d228b2/00048fc5-9764-408a-801d-9d9442974c9d)
- /dev/xen/blktap-2/tapdev0
[11247] 2012-05-23 22:54:56.583023 lock: released
/var/lock/sm/00048fc5-9764-408a-801d-9d9442974c9d/vdi
[11247] 2012-05-23 22:54:56.583125 lock: closed
/var/lock/sm/00048fc5-9764-408a-801d-9d9442974c9d/vdi
[11247] 2012-05-23 22:54:56.583289 lock: closed
/var/lock/sm/357e7a73-ec60-6ae6-fe0d-56ca87d228b2/sr
[11247] 2012-05-23 22:54:56.583770 lock: closed
/var/lock/sm/357e7a73-ec60-6ae6-fe0d-56ca87d228b2/sr
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674161: [Xen-API] Bug#674161: xcp-xapi: 'the device disappeared from xenstore' message during vbd-plug (vm-start)
On 23.05.2012 22:44, Dave Scott wrote: xenstore-write /local/domain/0/vm hello Yes, it plugged successfully (at least no error messages). I saw that code in device.ml (where exception was raised), it seems be checking that path in xenstore: (* Sanity check: ensure the backend domain exists *) let _ = try let (_: string) = t.Xst.read (sprintf /local/domain/%d/vm device.backend.domid) in () with Xenbus.Xb.Noent - raise (Device_backend_vanished device) in But even I was successfull, I unable to perform any IO in guest domain (I've get into initrd but I see no /dev/xvd* devices and no messages in dmesg related to new device). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674161: [Pkg-xen-devel] Bug#674161: xcp-xapi: 'the device disappeared from xenstore' message during vbd-plug (vm-start)
On 23.05.2012 19:28, Mike McClurg wrote: vbd plug to PV domain cause following error: The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd | devid=51760)) snip # xe sr-create type=file name-label=fileSR device-config:location=/mnt 319f3eaa-d1ba-a81d-acb3-493ecbdaab17 Here's the problem. The SR type file doesn't work the way you'd want it to. It's actually the base class for the ext and NFS backends, and isn't meant to be accessed directly. This class doesn't actually have the create methods required to actually create the appropriate directories necessary for a file-based SR. Could you please try to reproduce this bug with a different backend? NFS would probably be easiest. If the VBD plug happens on a different SR type, then I'll consider this a bug. Mike PS: As an aside, it should be possible to manually create an SR of this type yourself (or so the storage team leads me to believe). If you create a fresh uuid using uuidgen, you can then create a directory called /var/run/sm/new uuid, and then call 'xe sr-introduce type=file uuid=new uuid name-label=name'. I haven't tried this yet, but I'm about to. Ok, i've done it with nfs SM. xe vbd-plug uuid=605c8d8b-b91d-bca8-4df2-ee1b6ee3cf31 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=1 | kind=vbd | devid=51712); backend (domid=0 | kind=vbd | devid=51712)) After do manual 'xenstore-write /local/domain/0/vm hello' vbd-plug does not return error, but disk does not appear in guest domain (and no messages in dmesg of guest). Not in 'initrd' stage, not in debian netinst installer. But at least I see it (vdi) in /dev/sm: ls -la /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/651d7a25-d702-47dd-aa01-0469dec75c2a brw--- 1 root root 252, 0 May 24 01:50 /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/651d7a25-d702-47dd-aa01-0469dec75c2a here cut from xcp-xapi.log: [20120523T21:55:32.346Z| info|lab-xh3|370 UNIX /var/lib/xcp/xapi||cli] xe vbd-plug uuid=605c8d8b-b91d-bca8-4df2-ee1b6ee3cf31 username=root password=null [20120523T21:55:32.348Z| info|lab-xh3|370 UNIX /var/lib/xcp/xapi|session.login_with_password D:e241022d2c76|xapi] Session.create trackid=9ffe2bef6f34023ee4bdc35a2f2b9195 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120523T21:55:32.349Z|debug|lab-xh3|370 UNIX /var/lib/xcp/xapi|session.login_with_password D:e241022d2c76|xapi] Attempting to open /var/lib/xcp/xapi [20120523T21:55:32.350Z|debug|lab-xh3|371 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:52c338ab77c1 created by task D:e241022d2c76 [20120523T21:55:32.356Z|debug|lab-xh3|370 UNIX /var/lib/xcp/xapi|VBD.plug R:fc05dc0cbc95|audit] VBD.plug: VBD = '605c8d8b-b91d-bca8-4df2-ee1b6ee3cf31' [20120523T21:55:32.360Z|debug|lab-xh3|370 UNIX /var/lib/xcp/xapi|VBD.plug R:fc05dc0cbc95|locking_helpers] Acquired lock on VM OpaqueRef:39e6d669-5b1d-c589-1ea7-82f668c8bea4 with token 5 [20120523T21:55:32.360Z|debug|lab-xh3|370 UNIX /var/lib/xcp/xapi|VBD.plug R:fc05dc0cbc95|xapi] vbd_plug: attempting to attach vbd [20120523T21:55:32.360Z|debug|lab-xh3|370 UNIX /var/lib/xcp/xapi|VBD.plug R:fc05dc0cbc95|xapi] Attempting to dynamically attach VBD to domid 1 [20120523T21:55:32.361Z|debug|lab-xh3|370 UNIX /var/lib/xcp/xapi|VBD.plug R:fc05dc0cbc95|xapi] VBD device name 0 interpreted as Xen(0, 0) (hvm = false) [20120523T21:55:32.361Z| info|lab-xh3|370 UNIX /var/lib/xcp/xapi|VBD.plug R:fc05dc0cbc95|storage_impl] VDI.attach task:OpaqueRef:fc05dc0c-bc95-c277-1b9f-041d6d3a0d76 dp:vbd/1/0 sr:4c15ea03-5d70-938e-8265-d5424c0fda5e vdi:651d7a25-d702-47dd-aa01-0469dec75c2a read_write:true [20120523T21:55:32.361Z|debug|lab-xh3|370 UNIX /var/lib/xcp/xapi|VBD.plug R:fc05dc0cbc95|storage_impl] task:OpaqueRef:fc05dc0c-bc95-c277-1b9f-041d6d3a0d76 dp:vbd/1/0 sr:4c15ea03-5d70-938e-8265-d5424c0fda5e vdi:651d7a25-d702-47dd-aa01-0469dec75c2a superstate:activated RW [20120523T21:55:32.362Z| info|lab-xh3|370 UNIX /var/lib/xcp/xapi|VBD.plug R:fc05dc0cbc95|storage_impl] VDI.activate task:OpaqueRef:fc05dc0c-bc95-c277-1b9f-041d6d3a0d76 dp:vbd/1/0 sr:4c15ea03-5d70-938e-8265-d5424c0fda5e vdi:651d7a25-d702-47dd-aa01-0469dec75c2a [20120523T21:55:32.362Z|debug|lab-xh3|370 UNIX /var/lib/xcp/xapi|VBD.plug R:fc05dc0cbc95|storage_impl] task:OpaqueRef:fc05dc0c-bc95-c277-1b9f-041d6d3a0d76 dp:vbd/1/0 sr:4c15ea03-5d70-938e-8265-d5424c0fda5e vdi:651d7a25-d702-47dd-aa01-0469dec75c2a superstate:activated RW [20120523T21:55:32.363Z|debug|lab-xh3|370 UNIX /var/lib/xcp/xapi|VBD.plug R:fc05dc0cbc95|xenops] Device.Vbd.add (device_number=Xen(0, 0) |
Bug#674088: xcp-xapi: vbd-plug to dom0 does not creates /dev/xvd* devices in dom0
Package: xcp-xapi
Version: 1.3.2-6
Severity: normal
Tags: upstream
Normally (in 'iso-based' XCP) is possible to attach VDI to dom0.
That operation usually looks like:
xe vbd-create vdi-uuid=... vm-uuid=(dom0 uuid) device=N
xe vbd-plug
I done those steps in xcp-xapi and got success (no error), but no xvd* device
found.
Here operations log:
# xe vbd-create vdi-uuid=c95af56f-799f-49ad-a64f-82eca3299b50
vm-uuid=d859ed1a-760f-9928-b5be-f0ab1790b15f type=Disk mode=RW device=2
b2e8f7b3-34c4-fe9a-486e-6551b8ba4165
# xe vbd-plug uuid=b2e8f7b3-34c4-fe9a-486e-6551b8ba4165
# ls /dev/xv*
ls: cannot access /dev/xv*: No such file or directory
Data from different logs:
SMlog:
[12866] 2012-05-23 04:23:29.119125 vdi_activate {'sr_uuid':
'42cbc4a3-dae2-e756-d122-01b87ed871c2', 'subtask_of':
'DummyRef:|af7c4611-4409-96e2-ec06-9f4c58a8ec47|VDI.activate', 'vdi_ref':
'OpaqueRef:772f7273-f1a2-c340-89ae-43c3af049f15', 'vdi_on_boot': 'persist',
'args': ['true'], 'vdi_location': 'c95af56f-799f-49ad-a64f-82eca3299b50',
'host_ref': 'OpaqueRef:5005b228-e50d-0d6b-e4f9-8d85794ba15c', 'session_ref':
'OpaqueRef:4a336c86-82a9-1e99-f066-41015d88fec4', 'device_config': {'SRmaster':
'true', 'location': '/mnt'}, 'command': 'vdi_activate', 'vdi_allow_caching':
'false', 'sr_ref': 'OpaqueRef:a979869b-1538-51ff-39ab-3ddafc767cd2',
'vdi_uuid': 'c95af56f-799f-49ad-a64f-82eca3299b50'}
[12866] 2012-05-23 04:23:29.119394 blktap2.activate
[12866] 2012-05-23 04:23:29.119488 lock: acquired
/var/lock/sm/c95af56f-799f-49ad-a64f-82eca3299b50/vdi
[12866] 2012-05-23 04:23:29.119581 Adding tag to:
c95af56f-799f-49ad-a64f-82eca3299b50
[12866] 2012-05-23 04:23:29.133845 Activate lock succeeded
[12866] 2012-05-23 04:23:29.166975 ['/usr/sbin/td-util', 'query', 'vhd',
'-vpf', '/mnt/c95af56f-799f-49ad-a64f-82eca3299b50.vhd']
[12866] 2012-05-23 04:23:29.173445 SUCCESS
[12866] 2012-05-23 04:23:29.206198
PhyLink(/dev/sm/phy/42cbc4a3-dae2-e756-d122-01b87ed871c2/c95af56f-799f-49ad-a64f-82eca3299b50)
- /mnt/c95af56f-799f-49ad-a64f-82eca3299b50.vhd
[12866] 2012-05-23 04:23:29.212017 ['/usr/sbin/tap-ctl', 'allocate']
[12866] 2012-05-23 04:23:29.217046 = 0
[12866] 2012-05-23 04:23:29.223407 ['/usr/sbin/tap-ctl', 'spawn']
[12866] 2012-05-23 04:23:29.231105 = 0
[12866] 2012-05-23 04:23:29.231306 ['/usr/sbin/tap-ctl', 'attach', '-p',
'12901', '-m', '1']
[12866] 2012-05-23 04:23:29.236629 = 0
[12866] 2012-05-23 04:23:29.236851 ['/usr/sbin/tap-ctl', 'open', '-p',
'12901', '-m', '1', '-a', 'vhd:/mnt/c95af56f-799f-49ad-a64f-82eca3299b50.vhd']
[12866] 2012-05-23 04:23:29.245060 = 0
[12866] 2012-05-23 04:23:29.252379 tap.activate: Launched
Tapdisk(vhd:/mnt/c95af56f-799f-49ad-a64f-82eca3299b50.vhd, pid=12901, minor=1,
state=R)
[12866] 2012-05-23 04:23:29.252704
DeviceNode(/dev/sm/backend/42cbc4a3-dae2-e756-d122-01b87ed871c2/c95af56f-799f-49ad-a64f-82eca3299b50)
- /dev/xen/blktap-2/tapdev1
[12866] 2012-05-23 04:23:29.253008 lock: released
/var/lock/sm/c95af56f-799f-49ad-a64f-82eca3299b50/vdi
[12866] 2012-05-23 04:23:29.253116 lock: closed
/var/lock/sm/c95af56f-799f-49ad-a64f-82eca3299b50/vdi
[12866] 2012-05-23 04:23:29.253281 lock: closed
/var/lock/sm/42cbc4a3-dae2-e756-d122-01b87ed871c2/sr
[12866] 2012-05-23 04:23:29.253809 lock: closed
/var/lock/sm/42cbc4a3-dae2-e756-d122-01b87ed871c2/sr
xcp-xapi.log (ex. xensource.log):
[20120523T00:23:28.848Z| info|lab-xh3|1045 UNIX /var/lib/xcp/xapi||cli] xe
vbd-plug uuid=b2e8f7b3-34c4-fe9a-486e-6551b8ba4165 username=root password=null
[20120523T00:23:28.849Z| info|lab-xh3|1045 UNIX
/var/lib/xcp/xapi|session.login_with_password D:5d579e77454e|xapi]
Session.create trackid=f0c22aa371e94e4f976de937c65c5b83 pool=false uname=root
is_local_superuser=true auth_user_sid=
parent=trackid=9834f5af41c964e225f24279aefe4e49
[20120523T00:23:28.850Z|debug|lab-xh3|1045 UNIX
/var/lib/xcp/xapi|session.login_with_password D:5d579e77454e|xapi] Attempting
to open /var/lib/xcp/xapi
[20120523T00:23:28.851Z|debug|lab-xh3|1046 UNIX
/var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid
D:62a39592557b created by task D:5d579e77454e
[20120523T00:23:28.857Z|debug|lab-xh3|1045 UNIX /var/lib/xcp/xapi|VBD.plug
R:4db77abb7c5d|audit] VBD.plug: VBD = 'b2e8f7b3-34c4-fe9a-486e-6551b8ba4165'
[20120523T00:23:28.859Z|debug|lab-xh3|1045 UNIX /var/lib/xcp/xapi|VBD.plug
R:4db77abb7c5d|locking_helpers] Acquired lock on VM
OpaqueRef:1f9bb0d8-00d9-7aae-0acd-3bd17952c965 with token 19
[20120523T00:23:28.859Z|debug|lab-xh3|1045 UNIX /var/lib/xcp/xapi|VBD.plug
R:4db77abb7c5d|xapi] vbd_plug: attempting to attach vbd
[20120523T00:23:28.859Z|debug|lab-xh3|1045 UNIX /var/lib/xcp/xapi|VBD.plug
R:4db77abb7c5d|xapi] Attempting to dynamically attach VBD to domid 0
[20120523T00:23:28.859Z|debug|lab-xh3|1045 UNIX /var/lib/xcp/xapi|VBD.plug
R:4db77abb7c5d|xapi] VBD device name 2 interpreted as Xen(2, 0) (hvm = false)
Bug#671776: md/raid10 deadlock at 'Failing raid device'
On 10.05.2012 07:03, NeilBrown wrote: Fixed by commit fae8cc5ed0714953b1ad7cf86 I believe. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=fae8cc5ed From: NeilBrownne...@suse.de Date: Tue, 14 Feb 2012 00:10:10 + (+1100) Subject: md/raid10: fix handling of error on last working device in array. md/raid10: fix handling of error on last working device in array. If we get a read error on the last working device in a RAID10 which contains the target block, then we don't fail the device (which is good) but we don't abort retries, which is wrong. We end up in an infinite loop retrying the read on the one device. NeilBrown Ok, it was fixed in February and I got it in 3.2 (and I see nothing about it in fresh changelog for 3.2). Was that fix ported to 3.2 in vanilla? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
