July 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 293974] New: firmware test does not work
by bugzilla_noreply＠novell.com 30 Jul '08

30 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=293974 Summary: firmware test does not work Product: openSUSE 10.3 Version: Alpha 6 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: asvetter(a)cip.physik.uni-wuerzburg.de QAContact: jsrain(a)novell.com CC: asklein(a)wpax13.physik.uni-wuerzburg.de Found By: --- In alpha 6 the firmware test is broken on i386 and x86_64 DVDs. The image biostest does not contain the directory /usr/share/firmwarekit As a result the system falls back to ncurses UI and states in a red box: An error occurred during installation or similar - thats from human memory which is error prone ;-) -- 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 232403] New: Broken DSDT on ACER Travelmate 661
by bugzilla_noreply＠novell.com 30 Jul '08

30 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=232403 Summary: Broken DSDT on ACER Travelmate 661 Product: openSUSE 10.2 Version: RC 5 Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: michael.eschweiler(a)t-online.de QAContact: qa(a)suse.de As s2ram didn't even work with a minimum console (init=/bin/bash) I fixed the DSDT as discribed at http://forums.gentoo.org/viewtopic.php?t=122145 and integrated in the initrd. Now s2ram -f -s works fine - but only on runlevel 3 (with framebuffer). At runlevel 5 it still doesn't work but this seems to be a problem of the x-server (see bug 230123). -- 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 11

[Bug 219929] New: kde menu -> system seems to stat mount points
by bugzilla_noreply＠novell.com 30 Jul '08

30 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=219929 Summary: kde menu -> system seems to stat mount points Product: SUSE Linux 10.1 Version: Final Platform: PowerPC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: olh(a)novell.com QAContact: kde-maintainers(a)suse.de selecting 'System' from the KDE menu seems to trigger a stat on all mount points. It did have for a few seconds until it displayed the actual contents of the 'System' submenu. Now imagine if any of the mount points were a hanging NFS mount point... Luckily there was only a scsi drive in stand by mode. -- 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 21

[Bug 271307] New: Kickoff freezes KDE-Desktop
by bugzilla_noreply＠novell.com 30 Jul '08

30 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=271307 Summary: Kickoff freezes KDE-Desktop Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: funtasyspace(a)yahoo.com QAContact: qa(a)suse.de I sometimes experience, that clicking the SUSE icon in KDE/Kicker (Kickoff modus) freezes my desktop. The chameleon icon changes it's color to orange, but nothing happens... the menu won't open. I can't click icons on the desktop anymore, only existing apps seem to be left working. Killing the session using Ctrl+Alt+Backspace and logging in again won't help, as soon as I click the Kickoff icon the desktop freezes again. However, right clicking the Kickoff icon and switching to the old KDE menu style is possible and won't freeze the desktop. Clicking the old KDE menu button brings up the menu and everything works fine, no freezes. Switching back to Kickoff mode and left clicking the menu icon freezes the desktop immediately. So this is definitely a Kickoff related problem. Until yesterday I didn't know the reason for this behavior, why it only sometimes happen and how to reproduce it. Well, yesterday I realized, that it happens when I remove the network cable from my notebook and click the Kickoff icon afterwards. As long as I have no network connection, the desktop is frozen. But if I re-plug-in the network cable, the desktop recovers ater about 10 - 20 seconds and the menu appears and everything is working fine again. Here is the scenario how to reproduce it: - running KDE session with network connection - remove network cable and take the notebook with me to the couch, kitchen, ... whatever - left clicking the Kickoff menu icon to start some application (e.g. OpenOffice) freezes the desktop - I go back to my desk and plug-in the network cable, after 10 - 20 seconds the menu opens and KDE is usable again May it be, that Kickoff tries to access some NFS shares before the menu shows up? I have some NFS shares mounted (non of them is essential to the system or KDE) and they are not unmounted automatically when you just remove the network cable, so my first guess would be that this is causing Kickoff to hang!? Well, it seems my guess was good. If I do a 'rcnfs stop' before removing the network cable, Kickoff won't freeze when I click the menu icon. Of course this is no solution, because users without root rights can't shutdown the NFS client before they remove the network cable to move their notebook somewhere else. So I suggest to revisit the Kickoff code and consider that disconnected NFS shares can freeze Kickoff/Kicker/Desktop. -- 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 9

[Bug 280811] New: mono-winforms and libX11.so
by bugzilla_noreply＠novell.com 30 Jul '08

30 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=280811 Summary: mono-winforms and libX11.so Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de I am using the build service's mono to give winforms a try. Using the sample program using System; using System.Windows.Forms; public class MainClass { public static void Main(string[] args) { MessageBox.Show("Hello World!"); } } and compiling with: gmcs Main.cs -r:System.Windows.Forms that works. However, running it does not: Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.XplatUI ---> System.DllNotFoundException: libX11.so at (wrapper managed-to-native) System.Windows.Forms.XplatUIX11:XInitThreads () at System.Windows.Forms.XplatUIX11..ctor () [0x00000] at System.Windows.Forms.XplatUIX11.GetInstance () [0x00000] at System.Windows.Forms.XplatUI..cctor () [0x00000] --- End of inner exception stack trace --- at <0x00000> <unknown method> at System.Windows.Forms.Form.get_CreateParams () [0x00000] at System.Windows.Forms.MessageBox+MessageBoxForm.get_CreateParams () [0x00000] at System.Windows.Forms.Control.SizeFromClientSize (Size clientSize) [0x00000] at System.Windows.Forms.Control..ctor () [0x00000] at System.Windows.Forms.ScrollableControl..ctor () [0x00000] at System.Windows.Forms.ContainerControl..ctor () [0x00000] at System.Windows.Forms.Form..ctor () [0x00000] at System.Windows.Forms.MessageBox+MessageBoxForm..ctor (IWin32Window owner, System.String text, System.String caption, MessageBoxButtons buttons, MessageBoxIcon icon) [0x00000] at (wrapper remoting-invoke-with-check) MessageBoxForm:.ctor (System.Windows.Forms.IWin32Window,string,string,System.Windows.Forms.MessageBoxButtons,System.Windows.Forms.MessageBoxIcon) at System.Windows.Forms.MessageBox.Show (System.String text) [0x00000] at MainClass.Main (System.String[] args) [0x00000] The most important part there appears to be: Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.XplatUI ---> System.DllNotFoundException: libX11.so so I looked for libX11.so and did not find it. I did find libX11.so.6 in /usr/lib, so I symlinked it (which is itself a symlink) to libX11.so and everything worked. However, no package creates /usr/lib/libX11.so and neither does ldconfig: jnelson@linux-lel4:~/Projects/Forms1> rpm -qf /usr/lib/libX11.so file /usr/lib/libX11.so is not owned by any package jnelson@linux-lel4:~/Projects/Forms1> consequently, something must be wrong with the mono package in that it depends on a file which does not exist. :-( I hope this proves useful and that by the time openSUSE 10.3 is out that mono with winforms will work "out of the 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, or are watching someone who is.

1 5

[Bug 280537] New: libzypp / YaST: Show name of process which locks the database
by bugzilla_noreply＠novell.com 30 Jul '08

30 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=280537 Summary: libzypp / YaST: Show name of process which locks the database Product: openSUSE 10.3 Version: Alpha 4plus Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp AssignedTo: kkaempf(a)novell.com ReportedBy: burnus(a)gmx.de QAContact: kkaempf(a)novell.com Yast shows errors like: "ERROR Another process accesses the package database. Package management not possible. [ Ok ]" Expected: There is more information available about the process, e.g.: "The process 'zypper' is currently accessing the package database." or "The process 'y2base' is currently accessing the package database." Reasoning: Sometimes the DB is locked and it is not obvious why it is locked/what locks it. -- 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

[Bug 293356] New: Yast package install: Package manager access failed: offer "Abort"
by bugzilla_noreply＠novell.com 30 Jul '08

30 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=293356 Summary: Yast package install: Package manager access failed: offer "Abort" Product: openSUSE 10.3 Version: Alpha 4plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: burnus(a)gmx.de QAContact: jsrain(a)novell.com Found By: --- Currently, YaST2 sw_single shows the message: "Accessing the Package management failed [...] Would you like to continue without to continue without having access to the package management or retry to access it?" Well, what if I want to do neither but want to Cancel or Abort? Well, the answer is that YaST2 closes if one clicks "Continue". Expected: - Change "Continue" into "Cancel" or "Abort" If there are cases where "Continue" works (e.g. printer setup) then it should offer three options: "Continue" "Retry" "Abort" or "Cancel". -- 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 12

[Bug 295550] New: samba rejects password because it is "..too long."
by bugzilla_noreply＠novell.com 30 Jul '08

30 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=295550 Summary: samba rejects password because it is "..too long." Product: openSUSE 10.3 Version: Alpha 6 Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dpecka(a)novell.com QAContact: qa(a)suse.de Found By: --- input: mount -t cifs -o username=testcount,password=iamthemasterofknownuniverse //ntz-testing/testcount /mnt/samba/ output: password too long --- reproduced too at os.10.2. I thing, that this is result of last samba patches, because i used this kind of password previously with no problem.. --- password of this lenght can be entered manually.. -- 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 19

[Bug 275533] New: GRUB keymap
by bugzilla_noreply＠novell.com 29 Jul '08

29 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=275533 Summary: GRUB keymap Product: openSUSE 10.2 Version: Final Platform: 32bit OS/Version: openSUSE 10.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: spyhawk(a)mysunrise.ch QAContact: qa(a)suse.de I've a SwissFrench keyboard, and have installed openSUSE in French (with selection of CH_fr keyboard). After the end of install, the keyboard map on GRUB is an AZERTY (FR_fr) and I can't change that. It's very annoying, because the French keyboard (AZERTY) is very different of the SwissFrench keyboard (QWERTZ). I assume the problem is the same with other X_fr keyboard. -- 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 10

[Bug 230704] New: yast2/zypper incompatibility: online_update_setup sets invalid zypper option "-d"
by bugzilla_noreply＠novell.com 29 Jul '08

29 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=230704 Summary: yast2/zypper incompatibility: online_update_setup sets invalid zypper option "-d" Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: matthias.andree(a)gmx.de QAContact: jsrain(a)novell.com When configuring an online update with YaST2's online_update_setup feature and picking the "only download packages", yast writes "zypper up -y -t patch -d" into /etc/cron.d/yast2-online-update which leads to cron mail to root: Unknown option -d Which seems correct as far as the current zypper release is concerned. Deactivating the "only download packages" checkbox in YaST2 removes the -d from said cron.d file. The machine in question has been updated from SUSE Linux 10.0 and runs openSUSE 10.2, but this problem does not appear to be related to 10.0->10.2 updates, but a general incompatibility between YaST's online_update_setup module and zypper. Packages in question are: zypper-0.6.13-6 yast2-online-update-2.14.2-10 -- 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 14