Bug#976530: dolphin-emu: FTBFS: tests failed
Hi, The reason why one of the unit tests failed is because this unit test was triggering undefined behavior when generating its test values. In other words, there was no bug in the actual program, just in the unit test. This bug was fixed upstream in https://github.com/dolphin-emu/dolphin/commit/8d21fa56a1133529273d57df06888e42bb63fde7 (though do note that this commit depends on an earlier commit from the same pull request). For what it's worth, in upstream we've only encountered this issue on arm64, not amd64. But since it is undefined behavior, I'm not too surprised that this issue doesn't act the same way in your build environment as in ours. I'm not sure how you want to proceed, but I hope this information was useful. JosJuice, dolphin-emu upstream maintainer
Bug#958419: swi-prolog 8.1.29 in Debian
Hi Lev, Yes indeed, eye is using a saved state to have it started 10 times faster than normal: $ time swipl -x /opt/eye/lib/eye.pvm -- --version eye --version EYE v20.0423.1748 josd SWI-Prolog version 8.1.29 starting 31 [msec cputime] 37 [msec walltime] real 0m0.041s user 0m0.037s sys 0m0.004s $ time swipl -f /opt/eye/src/eye.pl -g main -- --version eye --version EYE v20.0423.1748 josd SWI-Prolog version 8.1.29 starting 344 [msec cputime] 393 [msec walltime] real 0m0.401s user 0m0.343s sys 0m0.015s and this is quite crucial as eye is typically used as a short running process which is getting data/rules/query from the web, returning answers/proofs for the query and then closing the process as the internal state (e.g. the deductive closure of the forward reasoning run) is of no use to the next run. Kind regards, Jos -- https://josd.github.io/ <http://josd.github.io/> On Tue, Apr 28, 2020 at 1:30 PM Lev Lamberov wrote: > Вт 28 апр 2020 @ 13:11 Jan Wielemaker : > > > Hi Lev, > > > > I most wanted to get Jos in the loop as the developer of eye. Packagers > > working together with developers/maintainers saves a lot of work :) > > Awww... so, CCing Jos De Roo. > > Jos, could you be so kind to take a look at the #958561 Debian bug > report concerning swi-prolog and eye. You can find it there: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958561 > > > On 4/28/20 12:49 PM, Lev Lamberov wrote: > >> Hi Jan, > >> > >> Вт 28 апр 2020 @ 11:22 Jan Wielemaker : > >> > >>> Hi Lev, Jos, > >>> > >>> For Jos, the problem is that eye installs as a SWI-Prolog saved state, > >>> which is highly version dependent and this is difficult to deal with > >>> given the Debian dependency and upgrade policy (Lev, hope this is the > >>> right summary, please correct if not). > >>> > >>> I has a little look at eye and I wonder why we need the state. eye.pl > >>> isn't that big and loads in about 0.12 sec on my machine. Without a > >>> state, eye seems to run easily using the simple script > >>> > >>> swipl -g main /path/to/eye.pl "$@" > >>> > >>> Or by installing eye.pl as the actual executable and start is using > >>> > >>> #!/bin/env swipl > >>> > >>> and use somewhere in the file > >>> > >>> :- initialization(main,main). > >>> > >>> Would it make sense to go this route? If not, why not? Is the > >>> somewhat longer startup time an issue? > >>> > >>> Thanks --- Jan > >> > >> I'm sending your message to the bug report and to Jonas Smedegaard. > >> Please, send your further replies to 958...@bugs.debian.org > >> > >> Cheers! > >> Lev >
Bug#882247:
Package: firefox Version: 58.0~b4-1 Severity: grave After upgrading firefox to version 58.0~b4-1 I get the same issue.
Bug#829557: lightdm 1.18.2-1 breaks D-BUS
I am using Debian/Sid and encountered the same issue. upgrading to lightdm_1.19.2-0ubuntu1_amd64.deb fixed all issues.
Bug#816376: [Pkg-owncloud-maintainers] Bug#816376: Bug#816376: Unfit upstream
On dinsdag 8 maart 2016 08:37:35 CET David Prévot wrote: > Hi, > > Le 08/03/2016 03:03, Jos Poortvliet a écrit : > > The situation is rather sad and frustrating > > OK. > > > as users who decided to trust the Debian developers and took their > > packages over ownCloud's provided packages are now stuck on a version > > which can't trivially be upgraded to either our upstream version or > > anything else. > The thing is, we were working on a proper upgrade path, but upstream > decided without even looking at it that it was “bad” (to put it mildly). > Because of upstream reaction, we have removed our work in progress, and > > now the PR crap (as in words not backed by anything) follows: > > We would love to find a solution for them I know that that is how you choose to look at it - and I feel there is no value to discuss that. > Regards > > David -- Disclaimer: Everything I do and say is based on my view of the world today. I am not responsible for changes in the world, nor my view on it. Everything I say is meant in a positive and friendly way, unless explicitly stated otherwise. find me on blog.jospoortvliet.com
Bug#816376: [Pkg-owncloud-maintainers] Bug#816376: Unfit upstream
On Monday, March 7, 2016 5:43:20 PM AMT Sébastien Villemot wrote: > Dear David, > > First, let me thank you for the work that you put into packaging > owncloud for Debian, it is really appreciated. > > On Tue, 1 Mar 2016 07:07:10 -0400 David =?iso-8859-1?Q?Pr=E9vot?= > wrote: > > > Upstream doesn’t wish to see their software in Debian anymore. Unless > > the situation changes in the next few months, owncloud will not be part > > of Stretch. > > Given that owncloud is such a useful and important package, and that > there is currently no credible alternative, this is really sad news, and > I am wondering whether this outcome could be avoided. > > If I understand correctly, your decision is essentially based on social > issues (upstream hostile to Debian packaging), coupled to some technical > aspects (complex upgrade paths). See my last email here - we'd love to have ownCloud included in Debian but obviously only if it provides a good experience to users. Right now, it seems that that is hard to do within the framework Debian provides. http://lists.alioth.debian.org/pipermail/pkg-owncloud-maintainers/2016-March/002899.html The situation is rather sad and frustrating as users who decided to trust the Debian developers and took their packages over ownCloud's provided packages are now stuck on a version which can't trivially be upgraded to either our upstream version or anything else. We would love to find a solution for them - as I've said many times, our main concern is the end users, rather than politics, rules or anything else. Thanks for caring about this, Jos > At first glance, this does not seem to prevent the package from staying > in Debian. Maybe this just means that the package needs a new > maintainer, who is willing to handle the tough interaction with upstream > and dealing with the technical issues (note that I am not applying for > the job). > > You are certainly in a better position than me to ascertain whether the > package can stay in Debian or not, but I think that it would be useful > if you could give a little more background on the issues that you > encountered. And, if you think it makes sense to orphan the package, > that would help prospective new maintainers in making the decision to > adopt the package or not. > > Cheers, > > signature.asc Description: This is a digitally signed message part.
Bug#802866: fcitx-frontend-qt5
Package: fcitx-frontend-qt5 Version: 1.0.4-1 Bug #802866 can be closed, the issue has been fixed by the release of version 1.0.4-1 in Sid. Thanks! Jos van Wolput
Bug#768522: libcurl3 (version 7.38.0-3) relocation error
On 11/08/2014 06:24 PM, Adam D. Barratt wrote: Given: -- System Information: Debian Release: jessie/sid + experimental which version of libssl1.0.0 do you have installed? If it's 1.0.2 from experimental, does downgrading to unstable's version help? I did have installed libssl1.0.0 version 1.0.2~beta3-1 from experimental, downgrading to 1.0.1j-1 (unstable) and installing libcurl3 (version 7.38.0-3) fixes this issue. Thanks! Jos v.Wolput -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734244: closed by Roland Stigge (Bug#734244: fixed in testdisk 6.14-3)
Please reopen bug #734244, testdisk_6.14-3_amd64 can't be installed because of the same dependency problem: - dpkg -i testdisk_6.14-3_amd64.deb (Reading database ... 191748 files and directories currently installed.) Preparing to unpack testdisk_6.14-3_amd64.deb ... Unpacking testdisk (6.14-3) over (6.14-2) ... dpkg: dependency problems prevent configuration of testdisk: testdisk depends on libntfs-3g844; however: Package libntfs-3g844 is not installed. dpkg: error processing package testdisk (--install): dependency problems - leaving unconfigured Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: testdisk - On 04/13/2014 07:09 PM, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the testdisk package: #734244: testdisk (6.14-2) has unmet dependencies It has been closed by Roland Stigge . Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Roland Stigge by replying to this email. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728361: lightdm, xfce4: No working restart/shutdown buttons
Hi, On my system, Debian/Sid using systemd and xfce4, I have solved the issue of no working lightdm and xfce4 buttons. As I already mentioned in Message #203, the xfce4 issue is fixed by upgrading policykit-1 to version 0.112-2 (experimental). The issue of the disappeared lightdm buttons is fixed by installing some rules in /etc/polkit-1/rules.d, enabling shutdown/restart/suspend/hibernate, see the attached file. Regards, Jos v.W. 99-lightdm-powerbuttons.rules Description: Binary data
Bug#728361: lightdm and pam-auth-update --force
In message #163 Louis Delmas advises pam-auth-update --force then selecting only "Unix Authentication". I tried selecting only "Register user sessions in the systemd control group hierarchy" and got a weird issue: lightdm allowed logging in without password. Immediately after typing a user name, no password is asked, and logging in is started, as user and as root. This could be a security issue. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728361: shutdown/restart/suspend/hibernate buttons
Upgrading policykit-1 to version 0.112-2 solves the problem (at least on my xfce4 system)! After upgrading policykit-1/0.105-4 (sid) to 0.112-2 (experimental) the xfce4 logout shutdown/restart/suspend/hibernate buttons are no longer greyed out, the lightdm/1.8.5-1 shutdown/restart/suspend/hibernate buttons are showed again. The only remaining issue is that after a second login the lightdm restart and hibernate buttons have disappeared, shutdown and suspend are still there. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728361: xfce4: No working restart/shutdown buttons
On 07/11/13 05:35, Yves-Alexis Perez wrote: > Can you check if libpam-ck-connector is installed? libpam-ck-connector was not installed. After installing still no shutdown... buttons in lightdm and xfce4 log out. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728361: xfce4: No working restart/shutdown buttons
After upgrading policykit-1/0.105-4 (sid) to policykit-1/0.112-2 (experimental) lightdm 1.6.3-1 shows the same issue. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#689191: python-libxml2 (v. 2.9.0) undefined symbol
>Is this helpful? >http://stackoverflow.com/questions/11643666/python-importerror-undefined-symbol- >for-custom-c-module Your reference talks about compiling a python module using g++. What I'm doing is building mesa, using 'make'. Compiling mesa with libxml2 v.2.9.0 (exp) and libxml2mod.so v.2.8.0 (sid) in /usr/lib/python2.7/dist-packages/ imports the module and builds without error. This seems to point to an error in libxml2mod.so v.2.9.0 (exp). Jos v.W. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659838: kmod: v5 acts like a fork bomb
Package: kmod Version: 5-1 System: amd64, kernel 3.2, Debian/Sid + experimental I tried playing midi using kmod 5-1 with all install commented out in /etc/modprobe.d/alsa-base.conf, Timidity worked but pmidi didn't, could not find sequencer, ending with system crash. Jos.v.W. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#533707: Debian changes to CPANPLUS
Hi Niko, On 8 Jul 2009, at 15:33, Niko Tyni wrote: The first patch is just a preconfigured CPANPLUS::Config::System module that tells CPANPLUS to install all modules, including core ones, in the site directories, even if their Makefile.PL or Build.PL says otherwise, so that they will not clobber the ones tracked by our package manager. Our @INC ordering will make sure that the local version in the site directory will be the first on the search path. (We've done this for ages with CPAN.pm and Makefile.PL, and I'm presently adding Build.PL support to that as well.) An alternative solution would be to modify the empty defaults in CPANPLUS::Config, but this one seems cleaner to me. No, this The Right Way(tm); ::System was designed for letting vendors/ packagers define defaults that apply to all users on the system. The other patch is about where the saved CPANPLUS::Config::System should go. Our policy says that configuration files need to be in / etc, and we have /etc/perl first on @INC for things like this. The patch is something of a hack, I'm not thrilled about messing inside the CPANPLUS::Internals namespace. Would you be willing to implement a cleaner hook for this? I would, but I'm not coming up with a clean way off the bat; the main problem is the Catch22 situation. Everything in CPANPLUS makes conditional decisions based on it's configuration settings, but this is not one of them. I'll give it some thought; in the meantime, the 'hack' is probably good enough. If you have any other questions, feel free to ask. Cheers, -- Jos Boumans "Whenever you find you are on the side of the majority, it is time to pause and reflect." - Mark Twain -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#535026: patch, please test
Robert Millan wrote: Hi, Please could you test if this patch helps? Thanks I am sorry I can no longer test while I got a disk crash! Jos v.W. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#535026: KMS not working after booting with grub-pc v.1.96+20090628-1 (unstable)
Robert Millan wrote: forcemerge 534944 535026 thanks On Mon, Jun 29, 2009 at 11:09:33AM +0800, Jos van Wolput wrote: Package: grub-pc Version: 1.96+20090628-1 (unstable) Severity: important System: Debian Sid Kernel: Linux 2.6.30-rc8-686 (kernel-archive.buildserver.net/debian-kernel) Processor: Pentium M, 852GM/855GM I am using KMS with module i915 modeset=1. When booting with the latest version of grub-pc (20090628), after loading module i915 modeset=1 the booting process is no longer shown on the screen until gdm is loaded. VT screens 1-6 are all showing the gdm login screen although without mouse pointer and no keyboard input. Only VT screen 7 works normally. When booting with version grub-pc_1.96+20090611-1, the screen is set to high resolution and KMS works perfectly. Hi, Same thing I said in #534944: I'm uploading 1.96+20090629-1, which includes some cleanup in the Linux loader. It's possible your problem might disappear with this version, please report. Note: Try it in text mode first (run "terminal_output console" in GRUB prompt). If that _does_ work, try from gfxterm then. Note2: If you can't wait, the patch you want is: svn diff -r 2372:2375 svn://svn.savannah.gnu.org/grub/trunk/grub2 Thanks! I just installed v. 1.96+20090629-1. Unfortunately it doesn't work. The bug is still the same as I previously mentioned. I have to revert to v. 1.96+20090611-1. Jos v. Wolput -- Jos VAN WOLPUT & JIN Yuehua 金月花 Tongelresestraat 204 A, 5613 DS Eindhoven, The Netherlands P.R.China, 310052 Hangzhou, Binjiang Qu, Jianghan Lu, Zhongxing Huayuan 49-1-1003 中国310052杭州市滨江去江汉路中兴花园49-1-1003 -- phone: 00 31 40 2449399 / 00 86 571 81713287 - 85054977 e-mail: wol...@onsneteindhoven.nl / wol...@sohu.com website: http://homepages.onsneteindhoven.nl/~wolput - Debian GNU/Linux: the Universal Operating System -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#450711:
On Mon, Mar 03, 2008 at 03:56:41PM +0100, Jos <[EMAIL PROTECTED]> wrote: I'm sorry that it took this long to respond, I'm like most of us, not enough time to do what I want. I tested 2.4.4., but its still terminate. in the log Mar 3 15:46:22 kast dkim-filter[29146]: Sendmail DKIM Filter: mi_stop=1 Mar 3 15:46:23 kast dkim-filter[29146]: Sendmail DKIM Filter v2.0.2 terminating with status 0, errno = 32 Mar 3 15:46:26 kast dkim-filter[29140]: Sendmail DKIM Filter: mi_stop=1 Mar 3 15:46:26 kast dkim-filter[29140]: Sendmail DKIM Filter v2.0.2 terminating with status 0, errno = 0 So there is still a problem. That's showing 2.0.2 still? I didn't notice that, sorry. It seems that somehow when I removed 2.0.2. the process was not killed??. So I thought 2.4.4 was running. I killed the process, and now 2.4.4 is running without any errors. Mike, thank you for all the good work. Jos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450711: Bugtracker error
I'm sorry that it took this long to respond, I'm like most of us, not enough time to do what I want. I tested 2.4.4., but its still terminate. in the log Mar 3 15:46:22 kast dkim-filter[29146]: Sendmail DKIM Filter: mi_stop=1 Mar 3 15:46:23 kast dkim-filter[29146]: Sendmail DKIM Filter v2.0.2 terminating with status 0, errno = 32 Mar 3 15:46:26 kast dkim-filter[29140]: Sendmail DKIM Filter: mi_stop=1 Mar 3 15:46:26 kast dkim-filter[29140]: Sendmail DKIM Filter v2.0.2 terminating with status 0, errno = 0 So there is still a problem. Jos Mike Markley schreef: On Sun, Feb 10, 2008 at 02:52:58AM -0800, Mike Markley <[EMAIL PROTECTED]> wrote: On Sun, Feb 10, 2008 at 11:29:27AM +0100, Jos <[EMAIL PROTECTED]> wrote: The last mail including the requested files, I've send it to both you and the BTS I didn't get them, either, and I'm not running any software in common with the BTS... strange. You may as well try with 2.4.4, since I've now uploaded it. Have you had a chance to try this? I'd really like to get this resolved, as it's been blocking dkim-milter from testing for quite some time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450711: Bugtracker error
The last mail including the requested files, I've send it to both you and the BTS Mike Markley schreef: On Fri, Feb 08, 2008 at 11:41:07AM +0100, Jos <[EMAIL PROTECTED]> wrote: I send the requested files 3 times, but got no confirmation from the bugtracker. Maybe a spamfilter is blocking the mail? Are you sending it just to the BTS, or to both me and the BTS? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450711: Bugtracker error
I send the requested files 3 times, but got no confirmation from the bugtracker. Maybe a spamfilter is blocking the mail? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450711:
Mike, did you ever received the requested info, I send dec 30? I don't see it in the bug tracker, Jos Mike Markley schreef: On Sun, Dec 23, 2007 at 12:37:02PM +0100, Jos <[EMAIL PROTECTED]> wrote: with 2.4.1, still a " can't initialize DKIM library" Then it may be a different problem; 2.4.1 should be able to handle the empty resolv.conf. Can you grab another set of ltrace/strace output for me? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450711:
with 2.4.1, still a " can't initialize DKIM library" Mike Markley schreef: Upstream fixed your specific case, and I've enabled another feature in the software that I probably should've enabled back in 2.3.2 when I turned on arlib. Can you test this binary with your setup? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450711:
That makes sense, as you already must know, I'm not a linux guru. In the resolv.conf man, "If no nameserver entries are present, the default is to use the name server on the local machine." according to other resources on the internet, resolv.conf is not even required if named is running. On localhost named is running, and a nslookup gives a correct result. The line in my resolv.conf does not make any sense, so I removed the resolv.conf. This didn't solved the error, so I created a resolv.conf with the line "nameserver 83.80.1.236" (the ip of the ISP nameserver) Still the same error "can't initialize DKIM library" in syslog. I'm confused, is this a config problem? If so, why does I never had and have any other problems with ip/name resolving. Jos Mike Markley schreef: On Mon, Dec 17, 2007 at 12:31:12PM +0100, Jos <[EMAIL PROTECTED]> wrote: with bind9. the server has the name "kast". Ah. I'm afraid that's not how resolv.conf works. "search" simply specifies a list of domains under which to search for hosts. So, for example, if you attempted to look up a host simply called "foo", the resolver would try resolving just "foo", then "foo.kast". That keyword has no bearing on where lookups are performed. Your system still needs "nameserver" entries so it knows what name server(s) to actually query. Upstream has dug into the resolver functions a bit and confirmed that this behavior would occur on a system with no nameservers available. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450711:
with bind9. the server has the name "kast". Mike Markley schreef: On Mon, Dec 17, 2007 at 10:08:07AM +0100, Jos <[EMAIL PROTECTED]> wrote: search kast How do you do name resolution? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450711:
Only one line search kast Mike Markley schreef: Aside from the updated deb, can I see your resolv.conf? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450711: bug 450711
Disable the arlib support did the trick. I'm running the test version without any problems. Do you reccoment to stay with this test version, or to downgrade to 2.0.2.? Jos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450711: bug 450711
I'm sorry to inform you, that with version 2.4.0. the problem still persists. So I'm back to version 2.0.2 Jos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450711:
Hi Mike, please send send me the 2.4.0 deb. I wil try is asap. It's oke to attach the config and trace files, but please remove any privacy related info, like the domainname, from the files. I don't want to increase the spam to this domain. Keep up the good work Jos Mike Markley schreef: Hi Jos, I've been unable to make heads or tails of this issue, so I'd like you to try with the 2.4.0 package I've just rolled. I'm uploading it tonight, but I can send you an i386 deb out-of-band if you'd like to try before it hits the mirrors. Just let me know. Also, do you mind if I attach the config and trace files you sent me to this bug report? That would be very helpful if I'm unable to make any headway and I ask upstream to take a look. Thanks, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450711: dkim-filter(2.3.2.dfsg-1) fails to start with settings that works with version2.0.2.dfsg-1. Only message is in syslog "dkim-filter[26391]: can't initialize DKIM library.". Settings are che
Package: dkim-filter Version: 2.0.2.dfsg-1 Severity: grave Justification: renders package unusable dkim-filter(2.3.2.dfsg-1) fails to start with settings that works with version2.0.2.dfsg-1. Only message is in syslog: "dkim-filter[26391]:can't initialize DKIM library.". Settings are checked and are valid for version 2.3.2.dfsg-1. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (990, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-486 Locale: LANG=nl_NL, LC_CTYPE=nl_NL (charmap=ISO-8859-1) Versions of packages dkim-filter depends on: ii adduser 3.102 Add and remove users and groups ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries ii libdb4.5 4.5.20-11 Berkeley v4.5 Database Libraries [ ii libmilter18.14.1-9 Sendmail Mail Filter API (Milter) ii libssl0.9.8 0.9.8g-1 SSL shared libraries dkim-filter recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#412054: [Strigi-devel] segfault running strigidaemon 0.3.11 on debian
Ah, libextractor! that is a problem causer. Please dont use it. 2007/2/26, CSights <[EMAIL PROTECTED]>: Hi Jos and Debian Bugzilla, I've attached output from valgrind after running: #valgrind xmlindexer kontact.desktop 2>&1>&valgrindOutput There are many messages such as "Loading `libextractor_exiv2' plugin failed: libextractor_exiv2.so: cannot open shared object file: No such file or directory" These files exist in /usr/lib/libextractor/, but perhaps they cannot be found by the program? Debian specific info: segfault: strigi-daemon, strigi-client, strigi-plugins (and their dependencies) no segfault: strigi-daemon, strigi-client (and their dependencies) So the problem is probably in the strigi-plugins package (as hinted at earlier in the bug report) Thanks, C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#412054: [Strigi-devel] segfault running strigidaemon 0.3.11 on debian
2007/2/23, CSights <[EMAIL PROTECTED]>: Hi Jon, I was able to find that the daemon segfaults on kontact.desktop file. I discovered which file was causing a segfault by running strigi-daemon under gdb, then when there was a segfault I checked lsof to find which file strigi-daemon had opened. Trying to run strigi-daemon again after moving kontact.desktop out of the search path, it again segfaults on another .desktop file. Adding *.desktop to the exclude filter, strigi-daemon segfaults, this time on "Adobe Acrobat 4.0.xpm". (Do you want this file?) Adding *.xpm to the exclude filter, strigi-daemon segfaults on a .jpg file. All of these files I can get the metainfo on (right-click, properties, meta info). Is this also a kfile function? I'm beginning to think strigi simply segfaults on the first file it encounters, and is probably a Debian specific problem. A bug has been opened already on the debian bug tracker. If you have any other input let me/us know: http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=412054 Hi C. It sounds like it crashes on the first file it sees! Does it actually index any file properly? Cheers, Jos Thanks, C. On Friday 23 February 2007 00:41, Jos van den Oever wrote: > Hi C., > Thanks for you report. Do you have an idea on what file it crashes? > The backtrace is useful in locating approximately where the error is. > It is in a kde plugins for analyzing the files. The simple solution > would be to remove strigita_kfile.so from your lib directory. This > will remove the problem. However, if you could track down the file > causing the problem, that would be very nice. > > Cheers, > Jos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#411479: bug 411479 iceweasel isn't controlable by external applications anymore
I have the same problem trying to call iceweasel v. 2.0.0.1+dfsg-3 from boinc: iceweasel is already running, but it is not responding. Applying the patch APPLICATION_ID=iceweasel in /usr/lib/iceweasel/iceweasel solves the issue! -- Jos VAN WOLPUT & JIN Yuehua Tongelresestraat 204 A, 5613 DS Eindhoven, The Netherlands P.R.China, 310052 Hangzhou, Binjiang Qu, Jianghan Lu, Zhongxing Huayuan 49-1-1003 -- phone: 00 31 40 2449399 / 00 86 571 81713287 - 85054977 email: [EMAIL PROTECTED] / [EMAIL PROTECTED] SIP phone: sip:[EMAIL PROTECTED] website: http://homepages.onsneteindhoven.nl/~wolput - Debian GNU/Linux: the Universal Operating System -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
