Package: evolution
Version: 3.36.0-1
Severity: grave
I am currently seeing the following error come up in evolution when
trying to connect to my gmail accounts. Presumably it is a knock on
effect of increased usage brought on by the lock down for COVID-19.
Someone needs to get the quota bumped up
Package: firefox
Version: 66.0.5-1
Severity: critical
Firefox v67 was released 10 days ago and includes critical security
fixes (as I'm sure I don't need to point out, they always do). Please
update the package on the unstable channel.
I am aware that we are currently in a freeze period for the n
Package: llvm-7
Version: 1:7.0.1~+rc2-1
Severity: grave
I've just updated my Sid install and found that building Rust crates
with Cargo now fails with a seg fault.
Initially I fired a bug report at cargo to kick things off, but I've
now discovered that it relates to the llvm-7 update, as switchin
Package: virtualbox
Version: 5.0.4-dfsg-3
Severity: grave
Certain virtualbox packages seem to have vanished from sid with the
latest update.
I noticed two packages being held back when performing an upgrade on a
sid host - virtualbox and virtualbox-qt (5.0.4-dfsg-2 -> 5.0.4-dfsg-3).
When doing a
On Mon, 2015-08-31 at 17:36 +0300, Sebastian Dröge wrote:
> On Mo, 2015-08-31 at 15:29 +0100, jnqnfe wrote:
> >
> > > Can someone who is still able to reproduce this with 1.5.90 from
> > > experimental also install debug symbols for libc6, libglib2.0-0,
> > >
On Mon, 2015-08-31 at 12:39 +0300, Sebastian Dröge wrote:
> Hi,
>
> On Sun, 30 Aug 2015 00:04:02 +0100 jnqnfe wrote:
>
> > Upgrading to gstreamer1.0-plugins-bad from experimental as someone
> > suggested resulted in the following package changes:
> >
> >
Package: iceweasel
Version: 38.2.1esr-1
Severity: grave
The latest iceweasel update causes it to segfault shortly after loading
it.
Tested with safemode in gdb as outlined by reportbug.
Backtrace:
#0 0x7fff9a3a8ff0 in gst_memory_unmap () from /usr/lib/x86_64
-linux-gnu/libgstreamer-1.0.so.
Hey. Although there may not be security issues within this package
itself, and while the descriptions of severity [1] may not perfectly
cover this unfortunate scenario, an update to this package (and others)
is urgently needed in order for Sid users to be able to install
critical security patches (
Hey. Although there may not be security issues within this package
itself, and while the descriptions of severity [1] may not perfectly
cover this unfortunate scenario, an update to this package (and others)
is urgently needed in order for Sid users to be able to install
critical security patches (
Control: severity -1 normal
Control: close -1
thanks
On Fri, 2015-02-20 at 15:12 -0500, Phillip Susi wrote:
> I'm sorry; I misread what you said. I thought you said you had
> removed the information about the individual disks that were members
> of the array.
No problem.
> At this point the arr
On Fri, 2015-02-20 at 10:16 -0500, Phillip Susi wrote:
> On 2/19/2015 2:24 PM, jnqnfe wrote:
> > Firstly, I am not running fdisk or parted on the raw member disks,
> > I am simply running generic 'fdisk -l' and 'parted -l' commands,
> > which return informa
On Wed, 2015-02-18 at 23:27 -0500, Phillip Susi wrote:
> All of the error messages shown in the logs you sent so far involve
> the raw disks ( sdb, etc ) rather than the raid array. You certainly
> should not be running fdisk or parted on the raw disk, and responding
> to the error messages by say
On Wed, 2015-02-18 at 16:35 -0500, Phillip Susi wrote:
> On 2/18/2015 4:05 PM, jnqnfe wrote:
> > Background = I have a 'fake-raid' RAID0 array,
> > created from two HDDs using my motherboard firmware. This is not
> > used for root, just data.
>
&
Package: libparted2
Version: 3.2-6
Severity: grave
libparted2 breaks my RAID GPT header!
There appears to be a disagreement between parted and fdisk as to the
correct size. fdisk is happy after creating a GPT partition table, but
parted is not and seems to be forcibly applying what it believes to
These errors actually disappeared after a reboot :/ ...
I guess that means I should have refreshed something, or fdisk should
have refreshed something, and thus this can be closed?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Cont
Package: libparted2
Severity: grave
With a 'fake RAID' RAID0 device constructed using motherboard firmware,
which has a GPT partitioning table setup using fdisk (gparted failed me
- see #778683), opening gparted now results in errors in relation to the
RAID member disks.
Specifically, I firstly g
Control: found -1 0.99-1
This security issue stretches back all the way as far as git history
goes, to 0.99-1. Attempting to update versions affected to update the
record, possibly causing correct listing against debian releases in
security trackers...
--
To UNSUBSCRIBE, email to debian-bugs-rc
17 matches
Mail list logo
