I think upstream changed that recently (on my request).
I will implement your workaround (probably tonight) but to be cleaner,
the packages with a dependecy on llvm
should be rebuilt
OK, I should have thought of doing the rebuilds before selecting
the severity. Feel free to lower the severity I
, which
requires radeonsi for acceleration), so few other people will be affected by
this bug right now.
HTH,
Dave Witbrodt
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (350, 'experimental')
Architecture: amd64 (x86_6
Package: libnfsidmap2
Version: 0.25-3
Severity: grave
Justification: renders package unusable
Upgrading to the latest libnfsidmap2 causes nfs-common to fail to start:
libnfsidmap2 0.25-3:
# service nfs-common start
[] Starting NFS common utilitie
I have a second machine which I use as a web/email server... let's call
it "webserver". (Let's call my first machine "desktop".)
Today I upgraded "webserver" from Lenny to Squeeze, and then to Sid.
This machine was running a custom 2.3.37 kernel throughout the upgrade
process. Once the upgra
On 03/06/2012 09:50 PM, Marco d'Itri wrote:
On Mar 07, Dave Witbrodt wrote:
All of the changes reveal that modules were no longer being added to the
initrd with 6-1 installed. Having painstaking crafted my own '.config'
Do you use MODULES=most in /etc/initramfs-tools/in
Package: procps
Severity: normal
> Did you reboot between upgrading/downgrading procps?
No, I merely performed the upgrade while I had stopped X.
I was experimenting with changes to xorg.conf because of
some X server peculiarities I was reporting to the radeon
driver mailing list (xorg-driver-...
Package: procps
Version: 1:3.2.8-8
Severity: critical
Justification: breaks unrelated software
Upgrading to 3.2.8-8 from 3.2.8-7 causes X software to receive endless
amounts of input. For example, trying to run an email client is
impossible because the password dialog is overwhelmed with input b
Ben,
I was just taking a look at this bug after I found it here:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=nfs-kernel-server
It is marked as resolved, because you closed it after you provided your
NMU, but it looks like this is not actually resolved. Did you mean to
reopen this bu
Package: nfs-common
Version: 1:1.2.1-1
Severity: grave
Justification: renders package unusable
Updated just now, and getting these results:
Selecting previously deselected package libtirpc1.
(Reading database ... 124081 files and directories currently installed.)
Unpacking libtirpc1
Package: libnfsidmap2
Version: 0.22-2
Severity: grave
Justification: renders package unusable
Upgraded on Sid today, and the move from libnfsidmap2 0.22-1 to 0.23-1 caused
this:
= BEGIN QUOTE =
[...]
Starting portmap daemon
Starting NFS common utilities: statd idmapdrpc.idmapd: libnf
Package: console-setup
Version: 1.34
Severity: serious
Justification: Policy 10.7.3
My last upgrade of 'console-setup' caused /etc/default/console-setup to
be overwritten without warning. The contents of the file before being
overwritten were :
# A configuration file for setupcon
# Cha
Any news from upstream on this? I was under the impression that the fix
had been committed immediately upstream since the bug can have the
effect of preventing the plugin from running at all.
DW
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscri
Package: xfce4-sensors-plugin
Version: 0.10.99.6-1.dwfix.nondebug
Followup-For: Bug #519181
I created an account at bugzilla.xfce.org and reported the bug
upstream. A developer there has acknowledged the bug, and says that a
fix for it will be applied to their subversion repository.
Sorry that
Tino Keitel wrote:
in your previous mail, you wrote that the segfault is caused by calls
to g_free() with an uninitialized checktext variable. Without looking
at the code, wouldn't just initializing cleartext with NULL be a much
smaller fix? I assume that g_free() behaves like free() here ("If pt
Package: xfce4-sensors-plugin
Version: 0.10.99.6-1.dwfix
Followup-For: Bug #519181
Attached is a patch showing changes I made which fix the crash problem on my
own machine. I created the patch like this:
diff -u hddtemp.c.orig hddtemp.c > ~/xfce4-sensors-plugin-0.10.99.6-1.diff
HTH,
Dave
Package: xfce4-sensors-plugin
Version: 0.10.99.6-1
Followup-For: Bug #519181
In xfce4-sensors-plugin-0.10.99.6/lib there is a file 'hddtemp.c'. It
is in this file that the plugin is crashing for me. (This is visible in
the output of the gdb 'where' command in my last post.)
The location of
Package: xfce4-sensors-plugin
Version: 0.10.99.6-1
Followup-For: Bug #519181
Sorry for my incompetence, but I've never used 'gdb' before.
I made an attempt to get an interactive 'gdb' session to run from the
script called by my modified *.desktop file, and it seems to have paid
off. This is the
Yves-Alexis Perez wrote:
On mar, 2009-03-10 at 20:54 -0400, Dave Witbrodt wrote:
To answer your questions directly:
- the plugin crashed when installed, and when attempting to add it
back to the panel. Not when doing some specific function of the
plugin, because it simply will not run
Yves-Alexis Perez wrote:
At what time does it crash? When Adding the plugin or when doing
something precise? Would it be possible to attach a gdb and provide a
backtrace?
The plugin had already been configured to appear on the panel when
I upgraded several days ago. Upgrading caused the plu
Package: xfce4-sensors-plugin
Version: 0.10.99.6-1
Severity: grave
Justification: renders package unusable
The previous version of xfce4-sensors-plugin (0.10.99.5~svn-r4998-2) works
just fine, but this latest version is crashing for me. Here is the output
in ~/.xsession-errors:
*** glibc de
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-1
Severity: critical
Justification: breaks the whole system
[NB: I refer below to self-compiled kernels a bit, but this report IS
against the stock kernel.]
I saw that there is a push to get 2.6.26 into Lenny, so when
linux-source-2.6.26_2.6.2
21 matches
Mail list logo
