April 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 247747] New: gnome-main-menu blocks while statting recently-used documents
by bugzilla_noreply＠novell.com 03 Apr '07

03 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=247747 Summary: gnome-main-menu blocks while statting recently-used documents Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: hpj(a)novell.com QAContact: qa(a)suse.de I've some files on a server. Sometimes I open these files from Nautilus. The server broke and now gnome-main-menu will take 30 seconds from click to map. The problem appears to be that it's blocking on a gnome-vfs call that's supposed to extract metadata for a file on the missing server. This should not happen. It should use placeholder icons/other metadata while waiting for the information to be resolved. I think this is a large part of the reason why people find gnome-main-menu "slow". This is different from bug #229190. That bug looks like a bug in the metadata extractor that causes excessive resource usage. I'm attaching a trace. -- 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 255906] New: obsolete --with arguments in the gnome-session package
by bugzilla_noreply＠novell.com 03 Apr '07

03 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=255906 Summary: obsolete --with arguments in the gnome-session package Product: openSUSE 10.3 Version: Alpha 2 Platform: All OS/Version: All Status: NEW Severity: Minor Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome-build(a)forge.provo.novell.com ReportedBy: andreas.hanke(a)gmx-topmail.de QAContact: qa(a)suse.de In the gnome-session spec file I can find: %configure\ --with-reboot-command=/sbin/reboot\ --with-halt-command=/sbin/poweroff\ These --with-reboot-command and --with-halt-command arguments do not exist any more, they have been removed upstream: http://svn.gnome.org/viewcvs/gnome-session/trunk/configure.in?r1=3697&r2=37… -- 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 258425] New: Powersave/cpufreq not initialised properly on boot - subsequent ondemand governor issues
by bugzilla_noreply＠novell.com 03 Apr '07

03 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=258425 Summary: Powersave/cpufreq not initialised properly on boot - subsequent ondemand governor issues Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: karl-heinz_tm(a)hotmail.de QAContact: qa(a)suse.de Machine is Sony Z600TEK - somewhat old laptop (P3-700 Coppermine) Initialisation of frequency scaling fails during boot - system message claims that frequency scaling wasn't supported. Once machine is up, it's possible to enable frequency scaling by executing modprobe speedstep-lib relaxed_check=1 modprobe speedstep-smi smi_cmd=0x82 smi_port=0xb2 rchal restart However, enabling the ondemand governor still produces errors such as "liblazy (liblazy_dbus_send_method_call:71): Received error reply: Initialization of ondemand interface failed" and kernel messages such as "ondemand governor failed to load due to too long transition latency". Nevertheless, the ondemand governor does get activated, i.e. dynamic frequency changes do occur. Note, there were no such errors under opensuse 10.1 frequency scaling worked flawlessly there. -- 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 222522] New: blam installs unneeded static libraries
by bugzilla_noreply＠novell.com 03 Apr '07

03 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=222522 Summary: blam installs unneeded static libraries Product: openSUSE 10.3 Version: unspecified Platform: All OS/Version: All Status: NEW Severity: Minor Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: andreas.hanke(a)gmx-topmail.de QAContact: qa(a)suse.de blam installs libtool cruft: /usr/lib/blam/libblam.a /usr/lib/blam/libblam.la These are both unused and should be removed. -- 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 260311] New: [amarok] Closing main window on WM without System-Tray
by bugzilla_noreply＠novell.com 03 Apr '07

03 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=260311 Summary: [amarok] Closing main window on WM without System-Tray Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ma(a)novell.com QAContact: qa(a)suse.de Closing amaroks main window a popup informs that amarok keeps running in the System Tray. That's bad if the Window Manager does not provide a System Tray. Amarok is "lost", running somewhere in the background. You have to find out the PID and kill it by hand. The popup should at least offer an exit button, so one is able to let amarok exit. Would be cool, if amarok was able to detect the presence of a System Tray and behaved accordingly. -- 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 3

[Bug 260495] New: epiphany-dbus-connection-close-fix-thoenig-01.patch is obsolete
by bugzilla_noreply＠novell.com 03 Apr '07

03 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=260495 Summary: epiphany-dbus-connection-close-fix-thoenig-01.patch is obsolete Product: openSUSE 10.3 Version: Alpha 2plus Platform: All OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: andreas.hanke(a)gmx-topmail.de QAContact: qa(a)suse.de I just found the following in the epiphany.spec file: # FIXME: make this reapply, if necessary Patch14: epiphany-dbus-connection-close-fix-thoenig-01.patch No need to do that because the bug has been fixed upstream in a different way. -- 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 1

[Bug 250170] New: ddclient errors when run on line 1646 (or 1660 for 3.7.1)
by bugzilla_noreply＠novell.com 03 Apr '07

03 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=250170 Summary: ddclient errors when run on line 1646 (or 1660 for 3.7.1) Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joe_morris(a)ntm.org QAContact: qa(a)suse.de I got an error, Use of uninitialized value in concatenation (.) or string at /usr/sbin/ddclient line 1646. in version 3.7.0 which came with openSUSE 10.2. Troubleshooting, I tried to update to 3.7.1 from Factory, but though the line number changed, the error remained. The error has something to do with fw setting, which I did not use. I used the web method to update my IP. Tracking and tracing led me to the (I guess) fix from the author upstream, from the svn version of ddclient. The patch is (for version 3.7.1) is: --- ddclient-3.7.1/ddclient.orig 2007-01-25 16:42:22.000000000 +0100 +++ ddclient-3.7.1/ddclient 2007-02-12 16:09:53.000000000 +0100 @@ -1657,6 +1657,6 @@ debug("server = $server"); - debug("opt(fw = ",opt('fw')); - debug("glo fw = $globals{'fw'}"); + opt('fw') && debug("opt(fw = ",opt('fw'),")"); + $globals{'fw'} && debug("glo fw = $globals{'fw'}"); #if ( $globals{'ssl'} and $server ne $globals{'fw'} ) { ## always omit SSL for connections to local router This was found at http://sourceforge.net/forum/forum.php?thread_id=1677041&forum_id=399428 Another problem I found when rebuilding the rpm, is that /var/cache/ddclient/ddclient.cache file was not created (needs to be 600). I have been running my rebuilt package for about 2 weeks without any further problems. BTW, before finding the fix from the author, I changed the erring line to debug("glo fw = ",$globals{'fw'});, (even though I am not a programmer, it seemed to match the line above's syntax better), and it seemed to also work with that as well, but I will defer to the author's fix. -- 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 3

[Bug 162255] Samba use of credentials file is broken
by bugzilla_noreply＠novell.com 03 Apr '07

03 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=162255 dmair(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|samba-maintainers(a)SuSE.de |dmair(a)novell.com -- 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 0

[Bug 162255] Samba use of credentials file is broken
by bugzilla_noreply＠novell.com 03 Apr '07

03 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=162255 dmair(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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 0

[Bug 119900] Improve default mount options
by bugzilla_noreply＠novell.com 03 Apr '07

03 Apr '07

https://bugzilla.novell.com/show_bug.cgi?id=119900 ------- Comment #32 from sbrabec(a)novell.com 2007-04-03 11:05 MST ------- I have just discussed the winnt problem. Summary: - Devices using only 8+3 uppercase. We want them all-lowercase, no vfat records. I name these as msdos, but we can mount most of them as vfat, but with "lower" option without risk of file system breakage. - Devices using long filenames. We want "winnt" option and vfat records. It is not easy to discriminate between these cases. There are few ideas: - Guess: Check file system root. If there is no vfat item, guess as msdos, otherwise vfat. Will fail if file system root was created on vfat, but all files and directories were 8+3 all-uppercase. Will fail for just formatted card. - Guess + ask user: Guess. If there is no vfat entry, ask user "File system seems to use only 8+3 uppercase file names. Do you want to support long file names and/or use simple case conversion?" - Guess + ask user + remember: Remember USB ID or flash serial number and not as again. - USB ID list: If you are mounting USB device known to not support vfat (most cameras, some MP3 players,...), use msdos. - Camera DCIM list: Mount ro as vfat, look at DCIM/dcim, look at 100*, compare it with camera default names. If it is owned by 8+3 device, unmount and mount as msdos, otherwise remount rw. - Format stamp list: Check format stamp. If card was formatted on known 8+3 device, use msdos, otherwise vfat. - Optionally allow to store correct options on a (hidden) file in the file system root. There is one unwanted consequence of winnt flag: If you are copying a lowercase file from computer back to former MSDOS-only medium, it creates two entries in the file system structure - one uppercase MSDOS entry and one lowercase vfat entry. Some embedded systems may not accept 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 0