January 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 739884] New: Kdevelop 4.2 can not set debugging launch.
by bugzilla_noreply＠novell.com 19 Jan '13

19 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=739884 https://bugzilla.novell.com/show_bug.cgi?id=739884#c0 Summary: Kdevelop 4.2 can not set debugging launch. Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: a.shimmura(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20100101 Firefox/9.0 Kdevelop 4.2 (on openSUSE 12.1 KDE 4.7.2) can not set debugging launch,and say "Could not locate the debugging shell 'file:///bin/bash'.". Reproducible: Always Steps to Reproduce: 1.Run menue -> Configure Launches 2.set Debug shell "/bin/bash" or any other shell. 3."Could not locate the debugging shell 'file:///bin/bash'.". Actual Results: "Could not locate the debugging shell 'file:///bin/bash'.". and can not debugging launch. Expected Results: Kdevelop can set debugging shell. -- 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 729706] New: opensuse 12.1 RC 2 control bar chaos
by bugzilla_noreply＠novell.com 19 Jan '13

19 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=729706 https://bugzilla.novell.com/show_bug.cgi?id=729706#c0 Summary: opensuse 12.1 RC 2 control bar chaos Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: 64bit OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: hans-juergen.greif(a)kabelbw.de 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 Hello, it may be I am unable to control the control bar. Symbols lay one upon the other, they can not be positioned. At each boot symbols are at a different place; it is a pure chaos. Any help is appreciated. Reproducible: Always Steps to Reproduce: 1.boot opensuse 12.1 2. 3. Actual Results: chaos in control bar Expected Results: functional control bar -- 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 799458] New: Reboot and or Shutdown requests Root auth..
by bugzilla_noreply＠novell.com 19 Jan '13

19 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=799458 https://bugzilla.novell.com/show_bug.cgi?id=799458#c0 Summary: Reboot and or Shutdown requests Root auth.. Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: caf4926(a)opensuse-forums.org QAContact: qa-bugs(a)suse.de Found By: Community User Blocker: --- 12.3 Gnome install _64 from Live CD Shutdown or Reboot requests Admin password. Test case: I went to Shutdown > Admin request pops up > I Cancel it > It logs me out > I try reboot and or Shutdown from the Login screen > Admin requests continue > eventually I give admin password and it shutdown -- 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 728731] New: Autologin issue: Cannot open ConsoleKit session: Connection was disconnected before a reply was received
by bugzilla_noreply＠novell.com 19 Jan '13

19 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=728731 https://bugzilla.novell.com/show_bug.cgi?id=728731#c0 Summary: Autologin issue: Cannot open ConsoleKit session: Connection was disconnected before a reply was received Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jux(a)4950.net QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 On a freshly Installed openSUSE 12.1 RC2 this message happens when enabling KDM AutoLogin "Warning: Cannot open ConsoleKit session: Unable to open session: Connection was disconnected before a reply was received". The logon continues after clicking "Ok". Reproducible: Always Steps to Reproduce: I can reproduce this by doing the following steps 1.) add a new user (maybe it also works with the first standard, non-root user) 2.) enable Auto-Login for this user via /etc/sysconfig/displaymanager/ DISPLAYMANAGER_AUTOLOGIN 3.) init 3 --> init 5 --> error occurs (also after reboot) After removing the user logon string from DISPLAYMANAGER_AUTOLOGIN and rebooting the message is gone again. -- 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 726088] New: Kdeveloper Segmentation fault
by bugzilla_noreply＠novell.com 19 Jan '13

19 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=726088 https://bugzilla.novell.com/show_bug.cgi?id=726088#c0 Summary: Kdeveloper Segmentation fault Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: chodorenko(a)mail.ru 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 Kdeveloper not start Application: KDevelop (kdevelop), signal: Segmentation fault [Current thread is 1 (Thread 0x7fdcf3be9760 (LWP 28584))] Thread 7 (Thread 0x7fdcda974700 (LWP 28585)): #0 0x00007fdcf0afe1eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdcf20c341e in wait (time=1000, this=0xac5bf0) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=<optimized out>, mutex=0xac2460, time=1000) at thread/qwaitcondition_unix.cpp:160 #3 0x00007fdcee4f8efb in ?? () from /usr/lib64/libkdevplatformlanguage.so.3 #4 0x00007fdcf20c3015 in QThreadPrivate::start (arg=0xac2440) at thread/qthread_unix.cpp:331 #5 0x00007fdcf0af9f05 in start_thread () from /lib64/libpthread.so.0 #6 0x00007fdcf0de853d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fdccfb34700 (LWP 28586)): #0 0x00007fff883fe98f in ?? () #1 0x00007fdccfb33b90 in ?? () #2 0x00007fdcef8afe91 in clock_gettime () from /lib64/librt.so.1 #3 0x00007fdcf2113054 in do_gettime (frac=0x7fdccfb33ba8, sec=0x7fdccfb33ba0) at tools/qelapsedtimer_unix.cpp:123 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #5 0x00007fdcf21d4b4d in QTimerInfoList::updateCurrentTime (this=0xb84b40) at kernel/qeventdispatcher_unix.cpp:339 #6 0x00007fdcf21d4e83 in QTimerInfoList::timerWait (this=0xb84b40, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #7 0x00007fdcf21d38ec in timerSourcePrepareHelper (src=<optimized out>, timeout=0x7fdccfb33c8c) at kernel/qeventdispatcher_glib.cpp:136 #8 0x00007fdcf21d3995 in timerSourcePrepare (source=<optimized out>, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169 #9 0x00007fdceb735b22 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #10 0x00007fdceb73692d in ?? () from /usr/lib64/libglib-2.0.so.0 #11 0x00007fdceb736f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #12 0x00007fdcf21d43a6 in QEventDispatcherGlib::processEvents (this=0xb78b10, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424 #13 0x00007fdcf21a8882 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #14 0x00007fdcf21a8a7f in QEventLoop::exec (this=0x7fdccfb33e20, flags=...) at kernel/qeventloop.cpp:201 #15 0x00007fdcf20c05cf in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498 #16 0x00007fdcf20c3015 in QThreadPrivate::start (arg=0xb86c50) at thread/qthread_unix.cpp:331 #17 0x00007fdcf0af9f05 in start_thread () from /lib64/libpthread.so.0 #18 0x00007fdcf0de853d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fdcce767700 (LWP 28603)): #0 0x00007fff883fe98f in ?? () #1 0x00007fdcce766b60 in ?? () #2 0x00007fdcef8afe91 in clock_gettime () from /lib64/librt.so.1 #3 0x00007fdcf2113054 in do_gettime (frac=0x7fdcce766b78, sec=0x7fdcce766b70) at tools/qelapsedtimer_unix.cpp:123 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #5 0x00007fdcf21d4b4d in QTimerInfoList::updateCurrentTime (this=0xeed1f0) at kernel/qeventdispatcher_unix.cpp:339 #6 0x00007fdcf21d4e83 in QTimerInfoList::timerWait (this=0xeed1f0, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #7 0x00007fdcf21d38ec in timerSourcePrepareHelper (src=<optimized out>, timeout=0x7fdcce766c5c) at kernel/qeventdispatcher_glib.cpp:136 #8 0x00007fdcf21d3995 in timerSourcePrepare (source=<optimized out>, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169 #9 0x00007fdceb735b22 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #10 0x00007fdceb73692d in ?? () from /usr/lib64/libglib-2.0.so.0 #11 0x00007fdceb736f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #12 0x00007fdcf21d43a6 in QEventDispatcherGlib::processEvents (this=0xee1770, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424 #13 0x00007fdcf21a8882 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #14 0x00007fdcf21a8a7f in QEventLoop::exec (this=0x7fdcce766df0, flags=...) at kernel/qeventloop.cpp:201 #15 0x00007fdcf20c05cf in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498 #16 0x00007fdcf218b94f in QInotifyFileSystemWatcherEngine::run (this=0xee1120) at io/qfilesystemwatcher_inotify.cpp:248 #17 0x00007fdcf20c3015 in QThreadPrivate::start (arg=0xee1120) at thread/qthread_unix.cpp:331 #18 0x00007fdcf0af9f05 in start_thread () from /lib64/libpthread.so.0 #19 0x00007fdcf0de853d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fdccb459700 (LWP 28612)): #0 0x00007fdcf0afde6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdcf20c34ab in wait (time=18446744073709551615, this=0x9e3030) at thread/qwaitcondition_unix.cpp:88 #2 QWaitCondition::wait (this=<optimized out>, mutex=0x8b8630, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160 #3 0x00007fdce8e5e104 in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x9e23f0, th=0xfcb010) at /usr/src/debug/kdelibs-4.7.2/threadweaver/Weaver/WeaverImpl.cpp:365 #4 0x00007fdce8e606ab in ThreadWeaver::WorkingHardState::applyForWork (this=0x9148a0, th=0xfcb010) at /usr/src/debug/kdelibs-4.7.2/threadweaver/Weaver/WorkingHardState.cpp:71 #5 0x00007fdce8e5f56f in ThreadWeaver::ThreadRunHelper::run (this=0x7fdccb458e40, parent=0x9e23f0, th=0xfcb010) at /usr/src/debug/kdelibs-4.7.2/threadweaver/Weaver/Thread.cpp:87 #6 0x00007fdce8e5f5fb in ThreadWeaver::Thread::run (this=0xfcb010) at /usr/src/debug/kdelibs-4.7.2/threadweaver/Weaver/Thread.cpp:142 #7 0x00007fdcf20c3015 in QThreadPrivate::start (arg=0xfcb010) at thread/qthread_unix.cpp:331 #8 0x00007fdcf0af9f05 in start_thread () from /lib64/libpthread.so.0 #9 0x00007fdcf0de853d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fdcc74f1700 (LWP 28617)): #0 0x00007fdcf0afde6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdce847a56c in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x00007fdce847a699 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x00007fdcf0af9f05 in start_thread () from /lib64/libpthread.so.0 #4 0x00007fdcf0de853d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fdcc6b97700 (LWP 28618)): #0 0x00007fdcf0ddf423 in poll () from /lib64/libc.so.6 #1 0x00007fdceb736a98 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fdceb736f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fdcf21d43a6 in QEventDispatcherGlib::processEvents (this=0x81e220, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424 #4 0x00007fdcf21a8882 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007fdcf21a8a7f in QEventLoop::exec (this=0x7fdcc6b96e20, flags=...) at kernel/qeventloop.cpp:201 #6 0x00007fdcf20c05cf in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498 #7 0x00007fdcf20c3015 in QThreadPrivate::start (arg=0x1f64f70) at thread/qthread_unix.cpp:331 #8 0x00007fdcf0af9f05 in start_thread () from /lib64/libpthread.so.0 #9 0x00007fdcf0de853d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fdcf3be9760 (LWP 28584)): [KCrash Handler] #6 0x00007fdce8496b39 in WTF::OSAllocator::reserveUncommitted(unsigned long, WTF::OSAllocator::Usage, bool, bool) () from /usr/lib64/libQtWebKit.so.4 #7 0x00007fdce857b208 in JSC::ExecutableAllocator::isValid() const () from /usr/lib64/libQtWebKit.so.4 #8 0x00007fdce84e21ec in JSC::JSGlobalData::JSGlobalData(JSC::JSGlobalData::GlobalDataType, JSC::ThreadStackType) () from /usr/lib64/libQtWebKit.so.4 #9 0x00007fdce84e4753 in JSC::JSGlobalData::createLeaked(JSC::ThreadStackType) () from /usr/lib64/libQtWebKit.so.4 #10 0x00007fdce7c193e2 in WebCore::JSDOMWindowBase::commonJSGlobalData() () from /usr/lib64/libQtWebKit.so.4 #11 0x00007fdce7bda226 in WebCore::FrameLoaderClientQt::createDocumentLoader(WebCore::ResourceRequest const&, WebCore::SubstituteData const&) () from /usr/lib64/libQtWebKit.so.4 #12 0x00007fdce7f3c3d5 in WebCore::FrameLoader::load(WebCore::ResourceRequest const&, WebCore::SubstituteData const&, bool) () from /usr/lib64/libQtWebKit.so.4 #13 0x00007fdce7ba0883 in QWebFrame::setHtml(QString const&, QUrl const&) () from /usr/lib64/libQtWebKit.so.4 #14 0x00007fdcccacf27a in ManPageModel::indexParser (this=0x706da0) at /usr/src/debug/kdevelop-4.2.3/documentation/manpage/manpagemodel.cpp:180 #15 0x00007fdcccacf6fd in ManPageModel::indexDataReceived (this=0x706da0, job=<optimized out>) at /usr/src/debug/kdevelop-4.2.3/documentation/manpage/manpagemodel.cpp:136 #16 0x00007fdcccacfe24 in ManPageModel::qt_metacall (this=0x706da0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff88276a80) at /usr/src/debug/kdevelop-4.2.3/build/documentation/manpage/manpagemodel.moc:93 #17 0x00007fdcf21bc3fa in QMetaObject::activate (sender=0xbcca20, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff88276a80) at kernel/qobject.cpp:3287 #18 0x00007fdcf36755c2 in KJob::result (this=<optimized out>, _t1=0xbcca20) at /usr/src/debug/kdelibs-4.7.2/build/kdecore/kjob.moc:194 #19 0x00007fdcf3675600 in KJob::emitResult (this=0xbcca20) at /usr/src/debug/kdelibs-4.7.2/kdecore/jobs/kjob.cpp:312 #20 0x00007fdcef4e7764 in KIO::SimpleJob::slotFinished (this=0xbcca20) at /usr/src/debug/kdelibs-4.7.2/kio/kio/job.cpp:494 #21 0x00007fdcef4ef13d in KIO::TransferJob::slotFinished (this=0xbcca20) at /usr/src/debug/kdelibs-4.7.2/kio/kio/job.cpp:1081 #22 0x00007fdcef4edaa1 in KIO::TransferJob::qt_metacall (this=0xbcca20, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff88276e30) at /usr/src/debug/kdelibs-4.7.2/build/kio/jobclasses.moc:369 #23 0x00007fdcf21bc3fa in QMetaObject::activate (sender=0xf95f10, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3287 #24 0x00007fdcef593af1 in KIO::SlaveInterface::dispatch (this=<optimized out>, _cmd=104, rawdata=...) at /usr/src/debug/kdelibs-4.7.2/kio/kio/slaveinterface.cpp:172 #25 0x00007fdcef5909a5 in KIO::SlaveInterface::dispatch (this=0xf95f10) at /usr/src/debug/kdelibs-4.7.2/kio/kio/slaveinterface.cpp:88 #26 0x00007fdcef583bee in KIO::Slave::gotInput (this=0xf95f10) at /usr/src/debug/kdelibs-4.7.2/kio/kio/slave.cpp:344 #27 0x00007fdcef58434c in KIO::Slave::qt_metacall (this=0xf95f10, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff88277260) at /usr/src/debug/kdelibs-4.7.2/build/kio/slave.moc:82 #28 0x00007fdcf21bc3fa in QMetaObject::activate (sender=0xf4ef30, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3287 #29 0x00007fdcef4b8837 in dequeue (this=<optimized out>) at /usr/src/debug/kdelibs-4.7.2/kio/kio/connection.cpp:82 #30 KIO::ConnectionPrivate::dequeue (this=0xf30950) at /usr/src/debug/kdelibs-4.7.2/kio/kio/connection.cpp:71 #31 0x00007fdcef4b88dd in KIO::Connection::qt_metacall (this=0xf4ef30, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x1cc0560) at /usr/src/debug/kdelibs-4.7.2/build/kio/connection.moc:79 #32 0x00007fdcf21bffaa in QObject::event (this=0xf4ef30, e=<optimized out>) at kernel/qobject.cpp:1226 #33 0x00007fdcf1578be4 in notify_helper (e=0xf45b70, receiver=0xf4ef30, this=0x6466c0) at kernel/qapplication.cpp:4481 #34 QApplicationPrivate::notify_helper (this=0x6466c0, receiver=0xf4ef30, e=0xf45b70) at kernel/qapplication.cpp:4453 #35 0x00007fdcf157da71 in QApplication::notify (this=0x7fff88277ea0, receiver=0xf4ef30, e=0xf45b70) at kernel/qapplication.cpp:4360 #36 0x00007fdcf2996e36 in KApplication::notify (this=0x7fff88277ea0, receiver=0xf4ef30, event=0xf45b70) at /usr/src/debug/kdelibs-4.7.2/kdeui/kernel/kapplication.cpp:311 #37 0x000000000040adb6 in KDevelopApplication::notify (this=0x7fff88277ea0, receiver=0xf4ef30, event=0xf45b70) at /usr/src/debug/kdevelop-4.2.3/app/main.cpp:90 #38 0x00007fdcf21a967c in QCoreApplication::notifyInternal (this=0x7fff88277ea0, receiver=0xf4ef30, event=0xf45b70) at kernel/qcoreapplication.cpp:787 #39 0x00007fdcf21aca58 in sendEvent (event=0xf45b70, receiver=0xf4ef30) at kernel/qcoreapplication.h:215 #40 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x6163d0) at kernel/qcoreapplication.cpp:1428 #41 0x00007fdcf21d3ee3 in sendPostedEvents () at kernel/qcoreapplication.h:220 #42 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:277 #43 0x00007fdceb73658d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #44 0x00007fdceb736d88 in ?? () from /usr/lib64/libglib-2.0.so.0 #45 0x00007fdceb736f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #46 0x00007fdcf21d433f in QEventDispatcherGlib::processEvents (this=0x615fd0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #47 0x00007fdcf161beae in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #48 0x00007fdcf21a8882 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #49 0x00007fdcf21a8a7f in QEventLoop::exec (this=0x7fff88277c80, flags=...) at kernel/qeventloop.cpp:201 #50 0x00007fdcf21acc47 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #51 0x000000000040a500 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kdevelop-4.2.3/app/main.cpp:467 Reproducible: Always Steps to Reproduce: 1.Start Kdeveloper 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 776272] New: My Computer shows /home is folder but a file was expected error
by bugzilla_noreply＠novell.com 19 Jan '13

19 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=776272 https://bugzilla.novell.com/show_bug.cgi?id=776272#c0 Summary: My Computer shows /home is folder but a file was expected error Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: rb03884(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=502632) --> (http://bugzilla.novell.com/attachment.cgi?id=502632) Screenshot of Konqueror message User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 Click on My Computer and left-click on any partition or device name. The partition will open with a message on the bottom left corner of Konqueror. Example /home is a folder, but a file was expected. Reproducible: Always Steps to Reproduce: 1. Left-click on My Computer 2. Navigate to Disk Information 3. Left-click on a device or partition name Actual Results: /home is a folder, but a file was expected. Expected Results: No message should appear -- 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 799348] New: Slow USB-speed when copy large files to an usb-drive
by bugzilla_noreply＠novell.com 19 Jan '13

19 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=799348 https://bugzilla.novell.com/show_bug.cgi?id=799348#c0 Summary: Slow USB-speed when copy large files to an usb-drive Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: jackbauer900(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 the issue is in openSuSE 12.2 too, the same as in openSuSE 12.3Beta1. the problem: when copy large files (>1Gb or so) to my usb-drive the transfer speed is round about 600kb/s for an USB2-drive only in writing direction. reading is just fine (10-11MB/s). tested whith various usb-drives, same issue. into the KDE4 the transfer-speed is rising up to >40MB/s and fells down to 600kb/s after a while. an old bug-report shows the same problem in openSUSE 12.2 with KDE3, but the workaround is not valid for KDE4. look here: https://bugzilla.novell.com/show_bug.cgi?id=784987 exactly the same problem here in openSUSE 12.2 to 12.3Beta1 the same usb-drive with other system like linuxmint has 8-9Mb/s write speed on my mashine. Reproducible: Always Steps to Reproduce: 1. changed the usb-drive, doesnt solve the problem 2. upgraded the kernel to 3.8RC from opensuse build-serve, doesnt solve the problem 3. tested with win7 and linuxmint13 problem solved Actual Results: - i mounted the usb-drive by hand over mount /dev/sdc1 .... , same problem - played around with the mount options (sync, flush ....), no succsess Expected Results: - normal a write speed from 5-6Mb/s out of the box tested on an ohter computer with different hardware like mine, same issue -- 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 419913] SuSEfirewall2: implement reload
by bugzilla_noreply＠novell.com 19 Jan '13

19 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=419913 https://bugzilla.novell.com/show_bug.cgi?id=419913#c10 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #10 from Ludwig Nussel <lnussel(a)suse.com> 2013-01-19 12:58:51 CET --- . -- 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 515040] New: How to start lircmd properly?
by bugzilla_noreply＠novell.com 19 Jan '13

19 Jan '13

http://bugzilla.novell.com/show_bug.cgi?id=515040 Summary: How to start lircmd properly? Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: PC OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: revealed(a)freakmail.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-5.2 Firefox/3.0.11 Hello there! First: I got a Haupauge PVR150; (No MCE); Remote is: A415 (Hauppauge); I am able to use the TV-Card very well, together with: - ivtv <- SuSE rpm's - tv-viewer <- (Program for watching TV, etc. ) [Not available as SuSE (rpm)] http://sourceforge.net/projects/tv-viewer I wanted to use all features of LIRC, too. There is a problem with IVTV of SuSE rpm's. - There seems to be no firmware for PVR 150 remote included. - Firmware for card itselves is definitively included and working fine. So i had to get it from another resource. So here is the first question: Can the Firmware for the PVR 150 remote be included into IVTV SuSE packing? This would be very Helpful in any case!! :) So i wanted to: Change channels and use all the buttons. With SuSE RPM of LIRC there was no chance in doing this. But i am very lucky, that there is a speciel CVS version of LIRC which makes it possible. Here you can find the CVS Version: http://www.blushingpenguin.com/mark/blog/?p=24 But... This version doesnt offer a convinient way to start LIRC. So i got me the SuSE RPM and used the contained rclirc to start LIRC. This works pretty well itselves. I also put symlinks to fit the binarys that it complies the same way with SuSE rpm. Also i added missing files like the sysconfig script manually. So i can start the CVS version of LIRC. :) And i can use the remote together with TV-Viewer to change volume and channels. Question one: I am wondering if it was possible to have the new PVR150 compatibility layer of the CVS packet from the link provided above implementend into SuSE's LIRC package. As i know that this is working ???? Next step for me was to try lircmd: LIRCMD is a daemon which makes it possible to control the desktop like using a mouse via a remote control. I had to add a new mouse section to xorg.conf. This was relatively easy. It simulates a mouse with IntelliMouse protocol in my case. Here is the problem.. or am i wrong? Is it an implementation issue? Dont blame me if it relies on the CVS version. I am using the SuSE RPM rclirc to start the LIRC functions. But there is no way offered to start LIRCMD properly. It has to be started prior to detection of mouse devices as there has to be an: /dev/lircm existant which is being created by the lircmd daemon. Else you will find errors in Xorg.0.log like: /dev/lircm doesnt exist. So i altered the RCSCRIPT from the SuSE rpm to start before acpid. This fixes this issue for me. And as there dont seem to be any functions existing within SuSE rcscript to start lircmd. I added them. So the second question is. How is this LIRCMD thing started correctly with SuSE rpm? Maybe there is a more efficent easyer way than the one i did? I will provide a diff here, what i did. This made it work for me: (In case there is no easyer way.) I am no profession. But i would be happy to at least offer a proposal for implementation, if it is possible to have this included? :) --- lirc.suse 2009-06-21 19:49:12.000000000 +0200 +++ lirc.neu 2009-06-21 19:48:21.000000000 +0200 @@ -13,10 +13,12 @@ # ### BEGIN INIT INFO # Provides: lirc -# Required-Start: $remote_fs -# Required-Stop: $remote_fs -# Default-Start: 3 5 +# Default-Start: 3 4 5 # Default-Stop: 0 1 2 6 +# Required-Start: +# Required-Stop: +# X-Start-Before: acpid +# X-Stop-After: # Short-Description: lirc daemon # Description: The main task of lircd is to decode the infrared # signals and provide an uniform interface for client applications @@ -24,13 +26,23 @@ # Check for missing binaries (stale symlinks should not happen) lircd_BIN=/usr/sbin/lircd +lircmd_BIN=/usr/sbin/lircmd +lircmd_flag="/etc/lircmd.conf" + test -x $lircd_BIN || exit 5 +test -x $lircmd_BIN || exit 5 # Check for existence of needed config file and read it lircd_CONFIG=/etc/sysconfig/lirc test -r $lircd_CONFIG || exit 6 $lircd_CONFIG +# Check for lircmd config to be available +lircmd_CONFIG=/etc/lircmd.conf +test -r $lircmd_CONFIG || { echo "$lircmd_CONFIG not existing"; + if [ "$1" = "stop" ]; then exit 0; + else exit 6; fi; } + # Source LSB init functions # providing start_daemon, killproc, pidofproc, # log_success_msg, log_failure_msg and log_warning_msg. @@ -142,7 +154,8 @@ ## Start daemon with startproc(8). If this fails ## the return value is set appropriately by startproc. eval startproc $lircd_BIN $(makeargs) - + ## Start the lircmd as daemon (default) (no evaluation) + $lircmd_BIN $lircmd_flag # Remember status and be verbose rc_status -v ;; @@ -152,6 +165,7 @@ ## killproc sets the return value according to LSB. killproc -TERM $lircd_BIN + killproc -TERM $lircmd_BIN # Remember status and be verbose rc_status -v @@ -181,6 +195,7 @@ echo -n "Reload service lircd " ## if it supports it: killproc -HUP $lircd_BIN + killproc -HUP $lircmd_BIN #touch /var/run/lircd.pid rc_status -v @@ -195,6 +210,7 @@ # If it supports signaling: echo -n "Reload service lircd " killproc -HUP $lircd_BIN + killproc -HUP $lircmd_BIN #touch /var/run/lircd.pid rc_status -v @@ -217,6 +233,7 @@ # NOTE: checkproc returns LSB compliant status values. checkproc $lircd_BIN + checkproc $lircmd_BIN # NOTE: rc_status knows that we called this init script with # "status" option and adapts its messages accordingly. rc_status -v I hope i could tell you to the point of my questions. My English is not the best. Many thanks for your time and Help in forward! Greetings, Reproducible: Always Steps to Reproduce: 1.Install IVTV for PVR150 2. Install LIRC 3. Try using lircmd Actual Results: LIRCMD seems to not be implemented in startupconfiguration of SuSE 11.1. Expected Results: Hauppauge PVR150 working out of the Box. -- 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 9

[Bug 440142] lirc-0.8.4-1.5: ordered comparison of pointer with integer zero
by bugzilla_noreply＠novell.com 19 Jan '13

19 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=440142 https://bugzilla.novell.com/show_bug.cgi?id=440142#c3 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |UPSTREAM --- Comment #3 from Ludwig Nussel <lnussel(a)suse.com> 2013-01-19 12:37:45 CET --- needs to be fixed upstream 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 0