QT5.4: Sdcard not shown in ciborium app

Bug #1418544 reported by Dave Morley
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ciborium (Ubuntu)
Fix Released
Undecided
Albert Astals Cid

Bug Description

STEPS:
1. Install latest vivid on krillin
2. citrain silo 5 onto the device
3. Open the External drives app

EXPECTED:
I expect to see the sdcard and some options to remove and format it

ACTUAL:
The app just has a blank page.

More information about using Qt 5.4 (targeted before Feature Freeze Feb 19) at https://wiki.ubuntu.com/Touch/QtTesting

Related branches

Dave Morley (davmor2)
tags: added: qa-manual-teating qt5.4
description: updated
Revision history for this message
Albert Astals Cid (aacid) wrote :

I don't think it'sa blank page, i think it is actually crashing, if you let it open for a while, you'll see it disappear and if you start it from the command line it crashes.

Revision history for this message
Albert Astals Cid (aacid) wrote :

I tried to debug why/where it's crashing but it being go-based i can't get gdb or valgrind to tell me anything interesting.

Revision history for this message
Albert Astals Cid (aacid) wrote :

Installing dbg for libc we get

#0 0xffffffff in strlen () at ../ports/sysdeps/arm/armv6t2/strlen.S:85
#1 0x000485ec in internalLogHandler(QtMsgType, QMessageLogContext const&, QString const&) ()
#2 0xffffffff in () at /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#3 0xffffffff in QMessageLogger::warning(char const*, ...) const () at /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#4 0xffffffff in QObject::startTimer(int, Qt::TimerType) () at /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#5 0xffffffff in QTimer::start() () at /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#6 0xffffffff in MInputContext::hideInputPanel() () at /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforminputcontexts/libmaliitphabletplatforminputcontextplugin.so
#7 0xffffffff in () at /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqpa-ubuntumirclient.so
#8 0xffffffff in () at /usr/lib/arm-linux-gnueabihf/libmirclient.so.8
#9 0xffffffff in () at /usr/lib/arm-linux-gnueabihf/libmirclient.so.8
#10 0xffffffff in () at /usr/lib/arm-linux-gnueabihf/libmirclient.so.8
#11 0xffffffff in () at /usr/lib/arm-linux-gnueabihf/libmirclient.so.8
#12 0xffffffff in () at /usr/lib/arm-linux-gnueabihf/libmirclient.so.8
#13 0xffffffff in () at /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#14 0xffffffff in start_thread (arg=0xb0489440) at pthread_create.c:311
#15 0xffffffff in () at ../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:92

And commenting all the code in internalLogHandler makes the crash go away, need to find out how to fix it next

Changed in ciborium (Ubuntu):
assignee: nobody → Albert Astals Cid (aacid)
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ciborium - 0.2.12+15.04.20150212-0ubuntu1

---------------
ciborium (0.2.12+15.04.20150212-0ubuntu1) vivid; urgency=medium

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Albert Astals Cid ]
  * Fix crash if context.file is null (LP: #1418544)

  [ Manuel de la Pena ]
  * Ensure that we remount the drives after we format them. Remove
    deadlocks.
 -- Ubuntu daily release <email address hidden> Thu, 12 Feb 2015 16:02:52 +0000

Changed in ciborium (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.