September 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 613898] New: hal is not started for the first boot after complete install
by bugzilla_noreply＠novell.com 18 Feb '15

18 Feb '15

http://bugzilla.novell.com/show_bug.cgi?id=613898 http://bugzilla.novell.com/show_bug.cgi?id=613898#c0 Summary: hal is not started for the first boot after complete install Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 7 Platform: 32bit OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jdd(a)dodin.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.2.4) Gecko/20100527 SUSE/3.6.4-2.2 Firefox/3.0.3, Ant.com Toolbar 1.1 When first trying to use 11.3 (just before RC1), I notice no of my devices where visible. K3b complain that hal was not started, and in fact "rchal status" shown it was not started; Went to YaST, runlevels, to see Hal was quoted "yes*". I could there start Hal without problem and now all works. Reproducible: Didn't try Steps to Reproduce: I have a BD write running, I will restart after that and see if hal is now started -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 39

[Bug 548018] New: Critical error in KHTML causing many crashes
by bugzilla_noreply＠novell.com 18 Feb '15

18 Feb '15

http://bugzilla.novell.com/show_bug.cgi?id=548018 Summary: Critical error in KHTML causing many crashes Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: suseer(a)mail.ru QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-3.2 Firefox/3.5.3 This bug is very annoying. In kopete and other apps: https://bugs.kde.org/show_bug.cgi?id=209960 please, update kde factory repository. Reproducible: Always Steps to Reproduce: 1.Open "Settings" in kopete 2.Switch to chat style changing section 3.Press 'Cancel' Actual Results: Kopete crashes Expected Results: Just close settings window :) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 529057] New: desktop-data-openSUSE: use inline by default for menus
by bugzilla_noreply＠novell.com 18 Feb '15

18 Feb '15

http://bugzilla.novell.com/show_bug.cgi?id=529057 Summary: desktop-data-openSUSE: use inline by default for menus Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: vuntz(a)novell.com QAContact: qa(a)suse.de CC: beineri(a)opensuse.org Found By: --- I'd like to add <DefaultLayout inline="true"/> to applications.menu by default. It will make the content of submenus appear in their parent if there are less than 4 items in the submenu. (we can use inline_limit="3" if we want 3, etc.) My understanding is that KDE already implements something like this, but without DefaultLayout. In GNOME, we need this to have a good behavior (we're just following the menu specification). Stephan, what do you think? -- Configure bugmail: http://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 542098] New: NTP init script fails if keysdir defined in ntp.conf
by bugzilla_noreply＠novell.com 11 Feb '15

11 Feb '15

http://bugzilla.novell.com/show_bug.cgi?id=542098 Summary: NTP init script fails if keysdir defined in ntp.conf Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: juha.mustonen(a)eads.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8 (.NET CLR 3.5.30729) NTP init script uses incorrect awk regular expression when attempting to find the name of NTP symmetric keys file. The expression matches both "keys" and "keysdir" keywords, when only the first was intended. See patch below. --- /etc/init.d/ntp.orig 2009-09-25 12:31:02.000000000 +0300 +++ /etc/init.d/ntp 2009-09-25 12:31:15.000000000 +0300 @@ -55,7 +55,7 @@ NTPDC_BIN="/usr/sbin/ntpdc" -NTP_KEYS=$(awk '/^keys/ { print $2 }' $NTP_CONF) +NTP_KEYS=$(awk '/^keys[[:blank:]]/ { print $2 }' $NTP_CONF) NTP_KEYID=$(awk '/^requestkey[[:blank:]]/ { print $2 }' $NTP_CONF) NTP_PASSWD=$(test -n "$NTP_KEYS" -a -n "$NTP_KEYID" -a -r "$NTP_KEYS" && awk '$0 ~ key { print $3 }' key="^[[:blank:]]*$NTP_KEYID[[:blank:]]" $NTP_KEYS) Reproducible: Always Steps to Reproduce: 1. Add line "keysdir /etc/ntp" to /etc/ntp.conf with appropriate parameters. 2. Restart ntp. Actual Results: Init scripts complains "NTP key id not defined" and fails to restart ntp. -- Configure bugmail: http://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 492261] New: zypper should support --continue or something like it
by bugzilla_noreply＠novell.com 23 Dec '14

23 Dec '14

http://bugzilla.novell.com/show_bug.cgi?id=492261 Summary: zypper should support --continue or something like it Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-1.1.6 Firefox/3.0.7 zypper supports -n (--non-interactive) more or less However, any minor download error aborts an entire operation unnecessarily. Not infrequently various mirrors may disconnect or fail to provide for many reasons a file when asked, and this is how zypper currently behaves: Retrieving package kdebase4-workspace-debuginfo-4.2.2-217.3.x86_64 (10/130), 36.8 M (160.1 M unpacked) Retrieving: kdebase4-workspace-debuginfo-4.2.2-217.3.x86_64.rpm [error] File './x86_64/kdebase4-workspace-debuginfo-4.2.2-217.3.x86_64.rpm' not found on medium 'http://opensuse.ca.unixheads.org/repositories/KDE:/KDE4:/Factory:/Desktop/o…' Abort, retry, ignore? [A/r/i]: a Failed to provide Package kdebase4-workspace-debuginfo-4.2.2-217.3. Do you want to retry retrieval? [KDE:KDE4:Factory:Desktop|http://opensuse.ca.unixheads.org/repositories/KDE:…] Can't provide file './x86_64/kdebase4-workspace-debuginfo-4.2.2-217.3.x86_64.rpm' from repository 'KDE:KDE4:Factory:Desktop' History: - File './x86_64/kdebase4-workspace-debuginfo-4.2.2-217.3.x86_64.rpm' not found on medium 'http://opensuse.ca.unixheads.org/repositories/KDE:/KDE4:/Factory:/Desktop/o…' - Can't provide ./x86_64/kdebase4-workspace-debuginfo-4.2.2-217.3.x86_64.rpm : Media Exception Abort, retry, ignore? [A/r/i]: a Problem occured during or after installation or removal of packages: Installation aborted by user Please see the above error message for a hint. It seems to me that --non-interactive should support a --continue mode where it ignores non-fatal errors and continues. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 497924] New: DHCP client NOT running, failed eth0 interface could not be set up until now
by bugzilla_noreply＠novell.com 14 Dec '14

14 Dec '14

http://bugzilla.novell.com/show_bug.cgi?id=497924 Summary: DHCP client NOT running, failed eth0 interface could not be set up until now Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ufest(a)mudal.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1.1 Firefox/3.0.8 The installation is an upgrade from opensuse 11.0 to opensuse 11.1. The init-script network run not correctly on boot time. On command line rcnetwork start is ok. The configuration use dhcp4 client. Error message on boot: eth0: RTL8168b/8111b at 0xf8f6e000, 00:17:31:87:44:be, IRQ 17 doneWaiting for mandatory devices: eth0 __NSC__ eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) eth0 DHCP client NOT running eth0 is down failed eth0 interface could not be set up until now Solution: script-part old: for a in $(type_filter `ls -A /sys/class/net/`); do test -d /sys/class/net/$a || continue t=`get_iface_type $a` case "$t" in eth|tr|ib|wlan) STAMPFILE=$STAMPFILE_STUB`cat /sys/class/net/$a/ifindex` if [ "$MODE" = onboot -a "$ACTION" = start ] ; then # skip interfaces (with active drivers) # but not yet prepared by an # ifup -o hotplug # call is triggered in udev rules. # (may need rename to their final name) if [ ! -e "$STAMPFILE" ] ; then continue fi fi ;; lo|wlan_aux) continue ;; esac for b in $VIRTUAL_IFACES ; do if [ "$a" = "$b" ] ; then NOT_PHYSICAL_IFACES="$NOT_PHYSICAL_IFACES $a" continue 2 fi done PHYSICAL_IFACES="$PHYSICAL_IFACES $a" done script-part new: for a in $(type_filter `ls -A /sys/class/net/`); do test -d /sys/class/net/$a || continue t=`get_iface_type $a` case "$t" in eth|tr|ib|wlan) STAMPFILE=$STAMPFILE_STUB`cat /sys/class/net/$a/ifindex` if [ "$MODE" = onboot -a "$ACTION" = start ] ; then # skip interfaces (with active drivers) # but not yet prepared by an # ifup -o hotplug # call is triggered in udev rules. # (may need rename to their final name) if [ ! -e "$STAMPFILE" ] ; then true # correction # continue # correction fi fi ;; lo|wlan_aux) continue ;; esac for b in $VIRTUAL_IFACES ; do if [ "$a" = "$b" ] ; then NOT_PHYSICAL_IFACES="$NOT_PHYSICAL_IFACES $a" continue 2 fi done PHYSICAL_IFACES="$PHYSICAL_IFACES $a" done Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://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 603609] New: OBS signing key expired
by bugzilla_noreply＠novell.com 14 Dec '14

14 Dec '14

http://bugzilla.novell.com/show_bug.cgi?id=603609 http://bugzilla.novell.com/show_bug.cgi?id=603609#c0 Summary: OBS signing key expired Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: linz(a)li-pro.net QAContact: adrian(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.9) Gecko/20100402 Ubuntu/9.10 (karmic) Firefox/3.5.9 The repository signing key for openSUSE:Tools and home:rexut expired at 1 April 2010. Could you please create and use a current GPG key? It seems the same problam as Bug 596080. apt-get on Debian outputs a warning; that's how I stumbled over it. Reproducible: Always Steps to Reproduce: Use apt-get on Debian W: GPG error: http://download.opensuse.org Release: The following signatures were invalid: KEYEXPIRED 1270156083 W: GPG error: http://download.opensuse.org Release: The following signatures were invalid: KEYEXPIRED 1270155834 Reproducible: Always Steps to Reproduce: 1. sudo apt-get update 2. sudo apt-key list Actual Results: 1. ... W: GPG error: http://download.opensuse.org Release: The following signatures were invalid: KEYEXPIRED 1270156083 W: GPG error: http://download.opensuse.org Release: The following signatures were invalid: KEYEXPIRED 1270155834 2. ... pub 1024D/EEFEFDE9 2008-01-22 [expired: 2010-04-01] uid openSUSE:Tools OBS Project <openSUSE:Tools@build.opensuse.org> pub 1024D/8C1AD9D3 2008-01-22 [expired: 2010-04-01] uid home:rexut OBS Project <home:rexut@build.opensuse.org> -- Configure bugmail: http://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 615417] New: activating apparmor: very slow (or it hanged up)
by bugzilla_noreply＠novell.com 14 Dec '14

14 Dec '14

http://bugzilla.novell.com/show_bug.cgi?id=615417 http://bugzilla.novell.com/show_bug.cgi?id=615417#c0 Summary: activating apparmor: very slow (or it hanged up) Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 7 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: jeffm(a)novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (Windows NT 6.1; U; en) Presto/2.5.24 Version/10.53 I wanted to try AppArmor, so I launched AppArmor Configuration (Yast), then I enabled AppArmor, then I clicked to configure AA profiles and I wait for over an hour and all I see is busy cursor mouse. a) even if the task is really time consuming, in such case there should be more visual feedback than just a mouse cursor -- a dialog with progress and steps would be nice However I am not sure if this is really slow or program went into infinite loop. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://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 631491] New: stale state file disables networking (after suspend)
by bugzilla_noreply＠novell.com 14 Dec '14

14 Dec '14

http://bugzilla.novell.com/show_bug.cgi?id=631491 http://bugzilla.novell.com/show_bug.cgi?id=631491#c0 Summary: stale state file disables networking (after suspend) Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hmuelle(a)novell.com QAContact: qa(a)suse.de Found By: Community User Blocker: --- Package: NetworkManager Version: 0.8-8.1.1.x86_64 Apparently due to battery loss while suspend the state file in /var/lib/NetworkManager/NetworkManager.state contained NetworkingEnabled=false which caused the network to remain in a disabled state. State does not change over reboot, and also isn't changeable from recent GUI-tools such as KDE's network-manager applet (which just showed "networking disabled") or gnome network manager applet. To remedy the problem you can: - remove the stale file: /var/lib/NetworkManager/NetworkManager.state - or edit the file and set NetworkingEnabled=true The usual desktop user will be lost. GUI is not providing any hints. Personally I would like to see an "enable network" option in the GUI but also cleaning up the state after reboot would be fine. Switching to "if*" tools and back to NetworkManager does not help, hence "major" as regular user is facing major loss of functionality. -- Configure bugmail: http://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 527936] New: xemacs ignores .xemacs/custom.el
by bugzilla_noreply＠novell.com 25 Nov '14

25 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=527936 Summary: xemacs ignores .xemacs/custom.el Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: wharms(a)bfs.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11 at startup .xemacs should load init.el and custom.el. i used strace -o xxx xemacs to see if custom.el is open at all and found that the programm is opening inil.el very often: grep init.el xxx | wc -l 2197 my .xemacs/custom.el ;; LINUX_C_MODE (defun linux-c-mode () "C mode with adjusted defaults for use with the Linux kernel." (interactive) (c-mode) (c-set-style "K&R") (setq c-basic-offset 8)) Reproducible: Always Steps to Reproduce: 1. strace -o xxx xemacs 2. 3. Actual Results: custom.el is never used and init.el is used in a loop -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8