January 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 222955] New: Dummy YaST (YCP) Module for Testing ZYPP
by bugzilla_noreply＠novell.com 17 Dec '08

17 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=222955 Summary: Dummy YaST (YCP) Module for Testing ZYPP Product: openSUSE 10.3 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: mvidner(a)novell.com ReportedBy: locilka(a)novell.com QAContact: jsrain(a)novell.com When I was adding a testsuite into the yast2-update to keep bug 153576 behavior controlled for future I ran into the problem with ZYPP trying to create some directories during initialization (somewhere deep in includes probably in Package.ycp). This was impossible to fix because testsuites are running with autobuild's permissions and one needs to be root to create these directories. That's why the testsuite couldn't pass. Please, create a dummy YCP module that would, e.g., initialize the ZYPP's Target in the /tmp directory or any other simple solution. It should be part of the yast2-testsuite package. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 2

[Bug 223895] New: YaST (Installation) - redirecting stdout/stderr to the /var/log/YaST2/run-std*
by bugzilla_noreply＠novell.com 17 Dec '08

17 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=223895 Summary: YaST (Installation) - redirecting stdout/stderr to the /var/log/YaST2/run-std* Product: openSUSE 10.3 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: mvidner(a)novell.com ReportedBy: locilka(a)novell.com QAContact: jsrain(a)novell.com CC: ms(a)novell.com, suse-beta(a)cboltz.de It's not easy to catch all error messages that are produced by running (broken) YaST. Some Perl modules complain about wrong commands, for instance, and there is no way how to report these errors well. One way is to find your camera and take a monitor-shot :) This could be fixed by redirecting stdout and stderr to some files under /var/log/YaST2/stdout and /var/log/YaST2/stderr or maybe even 2>>/var/log/YaST2/y2log Only redirecting doesn't make sense for same cases, so using `tee` would be probably better. There are at least two places where this should be implemented: * /sbin/yast2 * Installation startup scripts (YaST2.call) ..and maybe others. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 6

[Bug 205663] New: YCP (yast2-core) - Reference to Integer doesn't work
by bugzilla_noreply＠novell.com 17 Dec '08

17 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=205663 Summary: YCP (yast2-core) - Reference to Integer doesn't work Product: openSUSE 10.2 Version: Alpha 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: mvidner(a)novell.com ReportedBy: locilka(a)novell.com QAContact: jsrain(a)novell.com See this example: { void ChangeInteger (integer & in) { y2milestone("Changing from %1", in); in = 2; } integer in1 = 1; y2milestone("Old Integer: %1", in1); ChangeInteger(in1); y2milestone("New Integer: %1", in1); } It should work but ycpc reports: parsing 'ref_int.ycp' ref_int.ycp:4 [Parser] type mismatch in assignment ref_int.ycp:4 [Parser] Expected 'integer &', seen 'const integer'. Error This works for 'map' and 'string' (both tested), I hope it works for the other types as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 5

[Bug 223754] New: libexif: GPS Latitude not detected
by bugzilla_noreply＠novell.com 17 Dec '08

17 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=223754 Summary: libexif: GPS Latitude not detected Product: openSUSE 10.2 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: meissner(a)novell.com ReportedBy: kukuk(a)novell.com QAContact: qa(a)suse.de libexif shows for jpegs with GPS data: GPS tag version |0x02, 0x02, 0x00, 0x00 InteroperabilityInde|N InteroperabilityVers|49.00, 27.00, 2.21 East or West Longitu|E Longitude |11.00, 4.00, 12.74 Altitude reference |0x00 Altitude |335.00 While exiftool shows: GPS Version ID : 2.2.0.0 GPS Latitude Ref : North GPS Latitude : 49 deg 27' 2.21" GPS Longitude Ref : East GPS Longitude : 11 deg 4' 12.74" GPS Altitude Ref : Above Sea Level GPS Altitude : 335 metres GPS Time Stamp : 13:19:42 GPS Img Direction Ref : True North GPS Img Direction : 0 GPS Map Datum : WGS-84 GPS Date Stamp : 2006:11:25 libexif finds the Latitude data, but does not display it correct. Or exiftool is wrong here, I didn't found a second tool to verify. ~kukuk/Export/20061125141939-00.jpg is the used test image. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 2

[Bug 230912] New: customer center config. -- "creating source ..." not stoppable
by bugzilla_noreply＠novell.com 16 Dec '08

16 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=230912 Summary: customer center config. -- "creating source ..." not stoppable Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)novell.com Well, run it, and try to stop -- impossible. The close widget is not responding, there is not abort button, I have to wait until CCC is finished. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 13

[Bug 237309] New: yast and libzypp do not respect the disk space reserved for root user
by bugzilla_noreply＠novell.com 16 Dec '08

16 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=237309 Summary: yast and libzypp do not respect the disk space reserved for root user Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: lslezak(a)novell.com ReportedBy: lslezak(a)novell.com QAContact: jsrain(a)novell.com If e.g. root partition has 70MB free space and 500MB free space reserved for root user yast reports 570MB free. But installation of a package which is greater than 70MB fails: installing package kdelibs3-devel-doc-3.5.5-45 needs 335MB on the / filesystem Yast should display the non=root free space. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 4

[Bug 234545] New: sometimes the sound is broken with alsa and the maestro3 driver
by bugzilla_noreply＠novell.com 09 Dec '08

09 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=234545 Summary: sometimes the sound is broken with alsa and the maestro3 driver Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: SuSE Linux 10.0 Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: admin(a)eregion.de QAContact: qa(a)suse.de CC: suse-beta(a)cboltz.de BugsThisDependsOn: 192264 +++ This bug was initially created as a copy of Bug #192264 +++ Sometimes in KDE, the sound gets "broken" (all sounds sound like they're played with several times the speed than they're supposed to). in some cases, restarting artsd helps; in other cases, terminating arts, then reloading the alsa modules helps; in some cases, a reboot is needed. hwinfo --sound says: 19: PCI 08.0: 0401 Multimedia audio controller [Created at pci.286] UDI: /org/freedesktop/Hal/devices/pci_125d_1998 Unique ID: RE4e.vQKD5pEhpk5 SysFS ID: /devices/pci0000:00/0000:00:08.0 SysFS BusID: 0000:00:08.0 Hardware Class: sound Model: "Dell ES1983S Maestro-3i PCI Audio Accelerator" Vendor: pci 0x125d "ESS Technology" Device: pci 0x1998 "ES1983S Maestro-3i PCI Audio Accelerator" SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x00b0 Revision: 0x10 Driver: "Maestro3" Driver Modules: "snd_maestro3" I/O Ports: 0xd800-0xd8ff (rw) Memory Range: 0xf3ffe000-0xf3ffffff (rw,non-prefetchable) IRQ: 5 (38118 events) Module Alias: "pci:v0000125Dd00001998sv00001028sd000000B0bc04sc01i00" Driver Info #0: Driver Status: snd_maestro3 is active Driver Activation Cmd: "modprobe snd_maestro3" Config Status: cfg=yes, avail=yes, need=no, active=unknown -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 8

[Bug 233344] New: No sound from Crystal Audio sound card
by bugzilla_noreply＠novell.com 09 Dec '08

09 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=233344 Summary: No sound from Crystal Audio sound card Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: VladCodrea(a)mail.utexas.edu QAContact: qa(a)suse.de The Crystal Audio sound card on my Dell Inspiron 3200 laptop is not properly detected and no sound applications work. Using YAST to detect legacy audio cards freezes the system. When I try to play a WAVE file, I get: user@laptop:~> playwave compilation-ogg-q0.wav ALSA lib confmisc.c:670:(snd_func_card_driver) cannot find card '0' ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device ALSA lib confmisc.c:391:(snd_func_concat) error evaluating strings ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_concat returned error: No such device ALSA lib confmisc.c:1070:(snd_func_refer) error evaluating name ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_refer returned error: No such device ALSA lib conf.c:3968:(snd_config_expand) Evaluate error: No such device ALSA lib pcm.c:2143:(snd_pcm_open_noupdate) Unknown PCM default Opened audio at 22050 Hz 16 bit stereo On an earlier Debian installation (kernel 2.6.19) I was able to hear very faint music through the laptop speakers, but the application (mpg321) still triggered ALSA errors. Another person who has an Inspiron 3200 reported (http://audacityteam.org/forum/thread/184) that the sound card works after the following commands: modprobe sound modprobe ad1848 insmod uart401 insmod cs4232 io=0x530 irq=5 dma=1 dma2=0 mpuio=0x330 mpuirq=5 However, typing these commands doesn't enable sound for me on OpenSuse 10.2. I am attaching the dmesg below. I'd be happy to provide any other information, try out patches, or give developers SSH access to the affected computer. Thank you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 22

[Bug 205721] New: getgrgid_r always returns nonsense
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=205721 Summary: getgrgid_r always returns nonsense Product: openSUSE 10.2 Version: Alpha 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dmueller(a)novell.com QAContact: qa(a)suse.de getgrgid_r seems to fail. works on 10.1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 13

[Bug 213941] New: LSB: ttyname_r() returns an incorrect error value on a bad filedescriptor
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=213941 Summary: LSB: ttyname_r() returns an incorrect error value on a bad filedescriptor Product: openSUSE 10.2 Version: Alpha 5 plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jdluhos(a)novell.com QAContact: qa(a)suse.de Found by the LSB runtime test: When a ttyname_r() function is called on a filedescriptor that is already closed (and previously referred to a valid terminal device), the ENOTTY error is reported. This is incorrect, the EBADF error should be reported in this case. Please find the attached program that demonstrates this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 7