November 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 681078] New: After zypper dup to 11.4 , most of the (graphical) YaST modules do not start via YaST on GNOME - yast2-control-center-gnome
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=681078 https://bugzilla.novell.com/show_bug.cgi?id=681078#c0 Summary: After zypper dup to 11.4 , most of the (graphical) YaST modules do not start via YaST on GNOME - yast2-control-center-gnome Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Martin.Seidler(a)web.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 I had been using 11.4 as factory-tested until November/December. After switching form to the 'real' 11.4 via zypper dup and zypper ref, most of the (graphical) YaST modules are not startable via graphical YaST>[YaST Module] But the problem seems to me only the starting in that way. E. g. I could use the module "Software Repositories" if I start it via Main Menue ("Computer") > "Install/Remove Software"=Software Mangager > \/[Repositories] > Edit Repositories But the YaST modules itself seem to be working if I start them directly via gnomesu [name of the YaST module] like gnomesu /sbin/yast2 sw_single. But not working is the start of the modules from the YaST2 Control Center just the waiting symbole is to be seen. The YaST module in KDE or LXDE is working without problems. Reproducible: Always Steps to Reproduce: 0. Upgrade to openSUSE 11.4 (from 11.4 RC or other users from 11.3) 1. Start the YaST2 Control Center (graphical or via console) 2. Click on a YaST module (like the Software Manager) Actual Results: The waiting symbol appears and disapears. Expected Results: The YaST module starts (like software manager) See: http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta… http://lists.opensuse.org/opensuse-factory/2011-03/msg00511.html -- 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 35

[Bug 689245] New: Gnome 3 will not allow connecting to hidden SSID
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=689245 https://bugzilla.novell.com/show_bug.cgi?id=689245#c0 Summary: Gnome 3 will not allow connecting to hidden SSID Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: i586 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: imahuph(a)imahuph.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.0) Gecko/20100101 Firefox/4.0 Gnome 3 network managaer .90 will not allow connection to hidden SSID, when attempt to connect network manager shuts down Reproducible: Always Steps to Reproduce: 1.attempt to connect to hidden SSID 2. 3. Expected Results: allowed connection to hidden SSID -- 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

[Bug 676174] New: bluetooth: notebook not visible although "always visible" is set
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=676174 https://bugzilla.novell.com/show_bug.cgi?id=676174#c0 Summary: bluetooth: notebook not visible although "always visible" is set Classification: openSUSE Product: openSUSE 11.4 Version: RC 2 Platform: x86 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: casualprogrammer(a)opensuse.org QAContact: qa(a)suse.de CC: sbrabec(a)novell.com, vuntz(a)novell.com, vbotka(a)novell.com Depends on: 549023 Found By: Beta-Customer Blocker: --- Trying to send a file from Phone (Sony Ericsson ELM) to Notebook (FSC Amilo Si1520) fails, as Notebook is not visible to phone (no devices found) openSUSE 11.4 RC2 bluez-4.89-1.1.i586 bluez-devel-4.89-1.1.i586 gnome-bluetooth-2.32.0-8.2.i586 gnome-bluetooth-devel-2.32.0-8.2.i586 gnome-bluetooth-plugins-geoclue-2.32.0-8.2.i586 libbluetooth3-4.89-1.1.i586 libgnome-bluetooth7-2.30.0-3.3.i586 libgnome-bluetooth8-2.32.0-8.2.i586 pulseaudio-module-bluetooth-0.9.22-9.2.i586 Reproducible: Always Steps to Reproduce: 1. Enable Bluetooth on both devices 2. Check "Computer visible" in Bluetooth preferences 3. Select a file on the phone and set option to transmit via bluetooth 4. Search for devices starts on the phone 5. Message "No Bluetooth devices found. New search?" Pairing both devices works, but still no file can be sent from phone to notebook. When selecting the notebook in the phones device list and checking available services, only "audio-remote-control-target" and "audio-remote-control" are listed. -- 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 9

[Bug 673106] New: Gnome in 11.4 has 2 different icons for the "Montior preferences"
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=673106 https://bugzilla.novell.com/show_bug.cgi?id=673106#c0 Summary: Gnome in 11.4 has 2 different icons for the "Montior preferences" Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: puchenergy(a)hotmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 Gnome in 11.4 has 2 different icons for the "Montior preferences" This is very confusing, particularly for start-Linux user. For more information, you can view the illustration as appendix. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 693451] New: [gnome3] cancelling shutdown dialog kills x server
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=693451 https://bugzilla.novell.com/show_bug.cgi?id=693451#c0 Summary: [gnome3] cancelling shutdown dialog kills x server Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: ruchir.brahmbhatt(a)ecosmob.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24 I configured power profile to show confirmation when power button is pressed. On pressing the button, confirmation dialog appears showing cancel, poweroff and reboot. Clicking cancel kills x server and kdm login screen appears. Reproducible: Always Steps to Reproduce: 1. Configure power settings in gnome3 to ask when power button pressed. 2. Press power button. 3. Click cancel. Actual Results: X restarted and kdm login screen appears. Expected Results: Dialog should cancel and no other action taken. -- 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

[Bug 695153] New: [gnome 3] Network Applet closes "root" permissions dialog box
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=695153 https://bugzilla.novell.com/show_bug.cgi?id=695153#c0 Summary: [gnome 3] Network Applet closes "root" permissions dialog box Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Minor Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: mwhite(a)thesummit-grp.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110420 Firefox/3.6.17 ( .NET CLR 3.5.30729) Using gnome 3 thru the opensuse repo on a fresh install of 11.4 with all updates applied as of report date. When modifying the properties of eth0 by select "network settings" from the applet a dialog box prompting for the root password quickly displays and then closes before a password can be entered. Thus you can't save the settings. If you open nm-conections-editor directly then the prompt for root access remains open and the settings can be saved. Reproducible: Always Steps to Reproduce: 1. click network applet 2. select network settings 3. Edit "options" under wired connection. 4. Root password prompt opens and then closes Expected Results: root password prompt should remain open. -- 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 2

[Bug 695321] New: Gnome-Shell is broken after upgrade -> segfault at 0 ip (null) sp 00007fff8da8b668 error 14 in gnome-shell[400000+4000]
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=695321 https://bugzilla.novell.com/show_bug.cgi?id=695321#c0 Summary: Gnome-Shell is broken after upgrade -> segfault at 0 ip (null) sp 00007fff8da8b668 error 14 in gnome-shell[400000+4000] Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: lasombra(a)gmx.ch QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 I've installed 11.4 and added gnome3 yesterday (21.May) and this was working fine. Today (22.May) I've did an upgrade (zypper dup) and restarted. I've discovered that I am missing menu entries (e.g. Yast2, Gnome Menu editor). So I've checked with yast and saw that yast2 is installed. Digging a little deeper, I've saw several warning and errors in .xsession-errors and in messages log there are a lot of segfaults (see attachment) I had the exactly same behaviour some days ago: It's working fine until I do a zypper dup and restart the machine. No clue what is breaking gnome-shell I have the following repos enabled: Main Repository openSUSE-11.4-Source openSUSE-11.4-Non-Oss Packman Repository libdvdcss repository openSUSE-11.4-11.4-0 Main Repository (Contrib) openSUSE BuildService - devel:languages:python openSUSE BuildService - PHP openSUSE BuildService - devel:languages:perl openSUSE BuildService - Java:packages GNOME:STABLE:3.0 openSUSE BuildService - Virtualization (VirtualBox) openSUSE BuildService - Mozilla openSUSE BuildService - Games openSUSE BuildService - filesystems openSUSE BuildService - Database openSUSE BuildService - Wine CVS Builds openSUSE BuildService - Education openSUSE BuildService - Mono:Community openSUSE BuildService - Banshee Updates for openSUSE 11.4 11.4-0 Muzlocker Subpixel The following gnome-shell extensions are installed (from repo): gnome-shell-extension-alt-status-menu-3.0.1-3.1 gnome-shell-extension-auto-move-windows-3.0.1-3.1 gnome-shell-extension-user-theme-3.0.1-3.1 gnome-shell-extension-windows-navigator-3.0.1-3.1 gnome-shell-extensions-3.0.1-3.1 gnome-shell-extensions-lang-3.0.1-3.1 Reproducible: Always Steps to Reproduce: 1. Install 11.4 from scratch 2. Add and install Gnome3 3. Add additional repositories 4. zypper dup 5. Restart Actual Results: Gnome-shell starts but - missing menu entries - apps (session properties) are not started automatically (e.g. guake, ...) Expected Results: All is working as before Starting gnome-session-properties on console does not work: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Terminated starting alacarte ends with: Traceback (most recent call last): File "/usr/bin/alacarte", line 22, in <module> from Alacarte.MainWindow import MainWindow File "/usr/lib/python2.7/site-packages/Alacarte/MainWindow.py", line 19, in <module> import gtk, gmenu, gobject, gio File "/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 40, in <module> from gtk import _gtk ImportError: could not import gobject (could not find _PyGObject_API object) -- 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

[Bug 696365] New: Nautilus Bookmark > Add Bookmark Not Working
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=696365 https://bugzilla.novell.com/show_bug.cgi?id=696365#c0 Summary: Nautilus Bookmark > Add Bookmark Not Working Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: drichard(a)largo.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 When using Nautilus, if you highlight a folder and select Bookmark >> Add Bookmark it fails to add it to the left side. The only way to make this work is to drop and drag it to the side bar. This is a serious defect and is causing us a lot of support issues. This worked fine on OpenSuse 11.3, and has failed since upgrade. Tested with multiple user accounts, it's not working globally here. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 2

[Bug 698407] New: Glade crashes
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=698407 https://bugzilla.novell.com/show_bug.cgi?id=698407#c0 Summary: Glade crashes Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: andoresu(a)hotmail.co.jp QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 What trying to select a dialog box it crashes. Reproducible: Always Steps to Reproduce: 1.Open Glade-3 2.Select an Upper Level Dialog Box 3.If it doesn't crash, try selecting another, it'll crash after selecting more than one consecutively. Terminal output: (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-spinner' was found for object class 'GtkSpinner'. GladeUI-Message: No displayable values for property GtkScaleButton::size GladeUI-Message: No displayable values for property GtkImage::icon-size (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-sizegroup' was found for object class 'GtkSizeGroup'. (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-accelgroup' was found for object class 'GtkAccelGroup'. (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-adjustment' was found for object class 'GtkAdjustment'. (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-uimanager' was found for object class 'GtkUIManager'. (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-treemodelfilter' was found for object class 'GtkTreeModelFilter'. (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-treemodelsort' was found for object class 'GtkTreeModelSort'. (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-treeselection' was found for object class 'GtkTreeSelection'. (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-cellrendererspinner' was found for object class 'GtkCellRendererSpinner'. GladeUI-Message: No displayable values for property GtkCellRendererSpinner::size (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-statusicon' was found for object class 'GtkStatusIcon'. (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-textbuffer' was found for object class 'GtkTextBuffer'. (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-entrybuffer' was found for object class 'GtkEntryBuffer'. (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-texttag' was found for object class 'GtkTextTag'. GladeUI-Message: No displayable values for property GtkTextTag::direction (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-texttagtable' was found for object class 'GtkTextTagTable'. (glade-3:23266): GladeUI-WARNING **: No icon named 'widget-gtk-filefilter' was found for object class 'GtkFileFilter'. GladeUI-Message: 1 missing displayable value for GnomeDateEdit::dateedit-flags GladeUI-Message: No displayable values for property GnomeIconList::selection-mode GladeUI-Message: No displayable values for property GtkPrintUnixDialog::manual-capabilities GladeUI-Message: No DevHelp installed on your system, devhelp feature will be disabled. (glade-3:23266): GladeUI-CRITICAL **: glade_widget_get_from_gobject: assertion `G_IS_OBJECT (object)' failed (glade-3:23266): GladeUI-CRITICAL **: glade_widget_get_from_gobject: assertion `G_IS_OBJECT (object)' failed (glade-3:23266): GladeUI-CRITICAL **: glade_widget_get_from_gobject: assertion `G_IS_OBJECT (object)' failed (glade-3:23266): GladeUI-CRITICAL **: glade_widget_get_from_gobject: assertion `G_IS_OBJECT (object)' failed (glade-3:23266): GladeUI-CRITICAL **: glade_widget_get_from_gobject: assertion `G_IS_OBJECT (object)' failed (glade-3:23266): GladeUI-CRITICAL **: glade_widget_get_from_gobject: assertion `G_IS_OBJECT (object)' failed (glade-3:23266): GladeUI-CRITICAL **: glade_widget_get_from_gobject: assertion `G_IS_OBJECT (object)' failed (glade-3:23266): GladeUI-CRITICAL **: glade_widget_get_from_gobject: assertion `G_IS_OBJECT (object)' failed (glade-3:23266): GladeUI-CRITICAL **: glade_widget_get_from_gobject: assertion `G_IS_OBJECT (object)' failed (glade-3:23266): GladeUI-CRITICAL **: glade_widget_get_from_gobject: assertion `G_IS_OBJECT (object)' failed -- 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

[Bug 699914] New: [gnome3]winbind + gdm fails with first login after boot
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=699914 https://bugzilla.novell.com/show_bug.cgi?id=699914#c0 Summary: [gnome3]winbind + gdm fails with first login after boot Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: philip.raets(a)telenet.be QAContact: qa(a)suse.de Found By: Other Blocker: Yes I have a openSUSE 11.4 with Gnome 3.0 installed in a windows 2003 domain with winbind. If I start it up, the account doesn't show in the user list, I choose other, enter my domain username, I can enter my password and then gdm hangs. If I first log in on another tty-console with my domain account, then I can log in into gnome through gdm (it's asking to unlock the session). Afterwards it works fine, I can log out and log back in. It seems this is the same bug as https://bugzilla.redhat.com/show_bug.cgi?id=690873 Local users don't have this problem. If you first login with a local user and then logout doesn't matter. The problem stays in effect. Also very strange, if I kill gdm in another console, it doesn't come back at tty7 but at tty8, and then gnome always falls back in fallback modus. This is very annoying. A user shouldn't have to do this the first time he/she wants to login. Now they have to login twice, first through a console and then through gdm. I've experienced this on 2 different win2k3 domains (both in virtualbox) I don't have this problem at home with openLdap accounts. Regards, Philip -- 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 2

[Bug 700612] New: System beeps on shutdown/reboot, even when pcspkr is not loaded
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=700612 https://bugzilla.novell.com/show_bug.cgi?id=700612#c0 Summary: System beeps on shutdown/reboot, even when pcspkr is not loaded Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: johan.lans(a)apspektakel.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.100 Safari/534.30 When gnome is shut down/rebooted there is a loud system beep. Beep is unaffected by set sound volume. I tried blacklisting pcspkr, but no change. Reproducible: Always Steps to Reproduce: 1. hadoque@fermi:~> lsmod | grep -i pcspkr hadoque@fermi:~> 2. reboot Actual Results: System beeps Expected Results: Be quiet hadoque@fermi:~> uname --all Linux fermi 2.6.37.6-0.5-desktop #1 SMP PREEMPT 2011-04-25 21:48:33 +0200 x86_64 x86_64 x86_64 GNU/Linux fermi:~ # lspci | grep -i audio 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 01:05.1 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200] -- 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 725743] New: orca install fails
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=725743 https://bugzilla.novell.com/show_bug.cgi?id=725743#c0 Summary: orca install fails Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i386 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andreas.roehler(a)online.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041122 Firefox/1.0 when trying to access orca with orca --gui-setup or orca -V get likewise Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/site.py", line 73, in <module> __boot() File "/usr/lib/python2.7/site-packages/site.py", line 48, in __boot addsitedir(item) File "/usr/lib/python2.7/site.py", line 188, in addsitedir addpackage(sitedir, name, known_paths) File "/usr/lib/python2.7/site.py", line 158, in addpackage exec line File "<string>", line 1, in <module> AttributeError: 'module' object has no attribute 'setdefaultencoding' Reproducible: Always Steps to Reproduce: 1. > orca --gui-setup 2. 3. Actual Results: see above -- 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 720745] New: Radeon 6850 Causes Screen Corruption and Flickering When Activated During Second Phase of Install
by bugzilla_noreply＠novell.com 23 Nov '13

23 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=720745 https://bugzilla.novell.com/show_bug.cgi?id=720745#c0 Summary: Radeon 6850 Causes Screen Corruption and Flickering When Activated During Second Phase of Install Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: PC OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: malv_star(a)hotmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=453362) --> (http://bugzilla.novell.com/attachment.cgi?id=453362) Image of screen produced by this bug. User-Agent: Mozilla/5.0 (X11; Linux i686; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 When installing openSuSE 12.1 Milestone 5, I used a machine with a Radeon HD6850 graphics card installed. The first phase of install proceeded normally, however once the system rebooted to begin the second phase of install, the screen appeared covered in vertical stripes and seemed to flicker randomly. I was not able to progress past this point without swapping out the graphics card for a Radeon HD5670, after which the install continued normally. I don't know if it makes a difference, but I selected KDE as my desktop. Reproducible: Always Steps to Reproduce: 1. Begin installation of a machine with a Radeon HD6850 graphics card 2. Complete the first phase of installation, selecting KDE as your desktop. 3. Wait for the system to reboot and attempt to initiate the second phase of installation. Actual Results: Flickering stripes appear on the screen. Expected Results: Graphics are displayed normally on the screen. -- 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 28

[Bug 681109] New: /etc/init.d/boot.clock: SYSTZ is not set properly under some conditions
by bugzilla_noreply＠novell.com 22 Nov '13

22 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=681109 https://bugzilla.novell.com/show_bug.cgi?id=681109#c0 Summary: /etc/init.d/boot.clock: SYSTZ is not set properly under some conditions Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: SuSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sbrabec(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- FAT file systems are mounted with local time zone by default. It means that proper file time information needs SYSTZ kernel variable set correctly. There are two utilities to do it: hwclock --systz and warpclock. /etc/init.d/boot.clock uses them both, but only sometimes. SYSTZ needs to be set always. Actually, on my system SYSTZ remains to set incorrectly and all times on FAT filesystem are shifted one hour forward. Variables from my /etc/sysconfig/clock: HWCLOCK="-u" SYSTOHC="yes" TIMEZONE="Europe/Prague" DEFAULT_TIMEZONE="US/Eastern" File /etc/adjtime exists and contains: 0.0 0 0.0 0 UTC sh -x /etc/init.d/boot.clock start confirms, that hwclock --systz nor warpclock are called: + . /etc/rc.status ++ /bin/mountpoint -q /sys/fs/cgroup/systemd ++ LC_ALL=POSIX ++ export LC_ALL ++ trap rc_lc SIGWINCH ++ test -n '' -a -n '' ++ rc_lc ++ test -n '' +++ stty size ++ set -- 73 224 ++ LINES=73 ++ COLUMNS=224 ++ test 73 -eq 0 -o 224 -eq 0 ++ export LINES COLUMNS ++ case ":$PATH:" in ++ test -t 1 -a xterm '!=' raw -a xterm '!=' dumb +++ echo -en '\033' ++ esc=$'\E' ++ extd='' ++ warn='' ++ done='' ++ attn='' +++ echo -en '\017' ++ norm='' +++ echo -en '\015 ' ++ stat=' ' ++ rc_done=' done' ++ rc_running=' running' ++ rc_failed=' failed' ++ rc_missed=' missing' ++ rc_skipped=' skipped' ++ rc_dead=' dead' ++ rc_unused=' unused' ++ rc_unknown=' failed'' ++ rc_reset=''p=' ++ rc_save='' ++ rc_restor'=' ++ _rc_service=/etc/init.d/boot.clock ++ _rc_status=0 ++ _rc_status_all=0 ++ _rc_todo=start ++ test start = status ++ test -n start ++ cmdline= + . /etc/sysconfig/clock ++ HWCLOCK=-u ++ SYSTOHC=yes ++ TIMEZONE=Europe/Prague ++ DEFAULT_TIMEZONE=US/Eastern + USE_ADJFILE=no + case "$HWCLOCK" in + USE_ADJFILE=yes + test yes '!=' yes + USE_HWCLOCK=yes + case "$(uname -i)" in ++ uname -i + test -r /proc/xen/capabilities + ELEVENMIN_MODE=no ++ adjtimex --print ++ sed -rn '/^[[:blank:]]*status:/{ s/[^[:digit:]]*([[:digit:]]+)/\1/p; }' + typeset -i STA_CLOCK=8257 + test 64 -eq 0 + rc_reset + _rc_status=0 + _rc_status_all=0 + rc_check + _rc_status_ret=0 + test 0 -eq 0 + test 0 -eq 0 + return 0 + return 0 + case "$1" in + test -n '' + test yes '!=' yes + test no = yes + echo -n 'Set System Time to the current Hardware Clock' Set System Time to the current Hardware Clock+ test yes = yes + test '!' -s /etc/adjtime + test -w /etc/adjtime + adjfile_thirdline + rtc_rule /sbin/hwclock -u --adjust + local temprules=/dev/.udev/rules.d + local uevseqnum=/sys/kernel/uevent_seqnum + local rule=/dev/.udev/rules.d/95-rtc-cmos.rules + local -i start=0 end=0 + test -e /dev/rtc + /sbin/hwclock -u --adjust + return 0 + rc_status -v + rc_check + _rc_status_ret=0 + test 0 -eq 0 + test 0 -eq 0 + return 0 + test 0 -gt 7 + _rc_status_ret=0 + case "$_rc_todo" in + local i + for i in '"$@"' + case "$i" in + local vrt= + local out=1 + local opt=en + test -n '' + opt=e + case "$_rc_status" in + vrt=' done' + echo -e '' done done + _rc_status=0 + return 0 + rc_exit + exit 0 Related (already fixed): bug 556979 -- 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 30

[Bug 626463] New: Please bring your kdebase4-workspace feature for reducing the classic-menu menu-depth upstream
by bugzilla_noreply＠novell.com 21 Nov '13

21 Nov '13

http://bugzilla.novell.com/show_bug.cgi?id=626463 http://bugzilla.novell.com/show_bug.cgi?id=626463#c0 Summary: Please bring your kdebase4-workspace feature for reducing the classic-menu menu-depth upstream Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: cyberbeat(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.1 SUSE/6.0.443.0 (KHTML, like Gecko) Chrome/6.0.443.0 Safari/534.1 opensuse-11.3 contains a patch for kdebase4-workspace (plasma-kickoff-newly-collapsing.diff), which I would like to see included in kde upstream. I hope there would be not much modifications needed to this patch to do this? The patch reduces optionally the menu-depth for menu-folders with only one entry, and also shows optionally recently installed applications. 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 6

[Bug 733195] New: KMail 4.7.x ist broken, buggy, broken, buggy, broken, buggy and -- broken & buggy
by bugzilla_noreply＠novell.com 21 Nov '13

21 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=733195 https://bugzilla.novell.com/show_bug.cgi?id=733195#c0 Summary: KMail 4.7.x ist broken, buggy, broken, buggy, broken, buggy and -- broken & buggy Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: p.heinlein(a)heinlein-support.de QAContact: qa(a)suse.de Found By: --- Blocker: --- I'm very angry and "not amused" about the "new" Kmail with Akonadi-Storage. This KMail ist absolute broken and buggy, it's like an early pre-alpha-release. It's absolutly NOT working, even not in unstable testing enviroments. I absolutely DON'T understand how/why SUSE ships this version of Kmail with OpenSUSE 12.1. In fact: OpenSUSE 12.1 does NOT have a working KDE-Mail-Application at all. Hey, it's the year 2011! I have several MAJOR bugs and crashes in KMail. I won't file them one by one, because I don't believe they will be fixed by SUSE. All of those bugs have been mailed directly to KDAB (in German). Some of the major bugs: *) KMail crashes with Segfauls when using the "fast search" for folders. Makes KMail unusable. Bug 732925. *) Mails in Draft-Folders aren't opend rw, but ro. Open those mails manually rw leads to a data loss if the e-mail is closed afterwards without any changes. DATA LOSS!!!! *) KMail shows the content of INBOX in every subfolder, if the Draft-Folder has been changed during runtime. But I'm happy to say, that Kmail had not synchronized this bullshit to the server. Whow. *) KMail looses a "preferred folders" one-by-one after using the folder-search. Very funny. HarHar. *) Migration vom Kmail from OpenSUSE 11.4 to Kmail from OpenSUSE 12.1 hadn't worked at all. *) mailto:-Links don't work in OpenSUSE 12.1. Bug 732926. And many, many, more. How is resonsible to the decission, which KMail-version will be shipped with OpenSUSE? KMail 4.7.x shoudn't be shipped with OpenSUSE at all. Please provide downgrade-packages to working Kmail-versions! -- 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 14

[Bug 684762] New: Update of kdelibs4 overwrites /usr/share/kde4/apps/kssl/ca-bundle.crt
by bugzilla_noreply＠novell.com 21 Nov '13

21 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=684762 https://bugzilla.novell.com/show_bug.cgi?id=684762#c0 Summary: Update of kdelibs4 overwrites /usr/share/kde4/apps/kssl/ca-bundle.crt Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: rolf(a)rotkraut.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.16) Gecko/20110319 SUSE/3.6.16-0.2.1 Firefox/3.6.16 The file /usr/share/kde4/apps/kssl/ca-bundle.crt contains all the root certificates that should be trusted by KDE applications such as kmail. Sites using their own SSL certificates or admins having their own preferences on which certificates they want to trust need to edit this file to add or remove root certificates. Therefore this file definitely contains local site configuration. Unfortunately, the spec file for kdelibs4 fails to mark this file as %config and so it gets overwritten each time a new version of kdelibs4 gets installed. Strictly speaking, since this file may contain site configuration, /usr/share/kde4 is the wrong location to install it in the first place. It should rather be installed in /etc, for instance as /etc/kde4/share/apps/kssl/ca-bundle.crt. Reproducible: Always Steps to Reproduce: 1. Edit /usr/share/kde4/apps/kssl/ca-bundle.crt to add custom root certificates. 2. Upgrade kdelibs4, for instance installing some security patch. Actual Results: /usr/share/kde4/apps/kssl/ca-bundle.crt gets replaced by the version in the new rpm package. The local site configuration is lost. Expected Results: The file from the upgrade package should be installed as ca-bundle.crt.rpmnew rather then overwriting the existing file. -- 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 2

[Bug 691058] New: PulseAudio Applet icons multiply after each reboot.
by bugzilla_noreply＠novell.com 21 Nov '13

21 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=691058 https://bugzilla.novell.com/show_bug.cgi?id=691058#c0 Summary: PulseAudio Applet icons multiply after each reboot. Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Minor Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: rkoktan(a)novell.com QAContact: qa(a)suse.de Found By: Field Engineer Blocker: --- Since upgrading to 11.4 a few days ago, I've noticed that each time I reboot, when Gnome loads, there is 1 additional PulseAudio Applet icon on the system panel. If I manually close all but 1, then reboot, there are 2. If I reboot again, there are 3, etc. Not a deal-breaker, but irritating all the same, as after 10 days now the applet icons are taking up a lot of panel real estate. -- 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

[Bug 731575] New: No 12.1 repos for Virtualization:Cloud:OpenNebula, Virtualization:Cloud:OpenStack, or Virtualization:Cloud:Eucalyptus
by bugzilla_noreply＠novell.com 21 Nov '13

21 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=731575 https://bugzilla.novell.com/show_bug.cgi?id=731575#c0 Summary: No 12.1 repos for Virtualization:Cloud:OpenNebula, Virtualization:Cloud:OpenStack, or Virtualization:Cloud:Eucalyptus Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: rschweikert(a)suse.com ReportedBy: jfunk(a)funktronics.ca QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- The press release for 12.1 states that "the openSUSE Virtualization and Cloud repository for openSUSE 12.1 offers the latest versions of Eucalyptus, OpenNebula and OpenStack for openSUSE 12.1." OpenNebula and Eucalyptus are nowhere to be found for 12.1, and the main OpenStack project is also missing the 12.1 repo. Could someone with the necessary access turn these on? -- 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 728562] New: perlcritic missing executable permission
by bugzilla_noreply＠novell.com 21 Nov '13

21 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=728562 https://bugzilla.novell.com/show_bug.cgi?id=728562#c0 Summary: perlcritic missing executable permission Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: ASSIGNED Severity: Normal Priority: P5 - None Component: Development AssignedTo: rschweikert(a)suse.com ReportedBy: rschweikert(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- /usr/bin/perlcritic is not executable. This is the command line interface to the Perl-Critic collection of modules, thus it needs to be executable bye everyone on the system. Applies to 11.4 and 12.1 -- 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

[Bug 685949] New: iSCSI Target broken
by bugzilla_noreply＠novell.com 14 Nov '13

14 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=685949 https://bugzilla.novell.com/show_bug.cgi?id=685949#c0 Summary: iSCSI Target broken Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: udo1(a)udo.hu QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.16) Gecko/20110319 Firefox/3.6.16 iscsi_target is broken if configured. Ietd/rciscsitarget hangs by stopping the service. Reproducible: Always Steps to Reproduce: 1.Define 1 iscsi target 2.try to restart iscsi_target or reboot the machine. Iscsi not listening on the network... 3. Actual Results: rcicscitarget stop hangs (ietd remove) cannot reboot cannot restart the service cannot use the service Expected Results: normal operation -- 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 729667] New: grub error after each kernel-update: "Error 16: Inconsistent filesystem structure"
by bugzilla_noreply＠novell.com 13 Nov '13

13 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=729667 https://bugzilla.novell.com/show_bug.cgi?id=729667#c0 Summary: grub error after each kernel-update: "Error 16: Inconsistent filesystem structure" Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: Yarny(a)public-files.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Short summary: I'm running 4 32bit machines with openSUSE 11.4 and each time there is a kernel update, at least one or two of those (different ones each time) refuse to (re)boot afterwards. Grub shows its menu for a few seconds and then immediately says "Error 16: Inconsistent filesystem structure". On each machine, the boot partition is ~80MiB ext2. fsck.ext2 (from LiveCD) says everything's OK. Recreating the boot partition with mkfs.ext2 fixes the problem until the next update arrives. A bit more details. (This is mostly a copy from <URL:http://forums.opensuse.org/forums/english/get-technical-help-here/insta…>) Here's what I did/observed this Tuesday: * "zypper update", which (besides other stuff) listed kernel-default. I confirm. * After this is done, I did "shutdown -r now" to reboot. * Grub shows its menu (text mode only, I don't have the graphical bootsplash installed). After 3 sec or so timeout, it tries to boot as always, but immediately says "Error 16: Inconsistent filesystem structure". Unfortunately, this problem occurs only randomly. I'm running 4 64bit machines and 4 32bit machines. Up to now it happened only on 32bit machines and at every kernel-update, it occurs on 1 or 2 of my machines. To fix this, I have to boot from external media and recreate the broken boot-partition (i.e. copy files to some temporary place and do a "mkfs.ext2 /dev/sda1", then copy back on the new filesystem). Then I mount everything, chroot in my to-be-fixed system and run "grub-install". After that I can boot from harddisk again. The filesystem which is inconsistent according to grub is ok according to fsck.ext2. I checked this before rewriting the filesystem with mkfs.ext2. The system where it happened yesterday contains only one harddisk with two partitions: sda1 is /boot, ext2, 80MiB; sda2 is a luks-encrypted lvm container. Partition table is gpt, grub is installed in the mbr (I think). The way I installed these systems I a bit unorthodox: I basically set up the partitioning scheme by hand and mounted everything, then did a "zypper -R /mnt/root install ..". While this might contribute to the triggering of this behavior, it still believe there is an underlying bug that is causing this mess. I have no other explanation for this to happen only randomly, but not always. In the last months I always just "fixed" this as fast as possible to move on. On Tuesday I made a copy of /dev/sda1 ("cat /dev/sda1 > file") right after booting my rescue system. I also updated two other 32bit machines without problems. Another 32bit machine is still awaiting the kernel update (I did not "zypper update" yet). Sadly, I don't see an obvious way to reliably reproduce the problem (without waiting for the next kernel update). I can share my boot-partition-image with you which I created before fixing it, also log-files and other data. But since all 4 32bit machines are production systems my ability to do experimentation with them is limited. But if it would be helpful I can try to collect more data when updating my remaining not-updated machine. Reproducible: Sometimes -- 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 20

[Bug 608203] New: openmpi causes an error output on uninstall
by bugzilla_noreply＠novell.com 13 Nov '13

13 Nov '13

http://bugzilla.novell.com/show_bug.cgi?id=608203 http://bugzilla.novell.com/show_bug.cgi?id=608203#c0 Summary: openmpi causes an error output on uninstall Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: davejplater(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.4) Gecko/20100417 SUSE/3.6.4-1.10 Firefox/3.0.6, Ant.com Toolbar 1.3 When openmpi is uninstalled during osc build it gives the following output :- deleting openmpi /var/tmp/rpm-tmp.4Pvn8K: line 1: /usr/bin/mpi-selector: No such file or directory error: %preun(openmpi-1.2.8-11.18.x86_64) scriptlet failed, exit status 127 re-try deleting openmpi using --noscripts 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 11

[Bug 707823] New: chkconfig -l to list only services enabled in at least 1 runlevel
by bugzilla_noreply＠novell.com 13 Nov '13

13 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=707823 https://bugzilla.novell.com/show_bug.cgi?id=707823#c0 Summary: chkconfig -l to list only services enabled in at least 1 runlevel Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: volker3204(a)paradise.net.nz QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=441859) --> (http://bugzilla.novell.com/attachment.cgi?id=441859) Patch providing -L|-liston User-Agent: Mozilla/5.0 (compatible; Konqueror/4.6; Linux) KHTML/4.6.0 (like Gecko) SUSE Add option -L|--liston to checkconfig, which prints only those services that are on in at least one runlevel. Patch against chkconfig of openSUSE 11.4. Usually I'm not so interested in what services are installed, but only in those that are enabled. Reproducible: Always -- 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 505417] New: sysconfig editor: LANG for root is ignored
by bugzilla_noreply＠novell.com 13 Nov '13

13 Nov '13

http://bugzilla.novell.com/show_bug.cgi?id=505417 Summary: sysconfig editor: LANG for root is ignored Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)novell.com Found By: --- There are two nodes: environment/language/root_uses_lang environment/language/rc_lc_ctype that are related to setting LANG for root. The problem is no matter what the values are, LANG is always (as the effect) set to "POSIX". You can check it by executing set | grep -i lang in console. The only way to set LANG for root account for real is modify for example bashrc and add entry for LANG manually. Of course it is workaround, sysnconfig editor should set it (somehow) according to its own description. "This defines if the user "root" should use the locale settings which are defined here." (the first node) It is defined and it is not used. -- 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 640088] New: checking flavor of gethostbyname_r result sun
by bugzilla_noreply＠novell.com 12 Nov '13

12 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=640088 https://bugzilla.novell.com/show_bug.cgi?id=640088#c0 Summary: checking flavor of gethostbyname_r result sun Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: justo.alonso(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=390223) --> (http://bugzilla.novell.com/attachment.cgi?id=390223) conftest.c to reproduce problem User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.7) Gecko/20100726 CentOS/3.6-3.el5.centos Firefox/3.6.7 Compiling programs that check of flavor of gethostbyname_r fail, because the check result in sun flavor, not glibc The check from configure for idnkit, included in bind source rpm, result as sun. Reproducible: Always Steps to Reproduce: Compile the source code in attachement (extracted from configure): gcc -o conftest -g -O2 conftest.c -ldl -lnsl exec it. Actual Results: the program return 1 Expected Results: the program must be return 0 -- 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 15

[Bug 722043] New: Displayed installation time is jumpy
by bugzilla_noreply＠novell.com 12 Nov '13

12 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=722043 https://bugzilla.novell.com/show_bug.cgi?id=722043#c0 Summary: Displayed installation time is jumpy Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: ke(a)suse.com QAContact: jsrain(a)suse.com Found By: Documentation Blocker: --- The time displayed in YaST during package installation while updating is rather jumpy. More than 3000 package were needed to update. In the middle, it were down to a few seconds left, then it went up to half an hour. See the log. -- 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 8

[Bug 657863] New: NFS Server Displays Debug on exiting from Yast after sharing the root partition of large EXT3 Partitions
by bugzilla_noreply＠novell.com 11 Nov '13

11 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=657863 https://bugzilla.novell.com/show_bug.cgi?id=657863#c0 Summary: NFS Server Displays Debug on exiting from Yast after sharing the root partition of large EXT3 Partitions Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: scott(a)aphofis.com QAContact: jsrain(a)novell.com Depends on: 657836 Found By: Customer Blocker: No Created an attachment (id=403664) --> (http://bugzilla.novell.com/attachment.cgi?id=403664) Image file User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12 1. Default NON NFSV4 Client 2. Mount points are from NSF Server Clone. 3. Default creation of NFS Client from Mount Points of NFS Server Clone 4. On exit NFS Client Config either Debug displayed - Unsure of what debug is trying to tell me. 5. Please be specific on which logs your require 6 - NEW - Change in first impressions - The debug output or error may not necessarily be confined to the 2 example I have with NFS Server and NFS Client Reproducible: Always Steps to Reproduce: 1. Default NON NFSV4 Server 2. Mount points are created in different PC using NFS client 3. Default Settings but NOT NFS V4 4. On exit NFS Client Config either Debug displayed - Unsure of what debug is trying to tell me. 5. Please be specific on which logs your require **. QA - See Cloned bug and adjust both dependency and severity as required** - Thanks Jim Actual Results: Unsure of what debug is trying to tell me. Expected Results: Nil Debug output from any application called from Yast lease be specific on which logs your require Debug Output QApplication::qAppName: Please instantiate the QApplication object first kdeinit4: preparing to launch /usr/lib64/libkdeinit4_klauncher.so Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kded4.so kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kbuildsycoca4.so kbuildsycoca4 running... kbuildsycoca4(9343) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "application/vnd.openxmlformats-officedocument.presentationml.template.xml" kbuildsycoca4(9343) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "application/vnd.ms-excel.sheet.macroEnabled.12.xml" kbuildsycoca4(9343) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "application/vnd.ms-powerpoint.presentation.macroEnabled.12.xml" kbuildsycoca4(9343) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "application/vnd.ms-word.template.macroEnabled.12.xml" kbuildsycoca4(9343) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "application/vnd.openxmlformats-officedocument.wordprocessingml.template.xml" kbuildsycoca4(9343) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "application/vnd.ms-excel.sheet.binary.macroEnabled.12.xml" kbuildsycoca4(9343) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "application/vnd.ms-word.document.macroEnabled.12.xml" kbuildsycoca4(9343) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "application/vnd.ms-powerpoint.slideshow.macroEnabled.12.xml" kbuildsycoca4(9343) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "application/vnd.ms-excel.template.macroEnabled.12.xml" kbuildsycoca4(9343) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "application/vnd.ms-powerpoint.template.macroEnabled.12.xml" kbuildsycoca4(9343) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "application/vnd.openxmlformats-officedocument.spreadsheetml.template.xml" kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/opt/kde3/share/applications/kde/kresources.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/mail.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/sw_source.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/nfs_server.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/isdn.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/sudo.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/SD_Reports.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/scanner.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/hwinfo.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/vendor.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/SD_edit_profile.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/ldap_browser.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/autoyast.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/iscsi-server.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/checkmedia.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/keyboard.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/host.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/ca_mgm.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/bootloader.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/xen.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/proxy.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/runlevel.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/security.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/SD_control_panel.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/add-on.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/SD_logprof.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/mouse.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/tv.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/lan.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/ntp-client.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/sysconfig.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/instserver.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/tftp-server.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/yast-language.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/kerberos.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/nis.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/disk.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/nis_server.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/system_settings.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/restore.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/SD_add_profile.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/sw_single.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/SD_delete_profile.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/iscsi-client.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/ldap.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/inetd.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/users.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/sound.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/remote.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/samba-client.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/firewall.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/webpin.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/dsl.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/common_cert.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/printer.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/samba-server.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/groups/virtualization.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/groups/hardware.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/groups/apparmor.desktop" has Type= "Application" but no Exec line kbuildsycoca4(9343) KBuildServiceFactory::createEntry: Invalid Service : "/usr/share/applications/YaST2/groups/apparmor.desktop" kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/groups/high_availability.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/groups/security.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/groups/network_services.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/groups/support.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/groups/software.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/groups/system.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/groups/network_devices.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/groups/misc.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/irda.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/online_update.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/slp-server.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/nfs.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/backup.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/SD_genprof.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/modem.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/timezone.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/ftp-server.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(9343)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/joystick.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. "KConfigIni: In file /usr/share/applications/wine-browsedrive.desktop, line 3: " "Invalid escape sequence "\ "." "KConfigIni: In file /usr/share/applications/wine-browsedrive.desktop, line 4: " "Invalid escape sequence "\ "." "KConfigIni: In file /usr/share/applications/wine-browsedrive.desktop, line 10: " "Invalid escape sequence "\ "." kbuildsycoca4(9343) parseLayoutNode: The menu spec file contains a Layout or DefaultLayout tag without the mandatory Merge tag inside. Please fix your file. kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kconf_update.so "KConfigIni: In file /tmp/kde-root/kconf_updatepg9347.tmp, line 1: " Invalid entry (missing '=') kdeinit4: preparing to launch /usr/lib64/kde4/kio_file.so Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeinit4: preparing to launch /usr/lib64/kde4/kio_trash.so kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kbuildsycoca4.so <unknown program name>(9334)/ KStartupInfo::createNewStartupId: creating: "MULTIVAC-010;1291681415;49462;9334_TIME0" : "unnamed app" kbuildsycoca4 running... YaST got signal 11 at YCP file nfs/routines.ycp:284 /sbin/yast2: line 399: 9222 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS -- 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 16

[Bug 657836] New: NFS Server Displays Debug on exiting from Yast after sharing the root partition of large EXT3 Partitions
by bugzilla_noreply＠novell.com 11 Nov '13

11 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=657836 https://bugzilla.novell.com/show_bug.cgi?id=657836#c0 Summary: NFS Server Displays Debug on exiting from Yast after sharing the root partition of large EXT3 Partitions Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: scott(a)aphofis.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=403664) --> (http://bugzilla.novell.com/attachment.cgi?id=403664) Image file User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12 1. Default NON NFSV4 Server 2. Mount points are the physical root partitions of large physical HDD. 3. Default changed from Read Only to Read Write, the rest is default 4. On exit NFS Server Config either Debug displayed - Unsure of what debug is trying to tell me. 5. See images - I have many more such outputs in logs. 6. Please be specific on which logs your require Reproducible: Always Steps to Reproduce: 1. Default NON NFSV4 Server 2. Mount points are the physical root partitions of large physical HDD. 3. Default changed from Read Only to Read Write, the rest is default 4. On exit NFS Server Config either Debug displayed - Unsure of what debug is trying to tell me. 5. See images - I have many more such outputs in logs. 6. Please be specific on which logs your require Actual Results: Unsure of what debug is trying to tell me. The NFS Mount point are sometimes visible and other times non visible from a NFS Client Expected Results: Nil Debug output from any application called from Yast lease be specific on which logs your require Debug Output - This instance very small - Logs hold 40+ lines of similar output and are a bit large Depending on output please adjust Severity -- 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 15

[Bug 712614] New: Internal SLP server for installations is not consistent for product naming.
by bugzilla_noreply＠novell.com 11 Nov '13

11 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=712614 https://bugzilla.novell.com/show_bug.cgi?id=712614#c0 Summary: Internal SLP server for installations is not consistent for product naming. Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.5 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: General AssignedTo: ro(a)suse.com ReportedBy: dmacvicar(a)novell.com QAContact: adrian(a)novell.com CC: adrian(a)novell.com, mls(a)novell.com Found By: --- Blocker: --- This prevents using the SLP attributes from programs. Is there any convention or algorithm behind the naming? SLE_10_SP3_SDK 10.3-0 GM sle-sdk 11.2 SLE_10_SP3_SMT 10.3-0 sle-hae 11 GM SUSE_SLES_SP4 10.4-0 openSUSE 11.4 GM Expected: Either description includes something consistent naming a program can use to match or search for a repository, or additional attributes with known fields are added to the SLP attributes. -- 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 699458] New: local fs mount times out for loop-mounted filesystem
by bugzilla_noreply＠novell.com 11 Nov '13

11 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=699458 https://bugzilla.novell.com/show_bug.cgi?id=699458#c0 Summary: local fs mount times out for loop-mounted filesystem Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: volker3204(a)paradise.net.nz QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.6; Linux) KHTML/4.6.0 (like Gecko) SUSE The boot process gets stuck for 30 (40?) seconds trying to mount a local file-system, increasing boot time by that much. System configuration: /dev/md0 / reiserfs ... /dev/md1 /home reiserfs ... /dev/sda6 /local/data reiserfs ... /local/data/backup.ext2 /local/lastbackup auto loop,defaults,ro,auto Booting is stuck on mounting backup.ext2 until timeout occurs. At a guess, boot.localfs fails to notice that the backup.ext2 file is located on a filesystem that is not yet mounted, hence attempting to mount it can not succeed. Used to work fine on oS 11.1. A similar problem for shutdown also prevents clean shutdown (although this is not the only problem preventing clean shutdowns). Neither /dev/sda6 nor /dev/md0 are unmounted during shutdown. /dev/md0 can't be unmounted because it has the mount point for a file from /dv/sda6, /dev/sda6 can't be un-mounted because one of its files remains in use. Reproducible: Always Steps to Reproduce: 1. Create system file-system config as detailed. 2. Reboot. 3. Watch boot screen. Expected Results: Mount file-systems in correct order at boot time. Un-mount file-systems in correct order during 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 7

[Bug 680622] New: check_gcc_output mixes several files with same name
by bugzilla_noreply＠novell.com 11 Nov '13

11 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=680622 https://bugzilla.novell.com/show_bug.cgi?id=680622#c0 Summary: check_gcc_output mixes several files with same name Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: chrubis(a)novell.com QAContact: adrian(a)novell.com Found By: --- Blocker: --- It's common that in bigger projects source files are split between several directories which allows for having several source files with same name. That will however generate confusing check_gcc_output output. The lines containing errors for these files will be merged into "filename: line1 line2 line3" where lineX may be from just any of these source 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 7

[Bug 679810] New: openSUSE:Tools/osc: Bug
by bugzilla_noreply＠novell.com 11 Nov '13

11 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=679810 https://bugzilla.novell.com/show_bug.cgi?id=679810#c0 Summary: openSUSE:Tools/osc: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: adrian(a)novell.com ReportedBy: viliam.pucik(a)gmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- osc incorectly interprets macros if they are set in %if/%endif: In this example, "prerelease" macro should be interpeted as undefined, but osc thinks, it is defined and contains "pre1": --- BEGIN: part of rsync.spec taken from RHEL 6 %define isprerelease 0 %if %isprerelease %define prerelease pre1 %endif Summary: A program for synchronizing files over a network Name: rsync Version: 3.0.6 Release: 5%{?prerelease}%{?dist} Group: Applications/Internet URL: http://rsync.samba.org/ Source0: ftp://rsync.samba.org/pub/rsync/rsync-%{version}%{?prerelease}.tar.gz .. --- END $ cd rsync $ ls rsync-3.0.6-permissions.patch rsync-3.0.6.tar.gz rsync-patches-3.0.6.tar.gz rsync.spec rsync.xinetd $ osc ci rsync-3.0.6pre1.tar.gz mentioned in spec file does not exist. rsync-patches-3.0.6pre1.tar.gz mentioned in spec file does not exist. Attention, rsync-3.0.6.tar.gz is not mentioned in spec files as source or patch. Is this correct? [N/y/d] -- 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 639396] New: Won't boot inside openvz container because of the permissions /etc/init.d/boot mount devpts with.
by bugzilla_noreply＠novell.com 11 Nov '13

11 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=639396 https://bugzilla.novell.com/show_bug.cgi?id=639396#c0 Summary: Won't boot inside openvz container because of the permissions /etc/init.d/boot mount devpts with. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rob.fortune(a)live.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.7 SUSE/7.0.513.0 (KHTML, like Gecko) Chrome/7.0.513.0 Safari/534.7 System fails to boot because the pts are unavailable to the host system. Reproducible: Always Steps to Reproduce: 1. Get a VPS in OpenVZ 2. Try and boot it 3. Actual Results: Boot fails, can't login with "fake serial console" either because it can't get a pty Expected Results: Boot to work. Here are the changes I made to /etc/init.d/boot to make it work. You could add detection for being run under openvz and mount devpts differently. --- boot.orig 2010-09-15 06:46:45.000000000 +0000 +++ boot 2010-09-15 06:03:35.000000000 +0000 @@ -24,8 +24,9 @@ # # Standard input from the system console # -test -z "$CONSOLE" && CONSOLE=/dev/console REDIRECT="$(showconsole 2>/dev/null)" +CONSOLE="$REDIRECT" +#test -z "$CONSOLE" && CONSOLE=/dev/console export CONSOLE REDIRECT # @@ -96,16 +97,16 @@ fi fi -DTYPE=$(stat -f -c "%T" /dev 2>/dev/null) -if test "$DTYPE" != "tmpfs" ; then - echo -n "Mounting devtmpfs at /dev" - mount -n -t $DEVTMPFS -o mode=0755 $DEVTMPFS /dev - rc_status -v -r -fi - -echo -n "Copying static /dev content" -cp -axT --remove-destination /lib/udev/devices /dev -rc_status -v -r +#DTYPE=$(stat -f -c "%T" /dev 2>/dev/null) +#if test "$DTYPE" != "tmpfs" ; then +# echo -n "Mounting devtmpfs at /dev" +# mount -n -t $DEVTMPFS -o mode=0755 $DEVTMPFS /dev +# rc_status -v -r +#fi + +#echo -n "Copying static /dev content" +#cp -axT --remove-destination /lib/udev/devices /dev +#rc_status -v -r if test "$(stat -Lc %d /dev/shm 2>/dev/null)" = "$(stat -Lc %d /dev/shm/.. 2>/dev/null)" ; then echo -n "Mounting tmpfs at /dev/shm" @@ -118,14 +119,14 @@ if test "$DTYPE" != "devpts" ; then echo -n "Mounting devpts at /dev/pts" mkdir -p -m 755 /dev/pts - mount -n -t devpts -o mode=0620,gid=5 devpts /dev/pts + mount -n -t devpts -o defaults devpts /dev/pts rc_status -v -r fi # # Set I/O of this script and its childs to console # -exec 0<> $CONSOLE 1>&0 2>&0 +#exec 0<> $CONSOLE 1>&0 2>&0 # # Should we ask for interactive boot 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.

1 3

[Bug 626333] New: group lock does not exist while installing the filesystem package
by bugzilla_noreply＠novell.com 11 Nov '13

11 Nov '13

http://bugzilla.novell.com/show_bug.cgi?id=626333 http://bugzilla.novell.com/show_bug.cgi?id=626333#c0 Summary: group lock does not exist while installing the filesystem package Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lmuelle(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.7) Gecko/20100714 SUSE/3.6.7-0.1.1 Firefox/3.6.7 Installation von: filesystem-11.3-1.2 [fertig] Zusätzliche rpm-Ausgabe: warning: group lock does not exist - using root Reproducible: Always Steps to Reproduce: Performed an upgrade from 11.2 to 11.3 via zypper dup. -- 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 729796] New: mdns reenabled during upgrade
by bugzilla_noreply＠novell.com 07 Nov '13

07 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=729796 https://bugzilla.novell.com/show_bug.cgi?id=729796#c0 Summary: mdns reenabled during upgrade Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hamann.w(a)t-online.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.6) Gecko/20040113 upgrade installation (from 11.4 to 12.1 - same happened when upgrading to 11.4) activates avahi-daemon and modifies /etc/nsswitch.conf to use mdns-minimal Reproducible: Always Steps to Reproduce: 1. insert installation media, choose upgrade .... 2. 3. Actual Results: after installation avahi was active, and .local resolution used mdns Since the remainder of the network uses port 53 dns, local name resolution failed Expected Results: preserve old settings. There are very few reasons why one would have turned off mdns. These include a) existing network with .local name scheme b) no network at all (just a single computer connected to the internet) c) incompatible hardware on an existing network (e.g. printers and telephones that respond to mdns but do not allow setting of meaningful names) Neither of these reasons can be expected to change by upgrading a system May I also add a suggestion for enhancement: during a fresh install there is a warning against using .local domain. Could there be an option to disable mdns or a link to instructions? -- 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 712508] New: rpmbuild of mysql-community-server-5.1.53-4.7.1 fails
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=712508 https://bugzilla.novell.com/show_bug.cgi?id=712508#c0 Summary: rpmbuild of mysql-community-server-5.1.53-4.7.1 fails Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: leroy.nick(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/15.0.846.0 Safari/535.1 SUSE/15.0.846.0 It looks as though most of the build succeeds, but it then fails in the verification stages (see below). I've tried building 5.5.14-1.1 (from the 'openSUSE BuildService - Database' repo), with similar results. I've also tried this build on several different openSUSE 11.4 machines, with similar results. Finally, I've tried building mysql-community-server-5.1.46-2.18 on an openSUSE 11.3 machine -- this succeeds. I haven't tried building this source package on an 11.4 machine (yet). Please let me know what further information I can provide. Thanks -Nick Reproducible: Always Steps to Reproduce: 1.zypper si mysql-community-server 2.rpmbuild -bb mysql-community-server.spec Actual Results: ... INFO: relinking /usr/sbin/rcmysql -> /etc/init.d/mysql (was ./../etc/init.d/mysql) Processing files: mysql-community-server-5.1.53-4.7.1.x86_64 error: File not found by glob: /usr/src/packages/BUILDROOT/mysql-community-server-5.1.53-4.7.1.x86_64/etc/mysql/* RPM build errors: File not found by glob: /usr/src/packages/BUILDROOT/mysql-community-server-5.1.53-4.7.1.x86_64/etc/mysql/* -- 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 710794] New: mysql-community-server: Wrong Default-Start in init script
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=710794 https://bugzilla.novell.com/show_bug.cgi?id=710794#c0 Summary: mysql-community-server: Wrong Default-Start in init script Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lauffer(a)ph-freiburg.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0 In the init script of the mysql-community-server-5.1.53-4.7.1.x86_64 (openSUSE-11.4 final) we have in /etc/init.d/mysql line 19: # Default-Start: 2 3 5 Right is not trying to start in runlevel 2. The factory build of the mysql-community-server is already fixed. This is just a reminder to merge this fix in a further 11.4 update package. Reproducible: Always Steps to Reproduce: 1. insserv /etc/init.d/mysql if mysql-community-server is installed ends in a insserv warning that there is no network in runlevel 2... -- 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 730904] New: mysqld.service not found
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=730904 https://bugzilla.novell.com/show_bug.cgi?id=730904#c0 Summary: mysqld.service not found Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dominian(a)slackadelic.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0 Trying to start mysqld with rc.mysqld start or systemctl start mysqld.service results in mysqld not running saying file not found. destiny:~ # systemctl start mysqld.service Failed to issue method call: Unit mysqld.service failed to load: No such file or directory. See system logs and 'systemctl status mysqld.service' for details. destiny:~ # systemctl status mysqld.service mysqld.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) Reproducible: Always Steps to Reproduce: 1. chkconfig mysqld on 2. try to start mysqld with rcmysqld start or systemctl start mysqld.service 3. failure Actual Results: Mysqld fails to start with mysqld.service not found Expected Results: mysqld starting and working -- 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 668173] New: [SMBTA] WebYast module to control smbtad
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=668173 https://bugzilla.novell.com/show_bug.cgi?id=668173#c0 Summary: [SMBTA] WebYast module to control smbtad Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: ASSIGNED Severity: Enhancement Priority: P5 - None Component: Samba AssignedTo: bgeuken(a)novell.com ReportedBy: hhetter(a)novell.com QAContact: samba-maintainers(a)SuSE.de CC: hhetter(a)novell.com, mhaefner(a)novell.com, bbrunner(a)novell.com Found By: --- Blocker: --- During hackweek Björn took a look at SMBTA and made first steps to create a webyast module to control smbtad, which would be a killer feature for sure. Lots of IRC communication has passed. This stuff is totally in development, and no timeline or anything similar can be given at the moment. I created this bug for us to track the status of that idea, and of course this bug will not be blocking any release tracker bug. Stored as "Enhancement". I would be happy if Björn would update the status of this development in this bug from time to time ! -- 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 9