Re: Virtualbox install problems on Wheezy with 3.16.0 backports kernel (SOLVED)

[Marc Shapiro]

On 12/28/2014 05:03 AM, Andrei POPESCU wrote:

On Du, 28 dec 14, 15:02:02, Andrei POPESCU wrote:

You would need the package linux-headers-3.16-0.bpo.2-amd64, however,
backports is currently at 3.16.0-0.bpo.4-amd64 so you should probably
install linux-image-3.16.0-0.bpo.4-amd64 and
linux-headers-3.16.0-0.bpo.4-amd64, reboot, and then retry the
Virtualbox module compilation with 'dpkg-reconfigure virtualbox-dkms'.

Sorry, just re-read your OP and you already have these, so it seems like
you just need to reboot before re-trying the virtualbox installation ;)

Kind regards,
Andrei

Andrei,

Thanks.

The problem was the mismatch between linux-headers-3.16-0.bpo.4-amd64 
and linux-image-3.16.0-0.bpo.2-amd64.  Once I installed 
linux-image-3.16.0-0.bpo.4-amd64 and rebooted I was able to run 
'dpkg-reconfigure virtualbox-dkms' and it correctly built the driver.  I 
am still getting the initial error about drives not being accessible, 
but, as you said, that is just from deleted vms that I have not deleted 
through virtualbox.  I just need to delelete them from virtualbox to get 
rid of that error.  ReactOS is now booting correctly.


Marc


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54a10966.2000...@gmail.com

Re: Skipping fsck during boot with systemd?

[Ric Moore]

On 12/28/2014 10:58 AM, Jerry Stuckle wrote:

On 12/28/2014 5:54 AM, Lisi Reisz wrote:

On Sunday 28 December 2014 00:20:20 Celejar wrote:

On Thu, 11 Dec 2014 14:02:52 -0500

Jerry Stuckle  wrote:

On 12/11/2014 1:23 PM, Brian wrote:

On Thu 11 Dec 2014 at 12:11:26 -0500, Jerry Stuckle wrote:

I often give presentations with my notebook.  If I'm lucky, I get
10-15 minutes to set up.  If I'm not, less than 5 minutes (i.e.
another presenter ahead of me).  I use Linux whenever possible, but
since my time slot is limited, I can't wait for fsck to complete.


Your type of situation is well understood and there is sympathy for it.


I appreciate that - but unfortunately, sympathy doesn't solve the problem
:)


Someone may have suggested this, and I know it doesn't really solve the
core problem, but perhaps consider suspending (to disk or ram) instead
of shutting down when you have a presentation scheduled?


Again, that is a way round the problem not a solution to it.

A facility that was available no longer is.  Whether it should be, is an
entirely different question.

Lisi




Lisi,

While I agree it's only a way around a problem and not a solution, I do
appreciate people trying to help out.

And while I would prefer a solution, it looks like that's not going to
happen.  So, unfortunately, after many years as a Debian user, I'm
looking at other options.  My clients are looking, also, although not
every one has made the decision to switch yet.


What's wrong with sticking with Wheezy for the next couple of years?? I 
haven't had my ext4 file system want to fsck in eons. Several times I 
have MADE it do a check on the next boot, just to check, and a Tbyte of 
storage was fscked in about 10-15 seconds.


Besides, I never did buy that bit about doing a complete dist-upgrade to 
Jessie (testing!) and then expecting to do a presentation to clients 
without a complete shakedown. I'd shoot myself first. I know you know 
better.


Can we not let this pitiful excuse for a thread JUST DIE?? :/ Ric





--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54a0f323.5050...@gmail.com

Re: Testing needed for binutils security update

[Alexander Cherepanov]

On 2014-12-26 16:02, Luciano Bello wrote:

On Tuesday 23 December 2014 13.30.22 Alexander Cherepanov wrote:

CVEs were assigned only to a small number of issues so far and I'm not
sure it's worth it to fix them without fixing others.


That's true, but we have to draw the line somewhere. The bigger the patches to
backport, the easier to introduce regressions.

I suggest to patch in this DSA those issues with a CVE id. We can later release
a new DSA with the next batch of patches.


Sure, whatever is more convenient for you.


Or did you fix
others too? You can find more issues and fixes in two upstream bugs:

https://sourceware.org/bugzilla/show_bug.cgi?id=17512
https://sourceware.org/bugzilla/show_bug.cgi?id=17531

and the process is not over, new issues are still being found and fixed.


The suggested package for this DSA fixes some of the PoC in these issues.


I guess these are exactly the issues CVEs were assigned for.


Sorry if it's not easy to track. I'd like to make it easier for Debian.
Any feedback on the process is welcome.


Indeed, it is not easy to track, but I don't know how to improve that.


If you (or others) get any ideas please let me know. I hope to fuzz more 
programs in the future and I'm afraid it will be something similar.



It could be great to distinguish those critical crashes for security for those
less critical. I understand this might be complicated, tho.


There are some easy to implement ideas, e.g. to filter out non-security 
issues like null derefs.


Would it be useful to sort issues with the help of the "exploitable" GDB 
extension:

https://github.com/jfoote/exploitable
?


BTW, the situation with elfutils is somewhat similar, the bug report is
here:
https://bugzilla.redhat.com/show_bug.cgi?id=1170810


I'm reporting this issue to our elfutils maintainer to keep the track of it.


Thanks!


Do
you know if there is a plan to get CVE id for this/these issue/s?


Probably we need to at least match fixes with samples before requesting 
CVEs. I've written some thoughts here: 
https://lists.fedorahosted.org/pipermail/elfutils-devel/2014-December/004504.html 
. Feel free to comment.


--
Alexander Cherepanov


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54a0d3a1.4000...@mccme.ru

Re: /var/lib/dpkg/status strangeness

[Chris Bannister]

On Sun, Dec 28, 2014 at 10:15:36PM -0500, Cindy-Sue Causey wrote:
> The gist of whatever I read was that all we could do was hope it never
> happened to anything crucially important.. I am so sorry that that is
> as much as I remember with chances I'll ever stumble back on the same
> being pretty slim.
> 
> It's possible it was about something like rsync.. I've been relying on
> rsync regularly as I keep working on polishing my Debian Pure
> technique.. I do remember thinking it sure bytes that backups we hope
> will cover our backsides actually stand a known possibility for being
> disastrous themselves.. I can remember mentally visualizing the file
> hierarchy while thinking that every single file in it, no matter how
> critical, was 100% equally vulnerable at those times of transfers.
> 
> Couldn't think of the words then but "integrity checks" or some such
> similar comes to mind now...

I think that CRC would catch anything in that regard, the original file
would have to be 'corrupt' to start with.

http://en.wikipedia.org/wiki/Cyclic_redundancy_check

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141229040110.GA32656@tal

Re: /var/lib/dpkg/status strangeness

[Cindy-Sue Causey]

On 12/26/14, Bob Proulx  wrote:
>
> It feels more like a random machine failure due to the consumer grade
> hardware which we are all using these days.  It isn't required to run
> faster than the bear.  It is only required to run faster than the
> other person who is also running from the bear.  Therefore hardware
> vendors don't make great reliable Unix server quality hardware these
> days.  Instead it is mosly MS quality hardware.  Almost no desktops
> have parity anymore for example.  Because of this the hardware just
> isn't ultimately reliable.  You will drive yourself crazy if you try
> to chase down every odd thing.


Am reading through the latest on this thread again. Just had the same
thought I did while reading the original emails for it. Somewhere in
the last couple months... I read "something somewhere" about that lost
or mixed up packets (?) do and will happen regardless of our very best
efforts.

The gist of whatever I read was that all we could do was hope it never
happened to anything crucially important.. I am so sorry that that is
as much as I remember with chances I'll ever stumble back on the same
being pretty slim.

It's possible it was about something like rsync.. I've been relying on
rsync regularly as I keep working on polishing my Debian Pure
technique.. I do remember thinking it sure bytes that backups we hope
will cover our backsides actually stand a known possibility for being
disastrous themselves.. I can remember mentally visualizing the file
hierarchy while thinking that every single file in it, no matter how
critical, was 100% equally vulnerable at those times of transfers.

Couldn't think of the words then but "integrity checks" or some such
similar comes to mind now...

Thinking out loud.. :)

Cindy

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with plastic sporks *


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAO1P-kB-hoDSNqrq=vpoGZg7GAK9HatRxLf-dfqsgWVfPvwT=w...@mail.gmail.com

Re: wifi connection tool?

[Vincent Lefevre]

On 2014-12-29 01:07:48 +0100, Vincent Lefevre wrote:
> On 2014-12-28 12:43:19 -0800, Don Armstrong wrote:
> > On Sun, 28 Dec 2014, Vincent Lefevre wrote:
> > > Is there a wifi connection tool that can reconnect *automatically*
> > > after a disconnection? (This can happen several times per hour, though
> > > the wifi quality is not very bad.)
> > > 
> > > I'm currently using wicd, but it doesn't reconnect automatically.
> > 
> > wpa_supplicant should reconnect automatically, which is what wicd uses.
> > If not, run wpa_cli and see what the debugging output is.
> 
> When wpa_cli is running and a disconnection occurs, I get:
> 
> <3>CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=0
> <3>CTRL-EVENT-TERMINATING 
> Connection to wpa_supplicant lost - trying to reconnect
> 
> and wpa_supplicant is no longer running.
[...]

This was when the GUI was running.

I had also done a check a few days ago when the GUI was not running,
and also got a disconnection, and thought that there was the same
problem. Actually I think that I didn't wait for long enough. Indeed,
a few minutes ago, with wpa_cli running, I could see messages in
real time (which helps a lot since this shows some activity despite
temporary failures):

<3>CTRL-EVENT-SCAN-RESULTS 
<3>CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=0
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>Trying to associate with 00:1f:33:89:73:4e (SSID='lefevre' freq=2472 MHz)
<3>Association request to the driver failed
<3>CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=3 locally_generated=1
<3>CTRL-EVENT-TERMINATING 
Connection to wpa_supplicant lost - trying to reconnect
Connection to wpa_supplicant re-established
<3>Authentication with 00:1f:33:89:73:4e timed out.
<3>CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=3 locally_generated=1
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>Trying to associate with 00:1f:33:89:73:4e (SSID='lefevre' freq=2472 MHz)
<3>Association request to the driver failed
<3>Authentication with 00:1f:33:89:73:4e timed out.
<3>CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=3 locally_generated=1
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="lefevre" auth_failures=1 
duration=10 reason=CONN_FAILED
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>WPS-AP-AVAILABLE 
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="lefevre"
<3>Trying to associate with 00:1f:33:89:73:4e (SSID='lefevre' freq=2472 MHz)
<3>Association request to the driver failed
<3>Associated with 00:1f:33:89:73:4e
<3>WPA: Key negotiation completed with 00:1f:33:89:73:4e [PTK=CCMP GTK=CCMP]
<3>CTRL-EVENT-CONNECTED - Connection to 00:1f:33:89:73:4e completed [id=0 
id_str=]

In /var/log/wicd/wicd.log, I now have:

[...]
2014/12/29 01:25:32 :: ifconfig wlan0 0.0.0.0 
2014/12/29 01:25:32 :: /sbin/ip route flush dev wlan0
2014/12/29 01:25:32 :: ifconfig wlan0 down
2014/12/29 01:25:32 :: ifconfig wlan0 up
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/avahi-daemon with 
params 
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/bridge with params 
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/bridge returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/wireless-tools 
with params 
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/wireless-tools returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/wpasupplicant with 
params 
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2014/12/29 01:25:32 :: wpa_cli -i wlan0 terminate
2014/12/29 01:25:32 :: Executing /etc/network/if-down.d/avahi-autoipd with 
params 
2014/12/29 01:25:32 :: /etc/network/if-down.d/avahi-autoipd returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-down.d/bind9 with params 
2014/12/29 01:25:32 :: /etc/network/if-down.d/bind9 returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-down.d/postfix with params 
2014/12/29 01:25:32 :: /etc/network/if-down.d/postfix returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-down.d/resolvconf with params 
2014/12/29 01:25:32 :: /etc/network/if-down.d/resolvconf returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-down.d/upstart with params 
2014/12/29 01:25:32 :: /etc/network/if-down.d/upstart returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-down.d/wpasupplicant with 
params 
2014/12/29 01:25:32 :: /etc/network/if-down.d/wpasupplicant returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/avahi-daemon with 
params 
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/bridge with params 
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/bridge returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/wireless-tools 
with params 
2014/12/29 01:25:32 :: /etc/network/if-pos

Re: Possible incompatibility between wheezy gnome and wheezy-backports libreoffice

[Cindy-Sue Causey]

On 12/28/14, Miguel Ortiz Lombardía
 wrote:
>
> Hi,
>
> Not true in the case that I reported. Even after apt-get update, I get
> the same messages and gnome is marked to be removed... Looks like a
> different problem that the one found by Chris.


Some of this, *not all*, but some of this I found to be about not
having the right repository in my /etc/apt/sources.list.. Other
package managers have their own place where you would address the
same..

It's that "held back" part that *finally* clued me in at some point.
As soon as I do a quick tweak on that /etc/apt/sources.list by adding
the additional necessary repository and THEN *apt-get update*, I don't
see the message anymore.

Because of what I'm doing here, basically learning by (usually
accidentally) destroying then fixing, I've had the opportunity to
therefore "harmlessly" also try *dpkg -i --force-depends
[package-name]. SEEMS LIKE it was one of those "don't try this at
home, kids", last resort kinds of deal. It actually fixed something
for me in a system I eventually killed off permanently some other way
instead...

Another "thinking out loud"... :)

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with plastic sporks *


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAO1P-kDn6+x9RQraPXLcuwvXHdJh=bnvFkJfbhUA=igbmaf...@mail.gmail.com

Re: wifi connection tool?

[Vincent Lefevre]

On 2014-12-28 22:13:30 +0100, Hans wrote:
> Am Sonntag, 28. Dezember 2014, 21:26:20 schrieb Vincent Lefevre:
> > Is there a wifi connection tool that can reconnect *automatically*
> > after a disconnection? (This can happen several times per hour,
> > though the wifi quality is not very bad.)
> > 
> > I'm currently using wicd, but it doesn't reconnect automatically.
> > 
> Did you set "automatically connection" in the gui?

Yes.

> Here it is working, when I activate this.

Here it seems to work, i.e. when I boot the machine, wicd
automatically connects to this network. But in the case of a
disconnection from the kernel, it seems that wicd interprets
this as a disconnection by the user, so that it terminates
wpa_supplicant and does not try to reconnect.

> However, I did not test it with the demon or the ncurses 
> option.

This option is available in the GUI, but AFAIK, it is for the daemon.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141229001321.gc20...@xvii.vinc17.org

Re: wifi connection tool?

[Vincent Lefevre]

On 2014-12-28 12:43:19 -0800, Don Armstrong wrote:
> On Sun, 28 Dec 2014, Vincent Lefevre wrote:
> > Is there a wifi connection tool that can reconnect *automatically*
> > after a disconnection? (This can happen several times per hour, though
> > the wifi quality is not very bad.)
> > 
> > I'm currently using wicd, but it doesn't reconnect automatically.
> 
> wpa_supplicant should reconnect automatically, which is what wicd uses.
> If not, run wpa_cli and see what the debugging output is.

When wpa_cli is running and a disconnection occurs, I get:

<3>CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=0
<3>CTRL-EVENT-TERMINATING 
Connection to wpa_supplicant lost - trying to reconnect

and wpa_supplicant is no longer running.

According to /var/log/syslog, the disconnection starts with the
following messages:

Dec 28 22:41:19 xvii kernel: [21420.418746] wlan0: deauthenticated from 
00:1f:33:89:73:4e (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)
Dec 28 22:41:19 xvii kernel: [21420.06] cfg80211: Calling CRDA to update 
world regulatory domain
Dec 28 22:41:19 xvii kernel: [21420.831396] cfg80211: Calling CRDA to update 
world regulatory domain

In /var/log/wicd/wicd.log I have:

[...]
2014/12/28 22:41:17 :: ifconfig wlan0
2014/12/28 22:41:17 :: iwconfig wlan0
2014/12/28 22:41:19 :: ifconfig wlan0
2014/12/28 22:41:19 :: iwconfig wlan0
2014/12/28 22:41:21 :: ifconfig wlan0
2014/12/28 22:41:21 :: iwconfig wlan0
2014/12/28 22:41:21 :: Forced disconnect on
2014/12/28 22:41:21 :: Executing /etc/network/if-down.d/avahi-autoipd with 
params 
2014/12/28 22:41:21 :: /etc/network/if-down.d/avahi-autoipd returned 0
2014/12/28 22:41:21 :: Executing /etc/network/if-down.d/bind9 with params 
2014/12/28 22:41:21 :: /etc/network/if-down.d/bind9 returned 0
2014/12/28 22:41:21 :: Executing /etc/network/if-down.d/postfix with params 
2014/12/28 22:41:21 :: /etc/network/if-down.d/postfix returned 0
2014/12/28 22:41:21 :: Executing /etc/network/if-down.d/resolvconf with params 
2014/12/28 22:41:21 :: /etc/network/if-down.d/resolvconf returned 0
2014/12/28 22:41:21 :: Executing /etc/network/if-down.d/upstart with params 
2014/12/28 22:41:21 :: /etc/network/if-down.d/upstart returned 0
2014/12/28 22:41:21 :: Executing /etc/network/if-down.d/wpasupplicant with 
params 
2014/12/28 22:41:21 :: /etc/network/if-down.d/wpasupplicant returned 0
2014/12/28 22:41:21 :: attempting to set hostname with dhclient
2014/12/28 22:41:21 :: using dhcpcd or another supported client may work better
2014/12/28 22:41:21 :: /sbin/dhclient -v -r wlan0
[...]
2014/12/28 22:41:22 :: ifconfig wlan0 0.0.0.0 
2014/12/28 22:41:22 :: /sbin/ip route flush dev wlan0
2014/12/28 22:41:22 :: ifconfig wlan0 down
2014/12/28 22:41:22 :: ifconfig wlan0 up
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/avahi-daemon with 
params 
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/bridge with params 
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/bridge returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/wireless-tools 
with params 
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/wireless-tools returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/wpasupplicant with 
params 
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2014/12/28 22:41:22 :: wpa_cli -i wlan0 terminate
2014/12/28 22:41:22 :: Executing /etc/network/if-down.d/avahi-autoipd with 
params 
2014/12/28 22:41:22 :: /etc/network/if-down.d/avahi-autoipd returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-down.d/bind9 with params 
2014/12/28 22:41:22 :: /etc/network/if-down.d/bind9 returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-down.d/postfix with params 
2014/12/28 22:41:22 :: /etc/network/if-down.d/postfix returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-down.d/resolvconf with params 
2014/12/28 22:41:22 :: /etc/network/if-down.d/resolvconf returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-down.d/upstart with params 
2014/12/28 22:41:22 :: /etc/network/if-down.d/upstart returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-down.d/wpasupplicant with 
params 
2014/12/28 22:41:22 :: /etc/network/if-down.d/wpasupplicant returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/avahi-daemon with 
params 
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/bridge with params 
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/bridge returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/wireless-tools 
with params 
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/wireless-tools returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/wpasupplicant with 
params 
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/wpasupplicant returned 0
[...]

If I understand correctly, wi

Re: Possible incompatibility between wheezy gnome and wheezy-backports libreoffice

[Miguel Ortiz Lombardía]

Hi,

Not true in the case that I reported. Even after apt-get update, I get
the same messages and gnome is marked to be removed... Looks like a
different problem that the one found by Chris.

Cheers,

   Miguel

El 28/12/14 a las 19:17, Sven Joachim escribió:
> On 2014-12-28 18:40 +0100, Chris Swenson wrote:
> 
>> I'm having the same issue with libreoffice. I cannot upgrade it because
>> it is looking for libc6 >= 2.19, which is unavailable. It appears it was
>> compiled with libc6 at this version instead of the one available in
>> debian (2.13-38+deb7u6). Perhaps we should contact the libreoffice
>> maintainers?
> 
> That's probably not necessary, this mistake seems to have been corrected
> in version 1:4.3.3-2~bpo70+2[1].
> 
> Cheers,
>Sven
> 
> 
> 1. https://lists.debian.org/debian-backports-changes/2014/12/msg00043.html
> 
> 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54a0780c.8050...@igs.cnrs-mrs.fr

Re: wifi connection tool?

[Hans]

Am Sonntag, 28. Dezember 2014, 21:26:20 schrieb Vincent Lefevre:
> Is there a wifi connection tool that can reconnect *automatically*
> after a disconnection? (This can happen several times per hour,
> though the wifi quality is not very bad.)
> 
> I'm currently using wicd, but it doesn't reconnect automatically.
> 
Did you set "automatically connection" in the gui? Here it is working, when I 
activate this. However, I did not test it with the demon or the ncurses 
option.

Best 

Hans


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/3013225.5AvPbNJm1y@protheus2

Re: wifi connection tool?

[Don Armstrong]

On Sun, 28 Dec 2014, Vincent Lefevre wrote:
> Is there a wifi connection tool that can reconnect *automatically*
> after a disconnection? (This can happen several times per hour, though
> the wifi quality is not very bad.)
> 
> I'm currently using wicd, but it doesn't reconnect automatically.

wpa_supplicant should reconnect automatically, which is what wicd uses.
If not, run wpa_cli and see what the debugging output is.


-- 
Don Armstrong  http://www.donarmstrong.com

Nearly all men can stand adversity, but if you really want to test his
character, give him power.
 -- Abraham Lincoln


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141228204319.gz12...@teltox.donarmstrong.com

wifi connection tool?

[Vincent Lefevre]

Is there a wifi connection tool that can reconnect *automatically*
after a disconnection? (This can happen several times per hour,
though the wifi quality is not very bad.)

I'm currently using wicd, but it doesn't reconnect automatically.

The tool must handle wifi *only*, not Ethernet (which I use at some
places and for which I have my own, specific set-up).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141228202620.ga20...@xvii.vinc17.org

Re: udev madness ?

[Cindy-Sue Causey]

On 12/28/14, Renaud  OLGIATI  wrote:
> On Sat, 27 Dec 2014 17:34:19 -0800
> Patrick Bartek  wrote:
>
>> Do other cards fail to mount, too?  Have you tried another card reader?
>> Old card or new?
>
> Other cards mount in that reader;
>
< snipped >
>


Age or size of *both* cards *AND* readers can make a difference. It's
been a long time since I ran into that issue myself so I'm not
remembering exact details. I *do* remember going the route you're
going. Could find it as recognized hardware via multiple different
searches, but it just wouldn't work.

Went that route after a reader had been reading cards then stopped.
Smacked myself *slightly* because one factor was I had just bought the
card not being read. Had coincidentally ordered a newer reader that
was sitting to the side unused (or something like that). Pulled it
out, plugged it, and things worked great.

Somewhere along the line also discovered that my card readers need to
be plugged in directly (to laptop in that case) and not used via a USB
port hub. There, again, they showed up in hardware [output] but
wouldn't work as expected. Disclaimer there is I usually end up with
extremely bottom dollar readers and hubs which would likely also play
a notable part in any of this type of issue.

Just thinking out loud.. :)

Cindy

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* my dog runs with plastic bags. #truestory *


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cao1p-kayakvnszslpnn5tyc8bpmgngh-ewsm16ugbmjz97u...@mail.gmail.com

Re: Possible incompatibility between wheezy gnome and wheezy-backports libreoffice

[Sven Joachim]

On 2014-12-28 18:40 +0100, Chris Swenson wrote:

> I'm having the same issue with libreoffice. I cannot upgrade it because
> it is looking for libc6 >= 2.19, which is unavailable. It appears it was
> compiled with libc6 at this version instead of the one available in
> debian (2.13-38+deb7u6). Perhaps we should contact the libreoffice
> maintainers?

That's probably not necessary, this mistake seems to have been corrected
in version 1:4.3.3-2~bpo70+2[1].

Cheers,
   Sven


1. https://lists.debian.org/debian-backports-changes/2014/12/msg00043.html


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87r3vjej0i@turtle.gmx.de

Re: udev madness ?

[Patrick Bartek]

On Sun, 28 Dec 2014, Renaud (Ron) OLGIATI wrote:

> On Sat, 27 Dec 2014 17:34:19 -0800
> Patrick Bartek  wrote:
> 
> > > I plug a sd card in the USB reader; the system does recognize it,
> > > since I get the following in dmesg:
> > > # dmesg -c | tail -n25
> > > [452776.255955] sd 8:0:0:0: [sde] 3842048 512-byte logical blocks:
> > > (1.96 GB/1.83 GiB) [452776.261515] sd 8:0:0:0: [sde] No Caching
> > > mode page found [452776.261522] sd 8:0:0:0: [sde] Assuming drive
> > > cache: write through [452776.267555] sd 8:0:0:0: [sde] No Caching
> > > mode page found [452776.267561] sd 8:0:0:0: [sde] Assuming drive
> > > cache: write through [452776.269260]  sde: sde1
> > > ls confirms it is recognized:
> > > # ls -l /dev/sde*
> > > brw-rw---T 1 root floppy 8, 64 Dec 27 17:01 /dev/sde
> > > brw-rw---T 1 root floppy 8, 65 Dec 27 17:01 /dev/sde1
> > > Why does it fail to auto-mount, and does not appear in Thunar or
> > > Pcmanfm ?
> > > udev gone mad ?  
>  
> > Do other cards fail to mount, too?  Have you tried another card
> > reader?  Old card or new?
> 
> Other cards mount in that reader; 
>  
> > What does lsusb & ls /media report?  With just the reader plugged
> > in. With the card, too?
> 
> lsusb reports the same with or without the card :
> 
> # lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 002: ID 2109:3431  
> Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 004: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
> Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card
> Reader/Writer Bus 005 Device 002: ID 1e4e:0102  
> Bus 005 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port
> HUB Bus 006 Device 002: ID 413c:2107 Dell Computer Corp. 
> Bus 006 Device 003: ID 046d:c408 Logitech, Inc. Marble Mouse
> (4-button) Bus 004 Device 003: ID 03f0:2504 Hewlett-Packard DeskJet
> F4200 series
> 
> Same for ls /media, in both cases :
> 
> # ls /media
> cdrom  cdrom0  floppy  floppy0
>  
> > Which OS and GUI?
> 
> Debian 7.7.0 Xfce

Have you tried inserting the card in the reader, then plugging the
reader into the usb port?  That is, if it's an external reader.  Have
you cleaned the contacts? 

Your card could have a error (or errors) on the filesystem that might
prevent it from being mounted, while still being recognized.  Had it
happen. Two days ago, in fact.  Running dosfsck and reformatting solved
the problem.

At worse, you could write a udev rule to mount that specific card.

B


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141228093339.02235...@debian7.boseck208.net

Re: Possible incompatibility between wheezy gnome and wheezy-backports libreoffice

[Chris Swenson]

I'm having the same issue with libreoffice. I cannot upgrade it because
it is looking for libc6 >= 2.19, which is unavailable. It appears it was
compiled with libc6 at this version instead of the one available in
debian (2.13-38+deb7u6). Perhaps we should contact the libreoffice
maintainers?

-- 
– Chris
ch...@cswenson.com
cs.swen...@gmail.com


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54a04076.1030...@cswenson.com

Re: Skipping fsck during boot with systemd?

[Jerry Stuckle]

On 12/28/2014 5:54 AM, Lisi Reisz wrote:
> On Sunday 28 December 2014 00:20:20 Celejar wrote:
>> On Thu, 11 Dec 2014 14:02:52 -0500
>>
>> Jerry Stuckle  wrote:
>>> On 12/11/2014 1:23 PM, Brian wrote:
 On Thu 11 Dec 2014 at 12:11:26 -0500, Jerry Stuckle wrote:
> I often give presentations with my notebook.  If I'm lucky, I get
> 10-15 minutes to set up.  If I'm not, less than 5 minutes (i.e.
> another presenter ahead of me).  I use Linux whenever possible, but
> since my time slot is limited, I can't wait for fsck to complete.

 Your type of situation is well understood and there is sympathy for it.
>>>
>>> I appreciate that - but unfortunately, sympathy doesn't solve the problem
>>> :)
>>
>> Someone may have suggested this, and I know it doesn't really solve the
>> core problem, but perhaps consider suspending (to disk or ram) instead
>> of shutting down when you have a presentation scheduled?
> 
> Again, that is a way round the problem not a solution to it.
> 
> A facility that was available no longer is.  Whether it should be, is an 
> entirely different question.
> 
> Lisi
> 
> 

Lisi,

While I agree it's only a way around a problem and not a solution, I do
appreciate people trying to help out.

And while I would prefer a solution, it looks like that's not going to
happen.  So, unfortunately, after many years as a Debian user, I'm
looking at other options.  My clients are looking, also, although not
every one has made the decision to switch yet.

Jerry


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54a028b1.9020...@gmail.com

Business proposition

[Ron Walters]

hello, 

My name is Ron Walters and I am the advertising representative of a 
number of leading online companies. 
These companies operate in various fields, that include the gaming 
industry, sports activities, international flower delivery and various leisure 
activity fields. 
I was impressed by your internet site http://www.debian.org and would 
like to discuss the possibility of you hosting advertising space for my 
clients on your site. 
We are interested in various options that include textural 
advertisements, and Banner space. 
If you are interested please contact me and we can discuss all the 
possibilities in detail. 

Looking forward to doing business with you.

Best regards,

Ron Walters
Client side acquisition
http://www.igamingseo.net

Re: Virtualbox install problems on Wheezy with 3.16.0 backports kernel

[Andrei POPESCU]

On Du, 28 dec 14, 15:02:02, Andrei POPESCU wrote:
> 
> You would need the package linux-headers-3.16-0.bpo.2-amd64, however, 
> backports is currently at 3.16.0-0.bpo.4-amd64 so you should probably 
> install linux-image-3.16.0-0.bpo.4-amd64 and 
> linux-headers-3.16.0-0.bpo.4-amd64, reboot, and then retry the 
> Virtualbox module compilation with 'dpkg-reconfigure virtualbox-dkms'.

Sorry, just re-read your OP and you already have these, so it seems like 
you just need to reboot before re-trying the virtualbox installation ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Virtualbox install problems on Wheezy with 3.16.0 backports kernel

[Andrei POPESCU]

On Sb, 27 dec 14, 21:27:40, Marc Shapiro wrote:
> dpkg: warning: unable to delete old directory
> '/usr/src/virtualbox-4.1.18/vboxdrv': Directory not empty
> dpkg: warning: unable to delete old directory '/usr/src/virtualbox-4.1.18':
> Directory not empty

You might want to clean this up.

> Building only for 3.16-0.bpo.2-amd64
> Module build for the currently running kernel was skipped since the
> kernel source for this kernel does not seem to be installed.

You would need the package linux-headers-3.16-0.bpo.2-amd64, however, 
backports is currently at 3.16.0-0.bpo.4-amd64 so you should probably 
install linux-image-3.16.0-0.bpo.4-amd64 and 
linux-headers-3.16.0-0.bpo.4-amd64, reboot, and then retry the 
Virtualbox module compilation with 'dpkg-reconfigure virtualbox-dkms'.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Virtualbox install problems on Wheezy with 3.16.0 backports kernel

[Andrei POPESCU]

On Sb, 27 dec 14, 20:29:38, Marc Shapiro wrote:
> I am trying to test ReactOS in Virtualbox.  When I fired up virtualbox I
> received errors saying:
> -
> 
> One or more virtual hard disks, CD/DVD or floppy media are not currently
> accessible. As a result, you will not be able to operate virtual machines
> that use these media until they become accessible later.
> 
> Press Check to open the Virtual Media Manager window and see what media are
> inaccessible, or press Ignore to ignore this message.
> 
> --

Just as a side-note, this message is trying to tell you that you had 
setup a virtual drive on some media (e.g. partition) that is now 
unaccessible (e.g. not mounted). This doesn't have much to do with your 
Virtualbox installation...

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: SDHC error - which package to log against

[Andrei POPESCU]

On Du, 28 dec 14, 11:34:17, Allan Smith wrote:
> Dec 28 10:37:26 bilbo vmunix: [  418.450525] sd 7:0:0:0: Device 
> offlined
> - not ready after error recovery
> Dec 28 10:37:26 bilbo vmunix: [  418.453827] sd 7:0:0:0: [sdc] Unhandled
> error code
> Dec 28 10:37:26 bilbo vmunix: [  418.453829] sd 7:0:0:0: [sdc]  Result:
> hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> Dec 28 10:37:26 bilbo vmunix: [  418.453831] sd 7:0:0:0: [sdc] CDB:
> Write(10): 2a 00 01 45 4b a0 00 00 f0 00
> Dec 28 10:37:26 bilbo vmunix: [  418.453835] end_request: I/O error, dev
> sdc, sector 21318560
> Dec 28 10:37:26 bilbo vmunix: [  418.454571] sd 7:0:0:0: [sdc] Unhandled
> error code
> Dec 28 10:37:26 bilbo vmunix: [  418.454572] sd 7:0:0:0: [sdc]  Result:
> hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> Dec 28 10:37:26 bilbo vmunix: [  418.454574] sd 7:0:0:0: [sdc] CDB:
> Write(10): 2a 00 01 45 4c 90 00 00 f0 00
> Dec 28 10:37:26 bilbo vmunix: [  418.454577] end_request: I/O error, dev
> sdc, sector 21318800
> Dec 28 10:37:26 bilbo vmunix: [  418.466414] FAT-fs (sdc1): Directory
> bread(block 1706048) failed

Those look like hardware errors to me...

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

SDHC error - which package to log against

[Allan Smith]

I get errors using SDHC cards with my internal card reader. I wanted to
report a bug on this but I need the package ID. I think that the module
used to support this is xhci_hcd but which package is this?

Version info:
Distributor ID: Debian
Description:Debian GNU/Linux 7.7 (wheezy)
Release:7.7
Codename:   wheezy
Linux bilbo 3.2.0-4-686-pae #1 SMP Debian 3.2.63-2+deb7u2 i686 GNU/Linux


Dec 28 10:36:01 bilbo vmunix: [  333.453153] sd 7:0:0:0: Attached scsi
generic sg3 type 0
Dec 28 10:36:01 bilbo vmunix: [  333.998376] sd 7:0:0:0: [sdc] 31116288
512-byte logical blocks: (15.9 GB/14.8 GiB)
Dec 28 10:36:01 bilbo vmunix: [  333.998745] sd 7:0:0:0: [sdc] Write
Protect is off
Dec 28 10:36:01 bilbo vmunix: [  333.998746] sd 7:0:0:0: [sdc] Mode
Sense: 03 00 00 00
Dec 28 10:36:01 bilbo vmunix: [  333.999111] sd 7:0:0:0: [sdc] No
Caching mode page found
Dec 28 10:36:01 bilbo vmunix: [  333.999114] sd 7:0:0:0: [sdc] Assuming
drive cache: write through
Dec 28 10:36:01 bilbo vmunix: [  334.001029] sd 7:0:0:0: [sdc] No
Caching mode page found
Dec 28 10:36:01 bilbo vmunix: [  334.001031] sd 7:0:0:0: [sdc] Assuming
drive cache: write through
Dec 28 10:36:01 bilbo vmunix: [  334.002460]  sdc: sdc1
Dec 28 10:36:01 bilbo vmunix: [  334.004001] sd 7:0:0:0: [sdc] No
Caching mode page found
Dec 28 10:36:01 bilbo vmunix: [  334.004003] sd 7:0:0:0: [sdc] Assuming
drive cache: write through
Dec 28 10:36:01 bilbo vmunix: [  334.004005] sd 7:0:0:0: [sdc] Attached
SCSI removable disk
Dec 28 10:36:19 bilbo vmunix: [  351.193802] FAT-fs (sdc1): utf8 is not
a recommended IO charset for FAT filesystems, filesystem will be case
sensitive!
Dec 28 10:36:55 bilbo vmunix: [  387.592367] usb 3-7: USB disconnect,
device number 4
Dec 28 10:37:26 bilbo vmunix: [  418.450525] sd 7:0:0:0: Device offlined
- not ready after error recovery
Dec 28 10:37:26 bilbo vmunix: [  418.453827] sd 7:0:0:0: [sdc] Unhandled
error code
Dec 28 10:37:26 bilbo vmunix: [  418.453829] sd 7:0:0:0: [sdc]  Result:
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec 28 10:37:26 bilbo vmunix: [  418.453831] sd 7:0:0:0: [sdc] CDB:
Write(10): 2a 00 01 45 4b a0 00 00 f0 00
Dec 28 10:37:26 bilbo vmunix: [  418.453835] end_request: I/O error, dev
sdc, sector 21318560
Dec 28 10:37:26 bilbo vmunix: [  418.454571] sd 7:0:0:0: [sdc] Unhandled
error code
Dec 28 10:37:26 bilbo vmunix: [  418.454572] sd 7:0:0:0: [sdc]  Result:
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec 28 10:37:26 bilbo vmunix: [  418.454574] sd 7:0:0:0: [sdc] CDB:
Write(10): 2a 00 01 45 4c 90 00 00 f0 00
Dec 28 10:37:26 bilbo vmunix: [  418.454577] end_request: I/O error, dev
sdc, sector 21318800
Dec 28 10:37:26 bilbo vmunix: [  418.466414] FAT-fs (sdc1): Directory
bread(block 1706048) failed

lsudb output:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0471:2034 Philips (or NXP) Webcam SPC530NC
Bus 003 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 003 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1419762857.5813.4.camel@bilbo

Re: udev madness ?

[Ron]

On Sat, 27 Dec 2014 17:34:19 -0800
Patrick Bartek  wrote:

> > I plug a sd card in the USB reader; the system does recognize it,
> > since I get the following in dmesg:
> > # dmesg -c | tail -n25
> > [452776.255955] sd 8:0:0:0: [sde] 3842048 512-byte logical blocks:
> > (1.96 GB/1.83 GiB) [452776.261515] sd 8:0:0:0: [sde] No Caching mode
> > page found [452776.261522] sd 8:0:0:0: [sde] Assuming drive cache:
> > write through [452776.267555] sd 8:0:0:0: [sde] No Caching mode page
> > found [452776.267561] sd 8:0:0:0: [sde] Assuming drive cache: write
> > through [452776.269260]  sde: sde1
> > ls confirms it is recognized:
> > # ls -l /dev/sde*
> > brw-rw---T 1 root floppy 8, 64 Dec 27 17:01 /dev/sde
> > brw-rw---T 1 root floppy 8, 65 Dec 27 17:01 /dev/sde1
> > Why does it fail to auto-mount, and does not appear in Thunar or
> > Pcmanfm ?
> > udev gone mad ?  
 
> Do other cards fail to mount, too?  Have you tried another card reader?  Old 
> card or new?

Other cards mount in that reader; 
 
> What does lsusb & ls /media report?  With just the reader plugged in.
> With the card, too?

lsusb reports the same with or without the card :

# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 2109:3431  
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 005 Device 002: ID 1e4e:0102  
Bus 005 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 006 Device 002: ID 413c:2107 Dell Computer Corp. 
Bus 006 Device 003: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 004 Device 003: ID 03f0:2504 Hewlett-Packard DeskJet F4200 series

Same for ls /media, in both cases :

# ls /media
cdrom  cdrom0  floppy  floppy0
 
> Which OS and GUI?

Debian 7.7.0 Xfce 

 
Cheers,
 
Ron.
-- 
 A "critic" is a man who creates nothing and thereby feels qualified
  to judge the work of creative men. There is logic in this; he is unbiased
   -- he hates all creative people equally.

   -- http://www.olgiati-in-paraguay.org --
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141228080358.59d2b...@ron.cerrocora.org

Re: Skipping fsck during boot with systemd?

[Lisi Reisz]

On Sunday 28 December 2014 00:20:20 Celejar wrote:
> On Thu, 11 Dec 2014 14:02:52 -0500
>
> Jerry Stuckle  wrote:
> > On 12/11/2014 1:23 PM, Brian wrote:
> > > On Thu 11 Dec 2014 at 12:11:26 -0500, Jerry Stuckle wrote:
> > >> I often give presentations with my notebook.  If I'm lucky, I get
> > >> 10-15 minutes to set up.  If I'm not, less than 5 minutes (i.e.
> > >> another presenter ahead of me).  I use Linux whenever possible, but
> > >> since my time slot is limited, I can't wait for fsck to complete.
> > >
> > > Your type of situation is well understood and there is sympathy for it.
> >
> > I appreciate that - but unfortunately, sympathy doesn't solve the problem
> > :)
>
> Someone may have suggested this, and I know it doesn't really solve the
> core problem, but perhaps consider suspending (to disk or ram) instead
> of shutting down when you have a presentation scheduled?

Again, that is a way round the problem not a solution to it.

A facility that was available no longer is.  Whether it should be, is an 
entirely different question.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201412281054.24677.lisi.re...@gmail.com

Re: Virtualbox install problems on Wheezy with 3.16.0 backports kernel

[Dobigeon Nicolas]

Le 28/12/2014 06:27, Marc Shapiro a écrit :

Ooops!  Sorry, Carl.  This was supposed to go to the list.

On 12/27/2014 08:42 PM, Carl Fink wrote:

On Sat, Dec 27, 2014 at 08:29:38PM -0800, Marc Shapiro wrote:


... I have the following installed:


ilinux-headers-3.16.0-0.bpo.4-amd64  - Header
files for
Linux 3.16.0-0.bpo.4-amd64
i A linux-headers-3.16.0-0.bpo.4-common   - Common header
files
for Linux 3.16.0-0.bpo.4
ilinux-image-3.16-0.bpo.2-amd64 - Linux
3.16 for
64-bit PCs
i linux-kbuild-3.16 -
Kbuild infrastructure for Linux 3.16

i A dkms - Dynamic Kernel Module Support Framework
i virtualbox-dkms - x86
virtualization solution - kernel module sources for dkms

i virtualbox - x86 virtualization solution - base binaries
i virtualbox-qt - x86 virtualization solution - Qt based user interface

I still get the above error when I start virtualbox.  If I click past
it and
try to power up the ReactOS vm, I get:


Kernel driver not installed (rc=-1908)


The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or
there
is a permission problem with /dev/vboxdrv.
Please reinstall the kernel module by executing:

'/etc/init.d/vboxdrv setup'

as root.  If it is available in your distribution, you should install
the
DKMS package first.  This package keeps track if Linux kernel changes
and
recompiles the vboxdrv kernel module if necessary.
-

The problem is that '/etc/init.d/vboxdrv' does not exist. Neither does
'/dev/vboxdrv'.  Am I somehow missing a package that should have been
installed?  Have I missed a step somewhere in installing virtualbox?
How do
I get vboxdrv installed?

What version of virtualbox does the above represent?

In my experience dkms for VirtualBox has never worked in Wheezy. I
have to
manually compile the module every time I upgrade the kernel.

According to the Debian Wiki, you have to install VirtualBox from
backports
if you use a backports kernel:
https://wiki.debian.org/VirtualBox#Debian_7_.22Wheezy.22_Backports

Hmmm ... that's the x86 version of dkms for an AMD64 kernel. As this list
taught me some time ago, that can cause problems.

It was the Wheezy version of virtualbox, so I added contrib to the
wheezy-backports line in /etc/apt/sources.list.  I then performed
'aptitude update' and 'aptitude -t wheezy-backports install virtualbox'
with the following results:

~# aptitude -t wheezy-backports install virtualbox
The following NEW packages will be installed:
   libgsoap4{a}
The following packages will be REMOVED:
   libgsoap2{u}
The following packages will be upgraded:
   virtualbox virtualbox-dkms virtualbox-qt
3 packages upgraded, 1 newly installed, 1 to remove and 255 not upgraded.
Need to get 21.4 MB of archives. After unpacking 17.8 MB will be used.
Do you want to continue? [Y/n/?] y
Get: 1 http://http.debian.net/debian/ wheezy-backports/contrib
virtualbox-qt amd64 4.3.14-dfsg-1~bpo70+1 [4,525 kB]
Get: 2 http://http.debian.net/debian/ wheezy-backports/main libgsoap4
amd64 2.8.16-2~bpo70+1 [545 kB]
Get: 3 http://http.debian.net/debian/ wheezy-backports/contrib
virtualbox amd64 4.3.14-dfsg-1~bpo70+1 [15.8 MB]
Get: 4 http://http.debian.net/debian/ wheezy-backports/contrib
virtualbox-dkms all 4.3.14-dfsg-1~bpo70+1 [575 kB]
Fetched 21.4 MB in 12s (1,712 kB/s)
Reading changelogs... Done
(Reading database ... 220323 files and directories currently installed.)
Preparing to replace virtualbox-qt 4.1.18-dfsg-2+deb7u3 (using
.../virtualbox-qt_4.3.14-dfsg-1~bpo70+1_amd64.deb) ...
Unpacking replacement virtualbox-qt ...
Selecting previously unselected package libgsoap4:amd64.
Unpacking libgsoap4:amd64 (from
.../libgsoap4_2.8.16-2~bpo70+1_amd64.deb) ...
Preparing to replace virtualbox 4.1.18-dfsg-2+deb7u3 (using
.../virtualbox_4.3.14-dfsg-1~bpo70+1_amd64.deb) ...
Unpacking replacement virtualbox ...
Processing triggers for menu ...
Processing triggers for man-db ...
Processing triggers for shared-mime-info ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
Processing triggers for hicolor-icon-theme ...
Processing triggers for desktop-file-utils ...
(Reading database ... 220353 files and directories currently installed.)
Removing libgsoap2 ...
(Reading database ... 220338 files and directories currently installed.)
Preparing to replace virtualbox-dkms 4.1.18-dfsg-2+deb7u3 (using
.../virtualbox-dkms_4.3.14-dfsg-1~bpo70+1_all.deb) ...

--
Deleting module version: 4.1.18
completely from the DKMS tree.
--
Done.
Unpacking replacement virtualbox-dkms ...
dpkg: warning: unable to delete old directory
'/usr/src/virtualbox-4.1.18/vboxdrv': Directory not empty
dpkg: warning: unable to delete old d

Possible incompatibility between wheezy gnome and wheezy-backports libreoffice

[Miguel Ortiz Lombardía]

Hi,

I'm using debian wheezy (amd64) up-to-date till December 24.
I have installed some packages from wheezy-backports, essentially
libreoffice.

I made an upgrade this morning and I got these messages (that I didn't
look into at the time...):

> sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
  libreoffice libreoffice-avmedia-backend-gstreamer libreoffice-base
libreoffice-base-core libreoffice-base-drivers
  libreoffice-calc libreoffice-core libreoffice-draw
libreoffice-evolution libreoffice-gnome libreoffice-gtk
  libreoffice-impress libreoffice-l10n-ca libreoffice-math
libreoffice-sdbc-firebird libreoffice-sdbc-hsqldb
  libreoffice-writer python-uno uno-libs3 ure
The following packages will be upgraded:
  libreoffice-common libreoffice-java-common libreoffice-style-galaxy
libreoffice-style-tango
4 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
Need to get 26.5 MB of archives.
After this operation, 4096 B disk space will be freed.

Now, when I asked for a dist-upgrade I got:

> sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  gnome jabref-plugin-oo libreoffice
libreoffice-avmedia-backend-gstreamer libreoffice-base libreoffice-base-core
  libreoffice-base-drivers libreoffice-calc libreoffice-core
libreoffice-draw libreoffice-evolution libreoffice-gnome
  libreoffice-gtk libreoffice-help-ca libreoffice-help-en-us
libreoffice-impress libreoffice-math
  libreoffice-report-builder-bin libreoffice-sdbc-firebird
libreoffice-sdbc-hsqldb libreoffice-writer mythes-en-us
  python-uno unoconv
The following NEW packages will be installed:
  abiword abiword-common abiword-plugin-grammar abiword-plugin-mathview
libabiword-2.9 libgdome2-0
  libgdome2-cpp-smart0c2a libgtkmathview0c2a liblink-grammar4
libloudmouth1-0 libots0 libwps-0.2-2 libwv-1.2-4
  link-grammar-dictionaries-en
The following packages have been kept back:
  uno-libs3 ure
The following packages will be upgraded:
  libreoffice-common libreoffice-java-common libreoffice-l10n-ca
libreoffice-style-galaxy libreoffice-style-tango
5 upgraded, 14 newly installed, 24 to remove and 2 not upgraded.
Need to get 37.7 MB of archives.
After this operation, 334 MB disk space will be freed.

In the end, libreoffice was removed and somehow replaced with abiword,
but more dangerously, gnome was removed and all its associated packages
with it... Fortunately enough I had a recent backup so nothing got lost.

I don't know how to track where the problem comes from (gnome? backport
libreoffice?) so I can report it to the adequate developers. I would
appreciate any clue on this.

I would also appreciate your advice on how to resolve this issue: should
I go back to libreoffice from the wheezy repositories or rather upgrade
gnome to that from wheezy-backports ? The second options seems to me a
more risky one.

In the meantime, those in a similar configuration should avoid upgrading...

Cheers,

   Miguel


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/549fc720.8000...@igs.cnrs-mrs.fr