December 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 335540] New: Xorg-Driver "intel" causes "black screen" on Laptop with Intel 855GM chipset
by bugzilla_noreply＠novell.com 05 Dec '07

05 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=335540 Summary: Xorg-Driver "intel" causes "black screen" on Laptop with Intel 855GM chipset Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: sndirsch(a)novell.com ReportedBy: matthias.nissen(a)gmail.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Customer Older Intel graphics chips are supported by two drivers ( "i810" and "intel" ). On my Laptop, Acer Travelmate 291LCi with an intel 855 GM chipset and a 15" XGA TFT LCD, the i810 works proper, but the "intel" driver only shows a black screen. Steps to reproduce: Just install SuSE 10.3 on the laptop an reboot: At the point, where the display manager should appear, the monitor turns all black. Work around: Switch on a console, using STRG Alt F2 (German keyboard, ctrl, alt, f2 on English keyboard), log in as root and switch to i810 driver using sax2: sax2 -r -m 0=i810 The bug is reproducible on other linux distributions to, eg. the recent version of Kanotix live CD shows a similar behaviour. Installed Version: Xorg 7.2, recent Package. Further Information: Adding the Option "NoDCC" to Section "Device" seems to solve the Problem, too (found out by chance). -- 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.

1 17

[Bug 337412] New: ncursesw.h missing
by bugzilla_noreply＠novell.com 05 Dec '07

05 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=337412 Summary: ncursesw.h missing Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: dauti(a)oeh.tu-graz.ac.at QAContact: qa(a)suse.de Found By: --- Dear opensuse-team, I found two small bugs with the ncurses libraries: (a) Neither in ncurses-5.6-41 nor in ncurses-devel-5.6-41 the header file ncursesw/ncurses.h is installed. Please include that in an updated package... (b) The ncurses headerfiles are probably installed in the wrong directory - according to ncurses5-config, it should be found in /usr/include/ncurses: $ ncurses5-config --cflags -I/usr/include/ncurses But in ncurses-devel-5.6-41 the file is installed in /usr/include. (since this ist the default path, that is not a big problem). -- 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.

1 3

[Bug 333465] New: YaST2 hangs because of dangling reference in y2base
by bugzilla_noreply＠novell.com 05 Dec '07

05 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=333465 Summary: YaST2 hangs because of dangling reference in y2base Product: openSUSE 10.3 Version: Final Platform: 32bit OS/Version: openSUSE 10.3 Status: NEW Severity: Blocker Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: estellnb(a)gmail.com QAContact: jsrain(a)novell.com Found By: Customer > yast2 -i $(cat susedvd.lis) ThereUpon YaST2 has hanged because of dangling reference in y2base. [ctrl]-[C] YaST got signal 2 at YCP file /usr/share/YaST2/clients/sw_single.ycp:187 YaST got signal 3 at YCP file /usr/share/YaST2/clients/sw_single.ycp:187 killall yast2 Beendet Unfortunately even a reboot could not free the lock on the package management system; yast2-message (zypper ditto): Zugriff auf Paketmanagement gescheitert anderer Prozeß blockiert ... In a fact this has revealed two problems: * dangling reference in y2base * missing signal handlers for YaST (quit & free lock); free lock on shutdown -- 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.

1 10

[Bug 299638] New: software.opensuse.org: ugly/huge grey footer
by bugzilla_noreply＠novell.com 05 Dec '07

05 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=299638 Summary: software.opensuse.org: ugly/huge grey footer Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: BuildService AssignedTo: fs(a)novell.com ReportedBy: stbinner(a)novell.com QAContact: adrian(a)novell.com CC: rlihm(a)novell.com Found By: Development The grey footer on software.opensuse.org pages is huge and ugly. Please remove the static (!?) line "This page was last modified on 06/14/2007." and put the remaining text into one line (like on news.opensuse.org) -- 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.

1 3

[Bug 342612] New: bznew should operate on .tgz files
by bugzilla_noreply＠novell.com 05 Dec '07

05 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=342612 Summary: bznew should operate on .tgz files Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: psychonaut(a)nothingisreal.com QAContact: qa(a)suse.de Found By: Customer The openSUSE package for bzip2 (bzip2-1.0.3-36) contains a shell script /usr/bin/bznew for automatically converting gzip archives to bzip2 archives. This program is not present in the official bzip2 distribution, so I assume this is an addition by openSUSE. The program operates well on files with the extension .gz, but does not recognize the extension .tgz (a common abbreviation for .tar.gz). Please update bznew such that it will operate on .tgz files. -- 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.

1 3

[Bug 334146] New: Description of SARG option is wrong
by bugzilla_noreply＠novell.com 05 Dec '07

05 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=334146 Summary: Description of SARG option is wrong Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gankov.andrey(a)inbox.ru QAContact: qa(a)suse.de Found By: --- In different places has different description of sarg options -x and -z. when run "sarg -h" has one description when run "sarg -x" has secondary description when run "man sarg" has wrong description. Screen shot attachment. -- 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.

1 6

[Bug 345205] New: Latest update of samba 3.0.26a-3. 3 breaks vmware server authentication
by bugzilla_noreply＠novell.com 05 Dec '07

05 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=345205 Summary: Latest update of samba 3.0.26a-3.3 breaks vmware server authentication Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: sloncho(a)gmail.com QAContact: qa(a)suse.de Found By: --- Hi, I have opensuse 10.3, i386, running vmware server 1.0.4-56528. I'm using pam.d authentication, so I can authenticate against NT domain. My user authenticates against that domain as well. After the latest update of samba (incl. cifs, libsmb, samba-client, samba-winbind) to ver. 3.0.26a-3.3 vmware server console can not log to the server any more (local server). Downgrading to 3.0.26a-3 reverts to the previous situation, where everything was working. When I try to connect locally run vmware-server-console (under my domain user) to the local server, I see these errors in the vmware log file: Nov 30 09:27:51: app| New connection on socket server-vmdb from host localhost (ip address: local) , user: MYDOMAIN\sunny Nov 30 09:27:51: app| Failed to get password entry for : MYDOMAIN\sunny. Reason: Unknown error 4294967295 Nov 30 09:27:51: app| SP: New user session for user: MYDOMAIN\sunny, pos: 0 Nov 30 09:27:51: app| Failed to get password entry for : MYDOMAIN\sunny. Reason: Unknown error 4294967295 Nov 30 09:27:51: app| Failed to get password entry for : MYDOMAIN\sunny. Reason: Unknown error 4294967295 Nov 30 09:27:51: app| SP: Failed to impersonate as : MYDOMAIN\sunny Nov 30 09:27:51: app| Failed to get password entry for : MYDOMAIN\sunny. Reason: Unknown error 4294967295 Nov 30 09:27:51: app| Failed to get password entry for : MYDOMAIN\sunny. Reason: Unknown error 4294967295 Nov 30 09:27:51: app| SP: Failed to impersonate as : MYDOMAIN\sunny I gave restarted smbd and winbindd, and I can log in to my machine using the new samba stuff. Only the vmware server is affected, as far as I can see. Cheers -- 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.

1 5

[Bug 346182] New: Clicking on options in the Installation Settings does not have any effect
by bugzilla_noreply＠novell.com 05 Dec '07

05 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=346182 Summary: Clicking on options in the Installation Settings does not have any effect Product: openSUSE 11.0 Version: unspecified Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jdluhos(a)novell.com QAContact: jsrain(a)novell.com Found By: --- In the Installation Settings screen of the installer, the subtitles in the selection window (Partitioning, Software, Locale Settings) should be clickable but they are not; clicking on them does not do anything (well, it moves the focus, but nothing else). The pulldown menu below the window works okay. -- 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.

1 4

[Bug 344900] New: kernel does not support minix
by bugzilla_noreply＠novell.com 05 Dec '07

05 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=344900 Summary: kernel does not support minix Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: zoli(a)polarhome.com QAContact: qa(a)suse.de Found By: Customer hello, in pre 10.3 opensuse releases linux kernel supported minix fs format of initrd. Seems it is removed form the kernel and kernel support just cpio. Wonder is it possible to put back the minix support into the official kernel. There are product and applications that depend on such issues and I am getting tired of all these "revolutionary" changes in opensuse. Every new opensuse release is a challenge for whole development. I agree that you need to add new features, but why remove the old already well proven parts. Have you ever considered what implication is for all opensuse customers that use your linux distribution in professional purpose. And this minix issue is not a sole problem. dev usb and removed static executable from init_tools and who know what more have you changed just to make your users life more complicated. In general: Additions are welcome, but do not remove features. Here not this bug in particular but the approach is a major issue. Consider backwards compatibility with higher respect. Thank you in advance. Regards, Z -- 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.

1 3

[Bug 344195] New: PROBLEM: Periodic interupts stop after a few seconds under 8192Hz clock freq
by bugzilla_noreply＠novell.com 05 Dec '07

05 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=344195 Summary: PROBLEM:Periodic interupts stop after a few seconds under 8192Hz clock freq Product: SUSE Linux 10.1 Version: Final Platform: HP OS/Version: SLES 9 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: huxx(a)huawei.com QAContact: qa(a)suse.de Found By: Development ---------------------------------------------------- Most recent kernel where this bug did not occur: 2.6.5-7.191 ---------------------------------------------------- Distribution: SuSE Linux Enterprise Server 9 Service Pack Version 3 ---------------------------------------------------- Hardware Environment: HP-DL380-G5 Intel(R) Xeon(R) CPU 5110 @ 1.60GHz 4GB RAM ---------------------------------------------------- Software Environment: GCC 3.3.3 and my RTC test program: #include <stdio.h> #include <stdlib.h> #include <pthread.h> #include <linux/rtc.h> #include <sys/ioctl.h> #include <sys/time.h> #include <sys/types.h> #include <fcntl.h> #include <unistd.h> #include <errno.h> unsigned long long counter = 0; int fd = -1; void *thread_entry(void *param) { unsigned long data = 0; for (;;) { // This read system call will block each timer scale interval (1/8192s) read(fd, &data, sizeof(unsigned long)); counter++; } } int main(void) { int i, retval, irqcount = 0; unsigned long hz, pie; struct rtc_time rtc_tm; pthread_t thread; fd = open ("/dev/rtc", O_RDONLY); if (fd == -1) { perror("/dev/rtc"); exit(errno); } /* The frequencies 128Hz, 256Hz, ... 8192Hz are only allowed for root. */ retval = ioctl(fd, RTC_IRQP_SET, 4096); if (retval == -1) { perror("ioctl"); exit(errno); } ioctl(fd, RTC_IRQP_READ, &hz); fprintf(stderr, "%ldHz\r\n", hz); /* Enable periodic interrupts */ retval = ioctl(fd, RTC_PIE_ON, 0); if (retval == -1) { perror("ioctl"); exit(errno); } ioctl(fd, RTC_IRQP_READ, &hz); fprintf(stderr, " %ldHz\r\n", hz); pthread_create(&thread, NULL, thread_entry, NULL); for (;;) { ioctl(fd, RTC_PIE_ON, 0); ioctl(fd, RTC_IRQP_READ, &hz); fprintf(stderr, "counter is %ld, %ldHz\r\n", counter, hz); fflush(stderr); sleep(1); } return 0; } /* end main */ ---------------------------------------------------- Problem Description: Under 2.6.5-7.191, the test program goes well: # ./rtc_test counter is 0, 0Hz counter is 4100, 0Hz counter is 8203, 0Hz counter is 12304, 0Hz counter is 16405, 0Hz counter is 20508, 0Hz counter is 24609, 0Hz counter is 28712, 0Hz But, under 2.6.5-7.244, the periodic interupts freezed after a few seconds: # ./rtc_test counter is 0, 1024Hz counter is 4108, 1024Hz counter is 4547, 1024Hz counter is 4547, 1024Hz counter is 4547, 1024Hz counter is 4547, 1024Hz counter is 4547, 1024Hz // The counter freezed at random value # cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 0: 378101 360121 360123 360121 IO-APIC-edge timer 1: 9 2 0 0 IO-APIC-edge i8042 2: 0 0 0 0 XT-PIC cascade 8: 1 2 0 4547 IO-APIC-edge rtc 9: 0 0 0 0 IO-APIC-level acpi 12: 58 0 0 0 IO-APIC-edge i8042 14: 48 0 9 4 IO-APIC-edge ide0 16: 1 0 1 1 IO-APIC-level eth0 17: 119067 122348 7501 2424 IO-APIC-level cciss0, eth1 21: 31 0 32 36 IO-APIC-level uhci_hcd NMI: 1458101 1458028 1458027 1458026 LOC: 1458018 1458007 1458018 1458018 ERR: 0 MIS: 0 ---------------------------------------------------- Steps to reproduce: 1.Save the test program as 'rtc.c' file. 2.Use 'gcc -l pthread -o rtc_test rtc.c' command to compile and link it. 3.Use './rtc_test' command to run and wait for bug comes. The only difference between SLES9SP2 and SLES9SP3 is that boot_hpet_disable is set to 1 in SLES9SP2. So, periodic interrupt handler is rtc_interrupt in SLES9SP2 while it is hpet_rtc_interrupt in SLES9SP3. -- 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.

1 5