February 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 471024] New: google gadgets caused plasma to crash
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=471024 Summary: google gadgets caused plasma to crash Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: koucou_2005(a)yahoo.fr QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-2.5 Firefox/3.0.5 The application Plasma Workspace (plasma) crashed and caused the signal 11 (SIGSEGV). http://pastebin.be/16384 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 2

[Bug 469179] New: personal settings /configure Desktop causes plasma to crash '' The application Plasma Workspace (plasma) crashed and caused the signal 11 (SIGSEGV)''
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=469179 Summary: personal settings /configure Desktop causes plasma to crash '' The application Plasma Workspace (plasma) crashed and caused the signal 11 (SIGSEGV)'' Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: koucou_2005(a)yahoo.fr QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-2.5 Firefox/3.0.5 as soon as i clik on personal settings/konfigure Desktop, plasma crashes http://pastebin.be/16267 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 2

[Bug 444438] New: Yast test sound does not play with pulseaudio
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=444438 Summary: Yast test sound does not play with pulseaudio Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: rodrigo(a)novell.com ReportedBy: jpr(a)novell.com QAContact: qa(a)suse.de Found By: --- Yast test sound does not play with pulseaudio -- 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 470850] New: Cannot install projectM for Amarok
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=470850 Summary: Cannot install projectM for Amarok Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE3 AssignedTo: kde-maintainers(a)suse.de ReportedBy: marc(a)marcchamberlin.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-0.1 Firefox/3.0.5 Well I beat my head out trying to figure out how to install projectM so guess it is time to let someone else take a crack at it. This also applies to openSuSE11.0 as well.... It use to be the case that a package for projectM was supplied for SuSE in a repository such as - http://software.opensuse.org/download/home:/wstephenson/openSUSE_10.2 but none of the parallel repositories for openSUSE_11.x contain this package making it much harder to install projectM. I visited the website for Amarok at http://amarok.kde.org/wiki/ProjectM_HowTo but the info there is apparently out of date. So I went straight to the source for projectM at http://sourceforge.net/projects/projectm/ and downloaded the two tarballs for libprojectM and projectM-libvisual. Next I successfully compiled and installed libprojectM with the following procedures - untar the package for libprojectM enter the libprojectM directory, run 'cmake .', then 'sudo make install' Then I tried to compile and install projectM-libvisual by doing the following - untar the package for projectM-libvisual enter the projectM=libvisual directory, run 'cmake . -DCMAKE_BUILD_TYPE=RELEASE' as described in the install document and I got the following error message - -- [projectM-libvisual] projectM detected. CMake Error at CMakeLists.txt:30 (MESSAGE): libvisual 0.4 not found! Please visit http://libvisual.sf.net and download the module. I checked in YaST to see if the libvisual.0.4 package was installed on my system, and indeed there are 4 packages with libvisual as part of their names - amarok-libvisual libvisual libvisual-devel libvisual-plugins and I made sure all of them were installed. I checked the version numbers of the libvisual package which is 0.4.0-174.16-i586 which seems to be right??? I also looked in /usr/include to see if there was a directory for libvisual include files and indeed there is - /usr/include/libvisual-0.4/libvisual/ which has a number of .h files NO JOY! So I dunno how to proceed, (I am NOT a guru on all this so please bear with me!) I sure have tried to follow all the instructions as well as I could. I do NOT know where to properly report this problem but figure someone in the SuSE camp probably will have a better idea on how to get this solved. (I have tried several user groups and gotten this far but seem to be running into a wall of silence now, so suspect other users don't know either.) Sure hope this will get fixed soon, my wife and I really miss projectM visuals and I really need to keep the wife acceptance factor as high as possible!!! Thanks for any and all help in advance getting this solved! Marc... Reproducible: Always Steps to Reproduce: 1.See above 2. 3. Actual Results: See above Expected Results: Be really wonderful if projectM was once again supplied as a package to be simply installed via Yast2! -- 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 386864] New: For an even better menu Kickoff
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=386864 Summary: For an even better menu Kickoff Product: openSUSE 11.0 Version: Beta 2 Platform: i686 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: jpmartinlinux(a)free.fr QAContact: qa(a)suse.de Found By: Beta-Customer -- The search icon is not beautiful, -- It lacks the version number opensuse (11) -- For the "computer", it would be nice to have more information: http://www.kde-look.org/content/show.php/Kickoff with + + + + more information? Content = 71561 -- It would be nice to have some options that appear (configuration, suppression, ...) as for desktop icons of kde4 (See also: http://www.kde-look.org/content/show.php/Kickoff with + + + + more information? Content = 71561) Thanks for all JP Martin -- 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 471318] New: Edit User Data => 500 Internal Server Error
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=471318 Summary: Edit User Data => 500 Internal Server Error Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: vuntz(a)novell.com QAContact: adrian(a)novell.com Found By: --- Go on https://build.opensuse.org/user/edit I get "500 Internal Server Error" So I can't put my real name. -- 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 470156] New: Konqueror 4.2 crashes in Google Groups when JavaScript debugger is enabled
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=470156 Summary: Konqueror 4.2 crashes in Google Groups when JavaScript debugger is enabled Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: adrian.ioan.cozma(a)gmail.com QAContact: qa(a)suse.de Found By: --- Created an attachment (id=268250) --> (https://bugzilla.novell.com/attachment.cgi?id=268250) Backtrace (appearing to be of no use) User-Agent: Mozilla/5.0 (compatible; Konqueror/4.2; Linux 2.6.27.7-9-default; X11; x86_64; en-US, en) KHTML/4.2.0 (like Gecko) SUSE Konqueror 4.2.0-82.2 (and also the previous 4.2 release) with JavaScript debugger enabled crashes when viewing threads in Google Groups. If the JavaScript debugger is disabled, it works. Reproducible: Always Steps to Reproduce: 1. Enable the Javascript debugger in Konqueror's configuration dialog 2. Go to groups.google.com 3. Choose a group (e.g. comp.lang.python) 4. Enter a thread Actual Results: Konqueror crashes and causes signal 11 (SIGSEGV) Expected Results: Not to 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 2

[Bug 470195] New: banshee-1-1.4.1-4.4: integer out of range
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=470195 User dcb314(a)hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=470195#c61 Summary: banshee-1-1.4.1-4.4: integer out of range Classification: openSUSE Product: openSUSE 11.2 Version: unspecified Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de Found By: --- I just tried to compile the Suse Factory package banshee-1-1.4.1-4.4 with the Intel compiler and it said banshee-ripper.c(298): warning #61: integer operation result is out of range The source code is g_object_set (G_OBJECT (queue), "max-size-time", 120 * GST_SECOND, NULL); but in file /usr/include/gstreamer-0.10/gst/gstclock.h is the definition #define GST_SECOND (G_USEC_PER_SEC * G_GINT64_CONSTANT (1000)) and in /usr/include/glib-2.0/glib/gtimer.h is #define G_USEC_PER_SEC 1000000 so a number of value about 120e9 is being stored in a 32 bit value. Suggest rework code to use unsigned longs. Maybe #define G_USEC_PER_SEC 1000000UL would be enough. -- 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 469234] New: knm4 does not add passphrase to existing profiles that have an empty passphrase
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=469234 Summary: knm4 does not add passphrase to existing profiles that have an empty passphrase Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: sven.burmeister(a)gmx.net QAContact: qa(a)suse.de Found By: --- rev. 916398 One can set-up a new profile without giving a passphrase. If one tries to connect via this profile knm4 fails, not surprising. The user not given any hint on why it failed though. If one edits the profile and adds a passphrase, knm4 asks for access to kwallet, yet connecting fails again. Opening the profile shows that the passphrase is empty again. If one removes the profiel and adds it again, this time including the passphrase, it works. -- 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 469268] New: kde4-kmail (KDE4:Factory) crashes repeatedly on startup
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=469268 User cfarrell(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469268#c1 Summary: kde4-kmail (KDE4:Factory) crashes repeatedly on startup Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: cfarrell(a)novell.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5 kmail crashes immediately, on startup. Sometimes I actually see the application (i.e. the main panel) but more often than not, it crashes before any graphical output. Even if I get to see graphical output, it crashes almost immediately afterwards. cfarrell@paddy:~/> uname -a Linux paddy 2.6.27.7-9-pae #1 SMP 2008-12-04 18:10:04 +0100 i686 i686 i386 GNU/Linux cfarrell@paddy:~/> kde4-config --version Qt: 4.4.3 KDE: 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) "release 78.2" kde4-config: 1.0 cfarrell@paddy:~/Documents/Chat/Tyler> kmail --version Qt: 4.4.3 KDE: 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) "release 78.2" KMail: 1.11.0 Application: KMail (kmail), signal SIGSEGV [?1034h[Thread debugging using libthread_db enabled] [Current thread is 1 (Thread 0xb3c99700 (LWP 28800))] Thread 3 (Thread 0xb09fbb90 (LWP 28951)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb6908f62 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb696884c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #3 0xb695d9c6 in ?? () from /usr/lib/libQtCore.so.4 #4 0xb696785e in ?? () from /usr/lib/libQtCore.so.4 #5 0xb69051b5 in start_thread () from /lib/libpthread.so.0 #6 0xb5d1a38e in clone () from /lib/libc.so.6 Thread 2 (Thread 0xb01fab90 (LWP 28952)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb6908f62 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb696884c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #3 0xb695d9c6 in ?? () from /usr/lib/libQtCore.so.4 #4 0xb696785e in ?? () from /usr/lib/libQtCore.so.4 #5 0xb69051b5 in start_thread () from /lib/libpthread.so.0 #6 0xb5d1a38e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb3c99700 (LWP 28800)): [KCrash Handler] #6 0xb744d9dc in KMFolderImap::slotListFolderResult (this=0x80a0048, job=0x842e6e0) at /usr/src/debug/kdepim-4.1.96/kmail/kmfolderimap.cpp:1355 #7 0xb74506ac in KMFolderImap::qt_metacall (this=0x80a0048, _c=QMetaObject::InvokeMetaMethod, _id=27, _a=0xbfe457dc) at /usr/src/debug/kdepim-4.1.96/build/kmail/kmfolderimap.moc:181 #8 0xb6a6c580 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #9 0xb6a6d302 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #10 0xb79f2c33 in KJob::result(KJob*) () from /usr/lib/libkdecore.so.5 #11 0xb79f30d9 in KJob::emitResult() () from /usr/lib/libkdecore.so.5 #12 0xb6cb0885 in KIO::SimpleJob::slotFinished() () from /usr/lib/libkio.so5 #13 0xb6cb09ce in KIO::ListJob::slotFinished() () from /usr/lib/libkio.so.5 #14 0xb6cb5803 in KIO::ListJob::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #15 0xb6a6c580 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #16 0xb6a6d302 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #17 0xb6d61fb7 in KIO::SlaveInterface::finished() () from /usr/lib/libkio.so.5 #18 0xb6d64c0f in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /usr/lib/libkio.so.5 #19 0xb6d625c7 in KIO::SlaveInterface::dispatch() () from /usr/lib/libkio.so.5 #20 0xb6d54ee0 in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5 #21 0xb6d55253 in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #22 0xb6a6c580 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #23 0xb6a6d302 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #24 0xb6c7e0a7 in KIO::Connection::readyRead() () from /usr/lib/libkio.so.5 #25 0xb6c7fad3 in ?? () from /usr/lib/libkio.so.5 #26 0xb6c80126 in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #27 0xb6a6571b in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4 #28 0xb6a67281 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #29 0xb5fed8fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #30 0xb5ff575e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #31 0xb7d218fd in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #32 0xb6a57961 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #33 0xb6a585d5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #34 0xb6a587cd in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #35 0xb6a8236f in ?? () from /usr/lib/libQtCore.so.4 #36 0xb44369a8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #37 0xb443a063 in ?? () from /usr/lib/libglib-2.0.so.0 #38 0xb443a221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #39 0xb6a81fb8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #40 0xb6086785 in ?? () from /usr/lib/libQtGui.so.4 #41 0xb6a5601a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #42 0xb6a561da in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #43 0xb6a58895 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #44 0xb5fed777 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #45 0x0804a5e0 in main (argc=550, argv=0x86e38f8) at /usr/src/debug/kdepim-4.1.96/kmail/main.cpp:146 Reproducible: Always Steps to Reproduce: 1. start kmail Actual Results: kmail crashes. No chance to take any other action with the program Expected Results: To be able to use kmail >From openSUSE-11.1 (with zypper up updates as of 2009-01-26) and zypper dup -r KDE4:Factory as of 2009-01-23 -- 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