Looks like they have added SHA256 now.
Label: Google
Suite: stable
Codename: stable
Version: 1.0
Date: Thu, 17 Mar 2016 21:43:22 +
Architectures: amd64
Components: main
Description: Google chrome-linux repository.
MD5Sum:
89704f9af9e6ccd87c192de11ba4c511 145 main/binary-amd64/Release
250e7
Package: reportbug-ng
Version: 1.31
Control: severity -1 important
Control: tags -1 unreproducible moreinfo
Works here, with icedove.
--- System information. ---
Architecture: amd64
Kernel: Linux 4.4.0-1-rt-amd64
Debian Release: stretch/sid
500 unstable ftp.debian.org
500 testing ftp.debian.or
Package: linphone
Version: 3.6.1-2.4
Severity: serious
It seems with the recent rebuild for the libvpx transition,
linphone-common somehow picked up a +b1 which is not in the versioned
linphone-common depends of the other linphone packages.
..or something like that.
Also picked up by piuparts
control: severity -1 normal
thanks
This looks more like a problem with the kernel driver for that device.
Does it work with a newer (or, ftm, older) kernel?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.d
Looks like this is not going to happen in time for jessie? If not, in
terms of cleaning up severity inflation, shouldn't we put this back to
important?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.
control: severity -1 important
thanks
Does the workaround in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763599 work?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Sat, Dec 20, 2014 at 9:02 AM, Michael Gilbert wrote:
if [ -L /etc/X11/app-defaults/XScreenSaver ]; then
if [ "$(readlink /etc/X11/app-defaults/XScreenSaver)" =
"XScreenSaver-nogl" -o \
"$(readlink /etc/X11/app-defaults/XScreenSaver)" =
"XScreenSaver-gl"]; the
Seems to work ok with emacs24-nox. Perhaps using that would be a
temporary workaround?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
That is (was? not sure what the systemd and gnome people have decided
for us) the intended behaviour. The network setup is part of the system
configuration, not owned by a normal user.
Of course the problem you describe is real, and the solution is full
disk encryption (FDE). It's offered by s
These kinds of problems have plagued kmail for many, many years, dating
back to the beginnings of kmail2 (at least). As we can see from the
numerous upstream bugs, there is also no shortage of reports (IIRC, I
filed one myself for fake duplicates years ago). Perhaps upstream
doesn't care, or it
control: tags -1 +unreproducible
thanks
> PS.: Should this bug really be handled as release critical?
Your call, since you have made the most serious effort to understand and
reproduce it.
We also have gtk-vnc 0.5.3-1.3 in jessie now, is that affected as well
(probably yes, the changelog jus
control: severity -1 important
thanks
So in terms of deep-freeze bug triage and cleanup, what do we want to do
with this?
It's been over a year, and there aren't any "me-too" here, even though
there are reports of a similar problem at suse and ubuntu. Regardless,
it doesn't seem to be a wide-s
severity 770477 important
thanks
Setting appropriate (non-rc!) severity as suggested above.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
reassign 767745 pidgin-otr
severity 767745 important
thanks
Reassigning to correct package and adjusting severity according to
intrigeri's comment in #767075.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists
kdelibs4c2a? Isn't that oldstable, or worse? Do we support mixing
unstable and oldstable, at RC severity?
Because then I still have a few fresh bugs from unstable where
cooperation with compiz is impacted..?!
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of
Hi
My guess would be that thinkfan gets corrupted data from 'somewhere',
and then some lack of bounds or type checking messes up other internal
variables and leads to corrupt data being written out.
In that case, and if you are 100% sure there is no spurious special
characters in any config
severity 739605 normal
thanks
Perhaps have a look at the man page about where to find log info for
debugging this, and for possible quirks you may have to use.
The man page also states that the pm-* executables are normally supposed
to be called by power managers/daemons, and that calling the
Hi
Your problem is most likely that your system either doesn't support fan
control, or it has not been manually enabled (that's what the error
message says after all).
See also thinkfan's README.Debian reproduced below.
thinkfan for Debian
---
WARNING!
thinkfan CAN kill yo
Hi Bart,
sounds great, thank you for your work to keep the pepper version of
flash available and up-to-date; it's appreciated.
Alex
On 09/09/14 10:17 PM, Bart Martens wrote:
Hi Alex,
Thanks for reporting this.
What happened :
The script I use on people.d.o for updating the .txt files there
Package: pepperflashplugin-nonfree
Version: 1.5
Severity: grave
Tags: security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
The check for updates
update-pepperflashplugin-nonfree --status
checks an apparently hand-made file on people.d.o and not the real upstream.
As a consequence
Is this still an issue with radeon?
For my nvidia system it disappeared several weeks ago with a nouveau update.
It's tagged RC, so we should be sure it's still a "grave" bug?!
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Are we really sure it's a service to debian users or debian as a
distribution to simply remove compiz from wheezy based on a number of
minor(?) issues that are so obscure that they needed a fake RC bug?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "uns
Both procmeter3-xaw and procmeter3-gtk2 work on my amd64 sid system,
so something might be wrong on your side.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I don't know whether this helps, but I have maril...@debian.org's
flashplayer-mozilla 2:10.1.53.64-0.0 installed (from debian-multimedia),
which pulls in the 32 bit plugin and nspluginwrapper and a couple of
ia32 libs (some of them also from debian-multimedia), and it works quite
well in icewea
Actually, the same (/very similar) problem appears when using the NVIDIA
binary driver, directly after the 7.5+1 update. Reverting to testing
fixes this.
Unlikely that it's the nv driver only. Sorry.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubs
By now, numpy should implement most of the numeric API. In the actual
biggles code, numeric is used only a few times, and all of those
functions are in numpy (as far as I can see). Has anyone every tried
to just replace numeric by numpy in that code?
--
To UNSUBSCRIBE, email to debian-bugs-rc-r
I have this problem, too. Very annoying.
www.opbyte.it/release/grsync-0.9.2.tar.gz
gives me a 404
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: libwine-gl
Version: 1.1.24-1
Severity: serious
Still depends on ia32-libs, which apparently is being removed [1].
[1] http://packages.qa.debian.org/i/ia32-libs-tools/news/20090704T113230Z.html
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsu
Also, is the
Depends: ia32-libs
still needed/correct? I understand that one is going to be removed,
and the current (transitional) ia32-libs is a metapackage with a _lot_
of dependencies? And probably not all of them are needed for X/glx?!
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@list
29 matches
Mail list logo
