Bug#676735:
reassign 676735 libqtgstreamer-dev 0.10.2-1 reassign 676738 libqtgstreamer-dev 0.10.2-1 merge 676735 676738 affects 676735 src:kamoso src:qapt retitle 676735 QtGStreamerConfig.cmake calculates include dir as /usr/lib/include/QtGStreamer thanks This happens because QtGStreamerConfig.cmake calculates the include directory as a path relative to the path of QtGStreamerConfig.cmake, which has now changed path due to multiarch. I will prepare a fix asap. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646325: gstreamer0.10-gconf needs to replace gstreamer0.10-plugins-good
Package: gstreamer0.10-gconf Version: 0.10.30-1 Severity: serious Justification: Policy 7.6.1 E: /var/cache/apt/archives/gstreamer0.10-gconf_0.10.30-1_amd64.deb: trying to overwrite '/usr/lib/gstreamer-0.10/libgstgconfelements.so', which is also in package gstreamer0.10-plugins-good 0.10.24-1 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/3 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 gstreamer0.10-gconf depends on: ii gconf2 2.32.4-1 ii libc6 2.13-21 ii libgconf2-4 2.32.4-1 ii libglib2.0-02.28.6-1 ii libgstreamer0.10-0 0.10.35-1 gstreamer0.10-gconf recommends no packages. gstreamer0.10-gconf 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
Bug#596285: [Pkg-kde-extras] Bug#596285: kbluetooth: Please remove kbluetooth /k-a, k-i
On 09/10/2010 02:34 AM, Nobuhiro Iwamatsu wrote: Source: kbluetooth Version: 1:0.4.2-3 Severity: grave Hi, Please remove kfreebsd-i386 and kfreebsd-amd64 of kbluetooth package from unstable. This package depends bluez[0]. But bluez is a tool for Linux only. It doesn't work in kfreebsd. Moreover, bluetooth is not supported in curent kfreebsd. Best regards, Nobuhiro [0]: http://packages.qa.debian.org/b/bluez.html Hello, kbluetooth is going to be removed altogether from all architectures very soon. It is deprecated in favor of bluedevil, which is already uploaded and currently another upload offering transitional packages for kbluetooth/kdebluetooth is pending. As soon as the transitional packages are in the archive, I am going to ask for removal of src:kbluetooth. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595483: kde: KDE4 Crashes system
severity 595483 normal thanks On Sat, Sep 4, 2010 at 2:46 PM, lrhorer lrho...@fletchergeek.com wrote: Package: kde Version: KDE4 Severity: critical Justification: breaks the whole system KDE4 invariably crashes the system. This system is running on an AMD Athlon 64 x 2 processer under Debian Squeeze and kernel 2.6.32-3-amd64. The same symptoms (only worse) are also observed on a Pentium IV system running 2.6.32-trunk-686. One can log in via kdm and bring up KDE4, but sooner or later - usually within an hour or two, the system will crash hard. One then cannot reach the system via telnet, XDMCP, or from the console. Often, it will not even reply to pings. The only option is to hit the power switch. If no KDE session is active, both machines are 100% stable, up continuously for months at a time without issues. If a KDE4 session is active, then after between 30 minutes and 24 hours, the system will crash. No activity is required on the KDE session for the failure to occur, but it seems that changing window foocus often triggers an event. This is most likely due to a faulty gpu driver. I guess you are using amd's proprietary fglrx driver? I have seen such issues in the past with this driver. KDE has no way to lock the system, if a system lock happens this is a problem deep in the kernel or some of its modules. Btw, both of these kernels that you are using are out-of-date. The latest squeeze kernel is 2.6.32-5-amd64. I advise you to upgrade to this kernel and uninstall any proprietary graphics drivers. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563155: [Pkg-kde-extras] Bug#563155: partitionmanager: does not start, and several zombie processes appear
severity 563155 important thanks On Thu, Dec 31, 2009 at 2:18 PM, Jan Kusanagi janjab...@gmail.com wrote: Package: partitionmanager Version: 1.0.0-1 Severity: grave Justification: renders package unusable Upon starting partitionmanager, it asks for root password, but then the window doesn't appear, and you can see in System Activity how several zombie partitionmanager processes appear. There is one which is not zombie, if you kill it, all of them disappear. It seems like the program starts OK if you execute partitionmanager-bin, and it offers the option of not using root privileges, and therefore hard drives do not appear listed, etc. Maybe it's a bug in kdesu or something, not really partitionmanager fault... I have my own debian-liveCD made with live-helper, and same thing happens, but there's no root password there, of course. If I set one up, same problems occur.s Hi, I can see that partitionmanager produces several zombie processes, even by starting partitionmanager-bin as a user, and it looks like a Qt bug. However, it starts fine, both as a normal user and as root. For this reason, I am lowering the severity. Would it be possible for you to provide a strace log of partitionmanager when it locks up? Try running strace -f -o logfile partitionmanager-bin as root, or if it doesn't hang that way, start partitionmanager and do strace -p $pid, where $pid is the pid of the non-zombie partitionmanager-bin instance. I'd prefer the first way though. I'd also like the output of ps auxf while strace is running. Any other information is welcome too. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556627: Bug not fixed
found 556627 0.11.0-3 thanks Problems still exist in qemu 0.11.0-3... Unpacking qemu-system (from .../qemu-system_0.11.0-3_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/qemu-system_0.11.0-3_amd64.deb (--unpack): trying to overwrite '/etc/qemu-ifup', which is also in package qemu 0:0.11.0-1 Unpacking qemu-user (from .../qemu-user_0.11.0-3_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/qemu-user_0.11.0-3_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/qemu-user.1.gz', which is also in package qemu 0:0.11.0-1 dpkg-deb: subprocess paste killed by signal (Broken pipe) Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/qemu-system_0.11.0-3_amd64.deb /var/cache/apt/archives/qemu-user_0.11.0-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: dpkg: dependency problems prevent configuration of qemu: qemu depends on qemu-system; however: Package qemu-system is not installed. qemu depends on qemu-user; however: Package qemu-user is not installed. qemu depends on qemu-utils; however: Package qemu-utils is not installed. dpkg: error processing qemu (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: qemu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556627: Bug not fixed
On Wednesday 18 of November 2009 18:00:28 Aurelien Jarno wrote: notfound 556627 0.11.0-3 On Wed, Nov 18, 2009 at 02:39:58PM +0200, George Kiagiadakis wrote: found 556627 0.11.0-3 thanks Problems still exist in qemu 0.11.0-3... Unpacking qemu-system (from .../qemu-system_0.11.0-3_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/qemu-system_0.11.0-3_amd64.deb (--unpack): trying to overwrite '/etc/qemu-ifup', which is also in package qemu 0:0.11.0-1 Unpacking qemu-user (from .../qemu-user_0.11.0-3_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/qemu-user_0.11.0-3_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/qemu-user.1.gz', which is also in package qemu 0:0.11.0-1 dpkg-deb: subprocess paste killed by signal (Broken pipe) Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/qemu-system_0.11.0-3_amd64.deb /var/cache/apt/archives/qemu-user_0.11.0-3_amd64.deb qemu 0.11.0-3 does not have this file anymore, it's just that you have an old broken version (0.11.0-1) installed on your system. Try 'dpkg -i /var/cache/apt/archives/qemu_0.11.0-3_amd64.deb' and try the upgrade again after it. Alternatively remove qemu, and reinstall it after upgrading qemu-system and qemu-user. Yes, I already did that, but that didn't solve the /etc/qemu-ifup conflict... Unpacking qemu-system (from .../qemu-system_0.11.0-3_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/qemu-system_0.11.0-3_amd64.deb (--unpack): trying to overwrite '/etc/qemu-ifup', which is also in package qemu 0:0.11.0-3 I had to use dpkg -i --force-overwrite qemu-system_0.11.0-3_amd64.deb to continue the installation. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556627: Bug not fixed
On Wednesday 18 of November 2009 18:23:02 Aurelien Jarno wrote: On Wed, Nov 18, 2009 at 06:11:27PM +0200, George Kiagiadakis wrote: Yes, I already did that, but that didn't solve the /etc/qemu-ifup conflict... Unpacking qemu-system (from .../qemu-system_0.11.0-3_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/qemu-system_0.11.0-3_amd64.deb (--unpack): trying to overwrite '/etc/qemu-ifup', which is also in package qemu 0:0.11.0-3 qemu 0:0.11.0-3 does not contains this file, see http://packages.debian.org/sid/amd64/qemu/filelist It may be a dpkg bug then. Which version of dpkg are you using? I have dpkg 1.15.5.1, but I don't think it is a dpkg bug. As you probably know, files in /etc are considered configuration files and are never removed even if the package that installed them no longer installs them. To get them removed, one needs to purge the package. Since in our case I am upgrading and not purging qemu, this configuration file still belongs to qemu, so dpkg cannot allow another package to install the same file. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541136: kaboom deletes all customized kde4 settings
2009/8/12 Daniel Moerner dmoer...@gmail.com: Package: kaboom Version: 1.1.1 Severity: grave Hi, kaboom just caused serious data loss. I have a brand-new install of Debian sid. I installed kde4 (kde-standard metapackage). I start kdm, and on the first run of kde4, kaboom does not run. I customized the settings, turned on desktop effects, etc. I then rebooted. On the second start of kde4, kaboom ran. It explicitly said that existing kde4 settings would be unchanged. I told it to not backup KDE3 data and to not perform any migration. Instead, it deleted ALL my existing KDE4 settings. KDE3 was never installed on this system. There was no reason for kaboom to ever run. ..kaboom.log is attached. I am really sorry about that. The bug that kaboom runs on fresh kde4 installations is known and fixed in git. About the data loss though, it looks like you selected the option to start with clean settings, that's why it removed ~/.kde. The log says that: operation: do recursive rm of .kde dir if exists. Maybe you did it accidentally... Anyway, a new upload will come soon that will fix this bug. Best regards, George -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534166: Problem is way to KDE4
2009/6/25 forum+deb...@km.mydyn.de: The problem is that the packages are now screwed to KDE 4.2.2. So there is a Mixup from KDE 3 and KDE 4! It is not surprising that this is not working. Hi, Since you are using testing, you should not have packages from both kde3 and kde4. Testing only has kde4 now. The missing kcmkttsd module is not really missing, but you should use kde4's systemsettings to run it. kcontrol only shows kcm modules from kde3. You can run it separately if you want using the command kcmshell4 kcmkttsd. If it is still not opening, try running kbuildsycoca4 as a user. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532734: [kdebase-workspace-bin] Plasma refuses to start
severity 532734 important forcemerge 532734 532735 thanks Hi, This crash seems to be due to the recent update of python-qt4. You probably have some python plasmoids on your desktop. As a temporary workaround, backup your plasma configuration and let it start with a clean one, which has no python plasmoids on it. To backup: mkdir ~/plasma-backup mv ~/.kde/share/config/plasma* ~/plasma-backup/ I am lowering the severity, because this affects only people that use python plasmoids. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531976: bluez: Occasionally the kernel freezes while connecting bluetooth mouse
Package: bluez Version: 4.40-2 Severity: critical Justification: breaks the whole system Hi, I have a logitech bluetooth mouse which I connect using hidd --connect $MAC_ADDRESS. Before I upgrade to bluez 4.40 in unstable, it had always been working fine. Since I upgraded to bluez 4.40, I am experiencing strange behavior and occasional kernel freezes. My usage scenario is this: First I turn on the mouse and then I run a script on a console, which runs sudo hidd --connect $MAC_ADDRESS, to connect the mouse. When I want to disconnect it, I simply turn off the mouse. Before the bluez 4.40 upgrade I had no problems with that. Since 4.40 though, every time I run this script, I first get an error message saying No route to host and then I have to try once again and the mouse connects fine. Sometimes though, the second time it does not succeed either, and hidd does not return. After a few seconds, the kernel freezes completely. Keyboard/screen are dead and I can't ping the machine. Only alt+sysrq+b works, which reboots the machine. This has happened to me twice, one time with a custom 2.6.27 kernel and the second time with debian's 2.6.29-2 kernel. The logs don't write anything about it. Ask me if you need any further information. Regards, George -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-amd64 (SMP w/3 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bluez depends on: ii dbus 1.2.14-2simple interprocess messaging syst ii libbluetooth34.40-2 Library to use the BlueZ Linux Blu ii libc62.9-13 GNU C Library: Shared libraries ii libdbus-1-3 1.2.14-2simple interprocess messaging syst ii libglib2.0-0 2.20.3-1The GLib library of C routines ii libnl1 1.1-5 library for dealing with netlink s ii libusb-0.1-4 2:0.1.12-13 userspace USB programming library ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip ii makedev 2.3.1-88creates device files in /dev ii module-init-tools3.7-pre9-1 tools for managing Linux kernel mo ii udev 0.141-1 /dev/ and hotplug management daemo bluez recommends no packages. Versions of packages bluez suggests: ii python-dbus 0.83.0-1 simple interprocess messaging syst ii python-gobject2.16.1-1 Python bindings for the GObject li -- 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
Bug#507509:
On Sunday 07 December 2008 20:41:35 Diego Escalante Urrelo wrote: On 12/7/08, George Kiagiadakis [EMAIL PROTECTED] wrote: ALSO, I tried this with a different user and it seems to work! So, it's obviously some problem with the configuration. I tried to move away ~/.config/subtitleeditor, but that didn't help and I noticed that it still could remember the recently opened files, so it must be saving some configuration bits somewhere else. Any ideas where is that? ~/.recently-used*, keep your current copy before deleting so we can try to debug the problem further (perhaps it's a crash on missing files being on the r-u list) I tried moving those files away, but it didn't help. I discovered though a very odd thing. If subtitleeditor is running in my kde 4.2 (beta) session, it crashes. If it is not, it doesn't crash. Something like that: Non-crashing procedure: - Login to kde 4.2 as user1 - Start subtitleeditor as another user: $ ssh -Y [EMAIL PROTECTED] $ subtitleeditor - Open a file - opens fine! Crashing procedure: - Login to kde 4.2 as *either* user1 or user2 - Start subtitleeditor - Open a file - crash! In all cases I tried with a clean ~/.recent* This is very strange and I can't understand what might cause it. I am not using the gtk-qt theme engine for gtk and as far as I can tell, subtitleeditor doesn't dlopen() any qt/kde library. Any ideas? PS: I think the severity should be lowered now. Subtitleeditor works fine with kde 4.1 and older and kde 4.2 is unreleased (both upstream and in debian), so that's definitely not an rc bug :) Regards, George -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#507509:
On Sunday 07 December 2008 11:10:36 Cyril Brulebois wrote: Putting back the submitter in the loop. Diego Escalante Urrelo [EMAIL PROTECTED] (02/12/2008): Install de debug packages for libgtk, libglib, libgconf and similar, both the mm (C++) and usual C versions, example: ii libglib2.0-0-dbg 2.18.2-0ubuntu2 ii libgtk2.0-0-dbg 2.14.4-0ubuntu1 Hi, I tried to install many gtk/gnome related -dbg packages, but that didn't help. I tried to run gdb --pid `pidof subtitleeditor` to see which libraries lack symbols and I noticed this line: Reading symbols from /usr/bin/subtitleeditor...(no debugging symbols found)...done. So, I downloaded the source code (via apt-get source) and rebuilt it (after commenting out dh_strip in debian/rules) and I got a much better backtrace: Program received signal SIGABRT, Aborted. [Switching to Thread 0x7f62d11b46f0 (LWP 16381)] 0x7f62cb2eeed5 in raise () from /lib/libc.so.6 (gdb) bt #0 0x7f62cb2eeed5 in raise () from /lib/libc.so.6 #1 0x7f62cb2f03f3 in abort () from /lib/libc.so.6 #2 0x7f62cb330970 in malloc_printerr () from /lib/libc.so.6 #3 0x7f62d0d78b7a in Gtk::RecentManager::add_item (this=0xc08d50, [EMAIL PROTECTED], [EMAIL PROTECTED]) at recentmanager.cc:51 #4 0x004d1b82 in DocumentManagementPlugin::add_document_in_recent_manager (this=value optimized out, doc=value optimized out) at actions/DocumentManagement.cc:683 #5 0x0043b3a2 in DocumentSystem::append (this=value optimized out, doc=0xe2e3b0) at /usr/include/sigc++-2.0/sigc++/signal.h:690 #6 0x004d2dd0 in DocumentManagementPlugin::on_recent_item_activated (this=value optimized out, rc=value optimized out) at actions/DocumentManagement.cc:287 #7 0x7f62cf9d1c92 in Glib::SignalProxyNormal::slot0_void_callback (self=value optimized out, data=0xc1d870) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:440 #8 0x7f62ce7b9e9d in IA__g_closure_invoke (closure=0xc162c0, return_value=0x0, n_param_values=1, param_values=0x7fffd92f6150, invocation_hint=0x7fffd92f6050) at /build/buildd/glib2.0-2.16.6/gobject/gclosure.c:490 #9 0x7f62ce7cd11e in signal_emit_unlocked_R (node=0xc1c1f0, detail=0, instance=0xc1e030, emission_return=0x0, instance_and_params=0x7fffd92f6150) at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c:2510 #10 0x7f62ce7ce0ee in IA__g_signal_emit_valist (instance=0xc1e030, signal_id=value optimized out, detail=0, var_args=0x7fffd92f63b0) at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c:2199 #11 0x7f62ce7ce5f3 in IA__g_signal_emit (instance=0x3ffd, signal_id=16381, detail=6) at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c:2243 #12 0x7f62ce7b9e9d in IA__g_closure_invoke (closure=0xc19a90, return_value=0x0, n_param_values=1, param_values=0x7fffd92f66d0, invocation_hint=0x7fffd92f65d0) at /build/buildd/glib2.0-2.16.6/gobject/gclosure.c:490 #13 0x7f62ce7ccbfd in signal_emit_unlocked_R (node=0xb8cfa0, detail=0, instance=0xc07830, emission_return=0x0, instance_and_params=0x7fffd92f66d0) at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c:2440 #14 0x7f62ce7ce0ee in IA__g_signal_emit_valist (instance=0xc07830, signal_id=value optimized out, detail=0, var_args=0x7fffd92f6930) at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c:2199 #15 0x7f62ce7ce5f3 in IA__g_signal_emit (instance=0x3ffd, signal_id=16381, detail=6) at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c:2243 #16 0x7f62d02a39cb in IA__gtk_widget_activate (widget=0xc07830) at /scratch/build-area/gtk+2.0-2.12.11/gtk/gtkwidget.c:4709 #17 0x7f62d01972ad in IA__gtk_menu_shell_activate_item (menu_shell=0xc1e030, menu_item=0xc07830, force_deactivate=value optimized out) at /scratch/build-area/gtk+2.0-2.12.11/gtk/gtkmenushell.c:1150 #18 0x7f62d0198f85 in gtk_menu_shell_button_release (widget=0xc1e030, event=0xb4e080) at /scratch/build-area/gtk+2.0-2.12.11/gtk/gtkmenushell.c:674 #19 0x7f62d018a748 in _gtk_marshal_BOOLEAN__BOXED
Bug#507509: subtitleeditor: crashes when opening any subtitle file
Package: subtitleeditor Version: 0.21.1-2+b1 Severity: grave Justification: renders package unusable subtitleeditor crashes for me every time I try to open a subtitle file. I have tried with many files, so it's not a file-specific problem. I have generated a backtrace, although it still seems to lack some -dbg packages, but I don't know which ones. Please ask me any more information that you wish to know. I am not familiar with the gtk libraries, so I don't really know how to help more. Backtrace: (gdb) run Starting program: /usr/bin/subtitleeditor (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7fb2a74e36f0 (LWP 22789)] application run: 0.54 ** (subtitleeditor:22789): WARNING **: update_columns_displayed_from_config FAILED Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fb2a74e36f0 (LWP 22789)] 0x7fb2a161ded5 in raise () from /lib/libc.so.6 (gdb) bt #0 0x7fb2a161ded5 in raise () from /lib/libc.so.6 #1 0x7fb2a161f3f3 in abort () from /lib/libc.so.6 #2 0x7fb2a165f970 in malloc_printerr () from /lib/libc.so.6 #3 0x7fb2a70a7b7a in Gtk::RecentManager::add_item (this=0xfbb640, [EMAIL PROTECTED], [EMAIL PROTECTED]) at recentmanager.cc:51 #4 0x004d1bf2 in ?? () #5 0x0043b3e2 in ?? () #6 0x004d2e40 in ?? () #7 0x7fb2a5d00c92 in Glib::SignalProxyNormal::slot0_void_callback () from /usr/lib/libglibmm-2.4.so.1 #8 0x7fb2a4ae8e9d in IA__g_closure_invoke (closure=0x10352c0, return_value=0x0, n_param_values=1, param_values=0x7fffaf625470, invocation_hint=0x7fffaf625370) at /build/buildd/glib2.0-2.16.6/gobject/gclosure.c:490 #9 0x7fb2a4afc11e in signal_emit_unlocked_R (node=0x103b3a0, detail=0, instance=0x1046000, emission_return=0x0, instance_and_params=0x7fffaf625470) at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c:2510 #10 0x7fb2a4afd0ee in IA__g_signal_emit_valist (instance=0x1046000, signal_id=value optimized out, detail=0, var_args=0x7fffaf6256d0) at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c:2199 #11 0x7fb2a4afd5f3 in IA__g_signal_emit (instance=0x5905, signal_id=22789, detail=6) at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c:2243 #12 0x7fb2a4ae8e9d in IA__g_closure_invoke (closure=0x1034c70, return_value=0x0, n_param_values=1, param_values=0x7fffaf6259f0, invocation_hint=0x7fffaf6258f0) at /build/buildd/glib2.0-2.16.6/gobject/gclosure.c:490 #13 0x7fb2a4afbbfd in signal_emit_unlocked_R (node=0xfb5450, detail=0, instance=0x102e030, emission_return=0x0, instance_and_params=0x7fffaf6259f0) at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c:2440 #14 0x7fb2a4afd0ee in IA__g_signal_emit_valist (instance=0x102e030, signal_id=value optimized out, detail=0, var_args=0x7fffaf625c50) at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c:2199 #15 0x7fb2a4afd5f3 in IA__g_signal_emit (instance=0x5905, signal_id=22789, detail=6) at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c:2243 #16 0x7fb2a65d29cb in gtk_widget_activate () from /usr/lib/libgtk-x11-2.0.so.0 #17 0x7fb2a64c62ad in gtk_menu_shell_activate_item () from /usr/lib/libgtk-x11-2.0.so.0 #18 0x7fb2a64c7f85 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 ---Type return to continue, or q return to quit---
Bug#496125: strigi dolphin affected too
This bug also affects strigi which unfortunately uses libxml2 too. This causes applications that depend on strigi to crash too (like dolphin from kde4). In dolphin, if you try to mouseover any file, it crashes with the following backtrace: Application: Dolphin (dolphin), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0x7f53a8a02780 (LWP 27320)] [KCrash handler] #5 0x7f53a535a5c8 in _int_free () from /lib/libc.so.6 #6 0x7f53a535aa76 in free () from /lib/libc.so.6 #7 0x7f53a0291054 in xmlParseEntityDecl () from /usr/lib/libxml2.so.2 #8 0x7f53a02917e6 in xmlParseMarkupDecl () from /usr/lib/libxml2.so.2 #9 0x7f53a029187e in ?? () from /usr/lib/libxml2.so.2 #10 0x7f53a0292626 in xmlParseChunk () from /usr/lib/libxml2.so.2 #11 0x7f53a451640d in Strigi::FieldPropertiesDb::Private::parseProperties () from /usr/lib/libstreamanalyzer.so.0 #12 0x7f53a4516842 in Strigi::FieldPropertiesDb::Private::loadProperties () from /usr/lib/libstreamanalyzer.so.0 #13 0x7f53a4519251 in Strigi::FieldPropertiesDb::Private::Private () from /usr/lib/libstreamanalyzer.so.0 #14 0x7f53a4519f76 in Strigi::FieldPropertiesDb::FieldPropertiesDb () from /usr/lib/libstreamanalyzer.so.0 #15 0x7f53a4519fd4 in Strigi::FieldPropertiesDb::db () from /usr/lib/libstreamanalyzer.so.0 #16 0x7f53a451e815 in Strigi::FieldRegister::registerField () from /usr/lib/libstreamanalyzer.so.0 #17 0x7f53a451ea0a in Strigi::FieldRegister::FieldRegister () from /usr/lib/libstreamanalyzer.so.0 #18 0x7f53a4509e04 in Strigi::AnalyzerConfiguration::AnalyzerConfiguration () from /usr/lib/libstreamanalyzer.so.0 #19 0x7f53a8131956 in PredicatePropertyProvider (this=0xf2e810) at /build/buildd/kde4libs-4.1.0/kio/kio/predicateproperties.cpp:116 #20 0x7f53a8131b12 in PredicatePropertyProvider::self () at /build/buildd/kde4libs-4.1.0/kio/kio/predicateproperties.cpp:104 #21 0x7f53a80f3e10 in KFileMetaInfoPrivate::init (this=0xe46e80, [EMAIL PROTECTED], [EMAIL PROTECTED], mtime=1214391724) at /build/buildd/kde4libs-4.1.0/kio/kio/kfilemetainfo.cpp:194 #22 0x7f53a80f5ecf in KFileMetaInfo (this=0x7fffb0b39880, [EMAIL PROTECTED]) at /build/buildd/kde4libs-4.1.0/kio/kio/kfilemetainfo.cpp:224 #23 0x0043efcb in InfoSidebarPage::showMetaInfo (this=0xabe730) at /tmp/buildd/kdebase-4.1.0/apps/dolphin/src/infosidebarpage.cpp:388 #24 0x0043f3c1 in InfoSidebarPage::showItemInfo (this=0xabe730) at /tmp/buildd/kdebase-4.1.0/apps/dolphin/src/infosidebarpage.cpp:223 #25 0x0043fc68 in InfoSidebarPage::qt_metacall (this=0xabe730, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffb0b39bf0) at /tmp/buildd/kdebase-4.1.0/obj-x86_64-linux- gnu/apps/dolphin/src/infosidebarpage.moc:93 #26 0x7f53a5fdb474 in QMetaObject::activate (sender=0x7a0870, from_signal_index=value optimized out, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3016 #27 0x7f53a5fd5d83 in QObject::event (this=0x7a0870, e=0x7f53a54028d8) at kernel/qobject.cpp:1105 #28 0x7f53a66e641d in QApplicationPrivate::notify_helper (this=0x68bf70, receiver=0x7a0870, e=0x7fffb0b3a290) at kernel/qapplication.cpp:3800 #29 0x7f53a66ee17a in QApplication::notify (this=0x7fffb0b3a5d0, receiver=0x7a0870, e=0x7fffb0b3a290) at kernel/qapplication.cpp:3765 #30 0x7f53a7bdac0b in KApplication::notify (this=0x7fffb0b3a5d0, receiver=0x7a0870, event=0x7fffb0b3a290) at /build/buildd/kde4libs-4.1.0/kdeui/kernel/kapplication.cpp:311 #31 0x7f53a5fc711f in QCoreApplication::notifyInternal ( this=0x7fffb0b3a5d0, receiver=0x7a0870, event=0x7fffb0b3a290) at kernel/qcoreapplication.cpp:591 #32
Bug#489839: udev initscript exits unexpectedly before populating /dev
It also seems to affect initng, so I think it is not a bug in the initscript itself. I am using initng here in combination with a self-compiled 2.6.24 kernel without initrd. With udev 0.124-1 it stops when it tries to mount / because /dev/sda5 does not exist. The solution is to login and execute: # /etc/init.d/udev stop # /etc/init.d/udev start After that, initng is able to continue booting. It is quite strange though that the normal initscript works in this case... Note though that stop is required or else start fails. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
