October 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 785356] New: gnome-boxes fails to start without tracker being installed
by bugzilla_noreply＠novell.com 16 Oct '12

16 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=785356 https://bugzilla.novell.com/show_bug.cgi?id=785356#c0 Summary: gnome-boxes fails to start without tracker being installed Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: dimstar(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- > gnome-boxes (gnome-boxes:18054): GLib-GIO-ERROR **: Settings schema 'org.freedesktop.Tracker.FTS' is not installed Trace/breakpoint trap (core dumped) => org.freedesktop.Tracker.FTS comes from the tracker package. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 769115] New: Kontact crashes when I submit new email
by bugzilla_noreply＠novell.com 16 Oct '12

16 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=769115 https://bugzilla.novell.com/show_bug.cgi?id=769115#c0 Summary: Kontact crashes when I submit new email Classification: openSUSE Product: openSUSE 12.2 Version: Beta 1 Platform: PC OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: hepet(a)seznam.cz QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120614 Firefox/13.0.1 SeaMonkey/2.10 Lightning/1.5.1 I click to new email and kontact crashed. Reproducible: Always Steps to Reproduce: 1. 2. 3. I cannot use kdepim application. -- 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 682402] New: Intermittent fail to power off on shutdown on Acer Extensa 5220
by bugzilla_noreply＠novell.com 16 Oct '12

16 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=682402 https://bugzilla.novell.com/show_bug.cgi?id=682402#c0 Summary: Intermittent fail to power off on shutdown on Acer Extensa 5220 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: richard(a)urmonas.net QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=421211) --> (http://bugzilla.novell.com/attachment.cgi?id=421211) var-log-message last entries for a shutdown with no power off User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0 Fresh install of openSUSE x86-64 KDE as the single OS on the disk, on an Acer Extensa 5220 with Celeron 550 processor. Most times the computer will shut down and power off. However sometimes randomly the system will shutdown but not power off. I first noticed this with the power management set so that the laptop will shutdown on lid close. I always close all programs / windows before shutdown. The system finishes with the screen turned off, and unresponsive, it sounds as if the hard drive shuts down (seems to make the click of drive shutting down) but power LEDs and WiFi LED remain lit. Looking at /var/log/messages the only significant difference between a "good" shutdown and a "bad" shutdown is that on a "good" shutdown there is an acpid: exiting message. There is no such message on a "bad" shutdown. Looking for a cause I have tried a wide range of shutdowns. It does not appear to be related to what programs were in use, how long the system was running, or temperature. I tried shutdown just using the close lid, and also shutdown just using the menu selection. There is no obvious pattern. I also tried a fresh install of 11.4 x86-64 with Gnome desktop, and also a fresh x86 (32 bit) KDE install. These both had the same problem. Note that this problem occurs even with the default configuration. A possibly unrelated clue is that sometimes the shutdown / power-off takes a much longer time, so a shutdown normally takes less than 15 seconds from initiating shutdown to power-off, but sometimes it takes around 45 seconds. Note: This same laptop has run several versions of Ubuntu, Debian squeeze, and Fedora 14 with no shutdown / power-off problem. Reproducible: Sometimes Steps to Reproduce: 1. Normal shutdown of system 2. Approximately 1 in 4 times the laptop will not power off 3. Actual Results: Fails to power-off approximately 1 in 4 times, Expected Results: Power-off at end of shutdown cycle. -- 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 731569] New: German man page for whatis out of date
by bugzilla_noreply＠novell.com 16 Oct '12

16 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=731569 https://bugzilla.novell.com/show_bug.cgi?id=731569#c0 Summary: German man page for whatis out of date 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: martin(a)oneiros.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 The german man page for whatis does not describe the current version of whatis. Compare this: - With LANG=C: FILES /usr/share/man/index.(bt|db|dir|pag) A traditional global index database cache. /var/cache/man/index.(bt|db|dir|pag) An FHS compliant global index database cache. /usr/share/man/.../whatis A traditional whatis text database. - With LANG=de_DE.UTF-8 DATEIEN /var/catman/.../index.(bt|db|dir|pag) Die FSSTND complianten globalen Indexdatenbanken. /usr/man/.../whatis Traditionelle whatis Datenbank. There seems to be no option to uninstall the german man pages, so either they MUST be kept up to date OR removed. Keeping out of date man pages is BAD. Reproducible: Always Steps to Reproduce: 1. 2. 3. > rpm -qf /usr/share/man/de/man1/whatis.1.gz man-2.5.2-32.2.x86_64 -- 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 783854] New: [QGIS] repo-geo: cannot import qgis.core/gui into python without setting PYTHONPATH
by bugzilla_noreply＠novell.com 16 Oct '12

16 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=783854 https://bugzilla.novell.com/show_bug.cgi?id=783854#c0 Summary: [QGIS] repo-geo: cannot import qgis.core/gui into python without setting PYTHONPATH Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: 64bit OS/Version: openSUSE 12.2 Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sault.don(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1 When trying to import qgis modules into python, it fails because PYTHONPATH is not set. Is this something that could be set by default? Reproducible: Always Steps to Reproduce: 1. python 2. import qgis.core Actual Results: Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named qgis.core Expected Results: Python should not display an error. Empty output when importing modules usually means success. A workaround is to manually set PYTHONPATH: export PYTHONPATH=/usr/share/qgis/python -- 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 658604] New: Python distutils setup does not allow user installation of Python packages
by bugzilla_noreply＠novell.com 16 Oct '12

16 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=658604 https://bugzilla.novell.com/show_bug.cgi?id=658604#c0 Summary: Python distutils setup does not allow user installation of Python packages Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: jmatejek(a)novell.com ReportedBy: speilicke(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Currently, /usr/lib64/python/distutils/distutils.cfg has the following line: [install] prefix=/usr/local While the intent to not mess up the system-wide site-packages dir, it effectively disables user-installation of Python packages as one needs root-access to install files there. But it is common to supply the parameter '--user' to either easy_install or pip in order to use the local site-packages ($HOME/.local/lib/python...) instead of the system wide. However, this does not work if a prefix is hard-coded. Only easy_install allows to override by providing a custom '--prefix' option. The following request was one approach (revoked): https://build.opensuse.org/request/diff/54916 On the other hand we could also do this (in distutils.cfg): [install] user=1 Which makes user-installation the default. This could actually work because root would always want to install packages instead of /usr/local junk. Users would also prefer packages but rather have sth. in their $HOME than having to bug root for /usr/local. -- 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 723402] New: Emulators/wine: Bug
by bugzilla_noreply＠novell.com 16 Oct '12

16 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=723402 https://bugzilla.novell.com/show_bug.cgi?id=723402#c0 Summary: Emulators/wine: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: meissner(a)suse.com ReportedBy: rob.verduijn(a)gmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- the rpm installation of the wine-32bit-1.3.30-1.1.i586.rpm package always fails with the following error: error: unpacking of archive failed on file /usr/lib/wine/fakedlls/wlanapi.dll;4e949035: cpio: link failed - Too many links this also happened with wine-32bit-1.3.29-1.1.i586.rpm all other rpms install properly this is the only one that fails, this started with the release of wine 1.3.29, before that the installation of wine-32bit-1.3.27-1.1.i586.rpm worked as it should. Regards Rob -- 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 751716] New: Wine 1.4 for openSUSE 12.1?
by bugzilla_noreply＠novell.com 16 Oct '12

16 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=751716 https://bugzilla.novell.com/show_bug.cgi?id=751716#c0 Summary: Wine 1.4 for openSUSE 12.1? Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEEDINFO Severity: Normal Priority: P5 - None Component: Maintenance AssignedTo: meissner(a)suse.com ReportedBy: meissner(a)suse.com QAContact: qa(a)suse.de InfoProvider: maintenance(a)opensuse.org Found By: --- Blocker: --- As Wine 1.4 was released now, I could bring the 1.3.30 development version to 1.4 release level. ok? -- 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 538961] Creating Sequence Numbers in Release Notes Automatically
by bugzilla_noreply＠novell.com 16 Oct '12

16 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=538961 https://bugzilla.novell.com/show_bug.cgi?id=538961#c2 Karl Eichwalder <ke(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #2 from Karl Eichwalder <ke(a)suse.com> 2012-10-16 17:20:07 CEST --- Switch to default DocBook style sheets was done for 12.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 0

[Bug 656127] New: KDE Screensaver will not activate if the mouse pointer is left on the open kde slab
by bugzilla_noreply＠novell.com 16 Oct '12

16 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=656127 https://bugzilla.novell.com/show_bug.cgi?id=656127#c0 Summary: KDE Screensaver will not activate if the mouse pointer is left on the open kde slab Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Keywords: DSLA_REQUIRED, DSLA_SOLUTION_PROVIDED Severity: Enhancement Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: ke(a)novell.com QAContact: ke(a)novell.com CC: fs(a)novell.com Depends on: 638305 Found By: Documentation Blocker: --- +++ This bug was initially created as a clone of Bug #638305 +++ Customer uses screensaver as a security feature by locking the desktop after x number of minutes. The customer has found that if the KDE slab is opened and the mouse pointer is situated on the slab such that is stays open (ie I found that leaving the mouse any where on the slab will cause it to stay open) the screensaver will not activate. I ran xscreensaver from the command line and left the mouse pointer on the slab so that it would not close. The screen saver never activates and the following message appears in the terminal xscreensaver: couldn't grab keyboard! (AlreadyGrabbed) xscreensaver: couldn't grab pointer! (AlreadyGrabbed) xscreensaver: unable to grab the keyboard or mouse! blanking aborted. In more testing I have found that the mouse does not have to remain on the slab for the screen saver to load. Simply opening the slab and having it stay open causes the screen saver to not activate. =============================================================================== (In reply to comment #32) > I am afraid this is the only option we have, based on the technical > analyses I have seen. > > This is, of course, extremely unsatisfactory from a customer point > of view and needs to be presented as an inherent design problem that > is not specific to SUSE Linux Enterprise but shared across all Linux > and in fact Unix distributions (using X11). Everywhere we mention screen-savers and screen-locking in our docs, we must a strong warning. (This must happen in upstream docs (KDE, Gnome, XFCE, LXDE, etc.), too--if not already 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 3