[01:50] <arraybolt3> How would I report a bug that I believe is likely in the Firefox Snap, but not in Firefox itself and not in snapd? I'm experiencing some odd behavior of the mouse cursor when using Firefox on Lubuntu Kinetic Beta (it's rendering as a standard X cursor rather than as the themed cursor that Lubuntu uses or even the white cursor that was being used before).
[01:50] <arraybolt3> I don't think it should be reported against snapd, nor do I believe Mozilla can do anything about it, but I know reporting it against Firefox is likely to be deflected towards Mozilla.
[02:41] <Eickmeyer> arraybolt3: That sounds to me like a bug against the gtk-common-themes snap. The cursor theme might not be included in the snap.
[02:41] <arraybolt3> Eickmeyer: Thanks!
[02:42] <arraybolt3> Maybe Lubuntu just isn't seeding it?
[02:43] <Eickmeyer> arraybolt3: If that were the case, then the Lubuntu image would fail.
[02:43] <arraybolt3> Hmm. Then I wonder why the cursor renders properly in Ubuntu Desktop (or does it? Maybe it doesn't, I should check).
[02:44] <arraybolt3> (It rendered properly last I looked, but I haven't looked in a while.)
[02:45] <Eickmeyer> Because the theme is included in the gtk-common-themes snap. The cursor theme for Lubuntu, i'd venture, is not.
[02:46] <arraybolt3> Oh... that makes sense to me. OK, I'll make sure I can reproduce, then report a bug. How does one report a bug against a Snap?
[02:46] <arraybolt3> Same procedure as for apt packages?
[02:46] <Eickmeyer> "snap info gtk-common-themes" will tell you what you need to know.
[02:46] <arraybolt3> +1
[07:58] <gioele> hi, I have a patch for ubuntu-dev-tools to fix a bug related to Debian/sid. What is the preferred way to submit that patch? A bug report on bugs.debian.org?
[08:49] <tjaalton> I have a snap that says 'can't open blockdev' and is preventing the system from booting up
[08:49] <tjaalton> how to fix that?
[09:06] <tjaalton> hmm, with older kernel booted up
[09:06] <tjaalton> +it
[09:08] <tjaalton> but gnome-characters snap still complains
[09:24] <tumbleweed> gioele: ubuntu-dev-tools is maintained in git: https://code.launchpad.net/ubuntu-dev-tools . So file, a merge proposal there. Patches in the BTS obviously work too
[09:29] <Unit193> https://bugs.debian.org/1020901
[09:31] <gioele> tumbleweed: too late :) The Vcs-Browse header points to https://git.launchpad.net/ubuntu-dev-tools so I assumed that it was a bare git repo outside of LP
[09:35] <Unit193> I have https://git.unit193.net/cgit/users/unit193/ubuntu-dev-tools.git/commit/?id=acc92cb3b611635d04dcc288a21769cd116d593c :3
[09:40] <tumbleweed> gioele: committed
[09:43] <gioele> tumbleweed: what? really? unexpectedly quick :) Thanks
[09:46] <gioele> is a release in sight? (asking because the failing autopkgtest blocks lsb-release(-minimal)'s migration to testing)
[13:17] <jdstrand> bigon: oh gosh, I haven't done anything with that in 10 years :) I am not a nut user any more. I can say that the script came from here: https://git.launchpad.net/qa-regression-testing/log/scripts/test-nut.py (probably adapted). My last commit was 2013, but there have been patches from other team members since then, esp for python3.