Bug#959971: meet.google.com broken with debian build (ff76)

This is the corresponding upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1636632 Either building without --with-system-nss or adding a patch should resolve the problem.

Bug#887798: firefox-esr: impossible to connect to Google domains

On Sat, 20 Jan 2018 11:30:56 +0100 Vincent Lefevre wrote: > (...) > As a temporary and insecure workaround, I can avoid this error by > setting security.OCSP.require to false, even though the error was > not about OCSP. Hello Vincent, this is not a bug in Firefox (ESR). See

Bug#880490: tor: Does not start when the AppArmor LSM is enabled but the apparmor package is not installed

On Wed, 01 Nov 2017 08:04:37 +0100 intrig...@debian.org wrote: > So I propose we do this: > > --- a/debian/systemd/tor@default.service > +++ b/debian/systemd/tor@default.service > @@ -20,7 +20,7 @@ Restart=on-failure > LimitNOFILE=65536 > > # Hardening > -AppArmorProfile=system_tor >

Bug#867818: No printer listed in some applications when no default printer is set

Brian Potkin: > On Sun 09 Jul 2017 at 17:41:00 +0000, Viktor Jägersküpper wrote: > >> The bug is already fixed upstream. > > Reference, please. https://github.com/apple/cups/commit/b2f85109da901eb652babdc4f2a846c1c28228ff

Bug#772097: Aw: Bug#772097: LibreOffice sees only "Generic Printer"

Hi, Rene Engelhard: > I am actually not sure. This bug is so old that cups 2.2.3 vs. 2.2.4 didn't > exist > back then but is quite new. > What makes you think this is a cups 2.2.3 vs. 2.2.4 issue? (yes, I read your > above > steps, but...) I just filed bug #867818, you should be able to

Bug#867818: No printer listed in some applications when no default printer is set

Package: cups Version: 2.2.4-1 Severity: normal Forwarded: https://github.com/apple/cups/issues/5046 Tags: upstream Tags: fixed-upstream Control: affects -1 src:libreoffice Control: affects -1 gnome-control-center Dear Maintainer, CUPS 2.2.4-1 introduces a regression when no printer is set as

Bug#772097: LibreOffice sees only "Generic Printer"

reassign 772097 libreoffice 1:4.3.3-1 retitle 772097 libreoffice: LibreOffice sees only "Generic Printer" affects 772097 - src:libreoffice affects 772097 - gnome-control-center thanks This bug report is actually not about the bug I observed, so cleaning up the mess I created.

Bug#772097: Aw: Bug#772097: LibreOffice sees only "Generic Printer"

reassign 772097 src:cups 2.2.4-1 retitle 772097 printer not listed in some applications affects 772097 src:libreoffice affects 772097 gnome-control-center thanks Dear Maintainer, On Fri, 5 Dec 2014 10:08:23 +0100 "Rene Engelhard" wrote: (citing the original bug reporter)

Bug#858735: thunderbird: After migration Thunderbird fails to start due to AppArmor denials in ~/.icedove

Dear Gerald, Gerald Turner: > BTW, I'm having a frustrating time post-migration: My profile is 49GB, > Thunderbird decided it needs to re-download all that mail, and it has > also fogotten my per-folder "Sort By > Threaded" preference, that I'll > have to re-click hundreds of times, but only

Bug#856185: icedove-l10n-it wants to uninstall thunderbird-l10n-it

Dear Salvo, Carsten Schoenert: > On Sun, Feb 26, 2017 at 09:59:21AM +0100, Salvo Tomaselli wrote: >> # LANG=C aptitude remove icedove-l10n-it:all >> The following packages will be REMOVED: >> icedove-l10n-it thunderbird-l10n-it{u} > > carsten@i5:~/gitprojects/icedove [debian/sid] $ LANG=

Bug#854587: icedove: incorrect start-version in {icedove,thunderbird}.maintscript

Andreas Beckmann: > On 2017-02-08 16:23, Carsten Schoenert wrote: >>> PS: do you plan to rename the source package to thunderbird, too? >> >> Yes, this is planned. But probaly after the Stretch release. Otherwise >> we may conflict with apt-listchanges and the wanted pop-up for the >> change of

Bug#848355: New upstream release (0.96.24.8)

On Fri, 16 Dec 2016 17:16:38 +0100 Julian Andres Klode wrote: > I'd like to follow xenial's 0.96.20.X, as that's an LTS release > series and thus more appropriate for us than a version that only > has 9 months of upstream support (and is not frozen yet). > > I guess we can

Bug#834943: bug forwarded to GitHub

reopen 834943 retitle 834943 caja crash when changing from trash in list view to other directory in list view forwarded 834943 https://github.com/mate-desktop/caja/issues/649 thanks Dear MATE Maintainers, unfortunately I noticed recently that this bug is still present in caja 1.16.0 and I

Bug#836238: no command line prompt visible after updating GTK+3 to 3.21.5-1

Hello Adrian, if I start mate-terminal from the command line (with gnome-terminal) while using the "TraditionalOk" theme, I get $ mate-terminal (mate-terminal:4005): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:2202:16: not a number (mate-terminal:4005): Gtk-WARNING **: Theme parsing

Bug#836238: no command line prompt visible after updating GTK+3 to 3.21.5-1

Hello Adrian, I created a new user, opened mate-terminal, everything seemed ok, then set the theme to "TraditionalOk" which I used with my standard user and the bug appeared again. I also purged and reinstalled mate-terminal after that. Then I played around with the themes. With "High contrast",

Bug#836239: crash when changing the background after updating GTK3 to 3.21.5-1

Package: mate-terminal Version: 1.14.1-1 Severity: important Dear Maintainer, after updating the GTK+3 packages from version 3.20.9-1 to version 3.21.5-1 mate-terminal crashes when I change the background from "none" to whatever I want. Downgrading the GTK+3 packages makes the bug disappear.

Bug#836238: no command line prompt visible after updating GTK+3 to 3.21.5-1

Package: mate-terminal Version: 1.14.1-1 Severity: important Dear Maintainer, after updating the GTK+3 packages from version 3.20.9-1 to version 3.21.5-1 the command line prompt of mate-terminal is not displayed (just white background). Commands are executed although they are not visible.

Bug#835119: tor client does not immediately open new circuits after standby

found 835119 0.2.8.2-alpha-1 thanks I tested different versions again yesterday and today, this time only 0.2.7.6-1, 0.2.8.2-alpha-1 and 0.2.9.1-alpha-1 and I had several "long" standby sessions. The results are again confusing, the 0.2.7 series doesn't seem to have the issue, but it occurs in

Bug#835341: mutt 1.6.2-3 has wrong dependencies

Package: mutt Version: 1.6.2-3 Severity: serious Dear Maintainer, the latest version of mutt has somehow got wrong dependencies (from an older version I guess) and so is not installable in unstable or testing. # apt-get install mutt Reading package lists... Done Building dependency tree Reading

Bug#835119: tor client does not immediately open new circuits after standby

Package: tor Version: 0.2.8.6-3 Severity: normal Dear Maintainer, I use tor only as a client to connect icedove to the tor network with the extension Torbirdy (on port 9050). With the tor version 0.2.8.6 I can't immediately connect to any mail server or news feed after the pc woke up from

Bug#833698: Icedove 1:45.2.0-2+b1 (Debian Testing) SegFault

Everybody who reads only this bug report, please consider my workaround mentioned in bug 833532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833532#50

Bug#833864: icedove: Crash on big folders

Dear Jean-Philippe, from my point of view (I am not a developer) it looks like this is the same bug as 833532 (and the merged bugs). I suggest you to set "javascript.options.baselinejit" to "false" in about:config. If this fixes your problem, this is an indicator that your bug is the same as

Bug#833532: Rebuild against libicu57 causes icedove to crash

In case anyone is not able to use a version prior to 1:45.2.0-2+b1, and since this version is in testing now, I tried a workaround and set "javascript.options.baselinejit" to "false" in about:config. This worked for me so far.

Bug#833532: Rebuild against libicu57 causes icedove to crash

I analyzed the problem a bit more. I use the extension "ThunderBirthDay" which creates a calendar with the birthday dates found in my address book. If there is such a calendar, icedove crashes at startup. If there is no such calendar, icedove starts normally. Even with all extensions, plugins

Bug#833532: Rebuild against libicu57 causes icedove to crash

Dear Maintainers, I assume my problem is related to this bug. After the last upgrade from 1:45.2.0-2 to 1:45.2.0-2+b1 icedove does not start or crashes reliably. I found the following behaviour (plugins are always disabled): - with iceowl-extension and its german language pack enabled icedove