On 12/01/2017 10:23 AM, Guido Günther wrote:
> You can look at /etc/apparmor.d/usr.bin.thunderbird. Comment out the
> deny rules by using a '#' one by one. Then do a
>
> apparmor_parser -r /etc/apparmor.d/usr.bin.thunderbird
>
> to load the new profile and see if thunderbird runs.
>
$
Hi Guido,
> The apparmor profile has denials. That means that it will prevent TB
> from accessing files but not lock it. So what the above is not prove
> that Apparmor is not at fault yet. You would have to disable the profile
> using aa-disable and see if thunderbird starts then.
thanks to
Hi Simon,
thanks for the hint concerning apparmor!
On 11/23/2017 07:20 PM, Carsten Schoenert wrote:
> Hello Simon,
>
> On Thu, Nov 23, 2017 at 01:00:48PM -0500, Simon Deziel wrote:
> -T | grep 'apparmor="DENIED"'
I ran `thunderbird`, then `/usr/lib/thunderbird/thunderbird` and finally
Hi Carsten,
thank you for your very quick response!
> Carsten Schoenert hat am 19. November 2017 um 11:33
> geschrieben:
> > Any idea what the issue might be related to?
> No, not with some more information.
> I assume you have already restarted your machine to drop
Package: thunderbird
Version: 1:52.4.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After last nights upgrade I can no longer start Thunderbird.
Starting from the GUI fails silently, launching from the terminal gives the
following error:
$ thunderbird
No protocol
Thanks for fixing this, greatly appreciated!
Greetings
Jack
signature.asc
Description: OpenPGP digital signature
Hi,
are you aware that this change currently renders ansible uninstallable on new
systems? (i.e. where ansible previously has not been installed)
$ sudo apt install [--allow-downgrades] ansible
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some
1dc2f1c380cbbc6f81 Mon Sep 17 00:00:00 2001
From: Jack Henschel <jack...@mailbox.org>
Date: Mon, 6 Mar 2017 11:28:47 +0100
Subject: [PATCH] Fix FTBFS #856834
The location of the test socket is static. When the test is run
multiple times, the socket already exists (aka can't be created),
hence th
Can confirm, the stable kernel (compiled directly from kernel.org) works just
fine (along with the included packaging) with SystemTap 3.1 from Debian
experimental:
$ stap -V
Systemtap translator/driver (version 3.1/0.168, Debian version 3.1-1
(experimental))
Copyright (C) 2005-2017 Red Hat,
On 03/02/2017 06:40 PM, Ritesh Raj Sarraf wrote:
> I just pushed 3.1 to Experimental, the reason being 3.0 is going to be useless
> for Debian Stretch. We need 3.1 to get it working proper with 4.9 kernel too.
Did I get that right: you are planning to ship SystemTap 3.1 with Stretch?
(If so:
I created an upstream bug report at:
https://github.com/boothj5/profanity/issues/901
Greetings,
Jack
signature.asc
Description: OpenPGP digital signature
11 matches
Mail list logo