[Active] [Bug 315470] New: Application: plasma-desktop (0.4)
https://bugs.kde.org/show_bug.cgi?id=315470 Bug ID: 315470 Summary: Application: plasma-desktop (0.4) Classification: Unclassified Product: Active Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Plasma mobile shell Assignee: notm...@gmail.com Reporter: rosario_lambi...@hotmail.com CC: active@kde.org Application: plasma-desktop (0.4) KDE Platform Version: 4.9.4 Qt Version: 4.8.3 Operating System: Linux 3.5.0-17-generic x86_64 Distribution: Linux Mint 14 Nadia -- Information about the crash: In detail, tell us what you were doing when the application crashed. The crash can be reproduced some of the time. -- Backtrace: Application: Plasma Desktop Shell (plasma-desktop), signal: Bus error Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f83ab46a780 (LWP 1875))] Thread 8 (Thread 0x7f839a423700 (LWP 1876)): #0 0x7fff8b9ff827 in clock_gettime () #1 0x7f83b438215d in clock_gettime () from /lib/x86_64-linux-gnu/librt.so.1 #2 0x7f83bb3ce9c4 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7f83bb4a441d in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f83bb4a4763 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f83bb4a32cc in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f83bb4a3375 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f83b2494618 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f83b2494cab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f83b2494ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f83bb4a3c16 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7f83bb4742bf in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x7f83bb474548 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #13 0x7f83bb375b10 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #14 0x7f83bb4549af in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #15 0x7f83bb378aec in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #16 0x7f83b2b93e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #17 0x7f83be800cbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #18 0x in ?? () Thread 7 (Thread 0x7f83991d9700 (LWP 1877)): #0 0x7f83b2b97d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f83b84facd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7f83b84fad09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7f83b2b93e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f83be800cbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x in ?? () Thread 6 (Thread 0x7f8392811700 (LWP 1880)): #0 0x7f83b2b95ec7 in pthread_mutex_lock () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f83b24d1e21 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f83b24946eb in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f83b2494cf9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f83b24951e2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f83932fe4a6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7f83b24b8645 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f83b2b93e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f83be800cbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x in ?? () Thread 5 (Thread 0x7f838a6b8700 (LWP 2743)): #0 0x7f83b2b97d84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f83bb37904b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f83b777f0e1 in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f83b778192b in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f83b778079f in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x7f83b778082b in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #6 0x7f83bb378aec in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f83b2b93e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f83be800cbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x in ?? () Thread 4 (Thread 0x7f8393012700 (LWP 2744)): #0 0x7f83b2b97d84 in pthread_cond_wait@@GLIBC_2.3.2 () from
[plasma] [Bug 315470] Application: plasma-desktop (0.4)
https://bugs.kde.org/show_bug.cgi?id=315470 Thomas Pfeiffer colo...@autistici.org changed: What|Removed |Added CC||colo...@autistici.org Component|Plasma mobile shell |desktop Version|unspecified |4.9.4 Assignee|notm...@gmail.com |plasma-b...@kde.org Product|Active |plasma Target Milestone|unscheduled |--- --- Comment #1 from Thomas Pfeiffer colo...@autistici.org --- Changing product to Plasma since it's Plasma Desktop -- You are receiving this mail because: You are on the CC list for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
[plasma] [Bug 315470] Application: plasma-desktop (0.4)
https://bugs.kde.org/show_bug.cgi?id=315470 Thomas Pfeiffer colo...@autistici.org changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are on the CC list for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
PA on WeTab ExoPC
Hi! I haven't been following this list before, but searching the archives did not produce any hits. If the topic has been handled earlier please excuse and give me a pointer. I wonder whether it makes any sense to use PA on a WeTab and/or ExoPC? Does anybody do that and is the platform still actively developed or is that HW just stuff for the museum? I finally installed PA during the Christmas break, first on an ExoPC. After it became unusable after 2-3 days (don't remember which was the exact problem, something from the list below) I digged out a WeTab and installed it there. However, it did not go much better. Since then the devices have mainly collecting dust, because at best they could offer a hard-core debugging experience. The worst problems are: - In some phase start-up time increased drastically from the not so good but probably normal 2-3 minutes to something like 15-20 minutes. Currently both devices are in that state. From the log I spotted some D-Bus problems, not sure whether they could cause the extensive delays. - In some phase auto-suspend started to activate itself after ~3 seconds. Again this happened to both devices. After throwing the device into the corner (not physically) for a couple of times I got over it a few days later, not really sure how. - Touch is extremely unreliable at times. Probably 70% of the time it works nearly perfect or at least well, but the remaining 30% is awful. It accepts either no touch at all or at a completely random location. From the net I found that touchscreen firmware can be updated: http://wetabz.blogspot.fi/2011/03/upgrading-touchscreen-firmware-to-1006h.html Can I find out under Mer what version I have? Has anybody done the update successfully under Mer? - Connecting to WLAN with WPA has become a nightmare. Only serious fiddling with a combination of network manager and my own manual instance of wpa_supplicant were successful recently. - The power button does not work anymore. Well, systemctl poweroff is not so difficult to type, even on the virtual keyboard... I have run zypper up at at least 2 occasions, yesterday I got about 90 updated packages. But at least the 15-20 minute startup time remained unaffected (I read that others turned their devices unbootable, so probably mine was a good update...) Unfortunately I have not kept any history what got updated and when. So I guess if I don't hide the devices in the lowest layer of the electronic garbage pile soon, I should make a fresh installation. Are the repos configured in the October images still the ones to use are do I need different ones? All insights welcome! Uwe P.S. I don't expect a 100% working product, but the boot time and the touch mess are more than I am willing to tolerate. Of course if others are actively working on these issues I might contribute a bit from time to time, but mainly testing and taking logs. Realistically I don't have the time to dig really deep. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA on WeTab ExoPC
On 25.02.2013 12:13, Uwe Geuder wrote: Hi! Hi Uwe, I haven't been following this list before, but searching the archives did not produce any hits. If the topic has been handled earlier please excuse and give me a pointer. I wonder whether it makes any sense to use PA on a WeTab and/or ExoPC? Does anybody do that and is the platform still actively developed or is that HW just stuff for the museum? Well, both, in a way ;) The hardware itself is rather old and crappy, but in fact that's the hardware most of the development team uses. So if something works for us, it should work on your WeTab/ExoPC as well. I finally installed PA during the Christmas break, first on an ExoPC. After it became unusable after 2-3 days (don't remember which was the exact problem, something from the list below) I digged out a WeTab and installed it there. However, it did not go much better. Since then the devices have mainly collecting dust, because at best they could offer a hard-core debugging experience. Since the WeTab and ExoPC differ in little more than branding, the problems will always be the same with both of them. The first and most important question is: Which image did you use? Plasma Active 3? Testing? Development? The worst problems are: - In some phase start-up time increased drastically from the not so good but probably normal 2-3 minutes to something like 15-20 minutes. Currently both devices are in that state. From the log I spotted some D-Bus problems, not sure whether they could cause the extensive delays. - In some phase auto-suspend started to activate itself after ~3 seconds. Again this happened to both devices. After throwing the device into the corner (not physically) for a couple of times I got over it a few days later, not really sure how. - Touch is extremely unreliable at times. Probably 70% of the time it works nearly perfect or at least well, but the remaining 30% is awful. It accepts either no touch at all or at a completely random location. From the net I found that touchscreen firmware can be updated: http://wetabz.blogspot.fi/2011/03/upgrading-touchscreen-firmware-to-1006h.html Can I find out under Mer what version I have? Has anybody done the update successfully under Mer? - Connecting to WLAN with WPA has become a nightmare. Only serious fiddling with a combination of network manager and my own manual instance of wpa_supplicant were successful recently. - The power button does not work anymore. Well, systemctl poweroff is not so difficult to type, even on the virtual keyboard... I have run zypper up at at least 2 occasions, yesterday I got about 90 updated packages. But at least the 15-20 minute startup time remained unaffected (I read that others turned their devices unbootable, so probably mine was a good update...) Unfortunately I have not kept any history what got updated and when. So I guess if I don't hide the devices in the lowest layer of the electronic garbage pile soon, I should make a fresh installation. Are the repos configured in the October images still the ones to use are do I need different ones? All insights welcome! I'd recommend using the latest Devel image ( https://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/devel/weekly/ ) if you experience problems with the 3.0 image. The thing is: Since we don't have that many users using the stable images yet, it's rarely worth the effort to backport bug fixes to them. Therefore I think that probably Devel might currently be more stable than 3.0. I didn't experience the problems you're describing (except for the auto-suspend after a few seconds) with a freshly installed PA3 stable image on my WeTab, though, so I don't know what's causing them on your device(s). An update rendering your device unbootable is something that may happen from time to time with Devel, though, so to be on the safe side, you should always backup any critical data before doing zypper up. P.S. I don't expect a 100% working product, but the boot time and the touch mess are more than I am willing to tolerate. Of course if others are actively working on these issues I might contribute a bit from time to time, but mainly testing and taking logs. Realistically I don't have the time to dig really deep. with the problems you mentioned above, I can imagine that it's no fun using your devices at that point. Any contribution (even if it's only well-written bug reports) is always appreciated, of course. - Thomas ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA on WeTab ExoPC
Thanks Thomas for your quick reply. On 25 February 2013 14:20, Thomas Pfeiffer wrote: The hardware itself is rather old and crappy, but in fact that's the hardware most of the development team uses. So if something works for us™, it should work on your WeTab/ExoPC as well. OK, so this should not be a completely hopeless excercise. But the people in the team don't suffer from completely unusable touch some 30% of the time??? Because I have the feeling that this problem is caused by the Linux device driver at best, probably even the firmware or the hardware. Since the WeTab and ExoPC differ in little more than branding, the problems will always be the same with both of them. Yes, I know. But it makes at least the probability smaller that I just was unlucky enough to get a piece of exceptionally bad touch hardware. The first and most important question is: Which image did you use? Plasma Active 3? Testing? Development? Good question. I guess just followed the most prominent links that Google brought up and the image I still have on my PC is unumbered. Ah, md5sum matches with https://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/stable/ Is that what you call PA3? I'd recommend using the latest Devel image ( https://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/devel/weekly/ ) OK, good info, I wasn't aware that there are still weekly images produced. I somehow remembered that Eva said in here presentation in Akademy last summer that the active project phase had already ended by then. I can of course take that image. An update rendering your device unbootable is something that may happen from time to time with Devel, So do I interpret you correctly that updating from the repos configured in the weekly = devel image just give me the next week's image? (with some definition of week and plus/minus data in configuration files and plus/minus obscure differences caused by rpm updating of course) so to be on the safe side, you should always backup any critical data before doing zypper up. Understood. So far I haven't even dared to store any critical data :) Regards, Uwe ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Brainstorm: Possible niches for Plasma Active / what is needed
On Friday, February 22, 2013 14:30:47 joseph.ana...@gmail.com wrote: Plasma active, can be presented as the tablet interface to get some real work done. this is generally how we position it. key ideas include: * a task centric design in Activities * not just an app bucket * productivity applications included * a non-toy file manager, etc. -- Aaron J. Seigo signature.asc Description: This is a digitally signed message part. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: pa on nexus 7 and now?
Hi Aaron, Am 25.02.2013 17:47 schrieb Aaron J. Seigo ase...@kde.org: On Sunday, February 24, 2013 12:16:50 Daniel Kreuter wrote: How can I switch my pa3 to current master or integration without the need of building a new image? What we really need is a Nexus 7 image with the current Plasma Active packages on it that can be installed; PA3 is good, but for development the current state of things would be more useful. in-place online upgrade from an installed PA3 to current devel is not tested at this point, so i am hesitant to suggest changing the zypper repos and doing a pull .. Since I'm using multirom for all foreign os other than the internal android, a pull would be worse a try, if it breaks I can simply remove it and reinstall it (and since its quite unasable because most input fieldss loose focus when you type on the virtual keyboard this won't be such a problem. How can I get my bugfixes to my device, wouild Qt Creator 2.7 work with remote devices like it' done with Ubuntu Touch? I haven't tested it, but Qt Creator should be able to connect over ssh (when sshd is enabled, which is something that now exists in the Settings app, but that is also post-PA3 ...). the Nexus 7 images are being done by Ruediger (who i've cc'd on this email). perhaps step 1 would be to get more people helping Ruediger with that so we can get a devel based i mage available. When I even knew how to build roms for multirom, I could help in spreading pa devel images by providing this rom. But until now I didn't find a guide on how to do it (I only have a template for the multirom installer, that's all) So long -- Aaron J. Seigo ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: pa on nexus 7 and now?
I did an over the network update after switching the repos from testing to devel. The result however wasn't very functional. Many applications segfault, and the whole thing is barely working. See the comments to this post http://aseigo.blogspot.com/2013/01/plasma-active-stable-devel-and-bleeding.htmlabout details on switching the repositories. Regards, Hillel. On Mon, Feb 25, 2013 at 12:29 PM, Daniel Kreuter daniel.kreute...@gmail.com wrote: Hi Aaron, Am 25.02.2013 17:47 schrieb Aaron J. Seigo ase...@kde.org: On Sunday, February 24, 2013 12:16:50 Daniel Kreuter wrote: How can I switch my pa3 to current master or integration without the need of building a new image? What we really need is a Nexus 7 image with the current Plasma Active packages on it that can be installed; PA3 is good, but for development the current state of things would be more useful. in-place online upgrade from an installed PA3 to current devel is not tested at this point, so i am hesitant to suggest changing the zypper repos and doing a pull .. Since I'm using multirom for all foreign os other than the internal android, a pull would be worse a try, if it breaks I can simply remove it and reinstall it (and since its quite unasable because most input fieldss loose focus when you type on the virtual keyboard this won't be such a problem. How can I get my bugfixes to my device, wouild Qt Creator 2.7 work with remote devices like it' done with Ubuntu Touch? I haven't tested it, but Qt Creator should be able to connect over ssh (when sshd is enabled, which is something that now exists in the Settings app, but that is also post-PA3 ...). the Nexus 7 images are being done by Ruediger (who i've cc'd on this email). perhaps step 1 would be to get more people helping Ruediger with that so we can get a devel based i mage available. When I even knew how to build roms for multirom, I could help in spreading pa devel images by providing this rom. But until now I didn't find a guide on how to do it (I only have a template for the multirom installer, that's all) So long -- Aaron J. Seigo ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
