Bug#959853: libcamera-tools: description mentions it provides qcam, but it doesn't
Package: libcamera-tools Version: 0~git20200417+35269f0-2 Severity: important Dear Maintainer, libcamera-tools package description mentions that it provides 'qcam', however this program is not in the package. Please consider adding it. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcamera-tools depends on: ii libc6 2.30-4 ii libcamera0 0~git20200417+35269f0-2 ii libgcc-s1 10-20200418-1 ii libstdc++6 10-20200418-1 libcamera-tools recommends no packages. libcamera-tools suggests no packages. -- no debconf information
Bug#851701: kdevelop: missing dependency on kinit
Package: kdevelop Version: 4:5.0.1-2 Severity: important Steps to reproduce: 1. Install a fresh debian stretch system with GNOME! 2. apt install kdevelop 3. run kdevelop Observed behaviour: kdevelop greets you with an error dialog saying: "Could not start process Cannot talk to klauncher: The name org.kde.klauncher5 was not provided by any .service files" Apparently klauncher is in the kinit package, so a dependency seems appropriate. Installing kinit solves the issue. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.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 /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages kdevelop depends on: ii kdevelop-data 4:5.0.1-2 ii kdevplatform10-libs5.0.1-2 ii libc6 2.24-8 ii libclang1-3.8 1:3.8.1-16 ii libgcc11:6.2.1-5 ii libkasten3controllers3 4:16.08.2-1 ii libkasten3core34:16.08.2-1 ii libkasten3okteta1controllers1 4:16.08.2-1 ii libkasten3okteta1core1 4:16.08.2-1 ii libkasten3okteta1gui1 4:16.08.2-1 ii libkf5completion5 5.27.0-1 ii libkf5configcore5 5.27.0-1 ii libkf5configgui5 5.27.0-1 ii libkf5configwidgets5 5.27.0-1 ii libkf5coreaddons5 5.27.0-1 ii libkf5crash5 5.27.0-1 ii libkf5declarative5 5.27.0-1+b1 ii libkf5i18n55.27.0-2 ii libkf5iconthemes5 5.27.0-1 ii libkf5itemviews5 5.27.0-1 ii libkf5jobwidgets5 5.27.0-1 ii libkf5kiocore5 5.27.0-2 ii libkf5kiowidgets5 5.27.0-2 ii libkf5newstuff55.27.0-1 ii libkf5parts5 5.27.0-1 ii libkf5texteditor5 5.27.0-1 ii libkf5threadweaver55.27.0-1 ii libkf5widgetsaddons5 5.27.0-1 ii libkf5xmlgui5 5.27.0-1 ii libprocesscore74:5.8.2-1 ii libprocessui7 4:5.8.2-1 ii libqt5core5a 5.7.1+dfsg-2 ii libqt5dbus55.7.1+dfsg-2 ii libqt5gui5 5.7.1+dfsg-2 ii libqt5help55.7.1-1 ii libqt5network5 5.7.1+dfsg-2 ii libqt5quickwidgets55.7.1-2 ii libqt5webkit5 5.7.1+dfsg-1 ii libqt5widgets5 5.7.1+dfsg-2 ii libqt5xml5 5.7.1+dfsg-2 ii libstdc++6 6.2.1-5 Versions of packages kdevelop recommends: ii g++ 4:6.2.1-1 ii gcc 4:6.2.1-1 ii gdb 7.12-4 ii kapptemplate 4:16.08.2-1 ii kio-extras4:16.08.2-1 ii make 4.1-9 Versions of packages kdevelop suggests: ii cmake 3.7.1-1 pn kdevelop-l10n pn ninja-build -- no debconf information
Bug#776363: mouse disconnecting after some time
I can confirm this bug. I have a logitech bluetooth travel mouse that disconnects extremely often after a recent update (I suspect it was the update to bluez 5, but haven't confirmed it) Looks like it may have something to do with power saving, because it seems to disconnect when I leave the mouse without moving it for a few seconds. The only strange thing that I can see in the logs is: Jul 06 15:14:33 thinkpadaki kernel: hid-generic 0005:046D:B008.0066: unknown main item tag 0x0 This is an extremely frustrating bug that makes this mouse almost unusable. signature.asc Description: OpenPGP digital signature
Bug#703047: odbc-postgresql cannot be installed alongside kde
Package: odbc-postgresql Version: 1:09.01.0100-1 Severity: important I need to install odbc-postgresql on a system that is running a kde desktop. However, odbc-postgresql declares Breaks on libiodbc2, which is a direct dependency of kde libraries: i A libkio5 Depends libnepomuk4 (= 4:4.8.4-4) i A libnepomuk4 Depends libsoprano4 (= 2.5.63) i A libsoprano4 Depends soprano-daemon (= 2.7.6+dfsg.1-2) i A soprano-daemon Depends libiodbc2 (= 3.52.7) May I ask the reason for this Breaks? Is there something that could be done either in odbc-postgresql or libiodbc2 to prevent this conflict? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679939: [Pkg-kde-extras] Bug#679939: meta-kde-telepathy depends on obsoloete package telepathy-butterfly
On Sun, Jul 8, 2012 at 11:41 PM, Laurent Bigonville bi...@debian.org wrote:
Le Sun, 8 Jul 2012 00:32:33 +0300,
George Kiagiadakis kiagiadakis.geo...@gmail.com a écrit :
I don't really see any mention of telepathy-butterfly here:
Package: kde-telepathy-minimal
Architecture: all
Depends: kde-config-telepathy-accounts (= ${ktp:Version}),
kde-telepathy-approver (= ${ktp:Version}),
kde-telepathy-auth-handler (= ${ktp:Version}),
kde-telepathy-contact-list (= ${ktp:Version}),
kde-telepathy-integration-module (= ${ktp:Version}),
plasma-widget-telepathy-presence (= ${ktp:Version}),
kde-telepathy-text-ui (= ${ktp:Version}),
telepathy-mission-control-5 (= 1:5.12),
telepathy-connection-manager,
${misc:Depends}
Recommends: telepathy-gabble, telepathy-salut, telepathy-haze,
telepathy-logger Suggests: telepathy-rakia, telepathy-idle
Alexander, could dak be confused with telepathy-connection-manager which
is a virtual package?
George, I think it's not a good idea (isn't this even against the
policy?) to only have a virtual package listed in the dependencies, it
should be something like:
telepathy-gabble | telepathy-connection-manager or it should
completely be removed.
It's not against policy, at least according to lintian:
http://lintian.debian.org/tags/virtual-package-depends-without-real-package-depends.html
I know it's not a very good idea, but the question is which CM should
be proposed. Can we assume that most users will want to use gabble?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679939:
I don't really see any mention of telepathy-butterfly here:
Package: kde-telepathy-minimal
Architecture: all
Depends: kde-config-telepathy-accounts (= ${ktp:Version}),
kde-telepathy-approver (= ${ktp:Version}),
kde-telepathy-auth-handler (= ${ktp:Version}),
kde-telepathy-contact-list (= ${ktp:Version}),
kde-telepathy-integration-module (= ${ktp:Version}),
plasma-widget-telepathy-presence (= ${ktp:Version}),
kde-telepathy-text-ui (= ${ktp:Version}),
telepathy-mission-control-5 (= 1:5.12),
telepathy-connection-manager,
${misc:Depends}
Recommends: telepathy-gabble, telepathy-salut, telepathy-haze, telepathy-logger
Suggests: telepathy-rakia, telepathy-idle
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636042: [Pkg-kde-extras] Bug#636042: libbluedevil1: install library in multiarch path
tags 636042 + pending thanks On Sat, Jul 30, 2011 at 4:26 PM, Daniel Schaal farb...@web.de wrote: Package: libbluedevil1 Version: 1.9-1 Severity: wishlist Tags: patch Attached is a patch to install the library in multiarch paths. Thanks for the patch. I applied it in the repository and will be in the next upload. Best regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#465605: xserver-xorg-input-synaptics: When using xinerama, the touchpad cannot move the pointer from screen1 to screen0.
On Tue, Jan 18, 2011 at 8:28 PM, Cyril Brulebois k...@debian.org wrote: Hi George, George Kiagiadakis gkiag...@csd.uoc.gr (13/02/2008): When I use the synaptics touchpad to move the pointer from screen0 to screen1, it works fine. However, if I try to move the pointer back to screen0 from screen1, the pointer stops at the left side of screen1 (which is the boundary between the two screens). This doesn't happen with a usb mouse. I can use the usb mouse to move the pointer back to screen0 without any problems. is this still happening with the X stack from squeeze/sid, or with the one in experimental? KiBi. Hello, Sorry for the late reply. I have stopped using that setup for a long time now and I didn't have the time to get the pieces together again so that I can test it. So, I tried this on a squeeze system and I cannot reproduce it. The setup is not entirely identical though. One (probably unrelated) difference is that I am currently using the nouveau drivers on this laptop instead of nvidia that I was using back then and a second difference is that back then I used to configure dual-screen from xorg.conf (iirc) while this time I did it from KDE's configuration tool which applies changes on the fly. But in any case, I think this bug can be safely closed. Best regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546376: kdm: will there ever be a _real_ fix or answer?
On Sat, Dec 18, 2010 at 8:43 PM, arne anka deb...@ginguppin.de wrote: Package: kdm Version: 4:4.5.1-0r2 Severity: normal i reported the very same thing as #580269. it has been closed with the false claim of being solved -- my answer that this was not so, was ignored -- at least i never received an answer. i just upgraded to what most likely will become the official kde 4.5 in debian -- and the very same bug is still there. Are you sure? This is fixed in 4.5 upstream. Of course, there is no Administrator mode button like other distros may have added with patches in previous versions of KDE. The kdm configuration interface appears normally in systemsettings running as user, you are allowed to make changes and when you click the Apply button, it asks you for the root password. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546376: kdm: will there ever be a _real_ fix or answer?
On Sat, Dec 18, 2010 at 9:21 PM, arne anka deb...@ginguppin.de wrote: interesting -- at least the Apply button becomes active after a change ... but hitting Apply returns only: Unable to authenticate/execute the action: (code 4) Do you have polkit-kde-1 installed? If not, try installing it, logout/login and try again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605753: kaboom: diff for NMU version 1.1.2+nmu1
On Fri, Dec 10, 2010 at 1:08 AM, David Prévot taf...@tilapin.org wrote: tags 605753 + pending thanks Dear maintainer, I've prepared an NMU for kaboom (versioned as 1.1.2+nmu1) and uploaded it to DELAYED/4. Please feel free to tell me if I should delay it longer. Regards. David It looks fine to me. Thanks for taking care of it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605753: kaboom: Please activate the French translation
On Fri, Dec 3, 2010 at 12:03 PM, Frederik Schwarzer schwarz...@gmail.com wrote: diff -ur ./kaboom.pro ../orig/kaboom-1.1.2//kaboom.pro --- ./kaboom.pro 2010-12-02 22:34:05.0 -0400 +++ ../orig/kaboom-1.1.2//kaboom.pro 2009-07-04 06:58:46.0 -0400 @@ -13,7 +13,6 @@ kaboom_da.ts \ kaboom_de.ts \ kaboom_es.ts \ - kaboom_fr.ts \ kaboom_it.ts \ kaboom_el.ts Just out of curiosity. Removing fr from the project file makes it shippable? Looks odd. :) It should be +. Notice that diff has been called with the arguments swapped (original file should be first). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605040: ITP: qt-gstreamer -- GStreamer bindings for C++/Qt4
Package: wnpp Severity: wishlist Owner: George Kiagiadakis kiagiadakis.geo...@gmail.com * Package name: qt-gstreamer Upstream Author : George Kiagiadakis george.kiagiada...@collabora.co.uk, Mauricio Piacentini mauricio.piacent...@collabora.co.uk * URL : http://cgit.freedesktop.org/gstreamer/qt-gstreamer/ * License : LGPL Programming Lang: C++ Description : GStreamer bindings for C++/Qt4 QtGStreamer provides C++ bindings for GStreamer with a Qt-style API, plus some helper classes for integrating GStreamer better in Qt applications. The library is currently under heavy development and the first release is expected in a few weeks' time. I don't intend to upload pre-release snapshots to the debian archive, but only prepare the package to be ready for upload after the first release. It is probably best to put this under the maintenance of pkg-gstreamer, if the pkg-gstreamer team agrees of course, as it is an official gstreamer project. Of course, I will actively maintain this package. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599205: AW: Bug#599205: phonon-backend-vlc: kde is playing sounds via pcspeaker, instead of soundcard
On Mon, Oct 18, 2010 at 12:45 PM, sdfsdfsdf ewfwdfsdf spamfang1...@yahoo.de wrote: Additional informations: At the time of reporting the bug, neither pulseaudio and pulseaudio-module-x11, nor alsa-base and linux-sound-base were installed. After installing them, these problems vanished. But therefore other problems occured. This issue was happening because alsa was not configured. If you wish to use alsa as your sound system, you need to install alsa-base and run 'alsactl init' once to configure it. If you wish to use pulseaudio you need to install the pulseaudio package. I am wondering though, how did you install debian? Is the sound system broken by default like that? You can crosscheck the following bugreport for a better overview: bugs.kde.org/show_bug.cgi?id=240001 The problem seems to be related to Pulseaudio and to the vlc-plugin-pulse. Should I open another bug report? I suggest another bug report, yes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598975: QPainter Errors in ~/.xsession-errors
On Tue, Oct 5, 2010 at 2:04 AM, Eckhart Wörner ewoer...@kde.org wrote: tags 598975 + moreinfo thanks Am Sonntag, 03. Oktober 2010, 18:02:12 schrieb Thilo Six: After 6 hours uptime ~/.xsession-errors is now 5MB large. $ grep ^QPainter ~/.xsession-errors | wc -l 119030 It is difficult to stay aware of real problems with this mass messages. Those messages *do* indicate real problems. Can you please try to pinpoint it to a specific application? iirc it's konqueror. There was a thread about that in some kde mailinglist some time ago... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#597722: unblock: bluedevil/1.0~rc3-1
On Sun, Sep 26, 2010 at 4:31 PM, Julien Cristau jcris...@debian.org wrote: On Sun, Sep 26, 2010 at 15:03:24 +0300, George Kiagiadakis wrote: Ok, understood, so if I drop the kbluetooth transitional package and generate the version from debian/changelog somehow, would you then unblock it? Probably. Cheers, Julien bluedevil 1.0~rc3-2 was uploaded last night and adresses these issues. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#597722: unblock: bluedevil/1.0~rc3-1
Hello, On Sun, Sep 26, 2010 at 12:25 PM, Julien Cristau jcris...@debian.org wrote: On Wed, Sep 22, 2010 at 17:49:37 +0300, George Kiagiadakis wrote: This upload of bluedevil introduces transitional packages for kbluetooth and kdebluetooth, plus it packages the new rc3 upstream release, which is just a few bugfixes since rc2, which is in testing. The transitional kdebluetooth package is important to be in squeeze, since it will allow smooth upgrade from the outdated and broken kdebluetooth to the new bluedevil. What's the point of the kbluetooth package though. It's not transitional, since there's no such package in stable or testing at the moment? Also what's with the versioning for those packages? Having to modify debian/rules for every upload doesn't seem to be the way to go. kbluetooth is transitional for the kbluetooth that was in unstable (but never made it into testing). One of the ex-maintainers of kbluetooth suggested that I should also add a transitional package for it. Their version is just something higher than the last version of kbluetooth/kdebluetooth that was in unstable. I did that to avoid bumping epoch on bluedevil. Having to modify debian/rules for each upload isn't so great, but it's not much hassle either, because I don't intend to do any further uploads before squeeze is released and after the release I will again drop the transitional packages (well, supposing that the release will take some time...). The rc3 release introduces only a few bugfixes, which are a good thing in my opinion. It has: 2 crash fixes, 1 normal bugfix, a few string fixes and a few cosmetic changes. You could check this by checking the git history: I see string changes, but no corresponding translation changes. Is this translated at all? There are no translations for bluedevil. Upstream added the possibility to translate it in 1.0~rc4 (released last week) and it will take some time until translations are ready, so I don't think they can make it for squeeze. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#597722: unblock: bluedevil/1.0~rc3-1
On Sun, Sep 26, 2010 at 12:58 PM, Julien Cristau jcris...@debian.org wrote: On Sun, Sep 26, 2010 at 12:54:15 +0300, George Kiagiadakis wrote: kbluetooth is transitional for the kbluetooth that was in unstable (but never made it into testing). One of the ex-maintainers of kbluetooth suggested that I should also add a transitional package for it. Their version is just something higher than the last version of kbluetooth/kdebluetooth that was in unstable. I did that to avoid bumping epoch on bluedevil. Having to modify debian/rules for each upload isn't so great, but it's not much hassle either, because I don't intend to do any further uploads before squeeze is released and after the release I will again drop the transitional packages (well, supposing that the release will take some time...). Well I don't see a reason for squeeze to carry the kbluetooth cruft. And I don't think the way you call dh_gencontrol is acceptable, you could just pick the version from the changelog and add the epoch instead of hardcoding it. Ok, understood, so if I drop the kbluetooth transitional package and generate the version from debian/changelog somehow, would you then unblock it? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#597722: unblock: bluedevil/1.0~rc3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package bluedevil This upload of bluedevil introduces transitional packages for kbluetooth and kdebluetooth, plus it packages the new rc3 upstream release, which is just a few bugfixes since rc2, which is in testing. The transitional kdebluetooth package is important to be in squeeze, since it will allow smooth upgrade from the outdated and broken kdebluetooth to the new bluedevil. The rc3 release introduces only a few bugfixes, which are a good thing in my opinion. It has: 2 crash fixes, 1 normal bugfix, a few string fixes and a few cosmetic changes. You could check this by checking the git history: $ git clone git://gitorious.org/bluedevil/bluedevil.git $ cd bluedevil $ git shortlog v1.0-rc2..v1.0-rc3 I figured it would be better to upload rc3 since I was going to upload the update for the transitional packages anyway. I didn't mean to request a freeze exception just because it's a new bugfix release. It was all motivated by the fact that I needed to add those transitional packages in squeeze. The debian packaging history can be seen here: http://git.debian.org/?p=pkg-kde/kde-extras/bluedevil.git;a=summary Thanks in advance. unblock bluedevil/1.0~rc3-1 -- 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.35-trunk-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#597003: [Pkg-kde-extras] Bug#597003: [bluedevil] Bluedevil not find (and see) any device
On Wed, Sep 15, 2010 at 11:37 PM, Francesco Muzio muzi...@email.it wrote: Package: bluedevil Version: 1.0~rc2-1 Severity: important Buedevil not find any device while scanning from the GUI, but find my devices if I run hcitool scan while bluedevil is looking for new device. I think the KDE daemon is not able to put the device in scan mode and is not able to use this if i reach to pairing it with my pc (with the hcitool trick). Could you try upgrading to 1.0~rc3-1 and see if you still have the issue? Thanks, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596725: RM: kbluetooth -- ROM; obsolete, bluedevil replaces it
Package: ftp.debian.org Severity: normal Hello, Please remove src:kbluetooth from unstable. It is obsoleted and bluedevil now provides an alternative for its functionality. Please note that since today's bluedevil 1.0~rc3 upload, bluedevil now provides transitional packages for both kdebluetooth and kbluetooth, the two binary packages that were previously provided by src:kbluetooth. Thanks, George -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596233: network-manager should also recommend plasma-widget-networkmanagement
Package: network-manager Version: 0.8.1-2 Severity: important Currently, network-manager recommends, between others: network-manager-gnome | network-manager-kde However, network-manager-kde is deprecated and plasma-widget-networkmanagement takes its place now. This seems like a minor issue, but it's not. When a user is installing kde-standard, it pulls plasma-widget-networkmanagement, as kde-standard recommends it. This however causes network-manager-gnome to be installed as well, along with its gnome dependencies and recommends, including gnome-bluetooth, policykit-1-gnome and others. The chain is this: p kde-standardRecommends plasma-widget-networkmanagement p plasma-widget-networkmanagement Dependsknm-runtime (= 0.1~svn1141976-1) p knm-runtime Dependsnetwork-manager (= 0.7.0) p network-manager Recommends network-manager-gnome | network-manager-kde If network-manager was also recommending plasma-widget-networkmanagement in this OR-ed recommend, this wouldn't happen. I would very much like to see this fixed in squeeze, since this affects the user experience of the kde users. 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.35-trunk-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523094: The problem is still present
On Sun, Sep 5, 2010 at 12:36 PM, Marco Bajo marco.b...@gmail.com wrote: Package: systemsettings Version: 4:4.4.5-3 Severity: normal I have to report that the problem is still present. This problem is fixed in kde 4.5.0. -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595483: kde: KDE4 Crashes system
On Sat, Sep 4, 2010 at 3:32 PM, Leslie Rhorer lrho...@fletchergeek.com wrote: A normal severity for a bug that causes the system to be completely unusable when the package is in use? That locks up the system like Fort Knox? That causes data loss if any files are still open? I'm hard pressed to think of a more severe problem. It is a serious problem, but it is not related to the 'kde' package where you reported it. The 'kde' package is a metapackage from lenny and does not even exist in squeeze. The most likely cause of the bug is the kernel, so this bug should eventually be reasigned there and have its severity raised, however I cannot do that until the problem has been fully identified. There are no proprietary gpu drivers, and please re-read the post. One of the systems is Intel. Both systems were upgraded from Debian Lenny with no problems whatsoever running KDE3. Neither has any problem running gnome. KDE4 was so unusable on the Pentium system I wiped the drive and installed fresh from the Squeeze installer. It didn't help. Both use the graphics processors embedded on the motherboard, with plain-vanilla Debian installations straight from the Debian install CD. The Pentium system is an old Dell Optiplex GX-1 system, which is about as Plain Jane Intel as it gets. The AMD is over a year old. All of the software on both machines - other than that I have written myself - is straight from the Debian repositories. An intel system can have an amd graphics card, this is not uncommon. I still believe the problem is in graphics drivers, though. Even if these are the free intel or radeon drivers. Radeon drivers are known to lock up if their non-free firmware is missing, perhaps you should make sure to install firmware-linux-nonfree and I'm not sure about the intel drivers (never had one of those). Anyway, the kernel upgrade may help, since the -5- version of this kernel has all the graphics drivers backported from 2.6.33. PS: Do not keep cont...@bugs.debian.org in CC, it will just send you back an email full of errors, since you are not following its syntax in the email (it is a bot). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595013: Drkonqui does not work behind proxy
On Tue, Aug 31, 2010 at 4:00 PM, Bastien ROUCARIES roucaries.bast...@gmail.com wrote: package: kdebase-runtime severity: normal Dr konqui does not work when behind a proxy Bastien Does konqueror work? Did you configure konqueror properly? DrKonqi uses the same settings as konqueror, so if konqueror can connect to https://bugs.kde.org, so should drkonqi. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594501: llvm-2.7-runtime: update-binfmts called with wrong arguments in postinst
Package: llvm-2.7-runtime Version: 2.7-4 Severity: important I just installed llvm-2.7 and got the following installation error: Setting up binfmt-support (1.2.18) ... Enabling additional executable binary formats: binfmt-support. Setting up libllvm2.7 (2.7-4) ... Setting up llvm-2.7-runtime (2.7-4) ... update-binfmts: warning: unable to open /usr/share/binfmts/llvm.binfmt: No such file or directory update-binfmts: warning: couldn't find information about 'llvm.binfmt' to import update-binfmts: exiting due to previous errors It looks like update-binfmts is called with wrong arguments from postinst: update-binfmts --import llvm.binfmt while the file in /usr/share/binfmts is called llvm-2.7.binfmt. -- 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.32-5-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 llvm-2.7-runtime depends on: ii binfmt-support1.2.18 Support for extra binary formats ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libffi5 3.0.9-2Foreign Function Interface library ii libgcc1 1:4.4.4-9 GCC support library ii libllvm2.72.7-4 Low-Level Virtual Machine (LLVM), ii libstdc++64.4.4-9The GNU Standard C++ Library v3 llvm-2.7-runtime recommends no packages. llvm-2.7-runtime 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#593942: RM: libbluedevil [kfreebsd-amd64] -- ROM; no longer built on kfreebsd-amd64
Package: ftp.debian.org Severity: normal Hello, The initial libbluedevil upload was targeted to all architectures by mistake and thus it was accidentally built on kfreebsd-amd64. However, this package is meant to be linux-only (since it relies on the linux-only bluez), which was fixed in the next upload, however there is now a binary for kfreebsd-amd64 which blocks transition to testing. So, please remove libbluedevil1 and libbluedevil-dev from kfreebsd-amd64. Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582568: kdm: causes kaboom to show upgrade dialog on first root login
Btw, this bug is fixed upstream, as kdm 4.5 now runs as a separate kdm user, which has no $HOME and thus there are no such files created anywhere. We hoped to push 4.5 for squeeze, but unfortunately this is not possible anymore, so it seems we will have to work it around. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589892: kwrited: fail to show complete shutdown message
On Thu, Jul 22, 2010 at 2:14 AM, Petter Reinholdtsen p...@hungry.com wrote: Package: kdebase-workspace-bin Version: 4:4.4.4-1 When running shutdown to take down the machine, the broadcasted message is gathered by something and pushed out as a KDE notification. The problem is that the message shown in the notification window is only part of the message show. The complete message in the notification window after running shutdown -h +5 is Broadcast message from r...@tjener.intern (pts/2) (Thy Jul In the terminal where I started shutdown, this message is shown: The system is going DOWN for system halt in 5 minutes! Jul 22 01:09:18 2010): It would be more useful for the user if the full message from shutdown was shown in the notification. To test this, run shutdown with a delay (like +5 for 5 minutes) to see the notification. I tested using wall to see if all the text is shown there, and then the notification window is a bit too small when I do like this as root: (echo foo; echo bar; echo; echo baz) | wall Only a fraction of the 'baz' part is shown in the notification window. It would be better if the notification window was created a bit larger. Happy hacking, -- Petter Reinholdtsen This is a known plasma bug. It works fine with the old (kde 4.0) knotify popups and with gnome's notification-daemon. Unfortunately I cannot find the upstream bug number right now, but I am certain that it has been reported upstream. Rumor has it that the plasma notification system has been polished in 4.5 and that such layout bugs have been fixed... I will check it with 4.5 when it has been packaged. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588192: systemsettings: no user list in default (non-themed) login screen.
On Tue, Jul 6, 2010 at 6:49 AM, Alexandros Prekates apreka...@gmail.com wrote: Package: systemsettings Version: 4:4.4.4-1 Severity: normal Tags: upstream Althought i choose user list in systemsettings-advanced-loginScreen , with no theme , nevertheless a user list wont appear. I tried this, but I couldn't reproduce it. The user list appears just fine. 1) Make sure that you restart kdm after changing the settings (invoke-rc.d kdm restart). 2) Make sure that /etc/kde4/kdm/kdmrc gets modified when you change settings. For the user list option, it should say UserList=true somewhere, iirc. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584905: plasma-netbook not auto-starting on a fresh install
On Mon, Jun 7, 2010 at 4:35 PM, George Kiagiadakis kiagiadakis.geo...@gmail.com wrote: On Mon, Jun 7, 2010 at 3:39 PM, Brendon Higgins blhigg...@gmail.com wrote: Hi list, I think I've found a reason why plasma-netbook doesn't autostart. /usr/share/autostart/plasma-netbook.desktop doesn't exist. The equivalent, plasma-desktop.desktop, does exist (in the plasma-desktop package). Presumably, this is why plasma-desktop will autostart, whereas plasma-netbook won't. Now I don't know if plasma-netbook.desktop ought to exist given upstream sources, or not. A quick search in KDE sources doesn't find anything, yet apparently there is such a file in Ubuntu (Lucid). :-S I guess the Ubuntu file could be distro custom. I should file a bug with KDE, perhaps? Peace, Brendon I'm turning this email into a bug report, since this seems to be a packaging problem. The relevant kubuntu patch seems to be this one [1] and it seems it has been removed from the 4.5 beta packages, with a changelog message indicating it has been fixed upstream, although I see no plasma-netbook.desktop in their plasma-netbook.install file. I don't fully understand though how this is going to work when one has both plasma-desktop and plasma-netbook installed... are they both going to be autostarted? Also, why does plasma-netbook autostart when plasma-desktop is installed and a netbook form factor is selected in systemsettings? (I had tried that once) [1]. http://bazaar.launchpad.net/~kubuntu-members/kdebase-workspace/ubuntu/annotate/340/debian/patches/kubuntu_102_plasma_netbook_no_autostart.diff Hi, I tested this on my system and I noticed that both plasma-desktop and plasma-netbook can autostart without having any plasma-*.desktop file in /usr/share/autostart. I wonder how this happens and why it doesn't work on your system, Brendon. Scott, do you know any more details about how this is handled? I am still not convinced about why this patch solves the problem. Best regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584905: plasma-netbook not auto-starting on a fresh install
Package: plasma-netbook Version: 4:4.4.4-1 Severity: important On Mon, Jun 7, 2010 at 3:39 PM, Brendon Higgins blhigg...@gmail.com wrote: Hi list, I think I've found a reason why plasma-netbook doesn't autostart. /usr/share/autostart/plasma-netbook.desktop doesn't exist. The equivalent, plasma-desktop.desktop, does exist (in the plasma-desktop package). Presumably, this is why plasma-desktop will autostart, whereas plasma-netbook won't. Now I don't know if plasma-netbook.desktop ought to exist given upstream sources, or not. A quick search in KDE sources doesn't find anything, yet apparently there is such a file in Ubuntu (Lucid). :-S I guess the Ubuntu file could be distro custom. I should file a bug with KDE, perhaps? Peace, Brendon I'm turning this email into a bug report, since this seems to be a packaging problem. The relevant kubuntu patch seems to be this one [1] and it seems it has been removed from the 4.5 beta packages, with a changelog message indicating it has been fixed upstream, although I see no plasma-netbook.desktop in their plasma-netbook.install file. I don't fully understand though how this is going to work when one has both plasma-desktop and plasma-netbook installed... are they both going to be autostarted? Also, why does plasma-netbook autostart when plasma-desktop is installed and a netbook form factor is selected in systemsettings? (I had tried that once) [1]. http://bazaar.launchpad.net/~kubuntu-members/kdebase-workspace/ubuntu/annotate/340/debian/patches/kubuntu_102_plasma_netbook_no_autostart.diff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572848: gstreamer0.10-plugins-base: When used with phonon-gstreamer-backend and KDE4 plasma video widgets colors are wrong
This has also been reported to nokia as a bug in the phonon backend, with a trivial fix, but I'm still not sure if the bug is in phonon or gstreamer. The fix looks like a hack. http://bugreports.qt.nokia.com/browse/QTBUG-8737 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572848: gstreamer0.10-plugins-base: When used with phonon-gstreamer-backend and KDE4 plasma video widgets colors are wrong
reassign 572848 phonon-backend-gstreamer tags 572848 + upstream thanks Hello, 2010/4/15 Sebastian Dröge sl...@circular-chaos.org: On Thu, 2010-04-15 at 11:57 +0300, George Kiagiadakis wrote: This has also been reported to nokia as a bug in the phonon backend, with a trivial fix, but I'm still not sure if the bug is in phonon or gstreamer. The fix looks like a hack. http://bugreports.qt.nokia.com/browse/QTBUG-8737 The Nokia bug is a problem in phonon's gstreamer backend... It claims to support all kinds of RGB formats but in fact only supports xRGB in native endianness. Hmm, thanks for the explanation, I think I understand the issue now and what a proper fix would be. Could you add that to the Nokia bugreport? The code in question is in qwidgetvideosink.cpp: static GstStaticPadTemplate template_factory_yuv = GST_STATIC_PAD_TEMPLATE(sink, GST_PAD_SINK, GST_PAD_ALWAYS, GST_STATIC_CAPS(video/x-raw-yuv, framerate = (fraction) [ 0, MAX ], width = (int) [ 1, MAX ], height = (int) [ 1, MAX ], bpp = (int) 32)); static GstStaticPadTemplate template_factory_rgb = GST_STATIC_PAD_TEMPLATE(sink, GST_PAD_SINK, GST_PAD_ALWAYS, GST_STATIC_CAPS(video/x-raw-rgb, framerate = (fraction) [ 0, MAX ], width = (int) [ 1, MAX ], height = (int) [ 1, MAX ], bpp = (int) 32)); Not only does it claim to support all 32bpp RGB formats but also *all* YUV formats (and a bpp field is not used for YUV at all). That's not true, it claims either RGB or YUV depending on the template parameter. Note that QWidgetVideoSink is a template ;) The bpp for YUV may not be needed but it doesn't hurt either, plus this is completely unrelated to this bug since the code in question uses the RGB version of the template. If they need some help with fixing this they can contact me via mail but I don't want to subscribe to yet another bugtracker... So, from what I understand, the RGB caps need to specify the endianess so that it matches the endianess used by QImage. I'll try to fix it and inform them. If I need help I'll contact you. Thanks :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573063: konsole kfreebsd-i386 blank (terminal) display
On Mon, Mar 15, 2010 at 10:21 AM, Alan BRASLAU alan.bras...@cea.fr wrote: Hello, Have you been able to try konsole on kfreebsd-i386? Thank you. Hi, I have tried konsole on kfreebsd (kfreebsd-amd64 to be exact) and I can reproduce your bug. The problem seems to be that a call to openpty() fails. I think this has to do with the 8.0 kernel, since it used to work a few months ago when I still had the 7.2 kernel. I am currently looking for a solution... Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573063: konsole kfreebsd-i386 blank (terminal) display
On Mon, Mar 8, 2010 at 6:11 PM, Alan BRASLAU alan.bras...@cea.fr wrote: Package: konsole Version: 4:4.3.4-1 Severity: important Under kfreebsd(-i386) konsole is unusable: The terminal display is blank (just a blinking cursor) with no output (or blind input). I have tried different shell commands and tested this on both the :0 display and on an (otherwise working) remote display through XDMCP. Hmm, that's strange. I had added a patch in kdelibs 4:4.3.4-1 to fix that issue. I'll test again when I can. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#571155: libqalculate-dev is missing dependency on libxml2-dev
Package: libqalculate-dev Version: 0.9.7-1 Severity: normal Hi, Trying to find libqalculate using pkg-config, if libxml2-dev is not installed, pkg-config complains about it missing. $ pkg-config libqalculate --libs Package libxml-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `libxml-2.0.pc' to the PKG_CONFIG_PATH environment variable Package 'libxml-2.0', required by 'libqalculate', not found As a result, packages that build-depend on libqalculate-dev need to build-depend on libxml2-dev as well, although they don't use it directly. -- 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.32-trunk-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 libqalculate-dev depends on: ii libcln-dev1.3.1-2Development library for Class Libr ii libqalculate5 0.9.7-1Powerful and easy to use desktop c libqalculate-dev recommends no packages. libqalculate-dev 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#570544: udev: /dev/kvm no longer belongs to the kvm group and breaks libvirt
reopen 570544 reassign 570544 qemu-system thanks On Saturday 20 of February 2010 03:49:43 Marco d'Itri wrote: Upgrade kvm. Read the udev changelog. I actually have the latest qemu in unstable. After going through the changelog and the related bug reports I found that this bug is fixed in the qemu-kvm package, but not in qemu-system, which also has kvm support and is the one that I am using currently. So, I reopen and reassign this bug to qemu-system. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570544: udev: /dev/kvm no longer belongs to the kvm group and breaks libvirt
Package: udev Version: 150-2 Severity: normal Hi, Recently, after a reboot, I had a problem starting my kvm virtual machines with libvirt. After some research I found out that libvirt attempts to start qemu as the user libvirt-qemu (uid 112) and group kvm, which has no permission to access /dev/kvm and fails. I can temporarily fix this by running chown root:kvm /dev/kvm, but after a reboot it requires doing this again. Regards, George -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 36 lrwxrwxrwx 1 root root 19 May 14 2008 025_libgphoto2.rules - ../libgphoto2.rules -rw-r--r-- 1 root root 495 May 21 2009 56-hpmud_support.rules -rw-r--r-- 1 root root 1664 Oct 9 15:50 70-persistent-cd.rules -rw-r--r-- 1 root root 325 Sep 30 14:36 70-persistent-net.rules -rw-r--r-- 1 root root 283 Mar 25 2009 85_dmraid.rules lrwxrwxrwx 1 root root 15 Dec 22 12:10 libnjb.rules - ../libnjb.rules -rw-r--r-- 1 root root 649 Apr 2 2009 xpp.rules -rw-r--r-- 1 root root 51 May 31 2009 z60_dahdi-linux.dahdi.rules lrwxrwxrwx 1 root root 15 May 15 2008 z60_hdparm.rules - ../hdparm.rules -rw-r--r-- 1 root root 5354 Mar 17 2009 z60_hplip.rules -rw-r--r-- 1 root root 806 Jun 11 2009 z60_libvpb0.vtcore.rules -- /sys/: /sys/dev /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3/dev /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2/dev /sys/devices/pci:00/:00:01.0/:01:05.0/drm/card0/dev /sys/devices/pci:00/:00:01.0/:01:05.1/sound/card1/controlC1/dev /sys/devices/pci:00/:00:01.0/:01:05.1/sound/card1/hwC1D0/dev /sys/devices/pci:00/:00:01.0/:01:05.1/sound/card1/mixer1/dev /sys/devices/pci:00/:00:01.0/:01:05.1/sound/card1/pcmC1D3p/dev /sys/devices/pci:00/:00:11.0/host0/target0:0:0/0:0:0:0/block/sda/dev /sys/devices/pci:00/:00:11.0/host0/target0:0:0/0:0:0:0/block/sda/sda1/dev /sys/devices/pci:00/:00:11.0/host0/target0:0:0/0:0:0:0/block/sda/sda2/dev /sys/devices/pci:00/:00:11.0/host0/target0:0:0/0:0:0:0/bsg/0:0:0:0/dev /sys/devices/pci:00/:00:11.0/host2/target2:0:0/2:0:0:0/block/sdb/dev /sys/devices/pci:00/:00:11.0/host2/target2:0:0/2:0:0:0/block/sdb/sdb1/dev /sys/devices/pci:00/:00:11.0/host2/target2:0:0/2:0:0:0/bsg/2:0:0:0/dev /sys/devices/pci:00/:00:12.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:43/0005:046D:B008.000C/hidraw/hidraw1/dev /sys/devices/pci:00/:00:12.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:43/input16/event6/dev /sys/devices/pci:00/:00:12.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:43/input16/mouse1/dev /sys/devices/pci:00/:00:12.0/usb3/3-1/dev /sys/devices/pci:00/:00:12.0/usb3/3-2/3-2:1.0/0003:051D:0002.0001/hidraw/hidraw0/dev /sys/devices/pci:00/:00:12.0/usb3/3-2/3-2:1.0/usb/hiddev0/dev /sys/devices/pci:00/:00:12.0/usb3/3-2/dev /sys/devices/pci:00/:00:12.0/usb3/dev /sys/devices/pci:00/:00:12.1/usb4/dev /sys/devices/pci:00/:00:12.2/usb1/dev /sys/devices/pci:00/:00:13.0/usb5/dev /sys/devices/pci:00/:00:13.1/usb6/dev /sys/devices/pci:00/:00:13.2/usb2/dev /sys/devices/pci:00/:00:14.1/ide0/0.0/block/hda/dev /sys/devices/pci:00/:00:14.2/input/input5/event5/dev /sys/devices/pci:00/:00:14.2/sound/card0/adsp/dev /sys/devices/pci:00/:00:14.2/sound/card0/audio/dev /sys/devices/pci:00/:00:14.2/sound/card0/controlC0/dev /sys/devices/pci:00/:00:14.2/sound/card0/dsp/dev /sys/devices/pci:00/:00:14.2/sound/card0/hwC0D0/dev /sys/devices/pci:00/:00:14.2/sound/card0/mixer/dev /sys/devices/pci:00/:00:14.2/sound/card0/pcmC0D0c/dev /sys/devices/pci:00/:00:14.2/sound/card0/pcmC0D0p/dev /sys/devices/pci:00/:00:14.2/sound/card0/pcmC0D1c/dev /sys/devices/pci:00/:00:14.2/sound/card0/pcmC0D1p/dev /sys/devices/pci:00/:00:14.2/sound/card0/pcmC0D2c/dev /sys/devices/pci:00/:00:14.4/:03:0e.0/fw0/dev /sys/devices/pci:00/:00:14.5/usb7/dev /sys/devices/platform/i8042/serio0/input/input1/event1/dev /sys/devices/platform/pcspkr/input/input4/event4/dev /sys/devices/platform/serial8250/tty/ttyS1/dev /sys/devices/platform/serial8250/tty/ttyS2/dev /sys/devices/platform/serial8250/tty/ttyS3/dev /sys/devices/platform/vesafb.0/graphics/fb0/dev /sys/devices/pnp0/00:05/rtc/rtc0/dev /sys/devices/pnp0/00:08/tty/ttyS0/dev /sys/devices/pnp0/00:09/ppdev/parport0/dev /sys/devices/pnp0/00:09/printer/lp0/dev /sys/devices/virtual/block/dm-0/dev /sys/devices/virtual/block/dm-1/dev /sys/devices/virtual/block/dm-10/dev /sys/devices/virtual/block/dm-11/dev /sys/devices/virtual/block/dm-12/dev /sys/devices/virtual/block/dm-13/dev /sys/devices/virtual/block/dm-14/dev /sys/devices/virtual/block/dm-15/dev /sys/devices/virtual/block/dm-2/dev /sys/devices/virtual/block/dm-3/dev /sys/devices/virtual/block/dm-4/dev /sys/devices/virtual/block/dm-5/dev /sys/devices/virtual/block/dm-6/dev
Bug#563155: [Pkg-kde-extras] Bug#563155: Bug#563155: partitionmanager: does not start, and several zombie processes appear
On Thu, Jan 14, 2010 at 4:17 PM, Jan Jabbery janjab...@gmail.com wrote: Hi George, thanks for your help. I did the strace and the ps aux, but didn't have a chance to reply. I am attaching the files as a .tar.gz, hope that's OK. There are, however, some news for me. I made an updated version of my Debian LiveCD, and partitionmanager now starts normally, and it seems like there are no zombie processes anymore... Best regards, Jan Hi, Looking at the strace log it seems that partitionmanager hangs while trying to read the floppy drive: 2868 open(/dev/fd0, O_RDWR|O_DIRECT|O_LARGEFILE) = -1 EROFS (Read-only file system) 2868 open(/dev/fd0, O_RDONLY|O_DIRECT|O_LARGEFILE) = 9 ... 2868 _llseek(9, 0, [0], SEEK_SET) = 0 2868 read(9, 0x9d89200, 512) = -1 EIO (Input/output error) 2868 _llseek(9, 0, [0], SEEK_SET) = 0 2868 read(9, 0x9d87a00, 512) = -1 EIO (Input/output error) 2868 _llseek(9, 512, [512], SEEK_SET) = 0 2868 read(9, 0x9d87a00, 512) = -1 EIO (Input/output error) 2868 _llseek(9, 1024, [1024], SEEK_SET) = 0 2868 read(9, 0x9d87a00, 512) = -1 EIO (Input/output error) 2868 _llseek(9, 1536, [1536], SEEK_SET) = 0 2868 read(9, 0x9d87a00, 512) = -1 EIO (Input/output error) 2868 _llseek(9, 2048, [2048], SEEK_SET) = 0 2868 read(9, 0x9d87a00, 512) = -1 EIO (Input/output error) 2868 _llseek(9, 2560, [2560], SEEK_SET) = 0 2868 read(9, 0x9d87a00, 512) = -1 EIO (Input/output error) I assume that you have no floppy drive, right? In this case you should disable the floppy controller from the bios or blacklist the floppy kernel module, or something like that. The problem imho is in the floppy module. It should not allow you to open /dev/fd0 if there is no floppy drive, but maybe there is a hardware limitation there (i.e. it cannot detect whether there is a floppy drive or not) and there is nothing better that it can do. Maybe if you leave it running for a few minutes, it will finally pass this stage and open its window. I bet gparted also suffers from this problem, as the filesystem detection code is in libparted, which is also used by gparted. Regarding the zombie processes, it's a bug in Qt. Partitionmanager tries to find whether several partitioning/filesystem utilities are installed on the system by executing them. This involves fork() + execve(). If execve() fails (because the utility that it tries to execute is not installed on the system), this process will be left as a zombie because of a bug in QProcess. In your case, I guess the new live cd that you built has all the utilities required, so that's why there are no zombie processes left around. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-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
clone 563155 -1 reassign -1 libqtcore4 retitle -1 QProcess: when starting a non-existent application, a zombie process appears severity -1 normal affects -1 partitionmanager tags -1 upstream forwarded -1 http://bugreports.qt.nokia.com/browse/QTBUG-5990 thanks The issue with the zombie processes is indeed a Qt bug. See http://bugreports.qt.nokia.com/browse/QTBUG-5990 Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562026: [Pkg-utopia-maintainers] Bug#562026: [PATCH] Re: Bug#562026: kdm cannot open ConsoleKit session on first login attempt
On Thu, Dec 31, 2009 at 2:17 AM, Michael Biebl bi...@debian.org wrote: George Kiagiadakis wrote: So, I have modified console-kit-daemon a bit, so that it registers Manager before it registers the service name and it works fine. Patch attached. Hi, upstream already has a fix for this in current Git master: http://cgit.freedesktop.org/ConsoleKit/commit/?id=2418840248f07025ad0edc96ed17e03ce5e47f3e I would prefer to pull the patch from upstream Git. Can you confirm that the above patch also works for you? Yes, it works. It's almost the same patch after all :) Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562026: [PATCH] Re: Bug#562026: kdm cannot open ConsoleKit session on first login attempt
reassign 562026 consolekit 0.4.1-2
tags 562026 + patch
thanks
After some hours of debugging, I finally found the cause of this bug. It is a
race condition, so no wonder why it is only reproducable on some systems.
What happens is:
1) kdm (or whatever else, I can even reproduce the bug with dbus-send) tries
to call a method from the /org/freedesktop/ConsoleKit/Manager object, using
the org.freedesktop.ConsoleKit.Manager interface.
2) ConsoleKit is not running, so dbus-daemon activates it.
3) console-kit-daemon starts and registers the service.
4) dbus-daemon recognizes the service registration, tries to find the Manager
object, fails, returns error.
5) console-kit-daemon registers the Manager object at the same time that dbus-
daemon returns the error.
Second call to the same method obviously succeeds.
Now if you are lucky the kernel scheduler gives some more time to console-kit-
daemon before it switches back to executing dbus-daemon code, it will succeed.
I guess there was a change in the scheduler of linux 2.6.32 that made this bug
more easy to spot.
So, I have modified console-kit-daemon a bit, so that it registers Manager
before it registers the service name and it works fine. Patch attached.
Regards,
George
PS: This patch of course requires 04-defer_daemonizing.patch from the
consolekit packaging to be applied as well.
This is to register the Manager object on dbus before registering
the service name, so that when calling a method on Manager and
dbus has to activate ConsoleKit, the Manager is available immediately
after the service registration. Otherwise, the remote method call
will fail with a message saying that the Manager interface doesn't exist.
This is a race condition and may not be reproducable on all systems.
Index: consolekit/src/main.c
===
--- consolekit.orig/src/main.c 2009-12-30 17:17:05.0 +0200
+++ consolekit/src/main.c 2009-12-30 17:17:36.0 +0200
@@ -338,6 +338,12 @@
goto out;
}
+manager = ck_manager_new ();
+
+if (manager == NULL) {
+goto out;
+}
+
if (! acquire_name_on_proxy (bus_proxy) ) {
g_warning (Could not acquire name; bailing out);
goto out;
@@ -353,12 +359,6 @@
create_pid_file ();
-manager = ck_manager_new ();
-
-if (manager == NULL) {
-goto out;
-}
-
loop = g_main_loop_new (NULL, FALSE);
g_signal_connect (bus_proxy,
Bug#562026: kdm cannot open ConsoleKit session on first login attempt
On Tue, Dec 22, 2009 at 1:08 AM, Sergiy Yegorov pra...@unixzone.org.ua wrote: Messages in /var/log/daemon.log Dec 22 00:59:25 excelsior kdm: :0[2294]: Cannot open ConsoleKit session: Unable to open session: Method OpenSessionWithParameters with signature a(sv) on interface org.freedesktop.ConsoleKit.Manager doesn't exist Dec 22 00:59:25 excelsior kdm: :0[2294]: Client start failed Dec 22 00:59:25 excelsior kdm: :0[2294]: Cannot close ConsoleKit session: Unable to close session: no session open On second login attempt - no problems. Bug reproduced on 3 different installations. I can reliably reproduce this bug on my laptop. Looks like consolekit has changed its dbus interface, as the service org.freedesktop.ConsoleKit.Manager doesn't exist indeed. There is only org.freedesktop.ConsoleKit. I will investigate further... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562196: kdm needs to enter the password twice
forcemerge 562026 562196 thanks On Wed, Dec 23, 2009 at 8:38 PM, Hans-J. Ullrich hans.ullr...@loop.de wrote: Dear developer-team, I do not know, if it is a bug or a feature, but since the last update, kdm needs to enter the password twice. When entering the first time, it seems, kdm is stopped and restarted again. Then, when I try it a second time, everything works fine. I looked into the log files, but I could not see any unusual in it. Can someone confirm this behaviour, too? I weighted this bug as minor, but it would be nice, if you could some day have a look on it. I can confirm it, see bug 562026. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562026: kdm cannot open ConsoleKit session on first login attempt
reassign 562026 libck-connector0 0.4.1-2 thanks On Thu, Dec 24, 2009 at 2:02 PM, George Kiagiadakis kiagiadakis.geo...@gmail.com wrote: On Tue, Dec 22, 2009 at 1:08 AM, Sergiy Yegorov pra...@unixzone.org.ua wrote: Messages in /var/log/daemon.log Dec 22 00:59:25 excelsior kdm: :0[2294]: Cannot open ConsoleKit session: Unable to open session: Method OpenSessionWithParameters with signature a(sv) on interface org.freedesktop.ConsoleKit.Manager doesn't exist Dec 22 00:59:25 excelsior kdm: :0[2294]: Client start failed Dec 22 00:59:25 excelsior kdm: :0[2294]: Cannot close ConsoleKit session: Unable to close session: no session open On second login attempt - no problems. Bug reproduced on 3 different installations. I can reliably reproduce this bug on my laptop. Looks like consolekit has changed its dbus interface, as the service org.freedesktop.ConsoleKit.Manager doesn't exist indeed. There is only org.freedesktop.ConsoleKit. I will investigate further... After investigation, it seems that the dbus interface is ok. org.freedesktop.ConsoleKit.Manager is an interface, not a service, and the mentioned method with that signature exists. Facts: - It only happens right after boot. - If you login to a tty prior to logging in with kdm, kdm works from the first time. - Running ps auxf from the kdm init script, I can see that consolekit is not running right before kdm starts, so it must be kdm that first uses it and activates the daemon. (I suspect the error has to do with first-time activation) - kdm does not use dbus directly, it uses the libck-connector library, so the problem is obviously not kdm's fault. Thus, I am reassigning this bug to libck-connector0. - I am also using linux 2.6.32 The related code is here: http://websvn.kde.org/branches/KDE/4.3/kdebase/workspace/kdm/backend/client.c?revision=986143view=markup (line 1325) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523450: kpackage is not maintained anymore
tags 523450 + fixed-upstream thanks KPackage has been removed from upstream KDE SC in 4.4, so, it will also be removed from debian when kdeadmin 4.4 is packaged. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#357297: This new behaviour is really annoying and really should be totally reverted as a horrible idea.
On Sunday 22 of November 2009 01:55:08 Lennart Sorensen wrote: Having xscreensaver autostart is just wrong. The way to disable it is way too complicated for most users to understand, and it still interferes with kde and gnome's own screensaver setups. Please revert this completely and never do it again. It is simply the wrong way to do things. Every desktop manager has a way to start and select screensavers. Having xscreensaver but in the way simply annoys users and confuses everyone. it is easy to enable xscreensaver from any window manager and desktop. It is currently very hard to prevent xscreensaver from running. hence the current setup is just wrong. Wrong wrong wrong. I totally agree. Most users have gnome or kde and they are totally confused when they find that their screensaver settings are not honored. I was confused myself too, it took me a week to find out that xscreensaver was running. I am a kde user, so I can talk about what a kde user faces with this setup: 1) KDE screensaver settings are not honored. Setting a different screesaver, a different timeout, disabling screensaver, they all don't work because xscreensaver always kicks in. 2) Mplayer and other video players do not stop xscreensaver for some reason (probably because they attempt to stop kscreensaver as they are running inside kde?), so you get screensavers right in the middle of movies... :@ To fix this, a user has to: 1) Find xscreensaver in the output of ps and realize that xscreensaver is not part of KDE. (Do you really expect an average user to be able to do that??) 2) Either disable it by using the complicated method with the desktop files (which requires looking in this bug report to find instructions), or purge it. So, I think autostarting xscreensaver is just wrong and must be reverted asap. Users that use xscreensaver are probably advanced enough to know how to make xscreensaver autostart. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558420: anyremote-data should replace anyremote
Package: anyremote Version: 5.0+dfsg-1 Severity: important Upgrading anyremote fails because anyremote-data does not replace anyremote: Unpacking anyremote-data (from .../anyremote-data_5.0+dfsg-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/anyremote-data_5.0+dfsg-1_all.deb (--unpack): trying to overwrite '/usr/share/anyremote/cfg-data/Server-mode/nokia-e70.cfg', which is also in package anyremote 0:4.18.1-1+b1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-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 anyremote depends on: pn anyremote-datanone (no description available) ii libbluetooth3 4.57-1 Library to use the BlueZ Linux Blu ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libdbus-1-3 1.2.16-2 simple interprocess messaging syst ii libdbus-glib-1-2 0.82-2 simple interprocess messaging syst ii libglib2.0-0 2.22.2-2 The GLib library of C routines ii libx11-6 2:1.3.2-1 X11 client-side library ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension Versions of packages anyremote recommends: ii python2.5.4-2An interactive high-level object-o Versions of packages anyremote suggests: pn anyremote-doc none (no description available) pn python-xmmsclient none (no description available) -- 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#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-dist-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-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556739: os-prober: Mounts and reads logical volumes that are already mounted in a virtual machine
Package: os-prober Version: 1.35 Severity: important Hi, I have a logical volume here that acts as the / filesystem of a kvm virtual machine running lenny. When I upgraded my kernel today, I noticed that os-prober (called from update-grub) does mount this volume trying to find an OS on it, without caring about the fact that this volume is already mounted in the virtual machine. The kernel then complains in dmesg that the filesystem is not clean/corrupt/etc, and I guess that under certain circumstances this could cause filesystem corruption and data loss. It would be wiser if os-prober could check the flags of the logical volumes before mounting them. lvs here shows that this volume is open, so this is a hint that you could use to determine if the volume should be checked or not. Regards, George -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-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 os-prober depends on: ii libc6 2.10.1-7 GNU C Library: Shared libraries os-prober recommends no packages. os-prober 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#541804: kde-icons-oxygen: no icon for reboot the computer button
2009/8/16 Mikhail Vasil'jev dlia-sp...@mail.ru: Package: kde-icons-oxygen Version: 4:4.3.0-1 Severity: normal Hello. Today I updated the kde-icons-oxygen package and found, that reboot the computer button has no icon now. You should also upgrade the rest of kde. The reboot icon changed its name in kde 4.3, so old kde versions won't find the new icon. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-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-dist-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
reassign 531976 linux-image-2.6.29-2-amd64 thanks On Friday 05 of June 2009 14:53:04 George Kiagiadakis wrote: 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. It seems I was wrong about that. I didn't remember well the situation about the 2.6.27 kernel. In fact the freezes started to occur after I upgraded to 2.6.29. I discovered this by doing some tests during the past week: bluez 4.40 + linux 2.6.29 - freezes bluez 3.36 + linux 2.6.29 - freezes bluez 4.40 + linux 2.6.27 - ok bluez 3.36 + linux 2.6.27 - ok bluez 4.40 + linux 2.6.30 - ok I am now running the last combination, a custom 2.6.30 kernel and bluez 4.40 and I have no other problems except that the mouse doesn't connect automatically with the first invocation of hidd (or with bluetooth-applet), but I can work this around for now. So, I am reassigning this bug to linux-image-2.6.29-2-amd64 (which is the kernel that freezes), as this seems to be a kernel bug and will be fixed in debian when the kernel packagers package linux 2.6.30 or later. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532399: kaboom: settings migration wizard starts for no reason after migration was done once
2009/6/9 Török Edwin edwinto...@gmail.com: Package: kaboom Version: 1.1.1 Severity: normal The first migration kde3-kde4 went smoothly with kaboom. Then, as expected I've never seen kaboom again. However since yesterday's dist-upgrade kaboom always starts up when I log in. If I press 'Cancel' it just logs me out. If I click through next-next-finish it allows me to login (and my settings seem intact), however next time I log in to KDE it starts again and wants to migrate my settings again. How do I tell kaboom that I already migrated to KDE4, and it shouldn't do anything, just let me login? Kaboom should create ~/.local/kaboom, which is an empty file that works as an indicator that the migration has run successfully. I guess for some reason it does not create this file in your system. Maybe ~/.local doesn't have enough permissions? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#502530: kmix channel settings changes - master is nulled, possibly a bug in config management.
2009/6/9 Dev Random paralel...@gmail.com: Package: kmix Version: 4:4.2.2-1 --- Please enter the report below this line. --- Kmix doesn't work - it's information on channels is nulled every (or so) login. Maybe this has nothing to do here, but lcd weather station (plasma) also does this (null config), so it may be a bug in a configuration management (kaboom?). I've purged completely my old kde3 config after the transition to kde4 (if it gives you an additional info...). I don't think this is a configuration issue. It probably has to do with alsa. Is alsa installed and configured correctly on your system? Does alsamixer work from a terminal? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532399: kaboom: settings migration wizard starts for no reason after migration was done once
2009/6/9 Török Edwin edwinto...@gmail.com: On 2009-06-09 11:27, George Kiagiadakis wrote: Kaboom should create ~/.local/kaboom, which is an empty file that works as an indicator that the migration has run successfully. I guess for some reason it does not create this file in your system. Maybe ~/.local doesn't have enough permissions? Well, I've deleted .local once, because it didn't seem to contain anything useful. There is an empty kaboom file in .local though: -rw-r--r-- 1 edwin edwin 0 2009-06-09 09:06 /home/edwin/.local/kaboom If the file exists, then I don't understand why kaboom starts... The code in startkde is pretty clear: if [ ! -f $HOME/.local/kaboom ] then kaboom -style plastique RET=$? if [ $RET != 0 ] then exit $RET fi fi The first if clause makes sure not to start kaboom if the file exists, and additionally, kaboom internally checks this again! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532306: kdebase-workspace: Screen corruption in VNC sessions
tag 532306 + wontfix thanks Hi, Upstream plasma developers have no intention of fixing this bug, as they believe it is a bug in the vnc servers and not in plasma. See https://bugs.kde.org/show_bug.cgi?id=183974#c2. If you object to this solution, please discuss it with upstream developers. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532417: kdebase-workspace: Please add ETA to File Copying progress
tag 532417 + fixed-upstream thanks Implemented in 4.3. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522948: Bug fixed
forcemerge 520426 522948 thanks This bug is the same as #520426, which has been fixed. -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531976: [Pkg-bluetooth-maintainers] Bug#531976: bluez: Occasionally the kernel freezes while connecting bluetooth mouse
On Friday 05 of June 2009 18:58:08 Filippo Giunchedi wrote: Does hidd come from bluez? It is not in bluez anymore but in bluez-compat as it is deprecated. Anyhow, you should be able to pair your mouse with e.g. gnome-bluetooth (via bluetooth-applet) after that it is supposed to reconnect itself. Yes, hidd comes from bluez-compat. Sorry for reporting to the wrong package. I am used to doing this from console and I couldn't find any other tool similar to hidd, so I installed bluez-compat. gnome-bluetooth is not the optimal solution for me as I am a kde user and kde-bluetooth does not work for some reason... Anyway, I will try doing this with gnome-bluetooth to see if this is a specific issue with hidd and will let you know. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530358: [Pkg-kde-extras] Bug#530358: kmess: the '' characters appears in the chat window before every message
tags 530358 + fixed-upstream thanks This is already fixed upstream in beta 2. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524506: systemsettings: keyboard settings module is missing in 4.2.2
Hi again, Thanks to the help of a guy in irc, I have tracked down the issue to be caused by the package capplets-data. That package installs the file /usr/share/applications/keyboard.desktop, which has the same name as the keyboard.desktop shipped by kde and also it has a OnlyShowIn=GNOME entry. So, when the corresponding kdelibs code tries to find the keyboard module, it looks first in /usr/share/applications and finds this file instead of the one in /usr/share/kde4/services/. Then it reads the OnlyShowIn=GNOME entry and it refuses to load the module. Unfortunately, I have no idea what would be the proper solution to solve this problem. As a temporary workaround, you can uninstall capplets-data (which will probably uninstall most gnome-related packages, though). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524506: systemsettings: keyboard settings module is missing in 4.2.2
tags 524506 + fixed-upstream thanks To my surprise, this has been recently fixed in KDE upstream. The fix will appear in KDE 4.2.3. See http://bugs.kde.org/show_bug.cgi?id=169710 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525000: kmail: Kmail always send from default account
2009/4/21 Arnaud Battistella arnaud...@gmail.com: Hi, Kmail always send email from the default account regardless of the choice of identity. Even when replying to an email sent to a non-default account, kmail uses the default account to reply. Let me know if you need other information. Thanks a lot for your work! A. It works fine for me. In the composer window, select View-Identity and then select an identity from the drop-down list that appears above the To: field. This should send the email with the specified identity. Did you do that and didn't work? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524821: /usr/bin/plasma: Plasma loses minimized windows when show only minimized windows is selected.
2009/4/20 Hakan BAYINDIR hbayin...@gmail.com: Package: kdebase-workspace-bin Version: 4:4.2.2-2 Severity: normal File: /usr/bin/plasma When show only tasks that are minimized is selected under taskbar settings in plasma, all window buttons including minimized windows disappear. Present windows plugin is still able to present all windows. It's notable that some GTK applications' windows (such as pidgin's chat windows) vanish to background of the desktop rather than the taskbar area when the option is selected and the window is minimized. This behaviour is not observed in QT4 applications such as konsole under same circumstances. Maybe you are using compiz instead of kwin? It sounds like a window manager issue. It works for me using kwin. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524506: systemsettings: keyboard settings module is missing in 4.2.2
2009/4/19 Paul Pogonyshev pogonys...@gmx.net: On Sunday 19 April 2009 01:05:59 George Kiagiadakis wrote: I'm sorry I didn't make this clear, I actually wanted to know if after running this command keyboard settings work or not. As far as I understand, the answer is that they still don't work, right? So, let me do another question, can you open keyboard settings using kcmshell4 keyboard? If not, what output do you get on the console and any window(s) that may appear? I get no output and no windows appear. For comparison: Hi, I actually had forgotten that debian disables by default debugging output for kde4 programs, so here are some additional steps: Run kdebugdialog, do a search for kcm and select area 780 kcmshell (kdelibs) from the list that appears. Click ok. Then try again to run kcmshell4 keyboard and see what is the output now. Hopefully, it should give a more useful debugging message. If there is still no debugging output, maybe it would be useful to select all the areas from kdebugdialog (using the select all button) and try again. When you have finished, you can safely disable again any debug areas that you enabled. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524506: systemsettings: keyboard settings module is missing in 4.2.2
2009/4/21 Paul Pogonyshev pogonys...@gmx.net: I actually had forgotten that debian disables by default debugging output for kde4 programs, so here are some additional steps: [...] This is the output I get with only 780 enabled: $ kcmshell4 keyboard kcmshell(22056)/kcmshell (kdelibs) locateModule: keyboard should not be loaded. And this is with all debug areas enabled: $ kcmshell4 keyboard kcmshell(22056)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from /var/tmp/kdecache-paul/ksycoca4 kcmshell(22056)/kcmshell (kdelibs) locateModule: keyboard should not be loaded. Hope this helps. Thanks, that helped a lot. This error message can appear in two cases: The first case is if /usr/share/kde4/services/keyboard.desktop has a line that reads either NoDisplay=true, or OnlyShowIn=foo (where foo is not KDE), or NotShowIn=KDE. However, this is not the case here as this file is distributed by the packages and I can see here that it doesn't have such a line. The second case is if the module is locked by the kiosk framework. I could reproduce this by adding the following lines in ~/.kde/share/config/kdeglobals: [KDE Control Module Restrictions] keyboard.desktop=false So, could you please check if this file contains such an entry on your setup? Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524506: systemsettings: keyboard settings module is missing in 4.2.2
2009/4/18 Paul Pogonyshev pogonys...@gmx.net: On Saturday 18 April 2009 00:41:54 George Kiagiadakis wrote: What happens if you run kbuildsycoca4 --noincremental as a user (i.e. not as root)? I get the following output, no idea what should actually happen: I'm sorry I didn't make this clear, I actually wanted to know if after running this command keyboard settings work or not. As far as I understand, the answer is that they still don't work, right? So, let me do another question, can you open keyboard settings using kcmshell4 keyboard? If not, what output do you get on the console and any window(s) that may appear? Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524506: systemsettings: keyboard settings module is missing in 4.2.2
2009/4/17 Paul Pogonyshev pogonys...@gmx.net: Package: systemsettings Version: 4:4.2.2-2 Severity: important After upgrading to 4.2.2 I miss keyboard settings module. This makes it impossible to alter keyboard repeat delay (it is reset to some default value, probably as a part of migration of settings from ~/.kde4 to ~/.kde) and makes using the keyboard extremely annoying. At https://bugs.kde.org/show_bug.cgi?id=189822 upstream developers suggested this is a bug in packaging, not in KDE itself. What happens if you run kbuildsycoca4 --noincremental as a user (i.e. not as root)? This module works fine for me and from a quick look that I had, the packages install the required files for this module (in package kdebase-workspace-bin), so I don't understand what else can be wrong there. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524102: libsubtitleeditor0: missing Replaces: subtitleeditor
Package: libsubtitleeditor0 Version: 0.30.0-1 Severity: normal During upgrade, dpkg complains about that: Selecting previously deselected package libsubtitleeditor0. Unpacking libsubtitleeditor0 (from .../libsubtitleeditor0_0.30.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libsubtitleeditor0_0.30.0-1_amd64.deb (--unpack): trying to overwrite `/usr/share/subtitleeditor/menubar.xml', which is also in package subtitleeditor dpkg-deb: subprocess paste killed by signal (Broken pipe) Trying to install libsubtitleeditor0 after that works correctly. So, the package is obviously missing a Replaces: subtitleeditor line in control. Regards -- 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.27.5-gkserver (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 libsubtitleeditor0 depends on: ii libatk1.0-0 1.24.0-2 The ATK accessibility toolkit ii libc6 2.9-7GNU C Library: Shared libraries ii libcairo2 1.8.6-2+b1 The Cairo 2D vector graphics libra ii libcairomm-1.0-11.8.0-1 C++ wrappers for Cairo (shared lib ii libenchant1c2a 1.4.2-3.3a wrapper library for various spel ii libfontconfig1 2.6.0-3 generic font configuration library ii libfreetype62.3.9-4 FreeType 2 font engine, shared lib ii libgcc1 1:4.3.3-5GCC support library ii libglade2-0 1:2.6.4-1library to load .glade files at ru ii libglademm-2.4-1c2a 2.6.7-1 C++ wrappers for libglade2 (shared ii libglib2.0-02.20.1-1 The GLib library of C routines ii libglibmm-2.4-1c2a 2.20.0-1 C++ wrapper for the GLib toolkit ( ii libgtk2.0-0 2.14.7-5 The GTK+ graphical user interface ii libgtkmm-2.4-1c2a 1:2.14.3-2 C++ wrappers for GTK+ 2.4 (shared ii libpango1.0-0 1.24.0-3 Layout and rendering of internatio ii libpangomm-1.4-12.24.0-2 C++ Wrapper for pango (shared libr ii libsigc++-2.0-0c2a 2.0.18-2 type-safe Signal Framework for C++ ii libstdc++6 4.3.3-5 The GNU Standard C++ Library v3 ii libxml++2.6-2 2.24.3-1 A C++ interface to the GNOME XML l ii libxml2 2.7.3.dfsg-1 GNOME XML library libsubtitleeditor0 recommends no packages. libsubtitleeditor0 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#523944: kdelibs5: every kde application segmentation faults (krusader, amarok, systemsettings....etc)
2009/4/13 ile ile.nob...@gmail.com: ii libqt4-dbus 4.5.0~rc1-2 Qt 4 D-Bus module ii libqt4-designer 4.5.0~rc1-2 Qt 4 designer module ii libqt4-network 4.5.0~rc1-2 Qt 4 network module ii libqt4-qt3support 4.5.0~rc1-2 Qt 3 compatibility library for Qt ii libqt4-script 4.5.0~rc1-2 Qt 4 script module ii libqt4-svg 4.5.0~rc1-2 Qt 4 SVG module ii libqt4-xml 4.5.0~rc1-2 Qt 4 XML module ii libqtcore4 4.5.0~rc1-2 Qt 4 core module ii libqtgui4 4.5.0~rc1-2 Qt 4 GUI module Please upgrade those qt packages to the latest 4.5.0-2 version. The crash is probably caused by that. More accurately, the crash is probably caused by patch 24_runtime_qt45_locale_initialization.diff in kde4libs, which assumes that you have either Qt 4.4.x or Qt 4.5.0 or later (not 4.5.0-rc). If the problem still persists, install kdelibs5-dbg and retry getting a backtrace from gdb. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#471565: dbus-daemon segfaults
I'm getting a similar crash sometimes. This week it happened twice and it has happened in the past too... For me, the *user* dbus-daemon segfaults, making my kde4 desktop unusable (keyboard shortcuts stop working, communication with kded4, knotify4, klauncher, krunner and kio slaves is broken, I can't start new apps, etc...). The error in dmesg is: dbus-daemon[18614]: segfault at 7f1173558720 ip 7f1172416a92 sp 7fff7afb60c8 error 4 in libc-2.7.so[7f117239c000+14a000] This is a very annoying bug. Each time it happens, I have to kill X by ctrl+alt+backspace (logout doesn't work, it requires dbus!) and then login in a vt and start killing the remaining kde processes that are not killed with Xorg for some reason. These are knotify4, kwrited, krunner, artsd and kmail, which requires SIGKILL instead of SIGTERM for some reason... Unfortunately I can't find any way to debug this. dbus-daemon doesn't seem to keep any logs and there is no standard way of reproducing, so that I can attach a gdb, crash it and get a backtrace. Even if I could, dbus-daemon comes packaged without debug symbols, so that makes it even harder... These bug reports seem related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495894 https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/237527 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#512097: ITP: partitionmanager -- KDE Partition Manager
retitle 512097 ITP: partitionmanager -- KDE Partition Manager owner 512097 ! thanks Hi, I'm already working on this package. I hope it will be available soon. Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#507509: subtitleeditor: crashes when opening any subtitle file
Hi, I've found what was causing the problem. KDE 4 exports the variable MALLOC_CHECK_=2 when it starts. According to the glibc docs [1], this variable enables heap corruption checking and with the value 2, it aborts when such a corruption is detected. Setting this variable to 1 before opening subtitleeditor makes it work and outputs this to the console: *** glibc detected *** subtitleeditor: free(): invalid pointer: 0x00cc8e80 *** Setting the value to 0 it works without any further problems. I hope that the next version will not have this heap corruption, so that KDE4 users can run subtitleeditor without having to export MALLOC_CHECK_=0 before starting it... Regards, George [1]. http://www.gnu.org/software/libtool/manual/libc/Heap-Consistency- Checking.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#488555: kvm 82 available
On Sunday 11 January 2009 18:32:49 Guido Günther wrote: Hi George, there's kvm 82 available now in experimental. Does this help with your vista boot problems? -- Guido Hi, Unfortunately, it still doesn't solve the problem. However, I did some more research in the mailing lists and I found this post: http://www.mail-archive.com/k...@vger.kernel.org/msg06959.html He says that using an older bios.bin solves the problem. So I copied /usr/share/kvm in a directory in my home, I extracted bios.bin from the kvm-66 package and replaced it in this directory, then I run: $ kvm -m 768 -L path/to/old/bios/dir vista.qcow2 ...and it works!!! So, the real problem is in the bios file. I hope this helps to track down the issue. That user in the mailing list points to a specific commit, which was indeed between kvm-69 and kvm-70. As a sidenote, booting vista with --no-kvm works too now (I mean now with kvm-82, not with the old bios.bin), but this is rather unrelated I guess... Regards, George -- To UNSUBSCRIBE, email to debian-bugs-dist-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: 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#488555: kvm regression: Vista x86_64 fails to boot with kvm 70 and above but boots fine with 69
On Thursday 27 November 2008 11:01:38 you wrote: Hi George, It's strange, because with kvm-69 vista x86_64 was working perfectly... Too bad I can't find the kvm-69 .deb anymore :( Did you check archive.debian.org? I checked both archive.debian.org and snapshots.debian.net. archive holds very old releases (sarge and previous) and snapshots is not updated anymore. The last version I can find is kvm-66. Anyway, I tried kvm-66 now and it works fine! :D Could you try each of the magic -no-kvm, -no-kvm-irqchip and -no-kvm-pit optins? No need to reinstall, just trying to boot the installed system should be sufficient. -no-kvm makes it boot, but it shows a classic windows blue screen of death shortly after loading the kernel. Exactly the same happens in plain qemu 0.9.1. -no-kvm-irqchip and -no-kvm-pit make no difference at all. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488555: please retest with kvm 72/79
I am really sorry that it took me so long to reply to Jan Lubbe's reply, it's just that I was not subscribed to the bug and I wasn't notified when he answered. Last time I tried with kvm-72+dfsg-2 (the current version in lenny), it didn't work. At the moment I don't have this virtual machine image anymore, but I can try again to install vista on kvm using kvm-69 and upgrade to kvm-72 or kvm-79 to see what happens. I'll keep you informed. Regards, George -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488555: kvm regression: Vista x86_64 fails to boot with kvm 70 and above but boots fine with 69
Ok here are my results: First I installed vista x86_64 on kvm-72. The installation went fine, and when it rebooted for the first time to complete the installation, it worked like a charm. After the installation, I shut down the vm and tried to launch it again. Result: doesn't boot (again, shows this screen with random characters and eats 100% cpu) I tried to upgrade to kvm-79 from experimental, but still the same problem, although it looks a bit different. The resulting random-character screen looks different and it doesn't eat cpu at all while it shows it. (Notice: random is not really random... the screen is the same every time I try to boot it, but what I mean is that it just doesn't show something specific. I am attaching a screenshot) Then I installed vista x86 on kvm-79. Again, the installation works, it reboots for the first time just fine and then it doesn't work. Same problem. It's strange, because with kvm-69 vista x86_64 was working perfectly... Too bad I can't find the kvm-69 .deb anymore :( PS: Note that I tried vista service pack 1, just in case it matters... attachment: kvm-vista64.png
Bug#498371: /usr/lib/libkmailprivate.so.4: undefined symbol: _ZN4KPIM8KMeditor18insertFromMimeDataEPK9QMimeData
Package: kmail Version: 4:4.1.1-1 Severity: serious Justification: Sune says it's serious ;) The original description of the bug can be found here: http://bugs.kde.org/show_bug.cgi?id=170447 The thing is that libkdepim 4.1.1 contains one more function than 4.1.0 and libkmailprivate uses that, but the kmail package does not depend on libkdepim = 4.1.1, just on 4.1.0. This causes this undefined symbol error. The commit that added the function is: http://websvn.kde.org/?view=revrevision=841028 -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (120, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-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 kmail depends on: ii kdebase-runtime 4:4.1.1-1 runtime components from the offici ii kdelibs5 4:4.1.1-1 core libraries for all KDE 4 appli ii kdepimlibs5 4:4.1.1-1 core libraries for KDE PIM 4 appli ii libc6 2.7-13 GNU C Library: Shared libraries ii libgcc1 1:4.3.1-9 GCC support library ii libkdepim44:4.1.1-1 KDE PIM library ii libkleo4 4:4.1.1-1 certificate based crypto library f ii libkpgp4 4:4.1.1-1 gpg based crypto library for KDE ii libksieve44:4.1.1-1 KDE mail/news message filtering li ii libmimelib4 4:4.1.1-1 KDE mime library ii libphonon44:4.2.0-1 Phonon multimedia framework for Qt ii libqt4-dbus 4.4.1-1Qt 4 D-Bus module ii libqt4-network4.4.1-1Qt 4 network module ii libqt4-qt3support 4.4.1-1Qt 3 compatibility library for Qt ii libqt4-xml4.4.1-1Qt 4 XML module ii libqtcore44.4.1-1Qt 4 core module ii libqtgui4 4.4.1-1Qt 4 GUI module ii libstdc++64.3.1-9The GNU Standard C++ Library v3 ii perl 5.10.0-13 Larry Wall's Practical Extraction ii phonon4:4.2.0-1 metapackage for Phonon multimedia Versions of packages kmail recommends: ii procmail 3.22-16Versatile e-mail processor Versions of packages kmail suggests: pn clamav | f-prot-installer none (no description available) ii gnupg 1.4.9-3GNU privacy guard - a free PGP rep ii gnupg-agent 2.0.9-3GNU privacy guard - password agent ii kaddressbook 4:4.1.1-1 KDE address book ii kleopatra 4:4.1.1-1 KDE Certificate Manager ii pinentry-gtk2 [pinentry-x11] 0.7.5-2GTK+-2-based PIN or pass-phrase en pn spamassassin | bogofilter | a none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494427: plasma: emptying trash from the trash plasmoid does not notify about trash changes
On Friday 05 September 2008 12:54:33 Ana Guerrero wrote: Thanks for the patch! Please, submit it to bugs.kde.org so it can get applied direclty in KDE's SVN. Ana I think you completely missed the point here. Upstream, it works fine. It's debian's patches that rename ktrash to ktrash4 and create the necessity to also apply this patch! See patch 03_ktrash4.diff in kdebase-runtime. Thanks, George -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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#494427: plasma: emptying trash from the trash plasmoid does not notify about trash changes
Package: kdebase-workspace Version: 4:4.1.0-1 Severity: normal Tags: patch Steps to reproduce: 1) Have an empty trash 2) delete something from dolphin 3) go to trash in dolphin 4) click to empty trash from the trash plasmoid. You will notice that the trash plasmoid still says that there are items in trash and dolphin still shows those items. If you press f5 to reload dolphin, the items will disappear but the trash plasmoid will remain like this forever. The problem relies in the fact that dolphin calls directly ktrash to empty the trash and ktrash in turn uses dbus to notify other processes about the changes. However, in debian, ktrash from kde4 is renamed to ktrash4 and as a result, the kde3 version of ktrash is called. This sends the signal over dcop and kde4 processes never get informed. This patch should solve the issue: == diff -uprN kdebase-workspace-4.1.0/plasma/applets/trash/trash.cpp kdebase-workspace-4.1.0-fixed/plasma/applets/trash/trash.cpp --- kdebase-workspace-4.1.0/plasma/applets/trash/trash.cpp 2008-07-15 22:48:49.0 +0300 +++ kdebase-workspace-4.1.0-fixed/plasma/applets/trash/trash.cpp 2008-08-09 14:38:12.0 +0300 @@ -193,7 +193,7 @@ void Trash::slotEmpty() // we can simply call ktrash. //KonqOperations::emptyTrash(m_menu); KProcess process; -process KStandardDirs::findExe(ktrash) --empty; +process KStandardDirs::findExe(ktrash4) --empty; process.execute(); } == -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-gkserver-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 kdebase-workspace depends on: ii kde-window-manager4:4.1.0-1 the KDE 4 window manager (KWin) ii kdebase-workspace-bin 4:4.1.0-1 core binaries for the KDE 4 base w ii klipper 4:4.1.0-1 clipboard utility for KDE 4 ii ksysguard 4:4.1.0-1 System Guard for KDE 4 ii systemsettings4:4.1.0-1 KDE 4 System Settings Versions of packages kdebase-workspace recommends: ii kdebase-plasma4:4.1.0-1 plasma widgets from the KDE 4 base ii kdm 4:4.1.0-1 KDE Display Manager for X11 kdebase-workspace suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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]
Bug#488555: kvm regression: Vista fails to boot with kvm 70 but boots fine with 69
Package: kvm Version: 70+dfsg-1 Severity: important I have a windows vista ultimate 64-bit virtual machine installed with kvm 69 here. It installs, boots and works fine with kvm 69, however since I upgraded to kvm 70 today, this machine does not boot anymore. It seems to stuck in the NT bootloader. It displays an error message quickly (too quick to read) and then hangs showing a screen with random colors and symbols. Thinking that it could be a boot sector virus, I downgraded back to kvm 69 and the machine works fine again. I don't know how to provide more useful information. Please tell me if there is something I can do to help tracing the bug. -- Package-specific info: selected information from lshal(1): /proc/cpuinfo: processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD Phenom(tm) 8450 Triple-Core Processor stepping: 3 cpu MHz : 1050.000 cache size : 512 KB physical id : 0 siblings: 3 core id : 0 cpu cores : 3 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs bogomips: 4212.10 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate processor : 1 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD Phenom(tm) 8450 Triple-Core Processor stepping: 3 cpu MHz : 1050.000 cache size : 512 KB physical id : 0 siblings: 3 core id : 2 cpu cores : 3 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs bogomips: 4209.24 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate processor : 2 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD Phenom(tm) 8450 Triple-Core Processor stepping: 3 cpu MHz : 1050.000 cache size : 512 KB physical id : 0 siblings: 3 core id : 1 cpu cores : 3 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs bogomips: 4209.06 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-gkserver-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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480696: gtk-qt-engine-kde4: Conflicts with gtk-qt-engine
Package: gtk-qt-engine-kde4 Version: 1.1-1 Severity: normal Package is not coinstallable with gtk-qt-engine (the one for qt3). The error is: E: /var/cache/apt/archives/gtk-qt-engine-kde4_1.1-1_i386.deb: trying to overwrite `/usr/share/locale/it/LC_MESSAGES/gtkqtengine.mo', which is also in package gtk-qt-engine Probably this package should just replace gtk-qt-engine. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24.3 (SMP w/2 CPU cores) Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gtk-qt-engine-kde4 depends on: ii kdebase-runtime 4:4.0.72-1 runtime components from the offici ii kdelibs5 4:4.0.72-1 core libraries for all KDE 4 appli ii libbonoboui2-0 2.22.0-1The Bonobo UI library ii libc62.7-10 GNU C Library: Shared libraries ii libglib2.0-0 2.16.3-2The GLib library of C routines ii libgtk2.0-0 2.12.9-3The GTK+ graphical user interface ii libpango1.0-01.20.2-2Layout and rendering of internatio ii libqt4-gui 4.4.0~rc1-5 Qt 4 GUI module ii libqtcore4 4.4.0~rc1-5 Qt 4 core module ii libstdc++6 4.3.0-4 The GNU Standard C++ Library v3 ii libx11-6 2:1.1-2 X11 client-side library gtk-qt-engine-kde4 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465605: xserver-xorg-input-synaptics: When using xinerama, the touchpad cannot move the pointer from screen1 to screen0.
Package: xserver-xorg-input-synaptics Version: 0.14.7~git20070706-2 Severity: normal I have xinerama enabled with my laptop screen as screen0 and an external monitor as screen1, with screen1 being right of screen0. When I use the synaptics touchpad to move the pointer from screen0 to screen1, it works fine. However, if I try to move the pointer back to screen0 from screen1, the pointer stops at the left side of screen1 (which is the boundary between the two screens). This doesn't happen with a usb mouse. I can use the usb mouse to move the pointer back to screen0 without any problems. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23 (SMP w/2 CPU cores) Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-input-synaptics depends on: ii libc6 2.7-6 GNU C Library: Shared libraries ii libx11-6 2:1.1-2 X11 client-side library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxi6 2:1.1.3-1 X11 Input extension library ii xserver-xorg-core 2:1.4.1~git20080131-1 Xorg X server - core server xserver-xorg-input-synaptics recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464396: kdelibs5-doc does not contain api documentation. It is empty.
Package: kdelibs5-doc Version: 4:4.0.1-1 Severity: important The description of the package says that it contains KDE API documentation. However, the package contains only these files: /usr/share/doc/kdelibs5-doc/AUTHORS /usr/share/doc/kdelibs5-doc/copyright /usr/share/doc/kdelibs5-doc/TODO.gz /usr/share/doc/kdelibs5-doc/changelog.Debian.gz /usr/share/doc/kdelibs5-doc/README.gz This also applies to the previous version, 4:4.0.0-2 that is in lenny. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23 (SMP w/2 CPU cores) Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
