Bug#1070457: dino-im: FTBFS: error: ‘struct _gpgme_key’ has no member named ‘subkeys_length1’
I found this bug at upstream project: Dino 0.4.3 fails to compile after Vala-c update to 0.56.17 https://github.com/dino/dino/issues/1576 -- Stefan
Bug#1032655: psi-plus segfaults
On Fri, Mar 10, 2023 at 03:45:38PM +0100, Lee Garrett wrote: > psi-plus currently simply segfaults on a stock bookworm installation: > > $ psi-plus > [20230310 15:43:12] W:libpng warning: iCCP: known incorrect sRGB profile > (unknown:0, unknown) > [20230310 15:43:12] W:libpng warning: iCCP: known incorrect sRGB profile > (unknown:0, unknown) > [20230310 15:43:12] W:libpng warning: iCCP: known incorrect sRGB profile > (unknown:0, unknown) > [20230310 15:43:12] W:libpng warning: iCCP: known incorrect sRGB profile > (unknown:0, unknown) > Segmentation fault On my bookworm system, I also get libpng warnings, but no segfault. Maybe a backtrace in gdb can help to get more information.
Bug#1011684: t4kcommon: FTBFS: t4k_menu.c:1264:6: error: conflicting types for ‘set_font_size’; have ‘void(_Bool)’
Control: owner -1 ! Control: tags -1 + patch The problem is the declaration of function set_font_size. I added the bool parameter to the declaration. -voidset_font_size(); +voidset_font_size(bool); See attached patch file for more information. Index: b/src/t4k_menu.c === --- a/src/t4k_menu.c +++ b/src/t4k_menu.c @@ -151,7 +151,7 @@ SDL_Surface** render_buttons(MenuNode* char* find_title_length(MenuNode* menu, int* length); char* find_longest_text(MenuNode* menu, int* length); int find_longest_menu_page(MenuNode* menu); -voidset_font_size(); +voidset_font_size(bool); voidprerender_menu(MenuNode* menu); int min(int a, int b); int max(int a, int b);
Bug#930991: gajim in Debian stretch does not start anymore
Control: severity -1 normal Hello, there was no feedback on this bugreport. I will set the severity to normal, because: * I was not able to reproduce this bug * The bug is reported on o-o-stable * There was no feedback See: https://www.debian.org/Bugs/Developer.en#severities -- Stefan Kropp
Bug#1006966: gajim: Gajim won't start due to gajim.c.storage.cache error
Control: severity -1 important Hello Leandro, I will reduce the severity from grave to important. I'm using 1.3.3-1~bpo11+1 on my laptop and it's working. I also checked where the cache.db is stored. file ~/.cache/gajim/cache.db says: SQLite 3.x database, user version 6, last written using SQLite version 3034001 Anyway, I'm not sure if this is the reason of the problem or not. It's just a guess. I will try to check with upstream. -- Stefan
Bug#1006966: gajim: Gajim won't start due to gajim.c.storage.cache error
Hello, I just found this issue note on upstream project: https://dev.gajim.org/gajim/gajim/-/issues/10779#note_204952 It's sounds quite similar. Maybe a corrupted internal gajim db-file. -- Stefan
