Ask / Submit
2

[bug] screen stays black after reboot

asked 2014-11-18 00:06:06 +0300

vbregier gravatar image

After a reboot, my screen won’t turn on.

This is not a hardware problem, since I can see the jolla logo when I switch the device on.

I can ssh into the device using wifi, so the device is on, and running.

But the screen stays off. And double tapping does nothing. Pressing the power button switches the device led between on-white and off.

Any idea ? I guess it could be the proximity sensor stuck, but I don’t know how to get out of this. Please help !

edit retag flag offensive close delete

Comments

Try dropping the battery out for a few minutes. If not, you may need to use Jolla Recovery tool.

Edz ( 2014-11-18 00:43:54 +0300 )edit

Note that I did a zypper install gdb-gdbserver qt5-qtdeclarative-plugin-qmlinspector before rebooting. It ended up upgrading some qt5 packages.

It seems the issue is with libQt5Qml, because my journalctl is filled with:

nov. 18 00:00:23 zeratul start_alien.sh[1113]: /opt/alien/system/genv/bin/alien_gps_server: symbol lookup error: /usr/lib/libQt5Qml.so.5: undefined symbol: _ZN16QLoggingCategoryD1Ev

I need ideas on either how to downgrade the packages I have upgraded, or find out which other packages I need to upgrade to keep a coherent state (isn’t that what packages dependencies are for ?)

Here is the list of packages that were upgraded: qt5-qtdeclarative qt5-qtdeclarative-import-localstorageplugin qt5-qtdeclarative-import-models2 qt5-qtdeclarative-import-particles2 qt5-qtdeclarative-import-qtquick2plugin qt5-qtdeclarative-import-window2 qt5-qtdeclarative-import-xmllistmodel qt5-qtdeclarative-qtquick qt5-qtdeclarative-qtquickparticles lipstick-jolla-home-qt5 lipstick-jolla-home-qt5-components lipstick-qt5 sailfishsilica-qt5

I have the log of zypper upgrade, but it does not tell the version of the packages prior to update.

vbregier ( 2014-11-18 01:03:22 +0300 )edit

@vbregier by doing a partial upgrade you now have a mismatch of Qt libraries and anything using them may not start. Fixing this state is complicated, are you on IRC ?

iamer ( 2014-12-23 11:48:06 +0300 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2014-12-07 21:58:34 +0300

onurati gravatar image

Check your release by typing:

ssu release

Assuming that you have not upgraded your SailfishOS version accidentally, the following command shall give you the right version for your repos:

rpm -qi sailfish-version

Now, if the output of the previous command does not match the latter, then reset your release. For example, for SailfishOS 1.0.8.21, simply type:

ssu release 1.0.8.21

Your repositiories must be configured properly again. Refresh the repositories:

pkcon refresh

You should have received the "downgraded" versions of your broken qt5 packages now. Just reinstall them, e.g. using zypper and your UI should become functional again.

Btw, in order to find out what exactly causes the problem, you can have a look at journalctl by typing e.g.:

journalctl -n 100
edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

Follow
3 followers

Stats

Asked: 2014-11-18 00:06:06 +0300

Seen: 498 times

Last updated: Dec 07 '14