September 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 237741] provide in-compiled debuginfo packages
by bugzilla_noreply＠novell.com 01 Sep '11

01 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=237741 https://bugzilla.novell.com/show_bug.cgi?id=237741#c zj jia <zjjia(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia(a)suse.com AssignedTo|bnc-team-screening(a)forge.pr |bnc-team-xorg-bugs(a)forge.pr |ovo.novell.com |ovo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 715257] New: home:mihneadb: Bug bugreporter interprete left file key as symbol and not as a curser move
by bugzilla_noreply＠novell.com 01 Sep '11

01 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=715257 https://bugzilla.novell.com/show_bug.cgi?id=715257#c0 Summary: home:mihneadb: Bug bugreporter interprete left file key as symbol and not as a curser move Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: mihneadb(a)gmail.com ReportedBy: melchiaros(a)aol.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: No As the summary says. See console output: bugreporter Welcome to the submit bug report module! The user has stored credentials. Connecting to Novell's Bugzilla... If you don't know which package you want to file a bug to, you can use the susebugreport aid command to get some help. Which is the package you want to file a report against? If you are not sure, you can just type the beginning of the name and use a '*' to invoke globbing. Also, you can type '?' to start the aid_user module that helps finding the correct package name. Package name (or '?'): ? Available modules: 1. Find app - click on a window to find the application's name. 2. Find package - enter an executable's name to find its package. Which one? Enter a valid index number between 1 and 2: Index: 1 Please click on the window of which you want to find the app name. The app's name is plasma. Package name (or '?'): [preselected: plasma] ? Available modules: 1. Find app - click on a window to find the application's name. 2. Find package - enter an executable's name to find its package. Which one? Enter a valid index number between 1 and 2: Index: 1 Please click on the window of which you want to find the app name. The app's name is yast2. Package name (or '?'): [preselected: yast2] yast2 Package selected: yast2 Please enter the bug summary (should be short!) --> just a test of the bugreporte ^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D Summary entered: just a test of the bugreporte -- 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 667938] New: yast2: don't require yast2-branding
by bugzilla_noreply＠novell.com 01 Sep '11

01 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=667938 https://bugzilla.novell.com/show_bug.cgi?id=667938#c0 Summary: yast2: don't require yast2-branding Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: jsrain(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- yast2 requires yast2-branding. Therefore even on a minimal install with only ncurses available yast causes installation of e.g. hicolor-icon-theme. Moreover, the Supplements: packageand(yast2:branding-openSUSE) in the branding packages are also wrong for the same reason. The Supplements should trigger either trigger on the graphical frontends or the graphical front-end packages should require branding. -- 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 714262] New: yast2 depends on yast2-theme-openSUSE-any
by bugzilla_noreply＠novell.com 01 Sep '11

01 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=714262 https://bugzilla.novell.com/show_bug.cgi?id=714262#c0 Summary: yast2 depends on yast2-theme-openSUSE-any Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: richlv(a)nakts.net QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux i686; U; en) Presto/2.9.168 Version/11.50 yast2 depends on yast2-branding and that in turn depends on yast2-theme-openSUSE-any all of the yast2-theme-openSUSE* packages are for the gui yast (containing icons), which are not needed for cli (ncurses ?) yast. thus even on a cli-only system unneeded package with icons will be always be installed. this is highly inconvenient when attempting to create appliances and focusing on size reduction. it would be preferred if only corresponding gui counterparts (qt, gtk) of yast frontend would depend on yast2-theme-openSUSE-any (or yast2-branding-openSUSE) 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 3

[Bug 715372] New: Apache Security Release
by bugzilla_noreply＠novell.com 01 Sep '11

01 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=715372 https://bugzilla.novell.com/show_bug.cgi?id=715372#c0 Summary: Apache Security Release Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: SLES 11 Status: NEW Severity: Critical Priority: P5 - None Component: Apache AssignedTo: bnc-team-apache(a)forge.provo.novell.com ReportedBy: mattehle(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.1) Gecko/20100101 Firefox/6.0.1 Apache recently released 2.2.20, which is an important security fix. Please get this in the repositories as soon as possible. Apache releases prior to this are vulnerable to a DoS attack that takes advantage of the way Apache handles the byte-range header. An attacker can use this method to quickly take down Apache and seize up the whole server, sometimes requiring a reboot of the machine. Reproducible: Always Steps to Reproduce: 1. Download and run the Apache Killer script (http://seclists.org/fulldisclosure/2011/Aug/att-175/killapache_pl.bin) 2. Wait 30-60 seconds Actual Results: Apache will start swapping to disk and the whole server will become unresponsive for a long time. Expected Results: The new release ignores abusive byte-range headers and serves up the whole document. -- 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 66013] pthread_rwlock_rdlock: blocking error
by bugzilla_noreply＠novell.com 01 Sep '11

01 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=66013 https://bugzilla.novell.com/show_bug.cgi?id=66013#c10 Cyril Hrubis <chrubis(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|pmorreale(a)novell.com | --- Comment #10 from Cyril Hrubis <chrubis(a)suse.com> 2011-09-01 08:07:42 UTC --- Greg, we are actually fixing the LTP testcases and proved many of them wrong and fixed them, we just couldn't find anything wrong with this one (minus some coding style). So it would be great if somebody else could look at this as well. The test source wasn't most likely touched since 2002 (besides some minor whitespace cleanup), at least the git history says so. And as far as I understand the POSIX threads the read lock should not be obtained if there is writer locked or blocked on the lock and the writer has higher or equal priority. Unfortunately the reader gets the lock here. -- 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 0

[Bug 267306] /etc/init.d/ddclient can't see ddclient running
by bugzilla_noreply＠novell.com 01 Sep '11

01 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=267306 https://bugzilla.novell.com/show_bug.cgi?id=267306#c5 --- Comment #5 from Bernhard Wiedemann <bwiedemann(a)suse.com> 2011-09-01 10:00:10 CEST --- This is an autogenerated message for OBS integration: This bug (267306) was mentioned in https://build.opensuse.org/request/show/80461 Factory / ddclient -- 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 0

[Bug 713330] New: lockdev patch breaks interoperability of minicom and mgetty
by bugzilla_noreply＠novell.com 01 Sep '11

01 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=713330 https://bugzilla.novell.com/show_bug.cgi?id=713330#c0 Summary: lockdev patch breaks interoperability of minicom and mgetty Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dieter.jurzitza(a)t-online.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20100101 Firefox/5.0 patch 3 (lockdev patch) stops minicom from creating /var/lock - Lockfiles. This in turn breaks interoperability with mgetty, since mgetty relies on the presence of lockfiles. Reproducible: Always Steps to Reproduce: 1. start minicom when mgetty is active 2. minicom will hang short time 3. kill it Actual Results: minicom hangs due to concurrent port access with mgetty Expected Results: no hanging minicom :-) I removed patch 3 (lockdev-patch) and things come back into operation. Please fix! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 13

[Bug 715238] New: yast2 Product Creator - wrong disk space in select software dialog
by bugzilla_noreply＠novell.com 01 Sep '11

01 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=715238 https://bugzilla.novell.com/show_bug.cgi?id=715238#c0 Summary: yast2 Product Creator - wrong disk space in select software dialog Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: melchiaros(a)aol.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=448683) --> (http://bugzilla.novell.com/attachment.cgi?id=448683) screenshot User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 I´am on openSUSE12.1 MS which is brought to http://download.opensuse.org/factory-tested/repo/ (all there - 18.8.2011) In yast2 Product creator module there is a error in the Software selection dialog: It shows a diskspace of 999.00GB, which is not correct( only 80GB are there). -> See screenshot Reproducible: Always Steps to Reproduce: 1.Product creation with yast2 2.chose tree creation; not iso 3.See the software selection dialog -- 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 627901] New: occassionally system freezes with kbd and mouse dead
by bugzilla_noreply＠novell.com 01 Sep '11

01 Sep '11

http://bugzilla.novell.com/show_bug.cgi?id=627901 http://bugzilla.novell.com/show_bug.cgi?id=627901#c0 Summary: occassionally system freezes with kbd and mouse dead Classification: openSUSE Product: openSUSE 11.3 Version: RC 2 Platform: i686 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: p.bhat(a)gramtechnet.co.in QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.4; Linux) KHTML/4.4.4 (like Gecko) SUSE As above. When it happens, removing and re-inserting mouse has no effect.Caps lock,Num lock do not work.Though I have SysRq configured, with Alt+SysRq+e OR Alt+SysRq+i have no effect.As this is a laptop, I have no remote access to the system and cannot check. This occurrence is more frequent when the OS is run from a Live USB key.This can be reproduced in half an hour.On hard-disk based system, it occurs once in a few days. Almost always I have seen the freeze triggered by Mouse action, possibly mouse-wheel action.My mouse is USB mouse.Built in mouse pad is not working and I cannot check. Reproducible: Sometimes Steps to Reproduce: On a live system, run from pen-drive 1.Run the system 2.Keep working with USB mouse 3.In half an hour you should see a freeze. If you need any log file, I can send. I am classifying this as major, as it makes working in live system booted off a thumb drive impossible. -- 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 20