Strange webcam failure and 'fix'

[Alexis]

Hi all,

i have a Logitech Quickcam Pro 9000, which i use with the Jitsi
voice/video client. Occasionally it stops working, such that my laptop -
an Asus K53E running 64-bit Wheezy + all available updates - doesn't
appear to detect it at all (as per the output of e.g. `lsusb`). Leaving
the cam plugged in and soft-restarting the laptop makes no difference,
nor does hard-restarting the laptop. Unplugging the cam and soft- or
hard-restarting the laptop before plugging it back in makes no
difference either.

What /does/ make a difference, however, is simply plugging the cam into
a USB port of a desktop machine - an Ipex Augsburg 0431 running 32-bit
Wheezy + all available updates - waiting a few moments, then unplugging
it from the desktop machine and plugging it back into the laptop,
whereupon it's immediately detected and available for use.

Can anyone offer any insights as to what might be happening here?


Alexis.


-- 
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/87wq4xk8tc@gmail.com

Re: xterm choking on compose key input

[Kumar Appaiah]

Dear Sven,

Thanks for the e-mail.

On Wed, Jan 07, 2015 at 06:12:22PM +0100, Sven Joachim wrote:
> On 2015-01-07 09:38 +0100, Kumar Appaiah wrote:
> 
> > I regularly use the compose key to insert characters. The locale I
> > use, en_IN, doesn't have a Compose file in /usr/share/X11/locale, so I
> > copied the /usr/share/X11/locale/en_US.UTF-8/Compose file to
> > ~/.XCompose.
> >
> > Now, most applications work fine. However, xterm seems to choke on
> > compose key input, and I get garbage whenever I type any compose key
> > sequence. However, if I run LANG=en_US.UTF-8 xterm, then it works
> > fine.
> 
> Which version of xterm is that?  If ~/.XCompose exists, xterm does not
> read any other Compose files here:

dpkg -l xterm gives me:
Desired=Unknown/Install/Remove/Purge/Hold
ii  xterm  312-1amd64X terminal emulator

> ,
> | $ strace xterm -e true 2>&1 | grep Compose 
> | open("/home/sven/.XCompose", O_RDONLY)  = 5
> | stat64("/home/sven/.XCompose", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
> | stat64("/home/sven/.XCompose", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
> | open("/home/sven/.XCompose", O_RDONLY)  = 5
> `
> 
> So I don't have any explanation for the behavior you observe.

strace xterm -e true 2>&1 | grep Compose
open("/home/kumar/.XCompose", O_RDONLY) = 6
stat("/home/kumar/.XCompose", {st_mode=S_IFREG|0644, st_size=563251, ...}) = 0
stat("/home/kumar/.XCompose", {st_mode=S_IFREG|0644, st_size=563251, ...}) = 0
open("/home/kumar/.XCompose", O_RDONLY) = 6

This is fine. It is clear that xterm honours the .XCompose file. It's
just that the characters it seems to receive aren't the right
ones. For example, Compose + . + . should give me an ellipsis, as it
does on other programs. But on xterm, I get "â\200¦". But LC_ALL=en_US.UTF-8 
xterm
works perfectly.

Thanks.

Kumar


-- 
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/20150108065438.gb12...@bluemoon.iitb.ac.in

Re: remove me from this list

[Don Armstrong]

On Wed, 07 Jan 2015, Cindy-Sue Causey wrote:
> *PLEASE* help *ALL* those named there by clicking that "report as
> sp*m" button at the top right of that page.

Just one person clicking it is enough; the spam has to be manually
reviewed by someone with a spam review account. [Once they've done that,
it'll disappear.]


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

I leave the show floor, but not before a pack of caffeinated Jolt gum
is thrust at me by a hyperactive girl screaming, "Chew more! Do more!"
The American will to consume more and produce more personified in a
stick of gum. I grab it.
 -- Chad Dickerson


-- 
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/20150108070321.gt29...@teltox.donarmstrong.com

multiple outbound NAT

[Bonno Bloksma]

Hi,

At one place I have a Debian wheezy machine that acts as router / firewall 
using iptables and default routing.
I used to have just 1 ip number on the uplink interface. And a simple 
  $IPTABLES --table nat -A POSTROUTING -o $WORLD_IF -j MASQUERADE
line in my firewall script sends all traffic out with that single ip addres via 
NAT.

Due to several reasons I now have to use more than 1 outbound ip address to 
make clear from which internal segment the traffic is coming from.
So traffic coming from 172.16.20.0/24 needs to use $WORLD_IP1
And traffic coming from 172.16.22.0/24 needs to use $WORLD_IP2
And maybe traffic coming from 172.16.24.0/23 needs to use $WORLD_IP3

How do I configure something like that?
If it is any use in this case, I have quagga on that machine as well but so far 
that is used to do routing for the internal network. But I'd rather not mess 
with that config.

Bonno Bloksma


--
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/89d1798a7351d040b4e74e0a043c69d7ad5ff...@einexch-01.tio.nl

Re: remove me from this list

[Bret Busby]

On 08/01/2015, Cindy-Sue Causey  wrote:
> On 1/7/15, Talitha Thalya  wrote:
>> *My name was never meant to show up on a google search like this linked
>> to
>> Debian. and dated back in 2001  Not Ok  it was meant to go to the cause.
>> this is a misuse of trust.  please remove me.  name stated in this email
>> address.  Thanks*
>>
>> *Taliban **woman  2001*
>> https://lists.debian.org/debian-devel/2001/04/msg00110.html
>
>
> Hi.. Normally I no longer follow through reading these kinds of
> emails. For some reason, I did yours
>
> To All: In light of the highly publicized World events of the last 24
> hours, a personal request to my fellow Debian-Users...
>
> *PLEASE* help *ALL* those named there by clicking that "report as
> sp*m" button at the top right of that page. Enough of us click that
> *right now*, that should take care of her request because it is not
> Debian developer related anyway...
>
> If any Debian developers catch this now, could you please help speed
> up the process of yanking that off the WWW..?
>
> Thank you..
>
> Peace and Love to All..
>
> Cindy Sue
>
> --
> Cindy-Sue Causey
> Talking Rock, Pickens County, Georgia, USA
>

And that is related to this list, how?

It is all apparently, completely unrelated to this list.

Both messages above, seem to be spam.


-- 
Bret Busby
Armadale
West Australia
..

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992




-- 
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/cacx6j8ped1lyg+vy25zu+3lcjscfesvterbvoonqnqb3_kt...@mail.gmail.com

Re: remove me from this list

[Cindy-Sue Causey]

On 1/7/15, Talitha Thalya  wrote:
> *My name was never meant to show up on a google search like this linked to
> Debian. and dated back in 2001  Not Ok  it was meant to go to the cause.
> this is a misuse of trust.  please remove me.  name stated in this email
> address.  Thanks*
>
> *Taliban **woman  2001*
> https://lists.debian.org/debian-devel/2001/04/msg00110.html


Hi.. Normally I no longer follow through reading these kinds of
emails. For some reason, I did yours

To All: In light of the highly publicized World events of the last 24
hours, a personal request to my fellow Debian-Users...

*PLEASE* help *ALL* those named there by clicking that "report as
sp*m" button at the top right of that page. Enough of us click that
*right now*, that should take care of her request because it is not
Debian developer related anyway...

If any Debian developers catch this now, could you please help speed
up the process of yanking that off the WWW..?

Thank you..

Peace and Love to All..

Cindy Sue

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


-- 
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-kcqvyf+mz9ctwpd9tl-cxqdnuw4+au-xjaqc44u_kn...@mail.gmail.com

remove me from this list

[Talitha Thalya]

*My name was never meant to show up on a google search like this linked to
Debian. and dated back in 2001  Not Ok  it was meant to go to the cause.
this is a misuse of trust.  please remove me.  name stated in this email
address.  Thanks*

*Taliban **woman  2001*
https://lists.debian.org/debian-devel/2001/04/msg00110.html

Re: Please stop systemd-fsck on _every_ boot!

[~Stack~]

On 01/07/2015 01:45 PM, Bob Proulx wrote:
> The Wanderer wrote:
>> To my eye, based on what you've reported, it does look as if the reason
>> your system is running fsck on every boot is that something about a
>> mount attempt is failing. However, aside from "probably to do with the
>> swap partition", I have no clue what that something is - or how to
>> figure out more, beyond what you already seem to know to try.
> 
> I would also be concerned that on shutdown the disks aren't being
> marked as cleanly unmounted and shutdown.  Causing them to need to be
> checked at boot time.

I don't see anything in the log files saying otherwise. Then again, if
it is on unmount then it wouldn't necessarily wouldn't be able to write
the log files out...

I did make some pretty big progress earlier today, unfortunately I am
not sure the exact thing I did. I got in and started mucking about with
the starting and stopping of systemd services and what not and now that
kernel boot skip parameter works! So at least that is working now. :-)

Though I think I might be ok with an every boot fsck that takes >2
seconds...

Thanks!
~Stack~




signature.asc
Description: OpenPGP digital signature

Re: Please stop systemd-fsck on _every_ boot!

[~Stack~]

On 01/07/2015 08:16 AM, The Wanderer wrote:
> On 01/07/2015 at 08:39 AM, ~Stack~ wrote:
> 
[snip]
>>  However, I
>> *have* read the man page and the man page for fstab says "If the
>> sixth field is  not present or zero, a value of zero is returned and
>> fsck will assume that the filesystem does not need to be checked."
>> Therefore, I am explicitly telling systemd-fsck to buggeroff and not
>> check. I as the owner of the device have acknowledged and assumed all
>> the risk for not running fsck on my drive. The fact that it is
>> /still/ doing it against my wishes is what annoys me.
> 
> According to my understanding, this field is not in fact a global
> boot-time-fsck override, which you seem to be expecting it to be.
> 
> There are actually (at least) two ways in which fsck can be triggered at
> boot time: by the automatic iterate-through-the-fstab is-a-fsck-needed
> procedure, which reads and respects this field (because it's iterating
> through fstab anyway), and in response to a failed mount attempt, which
> I believe ignores this field (because the fsck was invoked in a way
> which has nothing to do with fstab - just as would happen if you invoked
> fsck manually).

Hrm. Ok. I learned something today. :-)

I don't know why, but I really thought that meant that fsck wouldn't
check at all if the sixth field was 0.

Thanks!
~Stack~




signature.asc
Description: OpenPGP digital signature

Re: Please stop systemd-fsck on _every_ boot!

[~Stack~]

Greetings,

On 01/07/2015 11:06 AM, Rob Owens wrote:
> I suppose it's possible that the bios battery is no good, and the clock
> is getting reset after each shutdown.  Then the "last time fsck'd" would
> be in the future, and I expect the system might fsck your disk as a 
> precaution.
> 
> You might never notice the clock issue if ntp or ntpdate is running and
> corrects the clock after the network is up.

Thanks for the suggestion. I did check that and the clock was off a bit,
but even after correcting it there was no change.

~Stack~



signature.asc
Description: OpenPGP digital signature

Re: debhelper stripping debugging symbols

[Kip Warner]

On Wed, 2015-01-07 at 11:19 -0800, Don Armstrong wrote:
> If you attach the actual rules file, then we might get to that answer.
> 
> It's also possible that you didn't have debugging symbols included in
> the first place (-g).

It turns out I'm either blind, stupid, or probably both. The = was
actually in the original and when I removed it, it behaves as it
should.

Here's the debian/rules anyways in case you see anything else that
could help:



> [Furthermore, dh_strip always runs, it just doesn't strip if nostrip is
> in DEB_BUILD_OPTIONS.]

Correct. The arguments vary depending on the value of
DEB_BUILD_OPTIONS.

-- 
Kip Warner -- Senior Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com


signature.asc
Description: This is a digitally signed message part

Re: Please stop systemd-fsck on _every_ boot!

[Bob Proulx]

The Wanderer wrote:
> To my eye, based on what you've reported, it does look as if the reason
> your system is running fsck on every boot is that something about a
> mount attempt is failing. However, aside from "probably to do with the
> swap partition", I have no clue what that something is - or how to
> figure out more, beyond what you already seem to know to try.

I would also be concerned that on shutdown the disks aren't being
marked as cleanly unmounted and shutdown.  Causing them to need to be
checked at boot time.

Bob


signature.asc
Description: Digital signature

Re: debhelper stripping debugging symbols

[Don Armstrong]

On Wed, 07 Jan 2015, Kip Warner wrote:
> So back to my original question, why was it being ignored?

If you attach the actual rules file, then we might get to that answer.

It's also possible that you didn't have debugging symbols included in
the first place (-g).

[Furthermore, dh_strip always runs, it just doesn't strip if nostrip is
in DEB_BUILD_OPTIONS.]

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

If you wish to strive for peace of soul, then believe; if you wish to
be a devotee of truth, then inquire.
 -- Friedrich Nietzsche


-- 
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/20150107191936.go27...@rzlab.ucr.edu

Re: debhelper stripping debugging symbols

[Kip Warner]

On Wed, 2015-01-07 at 00:07 -0800, Don Armstrong wrote:
> This line:
> 
> export DEB_BUILD_OPTIONS=
> 
> sets DEB_BUILD_OPTIONS to "", which isn't what you want.

Hey Don. That was actually a typo when copying and pasting into
pastebin. Ignore the = character. I know what you mean, and indeed, that
would have reset the variable had that been there.

So back to my original question, why was it being ignored?

(snip)

> nor do you need to include
> /usr/share/dpkg/default.mk, because dh knows how to do all of that
> itself, too.

Are you sure? The reason I ask is dh_make had actually created the
original template debian/rules using the debhelper 7 syntax and that was
what was in it.

> Finally, your debian/rules is missing a #!/usr/bin/make -f, which means
> that it isn't going to work at all.

Another pastebin copy / paste typo. It's in the original.

-- 
Kip Warner -- Senior Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com


signature.asc
Description: This is a digitally signed message part

No sound in Jessie KDE

[ntrfug]

When I had Windows 7 on my machine (Lenovo W53) the sound volume was
high enough that I usually set it at ~50%. With Jessie 100% volume
seemed barely adequate, and I was experimenting to see if I could get
more.

In KDE->System Settings->Multimedia I played with the settings; the
result was that no available playback devices are shown. Pressing the
"Reset" and "Defaults" buttons at the bottom of the screen had no
effect.

How can I get back to the defaults?


-- 
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/20150107121415.04ed5fce@sirius

Re: Please stop systemd-fsck on _every_ boot!

[Rob Owens]

On Tue, Jan 06, 2015 at 06:23:18PM -0600, ~Stack~ wrote:
> Greetings,
> 
> This problem has been a minor annoyance for a while but only recently
> have I started to use Jessie more and it is has finally peeved me off. I
> have been trying everything I can find for the last two hours and I
> still can't get systemd to STOP doing a fsck on _every_ boot!

I suppose it's possible that the bios battery is no good, and the clock
is getting reset after each shutdown.  Then the "last time fsck'd" would
be in the future, and I expect the system might fsck your disk as a 
precaution.

You might never notice the clock issue if ntp or ntpdate is running and
corrects the clock after the network is up.

Good luck!

-Rob


signature.asc
Description: Digital signature

Re: xterm choking on compose key input

[Sven Joachim]

On 2015-01-07 09:38 +0100, Kumar Appaiah wrote:

> I regularly use the compose key to insert characters. The locale I
> use, en_IN, doesn't have a Compose file in /usr/share/X11/locale, so I
> copied the /usr/share/X11/locale/en_US.UTF-8/Compose file to
> ~/.XCompose.
>
> Now, most applications work fine. However, xterm seems to choke on
> compose key input, and I get garbage whenever I type any compose key
> sequence. However, if I run LANG=en_US.UTF-8 xterm, then it works
> fine.

Which version of xterm is that?  If ~/.XCompose exists, xterm does not
read any other Compose files here:

,
| $ strace xterm -e true 2>&1 | grep Compose 
| open("/home/sven/.XCompose", O_RDONLY)  = 5
| stat64("/home/sven/.XCompose", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
| stat64("/home/sven/.XCompose", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
| open("/home/sven/.XCompose", O_RDONLY)  = 5
`

So I don't have any explanation for the behavior you observe.

Cheers,
   Sven


-- 
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/87lhle5xc9@turtle.gmx.de

Re: Please stop systemd-fsck on _every_ boot!

[Wim Bertels]

do u have a "fsck" file in the root / of the partition?
(this will cause a fs check as well)

mvg,
Wim

On Tue, 2015-01-06 at 18:23 -0600, ~Stack~ wrote:
> Greetings,
> 
> This problem has been a minor annoyance for a while but only recently
> have I started to use Jessie more and it is has finally peeved me off. I
> have been trying everything I can find for the last two hours and I
> still can't get systemd to STOP doing a fsck on _every_ boot!
> 
> It tells me with a nice count down that it will take 1:45 minutes to
> run. It always runs longer and it always hangs on the swap partition.
> Immediately after it finishes there is a /super/ quick message about a
> timeout on the swap partition (that I can *not* find in the log files
> anywhere) followed by another message I can't read nor find in the log
> files. I see where it runs fsck in both the daemon and syslog, but
> _every_ partition is clean. There are no errors or timeouts that I can
> find in the logs.
> 
> I keep seeing all of these posts online saying how easy it is to disable
> systemd from runing fsck because it "honors" the '0' in the sixth field
> of /etc/fstab. Well that's just pure bull$h1t... That was one of the
> first things I tried some time ago. As far as I can tell on neither of
> my Jessie machines (one physical one virtual) does systemd honor the
> fstab in terms of doing a fsck. All of the partitions are set to 0 in
> /etc/fstab.
> 
> I found a post saying to disable it in /etc/fstab as a mount option
> 'x-systemd.automount'. That doesn't work either.
> 
> $ sed -e '/^#/d' /etc/fstab
> /dev/mapper/sda2_crypt / ext4 errors=remount-ro 0 0
> UUID=af9e4bfa-5591-4b9a-a855-3444b2562493 /boot ext4 defaults 0 0
> /dev/mapper/sda3_crypt none swap,x-systemd.automount sw 0 0
> /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto  0 0
> /dev/mapper/sda4_crypt /home ext4 defaults 0 0
> 
> I tried disabling the systemd-fsck service. That didn't work either.
> 
> Finally, I just tried "fsck.mode=skip" on the kernel command
> line...guess what? That doesn't work either. I thought maybe there was
> an issue with me interupting grub manually to add that line, so I also
> added it to /etc/default/grub's GRUB_CMDLINE_LINUX_DEFAULT and ran
> update-grub. After rebooting WITH a fsck being run, I can see it in my
> /proc/cmdline and when I look through my last boot log I can *see* it
> there too! Still doesn't work and systemd-fsck still runs on _every_ boot.
> 
> $ cat cmdline
> BOOT_IMAGE=/vmlinuz-3.16.0-4-686-pae
> root=UUID=99d5a78e-7e8d-4426-83b2-33c06d630587 ro quiet
> init=/bin/systemd fsck.mode=skip
> 
> At this point I don't even care anymore if my disks never run fsck
> again. I just want systemd-fsck to STOP running on EVERY boot.
> 
> Thanks!
> ~Stack~
> 



-- 
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/1420646302..5.camel@zwerfkat

Re: File transfer between Debian Wheezy Xfce and iPad, iPod, iPhone

[John L. Cunningham]

On Fri, Jan 02, 2015 at 11:26:50AM -0800, David Christensen wrote:
> debian-user:
> 
> I would like to transfer files between Debian Wheezy Xfce computers
> (i386 and amd64) and iOS devices (iPod, iPad, iPhone).
> 
> 
> 
> 
> When I touch "Trust", there is activity in the icons in the
> upper-right corner of the iPad display, and then the pop-up dialog
> appears again; ad infinitum.
> 
> 
> Any suggestions?

What kind of files are you trying to transfer?  I was able to sync the photos 
on my wife's iphone via Shotwell despite the "Trust" pop up on the phone.  Just 
don't hit "Trust" during the sync or it will interrupt and possibly cause 
problems.  I wasn't able to browse the photos via Nautilus (I'm using Gnome) 
but I also didn't want to spend a lot of time on this.

--John


-- 
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/20150107161440.gb1...@clark17v.rootsmkt.com

Re: (EE) intel(G0): Failed to claim DRM device.

[VieuxGeek DuSystem]

Hi

Intel and DRM ... good luck :-)

maybe the libdrm-intel1 packages?

Stef


2015-01-07 15:20 GMT+01:00 Mladen Mijatov :

> Hi everyone,
>
> I am using Debian Testing, and some time ago I noticed my TV, which is
> connected to my Intel card, started having visual glitches. After some
> investigation I found the cause was the following error message in
> Xorg.0.log file:
>
> [ 3.854] (II) Loading sub module "dri2"
> [ 3.854] (II) LoadModule: "dri2"
> [ 3.854] (II) Module "dri2" already built-in
> [ 5.987] (EE) intel(G0): [drm] failed to set drm interface version:
> Permission denied [13].
> [ 5.987] (EE) intel(G0): Failed to claim DRM device.
> [ 5.987] (II) UnloadModule: "intel"
>
> This use to work just fine, and unfortunately I can't pin point the moment
> when this issue occurred as I don't use that display often.
>
> I have a desktop machine, with nVidia GT610 and i5 processor with built-in
> GPU. Am mentioning this because any online search for these messages
> resulted in Bumblebee specific issues, which I don't have.
>
> Since I don't know which package caused this issue I followed the
> instruction in "reportbug" tool to contact people on this mailing list. Can
> anyone suggest which packages I should include when reporting this issue?
>
> Thanks
> --
> Mladen Mijatov
> Key ID: 4096R/83EFD5A0 2013-08-18
>
>

Re: Please stop systemd-fsck on _every_ boot!

[The Wanderer]

On 01/07/2015 at 08:39 AM, ~Stack~ wrote:

> On 01/07/2015 03:10 AM, Ric Moore wrote:
> 
>> On 01/06/2015 07:23 PM, ~Stack~ wrote:
>> 
>>> I keep seeing all of these posts online saying how easy it is to
>>> disable systemd from runing fsck because it "honors" the '0' in
>>> the sixth field of /etc/fstab. Well that's just pure bull$h1t...
>>> That was one of the first things I tried some time ago. As far as
>>> I can tell on neither of my Jessie machines (one physical one
>>> virtual) does systemd honor the fstab in terms of doing a fsck.
>>> All of the partitions are set to 0 in /etc/fstab.
>> 
>> That doesn't make it "bullshit", it means that in your instance it
>> doesn't help. Instead, just maybe your system is trying to tell
>> you something when it continually forces fsck. Read the man page.
> 
> You are right in that there is something probably wrong with my
> instance and it might be trying to tell me something. However, I
> *have* read the man page and the man page for fstab says "If the
> sixth field is  not present or zero, a value of zero is returned and
> fsck will assume that the filesystem does not need to be checked."
> Therefore, I am explicitly telling systemd-fsck to buggeroff and not
> check. I as the owner of the device have acknowledged and assumed all
> the risk for not running fsck on my drive. The fact that it is
> /still/ doing it against my wishes is what annoys me.

According to my understanding, this field is not in fact a global
boot-time-fsck override, which you seem to be expecting it to be.

There are actually (at least) two ways in which fsck can be triggered at
boot time: by the automatic iterate-through-the-fstab is-a-fsck-needed
procedure, which reads and respects this field (because it's iterating
through fstab anyway), and in response to a failed mount attempt, which
I believe ignores this field (because the fsck was invoked in a way
which has nothing to do with fstab - just as would happen if you invoked
fsck manually).

To my eye, based on what you've reported, it does look as if the reason
your system is running fsck on every boot is that something about a
mount attempt is failing. However, aside from "probably to do with the
swap partition", I have no clue what that something is - or how to
figure out more, beyond what you already seem to know to try.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

(EE) intel(G0): Failed to claim DRM device.

[Mladen Mijatov]

Hi everyone,

I am using Debian Testing, and some time ago I noticed my TV, which is 
connected to my Intel card, started having visual glitches. After some 
investigation I found the cause was the following error message in Xorg.0.log 
file:

[ 3.854] (II) Loading sub module "dri2"
[ 3.854] (II) LoadModule: "dri2"
[ 3.854] (II) Module "dri2" already built-in
[ 5.987] (EE) intel(G0): [drm] failed to set drm interface version: 
Permission denied [13].
[ 5.987] (EE) intel(G0): Failed to claim DRM device.
[ 5.987] (II) UnloadModule: "intel"

This use to work just fine, and unfortunately I can't pin point the moment when 
this issue occurred as I don't use that display often.

I have a desktop machine, with nVidia GT610 and i5 processor with built-in GPU. 
Am mentioning this because any online search for these messages resulted in 
Bumblebee specific issues, which I don't have.

Since I don't know which package caused this issue I followed the instruction 
in "reportbug" tool to contact people on this mailing list. Can anyone suggest 
which packages I should include when reporting this issue?

Thanks
-- 
Mladen Mijatov
Key ID: 4096R/83EFD5A0 2013-08-18



signature.asc
Description: OpenPGP digital signature

Re: Please stop systemd-fsck on _every_ boot!

[~Stack~]

On 01/07/2015 05:21 AM, Martin Steigerwald wrote:
> Am Dienstag, 6. Januar 2015, 22:13:26 schrieb ~Stack~:
>> In summary:
>> * I have systemd-fsck disabled just about every damn place I can find to
>> do so, yet it still runs on boot every time. I see it on the screen and
>> in the log messages.
>> * I still can't find where the hell systemd stores the same information
>> it displays on the boot screen.
> 
> nothing shown by journalctl?

I did look there as well. I can see where it runs fsck but it says the
partitions are clean. There are other error messages about it not liking
my controller and what not, but no errors I see related to the fsck nor
the timeout. I tried filming the message as it went by the boot, but the
video just came out blurry...guess my camera isn't good enough. :-)

~Stack~



signature.asc
Description: OpenPGP digital signature

Re: Please stop systemd-fsck on _every_ boot!

[~Stack~]

On 01/07/2015 03:10 AM, Ric Moore wrote:
> On 01/06/2015 07:23 PM, ~Stack~ wrote:
> 
>> I keep seeing all of these posts online saying how easy it is to disable
>> systemd from runing fsck because it "honors" the '0' in the sixth field
>> of /etc/fstab. Well that's just pure bull$h1t... That was one of the
>> first things I tried some time ago. As far as I can tell on neither of
>> my Jessie machines (one physical one virtual) does systemd honor the
>> fstab in terms of doing a fsck. All of the partitions are set to 0 in
>> /etc/fstab.
> 
> That doesn't make it "bullshit", it means that in your instance it
> doesn't help. Instead, just maybe your system is trying to tell you
> something when it continually forces fsck. Read the man page.

You are right in that there is something probably wrong with my instance
and it might be trying to tell me something. However, I *have* read the
man page and the man page for fstab says "If the sixth field is  not
present or zero, a value of zero is returned and fsck will assume that
the filesystem does not need to be checked." Therefore, I am explicitly
telling systemd-fsck to buggeroff and not check. I as the owner of the
device have acknowledged and assumed all the risk for not running fsck
on my drive. The fact that it is /still/ doing it against my wishes is
what annoys me.


> The trick is to get your poor stupid dumb machine to tell it's human
> where it hurts and how to fix it. It's like dealing with a puppy that
> whines.

I will not deny that this laptop is more than a little weird. It's
almost 10 years old and has seen its share of hardship in life. But as a
secondary laptop I can haul around with me and not worry about it, it's
a fantastic system.

> 
> OK, your next message reveals that you are encrypting your drives,
> including swap?? Insert "encrypted hard drive fsck" into your search
> bar. Lately, others report problems.

I did look for that. Obviously not in the right places, but even typing
that exact string into my search bar returns results for people who have
errors to work with and search against. I don't. All my messages say
that fsck returned clean with the exception of the one that goes by too
fast and says something about a timeout.

> Another thought would be to disable swap, if you have enough memory to
> see if that helps at all. man swapoff

Well, since I figured out that systemd-fsck goes really quickly when I
have /dev/sda3 instead of the UUID for the swap partition, it works just
fine. I don't see how turning off swap all together will suddenly make
systemd-fsck start listening to the boot parameter and fstab telling it
not to run fsck at all.

> 
> Since it was encrypted no telling what this would do: man swapoff
> 
> swapoff-f, --fixpgsz
> Reinitialize (exec /sbin/mkswap) the swap space if its page size
> does not match that of the current  running  kernel.   mkswap(2)
> initializes the whole device and does not check for bad blocks.
> ---

# swapoff -a
# swapon --fixpgsz /dev/dm-1
# swapon -a
# swapon -s
Filename  Type Size Used Priority
/dev/sda3  partition 585724 0 -1

No errors or anything, so I assume that is good...

> At any rate all the fsck'ing is telling you something is broken. That is
> what it is supposed to do.

Not when I have told systemd-fsck to stop trying. Then it is supposed to
not do it. Also, I have yet to see a report that says something other
than clean. Using the information I have, I am leaning toward that
something broken being systemd-fsck...I have run out of ideas on how to
tell it to stop...

If you are running luks check this:
> http://serverfault.com/tags/luks/hot
> 
> Happy hunting troubleshooting with a shotgun. :) Ric

Thanks! I do appreciate the help!

~Stack~




signature.asc
Description: OpenPGP digital signature

Re: File transfer between Debian Wheezy Xfce and iPad, iPod, iPhone

[Stephen Allen]

On Fri, Jan 02, 2015 at 11:26:50AM -0800, David Christensen wrote:
> debian-user:
> 
> I would like to transfer files between Debian Wheezy Xfce computers (i386
> and amd64) and iOS devices (iPod, iPad, iPhone).
> 
> 
> On Debian, I have installed:
> 
> libimobiledevice-utils
>
I haven't had any success using iDevices with Linux unless the iDevice was 
jailbreak'ed. 


-- 
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/20150107120108.GB10629@stephen-desktop

Re: Please stop systemd-fsck on _every_ boot!

[Martin Steigerwald]

Am Dienstag, 6. Januar 2015, 22:13:26 schrieb ~Stack~:
> In summary:
> * I have systemd-fsck disabled just about every damn place I can find to
> do so, yet it still runs on boot every time. I see it on the screen and
> in the log messages.
> * I still can't find where the hell systemd stores the same information
> it displays on the boot screen.

nothing shown by journalctl?

> * As far as I am concerned (granted with my very small sample size of 2)
> systemd flat out ignores the 6th field of fstab.
> * systemd-fsck apparently really hates UUID's for crypttab
> 
> BUT! It now takes 2-3 seconds every time it says it is running a fsck
> during boot versus the 2-3 minutes it used to take.
> 
> So I think I am just going to call it a "win" for now and go to sleep.

Luckily it doesn´t seem to do it here. On none of my systems.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

signature.asc
Description: This is a digitally signed message part.

Re: Have I been hacked?

[Joel Rees]

Some people on this list are treating this far too casually.

2015/01/07 1:06 "Danny" :
>
> Hi guys,
>
> A while ago I posted a question about SFTP (I think the thread name was
"SFTP
> Question") about attacks I got against my server after syslog warned me
about an
> attempted breakin.

Too bad I've been so distracted dealing with social engineering issues. I
was going to tell you at the time, if you think your box has been cracked,
assume it's been cracked. Don't guess, don't swag in parts, don't tiptoe
through the tulips. Don't ask on mailing lists for someone to tell you it's
all right.

> Consequently I installed fail2ban and did a few other things to let me
sleep
> better at night.

Too late.

You're opponents probably already have their own, separate login mechanisms
in place. Those things only work against opponents who have only the front
door to come in through.

Unless you are talking about a physically separate firewall and a
physically separate proxy, I suppose. But then you  would be telling us
about what the firewall logged, instead of asking about the toys left
behind.

> However, prior to this breakin, in early December 2014, I noticed my
network
> behaving strangely especially through wireless connections. I have Debian
that
> acts as a gateway (wlan0->br0->eth0). wlan0 is the pickup for the internal
> network that gets bridged to eth0 which then goes through the router to
the
> internet. What I noticed was that wireless connections would break down
quickly,
> bind9 would fail to resolve (even on wired connections) and pages would
load
> slow. In general it was chaos.

You should be looking for the physical path of entry. If you can afford it,
set up logging monitors on the internal traffic, both wired and wireless.
And insert a dedicated logging firewall to the WAN, firewalling and logging
both ways. And you wanted to have done that back then.

> Under the impression that it was a hardware failure, I changed the wlan0
> adapter. Still it was the same. So I bought a more expensive one, and
still no
> change. I changed eth0 with an expensive one and still it was the same. I
bought
> 2 new Netgear ADSL routers but the chaos was still there.

Next time, remember what swagging hardware bought you -- just giving time
to your opponents.

> wlan0, br0 and eth0 just didn't want to work together no more. Eventually
I
> stopped all bootup scripts and processes trying to isolate the problem.
And
> guess what, I found the culprit.

More like one of the careless culprits' leftover toys. You've been had by
amateurs, but that doesn't mean that professionals have ignored you.

> Here it is:
> ##
> -rwxr-xr-x 1 root root  648K Dec 11 17:17 /boot/dippqejwvf
> ##

You really want to know how that file got there, and all its differently
named clones.

> This file got booted up and caused all the havoc. I moved it to a secure
place and
> now it seems that all gremlins have gone away. The date on this file is
11 Dec
> 2014, right about the time my troubles started. I think that those
Chinese guys
> got into my system even before syslog warned me a few days later.

You can't even trust the dates, of course.

> However, I have a few other weird looking files in the /boot directory.
Can you
> guys please have a look at them and tell me if they are normal or not.

There is no reason to ask. You're just giving your opponents more time.

> #
> drwxr-xr-x  3 root root 4.0K Jan  6 19:35 .
> drwxr-xr-x 24 root root 4.0K Jan  3 17:23 ..
> -rwxr-xr-x  1 root root 648K Jan  6 19:03 aknaykocbs
> -rwxr-xr-x  1 root root 648K Jan  1 11:34 bxerzoalfk
> -rw-r--r--  1 root root 157K Dec 10 18:57 config-3.16.0-0.bpo.4-686-pae
> -rw-r--r--  1 root root 132K Dec  8 00:36 config-3.2.0-4-686-pae
> -rwxr-xr-x  1 root root 648K Dec 20 08:04 cwpgfmvkrk
> -rwxr-xr-x  1 root root 648K Dec 30 22:41 czhlgmsgzh
> -rwxr-xr-x  1 root root 648K Dec 30 20:03 dkseypedtx
> -rwxr-xr-x  1 root root 648K Jan  3 15:14 esijfkmwnd
> -rwxr-xr-x  1 root root 648K Dec 27 14:49 fndswijgdk
> -rwxr-xr-x  1 root root0 Dec 20 08:14 gbwokvqoch
> drwxr-xr-x  3 root root  12K Jan  3 17:23 grub
> -rwxr-xr-x  1 root root 648K Jan  5 07:28 gyimenpwnt
> -rwxr-xr-x  1 root root 648K Dec 31 17:49 hjmmvaxfzq
> -rwxr-xr-x  1 root root 648K Dec 15 21:25 hutaslspbf
> -rw-r--r--  1 root root  14M Jan  3 17:25
initrd.img-3.16.0-0.bpo.4-686-pae
> -rw-r--r--  1 root root  11M Jan  2 22:01 initrd.img-3.2.0-4-686-pae
> -rwxr-xr-x  1 root root 648K Jan  2 18:47 isrgzlchmx
> -rwxr-xr-x  1 root root 648K Dec 27 14:56 izytxsbskq
> -rwxr-xr-x  1 root root 648K Jan  5 18:40 kvvcqvddix
> -rwxr-xr-x  1 root root 648K Jan  1 11:19 ryrfvxjggh
> -rwxr-xr-x  1 root root0 Jan  5 19:08 sgopxfsiac
> -rw-r--r--  1 root root 2.0M Dec 10 18:57
System.map-3.16.0-0.bpo.4-686-pae
> -rw-r--r--  1 root root 1.6M Dec  8 00:36 Syst

Re: Late authentication

[Liam O'Toole]

On 2015-01-06, August Karlstrom  wrote:
> On 2015-01-06 17:40, Liam O'Toole wrote:
>> On 2015-01-05, August Karlstrom  wrote:
>>> I tried adding the file
>>> /var/lib/polkit-1/localauthority/50-local.d/test.pkla with the content
>>> below (and restarting X) but it made no difference; update-manager still
>>> asks for root password when launched.
>>>
>>> $ sudo cat /var/lib/polkit-1/localauthority/50-local.d/test.pkla
>>> [test]
>>> Identity=unix-group:sudo
>>> Action=org.debian.apt.update-cache
>>> ResultActive=yes
>>
>> Some things to check:
>>
>> - Are the file name "test.pkla" and the group name "test" unique?
>
> I think so. At least there are no other (.pkla) files in 
> /var/lib/polkit-1/localauthority/*
>
>> - Does the unix group "sudo" exist, and are you a member thereof?
>
> Yes.
>
>> - Has the action "org.debian.apt.update-cache" been defined? (Look under
>>/usr/share/polkit-1/actions/.)
>
> Yes, it's defined in /usr/share/polkit-1/actions/org.debian.apt.policy.
>
>> - Is dbus-daemon running during your Blackbox session?
>
> Yes, my Blackbox session is started from ~/.xinitrc with the command
>
>   exec ck-launch-session dbus-launch blackbox
>
>
> -- August
>
>

Try the pkcheck command. I've never needed to use it, but it looks like
it might be helpful in your case. Good luck.

-- 

Liam



-- 
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/slrnmaq4bp.rcr.liam.p.otoole@dipsy.tubbynet

Re: Please stop systemd-fsck on _every_ boot!

[Ric Moore]

On 01/06/2015 07:23 PM, ~Stack~ wrote:


I keep seeing all of these posts online saying how easy it is to disable
systemd from runing fsck because it "honors" the '0' in the sixth field
of /etc/fstab. Well that's just pure bull$h1t... That was one of the
first things I tried some time ago. As far as I can tell on neither of
my Jessie machines (one physical one virtual) does systemd honor the
fstab in terms of doing a fsck. All of the partitions are set to 0 in
/etc/fstab.


That doesn't make it "bullshit", it means that in your instance it 
doesn't help. Instead, just maybe your system is trying to tell you 
something when it continually forces fsck. Read the man page.


The trick is to get your poor stupid dumb machine to tell it's human 
where it hurts and how to fix it. It's like dealing with a puppy that 
whines.


OK, your next message reveals that you are encrypting your drives, 
including swap?? Insert "encrypted hard drive fsck" into your search 
bar. Lately, others report problems.


Another thought would be to disable swap, if you have enough memory to 
see if that helps at all. man swapoff


Since it was encrypted no telling what this would do: man swapoff

swapoff-f, --fixpgsz
Reinitialize (exec /sbin/mkswap) the swap space if its page size
does not match that of the current  running  kernel.   mkswap(2)
initializes the whole device and does not check for bad blocks.
---
At any rate all the fsck'ing is telling you something is broken. That is 
what it is supposed to do. If you are running luks check this:

http://serverfault.com/tags/luks/hot

Happy hunting troubleshooting with a shotgun. :) 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/54acf7fc.5040...@gmail.com

Re: Have I been hacked?

[Mart van de Wege]

Brian  writes:

> On Tue 06 Jan 2015 at 19:47:09 +0100, Martin Steigerwald wrote:
>
>> Am Dienstag, 6. Januar 2015, 21:51:26 schrieb Danny:
>> > Hi guys,
>> > 
>> > I am afraid my happiness was short lived. To test if the deletion of the
>> > file (and the effects thereof) would be permanent I rebooted the system and
>> > consequently found another file (same size, same random lettering) booted
>> > up with everything else. :( ... The culprit is well hidden and regenerates
>> > itself ...
>> 
>> Well… if something creates a file in /boot, it needs to be started 
>> somewhere. I 
>> still bet an examination along the ideas I suggested from a live distro may 
>> reveal where the file is created. Or it may not, at least not easily, if a 
>> changed binary creates the file, instead of some script. Its still not clear 
>> whether its really a malware or just some broken third party software you 
>> installed, but… if you didn´t install any broken third party software and it 
>> really is, read on.
>
> Are we now to assume these files are only created on boot? The OP could 
> at least look into this and let us know whether this is so. It looks to
> me there is some configuration which creates them. The configuration is
> far more likely to have been produced by him than some invader.
>
I've seen malware that downloaded a BitCoin miner and installed it, and
reinstalled itself if removed.

That one was rather dumb and had installed the check for installation
and download script in a cronjob, so it was easy to remove, but if it is
at any rate possible, reinstalling is the best bet.

Mart
-- 
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.


-- 
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/86bnmbhtxg@gaheris.avalon.lan

xterm choking on compose key input

[Kumar Appaiah]

Hi.

I regularly use the compose key to insert characters. The locale I
use, en_IN, doesn't have a Compose file in /usr/share/X11/locale, so I
copied the /usr/share/X11/locale/en_US.UTF-8/Compose file to
~/.XCompose.

Now, most applications work fine. However, xterm seems to choke on
compose key input, and I get garbage whenever I type any compose key
sequence. However, if I run LANG=en_US.UTF-8 xterm, then it works
fine.

Is there a way to fix xterm, short of changing my locale or writing a
wrapper that calls "LANG=en_US.UTF-8 xterm"?

Thanks.

Kumar


-- 
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/20150107083850.ga4...@bluemoon.iitb.ac.in

Re: debhelper stripping debugging symbols

[Don Armstrong]

On Tue, 06 Jan 2015, Kip Warner wrote:
> I am trying to debianize a personal package for native compilation. I
> packaged it using the debhelper 7 syntax as aided with dh_make.
> 
> After customizing my debian/* metadata and scripts, I noticed that
> dh_strip is still stripping debugging symbols from my executable, even
> though debian/rules sets DEB_BUILD_OPTIONS=nostrip. The flag appears to
> be totally ignored, or perhaps clobbered later?
> 
> build log:
> ...
>dh_strip
>   strip --remove-section=.comment --remove-section=.note 
> debian/my-tool/usr/bin/my-tool
>dh_makeshlibs
>   rm -f debian/my-tool/DEBIAN/shlibs
> ...
> 
> My debian/rules below. Any help appreciated 
> 
> 

This line:

export DEB_BUILD_OPTIONS=

sets DEB_BUILD_OPTIONS to "", which isn't what you want.

Furthermore, it's bad practice to set DEB_BUILD_OPTIONS in debian/rules,
and you really don't need to set any of the other variables you're
setting in debian/rules, either, nor do you need to include
/usr/share/dpkg/default.mk, because dh knows how to do all of that
itself, too.

Finally, your debian/rules is missing a #!/usr/bin/make -f, which means
that it isn't going to work at all.

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

I really wanted to talk to her.
I just couldn't find an algorithm that fit.
 -- Peter Watts _Blindsight_ p294


-- 
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/20150107080741.go29...@teltox.donarmstrong.com