On 27/12/12 05:14, Michael Biebl wrote:
> On 26.12.2012 21:56, Daniel Pocock wrote:
>
>> Package: network-manager-gnome
>> Version: 0.9.4.1-2
>> Severity: serious
>>
>>
>>
>> I just did a fresh install of wheezy beta 4 i386 onto a Packard Bell
Package: network-manager-gnome
Version: 0.9.4.1-2
Severity: serious
I just did a fresh install of wheezy beta 4 i386 onto a Packard Bell
EasyNote B3410 laptop
I notice that the tray icon for network manager is invisible
I can move the mouse of the place where the icon should be and click and
p
Package: gphoto2-2
Version: 2.4.6-3
Severity: serious
I've marked this bug "serious" because it could lead to someone
accessing or deleting files on the wrong device when multiple devices
are connected.
I have a Samsung Galaxy SIII connected to a USB port. It is not mounted.
While the phone is
Package: installation-reports
Severity: serious
Image version: beta4 netinst CD amd64
System type: Toshiba Satellite P305-S8825
Installer is fine
During Debian's first and subsequent boot, the console becomes corrupted
The X display is just blank too
Access to the box is possible using ssh
A
On 25/11/12 16:16, Josselin Mouette wrote:
> Le dimanche 21 octobre 2012 à 21:34 +0200, Daniel Pocock a écrit :
>
>> I am raising the severity to `serious' because this hammers the NFS
>> fileserver and causes severe performance degradation for users logged in
>&
Package: repro
Version: 1.8.2-1+b1
Severity: serious
This bug is marked as serious because
a) it concerns a feature that has been very widely promoted for the 1.8
release, it has also been widely promoted upstream that wheezy will have
repro v1.8
b) because the bug causes the proxy to refuse SIP m
Package: sipdialer
Version: 1.8.2-1+b1
Severity: serious
This bug is marked as serious because it will create extra effort and
potential surprises for people upgrading the package in future.
This bug only concerns the sipdialer binary package and none of the
other binary packages built from the r
I am raising the severity to `serious' because this hammers the NFS
fileserver and causes severe performance degradation for users logged in
with NFS home directories.
Similar issue reported in Fedora, unfixed there too apparently:
https://bugzilla.redhat.com/show_bug.cgi?id=561904
The expla
Package: linux-image-3.2.0-3-amd64
Version: 3.2.21-3
Severity: serious
Leaves root filesystem in read-only state, some users have reported root
filesystem corruption (see below), so I have marked this as serious
I have a dom0 running Xen (standard squeeze installation) and several
domU VM instanc
I've finally observed something like this again, may or may not be related
On this second machine, there was an existing VG and existing NTFS
partitions (Windows and Lenovo recovery data) and an existing /boot
partition from a previous install
In partman, I did the following:
a) highlighted t
Control: forwarded 682905 https://sourceforge.net/p/enigmail/bugs/87/
Bug reported in enigmail bug tracker and discussed on enigmail mailing list
https://sourceforge.net/p/enigmail/bugs/87/
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Tr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/09/12 08:28, Patrick Brunschwig wrote:
> On 02.09.12 22:43, Daniel Pocock wrote:
>
>
>> Hi,
>
>> People are sending me signatures with caff and I can't import
>> them
>
>> Enigmail prompts
Some further observations. I tried running strace against the icedove
process
This is what I see after clicking `Import OpenPGP signature'
Notice that between the open() and close(), there is no write operation?
access("/tmp", W_OK)= 0
open("/tmp/0x6C6580E77BD756C4.3.sig
Hi,
People are sending me signatures with caff and I can't import them
Enigmail prompts for my password and decrypts the messages OK
When I click the attachment, right click, and select "Import OpenPGP
key" I just get the error "key importing failed" and "No valid armored
OpenPGP data block fo
On 29/08/12 20:33, Gunnar Wolf wrote:
> Daniel Pocock dijo [Sun, Aug 19, 2012 at 10:43:59PM +0200]:
>> I've been looking at the issue of installing both drupal6 and drupal7
>> packages simultaneously during migration (e.g. to migrate one site at a
>> time if there ar
Package: installation-reports
Severity: critical
Image version: beta1 DVD amd64
http://cdimage.debian.org/cdimage/wheezy_di_beta1/amd64/iso-dvd/debian-wheezy-DI-b1-amd64-DVD-1.iso
Date: 28 August 2012
I successfully proceed through all steps up to partitioning / partman
I have a single disk of
After testing the migration process, I've created a wiki page about it here:
http://wiki.debian.org/Drupal/Upgrade/From6To7
The emphasis is on steps specific to the Debian squeeze or wheezy users.
My system is still running squeeze and I added the drupal7 package from
backports, so I have
I've been looking at the issue of installing both drupal6 and drupal7
packages simultaneously during migration (e.g. to migrate one site at a
time if there are several sites)
The only obvious issue that sticks out is that both new and old packages
suggest the same location for locally installed
Package: btrfs-tools
Version: 0.19+20120328-7
Severity: critical
I've marked this as critical as more people are likely to use btrfs with
wheezy, and it results in filesystems not coming up at boot,
consequently it is a system-wide issue and not just a package issue. It
does not involve data loss
On 18/08/12 08:22, Daniel Pocock wrote:
>
>> Hmm, that may make it harder to reproduce it. Can you please send me
>> your enigmail settings in the problematic profile:
>>
>> egrep -i "enigmail|pgp" ~/.icedove/*/prefs.js
>
> I attach prefs from the b
Upstream have released 3.1.8 which only differs from 3.1.7 by adding the
fix for the security issue
It has now been pushed to the git.debian.org VCS for building the
Ganglia package
It is on the squeeze branch and ready for someone to build and upload a
binary package
Regards,
Daniel
--
T
Package: release.debian.org
Severity: grave
Tags: security
Short summary of request: please give authorization to
a) upload ganglia 3.3.8-1 to unstable
b) unblocking 3.3.8-1 to wheezy after appropriate cooling-off period
Longer summary:
- there is a security vulnerability - this unblock has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've now done the following:
- - create an upstream 3.3.8 release which includes only the security fix
- - imported 3.3.8 into the Debian git VCS:
94324d5e11f1332c0f5adecf17a709
- - update the changelog and control file
- - I've added myse
I certainly understand that the drupal6 / drupal7 is not Debian's fault
However, it would be good to have some suggestions for Debian users who
each have to deal with this issue.
a) The first thing is long term strategy: will people get better long
term support if they use some other package?
>>> You could also try with another local user account on that machine, to
>>> rule out that it is due to specific settings in your home directory.
>>
>> I created a new UNIX user, new email address and new PGP key
... snip ...
>> Therefore, it appears to be good for a completely clean user accoun
> Have you received my last mail concerning this bug?
I've just been really busy the last few days, but I still intend to test
more thoroughly and respond
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.deb
On 27/07/12 19:03, Willi Mann wrote:
> Hi!
>
> Am 2012-07-27 17:39, schrieb Daniel Pocock:
>> Maybe there is an issue in my configuration and enigmail is hiding
>> the error or something - I'm quite happy to look at the issue in
>> more detail if you can su
On 27/07/12 15:23, Willi Mann wrote:
> Hi!
>
>> I have the latest icedove and enigmail packages from wheezy, icedove is
>> 10.0.5-1
>>
>> The messages (usually sent to me by a user with caff) are decrypted
>> successfully.
>>
>> However, when I click to save the attached signature, a 0 byte file
g from the command line:
$ gpg --import 0x6C6580E77BD756C4.1.signed-by-0xD929F2992BEF0A33.asc
gpg: key 7BD756C4: "Daniel Pocock " 1 new signature
gpg: Total number processed: 1
gpg: new signatures: 1
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 sig
> Selecting previously unselected package ganglia-modules-linux.
> (Reading database ... 6621 files and directories currently installed.)
> Unpacking ganglia-modules-linux (from
> .../ganglia-modules-linux_1.3.4-2_amd64.deb) ...
> Setting up ganglia-modules-linux (1.3.4-2) ...
> invoke-
On 21/12/11 23:43, Daniel Svensson wrote:
> On Wed, Dec 21, 2011 at 11:18 PM, Daniel Svensson wrote:
>> On Wed, Dec 21, 2011 at 8:55 PM, Daniel Pocock wrote:
>>> Package: xmms2-core
>>> Version: 0.7DrNo+dfsg-2
>>> Severity: grave
>>>
>>> I
Package: xmms2-core
Version: 0.7DrNo+dfsg-2
Severity: grave
I've chosen the severity `grave' as it is suggested for issues that
could "introduce a security hole allowing access to the accounts of
users who use the package"
http://www.debian.org/Bugs/Developer#severities
Details:
- in the default
Package: lxmusic
Version: 0.4.4+git20100802-1
Severity: critical
I already have gxmms2 working fine
I did `apt-get install lxmusic' and then tried to run lxmusic from the
command line
There is a brief flash in the corner of the screen (maybe it is starting
to draw a window) and then I am returne
Package: gracie
Severity: grave
Version: 0.2.11-1
Installed on squeeze amd64 using apt-get
The system was updated with `apt-get upgrade' just before this attempt
to install gracie
Unpacking gracie (from .../gracie_0.2.11-1_all.deb) ...
Processing triggers for man-db ...
Setting up gracie (0.
Package: gracie
Severity: serious
Version: 0.2.11-1
Tags: security
The gracie daemon runs with root privileges
The daemon is a HTTP server that is intended to listen for connections
from the public internet. Therefore, it should not be root.
However, some of the pam functionality requires ro
201 - 235 of 235 matches
Mail list logo
