~flimflam


#387 Can't open images from files menu 1 year, 11 months ago

Comment by ~flimflam on ~mil/sxmo-tickets

Yep, that was it. I still see a couple errors in the terminal but the image does display:

$ sxmo_open.sh /usr/share/sxmo/background.jpg 
stat: cannot stat '/usr/local/share/applications//*.desktop': No such file or directory
grep: /usr/local/share/applications//*.desktop: No such file or directory
grep: /home/user/.local/share/applications//*.desktop: No such file or directory

#395 Battery icon and percentage incorrect when physical keyboard connected 1 year, 11 months ago

Comment by ~flimflam on ~mil/sxmo-tickets

These versions may also be relevant, I really don't know:

  • dbus-1.12.20-r2
  • dbus-glib-0.112-r0
  • dbus-libs-1.12.20-r2
  • dbus-openrc-1.12.20-r2
  • device-mapper-2.02.187-r1
  • device-mapper-event-libs-2.02.187-r1
  • device-mapper-libs-2.02.187-r1
  • device-mapper-udev-2.02.187-r1
  • device-pine64-pinephone-0.28-r3
  • device-pine64-pinephone-nonfree-firmware-0.28-r3
  • eudev-3.2.10-r0
  • eudev-libs-3.2.10-r0
  • eudev-openrc-3.2.10-r0

#395 Battery icon and percentage incorrect when physical keyboard connected 1 year, 11 months ago

Ticket created by ~flimflam on ~mil/sxmo-tickets

I'm running sxmo on the PinePhone. When I plug it into the docking bar (one of these guys) with a keyboard attached, the battery icon changes to a filled battery icon ( I believe) regardless of the charging status and the number next to the percent symbol disappears.

I investigated a little and discovered that when the dock is plugged in another file appears at /sys/class/power_supply/hidpp_battery_0. It's type is "Battery" but it doesn't have a capacity like the one in /sys/class/power_supply/axp20x-battery. Instead, it has a file named capacity_level:

$ ls -1 /sys/class/power_supply/hidpp_battery_0/
device@
hwmon5/
power/
powers@
subsystem@
wakeup12/
capacity_level
manufacturer
model_name
online
scope
serial_number
status
type
uevent

$ cat /sys/class/power_supply/hidpp_battery_0/{capacity_level,status,type}
Normal
Discharging
Battery

If I plug the dock into a USB power supply, the contents of these files change:

$ cat /sys/class/power_supply/hidpp_battery_0/{capacity_level,status,type}
Unknown
Unknown
Battery

The usual suspects:

  • postmarketos-ui-sxmo-1.5.1-r1
  • sxmo-dwm-6.2.14-r0
  • sxmo-utils-1.5.2.1-r0

#387 Can't open images from files menu 1 year, 11 months ago

Comment by ~flimflam on ~mil/sxmo-tickets

The file is definitely there, despite the error:

$ sxmo_open.sh /usr/share/sxmo/background.jpg
/usr/bin/sxmo_open.sh: line 167: file: not found
We failed to find the mime_type for "/usr/share/sxmo/background.jpg"

$ ls /usr/share/sxmo/background.jpg
/usr/share/sxmo/background.jpg

Same thing with a png file:

$ sxmo_open.sh /usr/share/feh/images/feh.png
/usr/bin/sxmo_open.sh: line 167: file: not found
We failed to find the mime_type for "/usr/share/feh/images/feh.png"

$ ls /usr/share/feh/images/feh.png
/usr/share/feh/images/feh.png

#393 No newline inserted for new contacts 1 year, 11 months ago

Ticket created by ~flimflam on ~mil/sxmo-tickets

Steps to repro:

  1. Open system menu > Contacts > New Contact
  2. Enter name and number

Expected result: contact is added on a new line at the end of contacts.tsv

Actual result: contact is added without a new line

  • postmarketos-ui-sxmo-1.5.1-r1
  • sxmo-utils-1.5.2.1-r0

#392 Dialer menu overlaps keyboard 1 year, 11 months ago

Ticket created by ~flimflam on ~mil/sxmo-tickets

With at least 10 distinct numbers in call history, the menu overlaps the keyboard, making it impossible to enter a new number. (I suspect this is related to #241, but not a duplicate.)

  • postmarketos-ui-sxmo-1.5.1-r1
  • svkbd-0.4-r0
  • sxmo-dmenu-5.0.10-r0
  • sxmo-dwm-6.2.14-r0
  • sxmo-utils-1.5.2.1-r0

#387 Can't open images from files menu 1 year, 11 months ago

Ticket created by ~flimflam on ~mil/sxmo-tickets

I have several png images in my home directory, but nothing happens when I select them in the files menu.

I figured at first that I just needed to add the MIME types to ~/.config/mimeapps.list, but it didn't make any difference. This is what I have in that file now:

[Default Applications]
image/bmp=feh.desktop
image/gif=feh.desktop
image/jpeg=feh.desktop
image/jpg=feh.desktop
image/pjpeg=feh.desktop
image/png=feh.desktop
image/tiff=feh.desktop
image/webp=feh.desktop
image/x-bmp=feh.desktop
image/x-pcx=feh.desktop
image/x-png=feh.desktop
image/x-portable-anymap=feh.desktop
image/x-portable-bitmap=feh.desktop
image/x-portable-graymap=feh.desktop
image/x-portable-pixmap=feh.desktop
image/x-tga=feh.desktop
image/x-xbitmap=feh.desktop

I also tried specifying the full path to feh's desktop entry (/usr/share/applications/feh.desktop) and adding the same list under "[Added Associations]" at the top of ~/.config/mimeapps.list.

  • feh-3.7-r0
  • libpng-1.6.37-r1
  • postmarketos-ui-sxmo-1.5.1-r1
  • shared-mime-info-2.1-r0
  • sxmo-dmenu-5.0.10-r0
  • sxmo-utils-1.5.2.1-r0
  • xorg-server-1.20.11-r0
  • xorg-server-common-1.20.11-r0

#386 Status bar overlaps window 1 year, 11 months ago

Ticket created by ~flimflam on ~mil/sxmo-tickets

This is pretty easy to reproduce. Just open a terminal and use less to view a text file.

  • busybox-1.33.1-r3
  • busybox-extras-1.33.1-r3
  • postmarketos-ui-sxmo-1.5.1-r1
  • sxmo-dwm-6.2.14-r0
  • sxmo-st-0.8.4.1-r0
  • sxmo-utils-1.5.2.1-r0
  • xinit-1.4.1-r0
  • xorg-server-1.20.11-r0
  • xorg-server-common-1.20.11-r0
  • xprop-1.2.5-r0
  • xrandr-1.5.1-r0

#385 Terminal crash on high unicode emoji character 1 year, 11 months ago

Comment by ~flimflam on ~mil/sxmo-tickets

Here are some version numbers, lmk if you need more:

  • postmarketos-ui-sxmo-1.5.1-r1
  • sxmo-st-0.8.4.1-r0
  • sxmo-utils-1.5.2.1-r0

#385 Terminal crash on high unicode emoji character 1 year, 11 months ago

Ticket created by ~flimflam on ~mil/sxmo-tickets

I received a text from my mom with this character: https://www.utf8icons.com/character/129303/hugging-face

When I try to view the file in the terminal, either with cat, less or tail, it crashes without any visible error message.