Date & Time-setting app is a very poor design

[treebeard]

The Date & Time-setting app in the Gnome settings actually changes the date/time each time a widget is changed.  This can result in dozens of date/time changes whipsawing between past & future and creating absolute chaos with scheduled tasks.  The most recent case of this resulted in the loss of some important log info, perhaps because logrotate was so thoroughly confused.

This app should generate one date/time change and only after the user says "okay, that's it".

[wibble]

I'd say this belongs in a bug report not a forum post.

[vusra]

How does an average user create a bug report? The procedure is labyrinthine. Why don't the developers participate in this forum? The pinephone community is fractured. It needs consolidation.

[wibble]

Maybe I've just been around free software projects for too long, and it all seems obvious and easy because of that. Most projects have a public issue tracker, whether it be github, gitlab, bugzilla or similar. This is usually easy to find either directly via a web search, or by checking the project's web site or wiki for a page on how to contribute. That 'contribute' page will usually have a list of ways they can be contacted like which matrix channels or fora they use too. The first place to report an issue is usually the distro in case it's their packaging or configuration that's responsible. They may suggest reporting the issue upstream, or report it themselves. In this case it may go from mobian through phosh to gnome. A quick search for mobian issue tracker leads me to https://gitlab.com/mobian1/issues where you could create a new one.

Most of the people involved in development of the software you use on the PinePhone wouldn't consider themselves part of 'the pinephone community.' They happen to develop code that we use on the PinePhone, but most gnome developers have probably never seen a pinephone, let alone have one. Even projects that you might think of as pinephone-centric, like mobian, support a range of other devices. I'm not going to grumble if they don't want to spend their free time reading fora other than the ones they say the follow.

[treebeard]

How does an average user  create a bug report? The procedure is labyrinthine.  Why don't the developers participate in this forum?  The pinephone community is fractured.  It needs consolidation.

wibble covered it pretty well.  One frustration I keep running into is that it seems like every time I want to report a bug, I first have to create yet another account on some project's gitlab.  I don't want to keep track of so many accounts!

[vusra]

wibble covered it pretty well.  One frustration I keep running into is that it seems like every time I want to report a bug, I first have to create yet another account on some project's gitlab.  I don't want to keep track of so many accounts!

Yass!  All  free and open source projects need anonymous bug report capacity.

[KC9UDX]

You could volunteer to provide the service. That's the benefit of open source.