Reply
Thread Tools
peterleinchen's Avatar
Posts: 4,117 | Thanked: 8,901 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#11
Hmm?
Do you talk about different files affected with ONE patch?
Then I assume patchmanager to be so intelligent to notice that and say 'cannot apply'.
Otherwise: different files affected with different patches. I do not see how that could cause a BANG
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
 

The Following 2 Users Say Thank You to peterleinchen For This Useful Post:
Posts: 539 | Thanked: 518 times | Joined on May 2010 @ nanaurbusiness
#12
Originally Posted by juiceme View Post
When patching multiple files, patches may apply cleanly to some and not ot others, so you end up in situation where couple of QML's are patched and couple are not... -> bang
Cannot happen.
One single mismatch even in a set of *.qml's to patch prevents patchmanager from applying anything.

But you can always check whats wrong with
Code:
patch --dry-run -p 1 -d / -i /usr/share/patchmanager/patches/your_problematic_patch/unified_diff.patch
__________________

N900 ~ $ make me a sandwich
-bash: no, make it yourself
N900 ~ $ sudo make me a sandwich
-bash: ok then...
 

The Following 4 Users Say Thank You to J4ZZ For This Useful Post:
coderus's Avatar
Posts: 6,436 | Thanked: 12,699 times | Joined on Nov 2011 @ Ängelholm, Sweden
#13
It can't happen because of patchmanager. It can happen because of installing some applications patching something in per-installation scripts automatically, like phonehook or some schturman applications.

anyway we can not get real reason now. the only way to get real reason is getting logs of lipstick when it crashed to load.
__________________
Telegram | Openrepos | GitHub | Revolut donations

Last edited by coderus; 2015-05-10 at 21:38.
 

The Following 2 Users Say Thank You to coderus For This Useful Post:
peterleinchen's Avatar
Posts: 4,117 | Thanked: 8,901 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#14
Originally Posted by coderus View Post
anyway we can not het real reason now. the only way to get real reason is getting logs of lipstick when it crashed to load.
How to?

Where located?
And still useful after restarting lots of times?
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
 

The Following User Says Thank You to peterleinchen For This Useful Post:
pichlo's Avatar
Posts: 6,445 | Thanked: 20,981 times | Joined on Sep 2012 @ UK
#15
Lipstick is known to be buggy. I got a lipstick restart numerous times, triggered simply by using the phone normally. Half of the times the restart wiped my desktop wallpaper (I got just a black background instead), but none of the restarts were as catastrophic as peterleinchen describes. And, like it or not, it always happened after installing some patch or another. I even went as far as uninstalling Patchmanaver but Jolla is pretty much unusable without some patches so I put it back on. Haven't had lipstick crashing on me for a while and if/when it happens again, I know what to do so no big deal.

All this has been reported by me and a (small) number of people more than once. No solution has been found or, as far as I am aware, even investigated. All you get back from Jolla is the usual silence. The only one who bothered to reply at all was coderus, with his usual, "works for me, problem is your device".

The fact that it affects only some of us suggests some edge condition. I have not been able to identify a specific patch that triggers it. It is as if the trigger was the mere fact that some QML files have been altered, it does not matter which one.
 

The Following 3 Users Say Thank You to pichlo For This Useful Post:
coderus's Avatar
Posts: 6,436 | Thanked: 12,699 times | Joined on Nov 2011 @ Ängelholm, Sweden
#16
Originally Posted by peterleinchen View Post
How to?

Where located?
And still useful after restarting lots of times?
journalctl -a /usr/bin/lipstick

Originally Posted by coderus View Post
anyway we can not get real reason now. the only way to get real reason is getting logs of lipstick when it crashed to load.
__________________
Telegram | Openrepos | GitHub | Revolut donations
 

The Following 3 Users Say Thank You to coderus For This Useful Post:
peterleinchen's Avatar
Posts: 4,117 | Thanked: 8,901 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#17
Originally Posted by coderus View Post
journalctl -a /usr/bin/lipstick
Unfortunately journalctl holds only info of a few hours (ca. 11.05. 20:00 - 11.05. 23:30).
So I need to provoke the crash once more and dump the journal ...
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
 

The Following 2 Users Say Thank You to peterleinchen For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 19:45.