- openSUSE KDE

RE: Re: [opensuse-kde] Leap Display settings
by stakanov＠freenet.de 09 Feb '16

09 Feb '16

> -----Ursprüngliche Nachricht----- > Von: Felix Miata > Gesendet: Di. 09.02.2016 20:06 > An: opensuse-kde(a)opensuse.org > Kopie: don fisher , > Betreff: Re: [opensuse-kde] Leap Display settings > > don fisher composed on 2016-02-09 11:25 (UTC-0700): > >> Felix Miata wrote: > >> Sorry, but I never made a screen shot before. How do you do this? My > > It used to be a utility aptly named ksnapshot, but since Kupstream recently > decided an apt name was no longer appropriate, I don't recall its name. Try > looking in graphics and utilities sections of main menu. If you don't see > anything and googling is no help, inquire on the opensuse-kde or a kde.org > mailing list what you're supposed to look for. > >> ~/.xsession-errors file is empty, yesterdays date. I have attached the >> .xsession-errors-:0 file. Don't recall what the difference is right now. > > I don't either. > >> I have also attached the outputs of the zypper and lspci commands you >> requested. Do you know how do you get Thunderbird to see fies starting >> with a .? > > Possibly by a right click while the file picker is open to see something like > "show all files". > >> felix.txt >> zypper se -s | grep ^i | sort | egrep 'creen|randr' > ... >> lspci | grep VGA >> 18:01:00.0 VGA compatible controller: NVIDIA Corporation GK104M [GeForce GTX 880M] (rev a1) > > >> xsession-errors-:0 > ... > Nothing there that I recognize as trouble, except that the session was not > plasma, but fvwm. > -- > "The wise are known for their understanding, and pleasant > words are persuasive." Proverbs 16:21 (New Living Translation) > > Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! > > Felix Miata *** http://fm.no-ip.com/ > -- > To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- The desired application is called "Spectacle" You can find it in Accessories or, if the shortcut is correctly set, it is sufficient as Per wrote to tap on the print screen button of you keyboard. --- Mail & Cloud Made in Germany mit 3 GB Speicher! https://email.freenet.de/mail/Uebersicht?epid=e9900000450 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] How are opensuse doing on the webkit-security updates?
by ianseeks 09 Feb '16

09 Feb '16

There is an accusation that distros are a long way behind the curve on updates. https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] Does kmymoney work with KDEPIM5?
by Stefan Vater 08 Feb '16

08 Feb '16

Hi, after Tumbleweed switched to KDEPIM5, I would like to use it too. But I also need kmymoney which has no official kf5 based version yet, and depends on akonadi4 in some parts. However, when I try to upgrade yast/zypper does not suggest to uninstal kmymoney. So does it still work with new KDEPIM5? If anyone has experience in that, I would appreciate! Thanks, Stefan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

[opensuse-kde] /var/tmp/kdecache-<username>/*
by Felix Miata 07 Feb '16

07 Feb '16

What's the purpose of multiple files of size 10280K or 82240K for every user who's ever logged into KDE? I find it hard to believe there would be more than a tiny fraction of icon files consuming space on disk compared to the 10280K icon-cache.kcache file, or that every user needs one or more theme cache's of 82240K. I also find it hard to believe a cache file of 82240K size could speed anything up. /var/tmp/kdecache-<username>/plasma-wallpapers/usr/share/wallpapers/Elarun/contents/images/2560x1600.png_#000000_0_1920x1200.png's 859115 byte consumption makes no sense either. What's the story on this puzzling filesystem space consumption? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] Tumbleweed : constant crash of plasma5
by Bruno Friedmann 06 Feb '16

06 Feb '16

I'm seeing tons of crash with my newer TW Opening closing, changing desktop etc lead to several kind of crash. They are all marked as closed (upstream QT) or directly in kde like https://bugs.kde.org/show_bug.cgi?id=355650 or Most of them tagged as duplicate of https://bugs.kde.org/show_bug.cgi?id=342763 I'm a bit confuse, since the version indicated as fixed seems to be installed Qt5.5.1 or plasma5 at 5.5.3-1.1 Anyone who can drive me to better backtrace or stop the crash will be receive here as a "hero" :-)) Some informations. My computer is a new Dell Workstation Precision Laptop 7510 series with a Intel(R) Xeon(R) CPU E3-1535M v5 @ 2.90GHz as cpu Intel GPU is P630 + Nvidia Quadro M2000M (actually with nouveau on optimus configuration) (i915 + nouveau ) loaded. I've tried few days ago Nvidia LTS 352.79 and also the newer 316.18 With kernel 4.4.0 and latest 4.5-rc1 (from kernel:head) without seeing big differences. On compositor I'm using openGL 3.1 + EGL Typical crash backtrace : Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff9aa4b68c0 (LWP 19416))] Thread 8 (Thread 0x7ff993c31700 (LWP 19419)): #0 0x00007ff9a3a3724d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007ff9a890d432 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7ff993c30c00) at /usr/include/bits/poll2.h:46 #2 0x00007ff9a890d432 in _xcb_conn_wait (c=c@entry=0xd3ed90, cond=cond@entry=0xd3edd0, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x00007ff9a890f007 in xcb_wait_for_event (c=0xd3ed90) at xcb_in.c:693 #4 0x00007ff995d80e29 in QXcbEventReader::run() (this=0xd492a0) at qxcbconnection.cpp:1229 #5 0x00007ff9a412894f in QThreadPrivate::start(void*) (arg=0xd492a0) at thread/qthread_unix.cpp:331 #6 0x00007ff9a323e4a4 in start_thread (arg=0x7ff993c31700) at pthread_create.c:334 #7 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7ff991d9c700 (LWP 19426)): #0 0x00007ff9a3a3724d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007ff9a012c264 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7ff984003070, timeout=<optimized out>, context=0x7ff984000990) at gmain.c:4135 #2 0x00007ff9a012c264 in g_main_context_iterate (context=context@entry=0x7ff984000990, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3835 #3 0x00007ff9a012c36c in g_main_context_iteration (context=0x7ff984000990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x00007ff9a434d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7ff9840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x00007ff9a42f763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ff991d9bcf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x00007ff9a4123b1c in QThread::exec() (this=this@entry=0xe23720) at thread/qthread.cpp:503 #7 0x00007ff9a73f39a5 in QQmlThreadPrivate::run() (this=0xe23720) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #8 0x00007ff9a412894f in QThreadPrivate::start(void*) (arg=0xe23720) at thread/qthread_unix.cpp:331 #9 0x00007ff9a323e4a4 in start_thread (arg=0x7ff991d9c700) at pthread_create.c:334 #10 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7ff97ffc2700 (LWP 19427)): #0 0x00007ff9a016f4b9 in g_mutex_lock (mutex=mutex@entry=0x7ff978000990) at gthread-posix.c:1338 #1 0x00007ff9a012ba91 in g_main_context_query (context=context@entry=0x7ff978000990, max_priority=2147483647, timeout=timeout@entry=0x7ff97ffc1bdc, fds=fds@entry=0x7ff978002e70, n_fds=n_fds@entry=1) at gmain.c:3544 #2 0x00007ff9a012c1df in g_main_context_iterate (context=context@entry=0x7ff978000990, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3822 #3 0x00007ff9a012c36c in g_main_context_iteration (context=0x7ff978000990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x00007ff9a434d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7ff9780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x00007ff9a42f763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ff97ffc1cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x00007ff9a4123b1c in QThread::exec() (this=this@entry=0x11bd4a0) at thread/qthread.cpp:503 #7 0x00007ff9a73f39a5 in QQmlThreadPrivate::run() (this=0x11bd4a0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #8 0x00007ff9a412894f in QThreadPrivate::start(void*) (arg=0x11bd4a0) at thread/qthread_unix.cpp:331 #9 0x00007ff9a323e4a4 in start_thread (arg=0x7ff97ffc2700) at pthread_create.c:334 #10 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7ff97e752700 (LWP 19428)): #0 0x00007ff9a012b8a6 in g_main_context_prepare (context=context@entry=0x7ff970000990, priority=priority@entry=0x7ff97e751bd8) at gmain.c:3453 #1 0x00007ff9a012c193 in g_main_context_iterate (context=context@entry=0x7ff970000990, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3820 #2 0x00007ff9a012c36c in g_main_context_iteration (context=0x7ff970000990, may_block=may_block@entry=1) at gmain.c:3901 #3 0x00007ff9a434d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7ff9700008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x00007ff9a42f763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ff97e751cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x00007ff9a4123b1c in QThread::exec() (this=this@entry=0x1243b90) at thread/qthread.cpp:503 #6 0x00007ff9a73f39a5 in QQmlThreadPrivate::run() (this=0x1243b90) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #7 0x00007ff9a412894f in QThreadPrivate::start(void*) (arg=0x1243b90) at thread/qthread_unix.cpp:331 #8 0x00007ff9a323e4a4 in start_thread (arg=0x7ff97e752700) at pthread_create.c:334 #9 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7ff97ce67700 (LWP 19430)): #0 0x00007ff9a324407f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007ff9a9b9ba84 in QTWTF::TCMalloc_PageHeap::scavengerThread() (this=0x7ff9a9e82ea0 <QTWTF::pageheap_memory>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x00007ff9a9b9bac9 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x00007ff9a323e4a4 in start_thread (arg=0x7ff97ce67700) at pthread_create.c:334 #4 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7ff974ac3700 (LWP 19436)): #0 0x00007ff9a3a3724d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007ff9a012c264 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7ff8e40041d0, timeout=<optimized out>, context=0x7ff8e400c7f0) at gmain.c:4135 #2 0x00007ff9a012c264 in g_main_context_iterate (context=context@entry=0x7ff8e400c7f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3835 #3 0x00007ff9a012c36c in g_main_context_iteration (context=0x7ff8e400c7f0, may_block=may_block@entry=1) at gmain.c:3901 #4 0x00007ff9a434d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7ff8e40040b0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x00007ff9a42f763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ff974ac2cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x00007ff9a4123b1c in QThread::exec() (this=this@entry=0x1964ad0) at thread/qthread.cpp:503 #7 0x00007ff9a7f78e42 in QQuickPixmapReader::run() (this=0x1964ad0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/util/qquickpixmapcache.cpp:760 #8 0x00007ff9a412894f in QThreadPrivate::start(void*) (arg=0x1964ad0) at thread/qthread_unix.cpp:331 #9 0x00007ff9a323e4a4 in start_thread (arg=0x7ff974ac3700) at pthread_create.c:334 #10 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7ff8ea7fe700 (LWP 19440)): #0 0x00007ff9a016f4d4 in g_mutex_unlock (mutex=0x7ff8dc00c700) at gthread-posix.c:1350 #1 0x00007ff9a012c186 in g_main_context_iterate (context=context@entry=0x7ff8dc00c700, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3818 #2 0x00007ff9a012c36c in g_main_context_iteration (context=0x7ff8dc00c700, may_block=may_block@entry=1) at gmain.c:3901 #3 0x00007ff9a434d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7ff8dc002c70, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x00007ff9a42f763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ff8ea7fdcd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x00007ff9a4123b1c in QThread::exec() (this=this@entry=0x3c6aa80) at thread/qthread.cpp:503 #6 0x00007ff8d207ce47 in KCupsConnection::run() (this=0x3c6aa80) at /usr/src/debug/print-manager-15.12.1/libkcups/KCupsConnection.cpp:304 #7 0x00007ff9a412894f in QThreadPrivate::start(void*) (arg=0x3c6aa80) at thread/qthread_unix.cpp:331 #8 0x00007ff9a323e4a4 in start_thread (arg=0x7ff8ea7fe700) at pthread_create.c:334 #9 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7ff9aa4b68c0 (LWP 19416)): [KCrash Handler] #6 0x00007ff9a71cfdf8 in VDMModelDelegateDataType::notify(QQmlAdaptorModel const&, QList<QQmlDelegateModelItem*> const&, int, int, QVector<int> const&) const (this=<optimized out>, items=..., index=1, count=1, roles=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/util/qqmladaptormodel.cpp:167 #7 0x00007ff9a74328ea in QQmlDelegateModel::_q_itemsChanged(int, int, QVector<int> const&) (roles=..., count=1, index=1, items=..., this=<optimized out>) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/util/qqmladaptormodel_p.h:118 #8 0x00007ff9a74328ea in QQmlDelegateModel::_q_itemsChanged(int, int, QVector<int> const&) (this=<optimized out>, index=1, count=1, roles=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/types/qqmldelegatemodel.cpp:1144 #9 0x00007ff9a7432a1a in QQmlDelegateModel::_q_dataChanged(QModelIndex const&, QModelIndex const&, QVector<int> const&) (this=<optimized out>, begin=..., end=..., roles=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/types/qqmldelegatemodel.cpp:1546 #10 0x00007ff9a74585bc in QQmlDelegateModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x35b7e60, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=12, _a=_a@entry=0x7ffe92db6a80) at .moc/moc_qqmldelegatemodel_p.cpp:203 #11 0x00007ff9a7458ca8 in QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) (this=0x35b7e60, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0x7ffe92db6a80) at .moc/moc_qqmldelegatemodel_p.cpp:344 #12 0x00007ff9a4327140 in QMetaObject::activate(QObject*, int, int, void**) (sender=0x35a62d0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe92db6a80) at kernel/qobject.cpp:3728 #13 0x00007ff9a4327787 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=<optimized out>, m=m@entry=0x7ff9a473cf40 <QAbstractItemModel::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe92db6a80) at kernel/qobject.cpp:3578 #14 0x00007ff9a439f21c in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector<int> const&) (this=<optimized out>, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:548 #15 0x00007ff8e80d1834 in TaskManager::TasksModelPrivate::itemChanged(QFlags<TaskManager::TaskChange>) (this=0x35a5b70, changes=...) at /usr/src/debug/plasma-workspace-5.5.3/libtaskmanager/tasksmodel.cpp:521 #16 0x00007ff8e80d29b7 in TaskManager::TasksModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x35a62d0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=9, _a=_a@entry=0x7ffe92db6c60) at /usr/src/debug/plasma-workspace-5.5.3/build/libtaskmanager/moc_tasksmodel.cpp:214 #17 0x00007ff9a4326f8a in QMetaObject::activate(QObject*, int, int, void**) (sender=0x3f2ff70, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe92db6c60) at kernel/qobject.cpp:3713 #18 0x00007ff9a4327787 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=<optimized out>, m=m@entry=0x7ff8e82f7900 <TaskManager::AbstractGroupableItem::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe92db6c60) at kernel/qobject.cpp:3578 #19 0x00007ff8e80da338 in TaskManager::AbstractGroupableItem::changed(QFlags<TaskManager::TaskChange>) (this=<optimized out>, _t1=...) at /usr/src/debug/plasma-workspace-5.5.3/build/libtaskmanager/moc_abstractgroupableitem.cpp:223 #20 0x00007ff8e80c7b90 in TaskManager::TaskItem::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (change=..., this=<optimized out>) at /usr/src/debug/plasma-workspace-5.5.3/libtaskmanager/taskitem.cpp:73 #21 0x00007ff8e80c7b90 in TaskManager::TaskItem::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/plasma-workspace-5.5.3/build/libtaskmanager/moc_taskitem.cpp:147 #22 0x00007ff9a4326f8a in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x358f0e0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe92db6da0) at kernel/qobject.cpp:3713 #23 0x00007ff9a4327787 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x358f0e0, m=m@entry=0x7ff8e82f7600 <TaskManager::Task::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe92db6da0) at kernel/qobject.cpp:3578 #24 0x00007ff8e80da468 in TaskManager::Task::changed(QFlags<TaskManager::TaskChange>) (this=this@entry=0x358f0e0, _t1=...) at /usr/src/debug/plasma-workspace-5.5.3/build/libtaskmanager/moc_task.cpp:359 #25 0x00007ff8e80ba22b in TaskManager::Task::setActive(bool) (this=this@entry=0x358f0e0, a=a@entry=true) at /usr/src/debug/plasma-workspace-5.5.3/libtaskmanager/task.cpp:178 #26 0x00007ff8e80cd759 in TaskManager::TaskManager::activeWindowChanged(unsigned long long) (this=0x7ff8e82f8fa0 <TaskManager::(anonymous namespace)::Q_QGS_privateTaskManagerSelf::innerFunction()::holder>, w=<optimized out>) at /usr/src/debug/plasma-workspace-5.5.3/libtaskmanager/taskmanager.cpp:412 #27 0x00007ff9a4326e17 in QMetaObject::activate(QObject*, int, int, void**) (a=0x7ffe92db6f20, r=0x7ff8e82f8fa0 <TaskManager::(anonymous namespace)::Q_QGS_privateTaskManagerSelf::innerFunction()::holder>, this=<optimized out>) at ../../src/corelib/kernel/qobject_impl.h:124 #28 0x00007ff9a4326e17 in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x7ff9a7125c00 <(anonymous namespace)::Q_QGS_g_kwmInstanceContainer::innerFunction()::holder>, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffe92db6f20) at kernel/qobject.cpp:3698 #29 0x00007ff9a4327787 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x7ff9a7125c00 <(anonymous namespace)::Q_QGS_g_kwmInstanceContainer::innerFunction()::holder>, m=m@entry=0x7ff9a7124b80 <KWindowSystem::staticMetaObject>, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffe92db6f20) at kernel/qobject.cpp:3578 #30 0x00007ff9a6f170e2 in KWindowSystem::activeWindowChanged(unsigned long long) (this=this@entry=0x7ff9a7125c00 <(anonymous namespace)::Q_QGS_g_kwmInstanceContainer::innerFunction()::holder>, _t1=132120581) at /usr/src/debug/kwindowsystem-5.18.0/build/src/moc_kwindowsystem.cpp:303 #31 0x00007ff991fb080b in NETEventFilter::nativeEventFilter(xcb_generic_event_t*) (this=0x317ae40, ev=0x7ff98c007b60) at /usr/src/debug/kwindowsystem-5.18.0/src/platforms/xcb/kwindowsystem.cpp:208 #32 0x00007ff9a42f687f in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=<optimized out>, eventType=..., message=message@entry=0x7ff98c007b60, result=result@entry=0x7ffe92db7048) at kernel/qabstracteventdispatcher.cpp:460 #33 0x00007ff995d84804 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0xd3d1a0, event=event@entry=0x7ff98c007b60) at qxcbconnection.cpp:1020 #34 0x00007ff995d8558b in QXcbConnection::processXcbEvents() (this=0xd3d1a0) at qxcbconnection.cpp:1504 #35 0x00007ff9a4327d79 in QObject::event(QEvent*) (this=0xd3d1a0, e=<optimized out>) at kernel/qobject.cpp:1239 #36 0x00007ff9a56708cc in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0xd2e2e0, receiver=receiver@entry=0xd3d1a0, e=e@entry=0x7ff98c003c80) at kernel/qapplication.cpp:3716 #37 0x00007ff9a56759d6 in QApplication::notify(QObject*, QEvent*) (this=0x7ffe92db7760, receiver=0xd3d1a0, e=0x7ff98c003c80) at kernel/qapplication.cpp:3499 #38 0x00007ff9a42f9cf3 in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffe92db7760, receiver=0xd3d1a0, event=event@entry=0x7ff98c003c80) at kernel/qcoreapplication.cpp:965 #39 0x00007ff9a42fc016 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (event=0x7ff98c003c80, receiver=<optimized out>) at kernel/qcoreapplication.h:224 #40 0x00007ff9a42fc016 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xd237b0) at kernel/qcoreapplication.cpp:1593 #41 0x00007ff9a42fc4f8 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451 #42 0x00007ff9a434d103 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0xd7e500) at kernel/qeventdispatcher_glib.cpp:271 #43 0x00007ff9a012c097 in g_main_context_dispatch (context=0x7ff98c0016f0) at gmain.c:3154 #44 0x00007ff9a012c097 in g_main_context_dispatch (context=context@entry=0x7ff98c0016f0) at gmain.c:3769 #45 0x00007ff9a012c2c8 in g_main_context_iterate (context=context@entry=0x7ff98c0016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3840 #46 0x00007ff9a012c36c in g_main_context_iteration (context=0x7ff98c0016f0, may_block=may_block@entry=1) at gmain.c:3901 #47 0x00007ff9a434d50f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0xda0be0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #48 0x00007ff9a42f763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffe92db7610, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #49 0x00007ff9a42ff2fd in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1229 #50 0x00007ff9a483553c in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1527 #51 0x00007ff9a566cf75 in QApplication::exec() () at kernel/qapplication.cpp:2976 #52 0x0000000000436527 in main(int, char**) (argc=4, argv=<optimized out>) at /usr/src/debug/plasma-workspace-5.5.3/shell/main.cpp:179 -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

[opensuse-kde] KDE Keyboard Shortcuts work everywhere except in KDE apps
by billb＠sent.at 05 Feb '16

05 Feb '16

I installed OpenSUSE Leap 42.1. I want the newer KDE experience, so following the info at https://en.opensuse.org/SDB:KDE_repositories I installed Version: Leap 42.1 Extra: http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_42.1/ Applications: http://download.opensuse.org/repositories/KDE:/Applications/openSUSE_Leap_4… KDE Frameworks 5: http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_42… I want to have a Keyboard Shortcut assigned to type my email address on a keystroke. So I opened "System Settings"/"Workspace"/"Shortcuts"/"Custom Shortcuts"/"Configure Input Actions settings". I right-clicked and created a "New > Global Shortcut > Send keyboard input" shortcut with Name == "TypeMyEmail" Then I set Comment == "Comment" Trigger == "Meta+Ctrl+Alt+M" Action == "m:e:Shift+2:e:x:a:m:p:l:e:.:c:o:m" I open a LibreOffice document and press "Meta+Ctrl+Alt+M". I immediately get the email address me(a)example.com typed into the document. I test it in Firefox when filling out forms and it works too. But when I try it in any KDE application, like Kate or Konsole, I don't get the address output. I get different output depending on the app. For example in Kate -> "." in Konsole -> "^C" in ApplicationLauncher -> it closes the window in Dolphin -> "." How do I fix this so the KDE Shortcuts work in KDE apps too? Bill -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

[opensuse-kde] digikam and marble
by Olaf Hering 03 Feb '16

03 Feb '16

Problem: digikam-libs-4.14.0-3.1.x86_64 requires marble-data, but this requirement cannot be provided A few months ago I tried to install digikam, which would have installed "half of KDE". As a result I have added a lock on "marble", then installed digikam and all was fine. The current digikam pkg introduced a hard requirement for marble. Will digikam really stop working when marble is not installed? Perhaps the "Requires: marble-data" was meant to be a Recommends. Olaf -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

[opensuse-kde] Upcoming changes for KDE users in Tumbleweed
by Raymond Wooninck 24 Jan '16

24 Jan '16

Some history As you may know, up to now the default PIM suite for Plasma 5 in openSUSE Tumbleweed was the KDE PIM 4.14, based on kdelibs 4.x. While upstream KDE has offered a KF5-based version since Applications 15.08, it has been originally marked as a technology preview, so we (the openSUSE community KDE team) thought it would be more prudent to stick with the 4.14 version (but offer the KF5 based PIM as an option for the daring). Fast forward to today: KDE Applications 15.12.1 have been released, and we’ve been testing and using the KF5 based PIM suite for all these months with no issues. In addition, PIM developers have been adding interesting new features and impressive speed optimization (see the blog post by PIM developer Dan Vratil), and at the same time dropped support for the the 4.14 PIM suite. What does it mean for openSUSE? This means that from the next openSUSE Tumbleweed snapshot, the old PIM 4.14.x packages will be replaced by their KF5 counterparts. Most settings should be migrated automatically, and the mail store is set in a DE-independent location, so you should not lose any data. You have two options for upgrading: 1) Start from scratch Simply recreate all your accounts in the new interface and redownload all your mail. This works best with IMAP (with setups and if you have enough bandwidth. 2) Use the PIM settings exporter You can export all your mail from KMail: under the Tools menu, there is the option Import/Export KMail Data, which you can use to create an archive with all your mails and account configurations. You need to do this before upgrading, then use the same option in KMail after upgrading to the KF5 based version to have all your accounts, calendars and mail set up. Caveats The 4.14.x and KF5 versions of the PIM stack are incompatible with each other. Therefore if you do not fully upgrade the system you will get strange issues. Ensure you update with zypper dup or with the equivalent option in YaST to ensure that all packages will be picked up. Bugs Bugs? What bugs? Software is perfect! ;) Jokes aside, if you find a bug in the PIM stack, please report it to the upstream bug tracker. If instead it’s a bug in the openSUSE packages (missing dependencies, etc.), report it to openSUSE’s Bugzilla Thanks Thanks go to the KDE PIM developers for their awesome work despite their small numbers (Laurent Montel and Dan Vratil deserve several beers each ;). See also Some history As you may know, up to now the default PIM suite for Plasma 5 in openSUSE Tumbleweed was the KDE PIM 4.14, based on kdelibs 4.x. While upstream KDE has offered a KF5-based version since Applications 15.08, it has been originally marked as a technology preview, so we (the openSUSE community KDE team) thought it would be more prudent to stick with the 4.14 version (but offer the KF5 based PIM as an option for the daring). Fast forward to today: KDE Applications 15.12.1 have been released, and we’ve been testing and using the KF5 based PIM suite for all these months with no issues. In addition, PIM developers have been adding interesting new features and impressive speed optimization (see the blog post by PIM developer Dan Vratil), and at the same time dropped support for the the 4.14 PIM suite. What does it mean for openSUSE? This means that from the next openSUSE Tumbleweed snapshot, the old PIM 4.14.x packages will be replaced by their KF5 counterparts. Most settings should be migrated automatically, and the mail store is set in a DE-independent location, so you should not lose any data. You have two options for upgrading: Start from scratch Simply recreate all your accounts in the new interface and redownload all your mail. This works best with IMAP (with setups and if you have enough bandwidth. Use the PIM settings exporter You can export all your mail from KMail: under the Tools menu, there is the option Import/Export KMail Data, which you can use to create an archive with all your mails and account configurations. You need to do this before upgrading, then use the same option in KMail after upgrading to the KF5 based version to have all your accounts, calendars and mail set up. Caveats The 4.14.x and KF5 versions of the PIM stack are incompatible with each other. Therefore if you do not fully upgrade the system you will get strange issues. Ensure you update with zypper dup or with the equivalent option in YaST to ensure that all packages will be picked up. Bugs Bugs? What bugs? Software is perfect! ;) Jokes aside, if you find a bug in the PIM stack, please report it to the upstream bug tracker. If instead it’s a bug in the openSUSE packages (missing dependencies, etc.), report it to openSUSE’s Bugzilla Thanks Thanks go to the KDE PIM developers for their awesome work despite their small numbers (Laurent Montel and Dan Vratil deserve several beers each ;) See also Luca's post here: https://www.dennogumi.org/2016/01/kdepim-changes-in-opensuse-tumbleweed/ Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

7 20

[opensuse-kde] KDE5 bluetooth system not running
by Malte Gell 23 Jan '16

23 Jan '16

Hi there, I have a USB bluetooth dongle connected to my machine (0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0 to be precise). When I now log in to a new KDE5 session, the bluetooth icon appears, but the BT adapter seems to not be activated.... Service bluetooth.service is running, restarting it, does not help. The only help so far is to pull and replug the BT dongle. Do you know any workaround to get active BT in KDE5 from start? Thanks -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] TW The kwin_x11 process keeps stopping causing the window decorations to disappear
by Roman Bysh 22 Jan '16

22 Jan '16

Hi, Anyone else experiencing the window decorations disappearing just as the "kwin_x11" process stops? This is happening quite often in Tumbleweed. I this a normal to have a separate process just for just for the decorations. Cheers! Roman -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

6 12