[Debian-on-mobile-maintainers] Bug#1040404: Bug#1040404: gnome-calls: First call after boot blanks screen; can't access call controls
Guido Günther
agx at sigxcpu.org
Wed Jul 5 15:58:38 BST 2023
Hi,
On Wed, Jul 05, 2023 at 10:36:47AM -0400, John Sullivan wrote:
> Package: gnome-calls
> Version: 44~alpha.1-1
> Severity: normal
>
> This is on a PinePhone, with the Phosh environment.
>
> Consistently, after a fresh boot, when I make a call, the screen goes
> blank. Hitting the lock button, which would normally un-blank the
> screen in some way (either by bringing up the PIN unlock screen, or by
> showing the active application), does nothing. Hitting the volume
> up/down buttons does show the expected volume adjustment pop-up.
I assume with the "lock button" you mean the (hardware) power button?
Calls itself doesn't do any blanking itself. The shell usually does.
E.g. phosh does this *based* on what gnome-calls exposes on DBus *and*
the state of the proximity sensor (also read from iio-sensor-proxy via
DBus).
So the thing to check on your device is what exposes incorrect results
or if the shell interprets them the wrong way.
>From what you write it looks as if your shell assumes the proximity
sensor is on as soon as the first call starts so I'd start debugging
there (e.g. in the case of phosh by using
`G_MESSAGES_DEBUG=phosh-proximity`).
Cheers,
-- Guido
>
> I can have the call as normal, but with the screen blank, I have no way to hang up, or to navigate menus by pressing dialpad numbers. My only workaround so far for ending the call is ssh'ing into the device
> and killing gnome-calls.
>
> Once the first call is complete, if I make a second call, it functions as normal -- the screen does not go blank immediately. When it does go blank, pressing the lock button brings up the call controls.
>
> This is 100% reproducible for me by just doing:
>
> 1) Reboot the phone
> 2) Place a call to any number or contact
> 3) Screen will go blank irrecoverably until gnome-calls is killed or other side ends call
> 4) After call, place another call
> 5) It works as expected, as do all subsequent calls, until the next boot
>
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: arm64 (aarch64)
>
> Kernel: Linux 6.1-sunxi64 (SMP w/4 CPU threads)
> Kernel taint flags: TAINT_CRAP, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages gnome-calls depends on:
> ii dconf-gsettings-backend [gsettings-backe 0.40.0-4
> nd]
> ii gstreamer1.0-plugins-bad 1.22.3-2
> ii gstreamer1.0-plugins-good 1.22.4-1
> ii libc6 2.36-9
> ii libcallaudio-0-1 0.1.9-1
> ii libebook-contacts-1.2-4 3.48.4-1
> ii libfeedback-0.0-0 0.2.0-2
> ii libfolks26 0.15.6-1
> ii libgee-0.8-2 0.20.6-1
> ii libglib2.0-0 2.74.6-2
> ii libgom-1.0-0 0.4-1
> ii libgstreamer1.0-0 1.22.3-2
> ii libgtk-3-0 3.24.37-2mobian2
> ii libhandy-1-0 1.8.2-2
> ii libmm-glib0 1.20.6-2
> ii libpeas-1.0-0 1.34.0-1+b1
> ii libsecret-1-0 0.20.5-3
> ii libsofia-sip-ua-glib3 1.12.11+20110422.1+1e14eea~dfsg-6
> ii libsofia-sip-ua0 1.12.11+20110422.1+1e14eea~dfsg-6
> ii modemmanager 1.20.6-2
>
> Versions of packages gnome-calls recommends:
> ii callaudiod 0.1.9-1
> ii gnome-contacts 43.1-1mobian1
>
> gnome-calls suggests no packages.
>
> -- no debconf information
>
> _______________________________________________
> Debian-on-mobile-maintainers mailing list
> Debian-on-mobile-maintainers at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers
>
More information about the Debian-on-mobile-maintainers
mailing list