Yeah it's definitely that strange hardcoded part in:
/usr/bin/check-support-status:
> DEB_LOWEST_VER_ID=7
> # Version ID for next Debian stable
> DEB_NEXT_VER_ID=9
> …
> if [ "$DEBIAN_VERSION" -lt "$DEB_LOWEST_VER_ID" ] || [ "$DEBIAN_VERSION" -gt
> "$DEB_NEXT_VER_ID" ] ; then
> eval_gettext
Package: base-files
Version: 10.2
Severity: critical
Justification: breaks unrelated software
Hi.
While the bug is likely in debian-security-support, as soon as upgrading to 10.2
(downgrading to 10.1 fixes the problem) a debian-security-support hook will
fail at basically every
Hey Ben, Salvatore.
Thanks for cherry-picking the bug for unstable.
AFAIU stretch and jessie[-backports] should be affected as well.
Shouldn't it go there, too?
At least at the upstream mailing list it was said[0] the the bug was
introduced around October 2008, which should be roughly kernel
Package: epiphany-browser
Version: 3.31.91-2
Severity: grave
Justification: renders package unusable
Hi.
When starting epiphany it crashes:
$ epiphany
(epiphany:1935): GLib-GIO-ERROR **: 19:35:05.423: Settings schema
'org.gnome.Epiphany.web' does not contain a key named
Here's the "proper" patch:
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg85515.html
Source: linux
Version: 4.19.20-1
Severity: critical
Tags: upstream patch
Justification: causes serious data loss
Hi.
Apparently there was a longer existing data corruption bug in btrfs[0],
AFAIU it happened when compression was used together with holes in data
and there was *no* recognition by
Source: openmpi
Version: 3.1.3-6
Severity: critical
Justification: causes serious data loss
Hi.
On upgrading from 3.1.3-5 I get these:
Unpacking libopenmpi3:amd64 (3.1.3-6) over (3.1.3-5) ...
rm: cannot remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-8#': No such file
or directory
rm:
For those reading along, Jens Axboe gave a summary on how to
check whether one's affected or not:
Quoting from: https://bugzilla.kernel.org/show_bug.cgi?id=201685#c294
> scsi_mod.use_blk_mq=0 will do the trick, as will just ensuring that you have
> a scheduler for your device. Eg for sda, check:
Source: linux
Version: 4.18.20-2
Severity: critical
Tags: upstream patch
Justification: causes serious data loss
Hi.
There's a bug in the blk-mq schedulers which may cause serious data
curruption...
See https://bugzilla.kernel.org/show_bug.cgi?id=201685
Seems like a patch was made recently,...
Package: iptables
Version: 1.8.1-1
Severity: critical
Tags: security
Hi.
Seems the massive changes in the recent version breaks loading of
firewall rules by tools like netfilter-persistent...
# journalctl | grep netfilter
Oct 25 15:36:55 klenze systemd[1]: Starting netfilter persistent
Package: o-saft
Version: 17.09.17-1
Severity: grave
Justification: renders package unusable
Hey.
The following happens on a fresh install:
$ o-saft
Can't locate osaft.pm in @INC (you may need to install the osaft module) (@INC
contains: ./ ./lib /usr/bin /bin /etc/perl
Package: nautilus
Version: 3.30.0-4
Severity: grave
Justification: renders package unusable
Hi.
Since a week or so (IIRC, when the new glib version entered unstable):
$ nautilus
(nautilus:32154): Tracker-ERROR **: 20:06:22.721: Unable to find default domain
ontology rule
Hey.
Well, while I guess it's functionality will be missed, you're right
that it probably makes no sense to keep it, now that Mozilla broke all
XUL add-ons.
Cheers,
Chris.
On Tue, 2018-07-10 at 17:20 -0400, Jeremy Bicha wrote:
> I don't know. It works fine here. Could you try to be more specific
> about *when* things stopped working?
I'm afraid I have no idea... I noticed it a week ago, which doesn't
mean though, that it wasn't introduced earlier.
Wasn't there
Package: gimp
Version: 2.10.2-1
Severity: grave
Justification: renders package unusable
Hi.
Since some time the GIMP is completely broken.
In most cases it does not even start (e.g. when invoking
it from another program) or when:
$ gimp
or
$ gimp 0.jpg
(with 0.jpg not existing)
it simply hangs
Ah I see... :-)
Thanks for the prompt reply :-)
Cheers,
Chris.
Package: cinnamon-control-center
Version: 3.6.5-1
Severity: grave
Justification: renders package unusable
Hi.
Since 3.6, when clicking on the control centre icon in the
"Start menu" the control centre doesn't start anymore.
When starting it manually via terminal:
$ cinnamon-control-center
All
Package: python-uniconvertor
Version: 1.1.5-4
Severity: grave
Justification: renders package unusable
Hi.
Since python-imaging is gone now, the package can not longer be installed.
Cheers,
Chris.
Ah I see... thanks for the information :-)
Cheers,
Chris.
Hey.
Shouldn't that go to stable security updates as well?
Cheers,
Chris.
Package: clamav-freshclam
Version: 0.99.3~beta1+dfsg-3
Severity: grave
Justification: renders package unusable
Hi.
With the lastest version the package fails to upgrade:
Setting up clamav-freshclam (0.99.3~beta1+dfsg-3) ...
To check for updates more often than hourly, please run freshclam as a
Package: xul-ext-useragentswitcher
Version: 0.7.3-3
Followup-For: Bug #881904
Hi.
I've just contacted the upstream author. He in fact plans to make a
WebExtensions
version sooner or later:
On Thu, 2017-11-16 at 17:02 -0800, Chris Pederick wrote:
> I was focused on updating Web Developer up to
Package: src:linux
Version: 4.13.10-1
Severity: critical
Justification: breaks unrelated software
Hi.
Apparently AppArmor was enabled per default in the last version.
While I'm usually in favour of anything that improves security
(leaving aside the question here whether SELinux wouldn't be the
Package: xul-ext-noscript
Version: 5.1.2-1
Severity: grave
Tags: security
Justification: renders package unusable
Hi.
Since the upgrade to 5.1.2-1 the plugin, while still appearing in the
add-ons list (and marked enabled there), no longer seems to work.
It's "icons/menus/etc" disappeared and
On Fri, 2017-09-15 at 19:18 +0100, Ben Hutchings wrote:
> Probably less critical than you think, since we enable
> CONFIG_CC_STACKPROTECTOR.
Well... yes, but it wouldn't be the first time in history, that such
defence could then also be circumvented in the next evolution of an
exploit :-)
But of
Source: linux
Version: 4.12.12-2
Severity: critical
Tags: security
Justification: root security hole
Hi.
Any chance to get CVE-2017-1000251, which seems to be quite critical fixed
anytime soon? :-)
https://security-tracker.debian.org/tracker/CVE-2017-1000251
Thx,
Chris
Package: xul-ext-status4evar
Version: 2016.10.11.01-1
Severity: grave
Justification: renders package unusable
Hi.
In FF54, the plugin does not really seem to work anymore.
The status bar is shown, but no content in it.
An update seems to be available, solving this:
Source: zookeeper
Severity: grave
Tags: security
Justification: user security hole
Hi.
It seems there is a grave permission issue in the zookeeper package,
namely that /var/lib/zookeeper is created world-readable.
Since ZK creates its files word-readable as well, any user on the system
can
On Sat, 2017-07-15 at 22:21 +, Debian Bug Tracking System wrote:
> * Disable remote updates to fix CVE-2017-7480 and prevent bugs like
> it in the future (closes: #765895, #866677)
It's good to see this finally done... but really sad to see, that it
required an actually exploit to be
On Sun, 2017-02-05 at 18:15 +0100, Pascal Legrand wrote:
> What is the way to downgrade 45.7.0esr-1 ?
You can for example enable testing in your sources.list, then update
and then just select/install the older version in aptitude.
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic
Package: firefox-esr
Version: 45.7.0esr-2
Severity: grave
Justification: renders package unusable
Hi.
Since the upgrade from -1 to -2 firefox esr crashes few seconds or minutes
after starting it,
with a Mozilla Crash Handler dialog.
Downgrading to 45.7.0esr-1 fixes the issue.
Cheers,
Chris.
On Fri, 2017-01-27 at 10:34 +0100, lopiuh wrote:
> * What outcome did you expect instead?
> [...]
> #LoginGraceTime 2m
> PermitRootLogin prohibit-password
> #StrictModes yes
> #MaxAuthTries 6
> #MaxSessions 10
> [...]
No, the outcome shouldn't be that, it should be left just at default
(which
Package: libxtables12
Version: 1.6.0+snapshot20161117-2
Severity: grave
Justification: renders package unusable
Hi.
Unpacking libxtables12:amd64 (1.6.0+snapshot20161117-2) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-DBLJsg/0-libxtables12_1.6.0+snapshot20161117-2_amd64.deb
Hey.
Is it really necessary that the userland tools binary package depends
on the kernel driver package?
That seems to be rather uncommon among similar packages...
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
Hey.
Not really sure whether these changes here makes things so much better:
1) It's still al just Wants, no Requires... i.e. if netfilter rules
loading fails for whichever reason, the boot process will continue just
normally, with networking and any daemons, that possibly require
netfilter for
Hey.
The backports version (8u102-b14.1-1~bpo8+1) seems to be still
broken...
When can one expect a fix there?
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
Purging and reinstalling it seems to have fixed the issue... also I
haven't had seen this on all my systems...
I'll leave the issue open, perhaps you can find some issue in the code.
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
Package: apt-listbugs
Version: 0.1.18
Severity: critical
Justification: breaks unrelated software
Hi.
Since today when running "g" in aptitude aptitude, upgrading packages:
# aptitude
Performing actions...
/usr/lib/ruby/vendor_ruby/aptlistbugs/logic.rb:345:in `block in initialize':
invalid
duplicate of #831807?
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
On Sun, 2016-07-24 at 01:38 +0200, Michael Biebl wrote:
> It doesn't help for the non-systemd case and people who opt to not
> install recommends by default use a non-standard configuration, so
> it's
> imho ok if those need to also apply additional configuration in case
> of
> SSH. We should
On Sat, 2016-07-23 at 11:29 +0100, Colin Watson wrote:
> While of course I have libpam-systemd installed on all my systems, I
> really don't want to depend on it; besides, the original report had
> people saying that they encountered occasional problems of sessions
> not
> being cleaned up even
For the records, I've asked upstream whether openjpeg support would be
possible:
https://bugs.kde.org/show_bug.cgi?id=364231
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
On Mon, 2016-06-06 at 23:44 +0200, Christoph Anton Mitterer wrote:
> I'd agree,.. but I think it would be worth to EITHER include the
> above
> in the documentation of debarchiver (since it will probably take some
> time until gpg changes its default to >SHA1)... OR, one could
&g
Hey Ola.
On Mon, 2016-06-06 at 23:28 +0200, Ola Lundqvist wrote:
> Thank you for your report, and sorry for a late reply.
No worries :)
> I have done some testing and the hash depends on the version of gpg
> you have and what key you have generated.
>
> If you have at least the version of gpg
On Sun, 2016-06-05 at 23:44 +0200, Michael Biebl wrote:
> On remove/purge yes, it makes sense to turn it back into a real file
but probably only if it's really a symlink to the path used by NM,..
not e.g. when it's the one from resolvconf?
Cheers,
Chris.
smime.p7s
Description: S/MIME
Hey.
libgtk-3-common is still missing from i386,... (but it's e.g. in
amd64)... any ideas? Or does that just take a while?
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
Package: debarchiver
Version: 0.10.5
Severity: grave
Tags: security
Justification: renders package unusable
Hi.
It seems that the Release/etc. files generated by debarchiver
use SHA1 as signature algorithm.
aptitude/etc. in sid no longer accept these weak algos per default
and reject such
On Thu, 2016-05-19 at 16:42 +0200, Christian Seiler wrote:
> This is getting _way_ off track. I just asked nicely because I
> do think the word crosses a line. I don't want to argue about
> the position of that line (because I don't think that would be
> productive); in the end it's up to you what
On Wed, 2016-05-18 at 10:08 +0200, Christian Seiler wrote:
> I can confirm that, this is weird, I'm pretty sure this wasn't always
> the case. Maybe there was some internal change in gtk3. I'll
> investigate.
Thanks :)
> PS: I dislike CSDs too (which is why I maintain this package), but
> could
Hey.
I'd want to object here.
I think this is any extremely helpful add-on, and just because there is
(currently) no active upstream, doesn't mean it must necessarily be
removed.
I think the last version for this add-on was from FF29,... ages ago,...
and it still works just nicely.
Even if FF
Control: notfound -1 1.1.5-4+b1
downgrading fixes the issue.
smime.p7s
Description: S/MIME cryptographic signature
Package: sks
Version: 1.1.5-5
Severity: grave
Justification: renders package unusable
Hi.
Since the recent upgrade to -5, sks no longer starts, bailing out
with:
May 08 22:46:58 kronecker systemd[1]: Started SKS database service.
May 08 22:46:58 kronecker systemd[1]: Started SKS reconciliation
Package: clearlooks-phenix-theme
Version: 6.0.3-1
Severity: grave
Justification: renders package unusable
Hi.
New major GTK, new breakage ;-)
I've collected a number of issues in #821409
Cheers,
Chris.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy:
On Thu, 2016-01-21 at 14:48 +0100, Michael Biebl wrote:
> With the default policy we ship in Debian, the following conditions
> need
> to be met, that a non-admin user can mount/umount
>
> - The user needs to be local and active, e.g. a user logged in via
> SSH
> can *not* arbitrarly mount/umount
On Thu, 2016-01-21 at 04:13 +0100, Michael Biebl wrote:
> This behaviour has been since 2000 or so, since at least the
> introduction of hal and pmount.
Then one has still some 30 years before where it has been different...
> You don't gain anything security wise by not allowing removable media
On Thu, 2016-01-21 at 04:32 +0100, Michael Biebl wrote:
> Right, since we had removable media 30 years ago.
No but mounting filesystems.
> In such a very specialised situation you can easily lock down the
> configuration. For such a setup you will most likely need custom
> configuration anyway
Package: policykit-1
Version: 0.105-14.1
Severity: grave
Tags: security
Hi.
Apparently polkit (or at least I guess it's ultimately the offender here,
if not please reassign accordingly) allows ordinary users to mount any
filesystem per default.
E.g. such connected via USB, or set up via
Control: reopen -1
Control: reassign -1 udisks2
On Thu, 2016-01-21 at 03:39 +0100, Michael Biebl wrote:
> Policykit is the wrong package. What you look for is udisks, most
> likely.
I went through /usr/share/polkit-
1/actions/org.freedesktop.udisks2.policy but all settings there seem to
be
Package: openssh-client
Version: 1:7.1p1-6
Severity: critical
Tags: security
Justification: root security hole
Hey.
You probably know about this already, but just in case not:
https://lists.mindrot.org/pipermail/openssh-unix-dev/2016-January/034679.html
Cheers,
Chris.
-- System Information:
On Thu, 2016-01-14 at 15:03 +, Colin Watson wrote:
> Yes, I do. Upload coming soon.
Great work :-) As usually the security team and maintainers are pretty
fast in Debian... if now there wouldn't be easy ways for blocking
attacks against secure APT, one could really feel pretty safe :)
On Thu, 2016-01-14 at 16:01 +0100, Yves-Alexis Perez wrote:
> Thanks for the report, yes we're aware of it.
The announcement doesn't read *that* extremely bad (well depends a bit
on whether one connects to untrusted systems), though,... thus maybe
the severity of this can be lowered.
OTOH, since
Package: ifupdown
Version: 0.8.5
Severity: critical
Justification: breaks unrelated software
Hi Guus.
I've just upgraded from 0.7.54 to 0.8.5 and after rebooting the server,
all kinds of daemons didn't come up anmore, e.g.
BIND:
# systemctl status bind9.service -ln 1
● bind9.service - BIND
Package: os-prober
Severity: critical
Justification: causes serious data loss
Hey.
AFAIU, os-prober still falls back to using the non grub-mount based probing,
when the later isn't available.
Also os-prober doesn't in anyway depend on grub, so there is absolutely no
guarantee it would be
Anything new on these recent CVEs? Guess quite some people use sid and
they're still vulnerable, AFAIU?!
Cheers,
chris.
Package: meld
Version: 3.14.1-1
Severity: grave
Justification: renders package unusable
Hey.
Since todays upgrades to gtk and friends:
[UPGRADE] gir1.2-gdkpixbuf-2.0:amd64 2.32.1-1 -> 2.32.2-1
[UPGRADE] gir1.2-gnomedesktop-3.0:amd64 3.18.1-1 -> 3.18.2-1
[UPGRADE] gir1.2-gtk-3.0:amd64 3.18.2-1
On Sat, 2015-10-10 at 12:25 +0200, Yves-Alexis Perez wrote:
> So I tried with adwaita, and here it works fine. My theme is usually
> Greybird, so GTK+ might /again/ have broken other them.
FTR: I'm using Clearlooks-Phenix, within cinnamon.
Cheers,
Chris.
smime.p7s
Description: S/MIME
Package: evolution
Version: 3.16.5-1
Severity: grave
Justification: renders package unusable
Hi.
Since some days in sid evolution crashes immediately when starting:
$ gdb evolution
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3
Downgrading libgtk-3-0 and it's friends to 3.16.6-1 "fixes" the issue.
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
Package: needrestart
Version: 2.3-1
Severity: grave
Justification: renders package unusable
Hey.
# needrestart
Can't locate File/Slurp.pm in @INC (you may need to install the File::Slurp
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2
On Wed, 2015-08-26 at 09:05 -0700, Dirk Hohndel wrote:
Some of us have expressed our dismay with the way distributions work
these days.
Well to be honest such dismay comes usually always from the same
fraction within open source... which is typically exactly that fraction
which tries to put more
On Wed, 2015-08-26 at 13:40 +0300, Lubomir I. Ivanov wrote:
your approach for convincing is offensive and unwise.
Well if upstreams are effectively hostile against core paradigms of the
FLOSS community, it must expect that people won't be happy with it.
as a peace of software it now no longer
On Tue, 2015-08-25 at 17:55 -0700, Dirk Hohndel wrote:
Being called stupid and arrogant is usually not a great conversation
opener, but hey, I've been called worse.
Well I should have probably immediately apologised along the way, just
for the sake of politeness...
But the believe to know it
Hey.
How saddening to see such a nice program for divers being basically
destroyed by a stupid and arrogant upstream (and while some may
consider this impolite, I guess it's simply the truth).
Especially the assumption to know it better than the rest of the whole
opensource world and decades of
On Wed, 2015-08-12 at 20:02 +0200, Sylvestre Ledru wrote:
libgit, libmarble libdivecomputer
What a pity :-(
I have been maintaining subsurface for a while. It was easy in the
past,
it is much harder now...
Well your work is highly appreciated... hope you're able to keep it up
=)
Cheers,
On Wed, 2015-08-12 at 09:31 +0200, Salvo Tomaselli wrote:
upstream forked quite a lot of libraries.
Which?
Packaging subsurface is
impossible.
Other projects would do this as well and packaging them works
nevertheless... and subsurface is already packaged, so it's definitely
not impossible...
Hey Rene.
On Tue, 2015-08-11 at 08:09 +0200, Rene Engelhard wrote:
Oh my. Define much more often?
Well roughly said, when I actively work on a spreadsheet,... every 15
minutes?
I don't, I think it's important at least until it crashes every few
minutes.
But I won't argue now :)
;-)
Seems
On Tue, 2015-08-11 at 15:18 +0200, Rene Engelhard wrote:
Oh,... completely forgot about that, sorry, I'll do so tonight.
attached =)
On Tue, 2015-08-11 at 11:24 +0200, Rene Engelhard wrote:
In fact I have diodon (1.0.3-1) running, which is a clipboard
thingy.
And if you disable it?
On Tue, 2015-08-11 at 20:30 +0200, Rene Engelhard wrote:
Well I'll need to try it for a longer while without diodon
running...
I'll tell you later.
OK.
I guess one can quite surely say that this in fact only happens when
diodon runs.
Actually, I even made libreoffice segfaulting
Control: severity -1 normal
Control: retitle -1 libphonenumber6: please use libboost-date-time 1.57 or 1.58
Simon McVittie was so kind to disable libphonenumber6 in evolution for
now and rebuild the package with that.
So I guess the severity of this can be lowered again, as this doesn't
block
Hey.
Anything new here? That blocks upgrading to to current libstdc++6
(without removing a large number of packages) and thus also prevents
other packages (that already depend on newer libstdc++6) with important
security updates to be installed.
Cheers,
Chris
smime.p7s
Description: S/MIME
Package: aptitude
Version: 0.7-1
Severity: grave
Justification: renders package unusable
Hi.
Aptitude 0.7-1 depends upon:
libcwidget3v5
and
libsigc++-2.0-0c2a (= 2.2.0)
(amongst others):
The former, however, depends on libsigc++-2.0-0v5 (= 2.2.0)
which in turn conflicts libsigc++-2.0-0c2a,
On Sat, 2015-08-08 at 02:06 +0200, Axel Beckert wrote:
You are aware that Debian Unstable is in the midst of a huge
transition (libstdc++6) with many followup transitions and that
temporary uninstallabilities are very normal during such transitions?
Sure... I just wasn't sure whether this may
On Sat, 2015-08-08 at 02:21 +0200, Axel Beckert wrote:
My current rule of thumb: Ignore any uninstallability which lasts
less
than two days during the next two weeks.
Normally I'd do,... but right now we have several packages (already
depending on v5 libstd++) with more or less critical
Hey.
I appreciate that you try to push in that matter,... but strictly
speaking, there is no security issue in this package, and also the
severity wouldn't be justified.
Some maintainers may not be too happy about that...
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
Hey.
I appreciate that you try to push in that matter,... but strictly
speaking, there is no security issue in this package, and also the
severity wouldn't be justified.
Some maintainers may not be too happy about that...
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
Package: openssl
Version: 1.0.2c-1
Severity: critical
Tags: security
Justification: root security hole
Control: found -1 1.0.2c-1+b2
CVE-2015-1793 got public, highest criticality.
https://openssl.org/news/secadv_20150709.txt
Cheers,
Chris.
-- System Information:
Debian Release: stretch/sid
Sorry, hand't seen that it was already uploaded :-)
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
On Thu, 2015-06-18 at 20:36 -0400, Michael Gilbert wrote:
See previous message.
I've had read that only afterwards, as well as this message.
You will get
absolutely nowhere continuing to tell people that they need to drop
everything to scratch your particular itches.
I don't think I've asked
On Thu, 2015-06-18 at 23:42 +0100, Steven Chamberlain wrote:
Upstream have said:
https://code.google.com/p/chromium/issues/detail?id=491435#c10
This is not opt-in default. If you do not explicitly opt in
(using
the Enable Ok Google setting in chrome://settings), then this
module
will
On Thu, 2015-06-18 at 20:19 -0400, Michael Gilbert wrote:
Except that the actual contents of the downloaded files in many ways
do not actually matter. Those files are nacl executables, which are
sandboxed in any nacl-enabled chromium, so barring a sandbox escape
included in the files, this is
On Tue, 2015-06-16 at 00:49 -0400, Michael Gilbert wrote:
Barring the obtusely incorrect rootkit miscategorization
Well, as I've said,.. no one can really tell what it is, since it's a
blob,... and even if one would assume that someone could correctly
reverse engineer it, or reproducibly build
Hi.
Shouldn't we see a DSA following this incident?
Since no one really know which binaries have been downloaded there and
what they actually do, and since it cannot be excluded that it was
actually executed, such systems are basically to be considered
compromised.
Quite a deal of people
Package: dsh
Version: 0.25.10-1.1
Severity: critical
Justification: causes serious data loss
Hi.
dsh installs the file /etc/dsh/group/all as a symlink to ../machines.list.
Since I didn't like the way that all host lists would be in /etc/dsh/group/
and just the -a list is in
Downgrading curl/curllibs to 7.42.1-2 fixes the issue again.
The problem may be actually in libculr3-gnutls,... I haven't upgraded
libgnutls-deb0-28.
smime.p7s
Description: S/MIME cryptographic signature
Package: evolution
Version: 3.12.11-1
Severity: grave
Justification: renders package unusable
Hey.
evolution segfaults at start since some of todays upgrades.
$ evolution
(evolution:9111): GLib-GObject-WARNING **: The property
GtkSettings:gtk-button-images is deprecated and shouldn't be used
Control: clone -1 -2
Control: reassign -2 cinnamon
Control: retitle -2 current clutter changed to GDK backend, which crashes
cinnamon
Control: tags -2 + patch
Control: forwarded -2
https://github.com/linuxmint/cinnamon-session/commit/70893dc7a32fb983f44c8e9be07ffe65baf6bbd3
Control: retitle -1
Source: clutter-1.0
Version: 1.22.2-1
Severity: grave
Hi.
Upgrading to 1.22.2-1 breaks cinnamon, i.e. everytime one logs in
from e.g. gdm it immediately crashes and gdm starts a fallback session
(I guess gnome classic or something like that).
Downgrading to 1.20.0-1 fixes the issue.
Cheers,
On Sun, 2015-05-24 at 20:00 +0200, Kurt Roeckx wrote:
It's been sitting in the new queue for at leats 7 months.
Sure but what's the status there,... what keeps that blocking?
smime.p7s
Description: S/MIME cryptographic signature
What's the status here?
Has jitsi been abandoned?
Cheers.
smime.p7s
Description: S/MIME cryptographic signature
On Mon, 2015-05-04 at 09:34 +0200, Kurt Roeckx wrote:
so if the changelog is correct, sid is *not* affected.
It's not.
Uhm... I thought 1.0.2a-1 (sid) is higher than 1.0.2~beta3-1
(experimental)... and I haven't found an entry fixing the issue.
Also tagging just sid is wrong in any case.
101 - 200 of 504 matches
Mail list logo
