February 2006 - openSUSE Programming - openSUSE Mailing Lists

Problem with icons in QFileDialog
by Jose Thadeu Cavalcante 06 Mar '06

06 Mar '06

Hi, After I update Qt4 to the last update, when I open QFileDialog no more icons is showed in the dialog, no toolbar icons (no Parent Directory icon, ...), directories is showed like files. There are some ways to correct this? Thank you Thadeu

1 1

building kdesdk from svn.
by Steven T. Hatton 26 Feb '06

26 Feb '06

I know there are mailing lists which more directly focus on KDE issues, but this seems like a reasonable place to start. I'm trying to build the svn image of kdesdk. I have everything installed that I can imagine is relevant on my SUSE LINUX 10.0 (i586) VERSION = 10.0 system from the supplementary directory on the ftp site. This is what I checked out: svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdesdk I did a $ make -fMakefile.cvs $ ./configure --prefix=/home/hattons/opt/org/kdesdk This is the tail of the ./configure output: checking for Qt... libraries /usr/lib, headers /usr/include checking for moc... /usr/bin/moc checking for uic... Qt user interface compiler. uic: Unrecognized option Usage: /usr/lib/qt3/bin/uic [options] [mode] <uifile> Generate declaration: /usr/lib/qt3/bin/uic [options] <uifile> Generate implementation: /usr/lib/qt3/bin/uic [options] -impl <headerfile> <uifile> <headerfile> name of the declaration file Generate image collection: /usr/lib/qt3/bin/uic [options] -embed <project> <image1> <image2> <image3> ... or /usr/lib/qt3/bin/uic [options] -embed <project> -f <temporary file containing image names> <project> project name <image[1-N]> image files Generate subclass declaration: /usr/lib/qt3/bin/uic [options] -subdecl <subclassname> <baseclassheaderfile> <uifile> <subclassname> name of the subclass to generate <baseclassheaderfile> declaration file of the baseclass Generate subclass implementation: /usr/lib/qt3/bin/uic [options] -subimpl <subclassname> <subclassheaderfile> <uifile> <subclassname> name of the subclass to generate <subclassheaderfile> declaration file of the subclass Options: -o file Write output to file rather than stdout -pch file Add #include "file" as the first statement in implementation -nofwd Omit forward declarations of custom classes -nounload Don't unload plugins after processing -tr func Use func() instead of tr() for i18n -L path Additional plugin search path -version Display version of uic -help Display this information Qt user interface compiler 4.1.0. /usr/bin/uic checking for uic3... /usr/bin/uic3 checking whether uic supports -L ... no checking whether uic supports -nounload ... no checking for rcc... /usr/bin/rcc checking if Qt needs -ljpeg... no checking for rpath... yes checking for KDE... configure: error: I can't find the designer plugins. These are required and should have been installed by kdelibs Suggestions? Steven

1 1

Problem with DiGi rpmbuild --rebuild 40002347_B.src.rpm
by Boyd Lynn Gerber 24 Feb '06

24 Feb '06

Hello, I need some assistance. I may be too tired but I can not seem to figure out this problem. I am trying to get the Digi PC/Xem board working on SUSE Linux 10.0 retail version. I have done the following... 1. cd /usr/src/linux-2.6.13-15.8 2. make mrproper 3. make oldconfig Then... # rpmbuild --rebuild 40002347_B.src.rpm ... + '[' /var/tmp/dgap-buildroot = / ']' + CFLAGS='-O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2' + export CFLAGS + CXXFLAGS='-O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2' + export CXXFLAGS + FFLAGS='-O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2' + export FFLAGS + ./configure --host=i686-suse-linux --build=i686-suse-linux --target=i586-suse-linux --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info ... (cd driver; make all) make[1]: Entering directory `/usr/src/packages/BUILD/dgap-1.2/driver' make -C /lib/modules/2.6.13-15.8-smp/build SUBDIRS=$PWD modules MYPWD=/usr/src/packages/BUILD/dgap-1.2/driver make[2]: Entering directory `/usr/src/linux-2.6.13-15.8-obj/i386/smp' make -C ../../../linux-2.6.13-15.8 O=../linux-2.6.13-15.8-obj/i386/smp modules CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_driver.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_fep5.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_mgmt.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_parse.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_proc.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_trace.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_tty.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.o /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:183: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:200: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:228: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:245: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:262: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:279: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:296: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:313: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:330: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:347: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c: In function ‘dgap_tty_class_init’: /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:387: error: implicit declaration of function ‘class_simple_create’ /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:387: warning: assignment makes pointer from integer without a cast /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c: In function ‘dgap_tty_class_destroy’: /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:400: error: implicit declaration of function ‘class_simple_destroy’ /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c: In function ‘dgap_tty_register_device’: /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:571: error: implicit declaration of function ‘class_simple_device_add’ /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:573: warning: assignment makes pointer from integer without a cast /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:582: warning: assignment makes pointer from integer without a cast /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c: In function ‘dgap_tty_unregister_device’: /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:605: error: implicit declaration of function ‘class_simple_device_remove’ make[5]: *** [/usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.o] Error 1 make[4]: *** [_module_/usr/src/packages/BUILD/dgap-1.2/driver] Error 2 make[3]: *** [modules] Error 2 make[2]: *** [modules] Error 2 make[2]: Leaving directory `/usr/src/linux-2.6.13-15.8-obj/i386/smp' make[1]: *** [build] Error 2 make[1]: Leaving directory `/usr/src/packages/BUILD/dgap-1.2/driver' make: *** [build] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.23324 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.23324 (%build) Can someone shed some light on what to do to fix this? Thanks, -- Boyd Gerber <gerberb(a)zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047

1 1

MIDI problems
by Rich Wilson 23 Feb '06

23 Feb '06

I'm having trouble using MIDI with Suse 10.0 eval. When I plug in a USB MIDI interface, the following appears in /var/log/messages: Feb 23 19:30:05 linux kernel: usb 2-3: new full speed USB device using ohci_hcd and address 2 Feb 23 19:30:06 linux kernel: usb-midi: Found MIDISTREAMING on dev 0582:0052, iface 0 Feb 23 19:30:06 linux kernel: usb-midi: Found MIDIStreaming device corresponding to Release 1.00 of spec. Feb 23 19:30:06 linux kernel: usb-midi: Found IN Jack 0x10 EMBEDDED Feb 23 19:30:06 linux kernel: usb-midi: Found IN Jack 0x20 EXTERNAL Feb 23 19:30:06 linux kernel: usb-midi: Found OUT Jack 0x30 EMBEDDED, 1 pins Feb 23 19:30:06 linux kernel: usb-midi: Found OUT Jack 0x40 EXTERNAL, 1 pins Feb 23 19:30:06 linux kernel: usb-midi: fetchString(2) Feb 23 19:30:06 linux kernel: usb-midi: fetchString = 4 Feb 23 19:30:06 linux kernel: usbmidi: found [ UM-1 ] (0x0582:0x0052), attached: Feb 23 19:30:06 linux kernel: usbmidi: /dev/midi00: in (ep:81 cid: 0 bufsiz:64) out (ep:01 cid: 0 bufsiz:64) Feb 23 19:30:06 linux kernel: usbcore: registered new driver midi Yet, nothing appears in /proc/asound/devices linux:/var/log # cat /proc/asound/devices 25: [0- 1]: digital audio capture 16: [0- 0]: digital audio playback 24: [0- 0]: digital audio capture 0: [0- 0]: ctl 1: : sequencer 33: : timer linux:/var/log # This makes it difficult for my program to open the raw MIDI interface from Alsa. Note that this works properly on older Suse versions. What's going on here? Thanks. Rich -- Rich Wilson richaw at gmail.com 425-337-7129

2 1

Updating SuSE 10.0 kernel to fix USB-storage bugs?
by Erich Boleyn 23 Feb '06

23 Feb '06

[First note, I'm not on the list, so please copy me with any replies!] Greetings all, I apologize if this is a semi-FAQ, but couldn't find reference to it anywhere on the net with search terms I tried, including archives of the list... I have installed SuSE Linux 10.0 commercial on my Wife's desktop, an Athlon64 3200+ on an ASUS K8V SE motherboard (VIA K8T800 chipset), and in general it's been working well, but I have had a problem that I haven't had time to completely debug myself, but figured there would likely be some knowledge on the list about it: -- There seems to be a rare but real USB-storage bug in the 2.6.13 series of kernels, and it affects both our Camera and the iPod Shuffle I got her. It causes indefinite hangs of the USB bus after some random amount of data has transferred (usually more than 1 song, between 15 and 100 songs, say), and it also runs the transfers to the iPod quite slowly. NOTE: I tried using a newer kernel to fix this because I had found references to USB-storage bugs in large data transfers in vanilla 2.6.13 kernels which were fixed in 2.6.14 series kernels. The feeling on the part of those posting seemed to be if there were ever glitches in the transfers, the 2.6.13 series kernel's USB storage drivers just gave up in bad and sometimes unrecoverable ways, and the symptoms to the hangs they observed were the same as the ones I saw. -- The only fix I could make in the time I have has been to replace it with a later kernel. I have tried both SuSE 10.1 Beta 4 and Fedora Core 4 update kernels (trying to get distribution bug-fixes in). -- After replacing the kernel, USB-storage works like a dream, fast and no observed hang or hiccoughs... -- But on the newer kernels, the desktop automounting of USB-storage now is broken. So, is there some either 2.6.13-specific or SuSE-specific feature which makes the desktop automounting work that I could fix? I patch kernels all the time, just don't have time to fully debug what mechanisms are failing and why... there didn't seem any obvious change in kernel configuration after looking at a few (like KOBJECT_UEVENT, which was functioning fine, and resmgrd was taking events)... Anyway, would appreciate any info on the topic that could shed light into how to get USB working clean/fast *and* keep desktop automounting working! (preferred solution is getting the automounting working correctly on the newer kernel, I think...) -- Erich Stefan Boleyn <erich(a)uruk.org> http://www.uruk.org/ "Reality is truly stranger than fiction; Probably why fiction is so popular"

1 1

What is the "most standard" c++ md5 header?
by Steven T. Hatton 20 Feb '06

20 Feb '06

I want to determine if files have been modified by the user so that my program will leave them unmodified when doing updates. Like YaST does. I plan on using MD5 to generate a hash to check when visiting files. I have sourcecode that claims to be genuine RSA MD5, so getting something that works isn't a problem. I would, however, prefer to build against a "standard" library rather than something I add to my own source tree just to get things working. Is there a good candidate for providing MD5 hashing that will be available on most systems? Steven

2 1