Bug#334239: koffice_1:1.3.5-5(m68k/unstable):
Package: koffice Version: 1:1.3.5-5 Severity: serious There was an error while trying to autobuild your package: > Automatic build of koffice_1:1.3.5-5 on ska by sbuild/m68k 69 > Build started at 20051014-1604 [...] > ** Using build dependencies supplied by package: > Build-Depends: g++-3.4 [arm hppa m68k], automake1.7, debhelper (>= 4.0.0), > flex, kdelibs4-dev (>= 4:3.2.0), libaspell-dev, libfontconfig1-dev, > libmagick++9-dev, libpaper-dev, libtiff4-dev, libwv2-dev (>= 0.1.9-0), > libxml2-dev, libxslt1-dev, postgresql-dev, python2.3-dev, sharutils [...] > The following central src deps are (probably) missing: > libtiff3g-dev [...] > ../../../karbon/core/vcolor.cc:294: internal compiler error: in > verify_initial_elim_offsets, at reload1.c:3297 > Please submit a full bug report, > with preprocessed source if appropriate. > See http://gcc.gnu.org/bugs.html> for instructions. > For Debian GNU/Linux specific bug reporting instructions, > see . > make[4]: *** [vcolor.lo] Error 1 > make[4]: Leaving directory > `/build/buildd/koffice-1.3.5/obj-m68k-linux-gnu/karbon/core' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory > `/build/buildd/koffice-1.3.5/obj-m68k-linux-gnu/karbon' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/build/buildd/koffice-1.3.5/obj-m68k-linux-gnu' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/build/buildd/koffice-1.3.5/obj-m68k-linux-gnu' > make: *** [build-stamp] Error 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=m68k&pkg=koffice&ver=1:1.3.5-5 I tried to build the offending file with gcc-4.0, and that succeeded; if koffice is built with g++-3.4 because it failed previously, you may want to try reverting that change on your next upload. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#781012: bluedevil: doesn't work when full KDE environment isn't installed
Package: bluedevil Version: 2.0~rc1-44-gb7697a7-3 Severity: important Hi, I'm not a fan of big desktop environments, but I do pick and choose a few useful applications from some desktop environments to run in my session. One of these is bluedevil, when I need to send something to my phone or tablet or some such. Unfortunately, this seems to have stopped working. When I invoke "bluedevil-sendfile", without argument, pick a file to send, pick a device to send to, and click on "send", a dialog box with a progress bar is shown for a short moment, but then bluedevil-sendfile quits unexpectedly. When this happens, the following shows on stdout: wouter@gangtai:~/data/audio/music/Mumford_&_Sons-Live_from_Studio_Brussel_Club_69$ bluedevil-sendfile Address: "18:1E:B0:A1:2F:BF" Name: "wouter alt" Alias: "wouter alt" Icon: "phone" ==== Address: "54:BE:F7:09:D6:8B" Name: "Wouter Verhelst (T)" Alias: "Wouter Verhelst (T)" Icon: "computer" Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QString) wouter@gangtai:~/data/audio/music/Mumford_&_Sons-Live_from_Studio_Brussel_Club_69$ Strangely enough, when I run it with a "-f" argument to select a specific file, it doesn't quit like that, but it doesn't seem to work either (it just sits there doing nothing). I suspect there's a missing dependency somewhere. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bluedevil depends on: ii bluez 5.23-2+b1 ii bluez-obexd 5.23-2+b1 ii kde-runtime 4:4.14.2-2 ii libbluedevil2 2.0~rc1-6-g7bb223c-2 ii libc6 2.19-17 ii libkdecore5 4:4.14.2-5 ii libkdeui5 4:4.14.2-5 ii libkfile4 4:4.14.2-5 ii libkio5 4:4.14.2-5 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libstdc++64.9.2-10 ii obex-data-server 0.4.5-1+b4 bluedevil recommends no packages. Versions of packages bluedevil suggests: pn pulseaudio-module-bluetooth | bluez-alsa -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150323084014.2594.37393.report...@gangtai.grep.be
Bug#808544: qt5-qmake: qmake binary in qt5-qmake doesn't use qt5
Package: qt5-qmake Version: 5.3.2+dfsg-4+deb8u1 Severity: grave Justification: renders package unusable Dear Maintainer, I've been trying to compile Mumble with qt5-qmake, but the qt5 version of qmake doesn't seem to work at alll. If I run qmake with both qt5-qmake and qt4-qmake installed, I have no option to use the qt5 version. If I run t5-qmake installed with only qt5-qmake installed I get the following result: [wouter@wouter-desktop mumble]$ qmake -v qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No such file or directory Running /usr/lib/x86_64-linux-gnu/qt5/bin/qmake directly does work and works like expected. Thanks for looking into this, Wouter Wijsman P.S. sorry if I made any mistakes, this is my first bug report. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qt5-qmake depends on: ii libc6 2.19-18+deb8u1 ii libgcc1 1:4.9.2-10 ii libstdc++6 4.9.2-10 ii qtchooser 47-gd2b7997-2 qt5-qmake recommends no packages. qt5-qmake suggests no packages. -- no debconf information
Bug#754269: persistently asks for password even when it can't do much with it
Package: korganizer Version: 4:4.12.4-1 Severity: minor File: /usr/bin/korgac Hi, I run korganizer without running the full KDE suite. This means that kwallet isn't available. As a result, when I run anything from KDE that needs a password, I need to enter it when the application starts. One of the applications in that boat are korganizer and korgac. The latter is fairly annoying, however, in that it asks a password without first checking whether it can connect to the network (or maybe it does try to check, but doesn't get an answer since I'm running wicd rather than network-manager; I haven't tried to see whether that is the case). Since my password is fairly long I tend to not enter it when I'm not connected, since that would be a waste of time anyway. However, not entering anything, or clicking cancel, doesn't cause the password dialog box to go away, as I would expect; instead, it reappears immediately, and keeps reappearing until I enter something, even if it's not correct. I think korgac should honor the "cancel" button and go away when I ask it to. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages korganizer depends on: ii kde-runtime 4:4.13.1-1 ii kdepim-runtime4:4.12.4-2 ii kdepimlibs-kio-plugins4:4.12.4-1 ii libakonadi-calendar4 4:4.12.4-1 ii libakonadi-contact4 4:4.12.4-1 ii libakonadi-kde4 4:4.12.4-1 ii libakonadi-kmime4 4:4.12.4-1 ii libc6 2.19-5 ii libcalendarsupport4 4:4.12.4-1 ii libeventviews44:4.12.4-1 ii libgcc1 1:4.9.0-10 ii libincidenceeditorsng44:4.12.4-1 ii libkabc4 4:4.12.4-1 ii libkcalcore4 4:4.12.4-1 ii libkcalutils4 4:4.12.4-1 ii libkcmutils4 4:4.13.1-1 ii libkdecore5 4:4.13.1-1 ii libkdepim44:4.12.4-1 ii libkdepimdbusinterfaces4 4:4.12.4-1 ii libkdeui5 4:4.13.1-1 ii libkholidays4 4:4.12.4-1 ii libkio5 4:4.13.1-1 ii libkmime4 4:4.12.4-1 ii libknewstuff3-4 4:4.13.1-1 ii libkontactinterface4 4:4.12.4-1 ii libkparts44:4.13.1-1 ii libkpimidentities44:4.12.4-1 ii libkpimutils4 4:4.12.4-1 ii libkprintutils4 4:4.13.1-1 ii libmailtransport4 4:4.12.4-1 ii libphonon44:4.7.1-1 ii libpimcommon4 4:4.12.4-1 ii libqt4-dbus 4:4.8.6+dfsg-2 ii libqt4-xml4:4.8.6+dfsg-2 ii libqtcore44:4.8.6+dfsg-2 ii libqtgui4 4:4.8.6+dfsg-2 ii libstdc++64.9.0-10 ii perl 5.18.2-5 ii phonon4:4.7.1-1 korganizer recommends no packages. Versions of packages korganizer suggests: ii kdepim-kresources 4:4.12.4-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140709073734.6196.68890.reportbug@localhost
Bug#557977: Remaps the window on (unexpected) disconnect, causing it to interrupt my work
Package: krdc Version: 4:4.3.2-1 Severity: normal Hi, I am currently at a customer where the security policy does not allow me to simultaneously connect my laptop to the Internet and the local LAN. However, there is a Windows Terminal server with a web browser that I can use in case I need to browse the Internet while connected to the LAN. This server is configured so that if the session has been idle for more than a certain amount of time, the connection is dropped, server-side. In itself, that's not a problem. However, it becomes a problem because this usually happens when krdc is on a different virtual desktop (otherwise I would've seen the warning that the server sends out two minutes prior to disconnecting), and upon disconnect krdc unmaps the full-screen window, and remaps a non-fullscreen but maximized window right after that, unconditionally. This remap causes it to be shown on the then-active virtual desktop, interrupting any work that I may be doing at that time. The fix to this is easy: rather than unmapping the normal window when going full-screen, it should be brought to the background. This way, when the full-screen window is removed, the maximized window does not need to be created, and will remain on the other virtual desktop. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages krdc depends on: ii kdebase-runtime 4:4.3.2-1 runtime components from the offici ii kdelibs5 4:4.3.2-2 core libraries for all KDE 4 appli ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libqt4-xml4:4.5.3-4 Qt 4 XML module ii libqtcore44:4.5.3-4 Qt 4 core module ii libqtgui4 4:4.5.3-4 Qt 4 GUI module ii libstdc++64.4.2-3The GNU Standard C++ Library v3 ii libvncserver0 0.9.7-2API to write one's own vnc server Versions of packages krdc recommends: ii rdesktop 1.6.0-3RDP client for Windows NT/2000 Ter Versions of packages krdc suggests: pn khelpcenter(no description available) pn krfb (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#364774: konsolekalendar: should output data in chronological order
Package: konsolekalendar Version: 4:3.5.2-1+b1 Severity: normal Hi, konsolekalendar orders events per day, but then orders events in the order that they were added to the database, rather than in chronological order; i.e., when I have an event at 10 AM, then add one at 9 AM, konsolekalendar will show the former before the latter. This is confusing. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-powerpc Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) Versions of packages konsolekalendar depends on: ii kdelibs4c2a 4:3.5.2-2+b1 core libraries for all KDE applica ii libart-2.0-22.3.17-1 Library of functions for 2D graphi ii libc6 2.3.6-7 GNU C Library: Shared libraries ii libgcc1 1:4.1.0-1GCC support library ii libkcal2b 4:3.5.2-1+b1 KDE calendaring library ii libkdepim1a 4:3.5.2-1+b1 KDE PIM library ii libqt3-mt 3:3.3.6-1Qt GUI Library (Threaded runtime v ii libstdc++6 4.1.0-1 The GNU Standard C++ Library v3 konsolekalendar recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#277582: ITP: kwin-baghira -- A MacOSX-like theme for Apple junkies ;)
On Fri, Oct 22, 2004 at 04:31:52AM +0200, Adeodato Simó wrote: > I would suggest a name like kde-$FOO-style to be used (e.g., > kde-baghira-style) for packages that provide a widget style for > QT/KDE, and include kwin decoration (if they exist) in the same > package. (*) For the sake of consistency, I would suggest kde-theme-$FOO. This is what enlightenment, jsboard, opie, and even previous incarnations of KDE itself use (kdeartwork-theme-*). -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune signature.asc Description: Digital signature
Re: KDE 3.1.5 Status Update - 20040119
On Mon, Jan 19, 2004 at 10:19:04PM -0600, Chris Cheney wrote: > Everything is in sid now, but the buildds FUCKING SUCK! The buildd > admins must be incompetent or on crack. They failed all the builds that > failed due to the g++ RC enum bug instead of updating their buildd and > setting the packages back to Needs-Build. sbuild doesn't update packages if it's not asked to. If you know beforehand that a package *will* fail to build with a certain compiler, you should update your build-depends and/or build-conflicts likewise, so that there won't be a failed build in the first place. sbuild (the building component of buildd) isn't pbuilder; sbuild tries to build as many packages in as little time as possible. Therefore, installed packages aren't looked at (so that time isn't wasted on them) except to check that they satisfy versioned build-depends and/or build-conflicts. > The g++ RC enum bug was already fixed before I even uploaded the > packages which shows you how slow they are to fix problems on their > machines... However, people like IJ are refused to help maintain > buildds because they have too little experience, hah! Actually, Ingo Juergensmann is just the local admin of arrakis. He doesn't help because he's not a DD, that's all. [...] > kdebase > --- > m68k - failed - needs retry This is my fault; I thought it had built on quickstep, but I seem to have messed up things. For that reason, it's not in dep-ret or needs-build ATM (where it should've been). I sent Goswin (see below) a mail, clearing that up. [...] Note that most kde packages are still in the queue for m68k; we've got quite a backlog currently[1]. That said, Goswin von Brederlow is building them, ignoring their position in the queue, thereby special-casing KDE so that it gets built sooner. [1] due to the fact that we don't have enough autobuilders ATM. There are more being set up though, so it's being handled. -- Wouter Verhelst Debian GNU/Linux -- http://www.debian.org Nederlandstalige Linux-documentatie -- http://nl.linux.org "Stop breathing down my neck." "My breathing is merely a simulation." "So is my neck, stop it anyway!" -- Voyager's EMH versus the Prometheus' EMH, stardate 51462. signature.asc Description: Digital signature
Re: strange kdepim failure on m68k build
On Fri, Apr 30, 2004 at 09:44:35AM -0500, Joaquin Ortega wrote: > > Kdepim (kdepim_4:3.2.2-2) > failed to build twice on the m68k buildd (kullervo.debian.org). It has > been labeled as failed and won't be built automatically. The reason given > on the log is > > Ouch... tries to write outside build directory: Because, indeed, it does: it tries to write to $HOME/.kde , which is outside the build directory. That's not allowed; it's a bug (even if no report has been filed). > It has only failed in this architecture. Could it be that kullervo ran > out of disk space? Unlikely; more likely is that other architectures happen to have a $HOME which actually exists inside their buildd chroots. That doesn't make your bug nonexisting there; it just happens not to hit it. You should fix this. -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune signature.asc Description: Digital signature
Re: strange kdepim failure on m68k build
On Fri, Apr 30, 2004 at 06:24:27PM +0300, Riku Voipio wrote: > On Fri, Apr 30, 2004 at 05:06:45PM +0200, Wouter Verhelst wrote: > > On Fri, Apr 30, 2004 at 09:44:35AM -0500, Joaquin Ortega wrote: > > > > > > Kdepim (kdepim_4:3.2.2-2) > > > failed to build twice on the m68k buildd (kullervo.debian.org). It has > > > been labeled as failed and won't be built automatically. The reason given > > > on the log is > > > > > > Ouch... tries to write outside build directory: > > > Because, indeed, it does: it tries to write to $HOME/.kde , which is > > outside the build directory. That's not allowed; it's a bug (even if no > > report has been filed). > > meinproc only complains if it fails to write the config files. The m68 build > is failing for some other reason. Uhm, yeah. Obviously; sorry for not paying attention. It most certainly isn't diskspace: /dev/sdc2 16G 3.9G 11G 26% /org which is what the buildd chroot lives on. I'm not sure what the problem actually is, though. -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune
Bug#771044: konsole: Konsole and Yakuake hang after selecting text and right click (dbus)
Package: konsole Version: 4:4.14.2-1 Severity: normal Hello, Konsole and Yakuake hang when selecting text in the terminal window and then right-clicking (or shift right-click for curses). The menu is never drawn. The hang-up doesn't always happen, but has manifested itself for many months so it's not a new bug. I used gdb to check what is happening and both Konsole and Yakuake seem to hang on dbus via search engine functionality in the context menu (backtrace follows). There are several related bug reports for different distributions, for instance this one from the KDE bugtracker: https://bugs.kde.org/show_bug.cgi?id=306338 I'm not sure how to track the exact reason dbus hangs. Thanks for your time, Wouter #0 0x778ec18d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fffeee04c98 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fffeee03b48 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fffeeded074 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fffeededa4d in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fffeedee02a in dbus_connection_send_with_reply_and_block () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #6 0x743b3e20 in ?? () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #7 0x7439f88b in QDBusConnection::call(QDBusMessage const&, QDBus::CallMode, int) const () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #8 0x743beea3 in QDBusAbstractInterface::callWithArgumentList(QDBus::CallMode, QString const&, QList const&) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #9 0x743c07bc in QDBusAbstractInterface::call(QDBus::CallMode, QString const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #10 0x743c0d7d in QDBusAbstractInterface::call(QString const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #11 0x763fb914 in KMimeType::favIconForUrl(KUrl const&) () from /usr/lib/libkdecore.so.5 #12 0x76f84cbd in ?? () from /usr/lib/libkio.so.5 #13 0x76f8595e in KUriFilterPlugin::iconNameFor(KUrl const&, KUriFilterData::UriTypes) const () from /usr/lib/libkio.so.5 #14 0x7fffdb49779b in ?? () from /usr/lib/kde4/kuriikwsfilter.so #15 0x7fffdb4981ef in ?? () from /usr/lib/kde4/kuriikwsfilter.so #16 0x76f87057 in KUriFilter::filterUri(KUriFilterData&, QStringList const&) () from /usr/lib/libkio.so.5 #17 0x76f87204 in KUriFilter::filterSearchUri(KUriFilterData&, QFlags) () from /usr/lib/libkio.so.5 #18 0x775a0613 in Konsole::SessionController::updateWebSearchMenu() () from /usr/lib/libkonsoleprivate.so #19 0x775a59a8 in Konsole::SessionController::showDisplayContextMenu(QPoint const&) () from /usr/lib/libkonsoleprivate.so #20 0x775a73e1 in ?? () from /usr/lib/libkonsoleprivate.so #21 0x75f30f4c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #22 0x775b5645 in Konsole::TerminalDisplay::configureRequest(QPoint const&) () from /usr/lib/libkonsoleprivate.so #23 0x775baaab in Konsole::TerminalDisplay::mousePressEvent(QMouseEvent*) () from /usr/lib/libkonsoleprivate.so #24 0x752c4057 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #25 0x775bb0fa in Konsole::TerminalDisplay::event(QEvent*) () from /usr/lib/libkonsoleprivate.so #26 0x7527029c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #27 0x75276f0f in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #28 0x769c309a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #29 0x75f1bf8d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #30 0x7527656f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #31 0x752ed0a2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #32 0x752eba9c in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #33 0x75314ad2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #34 0x70913c5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x70913f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x70913ffc in g_main_context_iteration () fr
Bug#860012: kwin-x11: kwin hangs randomly (drm:intel_pipe_update_end [i915]] Atomic update failure on pipe A)
Package: kwin-x11 Version: 4:5.8.6-1 Severity: important Hello, The last 8 months or so kwin_x11 has been hanging randomly probably at least once a day. The screen just freezes mid-operation and doesn't update anymore; but I can still switch to a non-x11 console. The hangups occur when switching desktops or on some websites in Firefox that are graphics intense or have video. I think the bug is related to the graphics driver code, because there's often a line in the logs around the time freezes happen. Here's one from today: [Mon Apr 10 11:09:48 2017] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=20652 end=20653) time 355 us, min 1192, max 1199, scanline start 1176, end 1202 The computer is a fairly old system with the Intel Q35 Chipset and uses the default Intel drivers: [drm] Initialized i915 1.6.0 20160919 for :00:02.0 on minor 0 Killing kwin from a non-X11 console (with `kwin_x11 --replace`) brings back the system – minus some programs that don't like that approach, so I assume the bug is in kwin or perhaps the Intel driver for i915. I have seen other references to "Atomic update failure on pipe ..." in bug reports in diverse places on the net, but no clear solution. Thanks for your time, Wouter -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kwin-x11 depends on: ii kwin-common 4:5.8.6-1 ii libc6 2.24-9 ii libepoxy0 1.3.1-2 ii libgcc1 1:6.3.0-11 ii libkf5configcore5 5.28.0-2 ii libkf5coreaddons5 5.28.0-2 ii libkf5crash5 5.28.0-1 ii libkf5i18n5 5.28.0-2 ii libkf5windowsystem5 5.28.0-2 ii libkwinglutils9 4:5.8.6-1 ii libkwinxrenderutils9 4:5.8.6-1 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5gui55.7.1+dfsg-3+b1 ii libqt5widgets55.7.1+dfsg-3+b1 ii libqt5x11extras5 5.7.1~20161021-2 ii libstdc++66.3.0-11 ii libx11-6 2:1.6.4-3 ii libxcb-cursor00.1.1-3 ii libxcb-randr0 1.12-1 ii libxcb-xfixes01.12-1 ii libxcb1 1.12-1 ii libxi62:1.7.9-1 kwin-x11 recommends no packages. kwin-x11 suggests no packages. -- no debconf information
Bug#641421: kmail: KMail asks for already saved (IMAP) password every time it starts up (KWallet/session interaction issues?)
Package: kmail Version: 4:4.4.11.1+l10n-1 Severity: minor Hello, KMail is started by the session manager when KDE starts up, and asks for a password (IMAP) that is already saved in KWallet. Sometimes KWallet gives a warning about a misbehaving application: "There have been repeated failed attempts to gain access to a wallet. An application may be misbehaving." The password can be found in KWallet when you check for it, so that's not the problem. I'm guessing either interaction issues between KMail and KWallet, or some sort of race condition in restoring sessions where KMail loads before or simultaneously with KWallet and requests the IMAP password before KWallet itself is unlocked: KWallet itself requests its unlock password *after* KMail requests the IMAP password, so KMail simply couldn't have checked the IMAP password from KWallet since it was still locked. I assume KMail for some reason doesn't wait until KWallet is unlocked, and hence asks the IMAP password directly from the user. What I expect and want to happen, quite logically, is that KMail uses the saved IMAP password from KWallet and doesn't ask for it to be manually entered every time. Thanks, Wouter -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kmail depends on: ii kdebase-runtime 4:4.6.5-1 ii kdepim-runtime 4:4.4.11.1-2 ii kdepimlibs-kio-plugins 4:4.6.5-1 ii libakonadi-contact4 4:4.6.5-1 ii libakonadi-kde4 4:4.6.5-1 ii libc6 2.13-20 ii libgcc1 1:4.6.1-10 ii libgpgme++2 4:4.6.5-1 ii libkabc44:4.6.5-1 ii libkcal44:4.6.5-1 ii libkcmutils44:4.6.5-2 ii libkde3support4 4:4.6.5-2 ii libkdecore5 4:4.6.5-2 ii libkdepim4 4:4.4.11.1+l10n-1 ii libkdeui5 4:4.6.5-2 ii libkhtml5 4:4.6.5-2 ii libkimap4 4:4.6.5-1 ii libkio5 4:4.6.5-2 ii libkldap4 4:4.6.5-1 ii libkleo44:4.4.11.1+l10n-1 ii libkmime4 4:4.6.5-1 ii libknotifyconfig4 4:4.6.5-2 ii libkontactinterface44:4.6.5-1 ii libkparts4 4:4.6.5-2 ii libkpgp44:4.4.11.1+l10n-1 ii libkpimidentities4 4:4.6.5-1 ii libkpimtextedit44:4.6.5-1 ii libkpimutils4 4:4.6.5-1 ii libkresources4 4:4.6.5-1 ii libksieve4 4:4.4.11.1+l10n-1 ii libktnef4 4:4.6.5-1 ii libmailtransport4 4:4.6.5-1 ii libmessagecore4 4:4.4.11.1+l10n-1 ii libmessagelist4 4:4.4.11.1+l10n-1 ii libmimelib4 4:4.4.11.1+l10n-1 ii libnepomuk4 4:4.6.5-2 ii libphonon4 4:4.6.0really4.5.0-5 ii libqt4-dbus 4:4.7.3-8 ii libqt4-network 4:4.7.3-8 ii libqt4-qt3support 4:4.7.3-8 ii libqt4-xml 4:4.7.3-8 ii libqtcore4 4:4.7.3-8 ii libqtgui4 4:4.7.3-8 ii libstdc++6 4.6.1-10 ii libthreadweaver44:4.6.5-2 ii perl5.12.4-4 ii phonon 4:4.6.0really4.5.0-5 Versions of packages kmail recommends: ii gnupg-agent 2.0.18-1 ii gnupg22.0.18-1 ii pinentry-gtk2 [pinentry-x11] 0.8.1-1 Versions of packages kmail suggests: pn clamav | f-prot-installer pn kaddressbook 4:4.4.11.1+l10n-1 pn kleopatra 4:4.4.11.1+l10n-1 pn procmail 3.22-19 pn spamassassin | bogofilter | annoyance-filter | spambayes -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110913104827.5358.71843.report...@kkv54.lib.helsinki.fi
Bug#446349: kdebase: Shutdown/reboot from KDE (with GDM) still doesn't work
Package: kdebase Followup-For: Bug #446349 Hello, Since a few months reboot/shutdown from the KDE menu (with KDE started from GDM) doesn't work anymore, apparently due to a socket path mismatch as mentioned earlier in this bug report. When will this fix appear in Debian unstable? Thanks, Wouter -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22 Locale: LANG=C, LC_CTYPE=en_GB.utf-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kdebase depends on: ii hal 0.5.10-5 Hardware Abstraction Layer ii kappfinder 4:3.5.8.dfsg.1-2 non-KDE application finder for KDE ii kate4:3.5.8.dfsg.1-2 advanced text editor for KDE ii kcontrol4:3.5.8.dfsg.1-2 control center for KDE ii kdebase-bin 4:3.5.8.dfsg.1-2 core binaries for the KDE base mod ii kdebase-data4:3.5.8.dfsg.1-4 shared data files for the KDE base ii kdebase-kio-plugins 4:3.5.8.dfsg.1-2 core I/O slaves for KDE ii kdepasswd 4:3.5.8.dfsg.1-2 password changer for KDE ii kdeprint4:3.5.8.dfsg.1-2 print system for KDE ii kdesktop4:3.5.8.dfsg.1-2 miscellaneous binaries and files f ii kfind 4:3.5.8.dfsg.1-2 file-find utility for KDE ii khelpcenter 4:3.5.8.dfsg.1-2 help center for KDE ii kicker 4:3.5.8.dfsg.1-2 desktop panel for KDE ii klipper 4:3.5.8.dfsg.1-2 clipboard utility for KDE ii kmenuedit 4:3.5.8.dfsg.1-2 menu editor for KDE ii konqueror 4:3.5.8.dfsg.1-2 KDE's advanced file manager, web b ii konqueror-nsplugins 4:3.5.8.dfsg.1-2 Netscape plugin support for Konque ii konsole 4:3.5.8.dfsg.1-2 X terminal emulator for KDE ii kpager 4:3.5.8.dfsg.1-2 desktop pager for KDE ii kpersonalizer 4:3.5.8.dfsg.1-2 installation personalizer for KDE ii ksmserver 4:3.5.8.dfsg.1-2 session manager for KDE ii ksplash 4:3.5.8.dfsg.1-2 the KDE splash screen ii ksysguard 4:3.5.8.dfsg.1-2 system guard for KDE ii ktip4:3.5.8.dfsg.1-2 useful tips for KDE ii kwin4:3.5.8.dfsg.1-2 the KDE window manager ii libkonq44:3.5.8.dfsg.1-2 core libraries for Konqueror ii pmount 0.9.16-4 mount removable devices as normal Versions of packages kdebase recommends: pn kdm(no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#640724: plasma-desktop: pager widget doesn't remember settings
Package: plasma-desktop Version: 4:4.6.5-3 Followup-For: Bug #640724 Hello, The pager widget/applet doesn't remember its settings. I have 4 workspaces in a horizontal row. In the pager applet, the setting "Number of rows:" is set to 1. When the system starts, the pager shows the workspaces in one row, but they are really arranged 2x2 and when using shortcuts, can only be switched to with left-right and up-down. When I set "Number of rows" in Pager Settings to 2, click OK, and then set it back to 1, the desktops are arranged correctly side-by-side in one row. After rebooting or restarting KDE, the pager shows 4 desktops side-by-side while they are physically arranged 2x2 (which is incorrect). Somehow, restoring the setting of "Number of rows" only applies to the pager widget and not the physical desktop layout. I expect the layout of the pager widget and the actual physical order of the workspaces to match (preferably in one row, because I'm too stupid to use 4 keys to switch workspace). Regards, Wouter -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages plasma-desktop depends on: ii kdebase-runtime 4:4.6.5-1+b1 ii libc6 2.13-21 ii libkcmutils4 4:4.6.5-2 ii libkdecore5 4:4.6.5-2 ii libkdeui5 4:4.6.5-2 ii libkephal4abi14:4.6.5-3 ii libkfile4 4:4.6.5-2 ii libkidletime4 4:4.6.5-2 ii libkio5 4:4.6.5-2 ii libknewstuff3-4 4:4.6.5-2 ii libktexteditor4 4:4.6.5-2 ii libkworkspace44:4.6.5-3 ii libplasma34:4.6.5-2 ii libplasmagenericshell44:4.6.5-3 ii libqt4-dbus 4:4.7.3-8 ii libqt4-xml4:4.7.3-8 ii libqtcore44:4.7.3-8 ii libqtgui4 4:4.7.3-8 ii libsolid4 4:4.6.5-2 ii libstdc++64.6.1-13 ii libtaskmanager4abi1 4:4.6.5-3 ii libx11-6 2:1.4.4-2 ii libxext6 2:1.3.0-3 ii plasma-widgets-workspace 4:4.6.5-3 Versions of packages plasma-desktop recommends: ii kdebase-workspace 4:4.6.5-3 plasma-desktop suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110929133136.4620.29763.report...@kkv54.lib.helsinki.fi
Bug#646584: [kdm] keyboard accelerators in shutdown menu are not honoured
Package: kdm Version: 4:4.6.5-3 Severity: normal --- Please enter the report below this line. --- Hi guys, ALT-s brings up the shutdown menu. In it, we see Restart and Turn off buttons. Their initial R and T are underlined, meaning that by pressing ALT-r or ALT-t I should be able to activate them. This used to work but does not anymore. The buttons can be activated by mouse just fine. It is the keyboard accelerators that are not honoured. With kind regards, Wouter --- System information. --- Architecture: amd64 Kernel: Linux 3.0.7.git Debian Release: wheezy/sid 990 testing the.earth.li 990 testing security.debian.org 500 unstable the.earth.li 500 stable-updates the.earth.li 500 stable the.earth.li 500 stable security.debian.org 1 experimental the.earth.li --- Package information. --- Depends (Version) | Installed ===-+-=== kdebase-runtime | 4:4.6.5-1+b1 libc6 (>= 2.3) | 2.13-21 libck-connector0 (>= 0.2.1) | 0.4.5-1 libdbus-1-3 (>= 1.0.2) | 1.4.16-1 libkdecore5 (>= 4:4.6.3) | 4:4.6.5-2 libkdeui5 (>= 4:4.6.3) | 4:4.6.5-2 libkio5 (>= 4:4.6.3) | 4:4.6.5-2 libknewstuff3-4 (>= 4:4.6.3) | 4:4.6.5-2 libkworkspace4 (= 4:4.6.5-3) | 4:4.6.5-3 libpam0g (>= 0.99.7.1) | 1.1.3-4 libqimageblitz4 (>= 1:0.0.4) | 1:0.0.6-4 libqt4-svg (>= 4:4.5.3) | 4:4.7.3-5 libqt4-xml (>= 4:4.5.3) | 4:4.7.3-5 libqtcore4 (>= 4:4.7.0~beta1) | 4:4.7.3-5 libqtgui4 (>= 4:4.5.3) | 4:4.7.3-5 libstdc++6 (>= 4.1.1) | 4.6.1-15 libx11-6 | 2:1.4.4-2 libxau6 | 1:1.0.6-3 libxdmcp6 | 1:1.1.0-3 libxtst6 | 2:1.2.0-3 debconf (>= 0.5) | 1.5.40 OR debconf-2.0 | lsb-base (>= 3.2-14) | 3.2-28 consolekit | 0.4.5-1 kdebase-workspace-kgreet-plugins (= 4:4.6.5-3) | 4:4.6.5-3 adduser | 3.113 Recommends (Version) | Installed ==-+-=== logrotate | 3.7.8-6 xserver-xorg | 1:7.6+9 OR xserver | kdebase | OR x-session-manager | OR x-window-manager | xterm | 271-1 OR x-terminal-emulator | Suggests (Version) | Installed -+-=== kdepasswd | 4:4.6.5-1 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ea6a11c.6000...@cwi.nl
Bug#648172: [kopete] Opening MSN inbox results in "The email address or password is incorrect. Please try again."
Package: kopete Version: 4:4.6.5-3 Severity: normal --- Please enter the report below this line. --- Hi guys, When I use kopete to open my Hotmail Inbox, iceweasel opens as usual. But it opens the following page https://login.live.com/ppsecure/md5auth.srf?f=9&MSPPError=-2147197902 which says "The email address or password is incorrect. Please try again." When I login in the browser with the same credentials I do proceed to my Inbox. This feature has worked for me for years. Did Microsoft change the login procedure again? Cheers, Wouter --- System information. --- Architecture: amd64 Kernel: Linux 3.1.0.git2+ Debian Release: wheezy/sid 990 testing the.earth.li 990 testing security.debian.org 500 unstable the.earth.li 500 stable-updates the.earth.li 500 stable the.earth.li 500 stable security.debian.org 1 experimental the.earth.li --- Package information. --- Depends (Version) | Installed =-+-=== kdebase-runtime | 4:4.6.5-1+b1 kdepim-runtime | 4:4.4.11.1-2 libc6 (>= 2.4) | 2.13-21 libexpat1 (>= 1.95.8) | 2.0.1-7 libgadu3 (>= 1:1.8.0+r592) | 1:1.11.0+r1184-2 libgif4 (>= 4.1.4) | 4.1.6-9 libglib2.0-0 (>= 2.12.0) | 2.28.6-1 libidn11 (>= 1.13) | 1.22-3 libjasper1 | 1.900.1-10 libkabc4 (>= 4:4.6) | 4:4.6.5-1 libkcmutils4 (>= 4:4.6) | 4:4.6.5-2+b1 libkde3support4 (>= 4:4.6) | 4:4.6.5-2+b1 libkdecore5 (>= 4:4.6) | 4:4.6.5-2+b1 libkdeui5 (>= 4:4.6) | 4:4.6.5-2+b1 libkdnssd4 (>= 4:4.6) | 4:4.6.5-2+b1 libkemoticons4 (>= 4:4.6) | 4:4.6.5-2+b1 libkhtml5 (>= 4:4.6) | 4:4.6.5-2+b1 libkio5 (>= 4:4.6) | 4:4.6.5-2+b1 libkmime4 (>= 4:4.6) | 4:4.6.5-1 libknewstuff2-4 (>= 4:4.6) | 4:4.6.5-2+b1 libknotifyconfig4 (>= 4:4.6) | 4:4.6.5-2+b1 libkopete4 (>= 4:4.6.1) | 4:4.6.5-3 libkparts4 (>= 4:4.6) | 4:4.6.5-2+b1 libkpimidentities4 (>= 4:4.6) | 4:4.6.5-1 libmeanwhile1 (>= 1.0.2) | 1.0.2-4 libmediastreamer0 (>= 3.3.2) | 3.3.2-4.1+b1 libmsn0.3 (>= 4.1~) | 4.1-3 libortp8 (>= 3.3.2) | 3.3.2-4.1+b1 libotr2 (>= 3.2.0) | 3.2.0-2.1 libphonon4 (>= 4:4.2.0) | 4:4.6.0really4.5.0-5 libqca2 (>= 2.0.2) | 2.0.3-2 libqimageblitz4 (>= 1:0.0.4) | 1:0.0.6-4 libqt4-dbus (>= 4:4.5.3) | 4:4.7.3-5 libqt4-network (>= 4:4.5.3) | 4:4.7.3-5 libqt4-qt3support (>= 4:4.5.3) | 4:4.7.3-5 libqt4-sql (>= 4:4.5.3) | 4:4.7.3-5 libqt4-xml (>= 4:4.5.3) | 4:4.7.3-5 libqtcore4 (>= 4:4.7.0~beta2) | 4:4.7.3-5 libqtgui4 (>= 4:4.5.3) | 4:4.7.3-5 libsolid4 (>= 4:4.6) | 4:4.6.5-2+b1 libssl1.0.0 (>= 1.0.0) | 1.0.0e-2 libstdc++6 (>= 4.6) | 4.6.1-15 libv4l-0 (>= 0.5.0) | 0.8.5-4 libx11-6 | 2:1.4.4-2 libxml2 (>= 2.7.4) | 2.7.8.dfsg-5 libxslt1.1 (>= 1.1.25) | 1.1.26-8 phonon | 4:4.6.0really4.5.0-5 zlib1g (>= 1:1.1.4) | 1:1.2.3.4.dfsg-3 Recommends (Version) | Installed ==-+-=== libqca2-plugin-ossl | 2.0.0~beta3-1 libqt4-sql-sqlite | 4:4.7.3-5 Suggests (Version) | Installed ===-+-=== kdeartwork-emoticons | khelpcenter4 | 4:4.6.5-1+b1 texlive-latex-base | 2009-14 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eb7b7b0.1040...@cwi.nl
Bug#361830: kde-core: No way to specify complex locale settings before KDE starts
Package: kde-core Version: 5:45 Followup-For: Bug #361830 Hello, I don't think there's a way to set individual locale variables before KDE starts. On my system, KDE is started by GDM via the regular 'kdestart' script. It doesn't read any dot-files such as dot.profile, dot.bash_profile, dot.bashrc. Although I can specify one variable (LANG, I suppose) in GDM itself, I prefer to have a more complex locale configuration. Gnome runs dot.gnomerc in the user's $HOME, where locales can be set. It would be handy if there was a way to get KDE to read either the user's dot-files or source a dedicated script like Gnome does. Thanks in advance, Wouter PS: FWIW, my settings are nl_BE with LC_MESSAGES set to en_GB and date set to en_DK.ISO-8859-1 to get ISO-8601 dates (-MM-DD). Currently, it's not possible to set LC_TIME to en_DK from within KDE, nor would there be a reason to if the dot-files are read in somewhere along the KDE starting process. PPS: Come to think of it, perhaps this should be discussed with login manager maintainers... -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kde-core depends on: ii arts 1.5.2-1sound system from the official KDE ii fontconfig2.3.2-5.1 generic font configuration library ii kdebase 4:3.5.2-1 base components from the official ii kdelibs 4:3.5.2-2 core libraries from the official K kde-core recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#363974: quanta: crash when clicking "Download Documentation..." in the Documentation panel
Package: quanta Version: 4:3.5.2-1 Severity: normal Hello, Quanta crashes when clicking on "Download Documentation..." in the Documentation panel. (You might have to click a few times.) The dialog itself doesn't seem to do anything, either. Or perhaps there isn't any extra documentation? Backtrace follows, not sure if it's useful. Regards, Wouter (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1242110272 (LWP 10082)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #5 0xb6f5b877 in QListBox::itemRect () from /usr/lib/libqt-mt.so.3 #6 0xb784ca9f in KJanusWidget::IconListItem::highlight () from /usr/lib/libkdeui.so.4 #7 0xb784cd68 in KJanusWidget::IconListBox::slotOnItem () from /usr/lib/libkdeui.so.4 #8 0xb784cdca in KJanusWidget::slotOnItem () from /usr/lib/libkdeui.so.4 #9 0xb784d532 in KJanusWidget::qt_invoke () from /usr/lib/libkdeui.so.4 #10 0xb6e72678 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #11 0xb72192fa in QListBox::onItem () from /usr/lib/libqt-mt.so.3 #12 0xb6f5f489 in QListBox::mouseMoveEvent () from /usr/lib/libqt-mt.so.3 #13 0xb6eacbfa in QWidget::event () from /usr/lib/libqt-mt.so.3 #14 0xb6e0887a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #15 0xb6e08dff in QApplication::notify () from /usr/lib/libqt-mt.so.3 #16 0xb759d02e in KApplication::notify () from /usr/lib/libkdecore.so.4 #17 0xb6d9a06f in QApplication::sendSpontaneousEvent () from /usr/lib/libqt-mt.so.3 #18 0xb6d957a4 in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #19 0xb6d940c1 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #20 0xb6dad2a2 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #21 0xb6e21255 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #22 0xb6e2117a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #23 0xb6e0738d in QApplication::exec () from /usr/lib/libqt-mt.so.3 #24 0x080f8a90 in ?? () #25 0x083e0578 in ?? () #26 0x in ?? () -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages quanta depends on: ii kdelibs4c2a 4:3.5.2-2+b1core libraries for all KDE applica ii kfilereplace 4:3.5.2-1 batch search-and-replace component ii klinkstatus 4:3.5.2
Bug#392037: konqueror crash when middle-clicking (new tab) on link
Package: konqueror Version: 4:3.5.5-1 Severity: important Konqueror crashed when middle-clicking (open in new tab) on a regular link somewhere in a wikipedia page. Backtrace from the KDE crash handler: (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232386368 (LWP 12488)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debu
Bug#446435: kde: holding down a key does not make the key repeat in KDE
Package: kde Version: 5:47 Severity: normal Hello, (I'm sorry for not knowing which KDE component is responsible for this particular problem. Feel free to reassign. Thanks.) Since a few days, holding a key down does not make the key repeat. I hadn't noticed, until I tried to scroll down in Firefox with the arrow keys. The page only scrolls down one unit, even if you keep the key down. I then tried some other programs (e.g. konsole), and none of the keys repeat, either arrows or normal letters. Did I accidently turn on some accessibility function I don't know about, or is this a new and known problem? Thanks for any clues, Wouter PS: I've been bitten by the X keyboard leds bug too (freedesktop #12434). Perhaps related? -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22 Locale: LANG=C, LC_CTYPE=en_GB.utf-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kde depends on: ii kde-amusements5:47 the K Desktop Environment games an ii kde-core 5:47 the K Desktop Environment core mod ii kdeaccessibility 4:3.5.7-1 accessibility packages from the of ii kdeaddons 4:3.5.7-3 add-on plugins and applets provide ii kdeadmin 4:3.5.7-1 system administration tools from t ii kdeartwork4:3.5.7-2 themes, styles and more from the o ii kdegraphics 4:3.5.7-4 graphics apps from the official KD ii kdemultimedia 4:3.5.7-3 multimedia apps from the official ii kdenetwork4:3.5.7-4 network-related apps from the offi ii kdepim4:3.5.7-4 Personal Information Management ap ii kdeutils 4:3.5.7-3 general purpose utilities from the ii kdewebdev 4:3.5.7-2 web development apps from the offi kde recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#277582: ITP: kwin-baghira -- A MacOSX-like theme for Apple junkies ;)
On Mon, Oct 25, 2004 at 06:23:08AM +0200, Adeodato Simó wrote: > * José Luis Tallón [Mon, 25 Oct 2004 03:53:46 +0200]: > > This is NOT a theme... > > agreed. note to Wouter: I strongly prefer kde-$FOO-style instead of > using the word theme, since kde uses the word "theme" for something > different than styles (as baghira). Noted. Didn't know KDE uses those two things for different things, but that's of course a good reason not to do it that way. -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune
