El 2022-07-30 a las 16:09 +0200, Paul Gevers escribió:
> Control: tags -1 moreinfo unreproducible
>
> Hi Camaleón,
>
> On 30-07-2022 10:10, Camaleón wrote:
> > When openning Liferea it logs these lines under /var/log/mesages, dmesg,
> > journatlctl:
> >
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 1 0x7fea3c64a34f
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 2 0x7fea3c4ff9ba
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 3 0x7fea3c7c7e8b
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 4 0x7fea3c7c817a
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 5 0x7fea3c7c845a
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 6 0x7fea3adcbd30
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 7 0x7fea3ae2cc66
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 8 0x7fea3ae2c0da
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 9 0x7fea3789dd6f
> > g_main_context_dispatch
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 10 0x7fea3789e118
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 11 0x7fea3789e40b
> > g_main_loop_run
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 12 0x7fea3ae2c6b6
> > WTF::RunLoop::run()
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 13 0x7fea3c79bff6
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 14 0x7fea3728cd0a
> > __libc_start_main
> > Jul 29 18:02:51 stt008 WebKitNetworkProcess[26567]: 15 0x40106a
> >
> > Note sure if this ir normal or expected, but to my eyes looks like a
> > trace or some kind of error.
>
> It looks wrong indeed, but it also doesn't happen on my system.
Try by setting «Open links in Lifea's window» and click on a feed to
load. This way I always get the above mesages.
> > I experience no visible/noticeable errors on the application and this
> > log is also visible on Debian tetsing.
>
> Is there anything special on you system? You say it also visible on Debian
> testing, does that mean you experience it on two systems?
Nothing special, I think.
Yes, the messages are visible in Debian Bullseye (installed on my main
system) and also in Debian testing (installed on a netbook I use for
tetsing purposes).
> Can you maybe try to start liferea from the command line and see if you can
> capture more of the output and the context? If that works, it might be good
> if we can try to get a backtrace, but honestly I don't have much experience
> there so we'd need to figure out how to do that.
1. On Debian testing:
testing@netbook:~$ liferea
libGL error: MESA-LOADER: failed to open i915:
/usr/lib/dri/i915_dri.so: no se puede abrir el fichero del objeto
compartido: No existe el fichero o el directorio (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix
_dri)
libGL error: failed to load driver: i915
The file DOES NOT exist in this system.
On testing I can reproduce the messages when I set to use Liferea's
browser and click a feed to open.
2. On Debian stable:
sm01@stt008:~$ liferea
(liferea:11886): dbind-WARNING **: 18:09:49.038: AT-SPI: Error
retrieving accessibility bus address:
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was
not provided by any .service files
Could not determine the accessibility bus address
(liferea:11886): Gtk-CRITICAL **: 18:09:51.101:
gtk_tree_model_filter_get_path: assertion 'GTK_TREE_MODEL_FILTER
(model)->priv->stamp == iter->stamp' failed
sys:1: Warning: g_hash_table_insert_internal: assertion 'hash_table !=
NULL' failed
sys:1: Warning: g_hash_table_lookup: assertion 'hash_table != NULL'
failed
Here the messages are logged everytime I click on a feed, despite the
feeds opens in Firefox (external browser) or Liferea's internal browser.
What seems triggering the messages is cliking on the feeds and load the
full page.
Not sure if this helps. Should you need more info kindy ask.
Greetings,
--
Camaleón
