Package: wodim
Version: 9:1.1.2-1
Severity: important
When attempting to burn a DVD+R DL at 1x wodim
ignores the speed=1 directive and writes at 2x resulting
in a failed burn. The speed directive is obeyed when
using driver=dvd_simul and also when using smaller media
(DVD+R (not DL), CDR).
Package: zabbix-agent
Version: 1:1.1.4-6
Severity: important
Upgrading this package will over write /etc/zabbix_agentd.conf
causing any changes to be lost. Most notably the
Server=myhost.localdomain is set to Server=localhost causing data
to be lost until this line is fixed.
-- System
Michael,
You were right, changing the DEBIAN_PRIORITY=medium gave me the option
to specifiy the server. Thanks for the help.
On Fri, Jan 26, 2007 at 09:21:09AM +0100, Michael Ablassmeier wrote:
hi Jeremiah,
On Thu, Jan 25, 2007 at 11:26:47PM -0800, Jeremiah Mahler wrote:
Upgrading
-ds_wspeed = speed; /* XXX Remove 'speed' in future */
***
drv_mmc.c:%
dp-cdr_dstat-ds_wspeed is not used anywhere
dp-cdr_dstat-ds_dr_cur_wspeed is used in several places
--
Jeremiah Mahler [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Eduard,
On Sun, Jan 28, 2007 at 08:29:41PM +0100, Eduard Bloch wrote:
#include hallo.h
* Jeremiah Mahler [Sat, Jan 27 2007, 06:03:47PM]:
Went looking through the source of wodim and it seems that the variable
dp-cdr_dstat-ds_wspeed in wodim.c:main() which is set by the speed=x
Package: php5
Version: 5.2.0-3
Followup-For: Bug #398367
Commenting out the line 'extension=pdo.so' in /etc/php5/conf.d/pdo.ini
fixed the problem for me. And I can still use PDO in my scripts too.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500,
Package: uswsusp
Version: 0.8-1.2+b1
Severity: normal
Suspend to ram seems to be working fine on my T61.
$ s2ram -f
But it still needs to be added to the whitelist.
$ s2ram -i
This machine can be identified by:
sys_vendor = LENOVO
sys_product = 76641KU
sys_version =
Package: libgtkglext1
Version: 1.2.0-1.1
Severity: normal
I am trying to get an application working but it segfaults
every time at the call to gdk_gl_get_proc_address.
Shown below is a simplified program and an example session.
-- get_proce_address.c
Package: uswsusp
Version: 0.8-1.2+b1
Severity: normal
The following is information needed to whitelist my Thinkpad T61.
There is one caveat though, it will not work with the nvidia driver
(nvidia-glx), only the vesa driver.
-- s2ram -n
Package: fluxbox
Version: 1.1.1+git20100807.0cc08f9-1
Severity: normal
The latest update of fluxbox eliminated the fix for this problem.
Included is another patch which is basically identical except it
is located at a different line number.
-- System Information:
Debian Release: squeeze/sid
(debian/copyright).
See the AUTHORS file for contact info for the author, etc.
One possible minor packaging issue is with version numbers.
Changes are made on the git branch quite rapidly and I am not sure
how this is classified as far as unstable, stable, etc.
--
Jeremiah Mahler
jmmah
...@lists.debian.org
--
Jeremiah Mahler
jmmah...@gmail.com
I just confirmed that this problem is only present when using a Nvidia
driver (nvidia-glx).
It works fine when using a ATI Radeon (radeon).
Perhaps re-assign this bug to nvidia-glx?
--
Jeremiah Mahler
jmmah...@gmail.com
Package: libgtkglext1
Severity: normal
What video driver are you using when this problem occurs?
nvidia, radeon, ?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: pidgin-audacious
Severity: normal
The latest version of pidgin-audacious (2.0.0-1+b1) seems to install
correctly.
-- System Information:
Debian Release: squeeze/sid
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500,
'stable')
Package: qpopper
Severity: normal
I can install/remove qpopper on my system with out a problem.
Could you (Astrild) verify that this problem is still present.
j...@bishop ~$ sudo apt-get install qpopper
Reading package lists... Done
Building dependency tree
Reading state
Package: perl-modules
Version: 5.10.1-13
Severity: normal
I can confirm that the encoding directive does not work with
Pod::PlanText. And looking through the documentation (perldoc -m
Pod::PlainText) there is no indication that it supports =encoding.
I believe the page referred to
Package: fluxbox
Version: 1.1.1-8
Severity: wishlist
The attached patch fixes fbsetbg so that it preserves the aspect ratio
when using feh to set the background image.
From the fbsetbg man page if the -a option was given it would attempt to
maximize the image while preserving the aspect ratio
Package: fluxbox
Version: 1.3.0-1
Severity: normal
Apparently the patch got lost again and the problem is back.
The same change as before fixes it.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
Package: debconf
Version: 1.5.50
Severity: important
Tags: patch
Dear Maintainer,
I received the following Use of unitialized value in concatentation
error when I tried to upgrade/install any package.
root@bishop:~# apt-get install --reinstall nmap
Reading package lists... Done
Building
Package: kicad
Followup-For: Bug #736180
Dear Maintainer,
I can confirm that with version 0.20131208 the error message about
missing *.mod files is present in CvPcb. Because of this error I also
could not open any previously created PCBs. Downgrading to 0.20130727
resolved the issue.
I also
Package: evince
Version: 3.10.0-1+b1
Severity: normal
Dear Maintainer,
When printing some PDF's using Evince CUPS fails with
an unexpected brace token error.
/var/log/cups/error_log
...
E [21/Dec/2013:12:20:06 -0800] [Job 423] Exception:
/var/spool/cups/d00423-001 (file position 2592):
Package: network-manager
Version: 0.9.8.8-4
Followup-For: Bug #632850
Dear Maintainer,
After upgrading network-manager to 0.9.8.8-4 the wlan0 interface
does not come up after a suspend/resume. In the task bar
it appears disabled and networking cannot be re-enabled.
Restarting network-manager
Package: light-locker
Version: 1.8.0-2
Followup-For: Bug #870641
Hi,
I am experiencing this problem and I found a workaround ...
If I lock the screen it goes black and won't unlock from the
keyboard. If I ssh to the machine I can restart lightdm and
get a login prompt.
$ light-locker-command
Re: Yves-Alexis,
On Tue, Oct 23, 2018 at 11:01:21AM +0200, Yves-Alexis Perez wrote:
[...]
>
> On Mon, 2018-10-22 at 20:48 -0700, Jeremiah Mahler wrote:
> > I am experiencing this problem and I found a workaround ...
>
> Did you try the other workarounds (vt-swi
Re: Yves-Alexis,
On Tue, Oct 23, 2018 at 05:29:02PM +0200, Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Tue, 2018-10-23 at 08:07 -0700, Jeremiah Mahler wrote:
> > Re: Yves-Alexis,
> >
> > On Tue, Oct 23, 2018 at 11:01:21AM
Package: libgl1-mesa-dri
Version: 22.3.0-1
Severity: normal
Dear Maintainer,
When attemtpting to start X it fails. And looking through the
.local/share/xorg/Xorg.0.log finds a segfault like below (Xorg.0.log.bad).
One workaround I found is to comment out the entire Intel Graphics
config. Not
27 matches
Mail list logo
