Bug#540226: plasma-scriptengine-javascript: scripted-image plasmoid fails to display image
Package: plasma-scriptengine-javascript
Version: 4:4.2.4-1+b1
Severity: normal
I recently installed the scripted image plugin to display
a weather forecast as described in:
http://hanswchen.wordpress.com/2009/07/30/plasma-a-nice-weather-plasmoid-in-4-easy-steps/
I used
http://www.yr.no/place/Austria/Upper_Austria/Linz/meteogram.png
as Image Url, Scale applet to content, and an update time of 30 minutes.
When I do a killall plasma plasma I see the following error:
JS CONSOLE MESSAGE: line 1 : ReferenceError: Can't find variable: init
When I click configure and apply I get a similar error:
JS CONSOLE MESSAGE: line 1 : ReferenceError: Can't find variable:
configChanged
Excerpt from script.js (part of the code of scripted image):
function init()
{
//alert(init)
g_img = new Image();
g_img.onload = widhtHeightReady;
constraintsEvent(FormFactorConstraint);
configChanged();
}
configChanged is defined in this script too.
As others commented on the Blog post, that it works for them, I guess
it is not a bug of the scripted image plasmoid.
regards,
Martin Maurer
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.30.1 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_AT (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages plasma-scriptengine-javascript depends on:
ii kdebase-runtime 4:4.2.4-2 runtime components from the offici
ii kdelibs5 4:4.2.4-1 core libraries for all KDE 4 appli
ii libc6 2.9-12 GNU C Library: Shared libraries
ii libgcc1 1:4.4.0-5 GCC support library
ii libplasma34:4.2.4-1 library for the KDE 4 Plasma deskt
ii libqt4-script 4:4.5.2-1 Qt 4 script module
ii libqtcore44:4.5.2-1 Qt 4 core module
ii libqtgui4 4:4.5.2-1 Qt 4 GUI module
ii libstdc++64.4.0-5The GNU Standard C++ Library v3
plasma-scriptengine-javascript recommends no packages.
plasma-scriptengine-javascript suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#441298: Still reproducible?
Hi, I still get a crash when closing tabs by middle click. This only happens sporadically, when I have a lot of tabs open and start closing them. I meanwhile use HoverCloseButton (X button when moving the mouse over a tab) to close the tabs. I can't recall crashing kde when using this or Ctrl-W, but I can't tell for sure neither. I have konqueror 3.5.10.dfsg.1-2 now and the backtrace has changed a little bit: [Thread debugging using libthread_db enabled] [New Thread 0xb7e2c700 (LWP 10555)] [KCrash handler] #6 0xb7f7a424 in __kernel_vsyscall () #7 0x42450640 in *__GI_raise (sig=value optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0x42452008 in *__GI_abort () at abort.c:88 #9 0x427e00a8 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6 #10 0x427ddf85 in ?? () from /usr/lib/libstdc++.so.6 #11 0x427ddfc2 in std::terminate () from /usr/lib/libstdc++.so.6 #12 0x427dec65 in __cxa_pure_virtual () from /usr/lib/libstdc++.so.6 #13 0x412b82f1 in KonqViewManager::removeTab (this=value optimized out, tab=value optimized out) at /tmp/buildd/kdebase-3.5.10.dfsg.1/./konqueror/konq_viewmgr.cc:565 #14 0x412b850d in KonqMainWindow::slotRemoveTabPopupDelayed (this=) at /tmp/buildd/kdebase-3.5.10.dfsg.1/./konqueror/konq_mainwindow.cc:2752 #15 0x412db4c6 in KonqMainWindow::qt_invoke (this=value optimized out, _id=value optimized out, _o=) at ./konq_mainwindow.moc:694 #16 0x44e677aa in QObject::activate_signal (this=value optimized out, clist=value optimized out, o=value optimized out) at kernel/qobject.cpp:2359 #17 0x451c4f8e in QSignal::signal (this=value optimized out, t0=) at .moc/release-shared-mt/moc_qsignal.cpp:100 #18 0x44e8470d in QSignal::activate (this=value optimized out) at kernel/qsignal.cpp:215 #19 0x44e8bac3 in QSingleShotTimer::event (this=) at kernel/qtimer.cpp:289 #20 0x44e02dc5 in QApplication::internalNotify (this=value optimized out, receiver=value optimized out, e=value optimized out) at kernel/qapplication.cpp:2638 #21 0x44e03e06 in QApplication::notify (this=value optimized out, receiver=value optimized out, e=value optimized out) at kernel/qapplication.cpp:2375 #22 0x416bbde2 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 #23 0x44df8603 in QEventLoop::activateTimers (this=) at kernel/qapplication.h:523 #24 0x44dadcbe in QEventLoop::processEvents (this=value optimized out, flags=value optimized out) at kernel/qeventloop_x11.cpp:392 #25 0x44e1b7a0 in QEventLoop::enterLoop (this=value optimized out) at kernel/qeventloop.cpp:201 #26 0x44e1b666 in QEventLoop::exec (this=) at kernel/qeventloop.cpp:148 #27 0x44e0345f in QApplication::exec (this=) at kernel/qapplication.cpp:2761 #28 0x412d7a2c in kdemain (argc=value optimized out, argv=value optimized out) at /tmp/buildd/kdebase-3.5.10.dfsg.1/./konqueror/konq_main.cc:206 #29 0xb7f6f464 in kdeinitmain (argc=1, argv=0x959f388) at konqueror_dummy.cc:3 #30 0x0804f2f1 in launch (argc=1, _name=0x959eac4 konqueror, args=0x959eace \001, cwd=0x0, envc=1, envs=0x959eade , reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x959eae3 nicisha;1240214933;43349;3969_TIME1110535) at /tmp/buildd/kdelibs-3.5.10.dfsg.1/./kinit/kinit.cpp:673 #31 0x0804fa7d in handle_launcher_request (sock=9) at /tmp/buildd/kdelibs-3.5.10.dfsg.1/./kinit/kinit.cpp:1240 #32 0x080500ca in handle_requests (waitForPid=0) at /tmp/buildd/kdelibs-3.5.10.dfsg.1/./kinit/kinit.cpp:1443 #33 0x08050b6a in main (argc=5, argv=0xbfb77f84, envp=0xbfb77f9c) at /tmp/buildd/kdelibs-3.5.10.dfsg.1/./kinit/kinit.cpp:1908 signature.asc Description: This is a digitally signed message part
Bug#496297: ROM: RM: fireflier -- no longer developped upstream, very few users
package: ftp.debian.org Severity: normal I am upstream and debian maintainer for the package fireflier. Development of this software ended in November 2005, and I discontinued it officially on Feb, 2007. The popcon statistics (only listing server as client without server is useless): fireflier-server: Inst: 36 Vote: 6 Old: 28 Recent: 2 Apart from debian qa messages (FTBFS, 1 security issue, ...) I don't get any more mails regarding fireflier, so I can safely assume, that is used by _very few_ people. There are two FTBFS issues in fireflier currently, where the second can't be solved easily, as iptables-dev no longer includes libipq and I would have to use libnetfilter-queue-dev which uses different library names. Open Bugs (ignoring wishlist): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486981 As there are quite a few firewall tools in debian, and the impact will be low, it is the best solution to remove fireflier. Please remove the versions in: unstable experimental fireflier shall not be part of the upcoming debian release (lenny) This package has always been uploaded by my sponsor Rene Mayrhofer, who agrees to the removal. greetings Martin Maurer signature.asc Description: This is a digitally signed message part
Bug#486981: fireflier: FTBFS: netfilter.h:44: error: field 'in' has incomplete type
On Sat, 2008-08-23 at 22:46 -0700, Steve Langasek wrote: I was going to try to rebuild fireflier, to see whether the bug in linux-libc-dev happened to be fixed. But now fireflier FTBFS because iptables-dev no longer provides libipq.a, in testing or unstable... And the linux-libc-dev bug isn't fixed, either. Hi, thanks for the additional information. I have just issued a request for removal, as I no longer develop fireflier and it has quite a low user base. see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496297 as soon as this removal is done I will close this bug. regards, Martin signature.asc Description: This is a digitally signed message part
Bug#486981: fireflier: FTBFS: netfilter.h:44: error: field 'in' has incomplete type
On Sun, 2008-08-24 at 10:20 -0700, Steve Langasek wrote: On Sun, Aug 24, 2008 at 12:31:20PM +0200, Martin MAURER wrote: On Sat, 2008-08-23 at 22:46 -0700, Steve Langasek wrote: I was going to try to rebuild fireflier, to see whether the bug in linux-libc-dev happened to be fixed. But now fireflier FTBFS because iptables-dev no longer provides libipq.a, in testing or unstable... And the linux-libc-dev bug isn't fixed, either. thanks for the additional information. I have just issued a request for removal, as I no longer develop fireflier and it has quite a low user base. see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496297 as soon as this removal is done I will close this bug. I spoke with the iptables maintainer on IRC now, and apparently the dropping of libipq.a was an oversight; it will be re-added soon. thanks for this additional info. Anyways, it doesn't change the request for removal for me, as I have already thought about this before this bug was opened. I don't develop fireflier any more and nobody has showed any interest in taking up its development for a long time now. very few users and no time to work on it led me to the conclusion, that it will be better to have this package removed. Outdated unmaintained packages won't help debian. regards, Martin signature.asc Description: This is a digitally signed message part
Bug#487103: linux-libc-dev: netfilter.h needs in.h include
Package: linux-libc-dev
Version: 2.6.25-5
Severity: normal
The file /usr/include/linux/netfilter.h leads to compile problems
in one of my packages. This worked with the version in debian testing:
Error message:
/usr/include/linux/netfilter.h:44: error: field 'in' has incomplete type
/usr/include/linux/netfilter.h:45: error: field 'in6' has incomplete type
the struct
union nf_inet_addr {
__u32 all[4];
__be32 ip;
__be32 ip6[4];
struct in_addr in;
struct in6_addr in6;
};
needs in_addr and in6_addr to be defined.
this seems to be a similar problem as in:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482331
I can certainly solve this problem in my package, as I do include in.h
a few lines later. Nevertheless I think there should be no dependance on the
order of the includes.
regards,
Martin
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22.1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=de_AT (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441298: konqueror: crash on tab close
Package: konqueror Version: 4:3.5.7-2+b1 Severity: normal konqueror sometimes crashes when I have a few tabs open and close one of them by clicking the middle mouse button. This doesn't always happen on the same web page and isn't easily reproducible (happens every now and then). Dist: Debian Testing (updated recently) Backtrace: Using host libthread_db library /lib/i686/cmov/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread -1208523072 (LWP 5008)] [KCrash handler] #6 0x4da39567 in KonqViewManager::showTab (this=0x8105810, view=0x0) at /build/buildd/kdebase-3.5.7/./konqueror/konq_viewmgr.cc:717 #7 0x4da39e39 in KonqMainWindow::slotRemoveTabPopup (this=0x80cfaa0) at /build/buildd/kdebase-3.5.7/./konqueror/konq_mainwindow.cc:2746 #8 0x4da5b991 in KonqMainWindow::qt_invoke (this=0x80cfaa0, _id=162, _o=0xbfbc3fdc) at ./konq_mainwindow.moc:693 #9 0x4c3e3d23 in QObject::activate_signal (this=0x82be9d0, clist=0x82c3420, o=0xbfbc3fdc) at kernel/qobject.cpp:2356 #10 0x4c3e47c8 in QObject::activate_signal (this=0x82be9d0, signal=17) at kernel/qobject.cpp:2325 #11 0x4d9fd47c in KonqFrameTabs::removeTabPopup (this=0x82be9d0) at ./konq_tabs.moc:160 #12 0x4da492be in KonqFrameTabs::slotMouseMiddleClick (this=0x82be9d0, w=0x8a9a5d0) at /build/buildd/kdebase-3.5.7/./konqueror/konq_tabs.cc:460 #13 0x4da49705 in KonqFrameTabs::qt_invoke (this=0x82be9d0, _id=71, _o=0xbfbc4104) at ./konq_tabs.moc:173 #14 0x4c3e3d23 in QObject::activate_signal (this=0x82be9d0, clist=0x8292758, o=0xbfbc4104) at kernel/qobject.cpp:2356 #15 0x4d468591 in KTabWidget::mouseMiddleClick (this=0x82be9d0, t0=0x8a9a5d0) at ./ktabwidget.moc:354 #16 0x4d4685f5 in KTabWidget::mouseMiddleClick (this=0x82be9d0, index=1) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kdeui/ktabwidget.cpp:400 #17 0x4d4b1014 in KTabWidget::qt_invoke (this=0x82be9d0, _id=61, _o=0xbfbc4248) at ./ktabwidget.moc:384 #18 0x4da49623 in KonqFrameTabs::qt_invoke (this=0x82be9d0, _id=61, _o=0xbfbc4248) at ./konq_tabs.moc:180 #19 0x4c3e3d23 in QObject::activate_signal (this=0x82c0498, clist=0x82bf868, o=0xbfbc4248) at kernel/qobject.cpp:2356 #20 0x4c3e463a in QObject::activate_signal (this=0x82c0498, signal=6, param=1) at kernel/qobject.cpp:2449 #21 0x4d427033 in KTabBar::mouseMiddleClick (this=0x82c0498, t0=1) at ./ktabbar.moc:162 #22 0x4d4332c1 in KTabBar::mouseReleaseEvent (this=0x82c0498, e=0xbfbc46d4) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kdeui/ktabbar.cpp:237 #23 0x4c41acb2 in QWidget::event (this=0x82c0498, e=0xbfbc46d4) at kernel/qwidget.cpp:4702 #24 0x4c52e7d9 in QTabBar::event (this=0x82c0498, e=0xbfbc46d4) at widgets/qtabbar.cpp:1147 #25 0x4c37b4e0 in QApplication::internalNotify (this=0xbfbc4d5c, receiver=0x82c0498, e=0xbfbc46d4) at kernel/qapplication.cpp:2635 #26 0x4c37d6a1 in QApplication::notify (this=0xbfbc4d5c, receiver=0x82c0498, e=0xbfbc46d4) at kernel/qapplication.cpp:2421 #27 0x4cad32c2 in KApplication::notify (this=0xbfbc4d5c, receiver=0x82c0498, event=0xbfbc46d4) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kapplication.cpp:550 #28 0x4c30e609 in QApplication::sendSpontaneousEvent (receiver=0x82c0498, event=0xbfbc46d4) at kernel/qapplication.h:523 #29 0x4c30d292 in QETWidget::translateMouseEvent (this=0x82c0498, event=0xbfbc4b08) at kernel/qapplication_x11.cpp:4301 #30 0x4c30b6da in QApplication::x11ProcessEvent (this=0xbfbc4d5c, event=0xbfbc4b08) at kernel/qapplication_x11.cpp:3478 #31 0x4c321fb8 in QEventLoop::processEvents (this=0x80ab958, flags=4) at kernel/qeventloop_x11.cpp:192 #32 0x4c395be6 in QEventLoop::enterLoop (this=0x80ab958) at kernel/qeventloop.cpp:198 #33 0x4c3959f6 in QEventLoop::exec (this=0x80ab958) at kernel/qeventloop.cpp:145 #34 0x4c37d089 in QApplication::exec (this=0xbfbc4d5c) at kernel/qapplication.cpp:2758 #35 0x4da56495 in kdemain (argc=3, argv=0x80894a8) at /build/buildd/kdebase-3.5.7/./konqueror/konq_main.cc:206 #36 0xb7f90454 in kdeinitmain (argc=3, argv=0x80894a8) at konqueror_dummy.cc:3 #37 0x0804e66f in launch (argc=3, _name=0x80894c4 konqueror, args=0x808950d , cwd=0x0, envc=0, envs=0x8089512 , reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050f54 0) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kinit/kinit.cpp:673 #38 0x0804eeff in handle_launcher_request (sock=9) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kinit/kinit.cpp:1240 #39 0x0804f2af in handle_requests (waitForPid=0) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kinit/kinit.cpp:1443 #40 0x0805051c in main (argc=5, argv=0xbfbc57f4, envp=0xbfbc580c) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kinit/kinit.cpp:1909 #41 0x4cc05050 in __libc_start_main () from /lib/i686/cmov/libc.so.6 #42 0x0804bb51 in _start () -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22.1 (SMP w/2 CPU cores; PREEMPT) Locale:
Bug#434308: any problems
Hi Steffen, looks like my sponsor is quite busy these days - I already reminded him of the upload some time ago, but he apparently didn't upload so far. Will try to contact him again in the evening. greetings Martin -Ursprüngliche Nachricht- Von: Steffen Joeris [EMAIL PROTECTED], [EMAIL PROTECTED] Gesendet: 07.08.07 12:14:11 An: [EMAIL PROTECTED] Betreff: Bug#434308: any problems Hi Are there any problems with the upload? Is there anything blocking you? The security fix is still blocked for testing this way :/ Cheers Steffen
Bug#434308: Fix
The fix for this is already at my sponsor awaiting upload. It will soon be uploaded. greetings, Martin On Sat, 2007-07-28 at 18:48 +0100, Neil McGovern wrote: This seems to be due to a missing debian/compat. As this is keeping a security hole in testing, I intend to NMU this on Monday unless the maintainer speaks up :) Cheers, Neil signature.asc Description: This is a digitally signed message part
Bug#433817: please migrate fireflier to gtkmm2.4
Fireflier is currently not developped any more. Actually we are considering to request a removal too here. Nevertheless, as there was a DSA fixed recently, and there are minor problems left, I will upload a new version on fireflier-1.1.7 soon. (I don't want those people who have it installed on their machine to remain on the security flawed version). The author of the fireflier gnomeclient is no longer active, and therefore a migration won't happen. So I think the best way will be to: 1.) upload a new fixed version, that still uses gtkmm-2.0 2.) a few weeks later remove fireflier altogether. I might discuss this step on debian-devel before. BTW, an information earlier would have helped a lot. greetings, Martin On Thu, 2007-07-19 at 18:41 +0200, Pierre Habouzit wrote: Package: fireflier Severity: grave gtkmm2.0 is scheduled for removal, you're the last package needing it in the archive, so it's either you migrate, or fireflier will be removed as well. :) signature.asc Description: This is a digitally signed message part
Bug#432408:
Hi all, thanks a lot for reporting the bug and fixing all those issues. I took some time to take a look at them and added most of them to my package. I did not add the automake dependency, but instead copied the files to the directory. I additionally added some dummy text to gnomeclient/NEWS. I know the author, and he won't object. there are some lintian messages left for the source package and the lsb message for the fireflier-server.deb Anyways I won't fix those for now, as fireflier is discontinued and will maybe be removed from the archive some time. The updated packages are on the way to my sponsor for uploading. greetings and thanks again, Martin On Tue, 2007-07-17 at 19:48 +0200, Cyril Brulebois wrote: tag 432408 patch thanks Jason Harrison [EMAIL PROTECTED] (17/07/2007): I have attached a patch that I believe fixes the build problem. Please let me know if it is acceptable. Hi, this patch is not sufficient, though, because gnomeclient/configure needs install-sh, which in this directory is symlinked to automake1.8's, broken symlink since automake1.8 is not Build-Depend'd upon. Since applying the patch, and adding the missing B-D (or copying this file once in the source) fixes the FTBFS, tagging accordingly. It would be nice to sort out the warnings and the error that lintian emits when run on the source package (e.g. the B-D on g++). Cheers, signature.asc Description: This is a digitally signed message part
Bug#432408: fireflier - FTBFS: ./configure: line 2018: [test: command not found
Fireflier has always been a native debian package, as I directly develop using debian (though there might be some reasons not do it that way anyways). This is only a small bugfix release, and I will have to check this compile problem. greetings Martin On Tue, 2007-07-10 at 18:40 +0200, Kurt Roeckx wrote: On Mon, Jul 09, 2007 at 09:37:57PM +0200, Bastian Blank wrote: Package: fireflier Version: 1.1.7 Severity: serious Is there a reason why this package suddenly has become a native package? Kurt signature.asc Description: This is a digitally signed message part
Bug#431332: CVE-2007-2837: Arbitary file removal
Hi, I agree that this code could become a problem, although I wasn't able to reproduce using screen and the command written in your mail. Anyways - what really might happen is that the file is overwritten, not deleted, as rm should delete the link not the file the link points to. Nevertheless, this doesnt make a big difference, so I will add your fix to the official version of fireflier. thanks, Martin Maurer (main developer, and original author of that code) signature.asc Description: This is a digitally signed message part
Bug#393031: New packages follwing soon
Hi all, I have currently prepared fireflier_1.1.6-3, which will fix those problems. I modified the build process, so that it no longer needs automake (but instead distributes the configure script). I will contact my sponsor, so this can be uploaded. greetings Martin pgpeixIWyPYaW.pgp Description: PGP signature
Bug#394402: new packages incoming soon
Hi all, new packages, which should fix this bug have been uploaded by my sponsor. I removed the automake dependency altogether, now distributing the configure script directly. greetings Martin pgpXGoTujBplA.pgp Description: PGP signature
Bug#393031: FTBFS: ./configure: line 1752: [test: command not found
On Sunday, 15. October 2006 18:47, James Westby wrote: Hi, I can reproduce this in an i386 pbuilder, but I cannot see the problem quite yet. the line stating [test command not found is quie old, yet I have never had any problems resulting of that, and therefore I did never investigate where it comes from. Looking at the first post regarding this bug, I see a line autoheader: error: AC_CONFIG_HEADERS not found in configure.in and others errors following that one. I think the best way to solve all those automake problems will be to include the configure script to the debian package and no longer depend on automake stuff for building the package. I will do so as soon as I get time. greetings Martin (maintainer/upstream of fireflier) pgpbIaG96aFPa.pgp Description: PGP signature
Bug#389233: fireflier: patch for 1.99.beta2.1 NMU
Hi, On Sunday, 8. October 2006 14:53, Sam Hocevar (Debian packages) wrote: Package: fireflier Followup-For: Bug #389233 Attached is the patch for my 1.99.beta2.1 NMU. thanks for fixing this bug. You should probably repackage fireflier as a non-native package and only apply the relevant parts of the patch. Currently it is not clear wheter I will continue fireflier development (i am upstream too), as i have got quite limited time at the moment. If I decide to do so, I will consider repackaging as non-native. greetings Martin pgpLQLmPPhDnT.pgp Description: PGP signature
Bug#295150: fireflier-client-kde: Nice to have connection tracking on by default (ACCEPT in iptables)
On Mon, 2005-02-21 at 20:05 +0100, Michal J. Gajda wrote: Martin MAURER napisa(a): On Mon, 2005-02-14 at 00:33 +0100, Michal J. Gajda wrote: Package: fireflier-client-kde Version: 1.1.5-1 Severity: minor It is pretty irritating to must have every connection to be accepted both from initiator and accepting side. It is also a bit of GUI haggle, as it is hard to notice what the option about connection tracking concerns. (I've been trying to switch it on for all packets, but without success.) the behaviour of fireflier regarding connection tracking should be correct as far as i know up to now. You can verify this by checking the rules which are inserted. there should be a matching rule for the opposite direction which includes --state RELATED,ESTABLISHED. This accepts all packets belonging to an active connection. The problem is that it works just for ESTABLISHED. RELATED connections usually concern different ports, so it is not enough to just accept the same connections. (Maybe just have an option to ACCEPT all RELATED?) oops... you are right, there is a problem in this case. i will have to fix this one :) thanks for bringing this to my attention... greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295150: fireflier-client-kde: Nice to have connection tracking on by default (ACCEPT in iptables)
On Mon, 2005-02-14 at 00:33 +0100, Michal J. Gajda wrote: Package: fireflier-client-kde Version: 1.1.5-1 Severity: minor It is pretty irritating to must have every connection to be accepted both from initiator and accepting side. It is also a bit of GUI haggle, as it is hard to notice what the option about connection tracking concerns. (I've been trying to switch it on for all packets, but without success.) the behaviour of fireflier regarding connection tracking should be correct as far as i know up to now. You can verify this by checking the rules which are inserted. there should be a matching rule for the opposite direction which includes --state RELATED,ESTABLISHED. This accepts all packets belonging to an active connection. Whenever you have a packet in the OUTPUT chain, which is of the protocol UDP or TCP you should be able to add a connection tracking rule. I will try to make this thing a little more clear with the next version of fireflier. Anyways this next version might take some time, as development is not very active at the moment. (limited time) thanks for reporting this issues. if you have further questions feel free to ask. greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#281871: licq-plugin-osd does not respect the configuration settings for timeout and delaypercharacter
Hi, the problem this bug report refers to was a problem of libxosd which is used by licq-osd. With recent (debian unstable) versions of libxosd2 this problem should no longer persist. Please tell me if this still happens. greetings Martin (licq-osd upstream author) Package: licq-plugin-osd Version: 1.3.0-2 Severity: important it is often the case that the OSD text is stuck on the screen and is not removed until the next event appears. Sometimes the same message is stuck forever (until licq restart) rendering that part of the screen hardly usable, this makes the plugin anoying and useless. signature.asc Description: This is a digitally signed message part
