December 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 340527] New: module ipmi_si declares itself able to handle random devices
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=340527 Summary: module ipmi_si declares itself able to handle random devices Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: anicka(a)novell.com QAContact: qa(a)suse.de Found By: --- Module ipmi_si uses for matching some ascii mess instead of valid pci ids. from modules.pcimap on my 10.3 box: ipmi_si 0x0000103c 0x0000121a 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 ipmi_si 0xffffffff 0xffffffff 0xffffffff 0xffffffff 0x000c0700 0xffffff00 0x0 ipmi_si 0x6f6c6e75 0x775f6461 0x5f6e6568 0x74706d65 0x00000079 0x00000000 0x0 ipmi_si 0x64696d70 0x00000000 0x00000000 0x00000000 0x00000004 0x00000000 0x0 and on 10.2: ipmi_si 0x0000103c 0x0000121a 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 ipmi_si 0xffffffff 0xffffffff 0xffffffff 0xffffffff 0x000c0700 0x000c0700 0x0 ipmi_si 0x64797274 0x75616665 0x0073746c 0x65707974 0x00000000 0x00000000 0x0 ipmi_si 0x0000001e 0x00000000 0x00000000 0x00000000 0x72646461 0x00000073 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x0 ipmi_si 0x00000008 0x00000000 0x00000000 0x00000000 0x74726f70 0x00000073 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x73717269 0x00000000 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x73676572 0x69636170 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x73676572 0x73657a69 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x73676572 0x74666968 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x76616c73 0x64615f65 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x0 ipmi_si 0x00000004 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x0 In result it is willing to handle nearly any device on my machine, ie: 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1) Subsystem: ASUSTeK Computer Inc. Unknown device 8141 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 217 Memory at febd7000 (32-bit, non-prefetchable) [size=4K] I/O ports at d080 [size=8] Capabilities: <access denied> Kernel driver: forcedeth Kernel module ipmi_si, forcedeth -- 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 305351] New: During installation selecting bluetooth and networkmanager fails
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=305351 Summary: During installation selecting bluetooth and networkmanager fails Product: openSUSE 10.3 Version: Beta 2 Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: clarkt(a)cnsp.com QAContact: jsrain(a)novell.com Found By: Beta-Customer During the installation of 10.3 B1/2, at the network section, network manager is disabled. Selecting it shows that NM is now to be enabled. After finishing up the install and login in, NM is not started. Starting Yast and going to network cards, general tap, NM shows that is is not selected. You have to turn it on at this point. In the last section, hardware, bluetooth is selected to be enabled, with or without an adapter in place. After a clean boot, bluetooth services are not started. A check of the runtime services shows that bluetooth was not started. -- 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 11

[Bug 333670] New: Cannot select directory by mouse in fingerprint configuration
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=333670 Summary: Cannot select directory by mouse in fingerprint configuration Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: uli.2001(a)gmx.de QAContact: jsrain(a)novell.com Found By: --- In Yast->Hardware->Fingerprint reader, I try to select the directory for fingerprint files by mouse. A dialog opens, I select a directory, but it does not end up in the text box. -- 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 11

[Bug 301143] New: Many YaST2 string errors.
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=301143 Summary: Many YaST2 string errors. Product: openSUSE 10.3 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: benji.weber(a)gmail.com QAContact: jsrain(a)novell.com CC: ke(a)novell.com Found By: --- I identified the following errors whilst translating the YaST strings into English. There are many more minor grammatical errors, but these are the most significant. I have translated them out for now, but they should be fixed at some point. add-on-creator: Resign all packages with selected key -> Re-sign all packages with selected key /usr/bin/unzip does not exists -> /usr/bin/unzip does not exist Re&sign all packages with selected key -> Re-&sign all packages with selected key autofs: You must configure LDAP to use the autofs modul. -> You must configure LDAP to use the autofs module. You can do it by using the YaST2 ldap modul. -> You can do it by using the YaST2 ldap module. Faild to bind to the LDAP server. -> Failed to bind to the LDAP server. The Path is the absolute pfad of the directory on -> The Path is the absolute path of the directory on the backup: Delete removes the selected constrain.\n -> Delete removes the selected constraint.\n base: An internal error occured when integrating additional workflow. -> An internal error occurred when integrating additional workflow. bootloader: Serial Connection Parameters lets you define the paramters to use\n -> Serial Connection Parameters lets you define the parameters to use\n cd creator: The dependecies cannot be resolved.\n -> The dependencies cannot be resolved.\n ftp-server (n.b. this is a bit of a mess, I've made my best guesses without context) : Cannot create upload direcotry for anonymous connections! -> Cannot create upload directory for anonymous connections! &Refuse Conections Without SSL/TLS -> &Refuse Connections Without SSL/TLS Example of correct imput set_anon_dir=/srv/ftp -> Example of correct input set_anon_dir=/srv/ftp Example of correct imput set_authen_dir=/srv/ftp -> Example of correct input set_authen_dir=/srv/ftp Uknown option. -> Unknown option. Refuse Conections Without SSL/TLS Refuse connections that don't use \n -> Refuse Connections Without SSL/TLS Refuse connections that don't use \n vsftpd only: If you want that anonymous users can upload you \n need existing directory with allowed writing in home directory after login.\n -> vsftpd only: If you want to allow anonymous users to upload you \n need an existing directory that allows writing in home directory after login.\n vsftpd only: If you want that anonymous users can create directories you \n need existing directory with allowed writing in home directory after login.\n -> vsftpd only: If you want to allow anonymous users to create directories you \n need existing directory that allows writing in home directory after login.\n If you want that \"anonymous\" users can upload\n you need to create directory with allowed writing.\n -> If you want to allow \"anonymous\" users to upload\n you need to create a directory that allows writing.\n If you want that \"anonymous\" users can upload\n you need directory with allowed writing.\n -> If you want to allow \"anonymous\" users to upload\n you need a directory that allows writing \n If you want that \"anonymous\" users can create directories\n you need to create directory with allowed writing.\n -> If you want that \"anonymous\" users can create directories\n you need to create directory that allows writing.\n If you want that \"anonymous\" users can create directories\n you need directory with allowed writing.\n -> If you want to allow \"anonymous\" users to create directories\n you need a directory that allows writing.\n installation: The current installation system does not seem\n to have configured network. -> The current installation system does not seem\n to have a configured network. Probe floppy disks devices -> Probe floppy disk devices Various instances of "Catalog" should be "Repository" now. You have better enable\n those you want to include in the upgrade process. -> You had better enable\n those you want to include in the upgrade process. iscsi-client: InitiatorName from iBFT and from /etc/iscsi/initiatorname.iscsi differ.\n Old initiatorname will be replaced by value from iBFT and create a backup.\n If you want to use different initiatorname change it in BIOS. -> InitiatorName from iBFT and from /etc/iscsi/initiatorname.iscsi differ.\n Old initiatorname will be replaced by value from iBFT and create a backup.\n If you want to use different initiatorname change it in BIOS. kdump: For applying changes is necessary reboot. -> For applying changes it is necessary to reboot. Wrong options was used. -> Wrong options were used. Size of allocate memory MB -> Size of memory to alocate (MB) Path of file which includes passwort (plain text file) -> Path of file which includes password (plain text file) You need specify -> You need to specify linux-user-mgmt: The eDirctory context (existing or created here) where the Linux/UNIX\n -> The eDirectory context (existing or created here) where the Linux/UNIX\n mail: This modul will configure your MTA with LDAP support. -> This module will configure your MTA with LDAP support. This will corrupt your actuall configuration. -> This will corrupt your actual configuration. network: Configuration Error : not initialized interface! -> Configuration Error : uninitialised interface! online-update: Installation Source module. -> Software Repositories module. This options allows to share printer via network.\n -> This option shares the printer via the network.\n security: &Shutdown Bhaviour of KDM: -> &Shutdown Behaviour of KDM: storage: a random password at system startup for you. This means, you will loose all \n -> a random password at system startup for you. This means, you will lose all \n <tt>writeback</tt> -- Data ordering is not preserved. No performanc impact.\n -> <tt>writeback</tt> -- Data ordering is not preserved. No performance impact.\n -- 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 160823] /var/adm/mount: Device is busy
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=160823#c13 --- Comment #13 from Hubert Mantel <mantel(a)novell.com> 2007-12-03 00:53:03 MST --- What would we gain by doing so? Not showing some error message to the user? If this is the goal, we could as well just suppress the error message. The real bug is somewhere else: YaST does not clean up correctly. If this bug is so severe that it needs fixing, it should be fixed in the right place and not being worked around by suppressing a correct error message. -- 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 0

[Bug 160823] /var/adm/mount: Device is busy
by bugzilla_noreply＠novell.com 03 Dec '07

03 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=160823#c12 Klaus Kämpf <kkaempf(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mantel(a)novell.com, snwint(a)novell.com --- Comment #12 from Klaus Kämpf <kkaempf(a)novell.com> 2007-12-02 21:24:53 MST --- This should be answered by our linuxrc/inst-sys experts. Putting them in CC. -- 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 0

[Bug 152522] Ioctl VT_ACTIVATE cause root shell in xterm to output many useless newlines
by bugzilla_noreply＠novell.com 02 Dec '07

02 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=152522#c26 Stefan Dirsch <sndirsch(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Enhancement |Minor --- Comment #26 from Stefan Dirsch <sndirsch(a)novell.com> 2007-12-02 15:30:03 MST --- At least minor. -- 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 0

[Bug 106886] Disable possibility to turn on Slowkeys( accessx) by default?
by bugzilla_noreply＠novell.com 02 Dec '07

02 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=106886#c13 Stefan Dirsch <sndirsch(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME --- Comment #13 from Stefan Dirsch <sndirsch(a)novell.com> 2007-12-02 15:14:10 MST --- Since I never was able to enable Slowkeys on any default installation in the last years I'm finally closing this one as WORKSFORME. -- 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 0

[Bug 343045] New: /etc/apache2/conf.d/trac. conf should include PythonInterpreter main_interpreter
by bugzilla_noreply＠novell.com 02 Dec '07

02 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=343045 Summary: /etc/apache2/conf.d/trac.conf should include PythonInterpreter main_interpreter Product: openSUSE 10.3 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Apache AssignedTo: herbert(a)graeber-clan.de ReportedBy: lmuelle(a)novell.com QAContact: qa(a)suse.de Found By: --- http://issues.apache.org/jira/browse/MODPYTHON-77 explains why 'PythonInterpreter main_interpreter' must be set. It's also the suggestion of http://trac.edgewall.org/wiki/TracModPython Adding 'PythonInterpreter main_interpreter' to the trac.conf solved my issue. -- 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 343649] New: trac config file attribute in the spec file list
by bugzilla_noreply＠novell.com 02 Dec '07

02 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=343649 Summary: trac config file attribute in the spec file list Product: openSUSE 11.0 Version: unspecified Platform: Other OS/Version: openSUSE 11.0 Status: NEW Severity: Enhancement Priority: P5 - None Component: Apache AssignedTo: herbert(a)graeber-clan.de ReportedBy: lmuelle(a)novell.com QAContact: qa(a)suse.de Found By: --- An update to trac moves /etc/apache2/conf.d/trac.conf to trac.conf.rpmsave. This happens even if the old configuration still works. To allow an user a smoother update I suggest to mark the file as %config(noreplace) in the spec file. Then trac even works with the previous running configuration without any manual interaction. -- 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 1