<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>123656</bug_id>
          
          <creation_ts>2006-02-21 14:54 0000</creation_ts>
          <short_desc>problems with qingy-0.7.1</short_desc>
          <delta_ts>2006-03-19 23:56:36 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Applications</component>
          <version>2005.1</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>masse_nicolas@yahoo.fr</reporter>
          <assigned_to>s4t4n@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>masse_nicolas@yahoo.fr</who>
            <bug_when>2006-02-21 14:54:00 0000</bug_when>
            <thetext>Previously, I was using qingy-0.6 with no problem. But since I install the 0.7.1, I&apos; ve lots of problems.
First of all, my system doesn&apos;t start any session anymore. I mean that qingy is  launched well, but when I try to login, I only have an empty console where I can&apos;t do anything. It does that with all the users.
In order to get logged, I have to switch to another console (where qingy isn&apos;t running) and login from there. Also, I&apos;ve remark that when he is started, qingy take all my cpu time. So I must kill it. And what is even more  strange is that  after that, qingy is respauwn (this is normal) but doesn&apos;t take all my cpu time. (But i can&apos;t use it to get logged)

Info about my system:

Portage 2.1_pre4-r1 (default-linux/x86/2005.1, gcc-4.0.2, glibc-2.3.6-r1, 2.6.14-gentoo-r3 i686)
=================================================================
System uname: 2.6.14-gentoo-r3 i686 AMD Athlon(tm) XP 2800+
Gentoo Base System version 1.12.0_pre11
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.91.0.4
sys-devel/libtool:   1.5.20-r1
virtual/os-headers:  2.6.11-r3
ACCEPT_KEYWORDS=&quot;x86 ~x86&quot;
AUTOCLEAN=&quot;yes&quot;
CBUILD=&quot;i686-pc-linux-gnu&quot;
CFLAGS=&quot;-O3 -march=athlon-xp -fomit-frame-pointer -pipe&quot;
CHOST=&quot;i686-pc-linux-gnu&quot;
CONFIG_PROTECT=&quot;/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control&quot;
CONFIG_PROTECT_MASK=&quot;/etc/gconf /etc/splash /etc/terminfo /etc/env.d&quot;
CXXFLAGS=&quot;-O3 -march=athlon-xp -fomit-frame-pointer -pipe&quot;
DISTDIR=&quot;/usr/portage/distfiles&quot;
FEATURES=&quot;autoconfig distlocks sandbox sfperms strict&quot;
GENTOO_MIRRORS=&quot;http://gentoo.inode.at/ http://mirror.datapipe.net/gentoo http://mirror.datapipe.net/gentoo &quot;
LINGUAS=&quot;fr fr_FR&quot;
MAKEOPTS=&quot;-j2&quot;
PKGDIR=&quot;/usr/portage/packages&quot;
PORTAGE_TMPDIR=&quot;/var/tmp&quot;
PORTDIR=&quot;/usr/portage&quot;
PORTDIR_OVERLAY=&quot;/usr/local/portage&quot;
SYNC=&quot;rsync://rsync.gentoo.org/gentoo-portage&quot;
USE=&quot;x86 3dnow X aac acpi adns alsa apm audiofile avi bitmap-fonts bmp cairo cdr crypt cups curl dbus dga divx4linux dri dvd dvdr eds emboss encode fbcon flac foomaticdb fortran gb gcj gdbm gif gimp gpm gtk gtk2 gtkhtml hal imagemagick imap imlib ipv6 java jikes joystick jpeg kerberos libg++ libwww mad mikmod mmx mp3 mpeg ncurses nls nocd nptl nsplugin nvidia ogg oggvorbis openal opengl oss pdf pdflib perl png python quicktime readline samba scanner sdl sox spell sse ssl szip tcpd tiff truetype truetype-fonts type1-fonts unicode usb videos vorbis win32codecs wmf xml2 xv xvid zlib elibc_glibc kernel_linux linguas_fr linguas_fr_FR userland_GNU&quot;
Unset:  ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LANG, LC_ALL, LDFLAGS</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>s4t4n@gentoo.org</who>
            <bug_when>2006-02-21 23:18:03 0000</bug_when>
            <thetext>May I see the contents of your /etc/inittab and /etc/qingy/settings?
Also, does it say something if you start it with --verbose command line arg, then switch to text mode via CTRL-ESC?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>masse_nicolas@yahoo.fr</who>
            <bug_when>2006-02-22 13:08:39 0000</bug_when>
            <thetext>/etc/inittab:

#
# /etc/inittab:  This file describes how the INIT process should set up
#                the system in a certain run-level.
#
# Author:  Miquel van Smoorenburg, &lt;miquels@cistron.nl&gt;
# Modified by:  Patrick J. Volkerding, &lt;volkerdi@ftp.cdrom.com&gt;
# Modified by:  Daniel Robbins, &lt;drobbins@gentoo.org&gt;
# Modified by:  Martin Schlemmer, &lt;azarah@gentoo.org&gt;
#
# $Header: /var/cvsroot/gentoo-x86/sys-apps/sysvinit/files/inittab,v 1.2 2004/12/22 03:25:20 vapier Exp $

# Default runlevel.
id:3:initdefault:

# System initialization, mount local filesystems, etc.
si::sysinit:/sbin/rc sysinit

# Further system initialization, brings up the boot runlevel.
rc::bootwait:/sbin/rc boot

l0:0:wait:/sbin/rc shutdown 
l1:S1:wait:/sbin/rc single
l2:2:wait:/sbin/rc nonetwork
l3:3:wait:/sbin/rc default
l4:4:wait:/sbin/rc default
l5:5:wait:/sbin/rc default
l6:6:wait:/sbin/rc reboot
#z6:6:respawn:/sbin/sulogin

# TERMINALS
c1:12345:respawn:/sbin/qingy tty1 linux
#c1:12345:respawn:/sbin/agetty 38400 tty1 linux
c2:12345:respawn:/sbin/agetty 38400 tty2 linux
c3:12345:respawn:/sbin/agetty 38400 tty3 linux
c4:12345:respawn:/sbin/agetty 38400 tty4 linux
c5:12345:respawn:/sbin/agetty 38400 tty5 linux
c6:12345:respawn:/sbin/agetty 38400 tty6 linux

# SERIAL CONSOLES
#s0:12345:respawn:/sbin/agetty 9600 ttyS0 vt100
#s1:12345:respawn:/sbin/agetty 9600 ttyS1 vt100

# What to do at the &quot;Three Finger Salute&quot;.
ca:12345:ctrlaltdel:/sbin/shutdown -r now

# Used by /etc/init.d/xdm to control DM startup.
# Read the comments in /etc/init.d/xdm for more
# info. Do NOT remove, as this will start nothing
# extra at boot if /etc/init.d/xdm is not added
# to the &quot;default&quot; runlevel.
x:a:once:/etc/X11/startDM.sh

# End of /etc/inittab
===============================================================================

/etc/qingy/settings:

# Directory containing X sessions
x_sessions = &quot;/etc/X11/Sessions/&quot;
# Directory containing text mode sessions
text_sessions = &quot;/etc/qingy/sessions/&quot;
# Directory where qingy should put its temporary files
temp_files_dir = &quot;/var/lib/misc&quot;

# Full path to the X server
# x_server = &quot;/usr/X11R6/bin/XFree86&quot;
# Full path to the &apos;xinit&apos; executable
xinit = &quot;/usr/bin/xinit&quot;

# Parameter we should pass to the X server
x_args = &quot;-nolisten tcp&quot;

# Offset to search for an available X server number.
# This number affects the DISPLAY env variable.
# Default is 1, setting it to 0 will make buggy OpenGL implementations
# (like the ATI one) work with qingy, but it will also make impossible
# to start an X server from console using startx without passing it
# extra parameters.
#x_server_offset = 1

# Scripts that should be executed just before/after qingy GUI is fired up/shut down
pre_gui_script  = &quot;/etc/qingy/pre_GUI.sh&quot;
#post_gui_script = &quot;/etc/qingy/post_GUI.sh&quot;

# Where are the screen savers?
screensavers_dir = &quot;/usr/lib/qingy/screensavers&quot;

#screensaver &quot;pixel&quot;
screensaver &quot;running_time&quot;#=&quot;%H:%S:%M&quot;

# Where are the themes?
themes_dir = &quot;/usr/share/qingy/themes&quot;

# What theme do you want (you can also specify &apos;random&apos;)
theme = random
#theme = &quot;default&quot;

# Who is allowed to shut down the system?
# Allowed options are &apos;everyone&apos;, &apos;root&apos;, &apos;noone&apos;
# default policy is everyone
# shutdown_policy = everyone

# How should latest user be calculated?
# global means get latest user that logged in using qingy from whichever tty
# tty    means get latest user that logged in using current tty
# default policy is global
#last_user_policy = global

# How should latest user session be calculated?
# user means get last session of each user
# tty  means get last session of current tty
# default policy is user
#last_session_policy = user

# What happens when we press the &apos;sleep&apos; button?
#sleep = &quot;/usr/local/sbin/hibernate&quot;

# wether we should clear background image during dialogs (default is no)...
# this is the default setting, it gets overridden if the theme you are using
# sets the same setting differently...
# clear_background = yes

# wether to allow session locking; if you enable this, when you try to
# switch to a qingy-controlled tty whose owner is not your current
# user, you will be asked for the password of that user before being
# allowed to continue. If you are root, of course, you can switch
# to any tty you chose to. Default setting is &apos;no&apos;.
#lock_sessions = yes

# How many times should we retry to fire app qingy interface
# before reverting to text mode? Default is 0...
#retries = 1

# these options are valid only if qingy is started from tty3
#tty = 3
#{
#	theme = &quot;fireplace&quot;
#	screensaver &quot;pixel&quot;

#	# Should we auto log in?
#	# Totally insecure, but very convenient ;-)
#	# Note that this section must be put inside a tty=n{} block
#	# Also, if you decide to use this feature, it is better
#	# that you also make this settings file readable only by root
#	autologin
#	{
#		username = &quot;myuser&quot;
#		password = &quot;mypassword&quot;
#		# You can also use &apos;session=lastsession&apos; to automatically choose last user session
#		session  = &quot;Text: emacs&quot;
#		# if set to &apos;no&apos;, qingy will autologin only once every system restart
#		relogin  = no
#	}
#}

keybindings
{
	prev_tty    = &quot;win&quot;      # switch to left tty
	next_tty    = &quot;menu&quot;     # switch to right tty
	poweroff    = &quot;ALT-p&quot;    # shutdown your system
	reboot      = &quot;ALT-r&quot;    # restart your system
	screensaver = &quot;ALT-s&quot;    # activate screen saver
	sleep       = &quot;ALT-z&quot;    # put machine to sleep
#	kill        = &quot;CTRL-c&quot;   # kill qingy
	text_mode   = &quot;CTRL-ESC&quot; # Revert to text mode
}

===============================================================================

I will try to see the output with --verbose as soon as I have time.
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>s4t4n@gentoo.org</who>
            <bug_when>2006-02-23 00:39:18 0000</bug_when>
            <thetext>From /etc/inittab:
c1:12345:respawn:/sbin/qingy tty1 linux
This is wrong. You should correct it as follows:
c1:12345:respawn:/sbin/qingy tty1

Also, make sure xdm is not added to runlevel default.

From /etc/qingy/settings:
pre_gui_script  = &quot;/etc/qingy/pre_GUI.sh&quot;
#post_gui_script = &quot;/etc/qingy/post_GUI.sh&quot;
I notice you decommented pre_gui_script: what did you put in &quot;/etc/qingy/pre_GUI.sh&quot;?

I notice there are some word-wrapped lines in /etc/qingy/settings, I assume this is bugzilla behaviour, and your actual file is not word wrapped.

Finally, what USE flags did you use when you emerged qingy?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>masse_nicolas@yahoo.fr</who>
            <bug_when>2006-02-23 13:37:07 0000</bug_when>
            <thetext>&gt; From /etc/inittab:
&gt; c1:12345:respawn:/sbin/qingy tty1 linux
&gt; This is wrong. You should correct it as follows:
&gt; c1:12345:respawn:/sbin/qingy tty1
done, but it change nothing


&gt; Also, make sure xdm is not added to runlevel default.
I&apos;m sure of that ;)

&gt; From /etc/qingy/settings:
&gt; pre_gui_script  = &quot;/etc/qingy/pre_GUI.sh&quot;
&gt; #post_gui_script = &quot;/etc/qingy/post_GUI.sh&quot;
&gt; I notice you decommented pre_gui_script: what did you put in
&gt; &quot;/etc/qingy/pre_GUI.sh&quot;?
Oups, I made that? Anyway, reverting this change has no effect


Also, I had the -v option to qingy, and now I have this message on the console:
Warning: Application exited withoud deinitialisation of directfb...

I assume the problem comes from that.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>s4t4n@gentoo.org</who>
            <bug_when>2006-02-24 01:44:31 0000</bug_when>
            <thetext>Try passing qingy the -t and -v arguments (in /etc/inittab). This will tell it to be verbose, but also to perform a text mode login. This way we can well wether there are problems with qingy authenticating you or with its graphical user interface.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>s4t4n@gentoo.org</who>
            <bug_when>2006-02-24 01:45:56 0000</bug_when>
            <thetext>And no, qingy exiting without deallocating DirectFB stuff is a feature, not a bug. This way it shuts down from DirectFB mode much faster (and DirectFB takes care to deinit all the stuff on qingy behalf)...
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>masse_nicolas@yahoo.fr</who>
            <bug_when>2006-02-26 04:39:09 0000</bug_when>
            <thetext>I&apos;ve tried to use the text mode ... it works, so the problem seems to be gui related.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>s4t4n@gentoo.org</who>
            <bug_when>2006-03-01 05:38:59 0000</bug_when>
            <thetext>Guess so. Does other DirectFB apps (like directvnc) work on your machine?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>masse_nicolas@yahoo.fr</who>
            <bug_when>2006-03-01 11:54:02 0000</bug_when>
            <thetext>yes, directfbterm works like a charm. The same is true for the flywithme demo (not in portage, i downloaded that directly from the directfb website).
I think that dfbsee is working to, even if I haven&apos;t tested that recently. 
Perhaps will I need to hack the code myself to see what happens?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>s4t4n@gentoo.org</who>
            <bug_when>2006-03-15 03:37:18 0000</bug_when>
            <thetext>Any help of this kind is always welcome. Anyway, since you can login with text-mode qingy, would you try recompiling it with crypto_openssl USE flag enabled, and see if it works?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>masse_nicolas@yahoo.fr</who>
            <bug_when>2006-03-16 13:21:44 0000</bug_when>
            <thetext>Created an attachment (id=82313)
Fixed ebuild(at least for me)

</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>masse_nicolas@yahoo.fr</who>
            <bug_when>2006-03-16 13:23:27 0000</bug_when>
            <thetext>Created an attachment (id=82314)
solve the problem

This patch fix the problem for me.
I also see that version 7.3 was out, I will try to see if this patch is also required or not (as 1st sight seems that yes, but...)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>s4t4n@gentoo.org</who>
            <bug_when>2006-03-17 00:35:10 0000</bug_when>
            <thetext>Interesting, you are the first user ever with a similar issue... and yes, 0.7.3 will have to be patched as well as that code section didn&apos;t change. I&apos;m going to test your fix and merge it upstream...
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>s4t4n@gentoo.org</who>
            <bug_when>2006-03-19 23:56:36 0000</bug_when>
            <thetext>Added new revision to Portage with a patch (similar to your own) that should solve your issue. Thanks for submitting this :-)</thetext>
          </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>82313</attachid>
            <date>2006-03-16 13:21 0000</date>
            <desc>Fixed ebuild(at least for me)</desc>
            <filename>qingy-0.7.1-r1.ebuild</filename>
            <type>application/octet-stream</type>
            <data encoding="base64">IyBDb3B5cmlnaHQgMTk5OS0yMDA2IEdlbnRvbyBGb3VuZGF0aW9uCiMgRGlzdHJpYnV0ZWQgdW5k
ZXIgdGhlIHRlcm1zIG9mIHRoZSBHTlUgR2VuZXJhbCBQdWJsaWMgTGljZW5zZSB2MgojICRIZWFk
ZXI6IC92YXIvY3Zzcm9vdC9nZW50b28teDg2L3N5cy1hcHBzL3Fpbmd5L3Fpbmd5LTAuNy4xLmVi
dWlsZCx2IDEuMSAyMDA2LzAyLzA3IDA4OjE2OjAzIHM0dDRuIEV4cCAkCgppbmhlcml0IGV1dGls
cyBkaXN0dXRpbHMKCkRFU0NSSVBUSU9OPSJhIERpcmVjdEZCIGdldHR5IHJlcGxhY2VtZW50IgpI
T01FUEFHRT0iaHR0cDovL3Fpbmd5LnNvdXJjZWZvcmdlLm5ldC8iClNSQ19VUkk9Im1pcnJvcjov
L3NvdXJjZWZvcmdlLyR7UE59LyR7UH0udGFyLmJ6MiIKCkxJQ0VOU0U9IkdQTC0yIgpTTE9UPSIw
IgpLRVlXT1JEUz0ifng4NiB+cHBjIH5hbWQ2NCIKSVVTRT0iY3J5cHRvX29wZW5zc2wgY3J5cHRv
X2xpYmdjcnlwdCBlbWFjcyBncG0gcGFtIHN0YXRpYyIKCkRFUEVORD0iPj1kZXYtbGlicy9EaXJl
Y3RGQi0wLjkuMTgKCWNyeXB0b19vcGVuc3NsPyAgICggPj1kZXYtbGlicy9vcGVuc3NsLTAuOS43
ZSApCgljcnlwdG9fbGliZ2NyeXB0PyAoID49ZGV2LWxpYnMvbGliZ2NyeXB0LTEuMi4xICkKCWVt
YWNzPyAgICAgICAgICAgICggdmlydHVhbC9lbWFjcyApCglwYW0/ICAgICAgICAgICAgICAoID49
c3lzLWxpYnMvcGFtLTAuNzUtcjExICkKCT49c3lzLWxpYnMvbmN1cnNlcy01LjQtcjYKCT49ZGV2
LXV0aWwvcGtnY29uZmlnLTAuMTIuMCIKCnNyY191bnBhY2soKQp7CglpZiB1c2UgY3J5cHRvX29w
ZW5zc2wgJiYgdXNlIGNyeXB0b19saWJnY3J5cHQ7IHRoZW4KCQllY2hvCgkJZWVycm9yICJZb3Ug
Y2FuIGhhdmUgb3BlbnNzbCBvciBsaWJnY3J5cHQgYXMgYSBjcnlwdG8gbGlicmFyeSwgbm90IGJv
dGguIgoJCWVlcnJvciAiUGxlYXNlIGNoZWNrIHlvdXIgVVNFIGZsYWdzLi4uIgoJCWVjaG8KCQlk
aWUgIlVTRSBmbGFncyBjaGVjayBmYWlsZWQiCglmaQoKCXVucGFjayAke0F9CgljZCAke1dPUktE
SVJ9LyR7UH0vc3JjL0RpcmVjdEZCLwoJcHdkCgllcGF0Y2ggJHtGSUxFU0RJUn0vbm9faGFuZ3Mu
cGF0Y2ggfHwgZGllCn0KCnNyY19jb21waWxlKCkKewoJbG9jYWwgY3J5cHRvX3N1cHBvcnQ9Ii0t
ZGlzYWJsZS1jcnlwdG8iCgoJdXNlIGNyeXB0b19vcGVuc3NsICAgJiYgY3J5cHRvX3N1cHBvcnQ9
Ii0tZW5hYmxlLWNyeXB0bz1vcGVuc3NsIgoJdXNlIGNyeXB0b19saWJnY3J5cHQgJiYgY3J5cHRv
X3N1cHBvcnQ9Ii0tZW5hYmxlLWNyeXB0bz1saWJnY3J5cHQiCgoJZWNvbmYgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIFwKCQktLXNiaW5kaXI9L3NiaW4gICAgICAgICAgICAgICAgICBc
CgkJLS1kaXNhYmxlLW9wdGltaXphdGlvbnMgICAgICAgICAgXAoJCWB1c2VfZW5hYmxlIGVtYWNz
YCAgICAgICAgICAgICAgIFwKCQlgdXNlX2VuYWJsZSBwYW1gICAgICAgICAgICAgICAgICBcCgkJ
YHVzZV9lbmFibGUgc3RhdGljIHN0YXRpYy1idWlsZGAgXAoJCWB1c2VfZW5hYmxlIGdwbSBncG0t
bG9ja2AgICAgICAgIFwKCQkke2NyeXB0b19zdXBwb3J0fSAgICAgICAgICAgICAgICBcCgkJfHwg
ZGllICJDb25maWd1cmF0aW9uIGZhaWxlZCIKCWVtYWtlIHx8IGRpZSAiQ29tcGlsYXRpb24gZmFp
bGVkIgp9CgpzcmNfaW5zdGFsbCgpCnsKCSMgY29weSBkb2N1bWVudGF0aW9uIG1hbnVhbGx5IGFz
IG1ha2UgaW5zdGFsbCBvbmx5IGluc3RhbGxzIGluZm8gZmlsZXMKCWRvZG9jIEFVVEhPUlMgQ2hh
bmdlTG9nIElOU1RBTEwgTkVXUyBSRUFETUUgVEhBTktTIFRPRE8KCgkjIGFuZCBmaW5hbGx5IGlu
c3RhbGwgdGhlIHByb2dyYW0KCW1ha2UgREVTVERJUj0ke0R9IGluc3RhbGwgfHwgZGllICJJbnN0
YWxsYXRpb24gZmFpbGVkIgoKCSMgU2V0IHRoZSBzZXR0aW5ncyBmaWxlIHVtYXNrIHRvIDYwMCwg
aW4gY2FzZSBzb21lYm9keQoJIyB3YW50cyB0byBtYWtlIHVzZSBvZiB0aGUgYXV0b2xvZ2luIGZl
YXR1cmUKCS9iaW4vY2htb2QgNjAwICR7RH0vZXRjL3Fpbmd5L3NldHRpbmdzCn0KCnBrZ19wb3N0
aW5zdCgpCnsKCWVpbmZvICJJbiBvcmRlciB0byB1c2UgcWluZ3kgeW91IG11c3QgZmlyc3QgZWRp
dCB5b3VyIC9ldGMvaW5pdHRhYiIKCWVpbmZvICJDaGVjayB0aGUgZG9jdW1lbnRhdGlvbiBhdCAk
e0hPTUVQQUdFfSIKCWVpbmZvICJmb3IgaW5zdHJ1Y3Rpb25zIG9uIGhvdyB0byBkbyB0aGF0LiIK
CWVjaG8KCWV3YXJuICJBbHNvIG5vdGUgdGhhdCBxaW5neSBkb2Vzbid0IHNlZW0gdG8gd29yayBy
ZWFsaWFibHkgd2l0aCIKCWV3YXJuICIyLjYuNyBrZXJuZWxzIGR1ZSB0byBwcm9ibGVtcyB3aXRo
IHRoZSBEaXJlY3RGQiBsaWJyYXJ5LiIKCWV3YXJuICJZb3VyIG1pbGVhZ2UgbWF5IHZhcnksIGJ1
dCBpdCBjb3VsZCBldmVuIGxvY2sgdXAgeW91ciBtYWNoaW5lISIKCWV3YXJuICJTZWUgaHR0cDov
L2J1Z3MuZ2VudG9vLm9yZy9zaG93X2J1Zy5jZ2k/aWQ9NTkzNDAiCglld2FybiAiYW5kIGh0dHA6
Ly9idWdzLmdlbnRvby5vcmcvc2hvd19idWcuY2dpP2lkPTYwNDAyIgoJZXdhcm4gIlVzZSBlaXRo
ZXIgYSAyLjYuNSBvciBhID49Mi42Ljgga2VybmVsISIKCglpZiB1c2UgY3J5cHRvX2xpYmdjcnlw
dDsgdGhlbgoJCWVjaG8KCQlld2FybiAiUGxlYXNlIG5vdGUgdGhhdCBsaWJnY3J5cHQgc3VwcG9y
dCBpcyBzdGlsbCBleHBlcmltZW50YWwuLi4iCgkJZWNobwoJCWVpbmZvICJZb3Ugd2lsbCBoYXZl
IHRvIGNyZWF0ZSBhIGtleSBwYWlyIHVzaW5nICdxaW5neS1rZXlnZW4nIgoJCWVjaG8KCQlld2Fy
biAiJ0xvZ2luIGZhaWxlZCcgbWVzc2FnZXMgZnJvbSBxaW5neSBHVUkgd2hlbiB5b3UgYXJlIHN1
cmUgeW91ciIKCQlld2FybiAicGFzc3dvcmQgaXMgY29ycmVjdCB1c3VhbGx5IG1lYW5zIHRoYXQg
eW91ciBrZXkgcGFpciBpcyBicm9rZW4iCgkJZXdhcm4gImFuZCB5b3UgaGF2ZSB0byBnZW5lcmF0
ZSBhIG5ldyBvbmUhIgoJZmkKfQo=
</data>        

          </attachment>
          <attachment
              isobsolete="0"
              ispatch="1"
              isprivate="0"
          >
            <attachid>82314</attachid>
            <date>2006-03-16 13:23 0000</date>
            <desc>solve the problem</desc>
            <filename>no_hangs.patch</filename>
            <type>text/plain</type>
            <data encoding="base64">LS0tIHFpbmd5LTAuNy4xL3NyYy9EaXJlY3RGQi9kaXJlY3RmYl9tb2RlLmMub2xkCTIwMDYtMDMt
MTUgMjM6NDY6MzYuMDAwMDAwMDAwICswMTAwCisrKyBxaW5neS0wLjcuMS9zcmMvRGlyZWN0RkIv
ZGlyZWN0ZmJfbW9kZS5jCTIwMDYtMDMtMTUgMjM6NDY6MDUuMDAwMDAwMDAwICswMTAwCkBAIC0y
NzIsNyArMjcyLDcgQEAKIC8qIAkJZnJlZSAoZGV2aWNlcyk7ICovCiAvKiAJCWRldmljZXMgPSBu
ZXh0OyAqLwogLyogCX0gKi8KKyAJaWYgKGRmYikgZGZiLT5SZWxlYXNlIChkZmIpOyAKLS8qIAlp
ZiAoZGZiKSBkZmItPlJlbGVhc2UgKGRmYik7ICovCiB9CiAKIHZvaWQgRGlyZWN0RkJfRXJyb3Io
KQo=
</data>        

          </attachment>
    </bug>

</bugzilla>