Processed: your mail
Processing commands for [EMAIL PROTECTED]: reassign 445454 kopete Bug#445454: kopete Bug reassigned from package `apt' to `kopete'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442417: recommends imagemagick
tag 442417 +wontfix thanks Hi! Ben Burton have given good reasons for the use of image-magick. I also think tha recommends is appropriate: Installed by default, so it works, but possible to not use. wontfix+closing it /Sune -- Genius, I'm not able to digit from the button, how does it work? You either need to reset the kernel of a window, or should never digit on a analogic POP utility to explore the virus over a DLL button. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: recommends imagemagick
Processing commands for [EMAIL PROTECTED]: tag 442417 +wontfix Bug#442417: recommends imagemagick There were no tags set. Tags added: wontfix thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442417: marked as done (recommends imagemagick)
Your message dated Sat, 6 Oct 2007 13:01:56 +0200 with message-id [EMAIL PROTECTED] and subject line recommends imagemagick has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: konq-plugins Version: 4:3.5.7-2 Severity: normal konq-plugins recommends imagemagick, presumably for the image gallery creation plugin. It must be a good idea that imagemagick is suggested, but it shouldn't be recommended since image gallery creation is not the only plugin. ---End Message--- ---BeginMessage--- tag 442417 +wontfix thanks Hi! Ben Burton have given good reasons for the use of image-magick. I also think tha recommends is appropriate: Installed by default, so it works, but possible to not use. wontfix+closing it /Sune -- Genius, I'm not able to digit from the button, how does it work? You either need to reset the kernel of a window, or should never digit on a analogic POP utility to explore the virus over a DLL button. ---End Message---
Bug#442069: marked as done (libqt4-dev: compiling xml examples from qt4 documentation fails)
Your message dated Sat, 6 Oct 2007 14:16:37 +0200 with message-id [EMAIL PROTECTED] and subject line libqt4-dev: compiling xml examples from qt4 documentation fails has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libqt4-dev Version: 4.3.1-2 Severity: normal I tried to compile the xml examples in the qt4 documentation, but none of them work. For example, for the streambookmarks exampe I get an error like: xbelreader.h:43:28: error: QXmlStreamReader: No such file or directory I tried the other examples too and it looks like QT can't find any of the files in the /usr/include/qt4/QtXml directory. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (700, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.21-1-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libqt4-dev depends on: ii libaudio-dev1.9-2+b1 The Network Audio System (NAS). (d ii libfreetype6-dev2.3.5-1+b1 FreeType 2 font engine, developmen ii libgl1-mesa-dev [libgl- 7.0.1-2 A free implementation of the OpenG ii libglib2.0-dev 2.14.0-2 Development files for the GLib lib ii libglu1-mesa-dev [libgl 7.0.1-2 The OpenGL utility library -- deve ii libglu1-xorg-dev1:7.2-5 transitional package for Debian et ii libice-dev 2:1.0.4-1X11 Inter-Client Exchange library ii libjpeg62-dev 6b-14Development files for the IJG JPEG ii libmng-dev 1.0.9-1 M-N-G library (Development headers ii libpng12-dev [libpng12- 1.2.15~beta5-2 PNG library - development ii libpq-dev 8.2.4-3 header files for libpq5 (PostgreSQ ii libqt4-core 4.3.1-2 Qt 4 core non-GUI functionality ru ii libqt4-gui 4.3.1-2 Qt 4 core GUI functionality runtim ii libqt4-qt3support 4.3.1-2 Qt 3 compatibility library for Qt ii libqt4-sql 4.3.1-2 Qt 4 SQL database module ii libsm-dev 2:1.0.3-1+b1 X11 Inter-Client Exchange library ii libsqlite0-dev 2.8.17-3 SQLite development files ii libx11-dev 2:1.0.3-7X11 client-side library (developme ii libxcursor-dev 1:1.1.9-1X cursor management library (devel ii libxext-dev 1:1.0.3-2X11 miscellaneous extensions libra ii libxft-dev 2.1.12-2 FreeType-based font drawing librar ii libxi-dev 2:1.1.3-1X11 Input extension library (devel ii libxinerama-dev 1:1.0.2-1X11 Xinerama extension library (de ii libxmu-dev 1:1.0.3-1X11 miscellaneous utility library ii libxrandr-dev 2:1.2.2-1X11 RandR extension library (devel ii libxrender-dev 1:0.9.3-1X Rendering Extension client libra ii libxt-dev 1:1.0.5-3X11 toolkit intrinsics library (de ii x11proto-core-dev 7.0.10-2 X11 core wire protocol and auxilia ii xlibmesa-gl-dev 1:7.2-5 transitional package for Debian et ii zlib1g-dev 1:1.2.3.3.dfsg-5 compression library - development Versions of packages libqt4-dev recommends: ii qt4-dev-tools 4.3.1-2Qt 4 development tools -- no debconf information ---End Message--- ---BeginMessage--- I should have read the documentation better. I had forgotten to add QT += xml to my .pro file. Now everything compiles just fine. ---End Message---
Bug#443600: konqueror-nsplugins: I think this was marked done prematurely
On Monday 01 October 2007, Shai Berger wrote: wildguess gtk-knowledge=rumours It is even arguable that initializing an environment (like gtk) is something only an app (like nspluginviewer) should do, and not a library (like flash) -- even though I've seen it argued that multiple GTK initialization is harmless. /wildguess nspluginviewer can't initialize any kind of environment that a plugin might or might not use. remember that this is plugins. If a plugin needs something special, then that something needs to do it. Additionally, unless it is the flash library itself which enters an infinite loop with this bug, nspluginviewer taking 100% CPU is undesired behavior; It is the flashplugins that does it. either the bug could be fixud at it roots (=in adobe) or worked around where special things are needed (=gtk). (And firefox and other gtk browsers works because they *tada* are gtk browsers - making konqueror a gtk browser isn't a choice we want to take) /Sune and whether or not nspluginviewer could behave better, konqueror (a separate process) hanging seems like a worthy bug. Hope this helps, Shai. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages konqueror-nsplugins depends on: ii kdelibs4c2a 4:3.5.7.dfsg.1-7 core libraries and binaries for al ii libc6 2.6.1-5 GNU C Library: Shared libraries ii libgcc1 1:4.2.1-5GCC support library ii libqt3-mt 3:3.3.7-9Qt GUI Library (Threaded runtime v ii libstdc++6 4.2.1-5 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-7X11 client-side library ii libxt6 1:1.0.5-3X11 toolkit intrinsics library konqueror-nsplugins recommends no packages. -- no debconf information -- Do you know how might I do for uninstalling a desktop? You neither can cancel a icon, nor should reset the periferic to the terminale, so that from MacOS 92 or from the tools inside Word you should never connect a ISA printer to cancel the space bar to a LCD folder over the laser 3D space bar. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: qt4-doc: QT = 4.2 documentation suggestions
Processing commands for [EMAIL PROTECTED]: severity 415246 wishlist Bug#415246: qt4-doc: QT = 4.2 documentation suggestions Severity set to `wishlist' from `minor' tags 415246 + upstream Bug#415246: qt4-doc: QT = 4.2 documentation suggestions There were no tags set. Tags added: upstream thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403681: kpilot: KPilot no longer works with Handspring Visor
Package: kpilot Version: 4:3.5.7-4 --- Please enter the report below this line. --- Ronny, make sure you have the visor kernel module loaded. I have a Tugesten E. It used to be autodetected, bt since a while a need to load by hand visor module (actually a added it to /etc/modules). Hope to help, Gilmar Santos Jr --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-venus32 Debian Release: lenny/sid 990 testing www.debian-multimedia.org 990 testing security.debian.org 990 testing ftp.br.debian.org 500 unstableftp.br.debian.org 1 experimentalftp.br.debian.org --- Package information. --- Depends (Version) | Installed ===-+- kdelibs4c2a (= 4:3.5.7-1) | 4:3.5.7.dfsg.1-7 libc6(= 2.6-1) | 2.6.1-1+b1 libgcc1 (= 1:4.2-20070516) | 1:4.2.1-4 libkcal2b (= 4:3.5.7) | 4:3.5.7-4 libpisock9 | 0.12.2-10 libqt3-mt (= 3:3.3.7) | 3:3.3.7-8 libstdc++6(= 4.2-20070516) | 4.2.1-4 debconf (= 0.5) | 1.5.14 OR debconf-2.0 | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445530: AbbrowserConduit segfaults on second run
Package: kpilot Version: 4:3.5.7-4 Severity: normal --- Please enter the report below this line. --- If I sync PC and Handheld (Tugsten E) twice, AbbrowserConduit segfaults. First run goes without problems and if AbbrowserConduit is disabled, everything works no matter how many times I sync. Thanks, Gilmar Santos Jr Backtrace: Using host libthread_db library /lib/i686/cmov/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xa65338d0 (LWP 10318)] [New Thread 0xa4746b90 (LWP 10511)] [New Thread 0xa4f46b90 (LWP 10491)] [New Thread 0xa6259b90 (LWP 10482)] 0xa7947f7c in nanosleep () from /usr/lib/debug/libc.so.6 #0 0xa7947f7c in nanosleep () from /usr/lib/debug/libc.so.6 #1 0xa7947d9a in __sleep (seconds=0) at ../sysdeps/unix/sysv/linux/sleep.c:138 #2 0xa74581d7 in KCrash::startDrKonqi (argv=0xaff65810, argc=17) at /build/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kcrash.cpp:312 #3 0xa746db17 in KCrash::defaultCrashHandler (sig=11) at /build/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kcrash.cpp:229 #4 0xe420 in ?? () #5 0x000b in ?? () #6 0xa6a6c67f in KABC::AddressBook::load (this=0x81e7170) at /build/buildd/kdelibs-3.5.7.dfsg.1/./kabc/addressbook.cpp:340 #7 0xa4f82087 in AbbrowserConduit::_loadAddressBook (this=0x8190d20) at /build/buildd/kdepim-3.5.7/./kpilot/conduits/abbrowserconduit/abbrowser-conduit.cc:328 #8 0xa4f828ac in AbbrowserConduit::exec (this=0x8190d20) at /build/buildd/kdepim-3.5.7/./kpilot/conduits/abbrowserconduit/abbrowser-conduit.cc:530 #9 0xa7b31f10 in SyncAction::execConduit (this=0x8190d20) at /build/buildd/kdepim-3.5.7/./kpilot/lib/syncAction.cc:96 #10 0xa7b32068 in SyncAction::qt_invoke (this=0x8190d20, _id=2, _o=0xaff65e88) at ./syncAction.moc:157 #11 0xa7b2bbab in ConduitAction::qt_invoke (this=0x8190d20, _id=2, _o=0xaff65e88) at ./plugin.moc:177 #12 0xa4f8bba3 in AbbrowserConduit::qt_invoke (this=0x8190d20, _id=2, _o=0xaff65e88) at ./abbrowser-conduit.moc:102 #13 0xa6e6bb10 in QObject::activate_signal (this=0x808ec00, clist=0x82307c8, o=0xaff65e88) at kernel/qobject.cpp:2356 #14 0xa71fb32e in QSignal::signal (this=0x808ec00, [EMAIL PROTECTED]) at .moc/debug-shared-mt/moc_qsignal.cpp:100 #15 0xa6e8acc6 in QSignal::activate (this=0x808ec00) at kernel/qsignal.cpp:212 #16 0xa6e92eaa in QSingleShotTimer::event (this=0x808ebd8) at kernel/qtimer.cpp:286 #17 0xa6e0036a in QApplication::internalNotify (this=0xaff66460, receiver=0x808ebd8, e=0xaff661c8) at kernel/qapplication.cpp:2635 #18 0xa6e02193 in QApplication::notify (this=0xaff66460, receiver=0x808ebd8, e=0xaff661c8) at kernel/qapplication.cpp:2358 #19 0xa7541ff2 in KApplication::notify (this=0xaff66460, receiver=0x808ebd8, event=0xaff661c8) at /build/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kapplication.cpp:550 #20 0xa6d916c9 in QApplication::sendEvent (receiver=0x808ebd8, event=0xaff661c8) at ../include/qapplication.h:520 #21 0xa6df31b1 in QEventLoop::activateTimers (this=0x80a5a80) at kernel/qeventloop_unix.cpp:556 #22 0xa6da619a in QEventLoop::processEvents (this=0x80a5a80, flags=4) at kernel/qeventloop_x11.cpp:389 #23 0xa6e1b6e4 in QEventLoop::enterLoop (this=0x80a5a80) at kernel/qeventloop.cpp:198 #24 0xa6e1b3e2 in QEventLoop::exec (this=0x80a5a80) at kernel/qeventloop.cpp:145 #25 0xa6e01f13 in QApplication::exec (this=0xaff66460) at kernel/qapplication.cpp:2758 #26 0x080587b5 in main (argc=0, argv=0x2e0343c5) at /build/buildd/kdepim-3.5.7/./kpilot/kpilot/pilotDaemon.cc:1400 #27 0xa78cb050 in __libc_start_main (main=0x8058590 main, argc=2, ubp_av=0xaff666a4, init=0x8071b30 __libc_csu_init, fini=0x8071b20 __libc_csu_fini, rtld_fini=0xa7efdb70 _dl_fini, stack_end=0xaff6669c) at libc-start.c:224 #28 0x08053ef1 in _start () Current language: auto; currently c --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-venus32 Debian Release: lenny/sid 990 testing www.debian-multimedia.org 990 testing security.debian.org 990 testing ftp.br.debian.org 500 unstableftp.br.debian.org 1 experimentalftp.br.debian.org --- Package information. --- Depends (Version) | Installed ===-+- kdelibs4c2a (= 4:3.5.7-1) | 4:3.5.7.dfsg.1-7 libc6(= 2.6-1) | 2.6.1-1+b1 libgcc1 (= 1:4.2-20070516) | 1:4.2.1-4 libkcal2b (= 4:3.5.7) | 4:3.5.7-4 libpisock9 | 0.12.2-10 libqt3-mt (= 3:3.3.7) | 3:3.3.7-8 libstdc++6(= 4.2-20070516) | 4.2.1-4 debconf (= 0.5) | 1.5.14 OR debconf-2.0 | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441294: Are you on unstable now?
Hello: I see that this bug is reported for stable but you are talking about unstable upgrade. Could you specify if this is happening on both stable and unstable, unstable only or stable only? Also please make sure you have the debug packages: kdelibs-dbg, kdepim-dbg and post a whole backtrace with them. Another thing I could blame is the Russian i18n, but this is only an unbased supposition right now. Thanks. -- Raúl Sánchez Siles -Proud Debian user- Linux registered user #416098 signature.asc Description: This is a digitally signed message part.
Bug#443600: konqueror-nsplugins: I think this was marked done prematurely
Hi Sune, Thanks for your clarification about the reason for the 100% CPU. For the rest, however, On Saturday 06 October 2007, Sune Vuorela wrote: nspluginviewer can't initialize any kind of environment that a plugin might or might not use. remember that this is plugins. If a plugin needs something special, then that something needs to do it. Well, ns in nspluginviewer stands for NetScape, as far as I'm aware, so I doubt that GTK can be regarded as something special. My understanding is that it should strive to make the plugin feel as if it is being run by netscape (or at least Gecko), and if that includes having an initialized GTK, then it is nspluginviewer's job to do so. either the bug could be fixud at it roots (=in adobe) or worked around where special things are needed (=gtk). I beg to differ twice. Adobe wrote a library to work in GTK applications, so not initializing GTK in the library cannot be called a bug. From their point of view, the plugin works perfectly in all environments where it was designed to work. GTK is also perfectly within their turf when they decide the meaning of their own API. The only problem is when a non-gtk application insists it can call gtk libraries without initialization. Essentially, nspluginviewer has broken the API's contract, and is now paying the consequences (or rather, the users are). (And firefox and other gtk browsers works because they *tada* are gtk browsers - making konqueror a gtk browser isn't a choice we want to take) While I understand and praise this desire for purity, I think it makes little sense when loading plugins designed for a GTK browser -- which is, after all, the whole point of nspluginviewer's existence, and more so, its existence as a separate entity. In essence, by choosing to use the plugin, the user has already told you they aren't interested in such purity. I also understand the reluctance to include a dependency on GTK at the heart of KDE -- perhaps this means nspluginviewer should be taken out of kdebase. However, what you're doing now is try to tell the writers of plugins for Gecko-based browsers that there's a special, added requirement for their plug-in to work in konqueror. I think this won't fly. And finally, you've ignored my point about konqueror hanging when this bug is triggered. Hope this helps, Shai. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443600: konqueror-nsplugins: I think this was marked done prematurely
On Saturday 06 October 2007, Shai Berger wrote: Hi Sune, Thanks for your clarification about the reason for the 100% CPU. For the rest, however, On Saturday 06 October 2007, Sune Vuorela wrote: nspluginviewer can't initialize any kind of environment that a plugin might or might not use. remember that this is plugins. If a plugin needs something special, then that something needs to do it. Well, ns in nspluginviewer stands for NetScape, as far as I'm aware Correct. doubt that GTK can be regarded as something special. My understanding is that it should strive to make the plugin feel as if it is being run by netscape (or at least Gecko), Actually no, the plugin API does not specify any particual rendering engine or browser technology. either the bug could be fixud at it roots (=in adobe) or worked around where special things are needed (=gtk). I beg to differ twice. Adobe wrote a library to work in GTK applications, so not initializing GTK in the library cannot be called a bug. From their point of view, the plugin works perfectly in all environments where it was designed to work. Adobe wrote a plugin for an application supporting the Netscape Plugin API. Since this API does not in any way specify that GTK is used for the APIs implementation, they can not assume this. Based on the API they can assume that the host application is having a Motif compatible event loop. Any plugin implementor therefore has to make sure other internal requirements are setup correctly in their code. GTK is also perfectly within their turf when they decide the meaning of their own API. No argument about that. Especially since gtk_init() is specified to be allowed to be called multiple times, where the first call will perform the initialization and every other call will basically be a no-op. There is no reason for the Adobe plugin not to call it. The only problem is when a non-gtk application insists it can call gtk libraries without initialization. Essentially, nspluginviewer has broken the API's contract, and is now paying the consequences (or rather, the users are). nspluginviewer doesn't use GTK, therefore can hardly have broken that API's contract. It fully implements the requirements of the NS Plugin API, thus not breaking this contract either. Adobe's QA has probably failed to detect the missing initialization, thus making the plugin break the GTK API contract (And firefox and other gtk browsers works because they *tada* are gtk browsers - making konqueror a gtk browser isn't a choice we want to take) While I understand and praise this desire for purity, I think it makes little sense when loading plugins designed for a GTK browser -- which is, after all, the whole point of nspluginviewer's existence, and more so, its existence as a separate entity. In essence, by choosing to use the plugin, the user has already told you they aren't interested in such purity. Well, as I wrote above, the plugin is not designed for a GTK browser. Even if it were designed for Firefox, which it isn', it wouldn't be designed for one. Firefox, including Gecko, does not depend on GTK but rather uses a kind of abstraction toolkit made by Mozilla so they can implement it differently depending on platform. I also understand the reluctance to include a dependency on GTK at the heart of KDE -- perhaps this means nspluginviewer should be taken out of kdebase. However, what you're doing now is try to tell the writers of plugins for Gecko-based browsers that there's a special, added requirement for their plug-in to work in konqueror. I think this won't fly. While it would be nice to have different plugin runners for plugins with different toolkit requirements, there is currently no way a browser can ask a plugin which toolkit it requires. This might be changed in a newer version of the plugin API, e.g. like it can decide which MIME type a plugin is capable of handling. Until then a plugin's toolkit requirements is an implementation detail the plugin itself has to take care of, since neither the browser nor its plugin runner can. It's not a good idea for plugin hosts to work around bugs in plugins, because it will likely end up in a situation where a workaround for one plugin breaks another. Especially in cases where the bug is trivial to fix for the plugin creator. Cheers, Kevin signature.asc Description: This is a digitally signed message part.
Bug#445571: kcontrol asks to add universe repository for windows apps setup
Package: kcontrol Version: 4:3.5.7.dfsg.1-1 Under the Windows Applications section, if wine is not installed, it asks if you want to go into Administrator Mode, add the Universe repository to sources.list, and install wine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
