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#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#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#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#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-rc-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-rc-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-rc-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-rc-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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661419: krusader: Crash at start with 'floating point exception' after update
Package: krusader Version: 1:2.4.0~beta1+git76+de1ea35-1 Severity: grave Justification: renders package unusable After update krusader crash with 'floater pointer exception'. Data from crashlog: Application: Krusader (krusader), signal: Floating point exception Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f9db9228760 (LWP 8471))] Thread 2 (Thread 0x7f9d9bc5b700 (LWP 8472)): #0 0x787ff8de in ?? () #1 0x7f9daec48e86 in clock_gettime () from /lib/x86_64-linux-gnu/librt.so.1 #2 0x7f9db46e7964 in ?? () from /usr/lib/libQtCore.so.4 #3 0x7f9db47a963d in ?? () from /usr/lib/libQtCore.so.4 #4 0x7f9db47a9973 in ?? () from /usr/lib/libQtCore.so.4 #5 0x7f9db47a83ec in ?? () from /usr/lib/libQtCore.so.4 #6 0x7f9db47a8495 in ?? () from /usr/lib/libQtCore.so.4 #7 0x7f9db0027672 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f9db002846d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f9db0028a99 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f9db47a8e96 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #11 0x7f9db477d492 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #12 0x7f9db477d68f in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #13 0x7f9db469530f in QThread::exec() () from /usr/lib/libQtCore.so.4 #14 0x7f9db476035f in ?? () from /usr/lib/libQtCore.so.4 #15 0x7f9db4697cf5 in ?? () from /usr/lib/libQtCore.so.4 #16 0x7f9db1956b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #17 0x7f9db395a90d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #18 0x in ?? () Thread 1 (Thread 0x7f9db9228760 (LWP 8471)): [KCrash Handler] #6 0x004578b7 in ?? () #7 0x00456e6a in ?? () #8 0x00459882 in ?? () #9 0x00459cd0 in ?? () #10 0x00463d82 in ?? () #11 0x00469d99 in ?? () #12 0x004626f7 in ?? () #13 0x7f9db38a0ead in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #14 0x004503b9 in _start () -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-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 krusader depends on: ii kdebase-runtime 4:4.6.5-1+b1 ii libc6 2.13-26 ii libgcc1 1:4.6.2-15 ii libkdecore5 4:4.6.5-2+b1 ii libkdeui5 4:4.6.5-2+b1 ii libkfile4 4:4.6.5-2+b1 ii libkhtml5 4:4.6.5-2+b1 ii libkio5 4:4.6.5-2+b1 ii libkjsapi44:4.6.5-2+b1 ii libkonq5abi1 4:4.6.5-1 ii libkparts44:4.6.5-2+b1 ii libnepomuk4 4:4.6.5-2+b1 ii libnepomukutils4 4:4.6.5-2+b1 ii libphonon44:4.6.0.0-1 ii libqt4-dbus 4:4.7.4-2 ii libqt4-network4:4.7.4-2 ii libqt4-svg4:4.7.4-2 ii libqt4-xml4:4.7.4-2 ii libqtcore44:4.7.4-2 ii libqtgui4 4:4.7.4-2 ii libsolid4 4:4.6.5-2+b1 ii libsoprano4 2.6.0+dfsg.1-4 ii libstdc++64.6.2-15 ii zlib1g1:1.2.6.dfsg-2 krusader recommends no packages. Versions of packages krusader suggests: ii arjnone ii arknone ii bzip2 1.0.6-1 ii cpio 2.11-7 ii kdiff3 | kompare | xxdiff none ii kmail none ii konsolenone ii krenamenone ii lhanone ii md5deep | cfv none ii okteta none ii p7zip 9.20.1~dfsg.1-4 ii rpmnone ii unace 1.2b-9 ii unrar 1:4.1.4-1 ii unzip 6.0-5 ii zip3.0-4 -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635235: iscsitarget-dkms: version 1.4.20 does not compile with kernel 2.6.39-2
Package: iscsitarget-dkms Version: 1.4.20.2-4 Severity: grave Justification: renders package unusable dkms does not compile iscsi-target kernel module: DKMS make.log for iscsitarget-1.4.20.2 for kernel 2.6.39-2-amd64 (x86_64) Sun Jul 24 09:14:22 MSK 2011 make: Entering directory `/usr/src/linux-headers-2.6.39-2-amd64' LD /var/lib/dkms/iscsitarget/1.4.20.2/build/built-in.o LD /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/built-in.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/tio.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/iscsi.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/nthread.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/wthread.o /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/wthread.c: In function ‘worker_thread’: /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/wthread.c:75: error: implicit declaration of function ‘copy_io_context’ make[4]: *** [/var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/wthread.o] Error 1 make[3]: *** [/var/lib/dkms/iscsitarget/1.4.20.2/build/kernel] Error 2 make[2]: *** [_module_/var/lib/dkms/iscsitarget/1.4.20.2/build] Error 2 make[1]: *** [sub-make] Error 2 make: *** [all] Error 2 make: Leaving directory `/usr/src/linux-headers-2.6.39-2-amd64' -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (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 iscsitarget-dkms depends on: ii dkms 2.2.0.2-1 Dynamic Kernel Module Support Fram ii make 3.81-8.1 An utility for Directing compilati iscsitarget-dkms recommends no packages. iscsitarget-dkms suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
