March 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 575994] New: YaST cannot find control file during installation "Welcome".
by bugzilla_noreply＠novell.com 05 Mar '10

05 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=575994 http://bugzilla.novell.com/show_bug.cgi?id=575994#c0 Summary: YaST cannot find control file during installation "Welcome". Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lars.koraeus(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.7) Gecko/20091222 SUSE/3.5.7-1.1.1 Firefox/3.5.7 Using SUSEopenSUSE-NET-x86_64-Build0412-Media.iso First time 01/28 it went to an installation but with the graphics messed up after finished installation. Second time 2 days later I did get problems but did reach a completet install but still with messed up graphics. After another two days and there after All of the followings and have to cancel the installation. So after YaST cannot find control file during installation "Welcome". Later no license agreement is found. Further during initial package manager, Error: Document load failed. File '/content.key' not found on ....../11.3/repo/oss/ History: AbstractCommand.cc:195 .......factory-snapshot/repo/oss/content.key Later no install than an 'empty' other is available and cannot proceed. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Will not see the licence agreement Cannot select type of install Gnome/KDE/Other Expected Results: Show the license agreement Allowed me to choose installation type and go on with the installation. -- 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 585320] New: AutoLoginDelay=10 does not work as of KDE 4.4.
by bugzilla_noreply＠novell.com 05 Mar '10

05 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=585320 http://bugzilla.novell.com/show_bug.cgi?id=585320#c0 Summary: AutoLoginDelay=10 does not work as of KDE 4.4. Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: dwightpaige79(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=346443) --> (http://bugzilla.novell.com/attachment.cgi?id=346443) /usr/share/kde4/config/kdm/kdmrc User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.2 Firefox/3.6 AutoLogin immediately works but when I set 'AutoLoginDelay=10' in '/usr/share/kde4/config/kdm/kdmrc' upon logging in login screen freezes and no user can login. Workaround is at login screen to select >Menu>Shutdown>Cancel and whichever user is selected will be logged in. FWIW this is also happening in Fedora 12 and Mandriva2010.0 both X86_64 since KDE 4.4. I filed bug report here as I am more familiar with openSuSE though by no means an expert. I'm new and getting used to Fedora and Mandriva seems shorthanded lately. Reproducible: Always Steps to Reproduce: 1.Edit '/usr/share/kde4/config/kdm/kdmrc' to: [X-:0-Core] AutoLoginAgain=true AutoLoginDelay=10 AutoLoginEnable=true AutoLoginLocked=false AutoLoginUser=<userx> ClientLogFile=.xsession-errors TerminateServer=true 2.logout/login or reboot 3.When login screen is reached user MUST very quickly hit enter [even though AutoLoginEnable=true] OR login screen freezes and no user can login. Actual Results: As above. Expected Results: Before KDE 4.4 AutoLogin worked fine with 10 second delay in KDE 4.3.x. Also same in Fedora 12 and Mandriva 2010.0 both x86_64. Let me know of any additional info needed. Or if I filed this in wrong place or with incorrect procedures. Am willing to learn and test things. [In following bugzilla I was led to openSuSE 11.2 though this would seem to me to be a Factory bug?] Will next post 'zypper -v lr'. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 567115] New: obs-worker: sysconfig entry descriptions
by bugzilla_noreply＠novell.com 05 Mar '10

05 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=567115 http://bugzilla.novell.com/show_bug.cgi?id=567115#c0 Summary: obs-worker: sysconfig entry descriptions Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: adrian(a)novell.com Found By: Beta-Customer Blocker: --- With the installation of obs-worker 1.6.85, the following new entries in /etc/sysconfig/obs-worker are added, but the description seems incorrect :-) There are also no defaults specified, which makes one think that a value is required. ## Path: Applications/OBS ## Description: Register in SLP server ## Type: ("yes" | "") ## Default: "" ## Config: OBS # # OBS_USE_SLP="" ## Path: Applications/OBS ## Description: Register in SLP server ## Type: string ## Default: "" ## Config: OBS # # OBS_CACHE_DIR="" ## Path: Applications/OBS ## Description: Register in SLP server ## Type: size in MB ## Default: "" ## Config: OBS # OBS_CACHE_SIZE="" -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 584062] New: Xorg Repository broken with KMS (invalid buffer id)
by bugzilla_noreply＠novell.com 05 Mar '10

05 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=584062 http://bugzilla.novell.com/show_bug.cgi?id=584062#c0 Summary: Xorg Repository broken with KMS (invalid buffer id) Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: death_knight(a)gamebox.net QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.2 Firefox/3.6 My setup is 64 bit 11.2 with vanilla 2.6.33 kernel, drm, mesa and ati from git trunk... I was use my 11.2 with KMS support with r600 (790GX) without any problem. But some day (~3-4 weeks ago) new xorg upgrades are released at http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_11.2/ I think it's standard Xorg repo for OpenSUSE 11.2 so I fill this bug report. My computer update newer packages. After update, X starts closing. I can log into X and can run Compiz without problem. But when I start some applications, X kills and take me back to login screen. Some applications doesn't make such an restart (like firefox) but others restart (like codeblocks, wxHexEditor...) "dmesg" has only one line about problem which is: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id And there is no error message at /var/Xorg.0.log and /var/Xorg.0.log.old. I remove all x11 packages and installed X11 packages from 11.2 DVD, recompiled git trunk codes (at ati,mesa,drm) and KMS works. Nothing changed at system but this and system is working. So I decide this is X packages bug. But this time, dmesg says "you are using old user space... etc" I love KMS because standard Mesa without KMS has problems with graphics (leaves lots of artifacts.) Also bug reporting is disabled for this repo. I don't understand why. I wish developers are aware this problem from now and could cure the problem. Reproducible: Always Steps to Reproduce: 1.Update Xorg with http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_11.2/ 2.Update Vanilla kernel 2.6.33 with KMS support. 3.Compile & install drm, mesa and ati from git trunk. 4.Login to user account. (GTK) 5.Try to run codeblocks or wxHexEditor...etc programs. (Doesn't kill X on some other programs like firefox, nautilus...) Actual Results: That restarts X. Added kernel message: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id Expected Results: Doesn't kill X -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 507321] New: UMTS fails to connect with Nozomi card (regression since 11.1): Looks like pppd didn't initialize our dbus module
by bugzilla_noreply＠novell.com 04 Mar '10

04 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=507321 Summary: UMTS fails to connect with Nozomi card (regression since 11.1): Looks like pppd didn't initialize our dbus module Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: i386 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Mobile Devices AssignedTo: mobile-bugs(a)forge.provo.novell.com ReportedBy: gp(a)novell.com QAContact: qa(a)suse.de CC: seife(a)novell.com Found By: --- The very same system - a T41p with a Nozomi base card -- running 11.0 or 11.1 has been working just fine, alas with current FACTORY I only get the following: May 26 12:13:54 rana NetworkManager: <info> (/dev/noz0): device state change: 2 -> 3 May 26 12:14:19 rana NetworkManager: <info> Activation (/dev/noz0) starting connection 'Vodafone' May 26 12:14:19 rana NetworkManager: <info> (/dev/noz0): device state change: 3 -> 4 May 26 12:14:19 rana NetworkManager: <info> Activation (/dev/noz0) Stage 1 of 5 (Device Prepare) scheduled... May 26 12:14:19 rana NetworkManager: <info> Activation (/dev/noz0) Stage 1 of 5 (Device Prepare) started... May 26 12:14:19 rana NetworkManager: <info> Activation (/dev/noz0) Stage 1 of 5 (Device Prepare) complete. May 26 12:14:20 rana NetworkManager: <info> Activation (/dev/noz0) Stage 2 of 5 (Device Configure) scheduled... May 26 12:14:20 rana NetworkManager: <info> Activation (/dev/noz0) Stage 2 of 5 (Device Configure) starting... May 26 12:14:20 rana NetworkManager: <info> (/dev/noz0): device state change: 4 -> 5 May 26 12:14:20 rana NetworkManager: <info> Starting pppd connection May 26 12:14:20 rana NetworkManager: <debug> [1243332860.265589] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute /dev/noz0 noipdefault usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so May 26 12:14:20 rana NetworkManager: <debug> [1243332860.283222] nm_ppp_manager_start(): ppp started with pid 3229 May 26 12:14:20 rana NetworkManager: <info> Activation (/dev/noz0) Stage 2 of 5 (Device Configure) complete. May 26 12:14:35 rana NetworkManager: <WARN> pppd_timed_out(): Looks like pppd didn't initialize our dbus module May 26 12:14:35 rana NetworkManager: <info> (/dev/noz0): device state change: 5 -> 9 May 26 12:14:35 rana NetworkManager: <info> Marking connection 'Vodafone' invalid. May 26 12:14:35 rana NetworkManager: <info> Activation (/dev/noz0) failed. Interestingly umtsmon does not get to its main screen either, a "Waiting for SIM Interface" popup appearing, so this may well be a kernel issue? Or ModemManager locking something? -- 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 19

[Bug 421159] Yast2 xen installing doesn't take all proxy settings in account (no_proxy)
by bugzilla_noreply＠novell.com 04 Mar '10

04 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=421159 http://bugzilla.novell.com/show_bug.cgi?id=421159#c9 James Fehlig <jfehlig(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|jmatejek(a)novell.com | Resolution| |DUPLICATE --- Comment #9 from James Fehlig <jfehlig(a)novell.com> 2010-03-04 23:47:45 UTC --- So this bug is a dup of 581949. Closing. *** This bug has been marked as a duplicate of bug 581949 *** http://bugzilla.novell.com/show_bug.cgi?id=581949 -- 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 0

[Bug 576169] New: NetworkManager-0.7.998_20100120 doesn't respect hostname
by bugzilla_noreply＠novell.com 04 Mar '10

04 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=576169 http://bugzilla.novell.com/show_bug.cgi?id=576169#c0 Summary: NetworkManager-0.7.998_20100120 doesn't respect hostname Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: lmedinas(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.2 Firefox/3.6 I upgraded from G:S:2.28 to G:F and NM doesn't set my hostname anymore Previously it was "tesla" now it's localhost Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 325753] Please install/enable email notification for the openSUSE wiki site
by bugzilla_noreply＠novell.com 04 Mar '10

04 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=325753 http://bugzilla.novell.com/show_bug.cgi?id=325753#c17 Matthew Ehle <mehle(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |tschmidt(a)novell.com --- Comment #17 from Matthew Ehle <mehle(a)novell.com> 2010-03-04 20:35:52 UTC --- Could I get some more detail on what is needed in this case? I'm assuming you need basic sendmail. Is this correct? -- 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 0

[Bug 473948] unable to turn off tx checksumming MCP55 (NVidia NForce chipset)
by bugzilla_noreply＠novell.com 04 Mar '10

04 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=473948 http://bugzilla.novell.com/show_bug.cgi?id=473948#c10 Brandon Philips <bphilips(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |UPSTREAM --- Comment #10 from Brandon Philips <bphilips(a)novell.com> 2010-03-04 19:39:58 UTC --- Thanks. Fixed upstream and in opensuse 11.2. Closing. -- 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 0

[Bug 585219] New: tar version does not support access control lists (acl)
by bugzilla_noreply＠novell.com 04 Mar '10

04 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=585219 http://bugzilla.novell.com/show_bug.cgi?id=585219#c0 Summary: tar version does not support access control lists (acl) Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 2 Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: j.lange(a)epic.ca QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.9 (KHTML, like Gecko) Chrome/5.0.307.7 Safari/532.9 The tar version in openSUSE and SLED/S does not support --acls. This is strange because it appears to be the most recent version of GNU tar which I believe supported acls back as far as 1.14 though I'm not really sure. Among other things, I suspect this would break the Yast based backup and restore tools since all ACL would be lost during a restore. Also, the SLE training that Novell offers also has an entire section dedicated to advanced access control lists so it would seem important to support them with tar. The solution does not seem to be as simple as a version upgrade since SUSE seems to have the most recent version of GNU tar, yet acl support is not included even though GNU tar seems to have had this for quite some time, at least according to this man page: http://linux.die.net/man/1/tar Reproducible: Always -- 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 2