Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 192982 - pidgin-2.2.0 -- gdk assertion when attemption to start pidgin
Summary: pidgin-2.2.0 -- gdk assertion when attemption to start pidgin
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Net-im project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-18 22:34 UTC by Justin C
Modified: 2007-10-26 01:21 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Justin C 2007-09-18 22:34:39 UTC 
after upgrading pidgin from 2.1.1 to 2.2.0, pidgin repeatedly fails to run.
attempt to print a backtrace of error not possible with the assertion, gdb output as follows:

>  (gdb) run
>  Starting program: /usr/bin/pidgin 
>  [Thread debugging using libthread_db enabled]
>  [New Thread -1232419120 (LWP 25185)]
>  No protocol specified
>
>  (pidgin:25185): Gdk-CRITICAL **: gdk_display_get_name: assertion `GDK_IS_DISPLAY (display)' failed
>  Pidgin 2.2.0
>
>  ** (pidgin:25185): WARNING **: cannot open display: unset
>
>  Program exited with code 01.
>  (gdb) bt full
>  No stack.

Reproducible: Always

Steps to Reproduce:
1.  echo 'net-im/pidgin avahi crypt dbus eds gnutls gstreamer gtk msn -ncurses nls perl spell ssl networkmanager sasl xscreensaver' >> /etc/portage/package.use
2.  emerge =pidgin-2.1.1
3.  emerge =pidgin-2.2.0
4.  run pidgin from command line.

Actual Results:  
> pidgin
No protocol specified

(pidgin:25185): Gdk-CRITICAL **: gdk_display_get_name: assertion `GDK_IS_DISPLAY (display)' failed
Pidgin 2.2.0

** (pidgin:25185): WARNING **: cannot open display: unset
Program exited with code 01.

Expected Results:  
Expected Pidgin to continue running.

installed dependencies are as follows:
1.  app-text/gtkspell-2.0.11-r1
2.  dev-lang/perl-5.8.8-r2
3.  dev-lang/python-2.4.4-r4
4.  dev-libs/cyrus-sasl-2.1.22-r2
5.  dev-libs/dbus-glib-0.73
6.  dev-libs/glib-2.12.13
7.  dev-libs/libxml2-2.6.28
8.  dev-perl/XML-Parser-2.34
9.  dev-python/dbus-python-0.81.0
10. dev-util/pkgconfig-0.21-r1
11. gnome-extra/evolution-data-server-1.10.2
12. media-libs/gst-plugins-good-0.10.4
13. media-libs/gstreamer-0.10.13
14. net-libs/gnutls-1.4.4-r1
15. sys-apps/dbus-1.0.2-r2
16. sys-apps/sed-4.1.5
17. sys-devel/autoconf-2.61
18. sys-devel/automake-1.9.6-r2
19. sys-devel/gettext-0.16.1
20. sys-devel/libtool-1.5.23b
21. x11-libs/gtk+-2.10.14
22. x11-libs/libXScrnSaver-1.1.2
23. x11-libs/startup-notification-0.8
Comment 1 Olivier Crete (RETIRED) gentoo-dev 2007-09-19 05:49:37 UTC 
can you do:
echo $DISPLAY
is it set ?
Comment 2 Justin C 2007-09-19 14:44:07 UTC 
I think I made a mistake concerning this bug.
I had used my Linux system for over a week since I last emerged anything.
Once I upgraded pidgin, this problem first appeared.
Afterward, as I tried to run other programs, this assertion occurred for them as well.
I don't remember upgrading my glib or gtk libraries, even when I emerged pidgin-2.2.0, but it's apparent my conflict is there.

I'm compiling my system to correct this.
Consider this bug operator error.