ppascher

Results 31 comments of ppascher

In case anyone else runs into this and is able to make sense of it here is another gpuvis screenshot of a trace with gamescope events logged while stuttering: ![20211017-221126_gpuvis](https://user-images.githubusercontent.com/10400581/137643486-3b4951ca-d200-464f-8c43-41dca457f06e.png)...

some more information: starting steam via gamescope (either from within sway or directly from tty with `/usr/local/bin/gamescope -e -f -- steam -tenfoot -steamos -fulldesktopres` and then a steam game does...

@Plagman Sorry, did not get a notification and just now saw your reply. I just tested with kernel 5.15.11, mesa, wlroots, gamescope git master as of today and still run...

I have this issue as well (with a different game though) since about a month (steam beta channel). I used to have this issue a couple of years ago (see...

Probably related and matches my experienced timeframe with the beta client: https://github.com/ValveSoftware/steam-for-linux/issues/11446

I added the comment above to an existing though closed nextcloud issue. [Someone mentioned](https://github.com/nextcloud/desktop/issues/4715#issuecomment-1311993870) to check the keepassxc bugtracker. As I was not able to find an open or closed...

regression bisected to ``` git bisect bad e2bf537c4acaa689f60a76ab09c01d2a62ce2d43 is the first bad commit commit e2bf537c4acaa689f60a76ab09c01d2a62ce2d43 Author: Aetf Date: Sat May 7 01:50:25 2022 -0400 FdoSecrets: ask to unlock the database...

> @ppascher, it looks like nextcloud fails to find an existing entry, but there are a few things I'd like to confirm: > > * is the database already unlocked...

With KPXC 2.7.1 at least I can restart nextcloud (or both keepassxc and nextcloud) and I do not get any new request access dialog after having allowed it once before...

If I comment out/remove line 236 in `./src/fdosecrets/objects/Prompt.cpp` `connect(c, &Collection::doneUnlockCollection, this, &UnlockPrompt::collectionUnlockFinished);` (or move it to after `c->doUnlock();` everything works fine again as with 2.7.1 Not sure if the intended...