Bug#843810: libgtk-3-0: gtk3 >= 3.21.4-1 does not show a menu in Firefox, virt-manager and probably many others
What Jason said. It's fine for me, on 3.22.2, and more info is needed in any case. Also, I suspect it's quite likely this is a duplicate of Bug#843418
Bug#824506: overlay scrollbars do not work properly
Don't. That's blaming Debian for upstream's problems, which are outwith the distro's control. Complain to the source. Then everyone who uses the upstream package benefits. Did you think that if you complain loudly enough to Debian, that its maintainers will wrangle with upstream on your behalf? They've got enough work of their own to do. On Mon, May 16, 2016 at 9:44 PM, Yuri D'Elia wrote: > On Mon, May 16 2016, Michael Biebl wrote: > >> I generally like the idea of overlay scrollbars, but somehow the current > >> implementation in GTK3 shouldn't have passed QA for basic usability. > > > > Thanks for your bug reports. Please consider filing such issues directly > > upstream [1]. Downstream is really the wrong place for this > > I will, however for some class of bugs that affect general system > usability (and the system as a whole), I also file reports downstream. > >
Bug#824841: libgtk-3-0: Properly include upstream changelog
You asked for "the upstream bug [log, presumably]", so it was reasonable for people to presume you wanted a list of bugfixes. upstream is git.gnome.org and browse for gtk+ On Fri, May 20, 2016 at 4:15 PM, Ximin Luo wrote: > Michael Biebl: > > Am 20.05.2016 um 12:15 schrieb Ximin Luo: > >> Package: libgtk-3-0 > >> Version: 3.20.4-1 > >> Severity: important > >> > >> Dear Maintainer, > >> > >> Whilst investigating a bug involving GTK themes, I found that the > contents of > >> the upstream bug is useless: > >> > >> $ zcat /usr/share/doc/libgtk-3-0/changelog.gz > >> A git checkout and git-log is required to generate this file > >> > >> Please fix this - if necessary by generating the changelog from git and > >> repacking the Debian "orig" tarball to include this generated version. > >> > >> Otherwise it makes bug tracking much harder. > > > > All bugs are mentioned in the NEWS file. > > For a complete and more detailed list, a git checkout is much, much > > better anyway. > > > > The NEWS file contains a list of bugs that have just been fixed, but > doesn't contain details of major changes that might have resulted in new > bugs. Obviously the latter is what I'm interested in - I wouldn't be trying > to read about bugs that were just fixed, since I hopefully wouldn't be > experiencing them in the first place. > > Where is the upstream git? It would be helpful to include the address of > this repository in changelog.gz, as well as the actual commands I need to > run (including its dependencies) to generate it. Saving people time really > helps to avoid user frustration, especially if upstream is prone to making > backward-incompatible changes that break everything. > > X > > -- > GPG: ed25519/56034877E1F87C35 > GPG: rsa4096/1318EFAC5FBBDBCE > git://github.com/infinity0/pubkeys.git > >
Bug#824891: gtk+3.0: latest version breaks external themes
Yup, I'm beginning to think it'd be good if Debian reverted to 3.18 until 3.20 is less broken. The latter will be great when it's ACTUALLY ready - but right now, it's a rushed-out, poorly tested mess in various areas. Maybe they felt meeting some deadline took precedence over actually testing everything. Including my application, which was going so well until 3.20 arrived... sigh On Fri, May 20, 2016 at 9:40 PM, Ximin Luo wrote: > Source: gtk+3.0 > Version: 3.20.4-1 > Severity: important > Tags: upstream > > Dear Maintainer, > > The version currently in sid breaks external themes including those > included in > gtk3-engines-breeze and gtk3-engines xfce. Downgrading back to 3.18.9-1 [1] > solves the problem. > > I've not investigated the full extent of this but attached are two > screenshots > of some of the issues. It basically makes large sections of the UI > completely > unusable. > > gedit: if using a dark theme (such as Breeze-Dark) the main text pane > background > becomes transparent, but the foreground text color remains white. > > pavucontrol and others: borders+padding around menu buttons are not shown, > and > widget elements like sliders and checkboxes are not shown either. > > I'm trying to go through the git changelog but it's massive and will take > me > quite a lot of time. Please forward this as approriate. > > X > > [1] http://snapshot.debian.org/package/gtk%2B3.0/3.18.9-1/ > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'stable'), (300, 'unstable'), (200, > 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) >
Bug#824835: tex-common: fmtutil fails
Thanks, Paul: I can confirm the below on unstable. Executing sudo aptitude install context sorted this... ...but seeing as this pulled in a whopping 365 MB of archives (and that's just the compressed version), which I might've never voluntarily installed, possibly just to get a single file that restores working updates to the wanted parts of my system... and of which apparently a full 207 MB are purely doc packages... I can't help but feel there must be a better way for upstream to handle all this. Well, that's not Debian's fault, so what can ya do. Thanks again! On Sat, 21 May 2016 11:49:31 +0200 Paul Seelig wrote: > i stumbled over the line stating: > > ! I can't find file `syst-tex.mkii'. > > Checking with apt-file, syst-tex.mkii appeared to be contained in two > packages, namely 'context' and 'texlive-latex-base'. Apparently there > was a change, as this file is no longer part of texlive-latex-base, but > only contained in context, which was not installed before on my systems. > > After adding the context package, all remaining packages configured just > fine. > > Looks as if we now also require to have context installed.
Bug#775445: License updates, music included, ready for review (I hope)
Hi, After speaking with the author of the menu music, he has licensed it under CC-BY-3.0. The latest package reflects this: http://mentors.debian.net/debian/pool/main/b/bitfighter/bitfighter_019d+dfsg-14.dsc I also replaced the 'Play' font usage with 'LiberationSans' so it isn't so ugly (because of bug #776273) I believe I am read for review again. Thank you!, David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775445: Bug #775445 - RFS: bitfighter ready for next review
Bitfighter is ready for another review. See the package here: http://mentors.debian.net/debian/pool/main/b/bitfighter/bitfighter_019d+dfsg-14.dsc Please forgive the double post. I had used poor subjects for previous e-mails. Thanks! David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#776273: Screenshots for fonts-play
Sorry about the delay, first message got caught by the debian spam filter. Here are the screenshots. Attached. Thanks, David
Bug#705303: Continue bitfighter work
Hi, I am attempting to continue the work that Bryan started for packaging bitfighter. Wish me good fortune! David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#705303: Restoration of deleted package 'bitfighter'
Hello, I am attempting to continue the work of a previous developer on packaging the game 'bitfighter'. He had previously uploaded a package here: https://mentors.debian.net/package/bitfighter However, I find that this has been deleted. Is there any possible way to restore it? He had gotten much further in packaging bitfighter, up to resolving all the lintian warnings. For reference, here is the bug that I recently switched to ITP: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705303 Thank you, David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#705303: Restoration of deleted package 'bitfighter'
Yes, it was I that had asked on IRC. Thank you very much for confirming. I asked again, but to this list, because the upstream packaging does not build as cleanly compared to what I remember there was on the mentors server (lintian had all passed). I was really hoping (but knew it was a slim chance) that the package might turn up elsewhere. I found snapshot.debian.org and was hoping some minor backup might exist for the mentors server as well. I will continue with the upstream packaging code. Thanks again! David On Wed, Jan 14, 2015 at 6:35 PM, Paul Wise wrote: > On Thu, Jan 15, 2015 at 4:23 AM, D B wrote: > > > However, I find that this has been deleted. Is there any possible way to > > restore it? > > I checked on the mentors server already (for someone else?) and found > no copies, however his packaging is present in the upstream code > repository: > > https://code.google.com/p/bitfighter/source/browse/debian > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise >
Bug#705303: back on mentors.debian.net
I have a crude package building again on mentors.debian.net: http://mentors.debian.net/package/bitfighter
Bug#775445: RFS: bitfighter/019d-2 [ITP]
Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "bitfighter" * Package name: bitfighter Version : 019d-2 Upstream Author : Chris Eykamp * URL : http://bitfighter.org/ * License : GPL-2+ Section : games It builds those binary packages: bitfighter - Fast-paced two dimensional online space shooter bitfighter-data - Resource and data files for bitfighter To access further information about this package, please visit the following URL: http://mentors.debian.net/package/bitfighter Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/b/bitfighter/bitfighter_019d-2.dsc More information about bitfighter can be obtained from http://bitfighter.org. Regards, David Buck -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#869386: on man page say what ! means
so file a bug upstream with a patch. I don't see why this should be debian's problem. Fyi, the docs seem to come from here: https://git.gnome.org/browse/gtk+/tree/docs/reference/gtk/gtk-query-settings.xml?h=gtk-3-22
Bug#869386: on man page say what ! means
On Sun, Jul 23, 2017 at 3:05 PM, D. B. wrote: > so file a bug upstream with a patch. I don't see why this should be > debian's problem. Fyi, the docs seem to come from here: > https://git.gnome.org/browse/gtk+/tree/docs/reference/gtk/ > gtk-query-settings.xml?h=gtk-3-22 > > Also, looking at the C source shows that the exclamation mark means deprecated: https://git.gnome.org/browse/gtk+/tree/gtk/gtk-query-settings.c?h=gtk-3-22#n77
Bug#847366: gtk apps die with 'Couldn't open libGL.so.1'
#2 seems like the superior option, right? On Fri, Dec 9, 2016 at 4:17 PM, Dariusz Gadomski < dariusz.gadom...@canonical.com> wrote: > Looks like this behaviour was introduced with a change to cairo > in version 1.12.16-4 [1]. So looks like gtk was depending on being > linked to libGL.so indirectly via cairo. > > So, any of the below should fix it: > 1) Re-enable GL/EGL support in cairo. > 2) Add libgl1-mesa-glx as a dependency of gtk. > 3) [upstream] Introduce runtime checks before calling GL functions. > > [1] https://anonscm.debian.org/cgit/collab-maint/cairo.git/commit/?id= > a4bad9f8463d3e1ed2ebe15890c5c52c1c29a271 > >
Bug#839122: Old GTK+ 3 Debian/Ubuntu patch causes Critical Warning every time a GtkComboBox is opened
On Fri, Dec 9, 2016 at 8:40 PM, Michael Biebl wrote: > Hi Daniel > > > I see that you've been working with upstream, trying to resolve this. > Thanks a lot for that. > The latest stable release 3.22.5, contains your patches. > > What's unclear to me is whether your patches replace the above two > patches and we can drop them now, or if we still need them (for > Ubuntu/Unity). > I've CCed William, from the Ubuntu side. Maybe you can confirm, that > those patches are safe to drop now or if they are still needed. > > Regards, > Michael > > Hi Michael, It took a while, but we got there in the end. :) I'm glad to have done my bit to help, and to get William's fix into 3.22. William's and my patches only resolve assertion failures, which were in part revealed by the Debian patches to prevent offscreen grabs: William's patch fixed an oversight in GtkCellRendererCombo, where the trigger event was not passed and failed an upstream assertion. This was forgotten for cherry-picking to 3.22, so I did that as part of merging my patch from master. My patch was for a parallel issue: some dodgy ordering of menu grab vs realise in GtkComboBox (with particular sets of properties) - which caused an assertion in Debian patch 016 to fail. So, if you want to prevent offscreen grabs, currently patches 016 and 017 seem to be still required. Near or identical patches are submitted upstream, and reviewed quite positively, but they don't seem to have gone any further than that. Maybe you'd like to request an update there? https://bugzilla.gnome.org/show_bug.cgi?id=658563 That's the thread with a reviewed patch against offscreen grabs for both widgets and devices, which AFAICT would cover both patches 016 and 017. It might be worth asking for an update, now that it wouldn't generate errors on Debian et al if merged. Cheers! Daniel
Bug#843418: menus do not appear on high-DPI display
Are you using X.org or Wayland, and which GTK+ theme?
Bug#794064: Confirmed
I get this sometimes in unstable of today, even without automatic login being enabled. Did anyone ever find a fix? This can be hugely disruptive. Sometimes messing around with the Ctrl+Alt+F1 etc works to get a working login screen, but I don't think this always works, so sometimes, the session is simply lost, which can be fatal. Cheers
Bug#847153: All combo boxes under GTK 3 render off screen
On Tue, Dec 6, 2016 at 3:53 AM, Jeffrey H. Ingber wrote: > Package: gtk+3.0 > Version: libgtk-3-0:amd64 > > All combo boxes under gtk 3 attempt to open in the very far upper-left > hand corner of the screen. Maybe you can see part of the combo box, and > maybe you can't. > > This is hardly enough info. That's not the version; they need something like 3.22. Which display server (X/Wayland), which desktop environment, etc.? When did the problem start happening?
Bug#836246: libgtk-3-0: Upgrade from 3.20.9 to 3.21.5 broke Mate desktop
On Thu, Sep 1, 2016 at 10:47 AM, Cesare Leonardi wrote: > On 01/09/2016 09:01, D. B. wrote: > >> Why did you log this against 3.20.9 if that one is fine? >> > > I reply only to the constructive part of your message. > No, you reply only to the part that doesn't reveal your entire report to be based on a flawed premise: that unstable isn't prone to breakage, and that the maintainers won't already be aware of such obvious issues and working on them. but OK.
Bug#837031: libgtk-3-0: Inconsistent double click behaviour in file chooser
As a fellow user I would request that you file this bug upstream so that GTK+ are aware of how annoying it is, if no one has already filed such a ticket (I could not find one on an extremely brief search) This annoyance is not debian specific, so why (A) burden the deb maintainers, (B) not make GTK+ aware of the annoyance, (C) exclude other distro users, etc. On Thu, Sep 8, 2016 at 12:57 AM, Fabián Inostroza wrote: > Package: libgtk-3-0 > Version: 3.21.5-3 > Severity: important > > Dear Maintainer, > > In recent versions of gtk3 the double click behaviour of the file chooser > dialog got inconsistent. > Basically sometimes, when a folder is already selected, a single click > opens that folder. > > See [1] for more information and a patch. > > [1]: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1519778 > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages libgtk-3-0 depends on: > ii adwaita-icon-theme 3.20-3 > ii hicolor-icon-theme 0.15-1 > ii libatk-bridge2.0-0 2.20.1-4 > ii libatk1.0-0 2.20.0-1 > ii libc6 2.23-5 > ii libcairo-gobject2 1.14.6-1+b1 > ii libcairo2 1.14.6-1+b1 > ii libcolord2 1.3.2-1 > ii libcups22.1.4-4 > ii libepoxy0 1.3.1-1 > ii libfontconfig1 2.11.0-6.7 > ii libfreetype62.6.3-3+b1 > ii libgdk-pixbuf2.0-0 2.34.0-1 > ii libglib2.0-02.49.6-1 > ii libgtk-3-common 3.21.5-3 > ii libjson-glib-1.0-0 1.2.2-1 > ii libpango-1.0-0 1.40.2-1 > ii libpangocairo-1.0-0 1.40.2-1 > ii libpangoft2-1.0-0 1.40.2-1 > ii librest-0.7-0 0.8.0-1 > ii libsoup2.4-12.55.90-1 > ii libwayland-client0 1.11.0-2 > ii libwayland-cursor0 1.11.0-2 > ii libwayland-egl1-mesa [libwayland-egl1] 11.2.2-1 > ii libx11-62:1.6.3-1 > ii libxcomposite1 1:0.4.4-1 > ii libxcursor1 1:1.1.14-1+b1 > ii libxdamage1 1:1.1.4-2+b1 > ii libxext62:1.3.3-1 > ii libxfixes3 1:5.0.2-1 > ii libxi6 2:1.7.6-1 > ii libxinerama12:1.1.3-1+b1 > ii libxkbcommon0 0.6.1-1 > ii libxml2 2.9.4+dfsg1-1+b1 > ii libxrandr2 2:1.5.0-1 > ii shared-mime-info1.6-1 > > Versions of packages libgtk-3-0 recommends: > ii libgtk-3-bin 3.21.5-3 > > Versions of packages libgtk-3-0 suggests: > ii gvfs 1.29.91-1 > ii librsvg2-common 2.40.16-1 > > -- no debconf information > >
Bug#837031: libgtk-3-0: Inconsistent double click behaviour in file chooser
Thanks for the links! Yes, in the interim, I wouldn't complain about a Debian specific patch. I don't know what clever thing they thought they were doing with that click behavior, but it's not clever. On Thu, Sep 8, 2016 at 2:57 AM, Fabián Inostroza wrote: > It has already been reported, I forgot to add links. I hope they fix this > problem but maybe would be faster to use the Ubuntu patch. > > https://bugzilla.gnome.org/show_bug.cgi?id=766089 > https://bugzilla.gnome.org/show_bug.cgi?id=758065 > > 2016-09-07 21:12 GMT-03:00 D. B. : > >> As a fellow user I would request that you file this bug upstream so that >> GTK+ are aware of how annoying it is, if no one has already filed such a >> ticket (I could not find one on an extremely brief search) >> >> This annoyance is not debian specific, so why (A) burden the deb >> maintainers, (B) not make GTK+ aware of the annoyance, (C) exclude other >> distro users, etc. >> >> >> On Thu, Sep 8, 2016 at 12:57 AM, Fabián Inostroza < >> soulsonceonf...@gmail.com> wrote: >> >>> Package: libgtk-3-0 >>> Version: 3.21.5-3 >>> Severity: important >>> >>> Dear Maintainer, >>> >>> In recent versions of gtk3 the double click behaviour of the file >>> chooser dialog got inconsistent. >>> Basically sometimes, when a folder is already selected, a single click >>> opens that folder. >>> >>> See [1] for more information and a patch. >>> >>> [1]: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1519778 >>> >>> -- System Information: >>> Debian Release: stretch/sid >>> APT prefers testing >>> APT policy: (500, 'testing') >>> Architecture: amd64 (x86_64) >>> Foreign Architectures: i386 >>> >>> Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) >>> Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8) >>> Shell: /bin/sh linked to /bin/dash >>> Init: systemd (via /run/systemd/system) >>> >>> Versions of packages libgtk-3-0 depends on: >>> ii adwaita-icon-theme 3.20-3 >>> ii hicolor-icon-theme 0.15-1 >>> ii libatk-bridge2.0-0 2.20.1-4 >>> ii libatk1.0-0 2.20.0-1 >>> ii libc6 2.23-5 >>> ii libcairo-gobject2 1.14.6-1+b1 >>> ii libcairo2 1.14.6-1+b1 >>> ii libcolord2 1.3.2-1 >>> ii libcups22.1.4-4 >>> ii libepoxy0 1.3.1-1 >>> ii libfontconfig1 2.11.0-6.7 >>> ii libfreetype62.6.3-3+b1 >>> ii libgdk-pixbuf2.0-0 2.34.0-1 >>> ii libglib2.0-02.49.6-1 >>> ii libgtk-3-common 3.21.5-3 >>> ii libjson-glib-1.0-0 1.2.2-1 >>> ii libpango-1.0-0 1.40.2-1 >>> ii libpangocairo-1.0-0 1.40.2-1 >>> ii libpangoft2-1.0-0 1.40.2-1 >>> ii librest-0.7-0 0.8.0-1 >>> ii libsoup2.4-12.55.90-1 >>> ii libwayland-client0 1.11.0-2 >>> ii libwayland-cursor0 1.11.0-2 >>> ii libwayland-egl1-mesa [libwayland-egl1] 11.2.2-1 >>> ii libx11-62:1.6.3-1 >>> ii libxcomposite1 1:0.4.4-1 >>> ii libxcursor1 1:1.1.14-1+b1 >>> ii libxdamage1 1:1.1.4-2+b1 >>> ii libxext62:1.3.3-1 >>> ii libxfixes3 1:5.0.2-1 >>> ii libxi6 2:1.7.6-1 >>> ii libxinerama12:1.1.3-1+b1 >>> ii libxkbcommon0 0.6.1-1 >>> ii libxml2 2.9.4+dfsg1-1+b1 >>> ii libxrandr2 2:1.5.0-1 >>> ii shared-mime-info1.6-1 >>> >>> Versions of packages libgtk-3-0 recommends: >>> ii libgtk-3-bin 3.21.5-3 >>> >>> Versions of packages libgtk-3-0 suggests: >>> ii gvfs 1.29.91-1 >>> ii librsvg2-common 2.40.16-1 >>> >>> -- no debconf information >>> >>> >> >
Bug#834457: libgtk-3-0: inconsistent signed/unsigned length parameter in gtk_builder_new_from_string() and gtk_builder_add_from_string()
Why are you reporting this here? Upstream would be happy to hear about it, but it's not Debian's problem (and nor is it serious enough to warrant a distro-specific patch) On Mon, Aug 15, 2016 at 10:51 PM, Joe Pfeiffer wrote: > Package: libgtk-3-0 > Version: 3.21.4-1 > Severity: minor > > gssize is signed, gsize is not. > > gtk_builder_new_from_string() has the prototype > > GtkBuilder * > gtk_builder_new_from_string (const gchar *string, > gssize length) > > It passes length to gtk_builder_add_from_string(), which has the > prototype > > guint > gtk_builder_add_from_string (GtkBuilder *builder, > const gchar *buffer, > gsize length, > GError **error) > > This in turn passes length to _gtk_builder_parser_parse_buffer(), with > prototype > > void > _gtk_builder_parser_parse_buffer (GtkBuilder *builder, > const gchar *filename, > const gchar *buffer, > gsize length, > gchar **requested_objs, > GError **error) > > This passes length to g_markup_parse_context_parse(), with prototype > > gboolean > g_markup_parse_context_parse (GMarkupParseContext *context, > const gchar *text, > gssizetext_len, > GError **error) > > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, > 'experimental'), (500, 'oldstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages libgtk-3-0 depends on: > ii libatk-bridge2.0-0 2.20.1-3 > ii libatk1.0-0 2.20.0-1 > ii libc6 2.23-4 > ii libcairo-gobject2 1.14.6-1+b1 > ii libcairo2 1.14.6-1+b1 > ii libcolord2 1.3.2-1 > ii libcups22.1.4-4 > ii libepoxy0 1.3.1-1 > ii libfontconfig1 2.11.0-6.5 > ii libfreetype62.6.3-3+b1 > ii libgdk-pixbuf2.0-0 2.34.0-1 > ii libglib2.0-02.49.4-1 > ii libgtk-3-common 3.21.4-1 > ii libjson-glib-1.0-0 1.2.2-1 > ii libpango-1.0-0 1.40.1-1 > ii libpangocairo-1.0-0 1.40.1-1 > ii libpangoft2-1.0-0 1.40.1-1 > ii librest-0.7-0 0.8.0-1 > ii libsoup2.4-12.54.1-1 > ii libwayland-client0 1.11.0-2 > ii libwayland-cursor0 1.11.0-2 > ii libwayland-egl1-mesa [libwayland-egl1] 11.2.2-1 > ii libx11-62:1.6.3-1 > ii libxcomposite1 1:0.4.4-1 > ii libxcursor1 1:1.1.14-1+b1 > ii libxdamage1 1:1.1.4-2+b1 > ii libxext62:1.3.3-1 > ii libxfixes3 1:5.0.2-1 > ii libxi6 2:1.7.6-1 > ii libxinerama12:1.1.3-1+b1 > ii libxkbcommon0 0.5.0-1 > ii libxml2 2.9.4+dfsg1-1+b1 > ii libxrandr2 2:1.5.0-1 > ii shared-mime-info1.6-1 > > Versions of packages libgtk-3-0 recommends: > ii libgtk-3-bin 3.20.7-1 > > Versions of packages libgtk-3-0 suggests: > ii gvfs 1.28.2-1 > ii librsvg2-common 2.40.16-1 > > -- no debconf information > >
Bug#842070: libgtk-3-0: Upgrade breaks gvim: Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >= -1' failed
With respect (and forasmuch as I love anything that promotes vim) - if some program and/or theme has managed to request <= 0 size for a widget, then it's broken GTK+, not the other way around. That said, on a quick glance at the gtk-3-22 branch, I can't see any changes in gtkwidget.c that would've broken this, but of course extra debug info may reveal that some other widget is leading to this.
Bug#832077: Info received (emacs clutter screen on windows switch)
Are you using unstable? Then you have no right to be melodramatic about people "demolishing" the distro. It's not the maintainers fault if 3rd-party software is not up to date with the libraries on which it relies. And by using unstable or testing, the user accepts the very likely possibility of temporary breakage. And there's the key word: temporary.
Bug#832301: [832391] firefox: Please reenable GTK3 support
Hello, I also second this request, for whatever it's worth. As of now with Debian unstable I don't have GTK+3 in Firefox and can see no way to install/enable it. Cheers!
Bug#832077: gvim is affected by this bug
That warning has been widely reported for countless packages and should be resolved by the app developer. Still, to keep people happy until then, it will be silenced by default in GTK+ 3.22.1 (accidentally got omitted in 3.22.0) https://git.gnome.org/browse/gtk+/commit/?id=54fdcb3ffac3383432b379f3e16e8cb0086b8101
Bug#839122: Old GTK+ 3 Debian/Ubuntu patch causes Critical Warning every time a GtkComboBox is opened
Package: gtk-3.0 Version: 3.22.0-1 Hello, The problem here is this patch: https://sources.debian.net/src/gtk%2B3.0/3.22.0-1/debian/ patches/016_no_offscreen_widgets_grabbing.patch/ although its counterpart looks similarly old and ill-substantiated: https://sources.debian.net/src/gtk%2B3.0/3.22.0-1/debian/ patches/017_no_offscreen_device_grabbing.patch/ - "The *exact* and *complete* text of any error messages printed or logged. This is very important!" Gdk-CRITICAL assertion 'GDK_IS_WINDOW (window)' failed See full report, backtraces, links to discussions of the offending patch, etc here https://bugzilla.gnome.org/show_bug.cgi?id=771242 - "Exactly what you typed or did to demonstrate the problem." Just use Debian's package of GTK+ 3.22, and try to open any ComboBox that does not have wrap-width manually set, or a CellRendererCombo. - A description of the incorrect behavior: exactly what behavior you were expecting, and what you observed. A transcript of an example session is a good way of showing this. See above at upstream Bugzilla. What I expected was not critical warning every time I open a ComboBox. What I got was just such a warning. This does not inspire confidence. - A suggested fix, or even a patch, if you have one. My suggested fix is to revert these seemingly ill-advised and ill-tested patches, please. They seemingly are not applicable to how GTK+ currently works, if they ever were. And a rationale like "seem like they should not be allowed to do grab the mouse or whatever" does not seem sufficiently substantive to justify critical warnings every time I popup a ComboBox. Thank you.
Bug#839122: Affects: libgtk-3-0
Package: libgtk-3-0 I'm still trying to figure out how this adventure game, I mean bugtracker, works - so forgive me if I seem to be spamming or failing comedically. In this case, I got the package name wrong, since the Package Tracker seems to use a different name from the Bug Tracker. Which is handy!
Bug#831977: FW: [LibreOffice Calc Bug 100841] Dragging a cell's frame to Fill Series, etc - no longer shows a tooltip indicating currently reached value
Package: libreoffice-calc Version: 5.1.4.2 and 5.1.5.1 Build ID: 1:5.1.4~rc2-2 and 1:5.1.5~rc1-1 Dear Maintainer, Tooltips are no longer shown in LibreOffice Calc when dragging to 'fill series' - and possibly in other location that use the same kind of tooltips. (Note that normal GTK+ tooltips on buttons seem to be OK.) I originally reported this upstream at https://bugs.documentfoundation.org/show_bug.cgi?id=100841 but it seems to be specific to the current Debian unstable package, at least based on 2 data points... myself and another user. As noted there, * I have tried this across GNOME, KDE, and XFCE with no differences in the missing tooltip. * the other user appears to have determined that the issue is specific to this Debian packaged version of LO, as parallel-installed 'vanilla' versions worked for them. I have not managed to try that yet, however. > Exactly what you typed or did to demonstrate the problem. * Open a new Calc document * Type a numeric 0 into a cell * Select the cell * Left-click and hold on the square handle at the cell's bottom right * Drag downwards > A description of the incorrect behavior: exactly what behavior you were expecting I expected the usual tooltip - known from my Debian stable version of LO, plus other popular office packages - to appear as I dragged down. This shows how far the series has been filled, i.e. the number which it would now reach if we release the mouse button. This is, of course, very useful. > and what you observed. What I actually observed was that this tooltip is never shown; i's missing. > A transcript of an example session is a good way of showing this. Video: https://bugs.documentfoundation.org/attachment.cgi?id=126152 > Details of the configuration of the program with the problem. Include the complete text of its configuration files. libreoffice-calc, standard unstable version, no customisations. > What kernel version you're using (type uname -a) Linux v3-771g 4.6.0-1-amd64 #1 SMP Debian 4.6.3-1 (2016-07-04) x86_64 GNU/Linux > your shared C library (type ls -l /lib/libc.so.6 or dpkg -s libc6 | grep ^Version) 2.23-1 > Appropriate details of the hardware in your system. If you're reporting a problem with a device driver please list all the hardware in your system, as problems are often caused by IRQ and I/O address conflicts. It was mentioned that some distros cite known issues with particular graphics hardware, so mind are an Intel HD Graphics 4000 + Nvidia GT650M. With the former being used most or all of the time AFAIK Also, disabling h/w acceleration etc in the LO options made no difference. > If you have reportbug installed the output of reportbug -q --template -T none -s none -S normal -b --list-cc none -q will also be useful, as it contains the output of maintainer specific scripts and version information. ...get ready... -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreoffice-calc depends on: ii coinor-libcbc3 2.8.12-1+b1 ii coinor-libcoinmp1v51.7.6+dfsg1-2 ii dpkg 1.18.9 ii libboost-filesystem1.58.0 1.58.0+dfsg-5.1 ii libboost-iostreams1.58.0 1.58.0+dfsg-5.1 ii libc6 2.23-1 ii libetonyek-0.1-1 0.1.6-2 ii libgcc11:6.1.1-9 ii libicu55 55.1-7 ii liblcms2-2 2.7-1 ii libmwaw-0.3-3 0.3.7-1 ii libodfgen-0.1-10.1.6-1 ii liborcus-0.11-00.11.2-2 ii libreoffice-base-core 1:5.1.5~rc1-1 ii libreoffice-core 1:5.1.5~rc1-1 ii librevenge-0.0-0 0.0.4-4 ii libstdc++6 6.1.1-9 ii libwps-0.4-4 0.4.3-3 ii libxml22.9.3+dfsg1-1.2 ii lp-solve 5.5.0.15-4 ii uno-libs3 5.1.5~rc1-1 ii ure5.1.5~rc1-1 ii zlib1g 1:1.2.8.dfsg-2+b1 libreoffice-calc recommends no packages. Versions of packages libreoffice-calc suggests: ii ocl-icd-libopencl1 2.2.9-1 Versions of packages libreoffice-core depends on: ii fontconfig2.11.0-6.4 ii fonts-opensymbol 2:102.7+LibO5.1.5~rc1-1 ii libboost-date-time1.58.0 1.58.0+dfsg-5.1 ii libc6 2.23-1 ii libcairo2 1.14.6-1+b1 ii libclucene-contribs1v52.3.3.4-4.1 ii libclucene-core1v52.3.3.4-4.1 ii libcmis-0.5-5v5 0.5.1-4 ii libcups2 2.1.4-4 ii libcurl3-gnutls 7.47.0-1 ii libdbus-1-3 1.10.8-1 ii libdbus-glib-1-2 0.106-1 ii libdconf1 0.26.0-1 ii libeot0 0.01-3 ii libexpat1
