July 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 735016] New: Zypper eats previous lines in terminal
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=735016 https://bugzilla.novell.com/show_bug.cgi?id=735016#c0 Summary: Zypper eats previous lines in terminal Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: anixx(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.1.19) Gecko/20110420 SUSE/2.0.14-0.2.1 SeaMonkey/2.0.14 When updating repositories zypper prints information about each updated repo not in the next line, but each time one line upper, with erasing the line below. This happens until it eats all lines to the top on the console window. 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 29

[Bug 754286] New: Update candidate needs to be recomputed if solver::allowVendorChange changes.
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=754286 https://bugzilla.novell.com/show_bug.cgi?id=754286#c0 Summary: Update candidate needs to be recomputed if solver::allowVendorChange changes. Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: ma(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- The YaST ui meanwhile supports changeing the allowVendorChange flag at runtime, so caching the update candidate requires invalidation if the flag changes. -- 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 751221] New: Bad media attach point / AP_* sometimes stay if yast/zypper are aborted
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=751221 https://bugzilla.novell.com/show_bug.cgi?id=751221#c0 Summary: Bad media attach point / AP_* sometimes stay if yast/zypper are aborted Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: ma(a)suse.com QAContact: qa(a)suse.de Found By: Customer Blocker: --- > Checked the code. For whatever reason (code is several years old) > we don't create more than 1000 AP_*. > We know AP_* sometimes stay if yast/zypper are aborted. No matter why > this happened, we need a garbage collection to cleanup the leftovers. Need cleanup of orphaned /var/adm/mount/AP_0x* -- 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 769853] New: suspend2disk and reboot fails after usage of USB mass storage device
by bugzilla_noreply＠novell.com 03 Jul '12

03 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=769853 https://bugzilla.novell.com/show_bug.cgi?id=769853#c0 Summary: suspend2disk and reboot fails after usage of USB mass storage device Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: lmuelle(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Community User Blocker: Yes This is a Dell workstation with a plain openSUSE 12.1 i686 install. In use are the oss, non-oss, update, and packman repositories. s2disk and reboot works well till an USB mass storage device was used. Even removing the additionally loaded modules before the reboot/ s2disk request doesn't change the failing behavior. -- 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 11

[Bug 749032] New: System does not go to sleep when closing lid
by bugzilla_noreply＠novell.com 03 Jul '12

03 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=749032 https://bugzilla.novell.com/show_bug.cgi?id=749032#c0 Summary: System does not go to sleep when closing lid Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: erwin.vandevelde(a)gmail.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1022.0 Safari/535.19 SUSE/18.0.1022.0 When Closing the lid of my laptop, it does not go to sleep, but logs following error in /var/log/messages: [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH Reproducible: Always Steps to Reproduce: 1. Close lid of laptop 2. Notice it does not go to sleep 3. Check /var/log/messages Actual Results: Laptop does not go to sleep Expected Results: Laptop should go to sleep Laptop: Lenovo Thinkpad T520 Intel 3000HD graphics OpenSuse 12.1 with kernel 3.1.9-1.4-desktop and xorg-x11 7.6-67.3.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 8

[Bug 742764] New: High power consumption after suspend
by bugzilla_noreply＠novell.com 03 Jul '12

03 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=742764 https://bugzilla.novell.com/show_bug.cgi?id=742764#c0 Summary: High power consumption after suspend Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: srid(a)rkmail.ru QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=472203) --> (http://bugzilla.novell.com/attachment.cgi?id=472203) modified 00powersave script User-Agent: Opera/9.80 (X11; Linux x86_64; U; ru) Presto/2.10.229 Version/11.60 I have asus u30sd laptop, and after resuming from suspend it starts to consume more power. There is no much difference if it is s2ram or s2disk. But if I plug in AC adapter, and then plug it off, power consumption will restore to it's normal level. I, personally, think it is a hardware problem, bad acpi, dsdt or whatever, but I've found an easy workaround: On resume force computer to use maximum power (#pm-powersave false), like it is on AC, and then run pm-powersave again with no parameters. The difference is 7-8W vs 10-11W in my case. My modified /usr/lib/pm-utils/sleep.d/00powersave (/etc/pm/sleep.d/00powersave) is in attachment Reproducible: Sometimes Steps to Reproduce: 1. Start your laptop 2. measure power consumption 3. suspend it 4. measure power consumption after resume 5. if there is no difference, repeat 3-4 several times Actual Results: Power consumption after resume is higher than normal (7-8W vs 10-11W in my case) I'm using openSUSE 12.1, sysvinit, kernel 3.1.9 from obs:Kernel:openSUSE-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 7

[Bug 741784] New: Enabling hyper threading leads to random freezes during boot up
by bugzilla_noreply＠novell.com 03 Jul '12

03 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=741784 https://bugzilla.novell.com/show_bug.cgi?id=741784#c0 Summary: Enabling hyper threading leads to random freezes during boot up Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: choroba(a)matfyz.cz QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 When booting kernel-default, kernel-desktop, or kernel-vanilla, enabling hyper threading leads to random freezes during bootup. Sometimes, messages are displayed (often incomplete) like "BUG: unable to handle kernel initcall acpi_processor_init +0x0/0x100 [processor] returned with preemption imbalance" or "BUG: unable to handle kernel paging request" or "scheduling while atomig" or just plain SIGSEGV or kernel panic. The only working option is "acpi=off", but system cannot be powered off with it (it just halts). The workaround is to disable HT in BIOS, then booting is possible without any options, but with only 1 cpu. Switching to sysvinit in the boot screen does not help. Reproducible: Sometimes Steps to Reproduce: 1. Turn on/reboot the computer 2. Specify acpi=ht or similar on the init line 3. Wait. If system boots succesfully, return to 1. The failure is far more common than success. Actual Results: The system freezes at various stages, usualy around "hub usb" and "rtc" initialization. Expected Results: The system should boot up and run on both CPUs. The bug might be related to https://bugzilla.novell.com/show_bug.cgi?id=731595. Motherboard: D865PERL, BIOS updated around 2007 CPU: vendor_id : GenuineIntel cpu family : 15 model : 3 model name : Intel(R) Pentium(R) 4 CPU 2.80GHz stepping : 3 cpu MHz : 2793.155 cache size : 1024 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc up pebs bts pni dtes64 monitor ds_cpl cid bogomips : 5586.31 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 32 bits virtual power management: Memory: 2GB -- 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 594232] New: Mysql is not starting automagically after install
by bugzilla_noreply＠novell.com 03 Jul '12

03 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=594232 http://bugzilla.novell.com/show_bug.cgi?id=594232#c0 Summary: Mysql is not starting automagically after install Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: i686 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mauropm(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 mysql server package need a modification in post install, so it can start the service right away. Additionally, need to be added to xinetd or similar, so it can restart everytime the machine restarts. Reproducible: Always Steps to Reproduce: 1. Install build 542. 2. Select GNOME 3. Install mysql server via zypper command (zypper in mysql-server). 4. Mysql won't start by itself. Actual Results: Mysql installed, no start. Expected Results: Mysql Server is actually being installed. If you start it manually, will work just fine. -- 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 591437] New: kernel fails to resume from hibernate although hibernation looks OK
by bugzilla_noreply＠novell.com 03 Jul '12

03 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=591437 http://bugzilla.novell.com/show_bug.cgi?id=591437#c0 Summary: kernel fails to resume from hibernate although hibernation looks OK Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: schaiba(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=350839) --> (http://bugzilla.novell.com/attachment.cgi?id=350839) a snip from /var/log/messages . User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 kernel-desktop-2.6.31.12-0.2.1.x86_64 fails to resume from hibernate; the system comes up, but freezes, leaving me with a lot of console messages. I did a 'sudo /var/log/messages | grep $time_of_resume > fail_suspend; will attach the file. 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 8

[Bug 602638] New: mysql after patch reports corrupt SQL and dies
by bugzilla_noreply＠novell.com 03 Jul '12

03 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=602638 http://bugzilla.novell.com/show_bug.cgi?id=602638#c0 Summary: mysql after patch reports corrupt SQL and dies Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jimc(a)math.ucla.edu QAContact: qa(a)suse.de Found By: Community User Blocker: --- Context: MythTV box with MySQL database, up to date on SuSE patches. Identification of today's patch: version 1706 dated 1260888174 PATCHINFO 74ffcb3d975f99b39204a9a17088e978, mysql-5.1.36-6.8.8.i586.rpm, id libmysqlclient-devel (including mysql itself and all libraries and clients) What happened: After applying today's patches, of which this one is the only one relevant to MythTV, I shut down the box in the normal way. It woke at the next scheduled time and recorded a program (meaning it must have successfully made several database queries), but then the Myth backend logged one complaint from MySQL of a SQL syntax error, and in subsequent queries the error message was "MySQL server has gone away", with an obvious bad effect on later recordings. /etc/init.d/mysql status said "running". I stopped the backend, then MySQL, and restarted them in the opposite order. After that I was able to record a program (as a test); we'll see tomorrow if scheduled recordings happen. What I want the developers to do: I'm pointing the finger of blame at today's mysql patch because nothing else changed. I'm sorry that there's not more evidence from which a mechanism could be nailed down. If other users report mysterious MySQL behavior, this report can be taken as corroboration that something is going on connected with this patch. -- 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