Thanks Gregor. I'll upload a new version with this patch.
On Fri, Jul 20, 2018 at 8:09 PM gregor herrmann wrote:
> Control: tag -1 + patch
>
> On Thu, 19 Apr 2018 18:08:40 +0000, Ari Pollak wrote:
>
> > Sorry, I haven't had time to do anything about it yet and I won't b
Sorry, I haven't had time to do anything about it yet and I won't be able
to look at it for the next month or so.
Package: libsfcgal1
Version: 1.3.3-1
Severity: serious
I have postgresql-9.6-postgis-2.3 installed (no longer in Debian
buster, but was in stretch, current stable). After upgrading libsfcgal1
and trying to use postgis on my existing Postgres 9.6 server, I get an
error when trying to access a
Thanks; could you install libgtk2.0-0-dbg and libglib2.0-0-dbg and obtain a
new backtrace?
Since I'm unable to reproduce this on my system, could you please get a
backtrace by installing the gimp-dbg package and following the directions
here: https://wiki.debian.org/HowToGetABacktrace
Shouldn't this be a bug on gegl?
Hi,
Is this crash fixed after upgrading to xwayland 2:1.18.2-1?
Thanks,
Ari
What happens if you remove beignet-opencl-icd?
It is not sufficient to create such a copyright file while
building the binary package.
Since when? The part of policy you quoted says the copyright file *should* be
in debian/copyright, not *must*.
https://www.debian.org/Bugs/Developer#severities
serious
is a severe violation of Debian policy (roughly, it violates a must or
required directive), or, in the package maintainer's or release manager's
opinion, makes the package unsuitable for release.
--
To UNSUBSCRIBE, email to
Package: gnome-shell-pomodoro
Version: 0.10.3-1
Severity: serious
gnome-shell-pomodoro 0.10.3 dosn't work with gnome-shell 3.16. There is a
new version of gnome-shell-pomodoro available upstream that does.
Maybe the Debian package should also be updated to depend on versions of
gnome-shell less
Can you please install gimp-dbg and follow the directions to obtain a
backtrace of the crash here: https://wiki.debian.org/HowToGetABacktrace
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
reassign 787893 libnettle4
forcemerge 787620 787893
thanks
Thanks for the backtrace, it looks like this is the same problem as
#787620, which involves an ongoing transition in sid for gnutls/nettle.
reopen 765654
thanks
Sorry, this now makes the package uninstallable because libgnutls-dev
ends up conflicting with itself. I think I meant that this should depend
on libgnutls28-dev instead.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
Package: libgadu-dev
Version: 1:1.12.0-3
Severity: serious
When running this: pkg-config --exists --print-errors libgadu
I get this error:
Package gnutls was not found in the pkg-config search path.
Perhaps you should add the directory containing `gnutls.pc'
to the PKG_CONFIG_PATH environment
Ugh. Thanks.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Is this something that can be taken care of with a binNMU after liblcms1 is
removed? I'm not sure there's much I can do at this point beyond patching
upstream.
Thanks, looks good to me.
On Feb 28, 2014 6:15 AM, Hideki Yamane henr...@debian.or.jp wrote:
Hi,
On Fri, 17 Jan 2014 10:25:33 -0500
Ari Pollak a...@debian.org wrote:
I was hoping upstream would release a new stable version, since it would
also fix a FTBFS. That still hasn't happened, so I
I was hoping upstream would release a new stable version, since it would
also fix a FTBFS. That still hasn't happened, so I might just end up
releasing a git snapshot.
On Fri, Jan 17, 2014 at 10:10 AM, Moritz Muehlenhoff j...@inutil.org wrote:
On Wed, Dec 04, 2013 at 08:48:59PM -0500, Ari
It seems unlikely that pidgin is at fault here, given that it hasn't
been updated in almost a year. Do you happen to have
gstreamer0.10-buzztard installed? Does this still happen if you remove it?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
If you're doing an NMU anyway, want to apply the patches for the recent
CVEs? I was waiting for a new release, but not sure when one will be out.
Thanks,
Ari
On Dec 12, 2013 12:39 PM, Cyril Brulebois k...@debian.org wrote:
Control: tag -1 upstream patch
Julien Cristau jcris...@debian.org
Just a note, I plan on updating unstable but not stable gimp.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
severity 714871 important
thanks
Lowering priority since it's not a regression from wheezy.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Could you try to get a backtrace by installing pidgin-dbg and following
the instructions here:
http://wiki.debian.org/HowToGetABacktrace#Running_gdb
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 02/24/2013 10:56 AM, Olaf Rühenbeck wrote:
Which lets the pidgin version I just updated to segfault, is fixed
in the next version.
See here: https://bugs.mageia.org/show_bug.cgi?id=9075
Thanks, I'll apply the upstream patch and upload a new revision.
--
To UNSUBSCRIBE, email to
FYI this is the patch that would have to be backported:
http://developer.pidgin.im/viewmtn/revision/info/18f2f94b625542348af0049e0132a83a1c58aef6
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
It does appear that squeeze's libpurple0 is affected by this, though the
patch doesn't apply cleanly.
Technically, the possible crash is in the client code, and I don't think
pidgin or finch exhibit this behavior; the original bug was against
Adium for OS X, based on libpurple.
I don't think
Thanks for the package update. Are you interested in taking over
maintainership of the package, or at least becoming co-maintainer?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I might get to this eventually, but I don't have the time in the immediate
future to do this transition, and upstream doesn't seem to have touched it. So
for the time being, it probably just makes sense to remove it from testing.
--
To UNSUBSCRIBE, email to
severity 642199 important
thanks
Fails to connect how? Is there an error message? Can you attach the
output from Help-Debug Window while connecting?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On 09/19/2011 05:55 PM, Noel David Torres Taño wrote:
So, your closing means that GIMP is not culprit at all of the failure? Is it
completely a responsability of the nvidia driver?
Correct.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
Which X display driver are you using?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Are you using the driver from a package or did you download it separately?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: libgadu-dev
Version: 1:1.11.0-1
Severity: serious
running pkg-config --libs libgadu reports the following error:
Package gnutls was not found in the pkg-config search path.
Perhaps you should add the directory containing `gnutls.pc'
to the PKG_CONFIG_PATH environment variable
--
severity 630254 important
thanks
The package is not unusable just because one protocol is unusable.
You cannot log in.. to what? ICQ? Can you open Help - Debug Window,
then try to log in, then attach the output from the debug window?
--
To UNSUBSCRIBE, email to
Package: libgraphviz-dev
Version: 2.26.3-5
Severity: grave
The following packages have unmet dependencies:
libgraphviz-dev: Depends: ocaml-base-nox-3.11.2 which is a virtual
package.
It looks like it should depend on ocamp-base-nox instead?
-- System Information:
Debian Release: wheezy/sid
On 05/31/2010 09:37 PM, Paul Szabo wrote:
This package suggests ghostscript, and may be affected. Please
evaluate the security of this package, and fix if needed.
What do you suggest I fix? gimp already calls gs with -dSAFER.
--
To UNSUBSCRIBE, email to
severity 562720 important
thanks
After some discussion with the bug reporter, I think we agreed that this
was not RC.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I can't seem to reproduce this. Can you send the output of
gconftool -R /system/gstreamer/0.10/default ?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
severity 562720 important
thanks
Please accept my deepest apologies for downgrading the severity of a bug
that obviously did not meet the criteria for a serious severity. Let me
quote from the BTS manual:
serious
is a severe violation of Debian policy (roughly, it violates a must or
required
Looks like this is going to take a while since I can no longer build
gimp in an unstable pbuilder as a result of the surprise libjpeg transition.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Nelson A. de Oliveira wrote:
Ari, is it right to don't have this dependency now or it was something
that went unnoticed?
This appears to be my fault, though I don't know how it happened.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
I've just been informed that this is CVE-2010-0013.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Nico Golde wrote:
Hi Ari,
are you working on an update? I'd NMU this bug otherwise,
the issue sucks for a lot of users.
Not yet. Feel free to NMU it.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
From upstream:
A patch for the file upload vulnerability can be found in 4be2df4f,
3d02401c, and c64a1adc [1, 2, 3]. The fix itself is in [3], but depends
on the first two to apply properly (and clean up memory correctly).
As a note, when backporting the patch to anything older than 2.6.0, the
retitle 548336 random crashes with type * * not a basic type
affects 548336 +iceweasel
thanks
Apparently this can be fixed by restarting your X session.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Adrian Glaubitz wrote:
Moreover, since all kernel packages in testing have been upgraded to
2.6.30, the issue should have solved itself. One could introduce a
dependency on linux-image-2.6, version 2.6.27 or higher but I don't
really know whether this is a clean solution. In any case,
reopen 520189
thanks
On Mon, 2009-09-14 at 20:51 +, Debian Bug Tracking System wrote:
It looks like at some point in the past, the plugin loader stub hasn't been
updated. This is possibly down to debconf settings - I'd advise turning on
automatic stub updating for globally installed
This is reported in gimp as #544618. Upstream is not planning on fixing
it until 2.8, and they recommend using pkg-config with gimp.pc instead.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
So.. can you install pidgin-dbg and get a backtrace as described here:
http://wiki.debian.org/HowToGetABacktrace
What's the output of pidgin -d?
Will pidgin start if you run pidgin -n?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
That would be enough, but there are so many other problems with the
libgimp-perl package as it related to gimp 2.6 that it's not worth
fixing until the other issues are resolved.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
So it crashes on exit or while you're using the program? What happens if
you remove libcanberra-gtk-module?
On Mon, 2009-06-22 at 17:16 +0200, Wouter Koolen-Wijkstra wrote:
Hi Ari,
Thanks for your quick reply. I rebuilt from source as indicated there.
Unfortunately, it's not a segfault, but
reassign 534161 libcanberra-gtk-module
thanks
On Tue, 2009-06-23 at 19:58 +0200, Wouter Koolen-Wijkstra wrote:
Ari Pollak wrote:
So it crashes on exit or while you're using the program?
During normal operation (some clicks here and there, switch tabs, search
etc.) it randomly quits
Could you get a backtrace as described here:
http://wiki.debian.org/HowToGetABacktrace
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
peter green wrote:
tags 523597 +patch
thanks
patch is attatched
Thanks, but any idea why this needs to be so complicated? Shouldn't it
just require updating the symlinks?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Can you try the plt-scheme package from testing or unstable?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
What happens if you move your ~/.plt-scheme directory out of the way?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
(forgot to send this reply to the bug)
On Wed, 2009-03-18 at 22:03 +, Rob Andrews wrote:
Given this situation, I'm wondering what worth there is implementing a fix
if it's already obsolete before the package is pushed out.
Because there's no dependency on kernel = 2.6.27, and there's
Package: nspluginwrapper
Version: 1.3.0-1
Severity: serious
nspluginwrapper currently does not work at all on my system; I believe
this has to do with a kernel 2.6.27-specific flag passed to socket()
now, but I'm not entirely sure. This is especially bad given that the
default kernel in both
I forgot to include the output of nspluginplayer:
~% NPW_INDENT_MESSAGES=1 NPW_DEBUG=1 nspluginplayer
src=http://magic.pen.fizzlebot.com/magic-pen.swf width=800 height=520
*** NSPlugin Wrapper *** plugin_exit
*** NSPlugin Wrapper *** NP_GetMIMEDescription
*** NSPlugin Wrapper *** plugin_init
I just confirmed that this is related to the kernel version; rebooting
into 2.6.28 fixed the problem.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Strange, this isn't happening for me with the same versions. However, it
looks like your gegl package is in a weird state:
pi libgegl-0.0-0 0.0.20-1 Generic Graphics Library
Can you check this and make sure it's fully installed?
--
To UNSUBSCRIBE, email to
What happens if you move your ~/.plt-scheme directory out of the way?
Also, could you follow the directions at
http://wiki.debian.org/HowToGetABacktrace to rebuild with debugging
symbols and get another backtrace?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a
Please install pidgin-dbg and get a backtrace as described at the web
page in the crash message.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Do you have an plugins loaded? What happens if you disable sounds
completely?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
What's the output of gconftool -R /system/gstreamer/0.10/default?
Also, could you try the version of pidgin from experimental?
Milan P. Stanic wrote:
On Wed, 2008-12-24 at 15:59, Ari Pollak wrote:
Do you have an plugins loaded? What happens if you disable sounds
completely?
I tested it more
If you run gstreamer-properties and set the output plugin to ALSA, then
set Pidgin back to Automatic sounds, I assume it works again?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
You'll have to include some more information or this bug report is
useless. Can you get a backtrace of the crash as described here:
http://wiki.debian.org/HowToGetABacktrace (you can skip to the Running
gdb section after installing the pidgin-dbg package)
Also, do you have any plugins loaded?
Nope, the crash was pretty clearly in the engine. I'm sure gimp 2.4 uses
newer features of GTK, which the theme could have problems with. I
haven't received any other reports of a crash under these circumstances.
Sergey I. Sharybin wrote:
I tested this issue on my Debian Etch machine with gimp
As far as I can tell, --with-system-ssl-certs doesn't exist in 2.4.3.
On Wed, 2008-08-06 at 13:03 -0400, Ethan Blanton wrote:
Why is a patch necessary to enable /etc/ssl/certs? Does
--with-system-ssl-certs= not do what you need? If so, we should fix
it, rather than applying additional hacks.
On Wed, 2008-08-06 at 14:43 -0400, Ethan Blanton wrote:
Whoops, an excellent point. You might want to simply use the attached
(untested, but compiles and looks rather trivial) patch, instead,
which is from upstream. It is upstream revision
90ed1fb17982cbb6355d5dd32d041b8c0027509b and
If what you say is correct, then most Pidgin installations are not
verifying certificates correctly and this isn't just a Debian problem.
Any patch needs to address the real issue, especially since upstream has
discouraged using GNUTLS.
Miron Cuperman wrote:
I believe this bug was introduced
Is the server certificate present in /etc/ssl/certs or Tools-Certificates?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Reinhard Tartler wrote:
Btw, why does rss-glx link against libopenal statically anyway? Isn't
that frowned upon by the security team?
Where do you see it being linked statically?
% ldd /usr/lib/xscreensaver/skyrocket
libalut.so.0 = /usr/lib/libalut.so.0 (0x2ab504196000)
I don't understand this bug, since it builds fine on my system and has
built fine on the buildds fairly recently.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Mon, 2008-04-28 at 09:45 +0200, Lucas Nussbaum wrote:
I improved my template to clarify that bugs are not necessarly
gcc-4.3-specific. But even if it's not gcc-4.3-related, it's still an
FTBFS, and it's still RC.
Except that it doesn't seem to happen under normal circumstances.
The
On Mon, 2008-04-28 at 18:10 +0200, Lucas Nussbaum wrote:
re-read what I wrote above. why would in check the write permissions on
foo if it's going to install in bar anyway?
It's not explicitly checking for write permissions, it just tries to
make the directory. I realize it's not actually doing
severity 477970 important
thanks
This appears to be some unrelated install error having nothing to do
with gcc-4.3. I can't reproduce this under a normal pbuilder
environment, and it hasn't been reproduced on the buildds.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Could you attach the full output from pidgin -d? Does 2.4.1 fix the
problem?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
reassign 474007 libpurple0
thanks
Do you have a /usr/lib/libnssutil3.so.1d file? Does it match what's in
the libnss3-1d package? Do you have anything in /usr/local/lib also?
reassign 474007 libnss3-1d
found 474007 3.12.0~beta2-1
reassign 474007 versions in symbols file not updated for nssutil
thanks
In version 3.12.0~beta2-1 of libnss3-1d, -lnssutil was added as a
required library in nss.pc, but the symbols file was not updated with
the correct version. So programs
# Automatically generated email from bts, devscripts version 2.10.18.1
#
# pidgin (2.4.0-2) UNRELEASED; urgency=low
#
# * debian/patches/22_zephyr-crash.patch:
#- Add patch from upstream to prevent crash in Zephyr when reading
# accounts.xml file (Closes: #470947)
# *
Does it actually freeze, or can you get to a console with
Ctrl-Alt-F1? If your browser when starting pidgin from a
terminal is links2, then it's probably the same as starting
pidgin from outside a terminal. What is the browser set to in
pidgin's preferences under the Network tab?
On Mon, Feb 11,
Wow. Can you elaborate a bit further for such a severe bug? What exactly
do you mean by the whole system crashes?
henry atting wrote:
Package: pidgin
Version: 2.3.1-2
Severity: critical
Justification: breaks the whole system
When in a Chat Window clicking on a link sent from a user the
severity 465102 important
thanks
Freezing logjam at this point does not freeze your entire desktop, it
just locks your input devices. Killing logjam from a console releases
the lock.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Unofficial prebuilt packages are here:
http://134.2.34.20/blank/debian/linux-2.6/
as referenced here:
http://lists.debian.org/debian-kernel/2008/02/msg00363.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Upstream seems to have patched referencer a while ago to support poppler
0.6: http://svn.icculus.org/referencer?rev=548view=rev
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
reassign 453767 python-gst0.10
thanks
I'm reassigning this back to python-gst0.10 since the python-gst package
no longer exists, but there does not seem to be a proper upgrade path
for people who already had python-gst installed from etch.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Package: quodlibet
Version: 1.0-1
Severity: grave
quodlibet no longer starts after upgrading python-gst0.10. It fails with
lots of errors like this:
Traceback (most recent call last):
File /usr/share/quodlibet/formats/__init__.py, line 22, in ?
try: format = __import__(name, {}, {}, self)
forcemerge 446759 453759
thanks
I'll ask you the same thing I asked the other bug submitter from which I
never got a response:
Could you try unloading all of the plugins and see if it still crashes? If
it no longer crashes, try loading each of them individually until you see
the crash.
--
Huh? Pidgin 2.2.2-1 doesn't depend on intltool, so why should it matter what
version is installed?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The point here is that xscreensaver should not unlock the screen when
missing xscreensaver-gl-helper, it should just display a blank
screensaver. rss-glx does not NEED to be run with xscreensaver-gl-helper
as it's perfectly feasible to run with gnome-screensaver, so rss-glx
shouldn't need to
According to NEWS.Debian:
* The gimp package now includes its own Print plug-in, and should
automatically remove the old gimp-print package that was provided by
Gutenprint. If you still want to use the extended Gutenprint Print
plug-in, please install the gimp-gutenprint package.
So
severity 41 wishlist
retitle 41 needs better error message when opening a second instance
forwarded 41 http://developer.pidgin.im/ticket/3417
thanks
You have another instance of pidgin running. Either kill that instance,
bring it back up normally, or start pidgin with --multiple.
Except for one problem - pidgin doesn't use gconf.
James LewisMoss wrote:
When I've logged out of X and logged back in, but not when logging in
right after a reboot.
It looks like the gconf daemon doesn't exit properly when X exits so the
next time you start there are two running, but the
Please install the pidgin-dbg and libgtk2.0-0 packages, and get a
backtrace as described here:
http://developer.pidgin.im/wiki/GetABacktrace
Also, moving your ~/.purple directory out of the way and trying again
might help, as will attaching the output of pidgin -d.
On Fri, 2007-09-28 at 11:00
What happens if you rename your ~/.purple directory?
On Fri, 2007-09-28 at 11:54 -0400, jlquinn (optonline) wrote:
Ari Pollak wrote:
Please install the pidgin-dbg and libgtk2.0-0 packages, and get a
backtrace as described here:
http://developer.pidgin.im/wiki/GetABacktrace
Also, moving
on libmpich1.0c2 to libmpich1.0ldbl
+(Closes: #441882)
+
+ -- Ari Pollak [EMAIL PROTECTED] Sun, 23 Sep 2007 10:53:22 -0400
+
mpich (1.2.7-3) unstable; urgency=low
* Corrected alternatives removal in prerm (closes: #306305).
diff -u mpich-1.2.7/debian/control mpich-1.2.7/debian/control
Sorry, this was well open for an immediate NMU since it had been filed for
longer than a week. No harm done in getting the fix in early.
Adam C Powell IV wrote:
Wow, thanks for the thirty minutes notice. I had planned to build and
upload tomorrow. Oh well.
--
To UNSUBSCRIBE, email to
Package: libc6-dev
Version: 2.6.1-4
Severity: grave
After the changes in -3 to sysmacros.h to fix #439859, software that
defined a major or minor variable now breaks, whereas it used to compile
fine. I have not heard a valid rationale for breaking things resulting
from that patch. gimp currently
1 - 100 of 165 matches
Mail list logo
