Bug#737015: icedove: Missing epoch in libnss3-dev build-dependency
Hello Sam, On Wed, Jan 29, 2014 at 11:43:44AM +, Sam Morris wrote: > Package: icedove > Version: 10.0.12-1 > Severity: normal > > The build-dependency on libnss3-dev doesn't take in to account the > package epoch. The dependency on libnss3-dev (>= 3.15~) in the package > in unstable is satisfied by version 2:3.14.5-1 of the package in stable. which version of Icedove you talking about? Debian version 10.0.12-1 depends on libnss3-dev >= 3.13.1 http://anonscm.debian.org/gitweb/?p=pkg-mozilla/icedove.git;a=blob;f=debian/control;h=1aac11940f625464bb93c9e2603d7ad745d25ab8;hb=a749d77cb42bc82b04d9ddf5edae4a95befef189 For this old version we want make any other packages. For building a backport or stable-security we have to use the libnss3 Package inside the sources because the libnss3-dev package in wheezy is to old. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#731538: [icedove] Keeps indexing forever
Hello Philip, On Fri, Dec 06, 2013 at 01:11:57PM +0100, Philipp Klaus Krause wrote: > Some time ago I notied that icedove constantly uses my cpu, draining my > notebook battery. Looking at the activities I found icedove was > indexing. I closed icedove and started it again, but it just started > indexing again. Soon it says that indexing is 99% completed, but both > the number stating how much has been indexed and the number stating how > much should be indexed in total keep going up. > Currently (some days later) it says that it indexed 12180596 out of > 12188498 messages. I don't think I have that many messages. > > Looking around the web, I only found a similar bug for thunderbird 3, > that apparently was fixed long ago. did this issue happen if you are running in safe mode? Have you also tried to disable partrially plugins? What happen if you backup your prefs.js and let Icedove recreate it while the next start. I know, all settings have to be redone, but I believe the problem is inside your configuration, not inside the Icedove binarys. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732652: testing changed Icedove package
Hello Ximin,
On Wed, Feb 12, 2014 at 04:00:47PM +, Ximin Luo wrote:
> All extensions are from the Debian repos. Actually I have disabled
> everything except moz-g-k and the bug is still present. I'm not sure
> how another extension could interfere with where icedove loads its
> libs from.
O.k. just want to be sure that no other installed software will causes
some trouble.
> I repeat, setting LD_LIBRARY_PATH=/usr/lib/icedove makes things work.
> Perhaps you just forgot a -Wl,rpath during the build process?
Mozilla has changed the starting wrapper for Thunderbird in version 14
or so. They use some kind of "intelligent" mechanism to detect the used
librarys and set a LD_LIBRARY_PATH if needed.
But this covers just a included directory 'plugins/' and not
/usr/lib/icedove.
So you propably right with the linker flag '-Wl,rpath". I rebuild
yesterday the current version 24.3.0 with this additional declaration to
LDFLAGS.
I uploaded the packages with this little change to
http://openmct.org/misc/icedove24-test/
I checked the builded binary 'icedove' with readelf. The binarys now
uses RUNPATH.
> (pbuilder)root@jessie:~/icedove-24.3.0/debian/tmp/usr/lib/icedove# readelf
> --dynamic icedove | grep PATH
> 0x001d (RUNPATH)Library runpath: [/usr/lib/icedove]
So I'd like to ask you if you please can test once again the Icedove
package with mozilla-gnome-keyring?
Unfortunately I never have used m-g-k and I'm having currently not much
time and testing installations to play with m-g-k. I think you know your
package much better then me and will find much quicker if it works
correctly with this changes while the build process.
> Here are the messages from icedove console:
>
> Could not read chrome manifest
> 'file:///usr/lib/icedove/components/components.manifest'.
This should be also fixed in the packages from above. We have forgotten
to change the install declarations for this directory. Mozilla has added
the manifest file between version 17 and 24.
> Failed to load native module at path
> '/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{6f9d85e0-794d-11dd-ad8b-0800200c9a66}/platform/Linux_x86_64-gcc3/components/libgnomekeyring-icedove.so':
> (80004005) libldif60.so: cannot open shared object file: No such file or
> directory
> Could not read chrome manifest
> 'file:///usr/lib/icedove/extensions/%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D/chrome.manifest'.
> While creating services from category 'profile-after-change', could not
> create service for entry 'Disk Space Watcher Service', contract ID
> '@mozilla.org/toolkit/disk-space-watcher;1'
>
> Feel free to install xul-ext-gnome-keyring and play with it yourself.
Thanks for your interaction.
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729073: icedove won't start
Hello Stephen, any news on this? Without further information I will close this bug. Regards Carsten On Fri, Nov 08, 2013 at 10:06:14PM +0100, Carsten Schoenert wrote: > could please give us some more information? > > Did you check this behaviour if you have disabled your plugins? > What happen if you use a fresh clean profile? > What you have done before you start icedove, did this happen right after > login to your desktop? What kind of desktop dou you use? > Did previous versions run without problems? > > Without further information it's not possible to fix such issues. > > Please provide a GDB backtrace if there are no other useful infos to > catch this issue. > https://wiki.debian.org/Icedove#Debugging > > Regards > Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732652: testing changed Icedove package
On Sat, Feb 15, 2014 at 07:46:17PM +, Ximin Luo wrote:
> (I assume 14 is a typo, you meant 24?)
Indeed, of course. ;)
> Perhaps a better fix would be to tweak the "intelligent" mechanism to
> be aware of /usr/lib/icedove, then. I can understand why upstream
> doesn't look here, since icedove is a Debian-specific name. This seems
> to me to be a better fix than to hard-code the path by -Wl,rpath,
> which AFAICS wasn't done before either (yet things still worked).
Mhh, I don't think so, Why?
The intelligence isn't really a intelligence. The wrapper script simple
checks if the *.so file are symbolic links and if so set a LD_LIBRAY_PATH.
The code part inside the script /usr/lib/icedove/run-mozilla.sh is the
follwing part:
> ##
> ## Set LD_LIBRARY_PATH
> ##
> ## On Solaris we use $ORIGIN (set in RUNPATH) instead of LD_LIBRARY_PATH
> ## to locate shared libraries.
> ##
> ## When a shared library is a symbolic link, $ORIGIN will be replaced with
> ## the real path (i.e., what the symbolic link points to) by the runtime
> ## linker. For example, if dist/bin/libxul.so is a symbolic link to
> ## toolkit/library/libxul.so, $ORIGIN will be "toolkit/library" instead of
> "dist/bin".
> ## So the runtime linker will use "toolkit/library" NOT "dist/bin" to locate
> the
> ## other shared libraries that libxul.so depends on. This only happens
> ## when a user (developer) tries to start firefox, thunderbird, or seamonkey
> ## under dist/bin. To solve the problem, we should rely on LD_LIBRARY_PATH
> ## to locate shared libraries.
> ##
> ## Note:
> ## We test $MOZ_DIST_BIN/*.so. If any of them is a symbolic link,
> ## we need to set LD_LIBRARY_PATH.
> ##
> moz_should_set_ld_library_path()
> {
> [ `uname -s` != "SunOS" ] && return 0
> for sharedlib in $MOZ_DIST_BIN/*.so
> do
> [ -h $sharedlib ] && return 0
> done
> return 1
> }
> if moz_should_set_ld_library_path
> then
>
> LD_LIBRARY_PATH=${MOZ_DIST_BIN}:${MOZ_DIST_BIN}/plugins:${MRE_HOME}${LD_LIBRARY_PATH:+":$LD_LIBRARY_PATH"}
> fi
>
> if [ -n "$LD_LIBRARYN32_PATH" ]
> then
>
> LD_LIBRARYN32_PATH=${MOZ_DIST_BIN}:${MOZ_DIST_BIN}/plugins:${MRE_HOME}${LD_LIBRARYN32_PATH:+":$LD_LIBRARYN32_PATH"}
> fi
> if [ -n "$LD_LIBRARYN64_PATH" ]
> then
>
> LD_LIBRARYN64_PATH=${MOZ_DIST_BIN}:${MOZ_DIST_BIN}/plugins:${MRE_HOME}${LD_LIBRARYN64_PATH:+":$LD_LIBRARYN64_PATH"}
> fi
> if [ -n "$LD_LIBRARY_PATH_64" ]; then
>
> LD_LIBRARY_PATH_64=${MOZ_DIST_BIN}:${MOZ_DIST_BIN}/plugins:${MRE_HOME}${LD_LIBRARY_PATH_64:+":$LD_LIBRARY_PATH_64"}
> fi
Currently I have no real idea how to tweek these lines to fix the issue without
the usage of -Wl,rpath. If you have a hint, please let us know. On the
other side, the rpath option doesn't break any thing.
> > So you propably right with the linker flag '-Wl,rpath". I rebuild
> > yesterday the current version 24.3.0 with this additional declaration to
> > LDFLAGS.
> > I uploaded the packages with this little change to
> >
> > http://openmct.org/misc/icedove24-test/
> >
>
> Thanks - could I ask you to sign the changes file so I can verify what I'm
> installing?
Yes, I uploaded a new gbp build with a signed dsc and changes file.
> This is an issue with icedove and not m-g-k though. I can only test,
> but I cannot attempt to fix it, since I'm not familiar with the
> icedove build system. You don't need to "know" m-g-k - it just helps
> you to verify that the bug is fixed, by confirming the absence of the
> "failed to load [..] .so" error message. You don't need to use m-g-k
> at all, you don't need to change any settings.
That's o.k. I'm in the opposite not familar with the
xul-ext-gnome-keyring package. ;)
> >> Here are the messages from icedove console:
> >>
> >> Could not read chrome manifest
> >> 'file:///usr/lib/icedove/components/components.manifest'.
> >
> > This should be also fixed in the packages from above. We have forgotten
> > to change the install declarations for this directory. Mozilla has added
> > the manifest file between version 17 and 24.
> >
> >> Failed to load native module at path
> >> '/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{6f9d85e0-794d-11dd-ad8b-0800200c9a66}/platform/Linux_x86_64-gcc3/components/libgnomekeyring-icedove.so':
> >> (80004005) libldif60.so: cannot open shared object file: No such file or
> >> directory
> >> Could not read chrome manifest
> >> 'file:///usr/lib/icedove/extensions/%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D/chrome.manifest'.
> >> While creating services from category 'profile-after-change', could not
> >> create service for entry 'Disk Space Watcher Service', contract ID
> >> '@mozilla.org/toolkit/disk-space-watcher;1'
> >>
> >> Feel free to install xul-ext-gnome-keyring and play with it yourself.
I tested yesterday the last ID build against the simple installed
xul-ext-gnome-keyring package. I couldn't see the error me
Bug#732652: testing changed Icedove package
Hello Ximin, I have CC'ed Mike, hopefully he can give us clearing answer. On Sun, Feb 16, 2014 at 02:39:36PM +, Ximin Luo wrote: > >> Currently I have no real idea how to tweek these lines to fix the issue > >> without > >> the usage of -Wl,rpath. If you have a hint, please let us know. On the > >> other side, the rpath option doesn't break any thing. > >> > > > > I have found a much cleaner way to fix this. :) > > > > Simply insert "libldif60.so" before "libldap60.so" in > > /usr/lib/icedove/dependentlibs.list. It appears the order is > > important - for example, if you add it to the end of the file, > > icedove fails to start with "Couldn't load XPCOM". > > > > Actually, I don't think this version of icedove touches > > run-mozilla.sh at all. (In theory that file should even set > > LD_LIBRARY_PATH correctly, since it includes MOZ_DIST_BIN.) Guido and myself talked today about that issue, we are asking ourself what in detail is now different from version 17? Why do we need now to set the LD_LIBRAY_PATH or set the option for RPATH. > > I'm not sure if this dependentlibs.list thing is an upstream bug - I > > can file one there too if you think it's appropriate. > > > > Looking into this issue further, it is the case that plain icedove and > its libxul.so do not have libldif60.so as a dependency (readelf > --dynamic do not list it AFAICS), which could explain why it's not > included in dependentlibs.list. We have to check the version 17 if there is the dependency inside that file, if so I think the version 24 has a bug on that. > However, m-g-k does for some reason: > > $ readelf --dynamic > /usr/lib/xul-ext/gnome-keyring/platform/Linux_x86_64-gcc3/components/libgnomekeyring-icedove.so > | grep ldif60 > 0x0001 (NEEDED) Shared library: [libldif60.so] > > I'm not doing anything special with the build process, so I am not > sure why ldif60 is in there. I'm pretty sure m-g-k doesn't need it - I > will see if I can build it without that dependency. > > But even if I tweak m-g-k like this, some questions still remain for > icedove/thunderbird: > > - if (the thunderbird developers) expect that no-one needs ldif60, why > keep it in the runtime directory? > - OTOH, if they do expect that (an extension) might need it, why not > include it in dependentlibs.list? There is no way for extensions to > load it dynamically, AFAIK. Thanks for figgering out this. @Mike Because you are deeper inside the whole source of Firefox/Thunderbird, do have a idea if the "issue" in the dependentlibs.list is a bug or do we something missing? Because we have to solve the RC bug depending on this bug report I think we can fix it in the first with the separate linker flag. And if this issue is related to an upstream bug we could get the transition to testing for the package Icedove* and related before Mozilla is releasing version 24.3.0+x. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732652: testing changed Icedove package
Hello Mike, On Mon, Feb 17, 2014 at 07:20:16AM +0900, Mike Hommey wrote: > On Sun, Feb 16, 2014 at 04:05:33PM +0100, Carsten Schoenert wrote: > > @Mike > > Because you are deeper inside the whole source of Firefox/Thunderbird, > > do have a idea if the "issue" in the dependentlibs.list is a bug or do > > we something missing? > > My bet is that you're building with -Wl,--as-needed, and that breaks > thunderbird's assumptions. hmm, quite possible. ,) Thanks for the hint, I play around with this option. I thought Christoph has taken this option because you use it in Iceweasel too. Anyway, one build later we will know more. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732652: testing changed Icedove package
On Mon, Feb 17, 2014 at 08:37:34AM +0100, Carsten Schoenert wrote: > Hello Mike, > > On Mon, Feb 17, 2014 at 07:20:16AM +0900, Mike Hommey wrote: > > On Sun, Feb 16, 2014 at 04:05:33PM +0100, Carsten Schoenert wrote: > > > @Mike > > > Because you are deeper inside the whole source of Firefox/Thunderbird, > > > do have a idea if the "issue" in the dependentlibs.list is a bug or do > > > we something missing? > > > > My bet is that you're building with -Wl,--as-needed, and that breaks > > thunderbird's assumptions. > > hmm, quite possible. ,) > Thanks for the hint, I play around with this option. I thought Christoph > has taken this option because you use it in Iceweasel too. Anyway, one > build later we will know more. Mike, obviously you are right! Thank you! @Ximin, I changed the debian/rules files an rebuild the whole packages. The testing yesterday workes like a charm an as expected. I pushed the build output once again to the URL I posted before. All files with *gbpe22ad0* inside are with changed linker flags. I think that will be the solution. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732652: testing changed Icedove package
tags 732652 pending thanks On Tue, Feb 18, 2014 at 05:10:55PM +, Ximin Luo wrote: > Hey Carsten, I have just tested e22ad0 and it works fine. :) You can > mark this bug closed. And I don't even need to re-compile m-g-k. > Thanks everyone! Excellent! I send my latest patches to Christoph, he will prepare a new upload to unstable. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712381: 17.0.10 on crashes wheezy
Hello Jonathan, On Tue, Feb 25, 2014 at 03:50:45PM +, J Chetwynd wrote: > okay so: > > $ icedove -safe-mode > > select disable addons from dialogue > > crashed wheezy as soon as application opened. > > further advice sought. do you noticed my last mail? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712381#10 There I wrote some things how you can collect informations to give some helpfull logs etc. But I don't believe at all that Icedove is the real problem, but this will be more clear with some logs to see what's going on. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728543: caff: missing dependency to libnet-smtp-ssl-perl
Hello Guilhelm, Am 25.02.2014 05:34, schrieb Guilhem Moulin: > If anything should depend on libnet-smtp-ssl-perl it should probably be > libmailtools-perl (which provides Mail::Mailer and which signing-party > depends on), not signining-party itself. > > libmailtools-perl actually added the dependency somewhere between the > wheezy (2.09-1) and sid/testing (2.12-1) versions :-) Indeed, it seems so. I looked inside my Jessie installation. > carsten@x201s:~ $ apt-cache show signing-party | grep Depends > Depends: libc6 (>= 2.14), perl, gnupg, libgnupg-interface-perl, > libtext-template-perl, libmime-tools-perl, libmailtools-perl, > libterm-readkey-perl, libclass-methodmaker-perl, qprint O.k. depends on 'libmailtools-perl'. > carsten@x201s:~ $ apt-cache show libmailtools-perl | grep Depends > Depends: perl, libnet-perl, libtimedate-perl, libnet-smtp-ssl-perl So everything should be fine for Jessie or greater. But as I can't check Wheezy directly. So a quick search via packages.debian.org shows me the dependency is still missing in Wheezy https://packages.debian.org/wheezy/signing-party https://packages.debian.org/wheezy/libmailtools-perl Don't know if it's possible to get a new version into stable-security with a better depends field set. -- Regards Carsten signature.asc Description: OpenPGP digital signature
Bug#712381: 17.0.10 on crashes wheezy
On Tue, Feb 25, 2014 at 05:33:29PM +, J Chetwynd wrote:
> it's not clear to me that this is icedove, however so far only icedove
> consistently crashes wheezy.
We will see.
> could you please send me specific instructions relating to my
> problem**?
I will try. :)
> bearing in mind I am concerned at possibility of corrupting hard
> drive. as with system crash I literally have to unplug to reboot.
Not really, the linux filesystems are more tolerate to such things like
the Windows NTFS.
> **I read through:
> https://wiki.debian.org/Icedove#Debugging
> and found it confusing.
Debugging is mostly for all "normal" users not easy. To get debugging
informations you have to do some things you normaly never will do, we have
hopefully collect all the needed things and steps written into the wikipage.
But o.k. I will make it hopefully clear to you what you should do.
> I read through and tried the hello exercise:
> How to get a backtrace
>
> on wheezy I tried:
>
> icedove -g [-safe-mode] 2>&1 | tee /tmp/icedove-gdb-$(apt-cache show icedove
> | grep Version | awk '{ print $2 }')_$(date +%F_%T).log
>
> before system crash iirc
> -g was not recognised,
You have read the line above this command line? This line is important!
>> # use this if you are running Wheezy (stable) or Squeeze (oldstable)
You are using Wheezy (and not Squeeze) o.k., but not the 'stable' tree. The
stable packages for Icedove are from version 10!
So o.k. what tree of Wheezy you are using? As you wrote you have installed
Icedove with version 17.0.10, so you must use the 'stable-security' tree
(that is the normal case).
https://packages.debian.org/source/stable/icedove
With this information you will asume that the command above is the wrong line.
So you have simple to use the other command line, you have could find it out
by yourself by just testing it too.
> i also tried :
>
> $ gdb icedove -g [-safe-mode] 2>&1 | tee /tmp/icedove-gdb-$(apt-cache show
> icedove | grep Version | awk '{ print $2 }')_$(date +%F_%T).log
>
> gdb: unrecognized option '-g'
With this line you have tried to start the GNU Debugger 'gdb' with an unknown
option for gdb. The gdb works in another way. Either you simply start the
debugger (gdb) and starting then the application inside, or you have gdb to
tell wich pid or remote host to take. The second line on the wiki uses a
wrapper script from the mozilla sources that calls the gdb with needed
arguments and starts then the gdb session. No further action have to be done
by you.
And please create a tarball of your logs! The output of the gdb will be hughe.
For example do a
$ tar Jcvf I_set_a_better_filename.tar.xz /path/to/logfile1 /path/to/logfile2
# and so on
As the description in the example for the possible output of the gdb is a
little bit misstakable I will rework the wiki side.
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712381: 17.0.10 on crashes wheezy
Please do not making top posting!! On Tue, Feb 25, 2014 at 06:22:25PM +, J Chetwynd wrote: > okay found what may likely be the issue. > should maybe be moved to separate bug? There are other bugs around issues with lost network connections but I think they not related to this bug. But please go through the bug list by yourself. > if ethernet cable is unplugged icedove loads fine no issues. > can read old mail etc... You unplug the cable and Icedove is working? Sounds strange and make me more believing it's not a Icedove problem. We will see more in the backtrace. > due to OS upgrade used webmail and changed password. I have now > removed all passwords, but still freezing system on password dialogue. > > ideas please We need a log from such a crash, without it's like navigation inside a frog. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734089: icedove shows read messages as unread
forcemerge 726052 734089 thanks Hello Gary, On Thu, Feb 06, 2014 at 04:02:05PM -0500, Gary Dale wrote: > I've switched from using CIFS to NFS for the share that my e-mail is that's a importand information you using no native classical linux filesystem! In the starting mail you haven't provide this info. > stored on and that seems to have fixed the problem. There seems to > be a problem with either Icedove and/or Samba that is leaving the > e-mail database in an inconsistent state. I dont think so. It's more a problem of the filesystem I would say. So what to do here? The issue isn't a problem of Icedove (Thunderbird). I suggest to write a hint into the wiki site of Icedove and close this bug. I merged your other bug into this, so closing one of them closes the other one too. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732652: more info needed
tags 732652 help thanks Hello Ximin, On Tue, Jan 21, 2014 at 04:57:13PM +, Ximin Luo wrote: > Hey, just pinging to say that this still happens in 24.2.0, and to > update my email address. I haven't looked at the debugging symbols > yet, but I will do when I get some time. what Icedove related extensions do you have installed? All extensions are from the Debian repositorys or there are some external extensions? What happen if you starting Icedove in safe mode? And can you please provide a debug log? Without that we are unable to track down this issue. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692984: upstream binary / DAViCal / CardDAV problems on wheezy
Hello Daniel, I imported the latest upstream version 24 of the sogo-connector and rebuild the package. The current output of git-buildpackage will be found on the links I posted earlier. On Sat, Aug 31, 2013 at 05:36:18PM +0200, Daniel Pocock wrote: > I found the solution to my problem using the connector > > I can confirm that both the TB10 and TB17 connectors from upstream work > with the respective icedove versions in wheezy against a DAViCal server > on wheezy. > > The reason it didn't work for me in the beginning is because the default > config in DAViCal is for a calendar-only resource. > > Somehow, Evolution was able to use the calendar-only resource to store > vCards: that seems like a bug in both DAViCal and Evolution, they > shouldn't allow that. However, that left me thinking there was > something wrong with the SOGo Connector because it couldn't see the > contacts the Evolution could create and retrieve. > > When I started looking around in the DAViCal settings, I realised I had > to create another resource for my address book and DAViCal creates a > different URL for that. I put that new address book URL in the SOGo > Connector and it is working. I plan to write a wiki page if the package is once available thrue the repositorys. Your summary above would be good to place then there. > It would be useful if the connector could give users a helpful error if > they misconfigure it like that, I had no useful error to help me and I > was just guessing what was wrong. Sadly true, maybe I can talk about that with Jeroen in the near future. > One minor problem left, Icedove address book only allows up to 2 email > addresses per contact but Evolution and Android allow more than 2. It > is not clear to me whether changing those contacts in Icedove's address > book will result in the loss of the extra email addresses when they sync. I don't believe Mozilla will work on such "minor" issues. We can be happy if Mozilla is making some housekeeping inside the code and implements some more core requirements like the TLS 1.2 implementation in the near past. We will see. :) Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#469448: icedove: Refuses to refuse certificate
Hello Dick, On Wed, Mar 05, 2008 at 09:35:38AM +, Dick Middleton wrote: > Package: icedove > Version: 2.0.0.9-3 > Severity: normal > > > Connecting to imaps server which offers unknown SSL certificate you get the > 'use always', 'use once' or 'never use' dialog. If you select the 'never use' > option or the 'Cancel' button the dialog closes and then reopens requesting > again. This is an infinite loop; it's impossible to get rid of it. Not only > that but it blocks the GUI alot making it very difficult to do anything such > as quit or add the root certificate needed to authenticate. > > I guess it's an upstream bug but the Mozilla bug server seems broken right now > so I can't check. is quite long ago you opened this bug. This bug is still alive with current versions of Icedove? I'm not able to test this behaviour, I'm not owning a imaps server instance with a self signed certificate. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724688: icedove: affects mozilla-gnome-keyring too
forwarded 724688 https://bugzilla.mozilla.org/show_bug.cgi?id=925823
retitle 724688 icedove: libxul.so incompatible with some external addons
thanks
Hello Ximin,
On Thu, Dec 19, 2013 at 06:52:55PM +, Ximin Luo wrote:
> Control: retitle -1 icedove unnecessarily incompatible with some binary
> extensions, potentially crashing
> Control: severity -1 serious
>
> This affects mozilla-gnome-keyring too, though only for icedove-dev
> 24.1.1 (worked in icedove-dev 24.0 for me).
>
> When I try to rebuild that extension against 24.1.1, it installs into
> icedove and is enabled but ineffective, and I get this in the error
> log:
>
> Failed to load native module at path
> '/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{6f9d85e0-794d-11dd-ad8b-0800200c9a66}/platform/Linux_x86_64-gcc3/components/libgnomekeyring-icedove.so':
> (80004005) /usr/lib/icedove/libxul.so: version `xul24.0' not found (required
> by
> /usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{6f9d85e0-794d-11dd-ad8b-0800200c9a66}/platform/Linux_x86_64-gcc3/components/libgnomekeyring-icedove.so)
Mozilla is versioning the libxul.so since the release of version 24 or
before. So basicly this is not a bug I think. Especially we build our
own "lightning".
The forwareded link is showing that it is nessesary to respect the
correct libxul version for the usage of a own extension.
As i can see you use icedove-dev (>= 17.0) in your control file, the
icedove version has to fit the version from experiemental (currently) if
you want build against the icedove 24.
We are planning to build icedove 24.2 right after the New Years Day and
upload it to unstable, the last ESR version 17 is now eol.
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732652: icedove does not load libraries from /usr/lib/icedove
Hello Ximin,
On Thu, Dec 19, 2013 at 10:00:45PM +, Ximin Luo wrote:
> It works fine with iceweasel 26.0. A previous similar package I built
> against icedove 24.0 also worked fine.
>
> However, with the new icedove 24.1.1, the package installs fine but I
> get this error in the log when starting icedove:
>
> Failed to load native module at path
> '/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{6f9d85e0-794d-11dd-ad8b-0800200c9a66}/platform/Linux_x86_64-gcc3/components/libgnomekeyring-icedove.so':
> (80004005) libldif60.so: cannot open shared object file: No such file or
> directory
>
> and the extension is "enabled" but does not work. But libldif60.so
> does exist in /usr/lib/icedove.
>
> OTOH, if I start icedove with LD_LIBRARY_PATH=/usr/lib/icedove, then
> everything works fine.
>
> This is possibly related to #724688, but I'm not sure. Shortly after I
> posted my message there, I was no longer able to reproduce the
> "xul24.0" error; instead this "libldif60.so" error popped up, and I
> worked around it as I just described.
can you please make a log with debugging symbols?
https://wiki.debian.org/Icedove#Debugging
Thanks and regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727677: icedove: "copies & folders" settings not saved with a gmail IMAP account
Hello Fabien, On Fri, Oct 25, 2013 at 11:42:08AM +0200, Fabien R wrote: > Package: icedove > Version: 10.0.12-1 > Severity: normal > > Dear Maintainer, > > I choose to keep a copy on a "sent" folder or a "draft" folder for my account. > After restarting icedove, my changes are lost. what "choose to keep" exactly mean? What you have done? You infos are a little bit small. What kind of extensions do you have installed and active? Your issue happen also without any extensions? Is there something visible in the error console? If I use the context menu and select "Copy To" the copy of the mail will be found on the selected folder. But I have to say that I use the Icedove from stable-security that's highly recommended to use instead of the Icedove version 10 from the Wheezy release! Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#725823: pu: package icedove/3.0.11-1+squeeze15
Hello, On Tue, Oct 08, 2013 at 09:30:26PM +0200, Carsten Schoenert wrote: > Any chances to get this change into the next point release for Squeeze? the next point release will for Squeeze is comming in february as far as I can see. What about this bug to take place into the next point release? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734859: icedove: FTBFS on powerpcspe: cannot reload integer constant operand in 'asm'
Hello Roland,
On Fri, Jan 10, 2014 at 01:31:01PM +0100, Roland Stigge wrote:
> icedove FTBFS on powerpcspe like this:
>
> ...
> In file included from
> /«PKGBUILDDIR»/mozilla/js/xpconnect/loader/mozJSComponentLoader.h:8:0,
> from
> /«PKGBUILDDIR»/mozilla/js/xpconnect/loader/mozJSComponentLoader.cpp:31:
> ../../../dist/include/jsapi.h: In member function 'nsresult
> mozJSComponentLoader::ImportInto(const nsACString_internal&, JSObject*,
> JSContext*, JSObject**)':
> ../../../dist/include/jsapi.h:151:45: error: cannot reload integer constant
> operand in 'asm'
> asm volatile("":: "g" (hold) : "memory");
> ^
> ../../../dist/include/jsapi.h:151:45: error: cannot reload integer constant
> operand in 'asm'
> asm volatile("":: "g" (hold) : "memory");
> ...
>
> The attached patch fixes this by omitting the asm construction on powerpcspe
> only (__NO_FPRS__).
we have no plans to work longer on the 17.0.x series because Mozilla has
stopped the 17esr versions. So I was looking at the current 24.2.0 if
your patch is needed there. But Mozilla has changend once more the code
base, I can't find the "asm volatile" statement somethere in the source.
So I think there is no need to patching anything related to the error
you have written.
Christoph is planning to create a upload of the 24.2.0 to unstable
within the next days. So we will see if some other errors will occur.
Please let us know if there some new action to take.
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724688: icedove: affects mozilla-gnome-keyring too
Hello Ximin, On Fri, Dec 20, 2013 at 08:44:00PM +0100, Carsten Schoenert wrote: > Mozilla is versioning the libxul.so since the release of version 24 or > before. So basicly this is not a bug I think. Especially we build our > own "lightning". > The forwareded link is showing that it is nessesary to respect the > correct libxul version for the usage of a own extension. > > As i can see you use icedove-dev (>= 17.0) in your control file, the > icedove version has to fit the version from experiemental (currently) if > you want build against the icedove 24. > > We are planning to build icedove 24.2 right after the New Years Day and > upload it to unstable, the last ESR version 17 is now eol. are you able to check the latest Icedove upload in unstable with mozilla-gnome-keyring? Hopefully it should working now with a dependencie on the current Icedove version. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735156: Does not use desktop notifications anymore
Hello, On Mon, Jan 13, 2014 at 12:00:15PM +0100, Yuri D'Elia wrote: > It seems like Icedove 24 cannot use desktop notifications for new mail anymore > (17.* could). The configurable "alert" shows only the thunderbird popup. > > Needless to say, it would be nice if proper desktop notification integration > could be restored. which desktop environment you are using? The notification works here on Gnome 3 and KDE. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728944: icedove: segmentation fault in icedove 24.0-1
Hello Daniel, are this segfaults also happen with the current 24.2.0? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728543: caff: missing dependencie to libnet-smtp-ssl-perl
Package: signing-party
Version: 1.1.4-1
Severity: normal
Dear Maintainer,
caff is not possible to send emails via smtps because the package
libnet-smtp-ssl-perl is needed for this. signing-party doesn't even
have not a Recommends entry for this package. But I think signing-party
should depend on this because some user won't send mails without
smtps support.
I found this issue while I set up a additional line to my .caffrc.
> $CONFIG{'mailer-send'} = [ 'smtps', Server => 'securesmtp.t-online.de', Auth
> => ['[my-name]@t-online.de', 'very-secret'] ];
After installing libnet-smtp-ssl-perl everything goes well.
Regards
Carsten
-- System Information:
Debian Release: 7.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-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
Versions of packages signing-party depends on:
ii gnupg 1.4.12-7+deb7u2
ii libc6 2.13-38
ii libclass-methodmaker-perl 2.18-1+b1
ii libgnupg-interface-perl0.45-1
ii libmailtools-perl 2.09-1
ii libmime-tools-perl 5.503-1
ii libterm-readkey-perl 2.30-4+b2
ii libtext-template-perl 1.45-2
ii perl 5.14.2-21+deb7u1
ii qprint 1.0.dfsg.2-2
Versions of packages signing-party recommends:
ii exim4-daemon-light [mail-transport-agent] 4.80-7
ii libgd-gd2-noxpm-perl 1:2.46-2+b1
ii libpaper-utils 1.1.24+nmu2
ii libtext-iconv-perl 1.7-5
ii whiptail 0.52.14-11.1
Versions of packages signing-party suggests:
ii imagemagick8:6.7.7.10-5+deb7u2
ii mutt 1.5.21-6.2+deb7u1
pn texlive-latex-recommended
pn wipe
-- 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#728834: doesn't know how to open http links by default
Hello Peter, On Tue, Nov 05, 2013 at 09:51:36PM -0500, Peter Eisentraut wrote: > Package: icedove > Version: 24.0-1 > Severity: normal > > I fresh icedove installation doesn't know how to open http links in > emails. Instead, it requires me to use a file system dialog to dig my > way down to /usr/bin/something, which is very unfriendly and slow. > Given that Debian has a standard for this (x-www-browser), this could > be configured by default. what kind of window manager do you use? What's your system? A fresh install from unstable or experiemental? What else do you have done? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729073: icedove won't start
Hello Stephen, On Fri, Nov 08, 2013 at 09:17:29AM -0600, Stephen Crowley wrote: > Package: icedove > Version: 17.0.9-2 > Severity: important > > crow@serenity:~$ icedove > > (process:7466): GLib-CRITICAL **: g_slice_set_config: assertion > sys_page_size == 0' failed > Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line > 103: Having multiple values in isn't supported and may not work > as expected > Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line > 138: Having multiple values in isn't supported and may not work > as expected > Fontconfig warning: "/etc/fonts/conf.d/90-fonts-unfonts-core.conf", > line 11: Having multiple values in isn't supported and may not > work as expected > crow@serenity:~$ could please give us some more information? Did you check this behaviour if you have disabled your plugins? What happen if you use a fresh clean profile? What you have done before you start icedove, did this happen right after login to your desktop? What kind of desktop dou you use? Did previous versions run without problems? Without further information it's not possible to fix such issues. Please provide a GDB backtrace if there are no other useful infos to catch this issue. https://wiki.debian.org/Icedove#Debugging Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729431: icedove-dev: please ship more python tools from source package's mozilla/config
Hello Daniel, On Tue, Nov 12, 2013 at 02:29:55PM -0500, Daniel Kahn Gillmor wrote: > I've been working on cleaning up the enigmail debian packaging, which > Build-Depends: icedove-dev. Good to here you are on the way to ship the enigmail addon usable for the Icedove 24. > I find that to build enigmail fairly cleanly, i still need to "borrow" > a few files from icedove's source package. It would be great if these > files could be shipped directly as part of icedove-dev, so i don't > have to embed a separate copy of them in enigmail_$foo.debian.tar.gz. That should be no problem to do that, the -dev package is so huge, it doesn't matter to ship this files too. ;) Thanks for your suggestion. > I don't think it matters to me where you place them in the icedove-dev > package, but it would help if they're all in the same directory. We will find a place for the python files, as far as I can see they my be shipped in '/usr/lib/icedove-devel/config' Guido and myself are worked last week an the FTBFS issues, a new version is also released by Mozilla. Hopefully we can meet us this week again and can further in preparing the next packaging round. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#628885: [Workaround] Folderpane ignores new Message
forwarded 628885 https://bugzilla.mozilla.org/show_bug.cgi?id=675526 thanks Hello Jakobus, Am 12.11.2013 12:02, schrieb "Jakobus Schürz (offiziell)": >> in case of this it make sense to forward that to upstream. >> Are you able to check if there is a entry in the Mozilla Bugzilla and if >> not to create a new bug? >> In both cases please provide the Bugzilla URL so we can set a additional >> forwarded entry to that bug. Thank you! > > > There is a Bugreport from me from 2011... > > https://bugzilla.mozilla.org/show_bug.cgi?id=675526 > > Nothing happened till now... sadly true. But you are not alone. There are many bugs that exist for years and nothing (seems?) really happen upstream. Unfortunately the packaging team hasn't enough time to dig deeper into such problems so we can't help much in case of such issues. After forwarding your URL we (and you) will be informed in case the status is changed in the forwarded bug. -- Regards Carsten Schönert -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727819: [icedove] found workaround
Hello Lorenz, On Mon, Oct 28, 2013 at 02:53:52PM +0100, Lorenz Wenner wrote: > i just found this simple work around, which i would liketo share with > you. In case icedoce is going mad, just tell it to work offline and you > are done. Until next time it goes mad... did this happen if you running Icedove in safe-mode (disables all plugins)? Or did this happen also with a fresh profile? You can run Icedove with some logging [1] to see what's going on inside. Mostly something inside the JS handling will produce high CPU activity I think. [1] https://wiki.debian.org/Icedove#Debugging Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712381: icedove: Icedove runs cpu to 100% when getting mail, program unusable
On Sat, Jun 15, 2013 at 02:16:52PM +0100, Christopher Haywood wrote: > For some reason icedove won't get me any more mail without crashing > > I had previously deleted lots and lots of mail > got reports of scripts not working > killed program. > restarted - mail had been deleted > opening inbox > cpu running at 100% > program now unusable > > attempted killing the program again, but its same situation on all restarts > > expected to be able to access the inbox however this is not the case, it > continues to try to access inbox, and of course continues crashing. do you have try to start without any extensions activated? Mostly some of the extensions are going mad and produces a high CPU load. Please visit the manpage for Icedove to find out how to do that. If possible turn on the debugging console (for JS) with "Crtl + Shift + J" to see what script is producing errors. If Icedove isn't starting correctly at all please create a log of the activity/crash from icedove [1]. [1] https://wiki.debian.org/Icedove#Debugging Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#703857: icedove: crashes with sigseg due NSS ldap lookup
Hello Thomas, On Mon, Mar 25, 2013 at 08:33:28PM +0100, Thomas Liske wrote: > I've done the following: > > thomas@buechse:~$ unset LANG > thomas@buechse:~$ export NSPR_LOG_MODULES=MCD:5 > thomas@buechse:~$ export NSPR_LOG_FILE=/tmp/icedove-mcd.txt > thomas@buechse:~$ strace -e file -f -s2048 -o > /tmp/icedove-strace.txt icedove > Segmentation fault (core dumped) > thomas@buechse:~$ ls -lha /tmp/icedove-* > -rw-r--r-- 1 thomas users 0 Mar 25 20:31 /tmp/icedove-mcd.txt > -rw-r--r-- 1 thomas users 54K Mar 25 20:31 /tmp/icedove-strace.txt > > > >You can combine the two logs into one file please! > > > > The MCD log is empty, nothing to combine at all. you allready use the deprecated version from stable? We wont do any work on this old ESR version. If the error happen on the latest 17.0.10 in stable-security please create a debugging log with the icedove debug package [1]. Without any output we can't catch anything. Please try before to start Icedove without any extension in safe-mode. [1] https://wiki.debian.org/Icedove#Debugging Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562984: missing metadata for mozilla-devscripts
Hello Benjamin,
On Wed, Aug 21, 2013 at 01:33:06PM +0200, Carsten Schoenert wrote:
> diff --git a/debian/control b/debian/control
> index 0e8cfde..9d82356 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -51,6 +51,7 @@ Depends: fontconfig, psmisc, debianutils (>= 1.16),
> ${shlibs:Depends}, ${misc:De
> Recommends: myspell-en-us | hunspell-dictionary | myspell-dictionary
> Suggests: fonts-lyx, libgssapi-krb5-2, ${gnome:Depends}
> Provides: mail-reader
> +Xb-Xul-AppId: {3550f703-e582-4d05-9a08-453d09bdfdc6}
> Replaces: icedove-gnome-support (<< 3.0-1~)
> Breaks: myspell-ru (<< 0.99g5-8.1), myspell-lv (<< 0.7.3-3.1), myspell-et
> (<< 1:20030606-12.1), myspell-fi (<< 0.7-17.2), myspell-cs-cz (<<
> 20040229-4.1), myspell-el-gr (<< 0.3-1.1), myspell-nn (<< 2.0$
> Description: mail/news client with RSS and integrated spam filter support
>
> What about the other packages?
> icedove-{dbg,dev}, calendar-timezone, calendar-google-provider, iceowl?
can you please check the previous question?
We prepare the next turn for the current version 24 and we would place
the requested things inte the next release.
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562984: missing metadata for mozilla-devscripts
On Sat, Nov 23, 2013 at 12:54:58PM +0100, Benjamin Drung wrote:
> > diff --git a/debian/control b/debian/control
> > index 0e8cfde..9d82356 100644
> > --- a/debian/control
> > +++ b/debian/control
> > @@ -51,6 +51,7 @@ Depends: fontconfig, psmisc, debianutils (>= 1.16),
> > ${shlibs:Depends}, ${misc:De
> > Recommends: myspell-en-us | hunspell-dictionary | myspell-dictionary
> > Suggests: fonts-lyx, libgssapi-krb5-2, ${gnome:Depends}
> > Provides: mail-reader
> > +Xb-Xul-AppId: {3550f703-e582-4d05-9a08-453d09bdfdc6}
> > Replaces: icedove-gnome-support (<< 3.0-1~)
> > Breaks: myspell-ru (<< 0.99g5-8.1), myspell-lv (<< 0.7.3-3.1), myspell-et
> > (<< 1:20030606-12.1), myspell-fi (<< 0.7-17.2), myspell-cs-cz (<<
> > 20040229-4.1), myspell-el-gr (<< 0.3-1.1), myspell-nn (<< 2.0$
> > Description: mail/news client with RSS and integrated spam filter support
>
> Yes, that's correct.
Fine, I can now prepare a patch before the next Icedove version will be
packed.
> > What about the other packages?
> > icedove-{dbg,dev}, calendar-timezone, calendar-google-provider, iceowl?
>
> icedove-{dbg,dev}, calendar-timezone, calendar-google-provider should
> not have this information, because a Xul extension that supports
> {3550f703-e582-4d05-9a08-453d09bdfdc6} should depend on icedove, but not
> on icedove-dbg, icedove-dev, calendar-timezone or
> calendar-google-provider.
Thanks for clearification.
> Does the Iceowl plugin have an own AppId and does it support it's own
> Xul-extensions?
That's a thing we have to asked Guido because that's his baby. He's CC'd
by this mail.
> PS: Sorry for the long delay. Your mail was in my primary inbox waiting
> for being answered.
No problem, we all lack of more free time. ;)
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675330: [icedove] Yahoogroups emails don't show reply list button.
Hello Mika, On Thu, May 31, 2012 at 12:38:41PM +0300, Mika Suomalainen wrote: > Hi, > > I noticed that "reply list" button doesn't appear with emails, which > are sent to Yahoo groups. > > I'm not sure is this Icedove or Yahoo issue. this issue is releated to the missed header from the Yahoo system. Without "List-ID:" in the message header Icedove can't identify the mail correctly an no "Reply To List" is shown. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#730450: icedove: crash after updating 10->24 with lightning add on
forcemerge 730450 724688
retitle 724688 icedove won't start with lightning
thanks
Hello Berni,
you writing you use the lightning plugin, do you use the real lightning
plugin from Mozilla or the iceowl plugin?
On Mon, Nov 25, 2013 at 08:44:08AM +, Berni Elbourn wrote:
> elbournb@cat:~$ icedove
> [calBackendLoader] Using libical backend at
> /home/elbournb/.icedove/h1qw5nt0.default/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical.manifest
> icedove: relocation error:
> /home/elbournb/.icedove/h1qw5nt0.default/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/Linux_x86_64-gcc3/libcalbasecomps.so:
> symbol _ZN2js13CheckedUnwrapEP8JSObjectb, version xul24.0 not defined in
> file libxul.so with link time reference
[...]
> elbournb@cat:~$ sudo apt-get install libmozjs24d xulrunner-24.0
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following package was automatically installed and is no longer required:
> sdparm
> Use 'apt-get autoremove' to remove it.
> The following NEW packages will be installed:
> libmozjs24d xulrunner-24.0
> 0 upgraded, 2 newly installed, 0 to remove and 3 not upgraded.
> Need to get 0 B/18.0 MB of archives.
> After this operation, 47.2 MB of additional disk space will be used.
> Retrieving bug reports... Done
> Parsing Found/Fixed information... Done
> Selecting previously unselected package libmozjs24d.
> (Reading database ... 327645 files and directories currently installed.)
> Unpacking libmozjs24d (from .../libmozjs24d_24.1.0esr-1~bpo70+1_amd64.deb) ...
> Selecting previously unselected package xulrunner-24.0.
> Unpacking xulrunner-24.0 (from
> .../xulrunner-24.0_24.1.0esr-1~bpo70+1_amd64.deb) ...
> Processing triggers for man-db ...
> Setting up libmozjs24d (24.1.0esr-1~bpo70+1) ...
> Setting up xulrunner-24.0 (24.1.0esr-1~bpo70+1) ...
The current version of Icedove in Backports is maintaint by Mike Hommey,
not by the Icedove Package Team. We currently only provide version 24 in
experimental because we don't feel it is currently ready for usage
without problems, as we see with by your bugreport.
Anyway, it's a regression.
We allready have another bug #724688 with the same symptom, a missed
symbol in the libxul.so. We haven't found any time to work on it,
propably there is something to fix while we link the libxul.so in the
build of the Icedove packages.
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752162: icedove: A line appears on right side bottom of the screen
Hello, On Fri, Jun 20, 2014 at 03:55:16PM +0530, Afsal wrote: > A line appeared right side (bottom). It appeared when using Icedove, I > deleted an unwanted message from my inbox suddenly this a blue color > line appeared. I think it is a divider, it has shadow effect, arround > length of half of the screen. I can't reproduce this behaviour with KDE and Gnome as desktop. Which desktop environment do you use? And are you able to make a screenshot from this issue? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#751077: icedove: program locks up when attempting attachment, gdb no help
Hello Arthur, On Thu, Jun 19, 2014 at 05:36:46PM +0930, Arthur Marsh wrote: > I tried backing up my .icedove directory and used a basic imap > setup with my ISP on a new profile and tried opening an attament, > same result of: > > Segmentation fault > > when run outside of gdb and > > Cannot find user-level thread for LWP 31075: generic error > > when run inside gdb unfortunately this helps nothing to find the reason for this issues. Without a backtrace there is nothing what we could do. We need at least the adresses of the data why there is something segfaulting. Are other software also ending up in a segfault? Do you have special hardware used or something special in your desktop environment? Do you have checked the RAM for possible errors? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#751077: icedove: segfaults on startup outside of gdb
Hello Arthur, please remove all not needed quoting if you answer by email to the BTS. Also adjust please the subject of the email! Your last emails was filtered out here, so normally I haven't seen your last entrys to the BTS. Thanks! On Mon, Jun 23, 2014 at 11:26:42PM +0930, Arthur Marsh wrote: > I disabled all plug-ins and tried gdb icedove, and still had a segfault: > > Program received signal SIGSEGV, Segmentation fault. > 0xa5c37008 in ?? () > (gdb) bt You must use 'thread apply all bt' (as already written in the wiki) inside the gdb to see all the threads that are initiated by the icedove binary. Your last logs are not suitable because we can't see the conflicting threads that are triggering the segfault. Please disable the Carrige Return if you are writing a email with a log inside or better append the log as a file. Your log isn't well readable. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729073: icedove won't start
Hello Nick, Am 10.04.2014 12:51, schrieb Nick: > I'm getting the same or similar bug after the most recent update. > > Ironically, I first realised I had the problem after trying to debug icedove, > in relation to another bug ( > https://bugzilla.mozilla.org/show_bug.cgi?id=963114 ). Icedove started and > first and showed the checking extensions compatibility dialogue. It said the > lightning (calendar) addon needed updating, which I did. It sorted that, and > then dissappeared. After that it wouldn't start again. you have installed the Lightning extension from Mozilla? Lightning *and* Icedove won't work together after version 24 because of internally symbol mismatch. Please use iceowl-extension from the Debian repositories instead of the Mozilla Lightning extension. The backtrace shows exactly the same error as bug #724688 [1]. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724688 -- Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729073: icedove won't start
Version: 24.3.0-2 Hello Nick, On Thu, Apr 10, 2014 at 07:17:17PM +0100, b...@theloosespoke.org.uk wrote: > > Hi Carsten, > > Ok, thanks - I'll do that. sorry for posting this against the wrong bug. so I'm closing this bug. Don't hesitate and report any new issues you found! Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745593: iceowl-extension: icedove does not start after update to 24.4.0-1~deb7u1
Hello zarg, On Wed, Apr 23, 2014 at 07:26:15AM +0100, zarg splendid wrote: >Seeing that a security update was recommended for Icedove, I >updated, via Synaptic, to version 24.4.0-1~deb7u1, including the >Iceowl Calendar extension (which is vital to me as I use it for >important work reminders such as domain renewals!). I didn't notice >at the time but the update removed the "Timezone Extension for >Lightning/Iceowl (mandatory)". The old extension calendar-timezones is now obsolete and no longer existes as Mozilla integrates the functionality into lightning (aka iceowl-extension inside Debian). >If I try to install the iceowl-extension then Synaptic marks >calendar- timezones for removal. If I try to install the >calendar-timezones Synaptic marks iceowl-extension for removal, but >these two packages are essential for each other. The behavior is correct, see above. >After the update, when I tried to run Icedove, I got the following error: > > icedove: relocation error: > .../components/Linux_x86_64-gcc3/libcalbasecomps.so: symbol > _ZN2js13CheckedUnwrapEP8JSObjectb, version xul24 not defined in file > libxul.so with link time reference This message means you have installed the Lightning extension from Mozilla. Lightning itself is incompatible to Icedove 24 because of internal liftime linking! Please use only the corrospondent Debian part 'iceowl-extension'. Remove the Lightning package and it should work. There is at least one bug in the BTS about this error. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729073 We added also a hint into the Wiki page. https://wiki.debian.org/Icedove#Icedove_and_the_Mozilla_Lightning_Extension >As I need to access the calendar for my work, is there any way to >revert to the previous version? (17.0.10-1~deb7u1) There is no need to do this. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745710: icedove: Can't send messages with imap
Hello, On Thu, Apr 24, 2014 at 10:51:25AM +0100, Z wrote: > > I can't remember when it started happening, but I think it might have been > when > I reinstalled debian recently, or when an update came through, before or > after. > I have several email accounts set up with icedove, and all the ones set up > with > IMAP will no longer send emails. just for the record, you don't send emails via IMAP. If you are talking about sending emails than you mean SMTP. Can you please make some logs about the activity if Icedove while trying to send emails? Without some logs it's impossible to say that's going wrong. https://wiki.debian.org/Icedove#Debugging_Icedove_Activity You have verified that the login data for SMTP are correct? If so how? The same account data works with another email client? This happen to if you start in safe-mode? > They say they are sending for a long time, and > use a lot of CPU. The POP3 accounts work fine. I tried setting up one of those > as IMAP, and it seemed to work too - but I don't want to try removing and re- > adding the other accounts, in case it doesn't work and it will take a lot of > time to add my labels, gpg etc - so I've had to use the webmail to send. You can and should make a copy of your current profile. cp -a ~/.icedove ~/.icedove-backup After this you can change what ever you want. If something is going wrong just delete the current working profile and copy your backup back. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745593: iceowl-extension: icedove does not start after update to 24.4.0-1~deb7u1
Hello tarin! On Thu, Apr 24, 2014 at 11:27:27PM +0200, tarin wrote: > I tryed different combinations and in the end I understood that the > problem is the ```lightning``` 2.6.4 plugin, so i disabled it. > > Then ```icedove``` starts correctly with the ```enigmail``` 1.6 plugin > enabled and ```lightning``` 2.6.4 plugin disabled. > > At the moment I can read/write e-mail but can't access to my calendar. As Mark wrote (and I also earlier in this Bug) you have to uninstall Lightning, not just disable it. Then install the package 'iceowl-extension'. All your calendars are reusable. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712381: run-mozilla.sh: Cannot execute [-safe-mode].
Hello Jonothan,
once again, please please do *not* top positing!
It's hard to read and find out in wich context you have problems or you
rely on..
Please answer in context to a previous specific part of the mail. This
helps massive to see there or that you answering. Delete all old parts
that are uninterested.
On Wed, Feb 26, 2014 at 06:59:05AM +, J Chetwynd wrote:
> $ /usr/lib/icedove/run-mozilla.sh -g [-safe-mode]
> /usr/lib/icedove/icedove-bin 2>&1 | tee /tmp/icedove-gdb-$(apt-cache show
> icedove | grep Version | awk '{ print $2 }')_$(date +%F_%T).log
>
> run-mozilla.sh: Cannot execute [-safe-mode].
If you look into man pages you will offen find such things that are
written inside the square brackets []. Thees are *additional* statements
or options.
So you can *add* to the command line above this additional option
'-safe-mode' to start Icedove in safe mode. If you want do so then you
have to exclude the square brackets. It then looks like:
> $ /usr/lib/icedove/run-mozilla.sh -g -safe-mode /usr/lib/
If you want start with the extensions enabled then remove the whole option
'-safe-mode' like this:
> $ /usr/lib/icedove/run-mozilla.sh -g /usr/lib/
> could not find obvious answer on search, sudo?
Icedove always runs in user context (otherwise it would not make any
sence). So there is never a needing for running with sudo rights.
> is it subject that creates top posting?
Yes. :)
Top-Posting is one of the horrible things that come with the "practical"
HTML Webmailers or by people that only knowing MS Outlook. But
top-posting makes it hard to find the relevant info in the right context
from reporters like you. ;) Imagin there longer mails out there like
your previous.
Here a short copy about top-posting and why don't to use it.
> A3: Please.
> Q3: Should I avoid top posting on mailing lists etc.?
>
> A2: Because, by reversing the order of a conversation, it leaves the
> reader without much context, and makes them read a message in an
> unnatural order.
> Q2: Why is top posting irritating?
>
> A1: It is the practice of putting your reply to a message before the
> quoted message, instead of after the (trimmed) message.
> Q1: What is top posting?
see also [1-3]
After reading this you will hopefully understand why we really dont like
top posting. If you read further on technical mailing lists you will
also see why we pratice the in context based answer.
[1] http://en.wikipedia.org/wiki/Posting_style#Top-posting
[2]
http://illuminated.co.uk/blog/2003/12/top-posting-vs-bottom-posting---or---microsoft-outlook-vs-the-right-thingtm.html
[3] http://mailformat.dan.info/quoting/top-posting.html
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712381: 17.0.10 on crashes wheezy
On Thu, Feb 27, 2014 at 09:05:54AM +, J Chetwynd wrote:
>
> >>So you have simple to use the other command line, you have could find it out
> by yourself by just testing it too.
>
> $ /usr/lib/icedove/run-mozilla.sh -g -safe-mode /usr/lib/icedove/icedove-bin
> 2>&1 | tee /tmp/icedove-gdb-$(apt-cache show icedove | grep Version | awk '{
> print $2 }')_$(date +%F_%T).log
>
> run-mozilla.sh: Cannot execute -safe-mode.
>
> $ /usr/lib/icedove/run-mozilla.sh -g /usr/lib/icedove/icedove-bin 2>&1 | tee
> /tmp/icedove-gdb-$(apt-cache show icedove | grep Version | awk '{ print $2
> }')_$(date +%F_%T).log
>
> .
>
> runs, icedove opens, and a few seconds later, OS hangs/crashes as described.
I still believe Icedove is not the real problem. There are now the
problem that the gdb logs to /tmp and this location is a tmpfs. So if
the system completely hangs we have no way to get into the /tmp
directory and grap the existings logfiles there.
You propably just can switch off your computer and the logs are also
gone by this.
You can try to log to another place like your home directory or an
external devices like a USB harddisk.
Simply change the '/tmp' part behind the tee command with a proper
location. For example with '$HOME' which points to
/home/[your_username]. After the next reboot you will find the logs
directly in your home directory.
The usage of a screen session is useless in your case, if your systems
hangs there is also nothing screen can help here.
But if your systems hangs completely there is more defect than Icedove
ever can be. Such a broken system on Debian stable I haven't seen for a
very long time.
In conversion about this bus I found no information which system with
which versions you are exactly running. Which sources.list you are
using? What about your free disk space?
I strongly suggest to use the tool 'reportbug' instead of a mail client,
reportbug appends all this needed infos (without the disk usage)
automatically to your bug report.
You wrote you using linux systems since the 90's, I think you can handle
this. The poor cummunication until now makes it hard to help you. Everey
mail from you is more a telegram than a good helpfull report.
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712381: SMTP freezing wheezy?
On Thu, Feb 27, 2014 at 12:33:38PM +, J Chetwynd wrote: > over a number of tests in the last day or two, it seems at least > likely that the hang is related to SMTP send password dialogue. Do you ever tried to set up a clean fresh profile? You can backup or old settings before, so you simply can switch back to your old profile. Just move the current Icedove profile directory out of the way. First stop Icedove if running, then do cd $HOME mv .icedove .icedove-old Now restart Icedove from the terminal. You have to re enter every setting of your profile. Don't copy back any thing from the old profile. Your current profile has something corrupted. I can't say much more that you can do, play around with the infos and tips from the wiki page, take a log into system log files. Make websearches with the suspicious things you found in the log files. Use the Mozilla Knowledge Base. http://kb.mozillazine.org/Knowledge_Base > as mentioned I changed the password, in order to access via webmail. > > > now when I start icedove as soon as the SMTP password dialogue > appears, > > system hangs. As I remember right previous bugreports with a crashing Icedove while sending messages the solution was to create a new profile. Probably the profile.js or the password store is broken. The wiki tells something about logging of internal functions and activity. Log them not to /tmp ! Use your home directory, so if it crashes again the old log file will be held. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712381: SMTP freezing wheezy?
Am 28.02.2014 10:25, schrieb J Chetwynd: > >>> mv .icedove .icedove-old > >>> Now restart Icedove from the terminal. You have to re enter every > setting of your profile. Don't copy back any thing from the old profile. > > tried this three times, system hangs, > top did not show anything... We can't help you before we know that's the problem. You need to get a log. Try to log what Icedove is doing with strace. Try to log what Icedove is inside doing. As you suspect that SMTP is the problem than you have to set NSPR_LOG_MODULES=SMTP:5 before starting Sorry, all this tips are written to the wiki. You maybe have to adopt the syntax to your needs. As I wrote, play around. I can't do this for you. There is no universal way to find the problem. > never actually got new profile created due to hang. You have only tried to set up one account? What provider? As your last mails come from outlook.com I wouldn't be surprised they handle SMTP by the M$ way. What happen if you do this with some other account (on another provider of course!)? > I suspect command migration/0 /1 due to brief but frequent 99%cpu > what is command migration, could it be relevant? Don't know that you mean here by command migration. Don't let me question every thing back, this is ineffective and frustrating not only me. Be precise by describing the things you are doing! -- Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712381: SMTP freezing wheezy?
Am 28.02.2014 19:22, schrieb J Chetwynd: > >>> NSPR_LOG_MODULES=SMTP:5 > > where is this to be placed? That's described on the wiki page. :) >>> migration > is responsible for moving threads between CPUs. > as nothing much is going on, it seems strange that > there are frequent short hangs when 99% CPU on top. No, you mean something like multi threading. The load balancing between the CPU cores is automatically done by the CPU (if the application is written for multi threading, that are all normal programs done). Take a look into the process list with htop for example, this has several options to display the current processes. >>> What happen if you do this with some other account (on another provider of >>> course!)? > > afaik I don't have access to another provider. Take a look for some free mail provider that supports IMAP secure and SMTP secure at least. Your ISP gives you "only" the way to the Internet, interesting that BT can't provide email by there self. > my ISP is BT business broadband and they are the mail provider and > they do use outlook. Before outlook.com arises Microsoft provided hotmail.com. This was ever only a web application, it was simply not usable with Thunderbird/Icedove or other mail clients. With this experience I would say, it isn't working better with outlook.com. If you don't care much about that your mails are visible for the provider you can take a look at Google Mail, GMX or Yahoo Mail for example. But there hundreds of free mail providers out there. Mostly the limit the amount of mails you can send or receive a day. But for testing it is o.k. to create a simple account on one of the providers. > my only other current option is a complete back-up and re-install!! That would be option B, maybe your system is a little bit miss configured, the fastest way to fix *can* be a complete reinstall. -- Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712381: what to do?
Hello! Am 01.03.2014 17:32, schrieb jonathan chetwynd: > Carsten, > > many thanks for your support, > I do feel that I tried my best. Sure, bug catching isn't easy. And as we can see, software isn't perfect. > I eventually felt driven to install Claws Mail > having used icedove for quite some years, could it be five to ten? > > Claws has performed fine, no crashes no problems at all. > of course this is only the second email, so Claws is fine. I assume you are using the "old" mail account that comes with your ISP account? If so I would suggest the following. Test all possibilities like IMAP vs IMAPs and SMTP vs SMTPs. If Claws is working without issues than Thunderbird/Icedove will be the problem in the end. :-( Please open a bug at the Mozilla bugtracker with good infos around the issue and how it can reproduce, like which distribution you use and what settings you have used, what things you have tried to get a log. Be as much precise as you can! Better to place more infos while opening the bug report there than the developers has to ask every thing back. Topic would be something like "Icedove/Thunderbird isn't working with outlook.com over SMTP" You find the Mozilla bugtracker at https://bugzilla.mozilla.org/ If your bug is accepted there please give a feedback with a URL to the bugreport upstream. We can add the URI here and the BTS will inform us if the status is changing upstream. > of course it may be that no one else has this issue, > but it seems unsatisfactory to just abandon. I think no one else had this issue with Icedove and outlook.com before. On the other side no one who is using Linux and free software will probably use outlook.com as mail provider. ;) -- Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#428554: Can't reproduce this problem
Hello, On Mon, Sep 24, 2007 at 04:35:05PM +1000, Ted Percival wrote: > Andrés Roldán wrote: > >Hi. > >I am unable to reproduce this problem. I have icedove 2.0.0.4.dfsg1-2 > >installed and I run prelink daily without problems. > > Today I took another look and it works fine, although I have upgraded > some packages since my first message. > > These are the packages that have been upgraded since: > libatk1.0-0 from 1.18.0-2 to 1.20.0-1 > libc6 from 2.6.1-3 to 2.6.1-5 > libpango1.0-0 from 1.18.1-1 to 1.18.2-1 > > I downgraded them to the original versions and ran `prelink --all > -mR` but icedove continued to work, so I guess this is now > unreproducible for me too. > > I'll leave the packages at these versions and see if it comes back > after I've restarted, but I suspect the old error was really because > of a mismatch between some installed library and what was already > loaded into memory. what about closing this bug? The reported Icedove version out of the official repos for quite some times and notheing else happen to this report quite over 6 years. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#585422: calendar-google-provider: Duplicates (and connects) added items between multiple Google calendars
Hello Jakub, On Thu, Jun 10, 2010 at 03:01:17PM +0200, Jakub Lucký wrote: > Package: calendar-google-provider > Version: 1.0~b1+dfsg-4 > Severity: normal > > Hi, I am experiencing pretty weird behaviour in Iceowl in connection > with calendar-google-provider. When I add some events, IceOwl > duplicates them in more of my google calendars. > > It's difficult to explain, so I am providing two screenshots. One from > IceOwl, one from calendar.google.com > > Those duplicates were added only once (so no adding duplication) (the > one with alarm through calendar.google.com, the one without alarm > through IceOwl) and they are connected together. When I delete one, > both of then get deleted. This is pretty annoying, because yesterday > all my events were duplicated 6 times (for each googlecalendar I have) your reported version is now quite older. To probably get that bug solved I'd like to ask what about your bug report and current version of c-g-p? This issue is still present? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#428554: Can't reproduce this problem
Hello Geoffrey, Am 03.03.2014 23:59, schrieb Geoffrey Thomas: Hi Carsten, There are a number of bugs against prelink that are outdated or irrelevant or fixed by the much-newer version I uploaded last week. I'm planning on systematically going through all of them and verifying whether there is any validity in them, although this may not be for a few weekends. I will probably end up closing this bug when that happens. I don't want to force something. I came to this bug over the Debian website for bugs older then three years. As you wrote you will go through all the bugs I can say I know that this means, I've done this for Icedove quite a year ago. First I searched for bugs that have reported versions older then the current versions inside the Debian repositories. This has taken a long time. ;) So now we can take a more detailed look at the current bugs. Thanks and wishes the best, Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#698041: iceowl-extension: Edit problems with tasks on yahoo calendar
Hello Antoon, On Sun, Jan 13, 2013 at 11:46:48AM +0100, Antoon Pardon wrote: > Package: iceowl-extension > Version: 10.0.11-1 > Severity: normal > > Dear Maintainer, > *** Please consider answering these questions, where appropriate *** > >* What led up to the situation? > > I needed to adapt a task on my yahoo calendar. > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > I double clicked on the task in question. An edit window > for the task opened. I changed a few things and then > I clicked on the save and close item. > >* What was the outcome of this action? > > Nothing. The edit window remained open. None of the > menu/icon options to save or close the edit window > within the edit-window seemed to work. I was able > to close the window through the taskbar icon but > all adaptations were lost. > >* What outcome did you expect instead? > > I would hav expected my adaptations to be saved > and the edit-window to close you are sure you have included the remote calendar with rw permissions? What is the JS error console showing? You can open that with Strg+Shift+J. Maybe you will see more if you run Icedove from a terminal window. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741245: [hppa][patch] icedove : FTBFS on hppa, patch attached.
Hello Helge, On Mon, Mar 10, 2014 at 12:23:52PM +0100, Helge Deller wrote: > Package: icedove > Version: 24.3.0-2 > Severity: important > Tags: patch > > icedove fails to build on the hppa (parisc) architecture. > Fail-Log is here: > http://buildd.debian-ports.org/status/package.php?p=icedove&suite=sid > > The attached patch fixes it. > IMPORTANT: Please apply it to the mozilla/ directory inside iceweasel. great to see patches. Thanks for contributing. I add pkg-mozilla-maintainer as well to forward your suggests to other Debian Mozilla Maintainers as you say your patch needs to apply to the Iceweasel build as well. > By the way, the same problem happened in iceweasel as well. > The patch is the same, bugzilla for iceweasel is: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737332 > > Thanks, > Helge > --- iceweasel-24.2.0esr.orig/js/src/gc/RootMarking.cpp > +++ iceweasel-24.2.0esr/js/src/gc/RootMarking.cpp > @@ -320,7 +320,7 @@ MarkConservativeStackRoots(JSTracer *trc > > uintptr_t *stackMin, *stackEnd; > #if JS_STACK_GROWTH_DIRECTION > 0 > -stackMin = rt->nativeStackBase; > +stackMin = reinterpret_cast(rt->nativeStackBase); This looks probably o.k. to me. But I haven't tested it for amd64/i386. Should work. > stackEnd = cgcd->nativeStackTop; > #else > stackMin = cgcd->nativeStackTop + 1; > diff -up iceweasel-24.2.0esr/js/src/jsapi.cpp.org > iceweasel-24.2.0esr/js/src/jsapi.cpp > --- iceweasel-24.2.0esr/js/src/jsapi.cpp.org 2014-02-01 19:22:54.488625002 > + > +++ iceweasel-24.2.0esr/js/src/jsapi.cpp 2014-01-31 13:28:30.309882024 > + > @@ -865,7 +865,7 @@ JSRuntime::JSRuntime(JSUseHelperThreads > PodZero(&atomState); > > #if JS_STACK_GROWTH_DIRECTION > 0 > -nativeStackLimit = UINTPTR_MAX; > +// nativeStackLimit = UINTPTR_MAX; Can you point a little bit why this work? I believe this change will break other platforms so we have to put this into a #ifdef #endif statement. > #endif > } > Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#746348: icedove: openpgp failed without error message after update to 24.4.0-1~deb7 version
Hello Francois, On Tue, Apr 29, 2014 at 10:57:05AM +0200, Francois Jay wrote: > Dear Maintainer, > > - icedove is running > - update to 24.4.0-1~deb7 is installing but icedove is NOT restart > - i sent a signed and crypted mail with enigmail 1.6 module > => the mail is sent in clear without signs and no warning/error message appear > - everything is ok after close/open icedove ... as you described you didn't restart Icedove after the update I say this is no bug. What is happened? 1. You started Icedove and Icedove collected all the extensions and the binarys they use. Like the enigmail extension. 2. Then you started the update, this update replaces all files with new files, all the information that was collected earlier are now wrong at this moment. 3. The update is now finished and you try to send an encrypted messages. Icedove believes that enigmail with version x is placed in the extension folder, but you (or the update) replaced this version to y. But Icedove doesn't know anything about that so the encryption will fail because some system calls have changed. 4. If you restart Icedove will again collecting all extension and the settings of these. Because now the binary calls and the files are correct to the collected infos the encryption will work. So I can't see a miss function here. If you argument that Icedove has to be restarted then I say yes, but the Debian policy did allow that. We never restart programs that running in a user context, even if we update a program because we can't know what the user is doing. Try to image what happens if you work on a presentation and we just shut down Libroffice because we update to a newer version! So it's allways up to the user to restart a program after a update. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692984: Expected upload of sogo-connector
Hello Boris, Am 30.04.2014 12:41, schrieb Boris Barbour: > I'm interested in obtaining the sogo-connector, as this seems to be the > only way to sync contacts with owncloud. I'd prefer to get it through > the debian repositories. The messages above suggest that it could be (or > has been) uploaded, which is good news. When might we expect it to appear? thanks for your interests! I don't know then the FTP Team will allow the upload of the package, so sorry, I can't say something promising right now. You can rebuild the package by yourself using the current repository which will be found on https://github.com/tijuca/sogo-connector You will probably need a sid chroot to build the package, right know I always used git-pbuilder and doesn't have cared about backports or so. But that should not be a big problem to created a wheezy-backport package too. -- Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#746640: icedove: Debian Bug report logs - #724688 not fixed in Deb stable repository
merge 746640 745593 thanks Hello Peter, On Fri, May 02, 2014 at 10:14:15AM +0200, Peter Mueller wrote: > Package: icedove > Version: 24.4.0-1~deb7u1 > Severity: normal > > Dear Maintainer, > *** Please consider answering these questions, where appropriate *** > >* What led up to the situation? > > The lighning calendar does not work with icedove 24.4.0, Deb wheezy. > >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? > > Propagate the already available solution from the unstable to the stable > icedove repository. we did in sid/testing nothing different saying like for stable-security. There is currently in all Icedove versions a symbol mismatching between the core Icedove itself and the original Lightning extension. We working on that. The symbol mismatch did not happen with the equivalent Debian package for Lightning -> 'iceowl-extension'. So remove Lightning and please use iceowl-extension instead. Christoph is preparing a new upload for s-s with a root mail for announcing what to do. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747183: icedove: Impossible to re-install icedove: libffi5 dependency cannot be solved.
Hello, On Tue, May 06, 2014 at 10:45:40AM +0200, ICEDOVE wrote: > Package: icedove > Version: 24.4.0-1 > Severity: important > File: icedove > > Dear Maintainer, > > icedove was removed, from my testing debian, automatically this morning, > the libffi5 library is no more accessible. Icedove on testing/jessie depends on libffi6 not on libffi5 as visible on the Debian package site [1] and via apt-cache $ apt-cache show icedove | grep libffi Depends: ... libffi6 (>= 3.0.4) ... or via your mail to the BTS. > Versions of packages icedove depends on: > ... > ii libffi6 3.1~rc1+r3.0.13-12 So you may have some pinning done in your sources? [1] https://packages.debian.org/jessie/icedove Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747183: icedove: Impossible to re-install icedove: libffi5 dependency cannot be solved.
Hello Jean-Luc, please do not top-post! And please use "Reply All" so the BTS is updated as well. > Hi, > > Thank you for tour answer. > > The issue is the following: > > apt-cache show :icedove depends on libffi6 > > apt-get install icedove depends on libffi5 no, the package icedove does not depend on libffi5. It depends on libffi6 like many other packages in testing. You don't provide a full log, so it's impossible to see what the real problem is. I can reinstall the package, or even remove and install afterwards without problems. > carsten@x201s:~ $ cat /etc/debian_version > jessie/sid > carsten@x201s:~ sudo apt-get install --reinstall icedove > Reading package lists... Done > Building dependency tree > Reading state information... Done > 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 452 not > upgraded. > Need to get 0 B/22.0 MB of archives. > After this operation, 0 B of additional disk space will be used. > (Reading database ... 292980 files and directories currently installed.) > Preparing to unpack .../icedove_24.4.0-1_amd64.deb ... > Unpacking icedove (24.4.0-1) over (24.4.0-1) ... > Processing triggers for hicolor-icon-theme (0.13-1) ... > Processing triggers for desktop-file-utils (0.22-1) ... > Processing triggers for gnome-menus (3.8.0-2) ... > Processing triggers for mime-support (3.54) ... > Processing triggers for menu (2.1.46) ... > Processing triggers for man-db (2.6.7.1-1) ... > Setting up icedove (24.4.0-1) ... > Processing triggers for menu (2.1.46) ... > carsten@x201s:~ $ sudo apt-get remove icedove > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following packages will be REMOVED: > icedove icedove-dispmua icedove-l10n-de iceowl-extension > xul-ext-compactheader xul-ext-dispmua xul-ext-gcontactsync > 0 upgraded, 0 newly installed, 7 to remove and 452 not upgraded. > After this operation, 64.9 MB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 292979 files and directories currently installed.) > Removing icedove-l10n-de (1:24.3.0-1) ... > Removing iceowl-extension (24.4.0-1) ... > Removing icedove-dispmua (1.6.9-1) ... > Removing xul-ext-compactheader (2.0.8-1) ... > Removing xul-ext-dispmua (1.6.9-1) ... > Removing xul-ext-gcontactsync (0.3.6-1) ... > Removing icedove (24.4.0-1) ... > Processing triggers for man-db (2.6.7.1-1) ... > Processing triggers for menu (2.1.46) ... > Processing triggers for desktop-file-utils (0.22-1) ... > Processing triggers for gnome-menus (3.8.0-2) ... > Processing triggers for mime-support (3.54) ... > Processing triggers for hicolor-icon-theme (0.13-1) ... > carsten@x201s:~ $ sudo apt-get install icedove icedove-dispmua > icedove-l10n-de iceowl-extension xul-ext-compactheader xul-ext-dispmua > xul-ext-gcontactsync > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following NEW packages will be installed: > icedove icedove-dispmua icedove-l10n-de iceowl-extension > xul-ext-compactheader xul-ext-dispmua xul-ext-gcontactsync > 0 upgraded, 7 newly installed, 0 to remove and 452 not upgraded. > Need to get 0 B/27.1 MB of archives. > After this operation, 64.9 MB of additional disk space will be used. > Selecting previously unselected package icedove. > (Reading database ... 292297 files and directories currently installed.) > Preparing to unpack .../icedove_24.4.0-1_amd64.deb ... > Unpacking icedove (24.4.0-1) ... > ... > Setting up icedove (24.4.0-1) ... > Setting up icedove-l10n-de (1:24.3.0-1) ... > Setting up iceowl-extension (24.4.0-1) ... > Setting up xul-ext-compactheader (2.0.8-1) ... > Setting up xul-ext-dispmua (1.6.9-1) ... > Setting up xul-ext-gcontactsync (0.3.6-1) ... > Setting up icedove-dispmua (1.6.9-1) ... > Processing triggers for menu (2.1.46) ... You can search for dependencies on libffi5 by the following command: apt-cache rdepends libffi5 Check the same command for libffi6 dependencies, the list will be much longer. ;) > I think the package icedove still has a problem. I say no. You have a problem with pinned packages or packages that are installed by hand or from a source that isn't working by the Debian rules for packaging. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743748: Folders are not listed, blank folder pane
Hello Mordur, On Sat, Apr 05, 2014 at 06:17:55PM -0400, Mordur Ingolfsson wrote: > The software seems to be working (filters, calendars etc.) except for > the folder pane and the folder list in the subscriptions control panel > are completely blank. The folder pane is gray like the background of > tabs and the top bar and when I click on "manage folder subscriptions, > that seems to work except no folders are displayed. > > The main pane to the right of the folder pane displays the settings pane > for the default (top) account of the 12 accounts that are set up on the > Icedove client. do you have any addons directly from Mozilla installed? What happend if you disabled them? Or if you start in safe-mode? > The accounts are all still there, settings, filters and all, everything > except for the folders themselves.. What happened if you backup your profile and restart Icedove? Is Icedove correctly crteating a new profile in $HOME/.icedove? I found a bug in my personal builds for Icedove 28 with a missspelled profile directory, Icedove isn't accepting the profile in $HOME/.icedove and instead need a directory $HOME/icdove. Can you please verify that? My latest version works probably if I renamed '.icedove' to '.icdove' ! Please ensure you have correct backup if you doing something like that! > This bug renders the software nearly useless. > > This is what I get when I start Icedove from terminal: These kind of logs are mostly useless. You will find proper information if you follow https://wiki.debian.org/Icedove#Debugging_Icedove_Activity But I think it's more a problem with your addons. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#748746: icedove-dev: pkg-config refers to non-existent library mozjs
Hello Ximin, On Tue, May 27, 2014 at 06:18:16PM +0100, Ximin Luo wrote: > Hi, I'm bumping the severity because this is preventing me from > releasing a newer version of mozilla-gnome-keyring, and users are now > noticing. that's o.k. for now I think. Christoph is preparing an upload of the current version 30.0b1 for Sid. Because of this we didn't have worked on a 24.5.0-3 für Sid/Testing. For stable-security it is much the same, Christoph will change your issue and others from Jonas Smedegard with the next 24.6.0 that will be released in 14 days on June 10, 2014. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749037: icedove: Regression of bug#730450: Same problem with Debian 7.5 stable, icedove=24.5.0-1~deb7u1 and lightning 2.6.5
tag 749037 + wheezy pending thanks Hello Tormen, On Fri, May 23, 2014 at 12:14:09PM +0200, Tormen wrote: > Package: icedove > Version: 24.5.0-1~deb7u1 > Severity: important > > Hi, > > I failed "reopening" the archived Debian bug #730450: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730450 > > Which I tried because I am sure (hoping I did not miss anything) that > it's the exact same problem that occurs to me for a version that the BTS > version tree shows green. the BTS is right, and you are also. The BTS shows fixed versions for testing and sid. You run into this old issue with the current version in wheezy, which isn't tracked in the named bugnumber. Do upload restrictions to stable-security this issue will be fixed with the upcomming version 24.6.0 of Icedove. You can work around this issue if you use 'iceowl-extension', which is the Debian renamed Lightning package. Unfortunately there are no l10n packages for iceowl-extension in stable-security. But you can use the packages for iceowl-l10n from unstable/testing. https://packages.debian.org/source/unstable/iceowl-l10n We preparing the l10n files for wheezy-backports. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646672: confirmation email not sent
Hello Daniel, On Sat, Nov 12, 2011 at 08:11:30PM +0100, Guido Günther wrote: > Hi Daniel, > On Wed, Oct 26, 2011 at 10:46:25AM +0800, Daniel Pocock wrote: > > Package: iceowl-extension > > Version: 1.0~b1+dfsg2-2+squeeze2 > > > > > > User accepts an event invitation > > > > The SMTP server is temporarily down > > > > Icedove displays a popup to inform the user that the confirmation could > > not be sent to the meeting organiser > > > > However, the event is stored in the calendar successfully. > > > > Icedove no longer offers an option to accept the event, consequently, > > there is no option to retry sending the confirmation. > > > > Possible fixes: > > > > - add a `Retry' button to the error popup, and if the user chooses to > > cancel, the invite should not be sent to the calendar - it should remain > > as a pending invitation and the user must try and accept it again > > > > - the confirmation message should be created in the Outbox and Icedove > > should keep trying to send the confirmation message until it > > successfully contacts an SMTP server > This looks like an upstream issue. We appreciate any help in forwarding > these kind of issues to bugzilla.mozilla.org. You can also recheck with > 8.0~rc4-2. do you have found some time to recheck this issue with current versions? We far away from squeeze and probably this issue is gone? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#644140: Windows-32 Version 3.1 of thunderbird is also affected
Hello Andreas, On Tue, Nov 22, 2011 at 07:09:34AM +0100, Andreas Glaeser wrote: > This bug can also be found in the 32 bit windows version 3.1 of Thunderbird. this issue is still around? If yes than it is definitely an upstream bug. Can you provide a URL to a Mozilla Bugzilla entry or willing to open a upstream bug there? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#703866: icedove: routine javascript exception in chrome://messenger/content/folderPane.js line 2477
Hello DAniel, On Sun, Mar 24, 2013 at 11:46:54PM -0400, Daniel Kahn Gillmor wrote: > Package: icedove > Version: 10.0.12-1 > Severity: normal > > I created a completely new icedove 10.0.12 installation on a fresh wheezy > installation. > > I set up a simple imap account, but did not fetch mail from it yet. > > If i open the "error console" from the "Tools" menu, and then just mouse > over anywhere in the main ui, i get the following message spewed > repeatedly to the error console: > > Error: [Exception... "Component returned failure code: 0x80004005 > (NS_ERROR_FAILURE) [nsIMsgFolder.getStringProperty]" nsresult: "0x80004005 > (NS_ERROR_FAILURE)" location: "JS frame :: > chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2475" > data: no] > Source File: chrome://messenger/content/folderPane.js > Line: 2477 > > This does not happen with icedove 17.0.4 from experimental. as you wrote this issue did not happen with a version >= 17.0.4 I would assume this issue is gone. Is it o.k. for you to close this report because we have no version 10 nor 17 in stable-security anymore? Regards Carsten? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722900: mozilla docs
Hello Daniel, On Fri, May 02, 2014 at 08:17:28PM +0200, Daniel Pocock wrote: > I had a look at this too: > > http://kb.mozillazine.org/Network.protocol-handler.app.%28protocol%29 > > > It really isn't clear how to enable "tel" URIs either using a command > defined within icedove or using the desktop/gnome settings. I'm not a expert in this part, especially in protocol handling. But if we implement this we have to take care for all the none Gnome users. It seems to me that there is on extension that will do the most of the integration inside Thunderbird/Icedove. https://addons.mozilla.org/de/thunderbird/addon/telify/ I found a thread on the Ubunto forum that shows how to integrate the Jitsi program to use SIP numbers. http://ubuntuforums.org/showthread.php?t=2181012 For me it's unclear how to define the standard application for SIP handling for the user without manuall edit some files inside the system. But as you are a "enhanced" user you can test the steps from the thread in the Ubuntu forum. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750153: icedove-l10n-*: not installable in sid, needs migration to icedove 30
tags 750153 pending thanks Hello Ralf, On Mon, Jun 02, 2014 at 08:41:25AM +0200, Ralf Treinen wrote: > Hello, all the icedove-l10n-* packages depending on icedove (<25) are no > longer installable in sid, now that we have icedove 30.0~b1-1 in sid. > This dependency is hard-wired in the debian/control file. yes, that's correct. We do this version scaping since several time. I prepared the l10n packages for version 30 in my staging repository and Christoph will keep it shortly. https://github.com/tijuca/icedove-l10n Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750201: icedove: this version breaks calendar-exchange-provider
reassign 750201 calendar-exchange-provider thanks Hello Eric, On Mon, Jun 02, 2014 at 02:55:46PM +0200, Eric Valette wrote: > After upgrading, I can no more access to my exchange calendar. The last > version of calendar-exchange-provider is 3.2.0-beta77 + in git and > apparently development it is no more developped (as of 8 may). > > It has been tested sucessfully up to 30.0.a2 and maybe it is just a matter > of updating the install.rdf. I think so. Look for minVersion and maxversion in the Thunderbird section. http://anonscm.debian.org/gitweb/?p=collab-maint/calendar-exchange-provider.git;a=blob;f=install.rdf;h=3f3082a2a1562ca79e4d51d1b1bb1de53bc2683d;hb=70432dc8c2fdd6fb310816398f4b5f38a5a5b89e This issue has to be solved inside the install.rdf from the plugin package. > In any case it should conflict with the version in unstable 3.2.0-beta53 > so that corporate users may not upgrade until a solution is found. No need for doing anything here for Icedove. I reassign your bug to the calendar-exchange-provider package. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750201: My repackaged version 3.2.0-b77+ of git works with 24.5.0 but not with 30.0b
On Mon, Jun 02, 2014 at 04:25:28PM +0200, VALETTE Eric OLNC/OLPS wrote: > just tested to make sure I did not broke something unrelated. So we need > to find a version that will work with icedove 30. There can we see what you have changed, there is the source to find? Once again, it's not a problem of Icedove, the problem are the prerequisites and depends of this plugin. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750201: icedove: this version breaks calendar-exchange-provider
Uhh html at it's finest ... On Mon, Jun 02, 2014 at 03:29:40PM +0200, VALETTE Eric OLNC/OLPS wrote: > Not sure I understand what you mean. I downloaded the latests > version of the calendar-exchange-provider plugin from git, modified > the install.rdf from the xpi and rebuild the xpi and installed it > with icedove 30.0 and iceowl-extension 30.0. Unfortunately it does > not work (no additional prompt for password meaning OWA server is > not even contactedcontacted) so unless there are specific debian > problem with the packaging like for lightning vsiceowl-extension, > I'm affraid no version of the calendar-exchange-provider will work > with icedove 30.0. I hope i'm wrong because I ( and most linux users > in our company) heavily depend on it I don't know the interna of this plugin, but there will be a reason why the minVersion and the maxVersion is not greater 26 as far as I have seen. So I don't think it's wise to use a Icedove beta version and try to get the plugin work with it. Please ask the maintainer of calendar-exchange-provider if there are possibilities to get it work with Icedove 30 or greater. If you need this plugin please use the version 24.x of Icedove, no one will give you support for beta version of Icedove. Once Thunderbird 31 will alive (it's the next long supported version) there will be surly an updated version of this plugin that will work with this. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750201: My repackaged version 3.2.0-b77+ of git works with 24.5.0 but not with 30.0b
On Mon, Jun 02, 2014 at 05:09:52PM +0200, VALETTE Eric OLNC/OLPS wrote: > But if there was a conflict I would not upgrade and break people config. Do you have log there we can see what is happen? I can't really believe that there is something broken. Version dependencies are solved by the package manager, so if calendar-exchange-provider is depending on iceowl-extension it's quite normal that i want work if the version dependency can't be solved. By the way, we are talking about packages in unstable. ;) It naturally possible that something is broken here. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750201: My repackaged version 3.2.0-b77+ of git works with 24.5.0 but not with 30.0b
On Mon, Jun 02, 2014 at 05:31:32PM +0200, VALETTE Eric OLNC/OLPS wrote: > It is broken : I get no prompt for passwd, exchange calendar is read > only and no appointment are shown. It not my setup as downgrading > icedove/iceowl make it work immediately either with my own cooked > version of the pluggin or the blessed debian one. For testing you will > need a exchange server with OWA enabled I'm affraid. You have to differ between wrong packaging and missfunctions inside the software. I read your bug report as "The packaging is broken." So as you not showing a log from the upgrade I can't assume that the packaging is broken in Icedove. > Usually with major TB version, all debian maintained packages packages > were -re-packaged at the same time and yes there are dependencies on > iceowl-extension and exchange calendar. Goggling will prove that easilly. No, it's a work in progress and that's why we start right now to upload 30.0~b1 to unstable. We haven't got the time to this with 28.0~b1 oder 29.0~b1. But we have done the same with 24.0~b3 several months ago. > Beta version of icedove and iceweasel traditionally did go to > experimental first. No, there is no rule to upload betas to experimental first. This would be a "yes" for first versions into Debian or alpha versions. https://wiki.debian.org/DebianReleases#Current_Releases.2FRepositories > There there is no PB. Breaking people mailer or > calendaring solution by uploading on unstable directly is something new. Also here No! It's unstable! There may things be broken. And when we should start do you think? We need unstable to get most of the testing people. There are more Mozilla extension that need a deeper testing before they could go down to testing or later to stable-security, like Enigmail for example. Don't blame us, the warnings are everythere to read about the side effects that unstable brings. And there is a *big* info on the Github site ... "NO LONGER MAINTAINED..." Sorry, but this aren't good news and I strongly believe this extension is then end of live for Icedove > 24. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#751077: icedove: program locks up when attempting attachment, gdb no help
Hello Arthur, On Tue, Jun 10, 2014 at 02:04:13PM +0930, Arthur Marsh wrote: >* What led up to the situation? > > attempting to attach a PDF file to an email. Do you have disabled all the plugins and/or started in save-mode? There your attachement was laying? Local filesystem, usb storage or a net resource? Do you have checked the permissions of this file? Is this file currupted? > Reading symbols from icedove...(no debugging symbols found)...done. > (gdb) run At this point there can't be more output if you trying to run the "normal" Icedove package. Do you have installed the -dbg package? https://wiki.debian.org/Icedove#Debugging But I think the debugger will not help here, I assume Icedove is not crashing. So you please have to take a look into the JS console (hit Ctrl + SHift + J). Further more you can debug that Icedove is doing inside. https://wiki.debian.org/Icedove#Debugging_Icedove_Activity Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#751077: icedove: program locks up when attempting attachment, gdb no help
On Tue, Jun 10, 2014 at 04:00:32PM +0930, Arthur Marsh wrote:
> Somehow the instructions didn't help much:
>
> /usr/lib/icedove/run-mozilla.sh -g -safe-mode
> /usr/lib/icedove/icedove-bin 2>&1 | tee /tmp/icedove-gdb-$(apt-cache
> show icedove | grep Version | awk '{ print $2 }')_$(date +%F_%T).log
>
> run-mozilla.sh: Cannot execute -safe-mode.
There it seems Mozilla has changed the possible options for the wraper
script, will change the wiki entry.
> cat /tmp/icedove-gdb-24.5.0-2
[snip]
> [Thread 0x92cffb40 (LWP 13881) exited]
> [Thread 0x90cfbb40 (LWP 13880) exited]
> [New Thread 0x90cfbb40 (LWP 13882)]
> [Thread 0x90cfbb40 (LWP 13882) exited]
> Cannot find user-level thread for LWP 13856: generic error
> (gdb) quit
> A debugging session is active.
I cant see a segfault here. In the other mail there is a segfault
visible. We need a backtrace from it. So reproduce it and create a
backtrace within the gdb.
> >But I think the debugger will not help here, I assume Icedove is not
> >crashing. So you please have to take a look into the JS console
> >(hit Ctrl + SHift + J).
> >Further more you can debug that Icedove is doing inside.
>
> That didn't work.
Very informative ...
I'm willing to help, but it's up to you to append any information as
much as you can. So please write some more things what you have done and
what do you not have done.
Did this issue happen with a fresh clean profile? Working other
documents as an attachment? What about other pdf files?
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#751077: icedove: program locks up when attempting attachment, gdb no help
On Tue, Jun 10, 2014 at 09:53:03PM +0930, Arthur Marsh wrote: > trying to attach a file to an outbound mail causes a segfault outside of gdb > and no segfault but a lockup from within gdb. > > strace of icedove when called outside of gdb ends with the following: [snip] Unfortunately there is nothing significant to see here. Maybe the binary 'icedove' or someone else is corrupted. Can you ples check the installation with debsums? $ debsums icedove You have probably to install the package 'debsums' first! If the output isn't allway 'ok' then please reinstall the icedove package. Please remove the old package from the local apt cache $ sudo rm /var/cache/apt/archives/icedove_*.deb $ sudo apt-get update $ sudo apt-get install --reinstall icedove > NSPR_LOG_MODULES=MCD:5 NSPR_LOG_FILE=~/icedove-mcd.log icedove > > ended up with a zero length log file Is there any output on the console if you try to run that comman line? Maybe again Mozilla has changed variables here. And have you tried to backup your current profile and start with a fresh profile if this all doesn't work? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747546: Any plans getting fix for bug#747546 into next stable release?
Hello Jonas, Am 12.06.2014 14:58, schrieb Jonas Smedegaard: > That is arguably of no use, however, if not then also fixed in stable. > > Any plans on doing that? yes of course. It's already prepared [1] for the next version 24.6.0 of Icedove. The version 24.6.0 for the Thunderbird package was released an Tuesday this week, as far as I know Christoph will prepare the upload for stable-security this weekend. [1] http://anonscm.debian.org/gitweb/?p=pkg-mozilla/icedove.git;a=commit;h=ddd0d7e761e24b24873cf2ef6dda70692a5841d3 -- Regards Carsten signature.asc Description: OpenPGP digital signature
Bug#747532: Any plans getting fix for bug#747532 into next stable release?
Hello Jonas, Am 12.06.2014 14:49, schrieb Jonas Smedegaard: > That is arguably of no use, however, if not then also fixed in stable. > > Any plans on doing that? same here too of course [1]. [1] http://anonscm.debian.org/gitweb/?p=pkg-mozilla/icedove.git;a=commit;h=dfbb25e2b7dcf10e318e64c717c08732db80bfd7 -- Regards Carsten signature.asc Description: OpenPGP digital signature
Bug#751466: icedove: Frontend looks ugly + Errors using Conversations
Hello Patrick, Am 13.06.2014 10:51, schrieb Patrick Winnertz: > since the update to 30.0 the "Write Mail" window looks quite ugly hmm, this isn't a bug I would say. This the "new" look & feel Mozilla want to use. The same composing window looks in Windows 8 exact the same. > and on the cmd I'll get several errors of this kind: >> The MsgHdrToMimeMessage callback threw an exception: TypeError: >> MailServices.headerParser.makeFullAddress is not a function We have several messages like that on the command line, they all come from the changes Mozilla is doing and doesn't correct clean up the wrappers for the transitions afterwards. I don't now exactly there this message is coming from, is this from JS code or from the C++ source. Anyway, this has to be fixed upstream. There are surely more than one bug opened up in the Bugzilla for issues like that. > In addition to that the plugin "Thunderbird Conversations" fails to > get access to the contact database and thus all address fields are empty. There seems to be no Debian package for this plugin. I think you should use debugging options [1] to get more informations around this plugin and report this issue on the Website for this plugin [2]. [1] https://github.com/protz/GMail-Conversation-View/wiki/Debugging-Conversations [2] https://github.com/protz/GMail-Conversation-View/issues -- Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747183: icedove: Impossible to re-install icedove: libffi5 dependency cannot be solved.
Hello, ones again, please do not top-post! And please remove all lines of your answering mail that do not interact with the context of your answer. That's a bad attitude to do not. And even GMail is usable in plain text mode! On Wed, May 07, 2014 at 05:47:26PM +0200, Jean-Luc Rossiny wrote: > Hello, > > Is there a similarity with the bug #742897? I can't see until now any parallelism to this bug. You wrote that icedove isn't installable any longer on testing depended on removed libffi5, the bugnumber you relay on is about a segfault in icedove in gdm3. You probably far away from a Icedove segfault I think. > I am using gdm3 too. I'm using Gnome3 and KDE with Wheezy and Jessie on various PCs, I never had this problems. And until now you are the only person that reported such problems, that makes me more believe that the real issue is on your configuration of your pc. Without any logs it doesn't make sense to talk about possibilities that this issue is triggering, so please check your configuration and append a log and tell us more about your configuration. Without that and more useful informations I will close this report in the near time. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747183: Icedove installation
Hello, On Thu, May 08, 2014 at 06:52:29AM +0200, Jean-Luc Rossiny wrote: > apt-get install icedove icedove-dispmua icedove-l10n-fr iceowl-extension > xul-ext-compactheader xul-ext-dispmua xul-ext-gcontactsync [...] > Les paquets suivants contiennent des dépendances non satisfaites : > icedove : Dépend: libffi5 (>= 3.0.4) mais il n'est pas installable We come closer. So what's your settings for apt? Which sources you use? What is apt telling about possible installation candidates? Have you tried to minimize your sources.list to the standard lines for jessie? BTW: Start the command with 'LANG= ' so the output will be in the default locale, that should be english. > $ LANG= apt-cache policy icedove > icedove: > Installed: 24.4.0-1 > Candidate: 24.4.0-1 > Version table: > *** 24.4.0-1 0 > 500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages > 100 /var/lib/dpkg/status Regrads Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747183: Icedove
Hello Jean-Luc, On Thu, May 08, 2014 at 08:59:30AM +0200, Jean-Luc Rossiny wrote: > The security lines are present in sources.lst file when you download and > install a testing version. > > So, my question is why are they present? I can't answer this question, it's been a long time ago I set up a new system based on testing. If this is true than it's bug and should be reported to the people that working on the installer. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747183: icedove version
Hello Jean-Luc, On Thu, May 08, 2014 at 10:30:49AM +0200, Jean-Luc Rossiny wrote: > Hi > > LANG= apt-cache policy icedove > icedove: > Installed: 24.4.0-1 > Candidate: 24.5.0-1~deb7u1 > Version table: > 24.5.0-1~deb7u1 0 > 500 http://security.debian.org/ stable/updates/main amd64 Packages > *** 24.4.0-1 0 > 500 http://ftp.fr.debian.org/debian/ jessie/main amd64 Packages > 100 /var/lib/dpkg/status > > > The stable version is higher than testing version and apt is picking this version because it's higher, but this Icedove version is depending an the old libffi5 version that can't be resolved via stable-security. So apt can't resolve the dependencies and finally Icedove won't be installed. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747501: thinkfan.service fails to start after upgrade
Package: thinkfan Version: 0.9.2-1 Severity: normal Dear Maintainer, while apt-get update && apt-get upgrade the thinkfan package produces a failure. Setting up thinkfan (0.9.2-1) ... Job for thinkfan.service failed. See 'systemctl status thinkfan.service' and 'journalctl -xn' for details. invoke-rc.d: initscript thinkfan, action "start" failed. dpkg: error processing package thinkfan (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: thinkfan E: Sub-process /usr/bin/dpkg returned an error code (1) The sugessted command gave back the following output. carsten@x201s:~ $ sudo systemctl status thinkfan.service [sudo] password for carsten: thinkfan.service - simple and lightweight fan control program Loaded: loaded (/lib/systemd/system/thinkfan.service; enabled) Active: failed (Result: resources) since Fr 2014-05-09 13:39:09 CEST; 14min ago Mai 09 13:39:09 x201s systemd[1]: Starting simple and lightweight fan control program... Mai 09 13:39:09 x201s thinkfan[24782]: thinkfan 0.9.1 starting... Mai 09 13:39:09 x201s thinkfan[24782]: WARNING: Using default fan control in /proc/acpi/ibm/fan. Mai 09 13:39:09 x201s thinkfan[24782]: WARNING: Using default temperature inputs in /proc/acpi/ibm/thermal. Mai 09 13:39:09 x201s thinkfan[24782]: WARNING: You're using simple temperature limits without correction values, and your fan ... drive. Mai 09 13:39:09 x201s thinkfan[24782]: Module thinkpad_acpi doesn't seem to support fan_control Mai 09 13:39:09 x201s systemd[1]: PID file /var/run/thinkfan.pid not readable (yet?) after start. Mai 09 13:39:09 x201s systemd[1]: Failed to start simple and lightweight fan control program. Mai 09 13:39:09 x201s systemd[1]: Unit thinkfan.service entered failed state. I don't know if the thinkfan apckage is the real package that produces the error or if kernel modul is wrong as written by the systemctl. I use the kernel package from testing. $ LANG= dpkg -l linux-image* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--===-===-= un linux-image (no description available) rc linux-image-3.10-2-amd64 3.10.7-1amd64 Linux 3.10 for 64-bit PCs rc linux-image-3.10-3-amd64 3.10.11-1 amd64 Linux 3.10 for 64-bit PCs rc linux-image-3.11-2-amd64 3.11.10-1 amd64 Linux 3.11 for 64-bit PCs rc linux-image-3.12-1-amd64 3.12.9-1amd64 Linux 3.12 for 64-bit PCs ii linux-image-3.13-1-amd64 3.13.10-1 amd64 Linux 3.13 for 64-bit PCs rc linux-image-3.2.0-3-amd643.2.23-1amd64 Linux 3.2 for 64-bit PCs rc linux-image-3.2.0-4-amd643.2.46-1amd64 Linux 3.2 for 64-bit PCs rc linux-image-3.9-1-amd64 3.9.8-1 amd64 Linux 3.9 for 64-bit PCs ii linux-image-amd643.13+56 amd64 Linux for 64-bit PCs (meta-package) Let me know if you need further logs or infos. Regards Carsten -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages thinkfan depends on: ii libc6 2.18-5 thinkfan recommends no packages. thinkfan 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#602102: icedove: Edit vCard dialogue has broken GUI element
Hello Martin, long time ago you opened this report. On Mon, Nov 01, 2010 at 05:07:48PM +0100, W. Martin Borgert wrote: > Package: icedove > Version: 3.0.7-1 > Severity: minor > > In the dialogue box: > > Edit>Account Settings...>[Some Account]>Attach my vCard to messages>Edit > Card... > > there is a selection box "Prefers to receive messages formatted as:" > with the values "Unknown", "Plain Text", or "HTML". If I set the value > to either "Plain Text" (what else?) or "HTML" (no!), and close the > dialogue, the next time I open it, the value is not visible. However, > the function works perfectly, i.e. the resulting vCard is OK, so it > is only a (very minor) GUI issue. I was able to reproduce this issue in version 10 of Icedove. I haven't tested it in 17 but I checked it right now again with version 24.4.0 and it seems this issue is fixed. I'm unable to reproduce this behavior. Can you please check on your side the status of this bug report? I'd happy to close this report if you found this issue as resolved. Regrads Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747501: thinkfan.service fails to start after upgrade
Hello Evgeni, On Sun, May 11, 2014 at 09:31:44AM +0200, Evgeni Golov wrote: > This is an upgrade from 0.8.1-1? hmm, I just run apt-get update and apt-get upgrade. But probably yes. The cache on the laptop just contains the last update, but mostly at home I use apt-cacher-ng. > $ ls -la /var/cache/apt/archives/thinkfan_0.9.2-1_amd64.deb > -rw-r--r-- 1 root root 33120 Apr 29 08:04 > /var/cache/apt/archives/thinkfan_0.9.2-1_amd64.deb I greped in my apt-cacher-ng repo this, so yes, the update was from 0.8.1. > carsten@iconnect-carsten:/data/apt-cacher-ng $ find | grep thinkfan > ./debrep/pool/main/t/thinkfan > ./debrep/pool/main/t/thinkfan/thinkfan_0.8.1-1_amd64.deb > ./debrep/pool/main/t/thinkfan/thinkfan_0.8.1-1_amd64.deb.head > Can you post your /etc/thinkfan.conf Yes of course, but that the should be the default config from thinkfan.conf.simple. There quite some days gone I was working on it. > $ cat /etc/thinkfan.conf > ## > # thinkfan 0.7 example config file > # > [snip] > # I use this on my T61p: > #tp_fan /proc/acpi/ibm/fan > #tp_thermal /proc/acpi/ibm/thermal (0, 10, 15, 2, 10, 5, 0, 3, 0, 3) > > (0, 0, 55) > (1, 48, 60) > (2, 50, 61) > (3, 52, 63) > (4, 56, 65) > (5, 59, 66) > (7, 63, 32767) > and cat > /sys/module/thinkpad_acpi/parameters/fan_control there is this inside > $ cat /sys/module/thinkpad_acpi/parameters/fan_control > N Hope that's helpful. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747974: icedove: Config - unhelpful messages
Hello Nigel, On Tue, May 13, 2014 at 08:08:07AM -0400, Nigel Horne wrote: > > When adding an account, if I get comething wrong I'm left guessing what's > wrong and wasting time diagnosing the wrong thing: > > 'Icedove failed to find the seccings for your email account' doesn't tell me > if it's my usersname or password that's wrong, or do I have something > wronte with my IMAP, or is it with the SMTP? Which setting am I supposed > to change? I would save time if it said something more useful such as > 'IMAP works, but can't authenticate via SMTP though I can connect'. unfortunately you are right. There are several issues like this inside Icedove (and also Thunderbird) since a long time. Look at some old entries in the BTS. We from the packaging side can't do any useful here, we are unable to do improvements on the source code too. So this is really a problem on upstream. But as Mozilla decided to put Thunderbird more into a opensource community project there is less attention than on Firefox on Thunderbird. As I understand it correct on the Fosdem this year there are only five persons left from Mozilla who working regular on Thunderbird. And they do mostly code clean up und keep the core in sync with Firefox (like libxul.so). So there is a poor situation, Mozilla won't and can't do much about such issues. But they are open to patches, it's up to the community to improve the situation. Care to create a new bugzilla entry on Mozilla or better search first if there is something similar already opened up. Whatever, we need the upstream bug url to keep a tracking forwarded to the upstream bug. Thanks and Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724688: libxul with icedove 24.3.0 and lightning 2.6.4
Hello Andrew,
On Wed, Mar 12, 2014 at 05:55:12PM -0500, Andrew Olney wrote:
> icedove: relocation error:
> /home/aolney/.icedove/lk7ao73s.default/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/Linux_x86_64-gcc3/libcalbasecomps.so:
> symbol _ZN2js13CheckedUnwrapEP8JSObjectb, version xul24 not defined
> in file libxul.so with link time reference
>
> Only occurs with lightning installed
if you using lightning from Mozilla this issue is normal. The symbol
tables are incompatible between Icedove/libxul and upstream lightning.
Please use iceowl-extension instead. The lightning package wan't work
with the Icedove packages.
That's excat the subject of this (closed) bug report.
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741245: [hppa][patch] icedove : FTBFS on hppa, patch attached.
tags 741245 pending thanks Hello Helge, On Mon, Mar 10, 2014 at 07:40:44PM +0100, Helge Deller wrote: > >> --- iceweasel-24.2.0esr.orig/js/src/gc/RootMarking.cpp > >> +++ iceweasel-24.2.0esr/js/src/gc/RootMarking.cpp > >> @@ -320,7 +320,7 @@ MarkConservativeStackRoots(JSTracer *trc > >> > >> uintptr_t *stackMin, *stackEnd; > >> #if JS_STACK_GROWTH_DIRECTION > 0 > >> -stackMin = rt->nativeStackBase; > >> +stackMin = reinterpret_cast(rt->nativeStackBase); > > > > This looks probably o.k. to me. But I haven't tested it for amd64/i386. > > Should work. > > This is inside the > #if JS_STACK_GROWTH_DIRECTION > 0 > ... > #endif > path. > Only the parisc (=hppa) and the "metag" processor architecture do have a > stack with grows upwards. > x86_64, ia64, sparc and on all others the stack grows down. > That means, this code change will not affect any other debian architecture > and this is the > reason that this FTBFS was not detected earlier. > The metag arch isn't supported by debian yet AFAIK. I made some testing builds and Icedove works as expected. I commited the changes based on the patch you appended previously and add you as author locally. Is this o.k. for you? Christoph or Guido will pick this commit before they will upload one of the next versions I think. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700639: icedove: Assertion failure: pRec->state != _PR_PID_REAPED, at uxproces.c:521 (SIGABRT)
Hello Daniel,
On Mon, Apr 22, 2013 at 04:09:51PM -0400, Daniel Kahn Gillmor wrote:
> On 04/22/2013 02:11 PM, Guido Günther wrote:
> > Could you check if enigmal (or any other not icedove related extension)
> > shows up?
>
> I thought maybe i should look for shared objects, since that's part of
> the current enigmail implementation, but these are the only references
> to '\.so' files in the backtrace:
>
>from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
>from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
>from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
> #90 0x7459cd6f in SharedStub () from /usr/lib/icedove/libxul.so
> exePath = "/usr/lib/icedove/\000ibxpcom.so", '\000' times>, ...
>
> i would have thought that
> /usr/lib/xul-ext/enigmail/platform/Linux_x86_64-gcc3/lib/libsubprocess-x86_64-gcc3.so
> or
> /usr/lib/xul-ext/enigmail/platform/Linux_x86_64-gcc3/components/libenigmime-x86_64-gcc3.so
> would have shown up here if enigmail was involved.
>
> there is no "enig" in the backtrace at all. however, looking at the
> code from the relevant backtrace, it really does look like it's stuff
> that happens after a child process terminates, so maybe enigmail isn't
> in the loop by that point.
>
> Anything else i should look for?
it's some time gone after this mail from you. The current Icedove
version 24.3.0-2 has a fixed LDFLAGS variable. We had include
'-Wl,--as-needed' which broke libraries dependencies while linking. So
maybe theese crashes are also possibly gone.
On the other hand the code line and function that shown in the gdb logs
are from the nspr thing and normaly should't depend on the fixed linker
option I think.
mozilla/nsprpub/pr/src/md/unix/uxproces.c
507 static void
508 ProcessReapedChildInternal(pid_t pid, int status)
509 {
510 pr_PidRecord *pRec;
511
512 pRec = FindPidTable(pid);
513 if (NULL == pRec) {
514 pRec = PR_NEW(pr_PidRecord);
515 pRec->pid = pid;
516 pRec->state = _PR_PID_REAPED;
517 pRec->exitStatus = ExtractExitStatus(status);
518 pRec->reapedCV = NULL;
519 InsertPidTable(pRec);
520 } else {
521 PR_ASSERT(pRec->state != _PR_PID_REAPED);<
522 if (_PR_PID_DETACHED == pRec->state) {
523 PR_ASSERT(NULL == pRec->reapedCV);
524 DeletePidTable(pRec);
525 PR_DELETE(pRec);
526 } else {
527 PR_ASSERT(_PR_PID_WAITING == pRec->state);
528 PR_ASSERT(NULL != pRec->reapedCV);
529 pRec->exitStatus = ExtractExitStatus(status);
530 pRec->state = _PR_PID_REAPED;
531 PR_NotifyCondVar(pRec->reapedCV);
532 }
533 }
534 }
As far as I can see the PR_ASSERT comes from
mozilla/nsprpub/pr/include/prlog.h, but this header is for debugging
stuff.
206 #define PR_ASSERT(_expr) \
207 ((_expr)?((void)0):PR_Assert(# _expr,__FILE__,__LINE__))
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700639: icedove: Assertion failure: pRec->state != _PR_PID_REAPED, at uxproces.c:521 (SIGABRT)
Hello, On Fri, Mar 21, 2014 at 04:29:25PM -0400, Daniel Kahn Gillmor wrote: > I'm not sure what i should do with this information. nothing special, I'm allready was thinking that the changed linker flags will not be the solution. Unfortunately such bugs are hard to find unless we are unable to provoke such a behavior of Icedove. I was asking you to see if this ugly bug is allready on the table. > I can re-run my MUA under debug mode again for a while if it would be > useful to get another backtrace. would that be helpful? Maybe, we are glad to have currently get the 24.3.0 into testing and Christoph can provide a new upload with the resent released 24.4.0 maybe this weekend. With this we would leave in afew days the version 17 in stable-security and have only one version all over. I thought the backtrace with a current version will probably better than searching and comparing with an older version because the original source has changed. > I'm surprised that I am the only one seeing this. Do other icedove > users not have my mail volume or something? maybe i happen to be > talking to servers with particular bugs? or too many servers > concurrently? I have no clue, my last crash is months ago. I would say I have a moderate amount of mails, sometimes 10-20 mails on other days up to 60. But I don't use News, RSS or Chat on this. > If icedove was a simpler program, i think it would be more > straightforward to diagnose; but at the moment, i'm mystified by this > ongoing problem. Indeed, Mozilla is forcing their FirefoxOS and only 4-5 persons working on Thunderbird (as told on the Fosdem this year). And this persons doesn't really "working" on new special features. Most of the work is code cleanup and addaptions on the other changes depended on Firefox, xulrunner, nss and so on. Icedove has hugh blob on source files and the internal structure is hard to understand. Thanks for your feedback! Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735156: [Icedove] no mail notifications
Hello Francesco, On Fri, Mar 21, 2014 at 09:23:34PM +0100, Francesco Muzio wrote: > I use KDE 4.11 on testing branch and I can confirm this bug for the latest > version of icedove (24.3.0-2) available I can't confirm this. I'm running the same here and notifications running well. Something to see in the error console? You have notifcation enabled? You can check this on the terminal by $ grep mail.biff.show_alert /path/to/prefs.js If you get nothing then it should be enabled. But you can do also system wide settings in /etc/icedove/pref/icedove.js that will override your local settings. See also http://email.about.com/od/mozillathunderbirdtips/fl/How-to-Get-New-Mail-Alerts-from-Mozilla-Thunderbird.htm Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700639: icedove: Assertion failure: pRec->state != _PR_PID_REAPED, at uxproces.c:521 (SIGABRT)
On Fri, Mar 21, 2014 at 05:18:27PM -0400, Daniel Kahn Gillmor wrote: > On 03/21/2014 05:08 PM, Carsten Schoenert wrote: > > I have no clue, my last crash is months ago. I would say I have a > > moderate amount of mails, sometimes 10-20 mails on other days up to 60. > > But I don't use News, RSS or Chat on this. > > i don't use news, rss, or chat either, but i think i have an order of > magnitude more mail than you :( On work I use the Thunderbird mobile version, there are often more than 100 mails per day and it works, but this the Windows version. :( > how many accounts are you connected to at once? depending on the day, > i'm connected to 3, 4, or 5 accounts concurrently. This depends on the PC/laptop, but it's very similar. On some PC only three, but there are also five accounts configured. But o.k., on the weekend in the upcomming week we meet us on the Groupware Meeting in the Linuxhotel Essen Germany, I think Guido with a significant more skills on GDB log reading and understanding will take a deeper look at your logs. I hope he have a idea to get it. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735156: [Icedove] no mail notifications
Hello Francesco, On Fri, Mar 21, 2014 at 10:56:06PM +0100, Francesco Muzio wrote: > But the problem is a regression. On a modern desktop environment any > notification are showed on a centralized manager. Older version of Iceweasel > (and Icedove <= 17) do this. It depends on the point of view. There will be reasons why Mozilla has removed the notification support via libnotify. > I don't know the details but on new versions of mozilla software lack the > libnotify support. > this bug affect also thunderbird on ubuntu > https://bugzilla.mozilla.org/show_bug.cgi?id=853104#c18 That's the point and the URL you posted is helpfull for fixing this bug report. But we have to discuss if we use the Ubuntu fix or if it maybe breaks somthing, I would say it's o.k. to take the patch from there. > Trying to fade any doubt: when you say "The notification works here on Gnome > 3 and KDE." you mean that the notification of a new mail arrived is showed, > on KDE, in the same position and with same style like a notification of > completed copy of a big file on the filesystem ? > > On my machine the answer is no. Icedove 24 (unlike 17 and 10) shows in > autonomous way its notifications. You are right, I mean the standalone notification from Icedove about new mails that are arrived. (For me this is enough.) Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742324: icedove: Can't create 2nd e-mail account
Hello Nigel, On Sat, Mar 22, 2014 at 07:59:21AM -0400, Nigel Horne wrote: > I'm trying to add a second e-mail account. All looks OK until the very > end when it aborts saying "Incoming server already exists". It doesn't > say where it exists or offer me a button to fix it. The name of the > incoming server is not the same as that on the existing account. can you please tell something more around your constellation? Is this a fresh installation? Have you tried to start in safe mode? Have you tried to backup your current config an setup a complete new profile? >From which provider is your first email account? What tells Icedove in the error console or equal what's printed out in the terminal if you start Icedove in a terminal window? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#510589: still crashing in 17.0-1
Hello Am 13.01.2013 18:32, schrieb Daniel Kahn Gillmor: > thanks for the suggestion! > > i've tried this, but all the stack frames are still anonymous memory > locations (weirdly, with the exception of a single non-helpful line in > thread 35: That's what I mean with "other" packages with debugging symbols. I believe your segfaults don't come from icedove itself. I thought they come from a other package, but don't know which package it could be. So a good backtrace would be really helpfull. > I have the corresponding icedove-dbg package -- what other package do i > need? As I can see you use a core dump, mhh as I remember right (I'm not at home while writing this mail) the gdb always show the package there the symbol would come from while the binary is running inside. So please try to icedove inside the gdb. > I use primarily wheezy, but with some packages from sid and experimental. o.k. thanks -- Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#435041: icedove: incosistent display of number of unread/available mails in newsgroup folders
Hello Moritz, On Sat, Jul 28, 2007 at 10:06:39PM +0200, Moritz Lenz wrote: > Package: icedove > Version: 1.5.0.12.dfsg1-0etch1 > Severity: normal > > for a newsgroup folder (for de.comp.lang.perl.cgi) icedove thinks there > are 1 unread and 229 read mails, however there are no unread messages. > After chosing 'Mark newsgroup as read' from the context menu the numbers > change to 0 unread and 340 read messages. After the next periodic query > to the server (or when chosing 'Get Messages for Account') the numbers > jump back to the original values (1 unread, 229 read). > > This occurs both in normal mode with a few plugins enabled as well as in > safe mode. It constantly occured during the last few days. > > Don't hestiate to ask for more informations if you need them, I just > don't know what else you need to know. are there any problems on recent versions with the same behavior you discribed? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#510589: still crashing in 17.0-1
Hello Daniel, Am 16.01.2013 18:10, schrieb Daniel Kahn Gillmor: > On Mon 2013-01-14 13:00:06 -0500, Daniel Kahn Gillmor wrote: > >> i've installed a bunch of other -dbg packages (e.g. libc6-dbg, >> libnspr4-dbg, libnss3-dbg, ...), in the hopes that that will give me >> more feedback in the next crash. > > woo, yay(?), i got one! Hmm, o.k. Can you provide a longer entry from the end? The few lines are to short to see anything. Hopefully we see the than the reason why it's segfaulting. :/ -- Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#510589: Fwd: Re: Bug#510589: still crashing in 17.0-1
Hello Mike, can you please take a look into this bug? You know more of the internal mystique of Icedove. :) This forwarded mail is the beginning of the interesting part that Daniel has posted. Thx Carsten Original-Nachricht Betreff: Re: Bug#510589: still crashing in 17.0-1 On 01/13/2013 04:08 AM, Carsten Schoenert wrote: > You have to call backtrace with a few more arguments, icedove is a multi > threaded program, so we must to see all the threads. So please try >> (gdb) thread apply all bt thanks for the suggestion! i've tried this, but all the stack frames are still anonymous memory locations (weirdly, with the exception of a single non-helpful line in thread 35: Thread 35 (LWP 17416): #0 0x7f37da62f64b in ?? () #1 0x076f in ?? () #2 0x7f37bc82c188 in ?? () #3 0x7f37bc8630e8 in ?? () #4 0x07d9 in ?? () #5 0x7f378b9fecd0 in ?? () #6 0x7fff347ffa1b in gettimeofday () #7 0x07da in ?? () #8 0x07d9 in ?? () #9 0x07d9 in ?? () #10 0x7f37bc8630e8 in ?? () #11 0x076f0002 in ?? () #12 0x in ?? () ) > This looks like there are no debugging symbols. Without the symbols it's > impossible to track down the error. I have the corresponding icedove-dbg package -- what other package do i need? > just need the output of icedove made with the gdb while crashing. In > the Icdove wiki page [1] are all the needed part to collect this data. > Please check if the segfaults also happen while using a clean fresh > profile without any extensions! Many problems happen to users that uses > migrated User Profiles from Thunderbird 1.5. or 2.0. the segfaults i've seen have not be trivially reproducible or tied to any particular action. they happen after at least a day of active use (and i process a lot of e-mail). This is not something i can actually do with a fresh profile, or without the extensions i rely on (enigmail in particular). > If you can also collect data from the icedove activity itself [2] so > please do. this seems to want me to run icedove while creating a huge activity log. I'll try this, but given the amount of activity between crashes, i suspect this file is likely to be enormous. I'll see what i can do with it, though. > Depending on point the segfault happen it's maybe necessary to install > more packages with debugging symbols. which packages should i install beyond icedove-dbg? >> fwiw, I'm running icedove from experimental: > > Strange, all my various icedove versions doesn't segfaulting for a long > time. Which debian release do you use? I use primarily wheezy, but with some packages from sid and experimental. --dkg -- Mit freundlichen Grüßen Carsten Schönert -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
