Package: kdevelop
Version: 4:3.4.0-1
Severity: grave
Justification: renders package unusable
After installing kdevelop and subversion via apt, I start kdevelop
and Project -> New Project results in a crash. Here is the backtrace.
(no debugging symbols found)
Using host libthread_db library "/lib/
Package: llvm-gcc-4.6
Version: 3.2-1~exp1
Severity: normal
When attempting to compile a file that utilizes boost's sign function, such as
goodrich@CYBERPOWERPC:/tmp$ cat sign.cpp
#include
#include
int main() {
std::cout << "expect 1, get " << boost::math::sign(10.0) << std::endl;
std::cout
Quoting Sylvestre Ledru :
Hello,
On 22/12/2012 09:04, Ben Goodrich wrote:
Package: llvm-gcc-4.6
Version: 3.2-1~exp1
Severity: normal
When attempting to compile a file that utilizes boost's sign function,
such as
Did you try with gcc 4.7 ?
Yes, the behavior is essentially the same
I think I had the same problem on my machine: clang-3.2 had been
working for months, then I upgraded to g++-4.8 from experimental when
it was officially released (which pulled in some other libc stuff),
and then I got the "error in backend":
fatal error: error in backend: Cannot select: 0x4
Quoting Sylvestre Ledru :
On 08/12/2012 21:57, Ben Goodrich wrote:
Package: clang-3.2
Version: 3.2~rc3-1~exp1
Severity: important
/usr/bin/clang: symbol lookup error: /usr/bin/clang: undefined symbol:
_ZN4llvm11AttrListPtr3getERNS_11LLVMContextENS_8ArrayRefINS_18AttributeWithIndexEEE
clang
After doing a reconfigure under the Tools menu, I am no longer able to
reproduce either issue, so you probably should downgrade the severity of
the bug report. Possibly the issue would go away on the next LyX upload.
Thanks,
Ben
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
See http://sidux.com/PNphpBB2-viewtopic-t-5314.html
Worked for two people at least. -- Ben
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGxLepzQDSXIcN85kRAiHrAJ46dCORRum9Z9UokKableca6RrTdwCfTT5j
BFF2B8PajZNxUfZTdtuUI8k=
=fKS9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: r-base-core
Version: 2.5.1-2
Severity: important
Hi Dirk,
To replicate this problem on a amd64 machine, do
cd /tmp
echo "log(1)" > crash.R
R -d "valgrind --verbose --db-attach=yes" --vanilla < crash.R
The last line is adapted from
http://
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
Dirk Eddelbuettel wrote:
> Doug,
>
> On 20 August 2007 at 11:12, Douglas Bates wrote:
> | I have been able to run the development version of R with valgrind on
> | an Ubuntu (gutsy) amd64 system. I am compiling R with the 4.2.1
> | series o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dirk Eddelbuettel wrote:
> Could be the compiler, could be R. FWIW the debian/rules specifies gcc 4.2
> as per
>
>
> # edd 03 Apr 2006 switch to gfortran
> # edd 04 Apr 2006 use optimflags, build per-compiler flags later
> # edd 26 Jun 2007 need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: r-base-core
Version: 2.6.2-1
Severity: normal
Hi Dirk,
With the new R and new BLAS, example(kappa) fails with the following error
BLAS/LAPACK routine 'DGEBRD' gave error code -10
Upon further review, the error is actually thrown from svd()
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dirk Eddelbuettel wrote:
[snip]
> I attach an example program below. It runs as follows
>
>[EMAIL PROTECTED]:~/src/progs/C> ./lapack_dgesdd
>info 0 tmp 1.00 != recd 603
>
> 1.725883,0.321633,0.031039,0.001979,0.88,0.03,0.
Package: rkward
Version: 0.4.7-2
Severity: important
Hi Thomas,
Hope things are well. To replicate this crash, execute
det(diag(3))
I would send a backtrace but rkward does not seem to play nice with gdb on my
system. Perhaps this is another bug? All I've got is the konsole message
rkward: sym
Quoting Thomas Friedrichsmeier <[EMAIL PROTECTED]>:
> I can reproduce the problem, but not sure, where it
> really comes from in the first place (worked smoothly shortly before).
I am pretty sure that det() was working within rkward prior to May 3 when a new
r-base was pushed onto unstable. Hopef
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: rkward
Version: 0.4.9-2
Severity: important
Hi Thomas,
rkward 0.4.9-2 fails to start on amd64
[EMAIL PROTECTED]:~$ rkward
/usr/bin/rkward.bin: error while loading shared libraries: libRblas.so:
cannot open shared object file: No such file o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I can confirm that if rkward 0.4.9-2 is built from source, it will run.
Perhaps downgrade the severity of this bug to "normal". -- Ben
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHp4eTzQDSXIcN85kRAuCoAJ9uyNfpQC3p4ULSD6XGFxI
Package: rkward
Version: 0.4.7a-1
Severity: important
*** Please type your report below this line ***
Hi Thomas,
Dirk uploaded R 2.6.0 alpha to unstable and now rkward does not start. -- Ben
[EMAIL PROTECTED]:~$ ps ux | grep rkward
goodrich 7097 0.0 0.0 3036 720 pts/1S+ 15:14 0:00
Package: xserver-xorg-input-mouse
Version: 1:1.2.2-5
Severity: important
*** Please type your report below this line ***
Hello,
Today I updated to the new xserver and xorg in
unstable, but the mouse is not working on my X41
Tablet PC laptop. I can see the pointer, but it does
not move or click. I
[forgot to CC the BTS]
Hi Brice,
Thank you for considering this bug.
Brice Goglin wrote:
> Ben Goodrich wrote:
>> Perhaps there is a larger problem in that I once tried
>> to mv xorg.conf to see if X would automatically
>> reconfigure itself to get the mouse working, bu
Hi Brice,
I understand that there are probably a number of bugs with the new xorg
and xserver that people are filing, but I currently cannot use a mouse
with my laptop (neither the built-in one nor a USB mouse). So, if no one
can think of ideas for a workaround, then I need to revert to the
versio
Hi Brice,
Brice Goglin wrote:
> Yes those input problems are strange and important. And actually, apart
> from the pixman bug (fixed now), and some ati driver specific problems,
> most of the remaining bugs reported since the upload of Xserver 1.4 are
> input related so we really need to care qui
Hi Brice,
Brice Goglin wrote:
> forwarded 442915 https://bugs.freedesktop.org/show_bug.cgi?id=12508
> thank you
>
> Forwarded at the URL above, feel free to add any comments there if you
> think it could help.
>
> Brice
Bug#442915 can be closed. In xorg.conf, I needed to specify
InputDevice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johannes Ranke wrote:
>> |
>> | I noticed this problem with R 2.5.1 (binary from Debian unstable or
>> | source from CRAN); do you want me to try the SVN version of R?
>>
>> Could be the compiler, could be R. FWIW the debian/rules specifies gcc 4.2
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dirk Eddelbuettel wrote:
> I still have the feeling that I am not quite sure why and where this would be
> a bug in R. As Doug demonstrated, it works merrily on amd64 with the same
> toolchain.
>
> So the ball is back in your court as we're not quit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dirk,
I suggest this bug report be closed. Today I dist-upgraded (for the
first time in about a week) within unstable and it pulled in the newest
valgrind from two days ago, and the original crash is gone on amd64 (not
entirely sure why from readin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It appears as if this bug was reported on LyX's bugzilla in January
http://bugzilla.lyx.org/show_bug.cgi?id=4568
and closed as invalid due to the fact that qt 4.4 is / was not released
yet. I requested that the bug be reopened now that the RC is in s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: rkward
Version: 0.4.9-2
Severity: important
Hi Thomas,
Dirk uploaded a new R 2.7.0 beta, which causes rkward not to start.
Konsole says:
/usr/bin/rkward.bin: error while loading shared libraries:
libRlapack.so: cannot open shared object fil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Temporary workaround for this bug if you have the R 2.7.0 beta:
ln -s /usr/lib/R/modules/lapack.so /usr/lib/R/lib/libRlapack.so
Ben
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH/j+czQDSXIcN85kRAjNnAJ4wJJij4c/aE6EKkPBq9Go4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At least two people have observed that the crashing of LyX 1.5.4 on
startup with the Qt from unstable can be avoided by installing more Qt
libraries; see
http://sidux.com/index.php?name=PNphpBB2&file=viewtopic&p=76615#76615
We are not sure which ones
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: rkward
Version: 0.5.0b-2
Severity: grave
- --- Please enter the report below this line. ---
Hi Thomas!
Starting rkward 0.5.0b-2 (0.4.9 still works) produces the following in
Konsole:
[EMAIL PROTECTED]:/tmp$ rkward
QFSFileEngine::open: No fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: r-base-core
Version: 2.6.1-1
Severity: important
Hi Dirk,
My strong hunch is that this bug should just be forwarded upstream but
it might have something to do with libc6 on Debian. To reproduce it, do
args(utils:::edit.matrix)
mat <- matrix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: mailody
Version: 0.5.0-2
Severity: important
When starting mailody, I was getting this message (in setup.cpp)
"Your system does not seem to be "
"setup for TLS or SSL, these settings "
"are disabled. Install QCA and "
"recompile Mailody or c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: r-base-core-ra
Version: 1.2.4-1
Severity: normal
Hi Dirk,
In a Ra session,
help(matrix) # -> No documentation for 'matrix' in specified packages
The issue is that my .libPaths() is
[1] "/usr/local/lib/R/site-library" "/usr/lib/R/site-libr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dirk and Steve,
Dirk Eddelbuettel wrote:
> Hi Ben,
>
> On 30 January 2009 at 14:04, Ben Goodrich wrote:
> | -BEGIN PGP SIGNED MESSAGE-
> | Hash: SHA1
> |
> | Package: r-base-core-ra
> | Version: 1.2.4-1
> | S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: sagemath
Version: 3.0.5dfsg-1
Severity: serious
Justification: no longer builds from source
Hi Tim,
William Stein pointed out to me that I needed the time program to build
sagemath. For the build failure log, see
http://groups.google.com/gr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: r-cran-matrix
Version: 0.999375-20-1
Severity: normal
*** Please type your report below this line ***
Hi Dirk,
On the 32bit version of r-cran-matrix only, the following functions are
producing an error message that says:
could not find sym
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: rkward
Version: 0.4.9a-1
Severity: grave
Justification: renders package unusable
Hi Thomas,
With the R 2.9.0 alpha, when starting rkward (this is with rkward from
testing and everything else from unstable but also happens on another
computer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: r-base-core
Version: 2.10.1-2
Severity: normal
Hi Dirk,
I just updated my systems (I am seeing this on i386 too) a few minutes
ago, and now R seems to have a problem loading some packages installed
from CRAN (but everything was working fine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dirk,
Dirk Eddelbuettel wrote:
> Weird that nobody else -- including, say, me and cranberries (!!) sees
> that. I am running 2.10.1-2 as well.
This is manifesting itself as a FTBFS on mipsel
https://buildd.debian.org/fetch.cgi?pkg=r-base;ver=2.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dirk,
Dirk Eddelbuettel wrote:
> Then it is probably Perl related -- see /usr/share/R/share/perl/R/Dcf.pm
That is certainly a possibility, but it appears as if none of the perl
packages have been updated recently. Just a few lines into read.dcf()
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dirk,
Dirk Eddelbuettel wrote:
> | I can install and use R 2.10.1 from the CRAN source, so it must be
> | something with a dependency of r-base-core. Does
> |
> | apt-get source -b r-base-core
>
> But that's now how I do it -- I use pbuilder (as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: rkward
Version: 0.5.1-2
Severity: normal
*** Please type your report below this line ***
Hi Thomas,
With the new version of R in unstable,
R version 2.10.0 beta (2009-10-12 r50045)
the help() function does not work as well in rkward as it
Package: r-cran-matrix
Version: 1.2-13-1
Severity: normal
Hi Dirk,
When I install r-cran-matrix version 1.2-13-1 from unstable, it puts it under
/usr/lib/R/site-library ,
whereas if I downgrade to version 1.2-12-1 from testing, it puts it under
/usr/lib/R/library with the
other recommended pack
43 matches
Mail list logo
