Bug#722989: (nessun oggetto)

2014-05-30 Thread Francesco Presel
actually no, 0.8.7-2 is my own local version, with applied the patch I have submitted. Being no developer/maintainer, I can only propose patches, not update the package myself, but you can compile this package on your own including this patch (see debian wiki) -- To UNSUBSCRIBE, email to

Bug#722989: proposing patch

2014-01-23 Thread Francesco Presel
; in the latter case the last section is empty. In that case, just skip it (parsing empty sections causes a crash). Author: Francesco Presel f.pre...@alice.it Bug-Debian: http://bugs.debian.org/722989 Last-Update: 2014-01-23 --- a/src/applib/smartctl_parser.cpp +++ b/src/applib/smartctl_parser.cpp

Bug#722989: some more tests

2014-01-22 Thread Francesco Presel
Axel, could it depend on your hardware? From what I've seen, the error only occurs when scanning/adding not SMART capable devices, so perhaps if you only have internal HDDs or SMART capable usb drives you could avoid the crash. Try connecting some old USB or FW enclosure. Apparently, the

Bug#722989: also affected - more info

2013-10-10 Thread Francesco Presel
I am also affected by this bug. I have tried running gsmartcontrol from console, using --no-scan option; this allowed the program to start normally. Next, I added all devices, one by one, trying different methods (ata, scsi, sat,...) I noticed that the problem occurs when I select SCSI, on

Bug#703239: [PATCH proposed] Bug#703239: virtualbox-guest-x11: Bad return status for module build on kernel

2013-03-29 Thread Francesco Presel
I've also been affected by this bug, and have apparently managed to solve it: $ sudo dpkg-reconfigure virtualbox-guest-dkms [...] Building initial module for 3.2.0-4-686-pae Done. [...] $ lsmod|grep vbox vboxvideo 12405 0 drm 146387 1 vboxvideo vboxsf

Bug#703239: [Patch proposed] further information

2013-03-29 Thread Francesco Presel
I enabled 3d acceleration; here's the (partial) output of glxgears and glxinfo. Glxgears is a bit slow, but that's quite usual on VB (I think), and might depend on hardware too. Anyway, things appear to work as expected, in my case. In reply to #55, I did not experience such problems. I'm