2006/7/9, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
A NOTE has been added to this issue. ====================================================================== http://www.yoper.com/bugtracker/view.php?id=137 ====================================================================== Reported By: DrRider Assigned To: ====================================================================== Project: Yoper 3.0 Alpha and Beta Issue ID: 137 Category: Reproducibility: always Severity: major Priority: normal Status: new Milestone: ====================================================================== Date Submitted: 04-05-2006 00:44 CEST Last Modified: 07-09-2006 13:49 CEST ====================================================================== Summary: GTK2 apps crash when open the dialog box Description: GTK2 apps crash (segmentation fault)when they were trying to open a dialog box such as open, preferences or some kinds of child window. There's no such thing when using gtk1 apps (xmms runs fine). ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0000145 xmms fails to start ====================================================================== ---------------------------------------------------------------------- Tobias G. - 04-05-06 17:13 ---------------------------------------------------------------------- Can you please add the following lines to /etc/ld.so.conf /usr/lib/qt-3.3/lib /opt/gnome/lib and run ldconfig -v and try rerunning the applications ? Everything does work smooth here, just that these 2 lines were missing for ld. ---------------------------------------------------------------------- fabian schindler - 05-19-06 15:44 ---------------------------------------------------------------------- Talking about smart --gui: After todays system upgrade and fixing the /etc/ld.so.conf file, it still crashes (gtk-package: [EMAIL PROTECTED]) Terminal output: [EMAIL PROTECTED] /home/test # smart --gui Xlib: connection to ":0.0" refused by server Xlib: No protocol specified Traceback (most recent call last): File "/usr/bin/smart", line 194, in ? main(sys.argv[1:]) File "/usr/bin/smart", line 161, in main forcelocks=opts.ignore_locks, loglevel=opts.log_level) File "/usr/lib/python2.4/site-packages/smart/__init__.py", line 126, in init iface.object = createInterface(ifacename, ctrl, command, argv) File "/usr/lib/python2.4/site-packages/smart/interface.py", line 150, in createInterface smart = __import__("smart.interfaces."+xname) File "/usr/lib/python2.4/site-packages/smart/interfaces/gtk/__init__.py", line 30, in ? import gtk File "/var/tmp/pygtk-buildroot/opt/gnome/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.py", line 38, in ? RuntimeError: could not open display [EMAIL PROTECTED] /home/test # ---------------------------------------------------------------------- fabian schindler - 05-20-06 12:47 ---------------------------------------------------------------------- Second result, using xhost + DISPLAY=:0 option: [EMAIL PROTECTED] /home/test # xhost + DISPLAY=:0 smart --gui Xlib: connection to ":0.0" refused by server Xlib: No protocol specified xhost: unable to open display ":0.0" [EMAIL PROTECTED] /home/test # ---------------------------------------------------------------------- fabian schindler - 05-21-06 16:49 ---------------------------------------------------------------------- Okay. I admit it. I was too stupid to find out that I had to launch xhost + as normal user. :p Everything works perfectly. Sorry for the mess. ---------------------------------------------------------------------- Musikolo - 07-09-06 13:49 ---------------------------------------------------------------------- I think those two lib paths should be added by default in the /etc/ld.so.conf. Otherwise every user will have to do it and I think it make no sense pleople have to repeat these steps once and again. This is necessary for lots of programas like firefox among others.
Yes, indeed they should. One attempt to adress such issues properly is this tool : http://www.yoper.com/wiki/index.php?title=Yopermaintain If you have Yoper 2.91 and my channel (tobias) in the beta repository in your smart configuration you should be able to update your linker cache properly with 'smart install yopermaintain' 'yopermaintain.sh -ul' This should rebuild the linker conf file , add some default entry and also keep any existing entry. Any feedback wanted. regards -- Tobias Gerschner Member of Board of Yoper Ltd. NZ Knowing is not enough; we must apply. Willing is not enough; we must do. _______________________________________________ yoper-dev mailing list [email protected] https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
