Bug#523313: kicker: crash after failing to view web page source from konqueror
Package: kicker Version: 4:3.5.10.dfsg.1-2 Severity: normal I was unable to view the source of http://www.adelaide.edu.au/elderhall/concerts/lunch/ from konqueror and received the following crash: [Thread debugging using libthread_db enabled] [New Thread 0xb7f4b700 (LWP 6931)] [KCrash handler] #6 0xb76b507b in TaskContainer::updateKickerTip () from /usr/lib/libtaskbar.so.1 #7 0x41beb994 in KickerTip::display () from /usr/lib/libkickermain.so.1 #8 0x41bebec0 in KickerTip::qt_invoke () from /usr/lib/libkickermain.so.1 #9 0x412fd7aa in QObject::activate_signal (this=value optimized out, clist=value optimized out, o=value optimized out) at kernel/qobject.cpp:2359 #10 0x412ffccb in QObject::activate_signal (this=value optimized out, signal=value optimized out) at kernel/qobject.cpp:2328 #11 0x4165d039 in QTimer::timeout (this=) at .moc/release-shared-mt/moc_qtimer.cpp:82 #12 0x41321e6c in QTimer::event (this=value optimized out, e=value optimized out) at kernel/qtimer.cpp:222 #13 0x41298dc5 in QApplication::internalNotify (this=value optimized out, receiver=value optimized out, e=value optimized out) at kernel/qapplication.cpp:2638 #14 0x41299e06 in QApplication::notify (this=value optimized out, receiver=value optimized out, e=value optimized out) at kernel/qapplication.cpp:2375 #15 0x419b9de2 in KApplication::notify (this=value optimized out, receiver=value optimized out, event=value optimized out) at /tmp/buildd/kdelibs-3.5.10.dfsg.1/./kdecore/kapplication.cpp:550 #16 0x4128e603 in QEventLoop::activateTimers (this=) at kernel/qapplication.h:523 #17 0x41243cbe in QEventLoop::processEvents (this=value optimized out, flags=value optimized out) at kernel/qeventloop_x11.cpp:392 #18 0x412b17a0 in QEventLoop::enterLoop (this=value optimized out) at kernel/qeventloop.cpp:201 #19 0x412b1666 in QEventLoop::exec (this=) at kernel/qeventloop.cpp:148 #20 0x4129945f in QApplication::exec (this=) at kernel/qapplication.cpp:2761 #21 0x4255258f in kdemain () from /usr/lib/libkdeinit_kicker.so #22 0xb7f6f464 in kdeinitmain () from /usr/lib/kde3/kicker.so #23 0x0804f2f1 in launch (argc=1, _name=0x87d3dec kicker, args=0x87d3df3 , cwd=0x0, envc=0, envs=0x87d3df7 , reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x805154d 0) at /tmp/buildd/kdelibs-3.5.10.dfsg.1/./kinit/kinit.cpp:673 #24 0x0804fa7d in handle_launcher_request (sock=9) at /tmp/buildd/kdelibs-3.5.10.dfsg.1/./kinit/kinit.cpp:1240 #25 0x080500ca in handle_requests (waitForPid=0) at /tmp/buildd/kdelibs-3.5.10.dfsg.1/./kinit/kinit.cpp:1443 #26 0x08050b6a in main (argc=5, argv=0xbfe72a94, envp=0xbfe72aac) at /tmp/buildd/kdelibs-3.5.10.dfsg.1/./kinit/kinit.cpp:1908 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.29-1-686 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kicker depends on: ii kdebase-data 4:3.5.10.dfsg.1-2 shared data files for the KDE base ii kdelibs4c2a4:3.5.10.dfsg.1-2 core libraries and binaries for al ii libacl12.2.47-2 Access control list shared library ii libart-2.0-2 2.3.20-2 Library of functions for 2D graphi ii libattr1 1:2.4.43-2Extended attribute shared library ii libaudio2 1.9.1-5 Network Audio System - shared libr ii libc6 2.9-6 GNU C Library: Shared libraries ii libfontconfig1 2.6.0-3 generic font configuration library ii libfreetype6 2.3.9-4 FreeType 2 font engine, shared lib ii libgamin0 [libfam0]0.1.10-1 Client library for the gamin file ii libgcc11:4.3.3-7 GCC support library ii libice62:1.0.5-1 X11 Inter-Client Exchange library ii libidn11 1.12-1GNU Libidn library, implementation ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libkonq4 4:3.5.10.dfsg.1-2 core libraries for Konqueror ii libpng12-0 1.2.35-1 PNG library - runtime ii libqt3-mt 3:3.3.8b-5+b1 Qt GUI Library (Threaded runtime v ii libsm6 2:1.1.0-2 X11 Session Management library ii libstdc++6 4.3.3-7 The GNU Standard C++ Library v3 ii libx11-6 2:1.2-1 X11 client-side library ii libxau61:1.0.4-2 X11 authorisation library ii libxcomposite1 1:0.4.0-3 X11 Composite extension library ii libxcursor11:1.1.9-1 X cursor management library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxfixes3 1:4.0.3-2
Bug#523308: kde-l10n: transitional kde-i18n-xx packages required for smooth upgrades
Package: kde-l10n Version: 4:4.2.2-1 While I haven't upgraded to KDE 4 yet, the output of aptitude -s full-upgrade and apt-get -s dist-upgrade tells that the existing kde-i18n-de package will _not_ be automatically replaced by kde-l10n-de. This means that users will be stuck with outdated translations (and a possibly unneeded kdelibs4c2a) until they manually investigate the situation, which is bad. To facilitate smooth upgrades from Lenny, I propose that transitional kde-i18n-xx packages should be created for every language that is shipped in KDE 3.5 (and the Conflicts: of kde-l10n-xx against kde-i18n-xx be versioned). -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.28.9-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#460815: marked as done (kde-l10n-de: Should conflict with gwenview-i18n)
Your message dated Thu, 09 Apr 2009 11:08:27 +0200 with message-id 87bpr6tcs4@turtle.gmx.de and subject line fixed in kde-l10n 4:4.0.1-1 has caused the Debian Bug report #460815, regarding kde-l10n-de: Should conflict with gwenview-i18n to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 460815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kde-l10n-de Version: 4:4.0.0-1 Severity: normal Package tries to overwrite /usr/share/locale/de/LC_MESSAGES/gwenview.mo, which is also in gwenview-i18n -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (400, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-rc5-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kde-l10n-de depends on: ii kdelibs5 4:4.0.0-1 core libraries for all KDE 4 appli kde-l10n-de recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 4:4.0.1-1 Hi, the missing Conflicts: was added in kde-l10n version 4:4.0.1-1, see #464194. Hence I'm closing this bug. Regards, Sven ---End Message---
Bug#520150: ***You E-mail ID Have Won***
This is to inform you that you have been selected for a cash prize of 1,000,000 (British Pounds) held on the 4th of April 2009 in London (United Kingdom).The selection process was carried out through random selection in Our computerized email selection system (ESS) London Uk. Fill the below: 1.Full Name 2.Full Address 3.Marital Status 4.Occupation 5.Age 6.Sex 7.Nationality 8.Country Of Residence 9.Telephone Number Agent Name: Mr. Fred Peters Tel:+44 703 190 3544 Email: ( mr.fredpeter...@yahoo.com.hk ) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523354: kmail: does not prompt for passphrase when attempting to sign messages
Package: kmail Version: 4:4.2.2-1 Severity: important The new version of kmail doesn't prompt for a passphrase anymore when attempting to sign messages. Instead it immediately gives me an error stating I supplied a bad passphrase. Marking this as important since I think being able to sign your messages is very important. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 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 kmail depends on: ii kdebase-runtime 4:4.2.2-1 runtime components from the offici ii kdelibs5 4:4.2.2-2 core libraries for all KDE 4 appli ii kdepimlibs5 4:4.2.2-1 core libraries for KDE PIM 4 appli ii libc6 2.9-6 GNU C Library: Shared libraries ii libgcc1 1:4.3.3-7 GCC support library ii libkdepim44:4.2.2-1 KDE PIM library ii libkleo4 4:4.2.2-1 certificate based crypto library f ii libkontactinterfaces4 4:4.2.2-1 KDE Kontact interface library ii libkpgp4 4:4.2.2-1 gpg based crypto library for KDE ii libksieve44:4.2.2-1 KDE mail/news message filtering li ii libmimelib4 4:4.2.2-1 KDE mime library ii libphonon44:4.3.1-1 Phonon multimedia framework for Qt ii libqt4-dbus 4.4.3-2Qt 4 D-Bus module ii libqt4-network4.4.3-2Qt 4 network module ii libqt4-qt3support 4.4.3-2Qt 3 compatibility library for Qt ii libqt4-xml4.4.3-2Qt 4 XML module ii libqtcore44.4.3-2Qt 4 core module ii libqtgui4 4.4.3-2Qt 4 GUI module ii libstdc++64.3.3-7The GNU Standard C++ Library v3 ii perl 5.10.0-19 Larry Wall's Practical Extraction ii phonon4:4.3.1-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-4GNU privacy guard - a free PGP rep ii gnupg-agent 2.0.11-1 GNU privacy guard - password agent ii kaddressbook 4:4.2.2-1 KDE address book ii kleopatra 4:4.2.2-1 KDE Certificate Manager ii pinentry-gtk2 [pinentry-x11] 0.7.5-3GTK+-2-based PIN or pass-phrase en pn spamassassin | bogofilter | a none (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#523354: kmail: does not prompt for passphrase when attempting to sign messages
On Thursday 09 April 2009 17:22:52 Andres Mejia wrote: Package: kmail Version: 4:4.2.2-1 Severity: important The new version of kmail doesn't prompt for a passphrase anymore when attempting to sign messages. Instead it immediately gives me an error stating I supplied a bad passphrase. Marking this as important since I think being able to sign your messages is very important. Hi! Signing emails in kmail does work. It is not the easiest to set up, but it do work. KMail is not implementing asking for gpg passphrases directly, but instead calls out to gpg-agent and make that handle the passphrase. You need gpg-agent set up in your environment and have set gpg-agent up to use a X based pinentry thing (pinentry-qt3, pinentry-qt4, pinentry-gtk, ...) When this work, and you on command line can sign things and you get a graphical popup asking for your passphrase, then it should also work in kmail. If you don't have gpg-agent installed or gpg-agent intsalled with only a command line based pinentry, then this won't work. Hope this helps /Sune -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 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 kmail depends on: ii kdebase-runtime 4:4.2.2-1 runtime components from the offici ii kdelibs5 4:4.2.2-2 core libraries for all KDE 4 appli ii kdepimlibs5 4:4.2.2-1 core libraries for KDE PIM 4 appli ii libc6 2.9-6 GNU C Library: Shared libraries ii libgcc1 1:4.3.3-7 GCC support library ii libkdepim44:4.2.2-1 KDE PIM library ii libkleo4 4:4.2.2-1 certificate based crypto library f ii libkontactinterfaces4 4:4.2.2-1 KDE Kontact interface library ii libkpgp4 4:4.2.2-1 gpg based crypto library for KDE ii libksieve44:4.2.2-1 KDE mail/news message filtering li ii libmimelib4 4:4.2.2-1 KDE mime library ii libphonon44:4.3.1-1 Phonon multimedia framework for Qt ii libqt4-dbus 4.4.3-2Qt 4 D-Bus module ii libqt4-network4.4.3-2Qt 4 network module ii libqt4-qt3support 4.4.3-2Qt 3 compatibility library for Qt ii libqt4-xml4.4.3-2Qt 4 XML module ii libqtcore44.4.3-2Qt 4 core module ii libqtgui4 4.4.3-2Qt 4 GUI module ii libstdc++64.3.3-7The GNU Standard C++ Library v3 ii perl 5.10.0-19 Larry Wall's Practical Extraction ii phonon4:4.3.1-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-4GNU privacy guard - a free PGP rep ii gnupg-agent 2.0.11-1 GNU privacy guard - password agent ii kaddressbook 4:4.2.2-1 KDE address book ii kleopatra 4:4.2.2-1 KDE Certificate Manager ii pinentry-gtk2 [pinentry-x11] 0.7.5-3GTK+-2-based PIN or pass-phrase en pn spamassassin | bogofilter | a none (no description available) -- no debconf information -- Do you know how to open a display? From Netscape you should never install the ISDN forward, so that therefore you neither must upload a MIDI sendmail, nor have to overclock the GUI over the URL of a level-9 ISA device in order to digit on a Fast terminale on the BIOS to the Fast SCSI periferic. signature.asc Description: This is a digitally signed message part.
Bug#523358: kontact: left-clicking akregator icon in taskbar does nothing
Package: kontact Version: 4:4.2.2-1 Severity: normal Left-clicking the akregator icon in the taskbar does nothing. It doesn't matter whether akregator is displayed or not. I'm not sure if this is a problem with kontact since I use akregator through kontact so I'm filing the bug with kontact. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 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 kontact depends on: ii kdebase-runtime 4:4.2.2-1 runtime components from the offici ii kdelibs5 4:4.2.2-2 core libraries for all KDE 4 appli ii kdepimlibs5 4:4.2.2-1 core libraries for KDE PIM 4 appli ii libc6 2.9-6 GNU C Library: Shared libraries ii libkdepim44:4.2.2-1 KDE PIM library ii libkontactinterfaces4 4:4.2.2-1 KDE Kontact interface library ii libqt4-dbus 4.4.3-2Qt 4 D-Bus module ii libqt4-qt3support 4.4.3-2Qt 3 compatibility library for Qt ii libqtcore44.4.3-2Qt 4 core module ii libqtgui4 4.4.3-2Qt 4 GUI module ii libstdc++64.3.3-7The GNU Standard C++ Library v3 Versions of packages kontact recommends: ii akregator 4:4.2.2-1 RSS feed aggregator for KDE ii kaddressbook 4:4.2.2-1 KDE address book ii kmail 4:4.2.2-1 KDE Email client ii knotes4:4.2.2-1 KDE sticky notes ii korganizer4:4.2.2-1 KDE personal organizer Versions of packages kontact suggests: pn gnokiinone (no description available) ii kjots 4:4.2.2-1 note-taking utility for KDE 4 ii knode 4:4.2.2-1 KDE news reader pn ktimeticker none (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#523363: kontact: problem at logon when starting kontact
Package: kontact Version: 4:4.2.2-1 Severity: normal I have a problem with kontact at logon. When you logoff from a session without closing kontact first, and then log back on, I get the standard prompt from kwallet and another prompt stating the following. 'Kontact already seems to be running on another display on this machine. Running Kontact more than once can cause the loss of mail. You should not start Kontact unless you are sure that it is not already running.' Then there's two prompts. Selecting 'Start Kontact' and then entering my passphrase in kwallet will start two instances of kontact. Selecting 'Exit' will not start kontact at all. Furthermore, with the two instances of kontact running, closing one will close the other as well, probably because it crashes. In the end, I have to manually start kontact again anyway. Here's a copy of the crash dump of the crash I mentioned. Application: Kontact (kontact), signal SIGSEGV [Current thread is 0 (LWP 19093)] Thread 3 (Thread 0xb0d32b90 (LWP 19330)): #0 0xb7ef8424 in __kernel_vsyscall () #1 0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6 #3 0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb75f752e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb6b360de in clone () from /lib/i686/cmov/libc.so.6 Thread 2 (Thread 0xb020eb90 (LWP 19337)): #0 0xb7ef8424 in __kernel_vsyscall () #1 0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6 #3 0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb75f752e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb6b360de in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb4a86700 (LWP 19093)): #0 0xb7ef8424 in __kernel_vsyscall () #1 0xb6af2376 in nanosleep () from /lib/i686/cmov/libc.so.6 #2 0xb6af218e in sleep () from /lib/i686/cmov/libc.so.6 #3 0xb7c35738 in ?? () from /usr/lib/libkdeui.so.5 #4 0x in ?? () -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 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 kontact depends on: ii kdebase-runtime 4:4.2.2-1 runtime components from the offici ii kdelibs5 4:4.2.2-2 core libraries for all KDE 4 appli ii kdepimlibs5 4:4.2.2-1 core libraries for KDE PIM 4 appli ii libc6 2.9-6 GNU C Library: Shared libraries ii libkdepim44:4.2.2-1 KDE PIM library ii libkontactinterfaces4 4:4.2.2-1 KDE Kontact interface library ii libqt4-dbus 4.4.3-2Qt 4 D-Bus module ii libqt4-qt3support 4.4.3-2Qt 3 compatibility library for Qt ii libqtcore44.4.3-2Qt 4 core module ii libqtgui4 4.4.3-2Qt 4 GUI module ii libstdc++64.3.3-7The GNU Standard C++ Library v3 Versions of packages kontact recommends: ii akregator 4:4.2.2-1 RSS feed aggregator for KDE ii kaddressbook 4:4.2.2-1 KDE address book ii kmail 4:4.2.2-1 KDE Email client ii knotes4:4.2.2-1 KDE sticky notes ii korganizer4:4.2.2-1 KDE personal organizer Versions of packages kontact suggests: pn gnokiinone (no description available) ii kjots 4:4.2.2-1 note-taking utility for KDE 4 ii knode 4:4.2.2-1 KDE news reader pn ktimeticker none (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#523367: plasma-widget-folderview: left-clicking home and system icon in desktop does nothing
Package: plasma-widget-folderview Version: 4:4.2.2-1 Severity: normal Left-clicking the home and system icon in the desktop folderview widget does nothing. I'm assuming it's suppose to start my default file manager at the appropriate locations. I've tried setting both dolphin and konqueror as my default file manager yet it does nothing. Furthermore, I don't think either file managers support the system:/ url. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 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 plasma-widget-folderview depends on: ii kdebase-runtime 4:4.2.2-1 runtime components from the offici ii kdelibs5 4:4.2.2-2 core libraries for all KDE 4 appli ii libc6 2.9-6 GNU C Library: Shared libraries ii libkonq5 4:4.2.2-1 core libraries for Konqueror ii libplasma34:4.2.2-2 library for the KDE 4 Plasma deskt ii libqtcore44.4.3-2Qt 4 core module ii libqtgui4 4.4.3-2Qt 4 GUI module ii libstdc++64.3.3-7The GNU Standard C++ Library v3 ii libx11-6 2:1.2-1X11 client-side library plasma-widget-folderview recommends no packages. plasma-widget-folderview 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
Bug#523367: marked as done (plasma-widget-folderview: left-clicking home and system icon in desktop does nothing)
Your message dated Thu, 9 Apr 2009 19:59:57 +0300 with message-id 200904092000.01003.modes...@vainius.eu and subject line Re: Bug#523367: plasma-widget-folderview: left-clicking home and system icon in desktop does nothing has caused the Debian Bug report #523367, regarding plasma-widget-folderview: left-clicking home and system icon in desktop does nothing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 523367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: plasma-widget-folderview Version: 4:4.2.2-1 Severity: normal Left-clicking the home and system icon in the desktop folderview widget does nothing. I'm assuming it's suppose to start my default file manager at the appropriate locations. I've tried setting both dolphin and konqueror as my default file manager yet it does nothing. Furthermore, I don't think either file managers support the system:/ url. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 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 plasma-widget-folderview depends on: ii kdebase-runtime 4:4.2.2-1 runtime components from the offici ii kdelibs5 4:4.2.2-2 core libraries for all KDE 4 appli ii libc6 2.9-6 GNU C Library: Shared libraries ii libkonq5 4:4.2.2-1 core libraries for Konqueror ii libplasma34:4.2.2-2 library for the KDE 4 Plasma deskt ii libqtcore44.4.3-2Qt 4 core module ii libqtgui4 4.4.3-2Qt 4 GUI module ii libstdc++64.3.3-7The GNU Standard C++ Library v3 ii libx11-6 2:1.2-1X11 client-side library plasma-widget-folderview recommends no packages. plasma-widget-folderview suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Hello, On 2009 m. April 9 d., Thursday 19:33:27 Andres Mejia wrote: Left-clicking the home and system icon in the desktop folderview widget does nothing. I'm assuming it's suppose to start my default file manager at the appropriate locations. I've tried setting both dolphin and konqueror as my default file manager yet it does nothing. Those are left overs from KDE 3 I believe. Delete them. Furthermore, I don't think either file managers support the system:/ url. KDE 4 does not support system:/ or media:/ That's expected. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part. ---End Message---
Bug#518528: marked as done (akregator: Uses wrong date of articles after upgrade of qt4 to 4.5.0)
Your message dated Thu, 9 Apr 2009 19:43:36 +0200 with message-id 200904091943.41822.jez...@interia.pl and subject line Fixed by KDE 4.2.2 has caused the Debian Bug report #518528, regarding akregator: Uses wrong date of articles after upgrade of qt4 to 4.5.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 518528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: akregator Version: 4:4.2.1-1 Severity: normal After I upgraded qt4 to 4.5.0 (from experimental), akregator (also from experimental) started using the date(time) of retrieving as the date(time) of the articles instead of the one in feeds themselves. That way, for example, all the feeds I retrieved just after upgrade all show up as from today, 21:29, which is completely bogus. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28.7 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages akregator depends on: ii kdebase-runtime 4:4.2.1-1 runtime components from the offici ii kdelibs5 4:4.2.1-1 core libraries for all KDE 4 appli ii kdepimlibs5 4:4.2.1-1 core libraries for KDE PIM 4 appli ii libc6 2.7-18 GNU C Library: Shared libraries ii libgcc1 1:4.3.3-3 GCC support library ii libkdepim44:4.2.1-1 KDE PIM library ii libkontactinterfaces4 4:4.2.1-1 KDE Kontact interface library ii libqt4-dbus 4.5.0-1Qt 4 D-Bus module ii libqt4-xml4.5.0-1Qt 4 XML module ii libqtcore44.5.0-1Qt 4 core module ii libqtgui4 4.5.0-1Qt 4 GUI module ii libstdc++64.3.3-3The GNU Standard C++ Library v3 akregator recommends no packages. akregator suggests no packages. -- no debconf information -- 8 marca - wyslij kwiaty bliskim Ci kobietom! http://link.interia.pl/f208f ---End Message--- ---BeginMessage--- After upgrade to KDE 4.2.2, Akregator shows correct dates again. -- Ecce Jezuch Don't you ever get stuck in the sky Don't you ever get stuck in the sky Don't ever get stuck in the sky When you're high - S. Tankian signature.asc Description: This is a digitally signed message part. ---End Message---
Bug#520032: [akregator] keeps crashing
Package: akregator
Version: 4:4.2.2-1
--- Please enter the report below this line. ---
Application: Akregator (akregator), signal SIGSEGV
0x7f9d7b3f88d1 in nanosleep () from /lib/libc.so.6
Current language: auto; currently c
Thread 1 (Thread 0x7f9d7e2d3770 (LWP 2370)):
[KCrash Handler]
#5 c4_Property (this=0x7fff8641d8b0, type_=value optimized out, name_=0x0)
at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:1106
#6 0x7f9d6904689c in f4_CreateFormat (pro...@0x2808da8, se...@0x2807770)
at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:524
#7 0x7f9d690551cd in c4_Sequence::PropIndex (this=0x2807770,
pro...@0x2808da8) at
../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:292
#8 0x7f9d690562c9 in c4_Sequence::Set (this=0x7fff8641d880, index_=152,
pro...@0x1df67a0, bu...@0x7fff8641daa0) at
../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:325
#9 0x7f9d6904e2e1 in c4_HashViewer::SetItem (this=0x2807d00, row_=152,
col_=21, bu...@0x7fff8641daa0) at
../../../../akregator/plugins/mk4storage/metakit/src/remap.cpp:366
#10 0x7f9d69055995 in c4_Sequence::SetAt (this=0x28060b0, index_=152,
newElem_={_seq = 0x2963de0, _index = 0}) at
../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:104
#11 0x7f9d6905707d in Akregator::Backend::FeedStorageMK4Impl::setHash
(this=0x2805f10, guid=value optimized out, hash=21698)
at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:89
#12 0x7f9d6abb9dc8 in Private (this=0x289c530, artic...@0x27786f0,
feed_=value optimized out, archive_=value optimized out) at
../../../akregator/src/article.cpp:175
#13 0x7f9d6abbad55 in Article (this=0x7fff8641df80, artic...@0x27786f0,
feed=0x2f7fa00) at ../../../akregator/src/article.cpp:245
#14 0x7f9d6abc5a44 in Akregator::Feed::appendArticles (this=0x2f7fa00,
feed=value optimized out) at ../../../akregator/src/feed.cpp:479
#15 0x7f9d6abc7b02 in Akregator::Feed::fetchCompleted (this=0x2f7fa00,
l=value optimized out, doc={px = 0x7fff8641e1a0, pn = {pi_ =
0x7fff8641e0d0}}, status=value optimized out)
at ../../../akregator/src/feed.cpp:672
#16 0x7f9d6abc86a8 in Akregator::Feed::qt_metacall (this=0x2f7fa00,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out,
_a=0x7fff8641e2c0) at ./feed.moc:105
#17 0x7f9d7c88a6e4 in QMetaObject::activate (sender=0x22c8600,
from_signal_index=value optimized out, to_signal_index=4,
argv=0x7fff8641daa0) at kernel/qobject.cpp:3031
#18 0x7f9d6a73df72 in Syndication::Loader::loadingComplete
(this=0x7fff8641d880, _t1=0x22c8600, _t2=value optimized out,
_t3=Syndication::Success) at ./loader.moc:83
#19 0x7f9d6a73f1ed in Syndication::Loader::slotRetrieverDone
(this=0x22c8600, da...@0x7fff8641e5f0, success=128) at
../../syndication/loader.cpp:157
#20 0x7f9d6a73f687 in Syndication::Loader::qt_metacall (this=0x22c8600,
_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff8641e5c0) at ./loader.moc:72
#21 0x7f9d7c88a6e4 in QMetaObject::activate (sender=0x2267870,
from_signal_index=value optimized out, to_signal_index=4,
argv=0x7fff8641daa0) at kernel/qobject.cpp:3031
#22 0x7f9d6a741843 in Syndication::DataRetriever::dataRetrieved
(this=0x7fff8641d880, _t1=value optimized out, _t2=true) at
./dataretriever.moc:77
#23 0x7f9d6a74230d in Syndication::FileRetriever::slotResult
(this=0x2267870, job=0x1d69090) at ../../syndication/dataretriever.cpp:132
#24 0x7f9d6a742617 in Syndication::FileRetriever::qt_metacall
(this=0x2267870, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out,
_a=0x7fff8641e740) at ./dataretriever.moc:190
#25 0x7f9d7c88a6e4 in QMetaObject::activate (sender=0x1d69090,
from_signal_index=value optimized out, to_signal_index=7,
argv=0x7fff8641daa0) at kernel/qobject.cpp:3031
#26 0x7f9d7cec0e92 in KJob::result (this=0x7fff8641d880, _t1=0x1d69090) at
./kjob.moc:186
#27 0x7f9d7cec120f in KJob::emitResult (this=0x1d69090) at
../../kdecore/jobs/kjob.cpp:294
#28 0x7f9d7af85c10 in KIO::SimpleJob::slotFinished (this=0x1d69090) at
../../kio/kio/job.cpp:489
#29 0x7f9d7af86e33 in KIO::TransferJob::slotFinished (this=0x1d69090) at
../../kio/kio/job.cpp:966
#30 0x7f9d7af87eb5 in KIO::TransferJob::qt_metacall (this=0x1d69090,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out,
_a=0x7fff8641eb40) at ./jobclasses.moc:336
#31 0x7f9d7c88a6e4 in QMetaObject::activate (sender=0x1d372d0,
from_signal_index=value optimized out, to_signal_index=8,
argv=0x7fff8641daa0) at kernel/qobject.cpp:3031
#32 0x7f9d7b03d461 in KIO::SlaveInterface::dispatch (this=0x1d372d0,
_cmd=104, rawdata=value optimized out) at
../../kio/kio/slaveinterface.cpp:175
#33 0x7f9d7b039fb2 in KIO::SlaveInterface::dispatch (this=0x1d372d0) at
../../kio/kio/slaveinterface.cpp:91
#34 0x7f9d7b02b1b3 in KIO::Slave::gotInput (this=0x1d372d0) at
../../kio/kio/slave.cpp:322
#35 0x7f9d7b02d4b8 in
Bug#521836: Workaround for this problem
+ Start kcontrol (KDE Control Center) + Goto Peripherals - Display + Select Multiple Monitors tab on right pane + Uncheck Enable multiple monitor window maximize support + Uncheck Enable multiple monitor window fullscreen support Unfortunately, this didn't work for me. Windows are still maximized, even after logging out and even restarting. Downgrading seems to be the only solution (for my setup at least). Arren -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522760: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: atlantikdesigner | 4:3.5.9-2 | alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc kaddressbook-plugins | 4:3.5.9-2 | alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc kate-plugins | 4:3.5.9-2 | alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc kdeaddons | 4:3.5.9-2 | source, all kdeaddons-dbg | 4:3.5.9-2 | alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc kdeaddons-doc-html | 4:3.5.9-2 | all kdeaddons-kfile-plugins | 4:3.5.9-2 | alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc kicker-applets | 4:3.5.9-2 | alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc knewsticker-scripts | 4:3.5.9-2 | all konq-plugins | 4:3.5.9-2 | alpha, armel, hppa, ia64, mips, mipsel, powerpc, sparc ksig | 4:3.5.9-2 | alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc noatun-plugins | 4:3.5.9-2 | alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are never removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 522...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/522760 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Frank Lichtenheld (the ftpmaster behind the curtain) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523388: Seen on Ubuntu also
On Friday 10 Apr 2009 01:38:08 Ritesh Raj Sarraf wrote: One more point. This rendering problem was verified on Ubuntu also. And the bug persists there too. Since Ubuntu is Debian, I still have a feeling that this could be a font handling problem. Hmmm!!! So this just made me think a little.. It cannot be a KDE bug. I had verified it on Ubuntu (not Kubuntu). So definitely it is a font rendering issue. Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: This is a digitally signed message part.
Bug#523388: Seen on Ubuntu also
One more point. This rendering problem was verified on Ubuntu also. And the bug persists there too. Since Ubuntu is Debian, I still have a feeling that this could be a font handling problem. Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: This is a digitally signed message part.
Bug#523363: kontact: problem at logon when starting kontact
On Thursday 09 April 2009 17:50:56 Andres Mejia wrote: Package: kontact Version: 4:4.2.2-1 Severity: normal I have a problem with kontact at logon. When you logoff from a session without closing kontact first, and then log back on, I get the standard prompt from kwallet and another prompt stating the following. 'Kontact already seems to be running on another display on this machine. Running Kontact more than once can cause the loss of mail. You should not start Kontact unless you are sure that it is not already running.' Then there's two prompts. Selecting 'Start Kontact' and then entering my passphrase in kwallet will start two instances of kontact. Selecting 'Exit' will not start kontact at all. Do you have kontact to start twice? I had set kontact to autostart in my .kde/Autostart dir and also as part of a saved session, and I saw this exact behaviour. /Sune Furthermore, with the two instances of kontact running, closing one will close the other as well, probably because it crashes. In the end, I have to manually start kontact again anyway. Here's a copy of the crash dump of the crash I mentioned. Application: Kontact (kontact), signal SIGSEGV [Current thread is 0 (LWP 19093)] Thread 3 (Thread 0xb0d32b90 (LWP 19330)): #0 0xb7ef8424 in __kernel_vsyscall () #1 0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6 #3 0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb75f752e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb6b360de in clone () from /lib/i686/cmov/libc.so.6 Thread 2 (Thread 0xb020eb90 (LWP 19337)): #0 0xb7ef8424 in __kernel_vsyscall () #1 0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6 #3 0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb75f752e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb6b360de in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb4a86700 (LWP 19093)): #0 0xb7ef8424 in __kernel_vsyscall () #1 0xb6af2376 in nanosleep () from /lib/i686/cmov/libc.so.6 #2 0xb6af218e in sleep () from /lib/i686/cmov/libc.so.6 #3 0xb7c35738 in ?? () from /usr/lib/libkdeui.so.5 #4 0x in ?? () -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 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 kontact depends on: ii kdebase-runtime 4:4.2.2-1 runtime components from the offici ii kdelibs5 4:4.2.2-2 core libraries for all KDE 4 appli ii kdepimlibs5 4:4.2.2-1 core libraries for KDE PIM 4 appli ii libc6 2.9-6 GNU C Library: Shared libraries ii libkdepim44:4.2.2-1 KDE PIM library ii libkontactinterfaces4 4:4.2.2-1 KDE Kontact interface library ii libqt4-dbus 4.4.3-2Qt 4 D-Bus module ii libqt4-qt3support 4.4.3-2Qt 3 compatibility library for Qt ii libqtcore44.4.3-2Qt 4 core module ii libqtgui4 4.4.3-2Qt 4 GUI module ii libstdc++64.3.3-7The GNU Standard C++ Library v3 Versions of packages kontact recommends: ii akregator 4:4.2.2-1 RSS feed aggregator for KDE ii kaddressbook 4:4.2.2-1 KDE address book ii kmail 4:4.2.2-1 KDE Email client ii knotes4:4.2.2-1 KDE sticky notes ii korganizer4:4.2.2-1 KDE personal organizer Versions of packages kontact suggests: pn gnokiinone (no description available) ii kjots 4:4.2.2-1 note-taking utility for KDE 4 ii knode 4:4.2.2-1 KDE news reader pn ktimeticker none (no description available) -- no debconf information -- Man, do you know how to save the desktop from X-Windows 5.4? From the control preferences inside Word XP you should insert a TCP display. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Update submitter address for my bugs
Processing commands for cont...@bugs.debian.org: # bugs from schep...@math.unipd.it submitter 390095 ! Bug#390095: klash: No control keys working Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 419472 ! Bug#419472: aegis: FTBFS under pbuilder even building as non-root Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 451447 ! Bug#451447: libperldoc-search-perl: FTBFS: Undefined subroutine Swish::API::Common::VERSION called Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 453072 ! Bug#453072: gcj-4.2: Java processes are memory hogs on amd64 Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 390094 ! Bug#390094: gnash: www.homestarrunner.com movies missing clipping Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 418943 ! Bug#418943: less: Please support lzma in lessfile/pipe Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 445816 ! Bug#445816: cfs: FTBFS with parallel build Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 445819 ! Bug#445819: dietlibc: FTBFS with parallel build Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 445823 ! Bug#445823: freecdb: FTBFS with parallel build Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 395154 ! Bug#395154: [process.in] support Blocks: at submit time Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 430889 ! Bug#430889: developers-reference: Please don't suggest vim as an example to follow Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 456429 ! Bug#456429: java-gcj-compat: Downgrade libmx4j-java to Recommends or Suggests Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 431608 ! Bug#431608: [PR32900] Abysmal performance compiling python-qt3 Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. submitter 457402 ! Bug#457402: gnuradio: Build-Depends on non-free package sdcc Changed Bug submitter from Daniel Schepler schep...@math.unipd.it to Daniel Schepler dschep...@gmail.com. # bugs from schep...@math.berkeley.edu submitter 483853 ! Bug#483853: libwww-doc: FTBFS: Section mismatch between control and file list Changed Bug submitter from Daniel Schepler schep...@math.berkeley.edu to Daniel Schepler dschep...@gmail.com. submitter 516425 ! Bug#516425: happy: FTBFS: Not in scope: `buildVerbose' Changed Bug submitter from Daniel Schepler schep...@math.berkeley.edu to Daniel Schepler dschep...@gmail.com. submitter 518851 ! Bug#518851: sockstat: FTBFS: 'CHAR_BIT' undeclared Changed Bug submitter from Daniel Schepler schep...@math.berkeley.edu to Daniel Schepler dschep...@gmail.com. submitter 518857 ! Bug#518857: irmp3-ncurses: FTBFS: 'NI_MAXHOST' undeclared Changed Bug submitter from Daniel Schepler schep...@math.berkeley.edu to Daniel Schepler dschep...@gmail.com. submitter 518863 ! Bug#518863: yasr: FTBFS: Conflicting types for 'openpty' Changed Bug submitter from Daniel Schepler schep...@math.berkeley.edu to Daniel Schepler dschep...@gmail.com. submitter 51 ! Bug#51: fam: FTBFS: 'NULL' was not declared in this scope Changed Bug submitter from Daniel Schepler schep...@math.berkeley.edu to Daniel Schepler dschep...@gmail.com. submitter 518890 ! Bug#518890: wmaloader: FTBFS: 'SSIZE_MAX' undeclared Changed Bug submitter from Daniel Schepler schep...@math.berkeley.edu to Daniel Schepler dschep...@gmail.com. submitter 519490 ! Bug#519490: FTBFS: compiler parser error Changed Bug submitter from Daniel Schepler schep...@math.berkeley.edu to Daniel Schepler dschep...@gmail.com. submitter 520853 ! Bug#520853: gpm: FTBFS: storage size of 'sucred' is unknown Changed Bug submitter from Daniel Schepler schep...@math.berkeley.edu to Daniel Schepler dschep...@gmail.com. submitter 521915 ! Bug#521915: epos: FTBFS: cannot stat `./644' Changed Bug submitter from Daniel Schepler schep...@math.berkeley.edu to Daniel Schepler dschep...@gmail.com. submitter 521937 ! Bug#521937: gplanarity: FTBFS: cannot find -ljasper Changed Bug submitter from Daniel Schepler schep...@math.berkeley.edu to Daniel Schepler dschep...@gmail.com. submitter 521952 ! Bug#521952: jbofihe: FTBFS: 'STAG_BO' undeclared Changed Bug submitter from Daniel Schepler schep...@math.berkeley.edu to
Bug#523363: kontact: problem at logon when starting kontact
On Thursday 09 April 2009 17:52:12 Sune Vuorela wrote: On Thursday 09 April 2009 17:50:56 Andres Mejia wrote: Package: kontact Version: 4:4.2.2-1 Severity: normal I have a problem with kontact at logon. When you logoff from a session without closing kontact first, and then log back on, I get the standard prompt from kwallet and another prompt stating the following. 'Kontact already seems to be running on another display on this machine. Running Kontact more than once can cause the loss of mail. You should not start Kontact unless you are sure that it is not already running.' Then there's two prompts. Selecting 'Start Kontact' and then entering my passphrase in kwallet will start two instances of kontact. Selecting 'Exit' will not start kontact at all. Do you have kontact to start twice? I had set kontact to autostart in my .kde/Autostart dir and also as part of a saved session, and I saw this exact behaviour. I don't have kontact set to autostart. Not sure what you mean by saved session. This behavior happens to me when I leave kontact open when logging off and then logging back on. /Sune Furthermore, with the two instances of kontact running, closing one will close the other as well, probably because it crashes. In the end, I have to manually start kontact again anyway. Here's a copy of the crash dump of the crash I mentioned. Application: Kontact (kontact), signal SIGSEGV [Current thread is 0 (LWP 19093)] Thread 3 (Thread 0xb0d32b90 (LWP 19330)): #0 0xb7ef8424 in __kernel_vsyscall () #1 0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6 #3 0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb75f752e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb6b360de in clone () from /lib/i686/cmov/libc.so.6 Thread 2 (Thread 0xb020eb90 (LWP 19337)): #0 0xb7ef8424 in __kernel_vsyscall () #1 0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6 #3 0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb75f752e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb6b360de in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb4a86700 (LWP 19093)): #0 0xb7ef8424 in __kernel_vsyscall () #1 0xb6af2376 in nanosleep () from /lib/i686/cmov/libc.so.6 #2 0xb6af218e in sleep () from /lib/i686/cmov/libc.so.6 #3 0xb7c35738 in ?? () from /usr/lib/libkdeui.so.5 #4 0x in ?? () -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 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 kontact depends on: ii kdebase-runtime 4:4.2.2-1 runtime components from the offici ii kdelibs5 4:4.2.2-2 core libraries for all KDE 4 appli ii kdepimlibs5 4:4.2.2-1 core libraries for KDE PIM 4 appli ii libc6 2.9-6 GNU C Library: Shared libraries ii libkdepim4 4:4.2.2-1 KDE PIM library ii libkontactinterfaces4 4:4.2.2-1 KDE Kontact interface library ii libqt4-dbus 4.4.3-2Qt 4 D-Bus module ii libqt4-qt3support 4.4.3-2Qt 3 compatibility library for Qt ii libqtcore44.4.3-2Qt 4 core module ii libqtgui4 4.4.3-2Qt 4 GUI module ii libstdc++64.3.3-7The GNU Standard C++ Library v3 Versions of packages kontact recommends: ii akregator 4:4.2.2-1 RSS feed aggregator for KDE ii kaddressbook 4:4.2.2-1 KDE address book ii kmail 4:4.2.2-1 KDE Email client ii knotes4:4.2.2-1 KDE sticky notes ii korganizer4:4.2.2-1 KDE personal organizer Versions of packages kontact suggests: pn gnokiinone (no description available) ii kjots 4:4.2.2-1 note-taking utility for KDE 4 ii knode 4:4.2.2-1 KDE news reader pn ktimeticker none (no description available) -- no debconf information -- Regards, Andres -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact
Re: Lancelot locks accessing NTFS partition
On 2009-04-09, Boyd Stephen Smith Jr. b...@iguanasuicide.net wrote: As far as the effort required to wrangle the bugs, this can be spread out b= y=20 getting users involved. KDE itself has had some pretty good luck with Bug= =20 Days where users meet developers on IRC (or whatever) and confirm/deny bug= s,=20 provide more details on how to reproduce, perhaps even try out patches. I will announce such a bug day in debian-kde shortly - when I have coordinated enough with the KDE bugsquad to not collide with their activities - and maybe have them to help. Last time I took it on myself to update bugs, I got some fairly stern email= s=20 indicating that changes need to go through the maintainers, but I am willin= g=20 to help. Thank you for offer for help. You are most welcome to forward all the kde bugs that aren't debian specific to bugs.kde.org. /Sune -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lancelot locks accessing NTFS partition
Hello, On 2009 m. April 9 d., Thursday 04:14:26 Boyd Stephen Smith Jr. wrote: Another good reason to file bugs that affect Debian in the DBTS even if they are already upstream: apt-listbugs. As I said, RC (grave, serious, critical) should end up in Debian BTS as they are likely to affect many Debian users and even do harm. That's fine. If Debian can't shoulder the burden of maintaining KDE, they shouldn't be packaging it. Debian maintainers should be ready to receive bug reports from Debian users. I should not have to run another distribution or compile KDE from source before I file a bug. Well, I will clarify you a few facts now: 1) If you report an obvious(!!!) upstream bug to Debian BTS which is of non-RC severity, the most attention you will probably get is a forwarded tag being added (if you are lucky). 2) We will probably never forward a new upstream bug reported to the Debian BTS to KDE BTS (i.e. open a new bug) and we will not play proxy between the user and upstream. 3) If you don't like something, you can either: 3a) do the job in the areas which are lacking in your opinion (the world is not perfect). But please don't tell everybody else what to do. 3b) switch to something else where the job is done better. 4) By doing 1) and 2) you clutter Debian BTS and real bugs which could and should be solved locally in Debian get lost. As Sune said, it's impossible for the Debian people to handle this, No its not. It takes effort. But that effort is required of every Debian maintainer. Can you think how fast a RFS on the debian-mentors list would be denied if accompanied by I won't have time to deal with bugs, please file them all upstream.? KDE is not a 20K source package. KDE is HUGE. Please do some background research before telling something. I am NOT saying I don't appreciate the effort the maintainers are putting forth now. That's exactly what you are saying. If I could get both my jobs and the development I do for my local charity in hand, I'd pitch in and help. But, wrangling bugs is *just* *as* *important* as packaging new versions. It may not be quite as sexy, but it makes for better software, not just more of it. Sorry, but you have no right to tell other volunteers what they have to do in their free time. You are free to do 3a) though (regularly). According to the official documents, if you open a bug in the DBTS, you should not open one upstream, but leave it up to the maintainer. Yeah, yeah, but you can spin official documents as much as you want. That BTS page is not more official than me telling you how things work currently. If you want an upstream bug to be solved, you better report it to KDE BTS. Or it won't be solved unless another user reports it upstream (as simple as that). I get my OS from one source, the Debian repositories (and initially the Debian cdimage ftp server). I should only need to provide feedback to one source: Debian. Maintainers are ultimately responsible for what I receive; *NOT* upstream. If you don't have enough time to *maintain* the package, don't even bother packaging it. Lets file KDE removal bug then. I guess 100% of Debian users will be more happy with that than currently situation. Again: the whole thing that I get is the Debian package, and the maintainer is definitely involved in that. Again: try doing the real work first before telling others what to do. As far as the effort required to wrangle the bugs, this can be spread out by getting users involved. KDE itself has had some pretty good luck with Bug Days where users meet developers on IRC (or whatever) and confirm/deny bugs, provide more details on how to reproduce, perhaps even try out patches. Last time I took it on myself to update bugs, I got some fairly stern emails indicating that changes need to go through the maintainers, but I am willing to help. So I say, HELP HELP HELP. Nobody is going to object. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Re: Lancelot locks accessing NTFS partition
On Thursday 09 April 2009 11:14:26 Boyd Stephen Smith Jr. wrote: Are you aware about how many Debian packagers has the Qt/KDE team? Do you imagine how many time is needed to handle this? And not only the KDE people, but other teams as well. If Debian can't shoulder the burden of maintaining KDE, they shouldn't be packaging it. Debian maintainers should be ready to receive bug reports from Debian users. I should not have to run another distribution or compile KDE from source before I file a bug. Boyd, You are going to start seeing a lot more messages like this one when you file a bug with a Debian package. I am the Debian maintainer for the hplip package: ! For end user support please Ask a question at the ! upstream hplip support site: ! https://answers.launchpad.net/hplip/+addquestion ! ! If you know that the bug you want to report is in the upstream ! code then please file report in the upstream hplip bug tracking system: ! https://launchpad.net/hplip/+filebug ! ! If you feel that the bug is one that other Debian users should ! know about then you are welcome to file a report in the Debian BTS ! as well. Please keep in mind, however, that managing bug reports ! is part of the maintainers' workload. Why have I done this? Because I am not able to keep on top of the bugs reports, let alone the packaging upstream releases and the like to maintain this and other packages. Also a lot of bugs are just upstream bugs and in most (all) cases it would be a lot better if the end user were talking directly to upstream. Sure if another 5 people wanted to come and help with the bugs then I wouldn't have to do this, but there aren't 5 people helping, so the users reporting the bugs can help and forward the bug to the place where they will get the fastest response to their issues. In a lot of cases the Debian maintain is on the upstream bug tracking list as well and will comment directly there when/ if things are being reported that are directly specific to the Debian package. You don't need to run a different distribution to report a bug upstream. Upstream will happily take reports from any users and will respond to your issues. However if you report another upstream bug to the BTS, the Debian maintainer may not be in a position to forward the bug upstream for many days/ weeks/ months if at all. So the end user doesn't get any feedback on their bug either. Users don't need a 'bug-day' to forward bugs upstream. Anyone can do that at any time and at any stage of the project. I hope you are contributing with every post you are making here to debian-kde and also forwarding a bug upstream. Takes me about 3-6 minutes per bug. Because that is what Debian is about. Lots of people, like you, doing a little bit of work when they have some spare time. So with your next spare 3 minutes, look at the BTS, check if a bug is still relevant, forward it upstream, and mark it as forwarded in the BTS. Mark signature.asc Description: This is a digitally signed message part.
Discussions with no sense
I'm new in this list, but I use KDE and Debian from long time ago. It's great to see this community of users that works for make the use of this pieces of software a better experience. But is a little disappointing to see that the more long discussions have to be more with personal problems/opinions than with the software (like Lancelot locks accessing NTFS partition or KDE 4.2 moving to unstable *this* week threads). It's always like that? The users (like me) are always so hard to understand the point of view of the developers? I think that we should just shut up some times and accept the opinion of people that knows things because it's doing it, and not because thinks that would be made in some way. Maybe I'm wrong, it's just my opinion. Thanks for all anyway, your help it's appreciated, and the results are wonderful. Enzo -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debian Lenny for the PPC (Iceweasel Misbehaves)
El Jueves 09 Abril 2009 03:07:37 Irena Richard Jenkins escribió: Not sure of the problem here, but Iceweasel has refused to start. Tried de-installing and re-installing ... with no improvement. I am left with Konqueror. However, I need Iceweasel or something similar to speak with my bank, etc. Is this a known hiccup, for the ppc install ... or are work-arounds available? I did try running as 'root' ... but there are issues ¿You tried also to rename your /home/user/.mozilla folder and launch Iceweasel to force the creation of new user's settings; or to launch it from a new user account? Also you did the uninstalltion with --purge? it's supposed to remove any possible remaining configuration files of the program you uninstall so when you reinstall, the reinstallation is really a fresh one. If you are in a hurry a temporal workaround could be using Firefox on Wine, or Virtualbox, I don't remember very well, sorry, I read a copule of months ago that it worked flawlessly. For more serious help I'd read and/or ask in http://forums.mozillazine.org -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debian Lenny for the PPC (Iceweasel Misbehaves)
Oh, and as Lisandro has said. Iceweasel has nothing to do, so this is not the best list to ask, :-/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
KMail (KDE 4.2.2) indexing? again and again
I just migrated from kde 3.5 to kde 4.2.2 (unstable). My system is up-to-date. From time to time, kmail eats up CPU, Disk I/O and memory while it seems to go through all emails (~25.000 and ~4,5 GB). Started from konsole, kmail outputs lines like: kmail(6098)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= /usr/oms/Mail/.MailingLists.directory/Andere/cur/1239002674.5913.zKNVK:2,S , r+) == stream == 0x9ae7668 kmail(6098)/kmail (storage internals) KMFolderMaildir::getDwString: fclose(mIndexStream = 0x9ae7668 ) kmail(6098)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= /usr/oms/Mail/.MailingLists.directory/Andere/cur/1239009776.5913.15eQ9:2,S , r+) == stream == 0x9a2c7a0 kmail(6098)/kmail (storage internals) KMFolderMaildir::getDwString: fclose(mIndexStream = 0x9a2c7a0 ) I already stopped kmail, removed all index files, started again. Kmail than rebuilds the index files - that's what i expect. after a few minutes pausing, kmail seems to start again... pausing... starting...etc. I have the 'feeling' that something triggers the reindexing, like a new incoming email or searching for an email. When I say 'reindexing', i am not shure if this is really what kmail does. Does anyone has an idea how to switch this behaviour off, since it is a killer (kmail is almost unusable when doing so) ?. Regards, Tim -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussions with no sense
Hello, On 2009 m. April 9 d., Thursday 14:58:18 Enzo wrote: But is a little disappointing to see that the more long discussions have to be more with personal problems/opinions than with the software (like Lancelot locks accessing NTFS partition or KDE 4.2 moving to unstable *this* week threads). The last few weeks were quite tense. Therefore discussions sometimes became quite offensive. Another reason is that they both were quite long overdue. For example, Debian KDE bug handling policy (it became such over time unwillingly and I don't see it changing due to the lack of manpower) has already been like this for the last couple of years (hence the number of bugs which has accumulated). However, it has simply never been official stated or explained anywhere. We know it might NOT be perfect or even good, however it is the best Debian Qt/KDE Team can do at the moment. I believe it is better for users to know that beforehand than get angry and annoyed because nobody cares about her/his bug report... And now here come people out of blue who say: If Debian can't shoulder the burden of maintaining KDE, they shouldn't be packaging it. That's harsh, disrespectful and quite insulting statement for both users and developers. Sometimes people forget that Debian is community/volunteer driven and we try to do our best. Suggestions about improvements are welcome, but demands are very impolite and unfair. It's always like that? Nop. I think it will get back to normal soon with another spike when KDE 4 migrates to testing. The users (like me) are always so hard to understand the point of view of the developers? I think most users understand perfectly. I think that we should just shut up some times and accept the opinion of people that knows things because it's doing it, and not because thinks that would be made in some way. Maybe I'm wrong, it's just my opinion. Thanks for all anyway, your help it's appreciated, and the results are wonderful. You are absolutely right. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Re: Lancelot locks accessing NTFS partition
On Thursday 09 April 2009 04:23:41 you wrote: On Thursday 09 April 2009 11:14:26 Boyd Stephen Smith Jr. wrote: Are you aware about how many Debian packagers has the Qt/KDE team? Do you imagine how many time is needed to handle this? And not only the KDE people, but other teams as well. If Debian can't shoulder the burden of maintaining KDE, they shouldn't be packaging it. Debian maintainers should be ready to receive bug reports from Debian users. I should not have to run another distribution or compile KDE from source before I file a bug. Boyd, You are going to start seeing a lot more messages like this one when you file a bug with a Debian package. I am the Debian maintainer for the hplip package: ! For end user support please Ask a question at the ! upstream hplip support site: ! https://answers.launchpad.net/hplip/+addquestion ! ! If you know that the bug you want to report is in the upstream ! code then please file report in the upstream hplip bug tracking system: ! https://launchpad.net/hplip/+filebug ! ! If you feel that the bug is one that other Debian users should ! know about then you are welcome to file a report in the Debian BTS ! as well. Please keep in mind, however, that managing bug reports ! is part of the maintainers' workload. I find that unfortunate, but clearly acceptable. BTW, for end user support you are welcome to point then at debian-user etc. We try and handle what questions we can. You don't need to run a different distribution to report a bug upstream. Upstream will happily take reports from any users and will respond to your issues. How am I supposed to determine if it is non-Debian-specific without running a different distribution or compiling from source? If it's Debian-specific, I'm wasting upstreams time. If it's not, it's still a bug in Debian. Actually, for hard crashes, if I can get a backtrace I know how to figure out if that line of code came from upstream or a Debian patch. I'm not sure the best way to do that for other bugs, but I'll try. Users don't need a 'bug-day' to forward bugs upstream. Anyone can do that at any time and at any stage of the project. Last time I tagged a bug without emailing the maintainer and waiting for a reply, I got a stern response from a different DD basically saying don't do that. But, I'll take this a permission to wrangle a few KDE bugs. Also, Bug Days can help because they get multiple users together with the maintainer(s) and developer(s) so the overlapping fields of knowledge can all be used at once. They also let interested wranglers single-task on bugs for at least a few hours; studies show virtually everyone is more productive when single-tasking than multi-tasking. Still, you don't have to be a maintainer to organize a Bug Day as long as you can get one or two to participate. So, the onus is on myself to organize one if I think one would be useful. I hope you are contributing with every post you are making here to debian-kde and also forwarding a bug upstream. Takes me about 3-6 minutes per bug. Because that is what Debian is about. Lots of people, like you, doing a little bit of work when they have some spare time. So with your next spare 3 minutes, look at the BTS, check if a bug is still relevant, forward it upstream, and mark it as forwarded in the BTS. Will do. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Lancelot locks accessing NTFS partition
El Jueves, 9 de Abril de 2009, Boyd Stephen Smith Jr. escribió: Can you think how fast a RFS on the debian-mentors list would be denied if accompanied by I won't have time to deal with bugs, please file them all upstream.? I maintained two KDE-related packages in Debian, and of course I dealt with the bugs I received. But if I alone had to deal with the huge number of reports that a popular KDE module receives, I could simply not do it. Of course, I could handle the Debian specific problems, or one user from time to time who did a tiny mistake reporting it on Debian's BTS. But not all the users of the package reporting it _on purpose_ as a Debian bug. It would be nice if I could, though, but I don't think that almost anyone could do that on their free time. I get my OS from one source, the Debian repositories (and initially the Debian cdimage ftp server). I should only need to provide feedback to one source: Debian. Come on: nobody reports to their ISP the problems of 3rd party websites. And they don't ask the shop were the bought a Windows box a problem they had with the software. Maintainers are ultimately responsible for what I receive; *NOT* upstream. If you don't have enough time to *maintain* the package, don't even bother packaging it. You just maintain the package, that is, the work you do, and the software you write, not the rest. -- Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2 http://barnacity.net/ | http://disperso.net -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lancelot locks accessing NTFS partition
In 200904091114.11428.modes...@vainius.eu, Modestas Vainius wrote: If Debian can't shoulder the burden of maintaining KDE, they shouldn't be packaging it. Debian maintainers should be ready to receive bug reports from Debian users. I should not have to run another distribution or compile KDE from source before I file a bug. Well, I will clarify you a few facts now: 2) We will probably never forward a new upstream bug reported to the Debian BTS to KDE BTS (i.e. open a new bug) and we will not play proxy between the user and upstream. This is part of being a maintainer. If you aren't willing to do it, you aren't being a very good maintainer. 3) If you don't like something, you can either: 3a) do the job in the areas which are lacking in your opinion (the world is not perfect). But please don't tell everybody else what to do. 3b) switch to something else where the job is done better. 3c) Make an impassioned plea to get others to do the job. Especially others that *already* volunteered for that job. Heck, sometimes you make a bigger impact campaigning for volunteers instead of trying to do it all yourself. Plus, I'm not going to let you tell me what my choices are. I can determine that myself and take whatever action I feel would be best. As Sune said, it's impossible for the Debian people to handle this, No its not. It takes effort. But that effort is required of every Debian maintainer. Can you think how fast a RFS on the debian-mentors list would be denied if accompanied by I won't have time to deal with bugs, please file them all upstream.? KDE is not a 20K source package. KDE is HUGE. Please do some background research before telling something. Why do you think I don't understand the size of KDE? I do. I am a developer by trade and I have adventured in the KDE svn repository in search of the origin of a bug. My current job is porting millions of lines of code in multiple languages from AIX to Linux. I am NOT saying I don't appreciate the effort the maintainers are putting forth now. That's exactly what you are saying. No, it's not. I love the new packages in unstable. I've heard other had problems upgradings (a few reports from friends and 2 on debian-user), but it went smooth as silk for me. I absolutely do appreciate what they are doing. That doesn't make me willing to let them shirk the responsibilities of a maintainer. If I could get both my jobs and the development I do for my local charity in hand, I'd pitch in and help. But, wrangling bugs is *just* *as* *important* as packaging new versions. It may not be quite as sexy, but it makes for better software, not just more of it. Sorry, but you have no right to tell other volunteers what they have to do in their free time. You are free to do 3a) though (regularly). I have the right to air my opinions. I don't have rank or authority in Debian; I am just a user. According to the official documents, if you open a bug in the DBTS, you should not open one upstream, but leave it up to the maintainer. Yeah, yeah, but you can spin official documents as much as you want. That BTS page is not more official than me telling you how things work currently. If you aren't willing to follow the official documents why should anyone else? If you want official documentation to change, there are established procedures for that. You shouldn't ignore them or change them by fiat just because they don't serve your purposes right now. If you want an upstream bug to be solved, you better report it to KDE BTS. Or it won't be solved unless another user reports it upstream (as simple as that). How is a non-technical Debian user supposed to know if a bug is Debian- specific or not without installing a different distribution? They know they got the software from Debian and it is broken, they should be able to file their bug with Debian. Maintainers should be prepared to forward a bug if need be. Won't someone please think of the users? Last time I took it on myself to update bugs, I got some fairly stern emails indicating that changes need to go through the maintainers, but I am willing to help. So I say, HELP HELP HELP. Nobody is going to object. Will do. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Discussions with no sense
Modestas Vainius escribió: Hello, On 2009 m. April 9 d., Thursday 14:58:18 Enzo wrote: But is a little disappointing to see that the more long discussions have to be more with personal problems/opinions than with the software (like Lancelot locks accessing NTFS partition or KDE 4.2 moving to unstable *this* week threads). The last few weeks were quite tense. Therefore discussions sometimes became quite offensive. Another reason is that they both were quite long overdue. For example, Debian KDE bug handling policy (it became such over time unwillingly and I don't see it changing due to the lack of manpower) has already been like this for the last couple of years (hence the number of bugs which has accumulated). However, it has simply never been official stated or explained anywhere. We know it might NOT be perfect or even good, however it is the best Debian Qt/KDE Team can do at the moment. I believe it is better for users to know that beforehand than get angry and annoyed because nobody cares about her/his bug report... And now here come people out of blue who say: If Debian can't shoulder the burden of maintaining KDE, they shouldn't be packaging it. That's harsh, disrespectful and quite insulting statement for both users and developers. Sometimes people forget that Debian is community/volunteer driven and we try to do our best. Suggestions about improvements are welcome, but demands are very impolite and unfair. It's always like that? Nop. I think it will get back to normal soon with another spike when KDE 4 migrates to testing. The users (like me) are always so hard to understand the point of view of the developers? I think most users understand perfectly. I think that we should just shut up some times and accept the opinion of people that knows things because it's doing it, and not because thinks that would be made in some way. Maybe I'm wrong, it's just my opinion. Thanks for all anyway, your help it's appreciated, and the results are wonderful. You are absolutely right. Thanks for the reply, Modestas. About the lack of manpower, how could I contribute? I don't have a lot of free time or big knowledge, but surely all starts from the beginning. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lancelot locks accessing NTFS partition
In 200904091620.34787@badopi.org, Alejandro Exojo wrote: El Jueves, 9 de Abril de 2009, Boyd Stephen Smith Jr. escribió: I get my OS from one source, the Debian repositories (and initially the Debian cdimage ftp server). I should only need to provide feedback to one source: Debian. Come on: nobody reports to their ISP the problems of 3rd party websites. Debian is not like an ISP. They don't simply serve as a medium through which unmodified data passes. Debian maintainers add to and change upstream to make Debian a complete system. If my ISP is routinely, detectably modifying the data I receive from third parties, they better be prepared to receive come calls. And they don't ask the shop were the bought a Windows box a problem they had with the software. Um, yes they do. Often. Or at least they did when I worked for a guy that sold Windows boxes. Dell/Gateway/HP do plenty of end-user support. Maintainers are ultimately responsible for what I receive; *NOT* upstream. If you don't have enough time to *maintain* the package, don't even bother packaging it. You just maintain the package, that is, the work you do, and the software you write, not the rest. Not true. If there's a security bug in a Debian package, it gets fixed even if upstream isn't happy with the way Debian does it. Other bugs should be handled the same way. Upstream is a valuable resource for Debian maintainers, but ultimately they are responsible for what they are providing users. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Lancelot locks accessing NTFS partition
El Jueves 09 Abril 2009 16:46:44 Boyd Stephen Smith Jr. escribió: How is a non-technical Debian user supposed to know if a bug is Debian- specific or not without installing a different distribution? Asking in upstream forums to see if users of different distributions are experiencing the same problems? From my common user's point of view it doesn't seem to me that hard. As Sune, or Modestas, I dont remember, have said, if they had more manpower perhaps some suggestions you make would be factible; but users have to admit that sometimes we demand too much from a group of not so many people who work as much as they can in their spare time, therefore do it perfectly or you better don't do it may be a bit harsh demand. I'd admit such dialectics in case Debian were a corporate-mantained distribution which is constantly advertising itself and telling the users hey, we are cooler than others, use us, but not being this the case I think users must do some search before flooding Debain mantainers with bug reports which may be not their fault, and if we don't want to do such effort, well, we have Kubuntu, Suse and other distros mor user-friendly. This isn't of course an excuse to say that users have to obey mantainers' will unconditionally, but considering the nature of Debian there should be some equilibrium. I repeat: I'm saying this from an ignorant, and perhaps wrong, ergo totally humble, point of view. Pax et amor , ;) -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussions with no sense
On 2009-04-09, Enzo zca...@gmail.com wrote: Thanks for the reply, Modestas. About the lack of manpower, how could I contribute? I don't have a lot of free time or big knowledge, but surely all starts from the beginning. The current place, where help is most welcomed no matter skill level, is helping with the bug load and get the bug count of non-forwarded bugs in debian down. on the graphs I pointed earlier, getting the green and the red line to almost get to each other - and make it stay that way. /Sune -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
components not working after upgrade to KDE 422 (and move to .kde)
Hello I'm using KDE 4 since the beginning (on Sid with experimental packages). Yesterday I've upgraded to KDE 422 and migrate my .kde4 to .kde Some hardware related things are not working anymore since the upgrade (I'm using a laptop): - phonon says that the sound card has been removed - the network-manager applet put the wifi controler on off and thus doesn't access wifi networks, it also crash the whole plasma desktop when I try to change the number of wifi networks displayed. - the battery monitor plasma applet doesn't detect the battery any more - powerdevil can't restore the display after suspend to ram. I've checked with Fedora 10 that all theses components are still working normaly. I've upgraded several other packages at the same time I've upgraded KDE, so may be this is not KDE related, but browsing the list of packages I can't found any related one, except may be acpid. So, before investigate and make some bug reports, I wonder if this is KDE known problems ? thanks xavier -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: components not working after upgrade to KDE 422 (and move to .kde)
On 2009-04-09, Xavier Brochard xav...@alternatif.org wrote: Hello I'm using KDE 4 since the beginning (on Sid with experimental packages). Yesterday I've upgraded to KDE 422 and migrate my .kde4 to .kde Some hardware related things are not working anymore since the upgrade (I'm using a laptop): - phonon says that the sound card has been removed - the network-manager applet put the wifi controler on off and thus doesn't access wifi networks, it also crash the whole plasma desktop when I try to change the number of wifi networks displayed. - the battery monitor plasma applet doesn't detect the battery any more - powerdevil can't restore the display after suspend to ram. I've checked with Fedora 10 that all theses components are still working normaly. I've upgraded several other packages at the same time I've upgraded KDE, so may be this is not KDE related, but browsing the list of packages I can't found any related one, except may be acpid. So, before investigate and make some bug reports, I wonder if this is KDE known problems ? You are at least the first to report this in a kde context. My best guess would be that this is completely unrelated to kde, but maybe a kernel upgrade or a hal upgrade ? /Sune -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussions with no sense
On Thu, Apr 09, 2009 at 08:58:18AM -0300, Enzo wrote: ... *this* week threads). It's always like that? 99% of the time, this is a nice list. I am myself surprised sometimes with the good ratio signal-noise. I chose this time ignore some mails and use my time in something better. Ana, who chose this time ignore some mails and use her time more productively than answering some people. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lancelot locks accessing NTFS partition
Alle Thursday 09 April 2009, Alejandro Exojo ha scritto: El Jueves, 9 de Abril de 2009, Boyd Stephen Smith Jr. escribió: Can you think how fast a RFS on the debian-mentors list would be denied if accompanied by I won't have time to deal with bugs, please file them all upstream.? I maintained two KDE-related packages in Debian, and of course I dealt with the bugs I received. But if I alone had to deal with the huge number of reports that a popular KDE module receives, I could simply not do it. Of course, I could handle the Debian specific problems, or one user from time to time who did a tiny mistake reporting it on Debian's BTS. But not all the users of the package reporting it _on purpose_ as a Debian bug. It would be nice if I could, though, but I don't think that almost anyone could do that on their free time. I get my OS from one source, the Debian repositories (and initially the Debian cdimage ftp server). I should only need to provide feedback to one source: Debian. Come on: nobody reports to their ISP the problems of 3rd party websites. And they don't ask the shop were the bought a Windows box a problem they had with the software. Maintainers are ultimately responsible for what I receive; *NOT* upstream. If you don't have enough time to *maintain* the package, don't even bother packaging it. You just maintain the package, that is, the work you do, and the software you write, not the rest. -- Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2 http://barnacity.net/ | http://disperso.net Never thought to start a topic like that... Anyhow, premised that none con be forced to do anything in free software, it's clear that from developers to users we are working altogether to make things better contributing in different ways and to different extents. Discussion has moved around the two poles: on a side there are rules, on the other, practical behaviors. Given that you can demonstrate everything you want by paradoxes like: if all users start filing bugs belonging to upstream to DBTS, blah blah or if you don't do a perfect work, then quit, blah blah. Luckily, bugs are not infinite, users are not brainless (almost), but sorely, developers are too few. Now we must check reality and see if someone can join you in developing and users can be so accurate (at least trained) to understand that a bug belongs to upstream. Boyd has made an harsh comment, but very likely IMHO, without meaning to offend anybody here: taking it personally is beyond what he meant. From my good human experience with Computer Scientists, I can say that harsh comments it's a lifestyle for them, a kind of feature. Generally you don't mind this. Now, please let's find the way to work in common. Valerio
Re: Lancelot locks accessing NTFS partition
Hello, On 2009 m. April 9 d., Thursday 17:46:44 Boyd Stephen Smith Jr. wrote: 2) We will probably never forward a new upstream bug reported to the Debian BTS to KDE BTS (i.e. open a new bug) and we will not play proxy between the user and upstream. This is part of being a maintainer. If you aren't willing to do it, you aren't being a very good maintainer. I think I can live with bad maintainer status then. What's good for small packages, may not work with big ones. 3c) Make an impassioned plea to get others to do the job. Especially others that *already* volunteered for that job. Heck, sometimes you make a bigger impact campaigning for volunteers instead of trying to do it all yourself. Campaigning is also work. Not everybody is good at compaigning. Why do you think I don't understand the size of KDE? I do. I am a developer by trade and I have adventured in the KDE svn repository in search of the origin of a bug. My current job is porting millions of lines of code in multiple languages from AIX to Linux. I'm not questioning your professionalism or experience. Just first try doing the job you are demanding others to do (i.e. dealing with Debian bug reports for all KDE packages). No, it's not. I love the new packages in unstable. I've heard other had problems upgradings (a few reports from friends and 2 on debian-user), but it went smooth as silk for me. I absolutely do appreciate what they are doing. That doesn't make me willing to let them shirk the responsibilities of a maintainer. By supervisoring others? Or asking for removal of KDE from Debian? Or what? You need to make compromises sometimes unless you are willing to do the work yourself. I have the right to air my opinions. I don't have rank or authority in Debian; I am just a user. Then better pick your words not to trash other people work next time. If you aren't willing to follow the official documents why should anyone else? If you want official documentation to change, there are established procedures for that. You shouldn't ignore them or change them by fiat just because they don't serve your purposes right now. That's the reason those upstream bugs are not closed as soon as they arrive at Debian BTS. But they rot there making BTS hard to find real issues which we could solve. How is a non-technical Debian user supposed to know if a bug is Debian- specific or not without installing a different distribution? They know they got the software from Debian and it is broken, they should be able to file their bug with Debian. Maintainers should be prepared to forward a bug if need be. Ask on generic kde forum, on generic kde irc channel or somewhere else first. I'm also talking about OBVIOUS upstream bugs. Btw, Debian ships as much unpatched vanilla KDE as possible. We do not backport features or even fixes for annyoing bugs from KDE trunk or random 3rd party patches. Won't someone please think of the users? The reason I'm talking with you is because I think of the users. The reason we try hard to maintain and publish _good_ packages is because we think of the users. The reason KDE is in Debian is because Debian KDE maintainers think of the users. Heck, the reason Debian exists is because Debian developers think of the users. Sure, users include developers themselves, but also all other people who find Debian usable regardless of (a few) deficiences. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Re: Lancelot locks accessing NTFS partition
In 200904091712.11218.variosin...@gmail.com, Manolete, ese artista... wrote: El Jueves 09 Abril 2009 16:46:44 Boyd Stephen Smith Jr. escribió: How is a non-technical Debian user supposed to know if a bug is Debian- specific or not without installing a different distribution? Asking in upstream forums to see if users of different distributions are experiencing the same problems? From my common user's point of view it doesn't seem to me that hard. Sounds reasonable. I think users must do some search before flooding Debain mantainers with bug reports which may be not their fault, and if we don't want to do such effort, well, we have Kubuntu, Suse and other distros mor user-friendly. The current openSUSE policy is to file KDE bugs upstream unless you can confirm they are openSUSE-specific. I find this policy to be a bit unreasonable, and I was under the impression that Debian's was much better. I'm willing to jump ship to get away from openSUSE policies I don't agree with, but I'm not willing to do the same w/ Debian. Instead, I intend to help. If wrangling KDE bugs where help is needed, I'll pencil in some time for it this weekend. This isn't of course an excuse to say that users have to obey mantainers' will unconditionally, but considering the nature of Debian there should be some equilibrium. I agree. I was harsh, but to make a point. Maintaining a Debian package has certain responsibilities that are fairly well spelled out in policy. But, despite the best of intentions sometimes maintainers cannot meet those responsibilities, through no fault of their own. I'm fine with that, I know I never seem to have the time I need either. I'm not fine with the maintainers saying Our package/team is special, so we aren't going to accept the same responsibilities. I repeat: I'm saying this from an ignorant, and perhaps wrong, ergo totally humble, point of view. Humility is a virtue that I could use more of at times. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: components not working after upgrade to KDE 422 (and move to .kde)
Hello, On 2009 m. April 9 d., Thursday 18:36:47 Xavier Brochard wrote: I'm using KDE 4 since the beginning (on Sid with experimental packages). Yesterday I've upgraded to KDE 422 and migrate my .kde4 to .kde Some hardware related things are not working anymore since the upgrade (I'm using a laptop): - phonon says that the sound card has been removed Try rm ~/.kde/share/config/phonondevicesrc - the network-manager applet put the wifi controler on off and thus doesn't access wifi networks, it also crash the whole plasma desktop when I try to change the number of wifi networks displayed. That widget is very fragile. Do not expect it to work most of the time. Or rather do not be surprised when it breaks. The reason there is no update is because later svn revision is worse than the current one in experimental. - the battery monitor plasma applet doesn't detect the battery any more - powerdevil can't restore the display after suspend to ram. powerdevil does not restore display, kernel/uswsusp/X do. battery issue might be related to hal, not sure. I've checked with Fedora 10 that all theses components are still working normaly. Could you check with fresh user account or at least with fresh ~/.kde profile? So, before investigate and make some bug reports, I wonder if this is KDE known problems ? I don't have problems with phonon and battery. However, suspend2ram does not work on my laptop due to kernel issues. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Re: components not working after upgrade to KDE 422 (and move to .kde)
Alle Thursday 09 April 2009, hai scritto: Hello I'm using KDE 4 since the beginning (on Sid with experimental packages). Yesterday I've upgraded to KDE 422 and migrate my .kde4 to .kde Some hardware related things are not working anymore since the upgrade (I'm using a laptop): - phonon says that the sound card has been removed - the network-manager applet put the wifi controler on off and thus doesn't access wifi networks, it also crash the whole plasma desktop when I try to change the number of wifi networks displayed. - the battery monitor plasma applet doesn't detect the battery any more - powerdevil can't restore the display after suspend to ram. I've checked with Fedora 10 that all theses components are still working normaly. I've upgraded several other packages at the same time I've upgraded KDE, so may be this is not KDE related, but browsing the list of packages I can't found any related one, except may be acpid. So, before investigate and make some bug reports, I wonder if this is KDE known problems ? thanks xavier Hi, I'm just guessing, but yesterday I had a problem with crucial packages, they remained un-configured because of splashy. If you have splashy my suggestion is to remove it, see this bug for more infos: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523187 I have got all the kind of strange behaviors with wi-fi, battery and so on until I removed it. My advise is not to use plasma-widget-networkmanagement since it is still in hard developing, come back to knetworkmanager or nm-applet. Hope this helps Valerio
Re: KMail (KDE 4.2.2) indexing? again and again
Is this happening on a Disconnected IMAP account ? Ritesh Tim Ruehsen wrote: I just migrated from kde 3.5 to kde 4.2.2 (unstable). My system is up-to-date. From time to time, kmail eats up CPU, Disk I/O and memory while it seems to go through all emails (~25.000 and ~4,5 GB). Started from konsole, kmail outputs lines like: kmail(6098)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= /usr/oms/Mail/.MailingLists.directory/Andere/cur/1239002674.5913.zKNVK:2,S , r+) == stream == 0x9ae7668 kmail(6098)/kmail (storage internals) KMFolderMaildir::getDwString: fclose(mIndexStream = 0x9ae7668 ) kmail(6098)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= /usr/oms/Mail/.MailingLists.directory/Andere/cur/1239009776.5913.15eQ9:2,S , r+) == stream == 0x9a2c7a0 kmail(6098)/kmail (storage internals) KMFolderMaildir::getDwString: fclose(mIndexStream = 0x9a2c7a0 ) I already stopped kmail, removed all index files, started again. Kmail than rebuilds the index files - that's what i expect. after a few minutes pausing, kmail seems to start again... pausing... starting...etc. I have the 'feeling' that something triggers the reindexing, like a new incoming email or searching for an email. When I say 'reindexing', i am not shure if this is really what kmail does. Does anyone has an idea how to switch this behaviour off, since it is a killer (kmail is almost unusable when doing so) ?. Regards, Tim -- If possible, Please CC me when replying. I'm not subscribed to the list. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: components not working after upgrade to KDE 422 (and move to .kde)
Modestas Vainius wrote: - the network-manager applet put the wifi controler on off and thus doesn't access wifi networks, it also crash the whole plasma desktop when I try to change the number of wifi networks displayed. That widget is very fragile. Do not expect it to work most of the time. Or rather do not be surprised when it breaks. The reason there is no update is because later svn revision is worse than the current one in experimental. Just wanted to add some points here. AFAIK, network-manager (and network-manager-kde) are maintained separately by Michael Biebel. The version of network-manager (+ nm-kde) in sid is very unstable. Many a times it doesn't work. VPN plugin doesn't work. I've noticed that it has been in sid for some time now. And am not sure what the criteria for it is, to enter testing. IMO, it shouldn't enter testing. The current network-manager (0.6.6) and network-manager-kde (qt3 based), in testing, are pretty stable and good. I've checked with Fedora 10 that all theses components are still working normaly. Could you check with fresh user account or at least with fresh ~/.kde profile? This is a very good point ModaX has put. I usually have a separate user account handy, where I test certain behavior, before being sure it is a bug (be it upstream or debian related). Please try it before reporting any bugs. It helps a lot. Ritesh -- If possible, Please CC me when replying. I'm not subscribed to the list. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lancelot locks accessing NTFS partition
Modestas Vainius wrote: Won't someone please think of the users? The reason I'm talking with you is because I think of the users. The reason we try hard to maintain and publish good packages is because we think of the users. The reason KDE is in Debian is because Debian KDE maintainers think of the users. Heck, the reason Debian exists is because Debian developers think of the users. Sure, users include developers themselves, but also all other people who find Debian usable regardless of (a few) deficiences. I think the Debian KDE Maintainers are doing a pretty good job. For example, I was very delighted, when I saw the announcement about Kaboom. I can't think of any other distribution (or upstream, for that matter), of thinking about the _User's_ data and how they should migrate. Upstream simply tagged it as a backward incompatible major release. And so did many of the other distributions. As far as bug handling is concerned, I think it is a challenge everywhere. I file many bug reports upstream and usually nobody even cares to respond to them, at times. And there can be 2 ways to look at it. 1) Nobody cares - KDE Sucks. 2) They are busy doing something better - Implementing features. Packaging KDE4 was a daunting task. At a time like that, focusing on other things, like bug reports et cetera is of a lower priority for the packagers. As users, we could take care of our bugs. Like the ones we report, when we see them fixed (downstream or upstream), we could mark them accordingly. That saves a lot of time for all. Ritesh -- If possible, Please CC me when replying. I'm not subscribed to the list. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Panel woes and other peculiarities
I made the switch to KDE 4 today, and over all it went rather well. Most of the annoyances are related to the panel. I may have been living under a rock not to know about this stuff, but here it goes: - I don't seem to be able to move widgets around, even though the panel is unlocked. On the left, there's the KMenu and plugged-in devices. On the far right I've managed to add a few application buttons, logout/lock, and trash. Over most of the space in the middle, the system tray stretches out. - Where do the panels get their colors from? I didn't react to changes in the Appearance Colors settings and stayed glossy black. When the panel crashed later, it reappeared in marine blue. - Is the digital clock really so dumb as to display the date in a second column instead of underneath the time? Other oddities I noticed: - Resizing Konsole windows lags by several seconds. This doesn't happen for other apps. - I can't bind Win-Shift-+ (aka Win-* on a german keyboard) to Maximize Vertically. - Akregator crashes when started with my original archive, and does so, too, after only importing the feeds.opml. I'll try to partition the feeds into smaller chunks. ~500 might be too much. Michael -- Michael Schuerig mailto:mich...@schuerig.de http://www.schuerig.de/michael/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bluetooth in KDE4
Hello folks! Today I made a dist-upgrade in Sid and got KDE4 that way. Now I can not use Bluetooth properly in KDE4. There is no Plasmoid or widget that gives me access to blueZ (neither directly nor via solid). The kdebluetooth suite from KDE3 is able to find my bluetooth dongle and I can search for bluetooth devices through it, but I can't establish any connection because the KDE3 bluetooth stuff relies on kio-slaves that don't work anymore in KDE4. I have my printer connected to my laptop via bluetooth and I use bluetooth to synchronize my appointments and contacts between my mobile phone and my laptop. Nothing of this is possible at the moment with KDE4 in Sid although it was working flawlessly in KDE3.5. I've read that there is a package called kdebluetooth4 which provides at least basic bluetooth functionality for KDE4, but it is not available in Sid. Is there any chance that I'll be able to print again anytime soon? If you need any further information to help me, I'll be glad to answer any questions that will bring me further towards a solution to my problem(s). Bye and Happy Easter Martin Neumann a.k.a. Neumaennl -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Panel woes and other peculiarities
In 200904100017.17828.mich...@schuerig.de, Michael Schuerig wrote: - I don't seem to be able to move widgets around, even though the panel is unlocked. On the left, there's the KMenu and plugged-in devices. On the far right I've managed to add a few application buttons, logout/lock, and trash. Over most of the space in the middle, the system tray stretches out. I've only had luck moving widgets when the panel settings are displayed. At point you can click a widget once to grab it, then move your pointer to where you want it and click to drop it. Regarding the system tray: Yeah, I'm pretty sure that's an upstream bug (I had a few people confirm it a couple of week ago on one of the KDE lists). The system tray seems to want to take all the extra space on the panel, unless it is on a panel with the Task Manager (or possibly another expanding widget. I haven't gotten around to filing a bug, and just worked around it locally. - Where do the panels get their colors from? IIRC, your desktop theme. Right click an empty spot on your desktop, choose Appearance, it should be on the first tab as a drop-down with previews. - Is the digital clock really so dumb as to display the date in a second column instead of underneath the time? I'm seeing the date underneath the time here. - I can't bind Win-Shift-+ (aka Win-* on a german keyboard) to Maximize Vertically. Where are you trying to do this and what error (or incorrect behavior) are you getting? - Akregator crashes when started with my original archive, and does so, too, after only importing the feeds.opml. I'll try to partition the feeds into smaller chunks. ~500 might be too much. No problems here, but I only have a few dozen feeds. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Panel woes and other peculiarities
On Friday 10 April 2009, Boyd Stephen Smith Jr. wrote: In 200904100017.17828.mich...@schuerig.de, Michael Schuerig wrote: - I don't seem to be able to move widgets around, even though the panel is unlocked. On the left, there's the KMenu and plugged-in devices. On the far right I've managed to add a few application buttons, logout/lock, and trash. Over most of the space in the middle, the system tray stretches out. I've only had luck moving widgets when the panel settings are displayed. At point you can click a widget once to grab it, then move your pointer to where you want it and click to drop it. Ah, yes, thanks, that works. Regarding the system tray: Yeah, I'm pretty sure that's an upstream bug (I had a few people confirm it a couple of week ago on one of the KDE lists). The system tray seems to want to take all the extra space on the panel, unless it is on a panel with the Task Manager (or possibly another expanding widget. I haven't gotten around to filing a bug, and just worked around it locally. I think it's an issue with the layout management. Apparently, panel widgets are packed tightly, at least I can't position them arbitrarily. Then, the stretchable widgets, such as the system tray and the digital clock take up all the place there is. - Where do the panels get their colors from? IIRC, your desktop theme. Right click an empty spot on your desktop, choose Appearance, it should be on the first tab as a drop-down with previews. Yes, I've noticed that, but I haven't seen a setting for the panel color. Anyway, that's a minor thing. - Is the digital clock really so dumb as to display the date in a second column instead of underneath the time? I'm seeing the date underneath the time here. Me too, after adjusting the panel height. Bummer. - I can't bind Win-Shift-+ (aka Win-* on a german keyboard) to Maximize Vertically. Where are you trying to do this and what error (or incorrect behavior) are you getting? In the Keyboard Mouse System Settings, Global Keyboard Shortcuts for KWin, there the action Maximize Window. When I press Win-Shift-+ for a custom setting, it makes Meta-* out of it. That's just fine, but it has no effect. Michael -- Michael Schuerig mailto:mich...@schuerig.de http://www.schuerig.de/michael/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Options for the Debian KDE team (was: Lancelot locks accessing NTFS partition)
On Friday 10 April 2009 00:46:44 Boyd Stephen Smith Jr. wrote: Won't someone please think of the users? Boyd, The Debian KDE team can do about 5-10 things in a month. Which would the users prefer: 1. Handle 2 RC bugs, build, package and upload 3 packages from KDE 4.2.x and discuss on IRC/ mailing lists etc, 2. Handle 2 RC bugs, forward 10 BTS bugs upstream and discuss on IRC/ mailing lists etc, or 3. As we don't have sufficient resources to do 1 2 at the same time, remove all KDE 4.2.x packages from Debian. In fact lets get more specific, which would you prefer? Mark signature.asc Description: This is a digitally signed message part.
Re: Bluetooth in KDE4
On Friday 10 April 2009 09:04:39 Martin Neumann wrote: Nothing of this is possible at the moment with KDE4 in Sid although it was working flawlessly in KDE3.5. Martin, Quite a few of us are using bluetooth as well. Unfortunately KDE4 doesn't have the full functionality of KDE3 so if those features are critical then you should stick with KDE3 for the time being. There is some work on packaging the bluetooth stack for KDE4 for debian, but there are a few issues which require resolution. The best place to discuss this is (Cc:): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504109 Mark signature.asc Description: This is a digitally signed message part.
