Bug#724275: Can't resume from hiberation

2013-10-23 Thread Kevin Vargo
Removing/re-installing uswsusp didn't change the situation.  Removing, of course, made it so the system didn't even try a "resume," re-installing left me back at the ~5 minute waiting before being given the option to skip resume.  I'm not sure why the wait duration is ~5 minutes. Probably unre

Bug#724275: Can't resume from hiberation

2013-10-23 Thread Kevin Vargo
I'm seeing similar issues:  can't resume from hiberation after an update in late September, 2013. dpkg-query -s uswsusp Package: uswsusp Status: install ok installed Priority: optional Section: admin Installed-Size: 575 Maintainer: Rodolfo García Peñas (kix) Architecture: amd64 Version: 1.0+201

Bug#717889: grilo-plugins-0.1: Grilo doesn't work in rhythmbox anymore (0.97 -> 0.99)

2013-07-25 Thread Kevin Vargo
Package: grilo-plugins-0.1 Version: 0.1.19-1 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? upgrade of rhythmbox, etc, from 0.97 -> 0.99 * What exactly did you do (or not do) that was effective (or

Bug#674753: djmount: Cannot read any media from mounted DLNA server

2012-08-04 Thread Kevin Vargo
Hi,   I just updated to djmount 0.71-5 as well, which brought the related libupnp update to 1.6.6.  Thereafter, I'm seeing the same symptoms:  I can `ls' the files, but when i try to actually play files, I get: (src/ixmlparser.c::Parser_getChar), line 0: Error 63 (src/ixmlparser.c::Parser_getCha

Bug#660098: djmount: support /etc/fstab mounting

2012-04-05 Thread Kevin Vargo
>____ > From: Dario Minnucci >To: 660...@bugs.debian.org >Cc: Kevin Vargo >Sent: Monday, April 2, 2012 6:56 PM >Subject: Re: Bug#660098: djmount: support /etc/fstab mounting > > >Hi Kevin, > >First of all, thanks al lot for improving djm

Bug#627020: Info received (Workaround: revert to previous xorg-{core,input-evdev})

2011-07-23 Thread Kevin Vargo
Looks like this/similar has surfaced again.  After the last round of updates, I again cannot start X, getting "no protocol specified" errors. Even with 6-3: ii  fglrx-driver  1:11-6-3  non-free ATI/AMD RadeonHD display driver ii  fglrx-glx

Bug#627020: Workaround: revert to previous xorg-{core,input-evdev}

2011-05-20 Thread Kevin Vargo
Reverted to 1.7.7 core and matching evdev got things working again, using debian-provided fglrx and kernel 2.6.38. # \ls -w1 xserver-xorg-core_1.7.7-13_amd64.deb xserver-xorg-input-evdev_2.3.2-6_amd64.deb So... is there a missing dependency that's not being tracked, maybe?  -- To UNSUBSCRIBE

Bug#627020: #627020 maybe related to #620603

2011-05-20 Thread Kevin Vargo
Maybe Related to:  Bug#620603: linux-image-2.6.38-2-amd64: Console turns to black during boot -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#627020: qa.debian.org: With update of kernel 2.6.38-2, xserver-xorg-core 2:1.10.1-2, fglrx no longer works (11-4, 11-5)

2011-05-16 Thread Kevin Vargo
Package: qa.debian.org Severity: important After upgrading (yesterday, 5/15) to 2.6.38-2, xserver-xorg-core 2:1.10.1-2, fglrx no longer works. X reports only "No protocol specified." I've tried the packaged fglrx (11-4-2), direct installer from ati.com of 11-4 and 11-5(DKMS fails due to kernel l