|
[01:20] <KGB-0> gnome-sudoku pristine-tar 40afd9c Jeremy Bicha gnome-sudoku_43.1.orig.tar.xz.delta gnome-sudoku_43.1.orig.tar.xz.id * pristine-tar data for gnome-sudoku_43.1.orig.tar.xz * https://deb.li/8JFE |
|
[01:20] <KGB-2> gnome-sudoku upstream/latest 30f6b76 Jeremy Bicha * pushed 19 commits (first 5 follow) * https://deb.li/Hxmh |
|
[01:20] <KGB-2> gnome-sudoku upstream/latest f8bb1c6 Jordi Mas po/ca.po * Update Catalan translation * https://deb.li/3SJQc |
|
[01:20] <KGB-2> gnome-sudoku upstream/latest a1d1d1e Charles Monzat help/fr/fr.po * Update French translation * https://deb.li/NDuC |
|
[01:20] <KGB-2> gnome-sudoku upstream/latest 6a89f8e Baurzhan Muftakhidinov po/kk.po * Update Kazakh translation * https://deb.li/ig8SG |
|
[01:20] <KGB-2> gnome-sudoku upstream/latest 2594e01 Sabri Ünal po/tr.po * Update Turkish translation * https://deb.li/2ZUl |
|
[01:20] <KGB-2> gnome-sudoku upstream/latest bfc6a4b Quentin PAGÈS po/oc.po * Update Occitan translation * https://deb.li/3h81I |
|
[01:28] <mybalzitch> to the individual helping me with my refresh rate issue, thank you for pointing out the 2 problems I had with my system. I removed the bad ppa, purged, and fixed my grub so I'd boot the correct and vastly newer kernel. |
|
[03:24] <duflu> mybalzitch, no problem. But did they fix the flicker? |
|
[03:27] <mybalzitch> nope. it's now different/worse. If I stay at 100hz its fine, but 120/165 I get a different kind of flickering and it's almost worse. |
|
[03:28] <mybalzitch> I was trying to get amdgpu going again, to see if they fixed it, but I'm having no luck. so I'll follow your instructions and submit another bug report |
|
[03:33] <duflu> mybalzitch, for bandwidth problems the best bet is to try a different display cable (or three). If that still doesn't fix it then you can reduce the bandwidth requirement without reducing the refresh rate using this new feature in GNOME 43: https://gitlab.gnome.org/GNOME/mutter/-/commit/03336788fb079cb8aa203e031f85d039a87832ce ($HOME/.config/monitors.xml) |
|
[03:33] -ubottu:#ubuntu-desktop- Commit 0333678 in GNOME/mutter "monitor-config-store: Add parsing support for 'maxbpc' in monitors.xml" |
|
[03:34] <mybalzitch> yeah I was using the dell supplied DP cable |
|
[03:34] <mybalzitch> I will take a look at that, thank you |
|
[03:37] <duflu> Probably equally likely is that you need a newer kernel to fix any signalling problems. You can try the latest kernel here (assuming you have secure boot disabled in the BIOS): https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.1.8/amd64/ |
|
[04:09] <mybalzitch> 6.1.8 doesn't like zfs on root (shoulda known) and the amdgpu-install I think blacklisted the default amdgpu driver because x11 won't load on boot with the hwe kernel unless I modprobe amdgpu, so I got more fixing to do in the morning. |
|
[07:09] <seb128> goood morning desktopers! |
|
[13:00] <jbicha> good morning |
|
[13:52] <KGB-0> gtk3 signed tags df641cc Jeremy Bicha ubuntu/3.24.36-2ubuntu1 * gtk+3.0 Debian release 3.24.36-2ubuntu1 * https://deb.li/3VShI |
|
[14:43] <seb128> ricotz, hey, do you have any idea maybe about https://launchpadlibrarian.net/647847075/buildlog_ubuntu-bionic-i386.thunderbird_1%3A102.7.1+build1-0ubuntu0.18.04.1_BUILDING.txt.gz ? |
|
[14:44] <seb128> > Duplicate key `lto` in table `profile.release` |
|
[14:46] <ricotz> seb128, hi, you can retry the build, it is a race only happening on i386 while patching Cargo.toml |
|
[14:49] <ricotz> seb128, do you if a merge of fontconfig 2.14.1 from debian is planned? |
|
[14:51] <seb128> ricotz, thanks, I retried once but maybe it got unlucky again, doing another retry |
|
[14:51] <seb128> ricotz, we should do it yes, nobody got assigned so far though ... are you maybe interested? ;) |
|
[14:52] <ricotz> seb128, just asking :), since libreoffice would require a patch for its test-suite |
|
[14:52] <seb128> k, I will try to maybe do it next week |
|
[14:52] <seb128> let's see if I manage to clear other items off my list first, including the thunderbird updates :) |
|
[14:53] <ricotz> seb128, okay :) |
|
[14:54] <ricotz> seb128, btw you can usually find a tarball in https://launchpad.net/~mozillateam/+archive/ubuntu/ppa/+packages (if you aren't faster) |
|
[15:10] <seb128> ricotz, yes, I noticed ... do you have automation for those? |
|
[15:18] <ricotz> seb128, no, just some simple scripts |
|
[15:26] <seb128> ricotz, ack, thanks |
|
[15:47] <seb128> ricotz, there is something weird with translations it seems, I'm testing 102.7.1 in a 22.04 VM with thunderbird-locale-fr and some of the strings are showing in english, like 'To' in the composer, where those are showing translated in the snap for the same version... |
|
[16:28] <ricotz> seb128, hmm, I seeing some untranslated strings here too on locale "de" |
|
[16:29] <seb128> :( |
|
[16:29] <seb128> I wonder if that's a side effect of the recent changes for langpacks |
|
[16:30] <seb128> the translations work in the snap and I would expect that to be the same source so to give the same results... |
|
[16:35] <ricotz> the packaging invokes the build target for language packs directly, maybe something needs to be adopted |
|
[16:35] <ricotz> although I would not expect such subtile problems, but things breaking for real |
|
[16:45] <ricotz> seb128, I think things are correct, but the revision reference in comm-esr102 isn't updated |
|
[16:45] <ricotz> I guess the upstream packaging simply uses the HEAD of comm-l10n |
|
[16:47] <ricotz> https://hg.mozilla.org/releases/comm-esr102/log/tip/mail/locales/l10n-changesets.json |
|
[16:48] <ricotz> 5b6788295358a875cf7ba9032584a069860bc032 is used and there were a lot of changes after that |
|
[17:15] <seb128> ricotz, weird, I would expect strings like 'To' to be translated since forever |
|
[17:17] <ricotz> seb128, it is not string based, but position based |
|
[17:17] <ricotz> so the translations refer to specific widgets/labels |
|
[17:43] <seb128> well, same I would expect the 'To' entry to not be something that change in the 102 serie but maybe that's naive from me |
|
[17:44] <seb128> so any idea if 1- that's a regression due to the recent changes to our packaging script? |
|
[17:44] <seb128> 2- how we fix that in the deb? |
|
[17:47] <ricotz> seb128, it is caused by the upstream switch to a single repo for translations |
|
[17:47] <ricotz> upstream should update the revision in l10n-changesets.json |
|
[17:48] <ricotz> if we would use the HEAD of comm-l10n the translations generation won't be stable |
|
[17:48] <ricotz> oops, translations/tarball |
|
[17:54] <seb128> I wonder why it works in the snap |
|
[17:55] <seb128> do you know who to raise that with upstream? |
|
[17:55] <seb128> I wonder if that's worth blocking the current updates until we get the issue resolved |
|
[17:58] <ricotz> seb128, maybe lis_syx can help with upstream? |
|
[17:59] <ricotz> hardcoding the latest l10n revision and regenerate the tarball as "*+build1.1" would be an option |
|
[18:09] <ricotz> seb128, I am going to push a repack to the mozillateam ppa for lunar |
|
[18:51] <ricotz> seb128, https://launchpad.net/~mozillateam/+archive/ubuntu/ppa/+sourcepub/14460889/+listing-archive-extra |
|
[19:18] <KGB-0> gnome-terminal signed tags dcb7844 Gunnar Hjalmarsson ubuntu/3.46.7-1ubuntu2 * gnome-terminal Debian release 3.46.7-1ubuntu2 * https://deb.li/3ivIE |
|
[21:55] <seb128> ricotz[m], thanks |
|
|