on a remote host
Thanks for the quick response,
On Wed, Oct 22, 2014 at 6:40 AM, Guido Günther a...@sigxcpu.org wrote:
On Tue, Oct 21, 2014 at 05:53:46PM -0700, Martin Gallant wrote:
Package: virt-manager
Version: 1:1.0.1-2
Severity: important
Since a recent update of virt-manager in Jessie, I have
Package: virt-manager
Version: 1:1.0.1-2
Severity: important
Since a recent update of virt-manager in Jessie, I have lost the ability to
pull down the small menu in the center of the client machine full screen
console. This is where the exit full screen mode button I was using is
located.
This
This is a laptop with nothing connected - There should only be one display.
lightdm + xfce4 works fine with the latest drivers installed.
lightdm + gnome still broken and leaves the following in my .xsession-errors
Xsession: X session started for martyg at Sun Oct 19 19:13:59 PDT 2014
The reason it appeared I did not restart X after loading the updated
module is the Xorg.1.log was a stale console from an older unrelated
XDMCP client session.
I cannot get the system to create a new Xorg.*.log when X is invoked via gdm3.
I have no idea why that is - If I invoke X directly, the
Followup-For: Bug #765726
Package: nvidia-driver
Version: 340.46-1
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was
I have reproduced this issue on a pristine untweaked Jessie install on
the same hardware.
1. Boot process never gets as far as gdm3 boot screen
2. No /var/log/Xorg.0.log creaed
--
Marty
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Package: nvidia-driver
Version: 340.46-1
Followup-For: Bug #765726
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was
Package: nvidia-driver
Version: 340.46-1
Severity: Critical
nvidia-driver upgrade this morning on my Jessie systems broke both my
NVIDIA boxes
One is a amd64 latop with Quadro 1000M (GF108M)
The other is a i386 with a generic GT610 card
Everything was peachy on 340.32.-1 before this upgrade
I tried to provide full info with my original report,
but was blocked by 758619 - reportbug fails with Attempt to unlock
mutex that was not locked
As soon as the GTK fixes for that propagate down to me, I will put
together what you need.
--
Marty
--
To UNSUBSCRIBE, email to
Same here on all 3 of my jessie machines, amd64 i386
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Has this issue been reported upstream to the kernel developers?
I just did a search on bugzila, and couldn't find any record of this issue.
--
Marty
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Wed, Nov 6, 2013 at 1:07 AM, Michael Vogt m...@debian.org wrote:
On Sat, Nov 02, 2013 at 12:53:47PM -0500, Martin Gallant wrote:
This problem appears to have been exposed by the update to apt
0.9.12.1 (0.9.12.1)
I have made three changes to the unattended-upgrade script to dig
I have been tracking down a related issue in the unattended-upgrades package.
Please refer to bug report 726123.
The traceback I get is nearly identical to that reported in this bug.
So I wanted to bring this related issue to your attention.
I have tried to put together a fix locally, but am
This problem appears to have been exposed by the update to apt
0.9.12.1 (0.9.12.1)
I have made three changes to the unattended-upgrade script to dig into this:
See enclosed patch.
1. Initialized return code to eliminate referenced before assignment
in the exception path
2. Added tracback code to
All my Jessie machines started reporting this error this morning.
(unattended-upgrades is run daily on all these machines.)
I am enclosing log files from today and 2 days preceeding on a
representative machine
--
Marty
(Reading database ... 123230 files and directories currently installed.)
This bus is still present in wheezy.
--
Marty
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Worked around this issue by inserting round parentheses around the
qw(...) stansas at the locations in the above report.
SMB failures turned out to be a configuration issue on my system, so
downgrading bug to NORMAL.
Thank you for maintaining this package
--
To UNSUBSCRIBE, email to
Package: backuppc
Version: 3.2.1-2
Severity: important
I get these errors whenever running tarCreate/tarExtract
I think these started happening about 2 weeks ago after a perl upgrade
tarExtract: Use of qw(...) as parentheses is deprecated at
/usr/share/backuppc/lib/BackupPC/Storage/Text.pm line
Marked this bus as important as this is currently blocking full
backup of my hosts via SMB.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: backuppc
Version: 3.2.0-3
Severity: important
When a file fails to backup (due to being locked) the marker used is that of th$
last full backup, instead of the last incremental.
Also, if I take a dump of the system using BackupPC_tarCreate, the resulting
image contains the last full
This is important to me, as I use the tar creation facility to snapshot my
hosts for offsite backups.
The way backuppc operates, the images I send offsite could have PST files
several days out of date.
--
Marty
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
Here is the attachment for this bug report.
attachment: sequence.jpg
Package: eclipse-platform
Version: 3.5.2-8
Severity: important
Tags: sid
eclipse-platform : Depends: sat4j ( 2.2.1) but 2.2.3-1 is to be installed
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture:
I have made progress isolating the problem by using manual invocations of GNU
tar.
Apparently the semantics of .tar .one-file-system. has changed.
If I remove this option from my test invocation, the dump proceeds normally.
--
To UNSUBSCRIBE, email to
I have isolated this issue to upgrading tar from 1.23-3 to 1.24-1.
The bug still exists in the latest version 1.25-2.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: amanda-server
Version: 1:3.1.0-1
Severity: grave
Justification: causes non-serious data loss
For the past few days all my dumps for volumes residing on the server machine
show an empty level 0 dump. I am using GNUTAR.
This has been observed with tar 1.25-1 and tar 1-25-2.
Dump volumes
Package: amanda-common
Version: 1:2.6.1p2-1
Severity: normal
Working around by
tweaking /usr/lib/amanda/perl/Amanda/Constants.pm
as described by Wolfgang
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture:
Package: imagemagick
Version: 7:6.6.0.4-1
Severity: normal
After a clean upgarde Lenny-Sid, montage gives the following error -
(Perhaps a missing dependency in imagemagick package?)
Testcase:
$ montage test.jpg test1.jpg
montage: unable to read font `(null)' @
Package: amanda-server
Version: 1:2.5.2p1-4
Severity: normal
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
]
Sent: Wednesday, October 18, 2006 2:09 AM
To: Martin Gallant; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#384762: amanda-server: Upgrade to Etch - Excessive
Loggingin /var/log/amanda
severity 384762 normal
thanks
On Sat, 2006-08-26 at 08:04 -0500, Martin Gallant wrote:
Tons
Package: amanda-server
Version: 1:2.5.0p2-1
Severity: important
Tons of logs being placed in /var/log/amanda since upgarde to Etch
Version in etch was compiled with --with-debugging=/var/log/amanda
Suspect this is the root cause
-- System Information:
Debian Release: testing/unstable
APT
31 matches
Mail list logo
