Bug 284279 - Resources cannot be added or removed on testing
Summary: Resources cannot be added or removed on testing
Status: RESOLVED FIXED
Alias: None
Product: Active
Classification: Plasma
Component: Plasma mobile shell (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: VHI critical
Target Milestone: unscheduled
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-17 15:42 UTC by Javier Llorente
Modified: 2011-12-06 10:44 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Javier Llorente 2011-10-17 15:42:59 UTC
Version:           unspecified
OS:                Linux

I have seen the following behaviour on 2011-10-16-16-48-meego-plasma-active-testing-USB-live.iso:

- Resources aren't displayed even after waiting for some time.
Restarting plasma-device is the trick to have them back (the ones that come in some activities by default + the ones you have added manually, if any). If you try to add some resources after restarting plasma-device, you will get the same result; no resources are added until you restart it again.

- Resources cannot be removed. Long tapping on the icon → activities → current activity doesn't do anything; the resource stays there on your activity until you restart plasma-device.

Note: resources are actually added/removed but changes aren't reflected, so for the normal user resources cannot be added or removed.

Reproducible: Always

Steps to Reproduce:
1. Flash 2011-10-16-16-48-meego-plasma-active-testing-USB-live.iso
2. Observe the display after first boot (no resources are displayed)
3. Try to add some resources
4. Observe the current activity (no resources are added)
5. Restart plasma-device
6. Observe the current activity (resources are displayed; default ones+the ones you add)
7. Try to remove some resources
8. Observe the current activity (resources aren't removed)
9. Restart plasma-device (resources previously removed are gone)


Expected Results:  
1. Resources should be displayed on first boot
2. Adding/removing resources shouldn't require restarting plasma-device; changes on resources should be reflected instantly.
Comment 1 Javier Llorente 2011-10-18 10:12:49 UTC
I'm seeing the same behaviour on 2011-10-18-00-53-meego-plasma-contour-in-progress-USB-live.iso
Comment 2 Javier Llorente 2011-10-18 14:03:48 UTC
This bug is not reproducible on 2011-10-11-17-56-meego-plasma-active-testing-USB-live.iso
Resources are loaded on first boot (after some minutes) and they can be added/removed.
Comment 3 Maurice de la Ferté 2011-10-28 10:56:54 UTC
The latest 'Testing' image is still effected by this bug:
2011-10-27-21-59-basyskom-plasma-active-testing-meego-usb-live.iso
Comment 4 Javier Llorente 2011-10-31 13:41:15 UTC
On 2011-10-27-21-59-basyskom-plasma-active-testing-meego-usb-live.iso, I cannot add/remove resources and restarting plasma-device does not do the trick any longer; apps and bookmarks appear after restarting it but not resources of other types (images, documents,etc).

BTW, starting plasma-device shows errors that I do not remember having seen before;
Soprano: "org.freedesktop.DBus.Error.UnknownObject - No such object path '/org/soprano/Server'"
Soprano: "QLocalSocket::connectToServer: Invalid name"
Comment 5 Javier Llorente 2011-10-31 15:50:58 UTC
The "restarting plasma-device" trick works again on 2011-10-27-21-59-basyskom-plasma-active-testing-meego-usb-live.iso + latest updates (from today).
Comment 6 Javier Llorente 2011-11-02 10:49:02 UTC
Resources aren't loaded on first boot nor they can be added/removed after second boot unless you restart plasma-device. I can see them on the "add resource" overlay but choosing any and tapping on "Add items" has no effect. The same applies to removing/unlinking resources.
Tested on 2011-11-02-09-45-basyskom-plasma-active-devel-USB-live.iso
Comment 7 Javier Llorente 2011-11-07 18:24:51 UTC
Resources on pre-filled activities aren't loaded on first boot nor adding resources to them works (changes are displayed on next boot though). Nevertheless, adding/removing resources after first boot to user created activities works. You have to wait some time until you get all the resources' categories on the add resource overlay.

Tested on 2011-11-04-22-22-basyskom-plasma-active-devel-USB-live.iso + latest updates
Comment 8 Javier Llorente 2011-11-10 14:18:38 UTC
Adding resources after first boot on user created activities works fine. Removing them doesn't work properly; you have to long tap and go through the menu twice (until you get the dots next to the current activity), after that plasma-device crashes (this is actually bug #286012 which is a duplicate of bug #285784). 
Tested on 2011-11-04-22-22 devel image + today's updates.

Application: Plasma Workspace (plasma-device), signal: Segmentation fault
[KCrash Handler]
#7  QBasicAtomicInt::ref (this=0xaad1970, other=@0xaad1978) at ../../src/corelib/arch/qatomic_i386.h:120
#8  QString::operator= (this=0xaad1970, other=@0xaad1978) at tools/qstring.cpp:1357
#9  0xa9180e16 in QPair<QString, int>::operator= (this=0xb19d560, abegin=0xaad1970, aend=0xaad1978) at /usr/include/qt4/QtCore/qpair.h:63
#10 qCopy<QPair<QString, int>*, QPair<QString, int>*> (this=0xb19d560, abegin=0xaad1970, aend=0xaad1978) at /usr/include/qt4/QtCore/qalgorithms.h:82
#11 QVector<QPair<QString, int> >::erase (this=0xb19d560, abegin=0xaad1970, aend=0xaad1978) at /usr/include/qt4/QtCore/qvector.h:606
#12 0xa917f698 in QVector<QPair<QString, int> >::remove (this=0xb19d520, urls=...) at /usr/include/qt4/QtCore/qvector.h:364
#13 MetadataCloudModel::entriesRemoved (this=0xb19d520, urls=...) at ../../../components/metadatamodel/metadatacloudmodel.cpp:327
#14 0xa917fb2d in MetadataCloudModel::qt_metacall (this=0xb19d520, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbffc4f58) at ./metadatacloudmodel.moc:100
#15 0x47f466ab in QMetaObject::metacall (object=0xb19d520, cl=QMetaObject::InvokeMetaMethod, idx=40, argv=0xbffc4f58) at kernel/qmetaobject.cpp:237
#16 0x47f54f8f in QMetaObject::activate (sender=0xa8ffed0, m=0xa91602e0, local_signal_index=1, argv=0xbffc4f58) at kernel/qobject.cpp:3278
#17 0xa9149fc4 in Nepomuk::Query::QueryServiceClient::entriesRemoved (this=0xa8ffed0, _t1=...) at ./queryserviceclient.moc:154
#18 0xa914b362 in Nepomuk::Query::QueryServiceClient::Private::_k_entriesRemoved (this=0x9a10ae8, uris=...) at ../../../nepomuk/query/queryserviceclient.cpp:125
#19 0xa914bd70 in Nepomuk::Query::QueryServiceClient::qt_metacall (this=0xa8ffed0, _c=QMetaObject::InvokeMetaMethod, _id=16, _a=0xbffc50d8) at ./queryserviceclient.moc:133
#20 0x47f466ab in QMetaObject::metacall (object=0xa8ffed0, cl=QMetaObject::InvokeMetaMethod, idx=20, argv=0xbffc50d8) at kernel/qmetaobject.cpp:237
#21 0x47f54f8f in QMetaObject::activate (sender=0x9a10b10, m=0xa9160404, local_signal_index=0, argv=0xbffc50d8) at kernel/qobject.cpp:3278
#22 0xa9155064 in OrgKdeNepomukQueryInterface::entriesRemoved (this=0x9a10b10, _t1=...) at queryinterface.moc:114
#23 0xa91554e5 in OrgKdeNepomukQueryInterface::qt_metacall (this=0x9a10b10, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbffc524c) at queryinterface.moc:89
#24 0x480f6cbd in QDBusConnectionPrivate::deliverCall (this=0x999ea90, object=0x9a10b10, msg=..., metaTypes=..., slotIdx=5) at qdbusintegrator.cpp:941
#25 0x481014e8 in QDBusCallDeliveryEvent::placeMetaCall (this=0xa4d8640, object=0x9a10b10) at qdbusintegrator_p.h:103
#26 0x47f54ad7 in QObject::event (this=0x9a10b10, e=0xa4d8640) at kernel/qobject.cpp:1217
#27 0x4882059c in QApplicationPrivate::notify_helper (this=0x8633890, receiver=0x9a10b10, e=0xa4d8640) at kernel/qapplication.cpp:4467
#28 0x4882517e in QApplication::notify (this=0x8629488, receiver=<value optimized out>, e=0xa4d8640) at kernel/qapplication.cpp:3867
#29 0xb726f62b in KApplication::notify (this=0x8629488, receiver=0x9a10b10, event=0xa4d8640) at ../../kdeui/kernel/kapplication.cpp:311
#30 0x47f40323 in QCoreApplication::notifyInternal (this=0x8629488, receiver=0x9a10b10, event=0xa4d8640) at kernel/qcoreapplication.cpp:731
#31 0x47f43d55 in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x8612f78) at ../../src/corelib/kernel/qcoreapplication.h:215
#32 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x8612f78) at kernel/qcoreapplication.cpp:1372
#33 0x47f43f2e in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1265
#34 0x47f6c7e5 in QCoreApplication::sendPostedEvents (s=0x8635180) at ../../src/corelib/kernel/qcoreapplication.h:220
#35 postEventSourceDispatch (s=0x8635180) at kernel/qeventdispatcher_glib.cpp:277
#36 0x47a41afb in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#37 0x47a4211f in ?? () from /lib/libglib-2.0.so.0
#38 0x47a422e2 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#39 0x47f6c95d in QEventDispatcherGlib::processEvents (this=0x8612e70, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#40 0x488d07b6 in QGuiEventDispatcherGlib::processEvents (this=0x8612e70, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#41 0x47f3f4ba in QEventLoop::processEvents (this=0xbffc5a14, flags=...) at kernel/qeventloop.cpp:149
#42 0x47f3f76a in QEventLoop::exec (this=0xbffc5a14, flags=...) at kernel/qeventloop.cpp:201
#43 0x47f43ff4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#44 0x4881e608 in QApplication::exec () at kernel/qapplication.cpp:3741
#45 0xb77dca29 in kdemain (argc=1, argv=0xbffc5c24) at ../../shell/main.cpp:63
#46 0x0804858c in main (argc=1, argv=0xbffc5c24) at plasma-device_dummy.cpp:3
Comment 9 Javier Llorente 2011-12-06 10:44:48 UTC
Already fixed in 2011-12-06-09-24-basyskom-plasma-active-testing-meego-usb-live.iso