November 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 731306] New: qbankmanager-0.9.52beta has broken dependence
by bugzilla_noreply＠novell.com 04 Mar '12

04 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=731306 https://bugzilla.novell.com/show_bug.cgi?id=731306#c0 Summary: qbankmanager-0.9.52beta has broken dependence Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: melchiaros(a)aol.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 yast2 tells me that qbankmanager-0.9.52beta-2.4.x86_64 needs libaqbanking.so29()(64bit), which is not available. Please provide the correct libaqbanking with qbankmanager. Reproducible: Always Steps to Reproduce: 1.call yast2 install software 2.try to install qbankmanager(version see above) 3.see the broken dependence package This package is in teh community KDE:KDE3 repository. -- 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 531677] New: rdesktop doesn't handle Alt+Tab and other special keyboard combinations
by bugzilla_noreply＠novell.com 04 Mar '12

04 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=531677 Summary: rdesktop doesn't handle Alt+Tab and other special keyboard combinations Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: stefan.heine(a)hp.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 using rdesktop to connect to a Windows box. trying to use Alt-Tab to switch the applications inside the Windows system - but instead, it switches the applications on the Linux level. actually this behavior should be configurable in rdesktop with the '-K' option, with the default to 'to grab all keyboard input when it is in focus' (man rdesktop). but in the version of rdesktop in openSUSE 11.1 it doesn't act that way. openSUSE 11.0 worked ok, and compiling the rdesktop 1.60 from the developer source also brings the expected behavior. Reproducible: Always Steps to Reproduce: 1. rdesktop <win box> 2. after login, press 'Alt+Tab' Actual Results: you'll find the Linux applications switching instead of the Windows apps Expected Results: the Alt+Tab should be handled inside rdesktop and passed to Windows. same behavior for other important keyboard combinations used in Windows, like Ctrl+Alt+Del. -- 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 620439] New: externel monitor does not work with kernel modesetting
by bugzilla_noreply＠novell.com 03 Mar '12

03 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=620439 http://bugzilla.novell.com/show_bug.cgi?id=620439#c0 Summary: externel monitor does not work with kernel modesetting Classification: openSUSE Product: openSUSE 11.3 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: estellnb(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 I have to boot with nomodeset in order to make my external monitor display anything. Otherwise it simply stays dark. Curiously the external monitor is recognized correctly even with kernel modesetting - and it can be configured comfortably under KDE. However it simply stays dark no matter what you do. This is not only to be observed with Xorg but also the same for the text consoles vt01-vt05 (ext. monitor also dark here). However as soon as you boot with nomodeset, the text consoles use both monitors in clone mode and there is no problem with Xorg. (During kernel initialization there are always both monitors up no matter whether you use nomodeset). Tested with both kernels(2.6.34-12.1 & -9.3) of RC1 and RC2. For both it is utterly the same play (tested extensively). 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 15

[Bug 722266] New: Shutter does not run, crashes at start
by bugzilla_noreply＠novell.com 03 Mar '12

03 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=722266 https://bugzilla.novell.com/show_bug.cgi?id=722266#c0 Summary: Shutter does not run, crashes at start Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: i586 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: EagleScreen(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Shutter application does not run on 12.1 Factory. It gives this error in terminal: Can't locate Sort/Naturally.pm in @INC (@INC contains: /usr/share/shutter/resources/modules /usr/lib/perl5/site_perl/5.14.1/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.14.1 /usr/lib/perl5/vendor_perl/5.14.1/i586-linux-thread-multi /usr/lib/perl5/vendor_perl/5.14.1 /usr/lib/perl5/5.14.1/i586-linux-thread-multi /usr/lib/perl5/5.14.1 /usr/lib/perl5/site_perl .) at /usr/bin/shutter line 123. Reproducible: Always Steps to Reproduce: 1.Install "shutter", the advanced screen-shot application. 2.Try to launch it from applications menu or from terminal. 3.You will see that it never starts. Actual Results: You will see that it never starts. Expected Results: The application should start. -- 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 18

[Bug 726194] New: iwlagn: kernel panic when connecting to wifi access point
by bugzilla_noreply＠novell.com 03 Mar '12

03 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=726194 https://bugzilla.novell.com/show_bug.cgi?id=726194#c0 Summary: iwlagn: kernel panic when connecting to wifi access point Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: alex239(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=458564) --> (http://bugzilla.novell.com/attachment.cgi?id=458564) photo of a dump trace (I have 3 more at different moments) User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.910.0 Safari/535.7 SUSE/16.0.910.0 Starting with at least milestone 5 (MS4 was working fine until the upgrade) connecting to a wifi base station kills my laptop with kernel panic. The problem still persists on RC1. It does not depend on the network control method or user settings. The iwlagn module itself loads OK, but at the moment of connection establishing (e.g. on graphical login for PNM) kernl just crashes, so I had to blacklist iwlagn in order to start KDE successfully and finally report this nasty bug. I have a 100% reproducibility of this crash. Reproducible: Always Steps to Reproduce: 1.modprobe iwlagn 2.try to connect to some wifi point (no matter with PNM or ifup) 3.see the dump trace about hard cpu lockup =) Actual Results: kernel panics Expected Results: wifi works out of the box as it used earlier My wifi adapter: 04:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N + WiMAX 6250 [8086:0087] (rev 5e) Subsystem: Intel Corporation Centrino Advanced-N + WiMAX 6250 2x2 ABG [8086:1306] My kernel-desktop: 3.1.rc9-1.2 My kernel-firmware: 20110709-8.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 14

[Bug 675960] New: programs start slower if entropy pool is drained
by bugzilla_noreply＠novell.com 02 Mar '12

02 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=675960 https://bugzilla.novell.com/show_bug.cgi?id=675960#c0 Summary: programs start slower if entropy pool is drained Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: meissner(a)novell.com QAContact: qa(a)suse.de CC: bg(a)novell.com, security-team(a)suse.de Found By: Development Blocker: --- various observations from our autobuild team seem to show that when the entropy pool is drained, programs start slower. It is not yet clear why. mmap randomization and AT_RANDOM elf vector use the "nonblocking" entropy pool (which I hope is non-blocking), so it should not affect this. -- 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 670914] New: tmpfs timeout when boot
by bugzilla_noreply＠novell.com 02 Mar '12

02 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=670914 https://bugzilla.novell.com/show_bug.cgi?id=670914#c0 Summary: tmpfs timeout when boot Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: eulenreich(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 Using openSUSE11.3 with Tumbleweed (kernel 2.6.37) Since the last two kernels I have when boot: myshm waiting ..... timeout But this entry from /etc/fstab is mounted: myshm /var/shmtmp tmpfs auto,rw,nosuid,nodev,relatime,mode=777 0 As you see from mounts: myshm on /var/shmtmp type tmpfs (rw,nosuid,nodev,relatime,mode=777) And as you see df: myshm 1,8G 0 1,8G 0% /var/shmtmp 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 3

[Bug 702217] New: syslog-ng stats_freq option not interpreted correctly
by bugzilla_noreply＠novell.com 02 Mar '12

02 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=702217 https://bugzilla.novell.com/show_bug.cgi?id=702217#c0 Summary: syslog-ng stats_freq option not interpreted correctly Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jschrod(a)acm.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.19) Gecko/20110420 SUSE/2.0.14-4.1 SeaMonkey/2.0.14 syslog-ng 3.2.2-5.1: When one uses the option stats_freq(60140); a statistics log record should be output roughly every week. Instead it's output every 10 seconds. That number 10 depends on 60140, if I change the latter, the former changes accordingly. Reproducible: Always Steps to Reproduce: 1. Add option stats_freq(60140); to syslog-ng.conf 2. Restart syslog-ng. 3. Wait 10 seconds. :-) Actual Results: Statistics log message is output every 10 seconds. Expected Results: Statistics log message should be output every 60140 seconds. 60140 seconds is, of course, a contrived example. I wanted weekly stats records (i.e., every 60480 seconds). But then you have to wait ca. 6 minutes for the superfluous log records. ;-) -- 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 727489] New: firefox locks up frequently, during startup
by bugzilla_noreply＠novell.com 01 Mar '12

01 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=727489 https://bugzilla.novell.com/show_bug.cgi?id=727489#c0 Summary: firefox locks up frequently, during startup Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: rcoe(a)wi.rr.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Name : MozillaFirefox Version : 7.0.1 Release : 1.1 Architecture: x86_64 Build Date : Sun 02 Oct 2011 09:40:45 AM CDT Firefox locks up frequently. I've noticed it when it starts up, that it is unresponsive for several minutes. The UI does not respond to mouse clicks and overlapping windows leave their impression on the UI. I've also noticed it when FF is downloading an file to save, like a tar file the first time a file gets downloaded. It was so busy (or out) that it never put up the downloading dialog box. There have been one or two other times where the UI is not responsive, but I did not associate it with a user action or startup. I was running FF 7.0 under 11.4 and didn't not observe this issue. 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 11

[Bug 650379] New: buildservice authentication seems to be broken
by bugzilla_noreply＠novell.com 01 Mar '12

01 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=650379 https://bugzilla.novell.com/show_bug.cgi?id=650379#c0 Summary: buildservice authentication seems to be broken Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: admin(a)eregion.de QAContact: adrian(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-1.1 Firefox/3.6.12 as soon as i log in to build.opensuse.org i cannot perform the si8mplest operations, not even operations that are allowed for anonymous access. All i get is this error: The account that is logged into the system lacks proper permissions to perform the operation. Please contact the openSUSE admin to get proper permissions for the user account. my username on OBS: lemmy04 Reproducible: Always Steps to Reproduce: 1. login to obs on my account 2. click on a link Actual Results: the above error Expected Results: whatever the link is supposed to do -- 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 722715] New: Update STIX Fonts (stix-fonts)
by bugzilla_noreply＠novell.com 01 Mar '12

01 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=722715 https://bugzilla.novell.com/show_bug.cgi?id=722715#c0 Summary: Update STIX Fonts (stix-fonts) Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: burnus(a)gmx.de QAContact: qa(a)suse.de CC: pgajdos(a)suse.com Found By: --- Blocker: --- STIX fonts are a set of mathematical fonts, which have been created by several publishing houses. They were designed to be compatible with the Times font. openSUSE contains the 1.0 version of the font; however, the 1.1 version is much more usable in normal applications and also in XeTeX/LUATeX. Currently, only the 1.1beta1 is available; given that the application support is much better, one should consider updating now; however, one might also wait for a new beta or until the final release is available. However, given the past experience, updates are relatively slow and the estimated dates were other very optimistic. (Current statement: "The beta period will remain open until December 1, 2011.") See http://www.stixfonts.org/ -- The font itself is available at http://sourceforge.net/projects/stixfonts/files/STIXv1.1.0-beta1.zip/downlo… >From the release notes: "What is new in this release? The original Version 1.0 STIX was packaged as 29 distinct font files. Version 1.1.0-‐beta1 provides the same set of glyphs packaged as a set of 4 text fonts and 1 symbol font. This new packaging will facilitate the use of the font on more desktop applications, and will specifically allow the symbol font to be used in recent versions of the Microsoft Word Equation Editor." "In addition, an update was made to address compatibility issues between the font set and the Windows PostScript driver." Besides those changes, some a (very) few glyphs have been added and some smaller changes have been done. -- 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 5

[Bug 731736] New: Invalid kernel OpCode with BTRFS
by bugzilla_noreply＠novell.com 01 Mar '12

01 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=731736 https://bugzilla.novell.com/show_bug.cgi?id=731736#c0 Summary: Invalid kernel OpCode with BTRFS Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: colin.walls(a)bt.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=463186) --> (http://bugzilla.novell.com/attachment.cgi?id=463186) Dump of dmesg output User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 This is similar to bug 716582. However my systems is an AMD-64 box rather than an old Pentium system. I have two BTRFS file systems, one for root and one for my home directories. After a clean power-off the system will no longer boot. On investigation it is during the mount of my home directories. Commenting out the line in /etc/fstab that mounts these allows the system to boot normally, if uselessly. Reproducible: Always Steps to Reproduce: 1. Boot the system with an entry in /etc/fstab to mount the home directories 2. 3. Actual Results: System refuses to load and drops to emergency shell Expected Results: System should boot to normal multi-user system My user id points to my old BT account. Could you please note that this has changed. I am now c.t.walls(a)btinternet.com. I would prefer to retain my current user id but with the modified mail address if at all possible -- 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 629854] New: openmpi/mpirun 1.2.8 crash when running any executable
by bugzilla_noreply＠novell.com 29 Feb '12

29 Feb '12

http://bugzilla.novell.com/show_bug.cgi?id=629854 http://bugzilla.novell.com/show_bug.cgi?id=629854#c0 Summary: openmpi/mpirun 1.2.8 crash when running any executable Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: g.macpherson(a)opencfd.co.uk QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8 Using mpirun from the version of openmpi that comes with the OpenSUSE 11.3 install fails to run any executable, it stops with an error message. Reproducible: Always Steps to Reproduce: mpirun -np 2 ls Actual Results: [myhost:21083] [NO-NAME] ORTE_ERROR_LOG: Not found in file runtime/orte_init_stage1.c at line 182 -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_rml_base_select failed --> Returned value -13 instead of ORTE_SUCCESS -------------------------------------------------------------------------- [myhost:21083] [NO-NAME] ORTE_ERROR_LOG: Not found in file runtime/orte_system_init.c at line 42 [myhost:21083] [NO-NAME] ORTE_ERROR_LOG: Not found in file runtime/orte_init.c at line 52 -------------------------------------------------------------------------- Open RTE was unable to initialize properly. The error occured while attempting to orte_init(). Returned value -13 instead of ORTE_SUCCESS. -------------------------------------------------------------------------- Expected Results: Return the result of "ls" twice. This problem occurs with the i586 version too, and when running as root. The version of openmpi from the build.opensuse.org/science repository (1.3.2) runs fine - tested for i586 only. As does a self-compiled recent version (1.4.1) - tested for x86_64 and i586. -- 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 628258] New: Release: magic on internal build service breaks build/quilt
by bugzilla_noreply＠novell.com 29 Feb '12

29 Feb '12

http://bugzilla.novell.com/show_bug.cgi?id=628258 http://bugzilla.novell.com/show_bug.cgi?id=628258#c0 Summary: Release: magic on internal build service breaks build/quilt Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: BuildService AssignedTo: adrian(a)novell.com ReportedBy: lmb(a)novell.com QAContact: adrian(a)novell.com CC: meissner(a)novell.com, mls(a)novell.com, ro(a)novell.com, bili(a)novell.com Found By: Development Blocker: --- The internal build service uses a magic marker in the spec files: Release: 0.<RELEASE5> Not only is this a pain when a submitreq is accepted (it seems this line very often causes a failed merge, requiring manual intervention - in particular if one manually changes this locally to a sane string and commits this), but it also breaks various tools. "quilt init" cannot handle this, and even worse, "osc build" can't either: .. Processing files: cluster-glue-debuginfo-1.0.6-0.<RELEASE5> Processing files: cluster-glue-debugsource-1.0.6-0.<RELEASE5> Processing files: libglue2-1.0.6-0.<RELEASE5> .. Wrote: /usr/src/packages/RPMS/x86_64/cluster-glue-debuginfo-1.0.6-0.<RELEASE5>.x86_64.rpm Wrote: /usr/src/packages/RPMS/x86_64/cluster-glue-debugsource-1.0.6-0.<RELEASE5>.x86_64.rpm Wrote: /usr/src/packages/RPMS/x86_64/libglue2-1.0.6-0.<RELEASE5>.x86_64.rpm Wrote: /usr/src/packages/RPMS/x86_64/libglue-devel-1.0.6-0.<RELEASE5>.x86_64.rpm .. .. running 09-check-packaged-twice sh: RELEASE5: No such file or directory sh: RELEASE5: No such file or directory sh: RELEASE5: No such file or directory sh: RELEASE5: No such file or directory .. RPMLINT report: =============== 0 packages and 0 specfiles checked; 0 errors, 1 warnings. Traceback (most recent call last): File "rpmlint.py", line 312, in <module> File "rpmlint.py", line 101, in main File "rpmlint.py", line 185, in runChecks File "BinariesCheck.py", line 360, in check IOError: [Errno 2] No such file or directory: '/tmp/libglue2-1.0.6-0.<RELEASE5>.x86_64.rpm.5609/etc/init.d/random' .. Perhaps using shell meta-characters in a Release: field is simply not such a good idea? -- 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 25

[Bug 726837] New: Evolution fails to connect to iCloud CalDAV (probably HTTP/parsing related)
by bugzilla_noreply＠novell.com 29 Feb '12

29 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=726837 https://bugzilla.novell.com/show_bug.cgi?id=726837#c0 Summary: Evolution fails to connect to iCloud CalDAV (probably HTTP/parsing related) Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: VMWare OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: b3738792(a)mailinator.com QAContact: lakhil(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 When trying to browse an iCloud CalDAV account, Evolution reports it cannot resolve a hostname, although the connection and password check have already been performed successfully. Reproducible: Always Steps to Reproduce: 1. File -> New -> Calendar 2. Type: Caldav 3. URL: caldav://caldav.icloud.com 4. Check "Use secure connection" 5. Enter iCloud username (form foo(a)bar.com) 6. Click "Browse for calendar" 7. Enter valid password Actual Results: Error message: "Server returned unexpected data. 2 - Cannot resolve hostname (caldav.icloud.comhttps)" [sic] Expected Results: Evolution should show a list of calendars. -- 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 732985] New: firefox: text is misrendered
by bugzilla_noreply＠novell.com 28 Feb '12

28 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=732985 https://bugzilla.novell.com/show_bug.cgi?id=732985#c0 Summary: firefox: text is misrendered Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jslaby(a)suse.com QAContact: qa(a)suse.de CC: eich(a)suse.com, kde-maintainers(a)suse.de, wolfgang(a)rosenauer.org Found By: --- Blocker: --- Created an attachment (id=464250) --> (http://bugzilla.novell.com/attachment.cgi?id=464250) artefact described I'm not sure whose fault this is. It looks like it is struck out several times. Like in the picture. It happens sometimes. Now I pressed ctrl+f to open a find box, then I closed it and this artefact appeared. It started happening after I moved from gnome2 to kde4. I.e. when I started using desktop effect. NOt sure if that's related. It happens both on my desktop (intel G33) and notebook (radeon x1450). The former is factory, the latter 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 2

[Bug 723614] New: ristretto image viewer crasches when rotating images
by bugzilla_noreply＠novell.com 28 Feb '12

28 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=723614 https://bugzilla.novell.com/show_bug.cgi?id=723614#c0 Summary: ristretto image viewer crasches when rotating images Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce(a)forge.provo.novell.com ReportedBy: jw(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- open a jpeg in ristretto press clockwise or counterclockwise rotation icons several times. Risotto disappears, and its stderr has this message: (ristretto:4169): GdkPixbuf-CRITICAL **: gdk_pixbuf_new_subpixbuf: assertion `src_x >= 0 && src_x + width <= src_pixbuf->width' failed Segmentation fault (core dumped) (gdb) where #0 0xb7054c98 in gdk_pixbuf_rotate_simple () from /usr/lib/libgdk_pixbuf-2.0.so.0 #1 0x08053978 in ?? () #2 0xb6e2bc80 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0xb6e2fddf in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #4 0xb6e30510 in ?? () from /usr/lib/libglib-2.0.so.0 #5 0xb6e30b1b in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #6 0xb73afeff in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #7 0x08050eda in ?? () #8 0xb6aa12b3 in __libc_start_main () from /lib/libc.so.6 #9 0x08050f59 in ?? () -- 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 718105] New: No icon is displayed by the panel plug-in "Action Buttons".
by bugzilla_noreply＠novell.com 28 Feb '12

28 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=718105 https://bugzilla.novell.com/show_bug.cgi?id=718105#c0 Summary: No icon is displayed by the panel plug-in "Action Buttons". Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce(a)forge.provo.novell.com ReportedBy: Markus.Elfring(a)web.de QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=451002) --> (http://bugzilla.novell.com/attachment.cgi?id=451002) excerpt from a screenshot The software component "XFCE panel 4.8.5-62.1" is also installed on my system. I wonder why I do not see a clear icon for the function "log out" or "exit" by the plug-in "Action Buttons". When will a corresponding icon be displayed? http://docs.xfce.org/help/xfce4-panel/C/actions.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 8

[Bug 555008] New: Horde does not work
by bugzilla_noreply＠novell.com 28 Feb '12

28 Feb '12

http://bugzilla.novell.com/show_bug.cgi?id=555008 Summary: Horde does not work Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i586 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Apache AssignedTo: bnc-team-apache(a)forge.provo.novell.com ReportedBy: alar.sing(a)err.ee QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729) There is some problem with PHP or apache when I try to use horde I get [Thu Nov 12 20:54:06 2009] [error] [client 10.10.9.1] PHP Warning: include_once(/srv/www/htdocs/client/config/nls.php): failed to open stream: Too many open files in /srv/www/htdocs/client/lib/Horde.php on line 520 [Thu Nov 12 20:54:06 2009] [error] [client 10.10.9.1] PHP Warning: include_once(): Failed opening '/srv/www/htdocs/client/config/nls.php' for inclusion (include_path='/srv/www/htdocs/client/lib:/srv/www/htdocs/client/lib/../pear:.:/usr/share/php5:/usr/share/php5/PEAR') in /srv/www/htdocs/client/lib/Horde.php on line 520 [Thu Nov 12 20:54:06 2009] [error] [client 10.10.9.1] PHP Warning: require(/srv/www/htdocs/client/config/registry.php): failed to open stream: Too many open files in /srv/www/htdocs/client/lib/Horde/Registry.php on line 212 [Thu Nov 12 20:54:06 2009] [error] [client 10.10.9.1] PHP Fatal error: require(): Failed opening required '/srv/www/htdocs/client/config/registry.php' (include_path='/srv/www/htdocs/client/lib:/srv/www/htdocs/client/lib/../pear:.:/usr/share/php5:/usr/share/php5/PEAR') in /srv/www/htdocs/client/lib/Horde/Registry.php on line 212 errors in my apache error log file 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

[Bug 714535] New: add patch for modern drag-to-tile support to xfwm4
by bugzilla_noreply＠novell.com 28 Feb '12

28 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=714535 https://bugzilla.novell.com/show_bug.cgi?id=714535#c0 Summary: add patch for modern drag-to-tile support to xfwm4 Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Enhancement Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce(a)forge.provo.novell.com ReportedBy: nick.steeves(a)shaw.ca QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.215 Safari/535.1 Drag-to-tile window management seems to have become a standard feature. (MacOS, Windows 7, KDE4, GNOME3) and will be part XFCE 4.10. If this patch proves itself to be stable, it would enhance the openSUSE desktop experience, by providing greater consistency between environments. There is a patch that adds drag-to-tile support to XFWM4 (4.8) here: https://bugzilla.xfce.org/attachment.cgi?id=3238&action=edit It's from this XFCE bug report: https://bugzilla.xfce.org/show_bug.cgi?id=6648 Could we test it for incorporation into openSUSE 12.1? I'd put a modified xfwm4 into OBS myself, but I'm too new to openSUSE to do so. A similar patch is currently being tested in archlinux's community repository Reproducible: Always Steps to Reproduce: 1. Install openSUSE 2. Missing feature Actual Results: Drag-to-tile is not supported. Expected Results: Drag-to-tile is supported. -- 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 5

[Bug 688084] New: Error message when cancelling YaST dialogs
by bugzilla_noreply＠novell.com 28 Feb '12

28 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=688084 https://bugzilla.novell.com/show_bug.cgi?id=688084#c0 Summary: Error message when cancelling YaST dialogs Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Minor Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce(a)forge.provo.novell.com ReportedBy: muczyjoe(a)gmail.com 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 Cancelling YaST dialogs produces the following xmessage window: "GTK GUI wanted but not found, falling back to Qt". Forum: http://forums.opensuse.org/english/get-technical-help-here/applications/455… 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 4

[Bug 710380] New: Xen: vm-install failed to start
by bugzilla_noreply＠novell.com 28 Feb '12

28 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=710380 https://bugzilla.novell.com/show_bug.cgi?id=710380#c0 Summary: Xen: vm-install failed to start Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)novell.com ReportedBy: a(a)skwar.me QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=444182) --> (http://bugzilla.novell.com/attachment.cgi?id=444182) rpm -qa -- complete package list User-Agent: Mozilla/5.0 (X11; Linux i686 (x86_64)) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/15.0.839.0 Safari/535.1 SUSE/15.0.839.0 I installed openSUSE 11.4 KDE x86_64 and later on enabled Xen by clicking on "Hypervisor und Hilfsprogramme installieren" (Install hypervisor and helper programs). I selected Xen (and also had the choice to select kvm). I rebooted into the Xen kernel, and when i now try to run vm-install as root, I get: ask@ewzw032:~> sudo env LC_ALL=C vm-install Error: None "xen-kernel" is installed. Installed packages which might be of interest: ask@ewzw032:~> rpm -qa | grep -E 'virt|xen|kernel' | sort ; rpm -q yast2-vm kernel-default-devel-2.6.37.6-0.7.1.x86_64 kernel-desktop-2.6.37.6-0.7.1.x86_64 kernel-desktop-devel-2.6.37.6-0.7.1.x86_64 kernel-devel-2.6.37.6-0.7.1.noarch kernel-source-2.6.37.6-0.7.1.noarch kernel-syms-2.6.37.6-0.7.1.x86_64 kernel-xen-2.6.37.6-0.7.1.x86_64 kernel-xen-devel-2.6.37.6-0.7.1.x86_64 libvirt-0.8.8-0.10.1.x86_64 libvirt-client-0.8.8-0.10.1.x86_64 libvirt-python-0.8.8-0.10.1.x86_64 patterns-openSUSE-devel_kernel-11.4-6.9.1.x86_64 soprano-backend-virtuoso-2.5.63-5.1.x86_64 virt-manager-0.8.5-8.1.x86_64 virtuoso-drivers-6.1.2-4.3.x86_64 virtuoso-server-6.1.2-4.3.x86_64 virt-utils-1.1.5-1.2.1.x86_64 virt-viewer-0.2.1-5.2.x86_64 xen-4.0.2_02-4.9.2.x86_64 xen-libs-4.0.2_02-4.9.2.x86_64 xen-tools-4.0.2_02-4.9.2.x86_64 yast2-vm-2.17.1-3.1.x86_64 Reproducible: Always Steps to Reproduce: See above Actual Results: nothing, vm-install didn't start - or better, it started, but failed because of this error message. Expected Results: vm-install should work. Did a little bit of debbugging by adding debug print statements to /usr/bin/vm-install. I found, that it errors out at line 243: defaults.connect = vminstall.options.calculate(options, defaults) -- 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 693640] New: Proxy settings are not enterd accordingly into the system configuration
by bugzilla_noreply＠novell.com 28 Feb '12

28 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=693640 https://bugzilla.novell.com/show_bug.cgi?id=693640#c0 Summary: Proxy settings are not enterd accordingly into the system configuration 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 x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 I installed 11.4 from a recent netiso. At the boot screen I entered the PROXY settings and started installation - everything seemed to run smoothly during the night, nobody observed the machine working after I started the installation. The next day there were no proxy settings in /etc/sysconfig/proxy, though the machine definitively had had them configured - otherwise installation would not have worked. So I entered them by hand. However, kde too did not take notice of /etc/sysconfig/proxy, I had to respecify the proxy in the "Systemeinstellung" dialogue in order to make things work. This is a x86_64 - machine. Thank you for looking into, take care Dieter Jurzitza Reproducible: Always Actual Results: Proxy settings have not been included into /etc/sysconfig/proxy Expected Results: Should have been entered into there I cannot test by restarting the installation. I need this machine running :-) -- 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 731395] New: amarok in OpenSUSE 12.1 segfaults when opening cover manager
by bugzilla_noreply＠novell.com 27 Feb '12

27 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=731395 https://bugzilla.novell.com/show_bug.cgi?id=731395#c0 Summary: amarok in OpenSUSE 12.1 segfaults when opening cover manager Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: chris.brown(a)sybase.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Amarok as shipped with openSUSE 12.1 crashes when opening the 'cover manager'. This is after re-scanning my music collection (to populate amarok with my music files) .. then when I go to tools --> open cover manager, amarok segfaults. Backtrace: Application: Amarok (amarok), signal: Segmentation fault [Current thread is 1 (Thread 0x7fade02c0760 (LWP 15338))] Thread 11 (Thread 0x7fadc197f700 (LWP 15342)): #0 0x00007faddcc1e423 in poll () from /lib64/libc.so.6 #1 0x00007fadd455c20f in ?? () from /usr/lib64/libpulse.so.0 #2 0x00007fadd454d61c in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #3 0x00007fadd454dc89 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x00007fadd454dd40 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x00007fadd455c1bf in ?? () from /usr/lib64/libpulse.so.0 #6 0x00007fadcfdbd248 in ?? () from /usr/lib64/libpulsecommon-1.1.so #7 0x00007faddad89f05 in start_thread () from /lib64/libpthread.so.0 #8 0x00007faddcc2753d in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7fadb6ed0700 (LWP 15345)): #0 0x00007faddad8d11f in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0 #1 0x00007fadd68ecb43 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fadd68ecf59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fadde229576 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #4 0x00007fadde1fda22 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #5 0x00007fadde1fdc1f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #6 0x00007fadde1155df in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x00007fadde1e0aef in ?? () from /usr/lib64/libQtCore.so.4 #8 0x00007fadde118025 in ?? () from /usr/lib64/libQtCore.so.4 #9 0x00007faddad89f05 in start_thread () from /lib64/libpthread.so.0 #10 0x00007faddcc2753d in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fadb4ba4700 (LWP 15346)): #0 0x00007fff9b7ff93c in ?? () #1 0x00007fadd6ba0e91 in clock_gettime () from /lib64/librt.so.1 #2 0x00007fadde168114 in ?? () from /usr/lib64/libQtCore.so.4 #3 0x00007fadde229d1d in ?? () from /usr/lib64/libQtCore.so.4 #4 0x00007fadde22a053 in ?? () from /usr/lib64/libQtCore.so.4 #5 0x00007fadde228abc in ?? () from /usr/lib64/libQtCore.so.4 #6 0x00007fadd68ebb22 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #7 0x00007fadd68ec92d in ?? () from /usr/lib64/libglib-2.0.so.0 #8 0x00007fadd68ecf59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #9 0x00007fadde229576 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #10 0x00007fadde1fda22 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #11 0x00007fadde1fdc1f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #12 0x00007fadde1155df in QThread::exec() () from /usr/lib64/libQtCore.so.4 #13 0x00007fadde118025 in ?? () from /usr/lib64/libQtCore.so.4 #14 0x00007faddad89f05 in start_thread () from /lib64/libpthread.so.0 #15 0x00007faddcc2753d in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7fadb3d29700 (LWP 15347)): #0 0x00007faddad8e1eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fadde11842e in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x00007fadde10ce9f in ?? () from /usr/lib64/libQtCore.so.4 #3 0x00007fadde118025 in ?? () from /usr/lib64/libQtCore.so.4 #4 0x00007faddad89f05 in start_thread () from /lib64/libpthread.so.0 #5 0x00007faddcc2753d in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7fadb3528700 (LWP 15349)): #0 0x00007faddad8de6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fadde1184bb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x00007fadda175104 in ?? () from /usr/lib64/libthreadweaver.so.4 #3 0x00007fadda1776ab in ?? () from /usr/lib64/libthreadweaver.so.4 #4 0x00007fadda1776c4 in ?? () from /usr/lib64/libthreadweaver.so.4 #5 0x00007fadda17656f in ?? () from /usr/lib64/libthreadweaver.so.4 #6 0x00007fadda1765fb in ThreadWeaver::Thread::run() () from /usr/lib64/libthreadweaver.so.4 #7 0x00007fadde118025 in ?? () from /usr/lib64/libQtCore.so.4 #8 0x00007faddad89f05 in start_thread () from /lib64/libpthread.so.0 #9 0x00007faddcc2753d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fadb21e0700 (LWP 15350)): #0 0x00007faddad8de6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fadde1184bb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x00007fadda175104 in ?? () from /usr/lib64/libthreadweaver.so.4 #3 0x00007fadda1776ab in ?? () from /usr/lib64/libthreadweaver.so.4 #4 0x00007fadda1776c4 in ?? () from /usr/lib64/libthreadweaver.so.4 #5 0x00007fadda1776c4 in ?? () from /usr/lib64/libthreadweaver.so.4 #6 0x00007fadda17656f in ?? () from /usr/lib64/libthreadweaver.so.4 #7 0x00007fadda1765fb in ThreadWeaver::Thread::run() () from /usr/lib64/libthreadweaver.so.4 #8 0x00007fadde118025 in ?? () from /usr/lib64/libQtCore.so.4 #9 0x00007faddad89f05 in start_thread () from /lib64/libpthread.so.0 #10 0x00007faddcc2753d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fadb17d4700 (LWP 15351)): #0 0x00007faddad8de6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fadde1184bb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x00007fadda175104 in ?? () from /usr/lib64/libthreadweaver.so.4 #3 0x00007fadda1776ab in ?? () from /usr/lib64/libthreadweaver.so.4 #4 0x00007fadda17656f in ?? () from /usr/lib64/libthreadweaver.so.4 #5 0x00007fadda1765fb in ThreadWeaver::Thread::run() () from /usr/lib64/libthreadweaver.so.4 #6 0x00007fadde118025 in ?? () from /usr/lib64/libQtCore.so.4 #7 0x00007faddad89f05 in start_thread () from /lib64/libpthread.so.0 #8 0x00007faddcc2753d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fadb0fd3700 (LWP 15352)): #0 0x00007faddad8de6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fadde1184bb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x00007fadda175104 in ?? () from /usr/lib64/libthreadweaver.so.4 #3 0x00007fadda1776ab in ?? () from /usr/lib64/libthreadweaver.so.4 #4 0x00007fadda1776c4 in ?? () from /usr/lib64/libthreadweaver.so.4 #5 0x00007fadda1776c4 in ?? () from /usr/lib64/libthreadweaver.so.4 #6 0x00007fadda17656f in ?? () from /usr/lib64/libthreadweaver.so.4 #7 0x00007fadda1765fb in ThreadWeaver::Thread::run() () from /usr/lib64/libthreadweaver.so.4 #8 0x00007fadde118025 in ?? () from /usr/lib64/libQtCore.so.4 #9 0x00007faddad89f05 in start_thread () from /lib64/libpthread.so.0 #10 0x00007faddcc2753d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fadb0190700 (LWP 15353)): #0 0x00007faddad8de6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fadd372c9dc in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x00007fadd372cb09 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x00007faddad89f05 in start_thread () from /lib64/libpthread.so.0 #4 0x00007faddcc2753d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fadaee79700 (LWP 15356)): #0 0x00007faddad8de6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fadd9197852 in ?? () from /usr/lib64/libQtScript.so.4 #2 0x00007fadd9197889 in ?? () from /usr/lib64/libQtScript.so.4 #3 0x00007faddad89f05 in start_thread () from /lib64/libpthread.so.0 #4 0x00007faddcc2753d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fade02c0760 (LWP 15338)): [KCrash Handler] #6 0x00007fadd80ccfee in TagLib::ByteVector::ByteVector(TagLib::ByteVector const&) () from /usr/lib64/libtag.so.1 #7 0x00007fadd80e06e0 in TagLib::MP4::CoverArt::data() const () from /usr/lib64/libtag.so.1 #8 0x00007faddf12c3ab in Meta::Tag::MP4TagHelper::embeddedCover() const () from /usr/lib64/libamaroklib.so.1 #9 0x00007faddf0dfb83 in Meta::Tag::embeddedCover(QString const&) () from /usr/lib64/libamaroklib.so.1 #10 0x00007fadbd52fe73 in ?? () from /usr/lib64/libamarok-sqlcollection.so.1 #11 0x00007faddf31eaaa in ?? () from /usr/lib64/libamaroklib.so.1 #12 0x00007faddf31f3c5 in ?? () from /usr/lib64/libamaroklib.so.1 #13 0x00007faddf322af5 in ?? () from /usr/lib64/libamaroklib.so.1 #14 0x00007faddf32588e in ?? () from /usr/lib64/libamaroklib.so.1 #15 0x00007fadde21159a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #16 0x00007fadbd515734 in ?? () from /usr/lib64/libamarok-sqlcollection.so.1 #17 0x00007fadde21159a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #18 0x00007fadda176a52 in ThreadWeaver::Job::done(ThreadWeaver::Job*) () from /usr/lib64/libthreadweaver.so.4 #19 0x00007fadda176b3c in ThreadWeaver::Job::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libthreadweaver.so.4 #20 0x00007fadde21514a in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #21 0x00007faddd5cdbe4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #22 0x00007faddd5d2a71 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #23 0x00007faddfcb8e36 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #24 0x00007fadde1fe81c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #25 0x00007fadde201bf8 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #26 0x00007fadde2290b3 in ?? () from /usr/lib64/libQtCore.so.4 #27 0x00007fadd68ec58d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x00007fadd68ecd88 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x00007fadd68ecf59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x00007fadde22950f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #31 0x00007faddd670f2e in ?? () from /usr/lib64/libQtGui.so.4 #32 0x00007fadde1fda22 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #33 0x00007fadde1fdc1f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #34 0x00007fadde201de7 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #35 0x00000000004093ce in ?? () #36 0x00007faddcb6f23d in __libc_start_main () from /lib64/libc.so.6 #37 0x000000000040bf9d in _start () Reproducible: Always Steps to Reproduce: 1. Import / re-scan music collection 2. Go to tools --> Cover manager 3. Watch Amarok crash Expected Results: shouldn't crash -- 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 679949] New: unable to unmount a cisf share as user in opensuse 11.4
by bugzilla_noreply＠novell.com 27 Feb '12

27 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=679949 https://bugzilla.novell.com/show_bug.cgi?id=679949#c0 Summary: unable to unmount a cisf share as user in opensuse 11.4 Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: fire.suse(a)gmail.com QAContact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 Mount a share as user is possible with UID=set from mount.cifs and a entry in fstab. Unmount as user is not possible. Message: umount: /home/fire/Server/public mount disagrees with the fstab As "root" the share can be unmounted. I suspect the symlink /etc/mtab to be the problem. If it is replaced by a "real" file unmounting as user will work like it used to do. Reproducible: Always Steps to Reproduce: 1.connect to share as normal user with "mount /home/fire/Server/public" 2.disconnect share as normal user with "umount /home/fire/Server/public" Actual Results: umount error: umount: /home/fire/Server/public mount disagrees with the fstab Expected Results: correct unmount See additional info on: http://forums.opensuse.org/english/get-technical-help-here/network-internet… -- 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 656589] New: YaST2 nukes APACHE_SERVER_FLAGS
by bugzilla_noreply＠novell.com 27 Feb '12

27 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=656589 https://bugzilla.novell.com/show_bug.cgi?id=656589#c0 Summary: YaST2 nukes APACHE_SERVER_FLAGS Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i686 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; pl-PL; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Ant.com Toolbar 2.0.1 Firefox/3.6.12 Steps to reproduce: 1. Tell Yast2 to configure WWW to use SSL. 2. Tell Yast2 to set APACHE_SERVER_FLAGS in sysconfig:WWW to SSL TRAC_WSGI. 3. Tell Yast2 to configure WWW. Yast2 will notify you about unsupported configuration changes. 4. Tell Yast2 to exit saving changes. 5. Tell Yast2 to examine APACHE_SERVER_FLAGS in sysconfig. Observe how the value is back to SSL. As a result, whatever you tell Yast2 to do to WWW, you have to fix sysconfig thereafter. Not funny. Reproducible: Always Steps to Reproduce: 1. Tell Yast2 to configure WWW to use SSL. 2. Tell Yast2 to set APACHE_SERVER_FLAGS in sysconfig:WWW to SSL TRAC_WSGI. 3. Tell Yast2 to configure WWW. 4. Tell Yast2 to exit saving changes. 5. Tell Yast2 to examine APACHE_SERVER_FLAGS in sysconfig. Actual Results: 3. Yast2 will notify you about unsupported configuration changes. 5. Observe how the value is set back to SSL. Expected Results: 5. SSL TRAC_WSGI This bug was first reported at Forum: Network/Internet <URL: http://forums.opensuse.org/english/get-help-here/network-internet/450342-ya… > -- 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 702220] New: KDE leave Reboot Fails Leaving Dim Screen & Useless Desktop
by bugzilla_noreply＠novell.com 26 Feb '12

26 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=702220 https://bugzilla.novell.com/show_bug.cgi?id=702220#c0 Summary: KDE leave Reboot Fails Leaving Dim Screen & Useless Desktop Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: rob.opensuse.linux(a)googlemail.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 Logged in 12.1 M2 was impressed. After many hours using new install, tried to leave KDE & reboot system. Screen dimmed, but no countdown appeared & nothing happened, nor could I use KDE to fix, had to type into root console "exec init 3". In log file found : Jun 26 14:35:01 fir kcheckpass[5314]: Authentication failure for ladm (invoked by uid 1000) Jun 26 14:35:25 fir su: (to root) ladm on /dev/pts/0 Jun 26 14:35:25 fir su: pam_apparmor(su-l:session): Unknown error occurred changing to root hat: Operation not permitted Jun 26 14:35:40 fir kdm[30026]: Cannot execute 'grub-set-default': not in $PATH. Jun 26 14:35:44 fir pulseaudio[32079]: ratelimit.c: 249 events suppressed Reproducible: Didn't try Actual Results: Dim screen without KDE window management Expected Results: Normally it dims creen with pop up counting down to reboot to give opportunity to cancel, or reboot immediately. -- 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 625773] New: Evolution-tracker Fails to Index Email
by bugzilla_noreply＠novell.com 24 Feb '12

24 Feb '12

http://bugzilla.novell.com/show_bug.cgi?id=625773 http://bugzilla.novell.com/show_bug.cgi?id=625773#c0 Summary: Evolution-tracker Fails to Index Email Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: delder(a)novacoast.com QAContact: lakhil(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 I have the evolution tracker plugin installed and enabled but it doesn't seem to ever index any email. I can see a number of errors in the tracker logs such as: 26 Jul 2010, 16:47:56: Tracker: ---> [778551|evolution] Failed, 1.12: syntax error, expected variable or term 26 Jul 2010, 16:47:56: Tracker: ---> [778552|evolution] Failed, 1.12: syntax error, expected variable or term 26 Jul 2010, 16:47:56: Tracker: ---> [778553|evolution] Failed, 1.12: syntax error, expected variable or term 26 Jul 2010, 16:47:56: Tracker: ---> [778554|evolution] Failed, 1.12: syntax error, expected variable or term 26 Jul 2010, 16:47:56: Tracker: ---> [778555|evolution] Failed, 1.12: syntax error, expected variable or term 26 Jul 2010, 16:47:56: Tracker: ---> [778556|evolution] Failed, 1.12: syntax error, expected variable or term 26 Jul 2010, 16:47:56: Tracker: ---> [778557|evolution] Failed, 1.12: syntax error, expected variable or term 26 Jul 2010, 16:47:56: Tracker: ---> [778558|evolution] Failed, 1.12: syntax error, expected variable or term 26 Jul 2010, 16:47:56: Tracker: ---> [778559|evolution] Failed, 1.12: syntax error, expected variable or term 26 Jul 2010, 16:47:56: Tracker: ---> [778560|evolution] Failed, 1.12: syntax error, expected variable or term 26 Jul 2010, 16:48:09: Tracker: ---> [780928|evolution] Failed, 1.12: syntax error, expected variable or term I have an imapx account, an imap account, and a Groupwise account, and none of them seem to work. Tracker-status always just shows: Store: ✓ Journal replay - Idle Miners: ✓ Applications - Idle ✓ File System - Idle ✓ Emails - Initializing I have the following installed: nautilus-tracker-0.8.5-2.7.x86_64 libtracker-client-0_8-0-0.8.5-2.7.x86_64 libtracker-extract-0_8-0-0.8.5-2.7.x86_64 evolution-tracker-0.8.5-2.7.x86_64 tracker-gui-0.8.5-2.7.x86_64 tracker-0.8.5-2.7.x86_64 libtracker-miner-0_8-0-0.8.5-2.7.x86_64 Indexing of files on the filesystem appear to work fine but never evolution data or email. I found someone else with the same problem under Debian (http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg776135.html) but no solution that I could find. Any suggestions on what to try would be greatly appreciated :) 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 10

[Bug 687548] New: smbd forks too early
by bugzilla_noreply＠novell.com 24 Feb '12

24 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=687548 https://bugzilla.novell.com/show_bug.cgi?id=687548#c0 Summary: smbd forks too early Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: lnussel(a)novell.com QAContact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- for some reason smbd fails to start on my system ("can not open secrets.tdb"). The init script however reports success nevertheless => smbd forks before it's fully initialized. smbd should fork later if possible so init scripts can do proper status reporting. -- 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 5

[Bug 686199] New: Logout cancelled by VLC
by bugzilla_noreply＠novell.com 24 Feb '12

24 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=686199 https://bugzilla.novell.com/show_bug.cgi?id=686199#c0 Summary: Logout cancelled by VLC 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: markcscott2003(a)hotmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0 Hi, VLC aborts shutdown/logoff even when idle, i.e not playing any media. As long as VLC is running it will abort shutdown/logoff every time. Reproducible: Always Steps to Reproduce: 1.Just open VLC 2.Try to log out 3. Actual Results: KDE Workspace notifies "Logout cancelled by VLC" Expected Results: KDE Workspace to shutdown without cancellation Please see thread in forums on this issue: http://forums.opensuse.org/english/get-technical-help-here/applications/457… This is using the current version of VLC from the Packman repo 1.18 and KDE 4.6.2 from /KDE:/Distro:/Factory/openSUSE_11.4/ This already has an open ticket from an ArchLinux user at the VLC bug tracker: http://trac.videolan.org/vlc/ticket/4606 -- 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 680193] New: Screen 'freezes' every 10 seconds or so: stock 'nouveau' driver crashes, proprietary NVIDIA driver resolves issue.
by bugzilla_noreply＠novell.com 24 Feb '12

24 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=680193 https://bugzilla.novell.com/show_bug.cgi?id=680193#c0 Summary: Screen 'freezes' every 10 seconds or so: stock 'nouveau' driver crashes, proprietary NVIDIA driver resolves issue. Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: pbutler(a)magma.ca QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 Original problem description: ------------------------------------------------------------------------------ With a fresh OpenSUSE 11.4 x86-64 installation on a system with an nVidia GT216 [GeForce GT 220] video card, every 10 or 15 seconds the system 'freezes' for a half second or so. That is, anything that is going on (visible) freezes for half a second or so. If you're in the process of moving the mouse, the pointer will stop dead in its tracks for that half second, and then when it resumes (a half-second later) it picks up from where "it would have been" had there not been a freeze (it will jump from one position on the screen to the next, as per the actual movement of the mouse. Or if you watching scrolling output in a terminal window, the scrolling will stop for the same half-second. I did a quick monitor with 'top' refreshing every tenth of a second, and when this freezing occurs it seems to coincide with spikes in the kernel thread 'kworker'. Note that dmesg also reports this log quite frequently: [ 9140.292127] [drm] nouveau 0000:01:00.0: DDC responded, but no EDID for DVI-I-1 [ 9171.038139] [drm] nouveau 0000:01:00.0: DDC responded, but no EDID for DVI-I-1 [ 9191.641121] [drm] nouveau 0000:01:00.0: DDC responded, but no EDID for DVI-I-1 [ 9212.129120] [drm] nouveau 0000:01:00.0: DDC responded, but no EDID for DVI-I-1 [ 9232.538139] [drm] nouveau 0000:01:00.0: DDC responded, but no EDID for DVI-I-1 [ 9242.614120] [drm] nouveau 0000:01:00.0: DDC responded, but no EDID for DVI-I-1 [ 9263.138154] [drm] nouveau 0000:01:00.0: DDC responded, but no EDID for DVI-I-1 Seems to occur with the same frequency as the screen 'freezing'. In addition to this 'freezing', X/KDE would completely lock up several times a day: the mouse pointer could still be moved, but the keyboard and screen were otherwise totally unresponsive. (Had to log in via SSH to do a clean system shutdown.) This is a FAST system (3 GHz and four cores) that is otherwise running IDLE, other than having logged into KDE. So it's not a case of high CPU usage or I/O usage. ------------------------------------------------------------------------------ After having added the nVidia repository for OpenSUSE 11.4, the following packages were automatically selected for installation by YaST: libvdpau-devel libvdpau_trace1 nvidia-gfG02-kmp-desktop x11-video-nvidiaG02 Once these were installed the above problems went away entirely. See also Bugzilla 639548, 674325 and 638137. Reproducible: Always Steps to Reproduce: 1. Install OpenSUSE 11.4 x86-64 on a system with an nVidia GT216 [GeForce GT 220] video card 2. Once up and running, simply move the mouse around (or do any other 'regular' activity for that matter) and you will notice the system hiccup every 10-20 seconds for a half-second or so; you will also get the above logs in dmesg etc. Actual Results: KDE/X sporadically hung, and the system would repeatedly hiccup every 10-20 seconds or so. Expected Results: There should be no hiccupping of the system and no associated drm error logs. See also Bugzilla 639548, 674325 and 638137. -- 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 732201] New: YaST / System / Power Management does not actually set the CPU speed on restart
by bugzilla_noreply＠novell.com 24 Feb '12

24 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=732201 https://bugzilla.novell.com/show_bug.cgi?id=732201#c0 Summary: YaST / System / Power Management does not actually set the CPU speed on restart Classification: openSUSE Product: openSUSE 12.1 Version: Final 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: jmcdaniel3(a)austin.rr.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 Setting Power Management in YaST (Which must be installed as it is not there be default) and selecting Low Latency Computing does not actually result in using the Performance Governor as it did with openSUSE 11.4. You can see this blog on how to setup Power Management in YaST: http://forums.opensuse.org/blogs/jdmcdaniel3/yast-power-management-control-… You can check and change your CPU speed Governor setting using this script file here: http://forums.opensuse.org/blogs/jdmcdaniel3/c-f-u-cpu-frequency-utilitiy-v… Reproducible: Always Steps to Reproduce: 1.Setup YaST Power Management as shown here: http://forums.opensuse.org/blogs/jdmcdaniel3/yast-power-management-control-… 2. Use the Low Latency Computing Setting in Power Management. 3. Reboot your computer and check your present CPU speed with this: http://forums.opensuse.org/blogs/jdmcdaniel3/c-f-u-cpu-frequency-utilitiy-v… Actual Results: CPU speed is set to OnDemade Governor after a reboot and ignores your YaST Power Management Setting. Expected Results: After selecting Low Latency Computer and doing a reboot, I expect the CPU speed governor to be using Performance. -- 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 640391] New: executing grub in shellscript executed from withing a makefile results in a bus error
by bugzilla_noreply＠novell.com 23 Feb '12

23 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=640391 https://bugzilla.novell.com/show_bug.cgi?id=640391#c0 Summary: executing grub in shellscript executed from withing a makefile results in a bus error Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: xanclic(a)googlemail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=390382) --> (http://bugzilla.novell.com/attachment.cgi?id=390382) Shellscript which executes grub and makefile which executes the script User-Agent: Opera/9.80 (X11; Linux x86_64; U; de) Presto/2.6.30 Version/10.61 After I updated my kernel (among other updates) today, I tried to build the project I'm working on (which is an operating system). The makefile I use executes a shellscript to create a floppy disk image which in turn calls grub to install grub on that image — this worked fine until yesterday, but after today's update I get a bus error everytime I execute grub in that shellscript (except when executing “grub --help”). If I call the script directly (without makefile), it works just fine. Reproducible: Always Steps to Reproduce: 1. Unpack the attached archive anywhere. 2. The first file it contains is a script called “make_image.sh”. This will create a FAT formatted floppy disk image, copy stage1 and stage2 from /boot/grub there and run grub on it. 3. The second file is a makefile, which simply runs that script. 4. Now type “make” or “./make_image.sh” and compare. Actual Results: When using make, GRUB crashes with a bus error. When directly executing the shellscript, it doesn't and a FAT formatted floppy disk image with a well installed GRUB is the result. Expected Results: GRUB should not crash in either of both cases. As said before, I ran the YaST online update some hours ago which included a kernel update. The versions of the used programs are: kernel — 2.6.34.7-0.2 (desktop) make — 3.81 (built for x86_64-unknown-linux-gnu) bash — 4.1.7(1)-release (built for x86_64-suse-linux-gnu) grub — 0.97 mtools — 4.0.13 (note: I set the serverity to “critical”, because the software obviously crashes — imho this is just a normal bug, but the description of “critical” told me it isn't) -- 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 31

[Bug 730109] New: KolorManager does not pass ICC profile name to Oyranos
by bugzilla_noreply＠novell.com 23 Feb '12

23 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=730109 https://bugzilla.novell.com/show_bug.cgi?id=730109#c0 Summary: KolorManager does not pass ICC profile name to Oyranos Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: ku.b(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20100101 Firefox/7.0 While oyranos-monitor can set a ICC profile and is visible in the qcmsevents applet, KolorManager can not. The bug is related to expecting a const char * from QString::toLocal8Bit() instead of handling the returned QByteArray object. Reproducible: Always Steps to Reproduce: 1. open KDE > Systemsettings > Color Management > Devices > your_actual_monitor 2. select a profile from the profile list other than the active one 3. qcmsevents does not show the new profile in any of its _ICC_(xxx_)PROFILExxx events Actual Results: 3. qcmsevents does not show the new profile in its _ICC_PROFILExxx event Expected Results: 3. qcmsevents shall show the new profile in a _ICC_PROFILExxx event fix is available in KolorManager git: http://quickgit.kde.org/?p=kolor-manager.git&a=commitdiff_plain&h=f1d568e0b… NEEDINFO maintenance(a)opensuse.org -- 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 731591] New: No notification on build failure
by bugzilla_noreply＠novell.com 23 Feb '12

23 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=731591 https://bugzilla.novell.com/show_bug.cgi?id=731591#c0 Summary: No notification on build failure Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: General AssignedTo: adrian(a)suse.com ReportedBy: rschweikert(a)suse.com QAContact: adrian(a)suse.com Found By: --- Blocker: --- I realize there were some issues with Hermes recently. However, I believe my trouble is unrelated to the recent issues. I have "Build Failure Receive a notification every time a package fails to build." Turned on for e-mail and immediate delivery. Yest, I do not get any messages on build failure. For example rubygem-rack (devel:languages:ruby:extensions) changed on Aug 30 and I suspect that ever since then packages in Virtualization:Cloud:OpenNebula are broken. Yet I have not, to the best of my knowledge received an e-mail about the broken build :( -- 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 732617] New: virt-manager does not start when python-virtinst is installed
by bugzilla_noreply＠novell.com 22 Feb '12

22 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=732617 https://bugzilla.novell.com/show_bug.cgi?id=732617#c0 Summary: virt-manager does not start when python-virtinst is installed Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: carnold(a)suse.com ReportedBy: ug(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- I have python-virtinst installed, because I need it for the package koan. Now, when I start virt-manager, I get the message that my python-virtinst is too old and virt-manager can not start. After digging a bit, I found out that virt-manager seems to contain it's own python-virtinst now, instead of using our existing one. virt-manager has not set a "provides: python-virtinst" in the RPM either. -- 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 727081] New: xend domains don't work anymore since update from 12.1 beta to 12.1 RC 1
by bugzilla_noreply＠novell.com 22 Feb '12

22 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=727081 https://bugzilla.novell.com/show_bug.cgi?id=727081#c0 Summary: xend domains don't work anymore since update from 12.1 beta to 12.1 RC 1 Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: i686 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)suse.com ReportedBy: novell(a)kapsler.ch QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Had several domU's running with 12.1 beta just fine. I can start suse with the new kernel but domU's dont start anymore. xen seems to crash after startup, see logs dmesg: [ 547.025607] xend[15061]: segfault at 240506dc098 ip 00007f7af0e3d779 sp 00007fff506dbe38 error 4 in libxenguest.so.4.0.0[7f7af0e22000+25000] xend-debug.log: Xend started at Fri Oct 28 16:11:03 2011. Exception in thread UnixHttpServer: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 552, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 505, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/xen/web/httpserver.py", line 312, in run (sock, addr) = self.accept() File "/usr/lib64/python2.7/site-packages/xen/web/httpserver.py", line 331, in accept return self.socket.accept() File "/usr/lib64/python2.7/socket.py", line 202, in accept sock, addr = self._sock.accept() error: [Errno 22] Invalid argument Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/xen/xend/server/Hald.py", line 55, in shutdown os.kill(self.pid, signal.SIGINT) OSError: [Errno 3] No such process Exception in thread UnixHttpServer: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 552, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 505, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/xen/web/httpserver.py", line 312, in run (sock, addr) = self.accept() File "/usr/lib64/python2.7/site-packages/xen/web/httpserver.py", line 331, in accept return self.socket.accept() File "/usr/lib64/python2.7/socket.py", line 202, in accept sock, addr = self._sock.accept() error: [Errno 22] Invalid argument Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/xen/xend/server/Hald.py", line 55, in shutdown os.kill(self.pid, signal.SIGINT) OSError: [Errno 3] No such process Xend started at Fri Oct 28 16:13:53 2011. Exception in thread UnixHttpServer: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 552, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 505, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/xen/web/httpserver.py", line 312, in run (sock, addr) = self.accept() File "/usr/lib64/python2.7/site-packages/xen/web/httpserver.py", line 331, in accept return self.socket.accept() File "/usr/lib64/python2.7/socket.py", line 202, in accept sock, addr = self._sock.accept() error: [Errno 22] Invalid argument Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/xen/xend/server/Hald.py", line 55, in shutdown os.kill(self.pid, signal.SIGINT) OSError: [Errno 3] No such process libvirtd seems also unstable, using the virtmanager fails often, it just crashes or says, that xend is not running. Reproducible: Always Steps to Reproduce: 1. start 12.1 rc with xen-kernel 2. start a domU 3. the domU is not really booting, or something from the xen-env. is crashing -- 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 52

[Bug 707016] New: YaST terminates when viewing mount graph in expert partitioner
by bugzilla_noreply＠novell.com 22 Feb '12

22 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=707016 https://bugzilla.novell.com/show_bug.cgi?id=707016#c0 Summary: YaST terminates when viewing mount graph in expert partitioner Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: aschnell(a)novell.com QAContact: jsrain(a)novell.com Found By: Development Blocker: --- YaST terminates when viewing mount graph in expert partitioner. I was able to make a screenshot of the console that shows some pango related errors. -- 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 721658] New: zypper: fails to rerun applydeltarpm
by bugzilla_noreply＠novell.com 22 Feb '12

22 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=721658 https://bugzilla.novell.com/show_bug.cgi?id=721658#c0 Summary: zypper: fails to rerun applydeltarpm Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- Action: Interrupting the undeltification/applydeltarpm stage in zypper-1.5.3 and then issuing "resume" at the next prompt Observing: the full brpm is now downloaded Expected: apply delta.rpm again. Other info: Exiting zypper, and reissuing `zypper up` will properly process delta.rpm that is still present in /var/cache/zypp. # zypper up .. 74 packages to upgrade. Overall download size: 58.6 MiB. After the operation, 197.0 KiB will be freed. Continue? [y/n/?] (y): Do you agree with the terms of the license? [yes/no] (no): y Retrieving package flash-player-10.3.183.10-0.2.1.i586 (1/74), 7.0 MiB (22.2 MiB unpacked) Retrieving delta: /rpm/i586/flash-player-10.3.183.7_10.3.183.10-0.2.1.i586.delta.rpm, 350.0 KiB Applying delta: ./flash-player-10.3.183.7_10.3.183.10-0.2.1.i586.delta.rpm [8%]^C Applying delta: ./flash-player-10.3.183.7_10.3.183.10-0.2.1.i586.delta.rpm [error] applydeltarpm failed. Retrieving: flash-player-10.3.183.10-0.2.1.i586.rpm [error] Download (curl) error for 'http://download.opensuse.org/update/11.4/rpm/i586/flash-player-10.3.183.10-…': Error code: User abort Error message: cancelled Abort, retry, ignore? [a/r/i/?] (a): r Retrieving: flash-player-10.3.183.10-0.2.1.i586.rpm [2% (110.5 KiB/s)] -- 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 701076] New: openSUSE 11.4 doesn't shutdown normally
by bugzilla_noreply＠novell.com 22 Feb '12

22 Feb '12

https://bugzilla.novell.com/show_bug.cgi?id=701076 https://bugzilla.novell.com/show_bug.cgi?id=701076#c0 Summary: openSUSE 11.4 doesn't shutdown normally Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: map_heldar(a)mail.ru 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 openSUSE 11.4 - the system doesn't turn off normally (loads to init 0, and i need to press power off button), but in 11.3 works fine. CPU: AMD Phenom(tm) II X6 1075T Processor (6 cpu cores) (version 2.20.00) MB: MSI 870U-G55, Bios ver. 25.0 /var/log/messages: Mar 17 20:21:08 Heldar kernel: [ 15.034317] powernow-k8: Found 1 AMD Phenom(tm) II X6 1075T Processor (6 cpu cores) (version 2.20.00) Mar 17 20:21:08 Heldar kernel: [ 15.034326] powernow-k8: Core Performance Boosting: on. Mar 17 20:21:08 Heldar kernel: [ 15.034336] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found. Mar 17 20:21:08 Heldar kernel: [ 15.034337] [Firmware Bug]: powernow-k8: Try again with latest BIOS. Workaround - enable Cool'n'Quiet technology. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: System doesn't turn off normally Expected Results: System turn off normally -- 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