| *** zbenjamin_ is now known as zbenjamin | 02:25 | |
| dcaliste_ | Hello chriadam, sorry for the disconnection yesterday, power supply issues in the building. | 07:44 |
|---|---|---|
| chriadam | dcaliste_: no problem :-) | 07:45 |
| dcaliste_ | Thanks, I'm looking at rebasing and checking MR!17 | 07:46 |
| Mister_Magister | Hmmm Someone has suggestions on how to make notch support? i changed height and y: in ApplicationWindow.qml and apps are fine but gui is one of a hell broken | 08:01 |
| Mister_Magister | i need to change it on higher level | 08:01 |
| Mister_Magister | or change some lipstick components like top menu or home screen | 08:03 |
| r0kk3rz | squish the wayland window dimensions? | 08:06 |
| Mister_Magister | r0kk3rz: i was thinking of leaving indicator icons in notch area | 08:06 |
| r0kk3rz | then yes, change th homescreen qml | 08:07 |
| Mister_Magister | when i change applicationWindow apps are fine but app drawer and lockscreen and top menu aren't ;-; | 08:07 |
| Konsieur | Hey all, all the virtual keyboards (including number keypads) on my Jolla C were borked after I updated OKBoard on a pre 3.0 SFOS version (using Storeman). The keyboards did not show up and froze the applications when I tapped in the text field. | 08:59 |
| Konsieur | Therefore I uninstalled OKBoard using devel-su pkcon remov okboard-full. | 08:59 |
| Konsieur | And now I just have a white screen when booting my Jolla C after the SFOS splash screen. I believe the white screen appears when I'm supposed to type the device lock code, or maybe the SIM code. Any ideas? | 09:00 |
| Konsieur | I can try to get into recovery mode but I'm not sure what to do next. | 09:00 |
| chriadam | Konsieur: do you have developer mode enabled, i.e. can you ssh in? | 09:01 |
| Mister_Magister | white screen would mean that qml broke | 09:01 |
| Konsieur | It is enabled but unfortunately the device was turned off with Wifi OFF and USB mode set as "Pick when USB is plugged in" | 09:01 |
| Konsieur | So I can't SSH without interacting with the phone chriadam :( | 09:01 |
| chriadam | unfortunate. perhaps pketo would have some suggestion? otherwise, recovery mode is looking like the best bet. | 09:03 |
| Konsieur | Yeah Mister_Magister, the symptom kinda reminded me of my first mistakes with Patchmanager. But that time I didn't mess with Patchmanager. I was merely using the Jolla C without installing anything, patiently waiting for the Pro1 to be delivered | 09:03 |
| Konsieur | That's also the reason why I didn't take the risk to upgrade SFOS, it was just a backup phone until delivery | 09:03 |
| Mister_Magister | oh pro1 user interesting | 09:04 |
| Mister_Magister | Konsieur: try booting with usb in | 09:05 |
| Mister_Magister | it should give you usb connection | 09:05 |
| Mister_Magister | maybe | 09:05 |
| Mister_Magister | at least ports od | 09:05 |
| Mister_Magister | do* | 09:05 |
| Konsieur | Nope it didn't, but not sure if it's because USB is set as "Pick mode when plugged in" or because I have a device lock | 09:06 |
| Mister_Magister | huh | 09:06 |
| Konsieur | And yeah future Pro1 user with the port Mister_Magister, I intend to install it asap and report what I can on Github | 09:06 |
| Mister_Magister | suuure | 09:06 |
| * Mister_Magister runs | 09:06 | |
| Konsieur | :> | 09:06 |
| pketo | yeah, recovery it is if you can't ssh in.... not sure what you should do in recovery.... probaly enable persistent journal then reboot, reboot back to recovery and check the logs where the problem is | 09:07 |
| chriadam | most likely the custom keyboard package broke something in silica | 09:07 |
| chriadam | good news is that it's most likely a .qml (i.e. text, human readable) file which can be edited to fix the issue | 09:08 |
| Mister_Magister | yeah | 09:08 |
| Konsieur | Yeah, the problem complicating things is I don't have internet connection when in Recovery mode | 09:08 |
| Konsieur | And can't fix things by forcing updates/reinstalls | 09:09 |
| Mister_Magister | Konsieur: that can be done tbh | 09:09 |
| chriadam | shouldn't need internet connection. as pketo said, you just enable persistent journal, reboot, then reboot back into recovery mode to read the journal to see what the error was. then fix the .qml file which caused the error (should be mentioned in the journal) | 09:11 |
| Konsieur | Meh, but I see that neither pkcon or zypper are available in the recovery shell anyway | 09:11 |
| Konsieur | Alright, I'll try that. Do you know the command line to enable persistent journal? | 09:12 |
| pketo | Konsieur: you need to chroot to the actual rootfs to use rpm or anything like that | 09:12 |
| Konsieur | (Found out that I need to chroot /rootfs to get zypper) | 09:12 |
| Konsieur | Exactly | 09:13 |
| pketo | to enable persisten journal you need to edit /etc/systemd/journald.conf | 09:13 |
| pketo | set storage=persistent | 09:14 |
| Konsieur | Done, thanks, I'll reboot now | 09:14 |
| Konsieur | Many errors (it's an old unused device, probably left it in a bad state or used it to fiddle around some years ago) | 09:20 |
| Konsieur | But there indeed is a "Nov 27 08:27:22 Sailfish systemd[1063]: Failed to start The lipstick UI. | 09:20 |
| Konsieur | " which seems to concur with the qml issue | 09:20 |
| chriadam | no error mentioning specific .qml file? | 09:22 |
| Konsieur | I'll try to grep on .qml | 09:22 |
| chriadam | if nothing, what does `systemctl --user status lipstick` say - could be blocked on a dependency | 09:23 |
| Konsieur | It says 'Failed to get D-Bus connection: Operation not permitted" but I'm root | 09:23 |
| Konsieur | And here is the grep on .qml: https://hastebin.com/avupuwetuw | 09:24 |
| chriadam | yeeks. libsailfishsilicaplugin.so is not providing needed symbol | 09:25 |
| chriadam | unfortunately that's not fixable with a text editor | 09:25 |
| Konsieur | Any way it could happen with just upgrading and then removing OKBoard? I mean Patchmanager is installed on the phone, but I have not used it in months | 09:26 |
| chriadam | no idea what okboard provides or does. seems unlikely, though.. | 09:26 |
| *** flx_ is now known as flux | 09:27 | |
| Konsieur | Would there be a way maybe to use the commandline to do the following: | 09:29 |
| Konsieur | - Remove the devicelock (I know the code) | 09:29 |
| chriadam | is libnemothumbnailer installed? | 09:29 |
| Konsieur | - Select USB mode as Developper mode automatically | 09:29 |
| Konsieur | So that I can boot normally, plug USB, ssh in and reinstall Silica? | 09:30 |
| chriadam | I don't know much about devicelock unfortunately. denexter has gone home for the night, otherwise I would ask him. | 09:30 |
| chriadam | if you ping me tomorrow, I can follow up | 09:30 |
| Konsieur | Not sure how to check if libnemothumbnailer is installed. | 09:31 |
| Konsieur | There is a /usr/share/lipstick/devicelock/devicelock_settings.conf file I could perhaps edit to disable the devicelock at boot | 09:33 |
| chriadam | does /usr/lib/libnemothumbnailer-qt5.so exist? | 09:33 |
| Konsieur | But I'm struggling to identify which option would do it | 09:33 |
| chriadam | possibly? I don't know anything about devicelock unfortunately | 09:33 |
| chriadam | and any change could permanently brick the device, really | 09:33 |
| Konsieur | /usr/lib/libnemothumbnailer-qt5.so.1 exists | 09:34 |
| chriadam | ok, so it is installed. that's not the issue then.. | 09:34 |
| chriadam | hrm. | 09:34 |
| Mister_Magister | maybe pkcon removed smth | 09:34 |
| Konsieur | Yep, unfortunately I don't see any option to show pkcon history | 09:35 |
| Konsieur | I could check what it did when uninstalling okboard-full yesterday | 09:35 |
| Mister_Magister | i don't use pkcon, zypper ftw you can actually see what it's doing | 09:36 |
| Konsieur | I use them interchangeably but I guess I should have preferred zypper last night | 09:37 |
| chriadam | I have to head off unfortunately - good luck | 09:37 |
| Konsieur | Any way to just fully reinstall Silica if I can get Internet connection in the recovery shell? | 09:37 |
| Konsieur | (Using this for instance https://together.jolla.com/question/22079/howto-all-computer-users-recover-or-reset-a-device-that-is-stuck-in-boot-loop/?answer=45710#post-id-45710) | 09:38 |
| chriadam | `zypper in -f sailfishsilica-qt5` should work | 09:39 |
| * chriadam -> home, gnight | 09:39 | |
| Konsieur | Ok, thanks, I'll try to get network connection in the recovery shell then | 09:40 |
| pketo | package installation/removal history is in /var/log/zypp/history | 09:43 |
| Konsieur | Nice. Here is what seems to have changed when I upgraded then removed okboard-full because it didn't work (probably because I'm on Sailfish 2.x): https://hastebin.com/uxuzibeton.rb | 09:46 |
| Konsieur | First line to show that nothing happens in several days before that | 09:46 |
| Konsieur | happened* | 09:46 |
| Konsieur | Ok so I can ping my computer from the recovery shell and I set the computer as a router, so I can ping 8.8.8.8 too from the recovery shell | 09:52 |
| Konsieur | But unfortunately I fail to add a nameserver in /etc/resolv.conf | 09:53 |
| Konsieur | I think this is the only thing missing to get proper network support | 09:53 |
| Konsieur | 'bash-3.2# echo "nameserver 8.8.8.8" >> /etc/resolv.conf' returns 'bash: /etc/resolv.conf: No such file or directory' | 09:53 |
| Konsieur | Yet /etc/resolv.conf does exist, but is empty, and sudo nano to manually add the server fails too for the same reason | 09:54 |
| Konsieur | Perhaps an issue related to chroot, since I believe /etc/resolv.conf is just a symlink? | 09:54 |
| *** vilpan is now known as Guest55245 | 10:04 | |
| *** frinring_ is now known as frinring | 10:50 | |
| *** dcaliste_ is now known as dcaliste | 10:50 | |
| Mister_Magister | by the way, piggz_'s camera ftw. Every time i take picture on x2 when i click button it looses focus and every photo is blurry while using piggz_'s camera everything is fine as it should be | 11:17 |
| Mister_Magister | we are close to redoing every jolla's app but better | 11:18 |
| *** Guest55245 is now known as vilpan | 11:40 | |
| Konsieur | I can't seem to get network working in the recovery shell. I can ping my computer and even ips of websites, but dns resolution does not work | 12:30 |
| Konsieur | Despite having 'nameserver 8.8.8.8' in /etc/resolv.conf | 12:31 |
| Konsieur | Is there something I should check? | 12:31 |
| Konsieur | Anyone with a Jolla C can tell me where is the original resolv.conf file, not the symlink in /etc/resolv.conf? | 12:44 |
| Konsieur | It seems to be /var/run/connman/resolv.conf in Jolla 1, but there is no /var/run/connman directory on my Jolla C | 12:44 |
| Konsieur | coderus perhaps you would know? Sorry to bother you, but I see that you were one of those who replied in a TJC thread about someone wanting to change his resolv.conf on Sailfish X | 12:45 |
| coderus | Konsieur: what the problem? resolv doesnt exists? check stat of /etc/resolv.conf or la -la it | 15:03 |
| Konsieur | /etc/resolv.conf existed but it was empty (in recovery mode at least, which might be expected since it is a symlink of /var/run/connman/resolv.conf, created at boot) | 15:05 |
| Konsieur | In the end I gave up and did a factory reset | 15:05 |
| Konsieur | Being in the first batch of the Pro1 would have spared this reset and potential data loss :p | 15:05 |
| Konsieur | Adding 'nameserver 8.8.8.8' in /etc/resolv.conf did not help resolving domain names anyway, so zypper was still failing to get rpms from the repos | 15:06 |
| LouisDK | Could somebody please tell me the current version number of the aliendavik package in Xperia X with SFOS 3.2? :) | 16:45 |
| r0kk3rz | would still be 4.4.4 | 21:27 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!