Re: Xorg replaces TTY1

[Felix Miata]

Martin Str|mberg composed on 2015-12-02 07:39 (UTC+0100):

> Chris Bannister wrote:

>> On Thu, Nov 26, 2015 at 06:54:34PM +, Brian wrote:

>> > There are still users (an example is in
>> > this thread) who believe ctrl-alt-backspace no longer works in Debian.
>> > It does.

>> So it does! Wonder why it didn't work for me on another machine. :(

> It's because those nice and user-friendly DE have it disabled by
> default (IIRC). I always have to go search for where they've hidden
> that option this time, when I try another one or a new version.

I mostly use KDE, never Gnome, little other. That said,
/etc/X11/xorg.conf.d/00-keyboard.conf always works for me:

Section "InputClass"
Identifier "system-keyboard"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Xorg replaces TTY1

[Martin Str|mberg]

In article  Chris Bannister 
 wrote:
> On Thu, Nov 26, 2015 at 06:54:34PM +, Brian wrote:
> > There are still users (an example is in
> > this thread) who believe ctrl-alt-backspace no longer works in Debian.
> > It does.

> So it does! Wonder why it didn't work for me on another machine. :(

It's because those nice and user-friendly DE have it disabled by
default (IIRC). I always have to go search for where they've hidden
that option this time, when I try another one or a new version.


-- 
MartinS

(SOLVED) Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Marc Shapiro]

On 12/01/2015 02:05 PM, Sven Arvidsson wrote:

On Tue, 2015-12-01 at 16:39 -0500, Felix Miata wrote:

"Now", as in Stretch and/or Sid? I searched in Jessie and failed to
discover
any available firmware-amd-graphics. Is another repo besides main and
updates
required? I booted same machine to Stretch, and neither package was
found.
And, Stretch is also using FBDEV, like OP here, and stuck in
1280x1024 on a
1680x1050 display, with libdrm-radeon1, xserver-xorg-video-ati and
xserver-xorg-video-radeon installed. ???


Sid and/or stretch, I don't recall exactly when the split was made.

The clue is in the name, nonfree ;)

The correct package in Jessie is firmware-linux-nonfree.  It apparently 
no longer pulls in anything else and has all the drivers, itself.  There 
is no firmware-amd-graphics in Jessie.  Yes.  Having nonfree in your 
sources list does help, but I do keep it there. Installing 
firmware-linux-nonfree and rebooting was the answer.


Thank you to everybody that helped on this.  Since this is solved and 
the answer wasn't found in the logs, I will pass on sending a really 
long post by including the logs.


Marc

Re: OT: reply styles, family matters

[Stuart Longland]

On 01/12/15 11:56, John Hasler wrote:
> Bob Bernstein writes:
>> With that as background, here is my question/request: is anyone aware
>> of a spirited defence of our ideal method of "selective quoting," (for
>> lack of a better label) one, say, that perhaps has achieved the status
>> of a "net classic?" Surely some 'net genius has dealt these
>> nay-sayers, who seem to LIKE top-posting, a solid uppercut?
> 
> Waste of effort.  The usual reason for top-posting (or bottom-posting
> without editing) is laziness.
> 

I often counter that by passing my would-be reply through tac and
top-post it that way.

Then they see it from my perspective.
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.



signature.asc
Description: OpenPGP digital signature

Re: A stop job is running for...

[James P. Wallen]

On 12/01/2015 09:47 AM, Sven Arvidsson wrote:

On Mon, 2015-11-30 at 21:04 -0500, Jape Person wrote:

Make remote CUPS printers available locally
Network Time Synchronization

For several weeks I've been seeing this stop job notification for
these
two items frequently when rebooting or shutting down two of my four
testing systems.

The first notification counts all the way up to 1 min 30 sec before
the
shutdown scroll restarts. The second notification only counts for a
few
seconds before terminating.

I'm a patient guy, but adding almost two minutes to almost every
restart
or shutdown procedure gets a bit tedious after a while.


Yes, I have noticed this too, but with different services. So it's
probably not specific to CUPS or NTP.

Unfortunately it seems to always happen when I need to shutdown quickly
(thunderstorms). Would be great if it was possible to configure the
countdown to simply kill the service after a few seconds and proceed
with shutdown/reboot.



Thanks for your response, Sven. It's nice to know that someone else has 
seen this type of problem. I was thinking that this could be 
self-inflicted. Perhaps that's a little less likely now.


So, is this behavior controlled by systemd?

I'm not trying to start a fracas. I'm really interested. What I'm asking 
is, do I need to start poring over systemd documentation to see if there 
might be a way to control this behavior?

Re: Recent linux-image update broke CPU fan

[Neal P. Murphy]

On Sun, 29 Nov 2015 17:18:51 -0500
"Neal P. Murphy"  wrote:

> On Sun, 29 Nov 2015 14:35:15 +0100
> Sven Arvidsson  wrote:
> 
> > On Sun, 2015-11-29 at 02:16 -0500, Neal P. Murphy wrote:
> > > I think the last linux-image update broke my CPU fan. OK, it didn't
> > > actually break it. But since the last update, my CPU fan (stock with
> > > vishera 8350 black) will NOT turn faster than about 3500 RPM.
> > > 
> > > I have been using fancontrol for months. It took weeks to get it set
> > > correctly. At maximum speed, I've seen (and heard) the fan turn in
> > > excess of 6500 RPM.
> > > 
> > > Until the recent kernel update, the CPU and case fans have ramped up
> > > with increasing temp and ramped down with decreasing temp. The CPU
> > > never exceeded about 60C when compiling linux using all 8 CPUs for 5
> > > minutes. And that was with a mild overclock (4.4GHz, 1866 RAM at
> > > 2133).
> > > 
> > > Now, the CPU fan will not exceed about 3700 RPM. That's barely fast
> > > enough to keep 4 non-overclocked CPUs cool.
> > > 
> > > Has anyone else experienced this? Is it related to the kernel update?
> > > Or do I have a power supply or motherboard failing (again)?
> > 
> > If this was on a stable system it seems odd, if it was unstable or
> > testing it might just be one of the "charms" of running something that
> > is in development.

It's still odd. But with no change to the OS, the fan speed has returned. So 
I'm going to conclude that it is related to hardware and/or firmware (flaky 
NVRAM, flaky power supply, flaky mainboard, &c.), that the kernel update was 
not the cause.

Thanks,
N

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Felix Miata]

Sven Arvidsson composed on 2015-12-01 23:05 (UTC+0100):

> On Tue, 2015-12-01 at 16:39 -0500, Felix Miata wrote:

>> "Now", as in Stretch and/or Sid? I searched in Jessie and failed to discover
>> any available firmware-amd-graphics. Is another repo besides main and updates
>> required? I booted same machine to Stretch, and neither package was found.
>> And, Stretch is also using FBDEV, like OP here, and stuck in 1280x1024 on a
>> 1680x1050 display, with libdrm-radeon1, xserver-xorg-video-ati and
>> xserver-xorg-video-radeon installed. ???

> Sid and/or stretch, I don't recall exactly when the split was made.

> The clue is in the name, nonfree ;)

Helps to have non-free included in apt sources before searching for nonfree
packages. :-p I wonder if this omission accounts for OP?
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Can't startx as normal user

[Rodrigo S. Cañibano]

On 1 December 2015 at 16:47, Sven Arvidsson  wrote:
> The NEWS entry should have been picked up by apt-listchanges:

I must have missed it. Thanks!

Re: X using ~ 35% of a CPU core

[Celejar]

On Mon, 30 Nov 2015 21:47:43 +0100
Sven Arvidsson  wrote:

> On Mon, 2015-11-30 at 13:44 -0500, Celejar wrote:
> > Hi,
> > 
> > On my ThinkPad T61 (Core 2 Duo T7300 @ 2.00GHZ) running Debian stable
> > (8.2) with Xfce, the X process (/usr/bin/X) has recently begun to
> > consume some 35% (seems to vary between 33-40 %) for several minutes
> > at
> > a time, with the system becoming unpleasantly unresponsive during
> > this

...

> Long shot, but maybe it's something similar to this? Probing for new
> screens after resume and spamming a log before giving up?
> 
> https://bbs.archlinux.org/viewtopic.php?id=204098
> 
> Would be interesting to know where the X process spends all that time,
> but I guess you would need to profile it to find out.

Thanks for the tip! My problem is actually at least somewhat similar. I
tried tailing the X log when I caught the problem occurring, and I
found zillions of these:

[ 82198.046] (II) intel(0): EDID vendor "LEN", prod id 16435
[ 82198.046] (II) intel(0): Printing DDC gathered Modelines:
[ 82198.046] (II) intel(0): Modeline "1440x900"x0.0   96.50  1440 1522 1576 
1706  900 905 914 943 -hsync -vsync (56.6 kHz eP)
[ 82198.046] (II) intel(0): Modeline "1440x900"x0.0   80.44  1440 1522 1576 
1706  900 905 914 943 -hsync -vsync (47.2 kHz e)
[ 82198.084] (II) intel(0): EDID vendor "LEN", prod id 16435
[ 82198.084] (II) intel(0): Printing DDC gathered Modelines:
[ 82198.084] (II) intel(0): Modeline "1440x900"x0.0   96.50  1440 1522 1576 
1706  900 905 914 943 -hsync -vsync (56.6 kHz eP)
[ 82198.084] (II) intel(0): Modeline "1440x900"x0.0   80.44  1440 1522 1576 
1706  900 905 914 943 -hsync -vsync (47.2 kHz e)
[ 82198.166] (II) intel(0): EDID vendor "LEN", prod id 16435
[ 82198.166] (II) intel(0): Printing DDC gathered Modelines:
[ 82198.166] (II) intel(0): Modeline "1440x900"x0.0   96.50  1440 1522 1576 
1706  900 905 914 943 -hsync -vsync (56.6 kHz eP)
[ 82198.166] (II) intel(0): Modeline "1440x900"x0.0   80.44  1440 1522 1576 
1706  900 905 914 943 -hsync -vsync (47.2 kHz e)

...

[ 82198.574] (II) intel(0): EDID vendor "LEN", prod id 16435
[ 82198.574] (II) intel(0): Printing DDC gathered Modelines:
[ 82198.574] (II) intel(0): Modeline "1440x900"x0.0   96.50  1440 1522 1576 
1706  900 905 914 943 -hsync -vsync (56.6 kHz eP)
[ 82198.574] (II) intel(0): Modeline "1440x900"x0.0   80.44  1440 1522 1576 
1706  900 905 914 943 -hsync -vsync (47.2 kHz e)
[ 82198.662] (II) intel(0): EDID vendor "LEN", prod id 16435
[ 82198.662] (II) intel(0): Printing DDC gathered Modelines:
[ 82198.662] (II) intel(0): Modeline "1440x900"x0.0   96.50  1440 1522 1576 
1706  900 905 914 943 -hsync -vsync (56.6 kHz eP)
[ 82198.662] (II) intel(0): Modeline "1440x900"x0.0   80.44  1440 1522 1576 
1706  900 905 914 943 -hsync -vsync (47.2 kHz e)
[ 82198.710] (II) intel(0): EDID vendor "LEN", prod id 16435
[ 82198.710] (II) intel(0): Printing DDC gathered Modelines:
[ 82198.710] (II) intel(0): Modeline "1440x900"x0.0   96.50  1440 1522 1576 
1706  900 905 914 943 -hsync -vsync (56.6 kHz eP)
[ 82198.710] (II) intel(0): Modeline "1440x900"x0.0   80.44  1440 1522 1576 
1706  900 905 914 943 -hsync -vsync (47.2 kHz e)


When the problem ceases (CPU usage back down to zero / normal), these
lines cease, too. Anyone know what this is, and / or how to fix it?

I found this:

https://forums.gentoo.org/viewtopic-t-716774-start-0.html

But I don't have anything like his xrandr script running, and my
problem is intermittent - it starts and stops at apparently random
times.

> Sven Arvidsson

Celejar

Re: Problems with Gmail IMAP on Icedove

[Lisi Reisz]

On Monday 30 November 2015 23:06:06 Lisi Reisz wrote:
> I have been trying to set up IMAP from two different accounts on Gmail in
> Icedove: 31.8.0-1~deb7u1.  I have tired changing the password in case I had
> got it wrong, I have retyped everything several times, I have copied and
> pasted, I have crawled up the wall, then I suddenly started to get messages
> from Gmail:
> 
>
> Sign-in attempt prevented
>
>
>
> Hi x,
> Someone just tried to sign in to your Google Account xx...@gmail.com
> from an app that doesn't meet modern security standards.


Annoying as this was, Google may have had a point:

Just received from security alerts:

Multiple security issues have been found in Icedove, Debian's version of
the Mozilla Thunderbird mail client: Multiple memory safety errors,
integer overflows, buffer overflows and other implementation errors may
lead to the execution of arbitrary code or denial of service.

For the oldstable distribution (wheezy), these problems have been fixed
in version 38.4.0-1~deb7u1.


Lisi

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Sven Arvidsson]

On Tue, 2015-12-01 at 16:39 -0500, Felix Miata wrote:
> "Now", as in Stretch and/or Sid? I searched in Jessie and failed to
> discover
> any available firmware-amd-graphics. Is another repo besides main and
> updates
> required? I booted same machine to Stretch, and neither package was
> found.
> And, Stretch is also using FBDEV, like OP here, and stuck in
> 1280x1024 on a
> 1680x1050 display, with libdrm-radeon1, xserver-xorg-video-ati and
> xserver-xorg-video-radeon installed. ???
> 

Sid and/or stretch, I don't recall exactly when the split was made.

The clue is in the name, nonfree ;)

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5





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

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Felix Miata]

Sven Arvidsson composed on 2015-12-01 18:15 (UTC+0100):

> On Tue, 2015-12-01 at 12:01 -0500, Felix Miata wrote:

>> Hmmm. My Cedar is working in Jessie, and there is no firmware-amd-graphics
>> installed. Neither do aptitude search firmware-amd-graphics or aptitude
>> search amd-graph return anything. firmware-linux-nonfree however is
>> installed.

> The AMD firmware used to be in firmware-linux-nonfree. Now that is a
> metapackage that depends on firmware-amd-graphics and a few others.

"Now", as in Stretch and/or Sid? I searched in Jessie and failed to discover
any available firmware-amd-graphics. Is another repo besides main and updates
required? I booted same machine to Stretch, and neither package was found.
And, Stretch is also using FBDEV, like OP here, and stuck in 1280x1024 on a
1680x1050 display, with libdrm-radeon1, xserver-xorg-video-ati and
xserver-xorg-video-radeon installed. ???

http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-big41-stretch-fbdev
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: OT: reply styles, family matters

[Bob Bernstein]

On Tue, 1 Dec 2015, anxious...@gmail.com wrote:

If I bottom posted at work, no-one would ever discover my 
replies. I occasionally interleave if a point by point 
response seems sensible, or if the joke only works that way


Word dat. 

--
Bob Bernstein

Re: Trying to remove "architecture i386"

[Steve McIntyre]

boudic...@skimble.plus.com wrote:
>Ansgar Burchardt <"Ansgar Burchardt"@43-1.org> writes:
>>
>> Do you still have any i386 packages installed? I think running
>>
>>   dpkg -l "*:i386"
>>
>> should list them (I don't use multiarch myself, but it works for the
>> native architecture and "*:all").
>>
>> Ansgar
>
>Thanks Ansgar.
>
>--8<---cut here---start->8---
>dpkg -l "*:i386"
>Desired=Unknown/Install/Remove/Purge/Hold
>| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>||/ Name  Version   Architecture  Description
>+++-=-=-=-===
>rc  crossover 14.1.11-1 i386  Run Windows 
>applications like MS Office
>rc  libasound2:i386   1.0.28-1  i386  shared 
>library for ALSA applications
>rc  libc6:i3862.19-18+deb8u1i386  GNU C 
>Library: Shared libraries
>rc  libc6-i686:i386   2.19-18+deb8u1i386  GNU C 
>Library: Shared libraries [i686 optimized]
>rc  libxxf86vm1:i386  1:1.1.3-1+b1  i386  X11 XFree86 
>video mode extension library



>rc  zlib1g:i386   1:1.2.8.dfsg-2+b1 i386  compression 
>library - runtime
>--8<---cut here---end--->8---
>
>Wow, that *is* a lot! But I don't think that they're all installed, ATM.
>I don't know what the "rc" means though.

It's not the clearest unless you're looking for it, but it's in the
header at the top of the output. "r" means "Remove", "c" means
"Conf-files", i.e. the packages have been (or are about to be) removed
but still have configuration left. A normally installed package would
be shown as "ii", by comparison.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Further comment on how I feel about IBM will appear once I've worked out
 whether they're being malicious or incompetent. Capital letters are forecast."
 Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html

Re: Can't startx as normal user

[Sven Arvidsson]

On Mon, 2015-11-30 at 19:20 -0300, Draco Metallium(Rodrigo S. Cañibano)
wrote:
> It could be that, since I don't have systemd, nor systemd-shim
> installed (I just checked again).
> 
> I had to install xserver-xorg-legacy, just as Harald Dunkel
> suggested.
> 
> Should't apt-get have warned me that there were unmet dependencies?

The NEWS entry should have been picked up by apt-listchanges:
https://sources.debian.net/src/xorg-server/2:1.17.3-2/debian/xserver-xorg-core.NEWS/

(And will probably also be mentioned in the release docs)

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5





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

Re: L7 filter and iptables Problem

[Muhammad Yousuf Khan]

Thanks i manage to do that with IPtable string  and ipp2p
although still in monitoring however i am seeing some good result.
hopefully that will work.
Thanks,
Yousuf

On Tue, Dec 1, 2015 at 10:58 PM, Roman  wrote:

> Hi,
>
> Even if it would be supported there is no much use of iptables l7 filters.
> They never worked as expected. Get yourself a small juniper srx  :)
>
> 2015-12-01 19:51 GMT+02:00 Peter Ludikovsky :
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi,
>>
>> According to to project site [0] there hasn't been any real
>> development since 2013, which was a patch against the 2.6 kernel line.
>> That kernel line is out of support since mid-2015.
>>
>> I'm afraid the string matching module would be your best bet for now.
>>
>> Regards,
>> /peter
>>
>> [0] http://l7-filter.clearos.com/
>>
>> Am 01.12.2015 um 08:56 schrieb Muhammad Yousuf Khan:
>> > Hello,
>> >
>> > i am using  Debian jessie and I have been trying to work with L7
>> > filter to block p2p but its not working
>> >
>> > iptables -I FORWARD -m layer7 --l7proto bittorrent -j DROP iptables
>> > v1.4.21: Couldn't load match `layer7':No such file or directory
>> >
>> > Try `iptables -h' or 'iptables --help' for more information.
>> >
>> > can you guys Please help.  string match with ip tables is easy but
>> > i am looking to use L7 filter on jessie. all the how-tos are out
>> > dated. example kernel patch etc.
>> >
>> > Please help.
>> >
>> > Thanks, Yousuf
>> >
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v2.0.22 (MingW32)
>>
>> iQIcBAEBAgAGBQJWXd4OAAoJEM+6Ng5pbtyZAd8P/3vM3gVfiaUcVVdxsNPkRIzb
>> NddWvxnWwYp4DNCHRj5sKAJ4X5DhdqClEysT8eLMBfG+IXLW44mF/M3NBeVsbMAk
>> 5ugH4hlyaIK2Pxh1yIHOCz1uP7yRnj8X6ASp5PxbzBTowmHLynjyka0OnEdg0pR4
>> hsNvw9RyxPKPuqBTXy37SXGbp8mBmuFbQucaX7G80e8n5reCL9CvLTHKLiQ3BGdc
>> KanmYQjZ7K1/FISuBpl653iiR/Kpb4bfY2x2Nl54Pxs2ueFMwskIqsfGyxU6nSPb
>> Hk9OpDpJlQ14PTxZ2Tw/tvPJIhFqvQshrVD57OvQhgXrda+7o/sz1DbL5djLSAPj
>> b05luaVW9U+88XgAkcNPNZfrohy3JY1EnXPY5n3M83yZZ7QPPlwxc66Nu2PBS/rM
>> B0erP4t0c2tqxpMoewSmlX3Q0qm83IRET9ozSMqoEWbFYho499MR+uyTCkw1YO05
>> JfHS/4o/t+z9PzHo1h2r0tqij52WcgeD4TSZ8W4MdZxMmwk6w+XOsJYDpY7eX2gt
>> a6IRr5/pgzv6PLWjpXSwj1XCtQUxoZkWS7GPF5qfbBh1/t3hjRe6Hv8MwQPP0oSw
>> LelvMIhii2NVvlPueuSWH46XencEQId66wTkAx02YxP84FMctw7jJl7oljb/JrQ7
>> EXo9Iaaohz1ZjLSH3+Ht
>> =rHnt
>> -END PGP SIGNATURE-
>>
>>
>
>
> --
> Best regards,
> Roman.
>

Re: Trying to remove "architecture i386"

[Sharon Kimble]

Sharon Kimble  writes:

> I am running a "amd64" version of jessie and in an effort to get
> 'crossover_14.1.11-1.deb' installed, which is 32-bit. To do this I issued the
> command -
>
> ╭
> │sudo dpkg --add-architecture i386
> ╰
>
> and then -
>
> ╭
> │dpkg --print-foreign-architectures
> ╰
>
> then I did a 'apt-get update' and tried to install crossover again. I've
> now given up trying to instal it and wish to move back to just being a
> 64-bit machine using amd64 packages only. I've therefore done -
>
> ╭
> │sudo dpkg --remove-architecture i386
> ╰
>
> which failed saying -
>
> dpkg: error: cannot remove architecture 'i386' currently in use by the 
> database
>
> How then can I remove 'i386' please, or should I just cut my losses and 
> reinstall?
>

I think that I've resolved the situation by -

--8<---cut here---start->8---
deb [arch=amd64] http://foo
deb-src [arch=amd64] http://foo
--8<---cut here---end--->8---

in my sources.list.

I installed all amd64 packages that were shown as being removed in
yesterdays logwatch, and then I manually removed all the i386 packages
From /var/cache/apt/archives and then rebooted.

Everything came back up successfully, and I then "sudo dpkg
--remove-architecture i386" and checked using "dpkg
--print-foreign-architectures" which showed a zero response, and I then
"dpkg --print-architecture" which showed "amd64"!

Mission accomplished!

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.0, fluxbox 1.3.7, emacs 24.5.1


signature.asc
Description: PGP signature

Re: Disable Ctrl-Alt-Del in Jessie [Solved]

[Bit Head]

Thanks, Martin. With that info, I was able to confirm that the link 
'control-alt-del.target -> /dev/null' does disable C-A-D from a tty.  And it 
took a bit to find it, but the behavior in KDE can be managed in:

System Settings --> Shortcuts and Gestures --> Global Keyboard Shortcuts --> 
The KDE Session Manager (from the pull down menu)

There are 3 items there which can be configured independently: Log Out, Log Out 
without Confirmation, and Reboot without Confirmation.  Each can have its own 
keystroke sequence, or be set to None.

Yeah!  No more erroneous reboots due to Windows screen lock attempts on Jessie! 
:-)


From: Martin Read 
Sent: Monday, November 30, 2015 4:31 PM
To: debian-user@lists.debian.org
Subject: Re: Disable Ctrl-Alt-Del in Jessie

On 30/11/15 00:05, Bit Head wrote:
> In Jessie, this is proving to be more challenging as there is no inittab
> file to edit, and while I could create one, it would only contain
> commented lines, having a null effect.  It seems that in prior releases,
> one had to explicitly say what to do in order for anything to happen,
> and in Jessie, one has to explicitly say "do nothing" or action is taken
> (the logout/reboot/shutdown prompt is presented with a 30 second timeout).

That logout/reboot/shutdown prompt is a feature of your GUI environment,
which should have a mechanism for configuring it to do something *else*
(or, hopefully, nothing at all) in response to C-A-D.

For example, my XFCE4 environment is configured to lock the console when
I make the three-finger salute.

Re: Trying to remove "architecture i386"

[Sharon Kimble]

Ansgar Burchardt <"Ansgar Burchardt"@43-1.org> writes:

> Sharon Kimble  writes:
>> ╭
>> │sudo dpkg --remove-architecture i386
>> ╰
>>
>> which failed saying -
>>
>> dpkg: error: cannot remove architecture 'i386' currently in use by the 
>> database
>>
>> How then can I remove 'i386' please, or should I just cut my losses and 
>> reinstall?
>
> Do you still have any i386 packages installed? I think running
>
>   dpkg -l "*:i386"
>
> should list them (I don't use multiarch myself, but it works for the
> native architecture and "*:all").
>
> Ansgar

Thanks Ansgar.

--8<---cut here---start->8---
dpkg -l "*:i386"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version   Architecture  Description
+++-=-=-=-===
rc  crossover 14.1.11-1 i386  Run Windows 
applications like MS Office
rc  libasound2:i386   1.0.28-1  i386  shared 
library for ALSA applications
rc  libc6:i3862.19-18+deb8u1i386  GNU C 
Library: Shared libraries
rc  libc6-i686:i386   2.19-18+deb8u1i386  GNU C 
Library: Shared libraries [i686 optimized]
rc  libdrm2:i386  2.4.58-2  i386  Userspace 
interface to kernel DRM services -- runtime
rc  libexpat1:i3862.1.0-6+deb8u1i386  XML parsing C 
library - runtime library
rc  libfreetype6:i386 2.5.2-3+deb8u1i386  FreeType 2 
font engine, shared library files
rc  libgcc1:i386  1:4.9.2-10i386  GCC support 
library
rc  libgl1-mesa-glx:i386  10.3.2-1+deb8u1   i386  free 
implementation of the OpenGL API -- GLX runtime
rc  libglapi-mesa:i38610.3.2-1+deb8u1   i386  free 
implementation of the GL API -- shared library
rc  libglu1-mesa:i386 9.0.0-2   i386  Mesa OpenGL 
utility library (GLU)
rc  libice6:i386  2:1.0.9-1+b1  i386  X11 
Inter-Client Exchange library
rc  liblcms2-2:i386   2.6-3+b3  i386  Little CMS 2 
color management library
rc  libpng12-0:i386   1.2.50-2+deb8u1   i386  PNG library - 
runtime
rc  libsm6:i386   2:1.2.2-1+b1  i386  X11 Session 
Management library
rc  libstdc++6:i386   4.9.2-10  i386  GNU Standard 
C++ Library v3
rc  libudev1:i386 215-17+deb8u2 i386  libudev 
shared library
rc  libuuid1:i386 2.25.2-6  i386  Universally 
Unique ID library
rc  libx11-6:i386 2:1.6.2-3 i386  X11 
client-side library
rc  libx11-xcb1:i386  2:1.6.2-3 i386  Xlib/XCB 
interface library
rc  libxau6:i386  1:1.0.8-1 i386  X11 
authorisation library
rc  libxcb-dri2-0:i3861.10-3+b1 i386  X C Binding, 
dri2 extension
rc  libxcb-dri3-0:i3861.10-3+b1 i386  X C Binding, 
dri3 extension
rc  libxcb-glx0:i386  1.10-3+b1 i386  X C Binding, 
glx extension
rc  libxcb-present0:i386  1.10-3+b1 i386  X C Binding, 
present extension
rc  libxcb-sync1:i386 1.10-3+b1 i386  X C Binding, 
sync extension
rc  libxcb1:i386  1.10-3+b1 i386  X C Binding
rc  libxcursor1:i386  1:1.1.14-1+b1 i386  X cursor 
management library
rc  libxdamage1:i386  1:1.1.4-2+b1  i386  X11 damaged 
region extension library
rc  libxdmcp6:i3861:1.1.1-1+b1  i386  X11 Display 
Manager Control Protocol library
rc  libxext6:i386 2:1.3.3-1 i386  X11 
miscellaneous extension library
rc  libxfixes3:i386   1:5.0.1-2+b2  i386  X11 
miscellaneous 'fixes' extension library
rc  libxi6:i386   2:1.7.4-1+b2  i386  X11 Input 
extension library
rc  libxrandr2:i386   2:1.4.2-1+b1  i386  X11 RandR 
extension library
rc  libxrender1:i386  1:0.9.8-1+b1  i386  X Rendering 
Extension client library
rc  libxshmfence1:i3861.1-4 i386  X shared 
memory fences - shared library
rc  libxxf86vm1:i386  1:1.1.3-1+b1  i386  X11 XFree86 
video mode extension library
rc  zlib1g:i386   1:1.2.8.dfsg-2+b1 i386  compression 
library - runtime
--8<---cut here---end--->8---

Wow, that *is* a lot! But I don't think that they're all in

Re: L7 filter and iptables Problem

[Roman]

Hi,

Even if it would be supported there is no much use of iptables l7 filters.
They never worked as expected. Get yourself a small juniper srx  :)

2015-12-01 19:51 GMT+02:00 Peter Ludikovsky :

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> According to to project site [0] there hasn't been any real
> development since 2013, which was a patch against the 2.6 kernel line.
> That kernel line is out of support since mid-2015.
>
> I'm afraid the string matching module would be your best bet for now.
>
> Regards,
> /peter
>
> [0] http://l7-filter.clearos.com/
>
> Am 01.12.2015 um 08:56 schrieb Muhammad Yousuf Khan:
> > Hello,
> >
> > i am using  Debian jessie and I have been trying to work with L7
> > filter to block p2p but its not working
> >
> > iptables -I FORWARD -m layer7 --l7proto bittorrent -j DROP iptables
> > v1.4.21: Couldn't load match `layer7':No such file or directory
> >
> > Try `iptables -h' or 'iptables --help' for more information.
> >
> > can you guys Please help.  string match with ip tables is easy but
> > i am looking to use L7 filter on jessie. all the how-tos are out
> > dated. example kernel patch etc.
> >
> > Please help.
> >
> > Thanks, Yousuf
> >
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (MingW32)
>
> iQIcBAEBAgAGBQJWXd4OAAoJEM+6Ng5pbtyZAd8P/3vM3gVfiaUcVVdxsNPkRIzb
> NddWvxnWwYp4DNCHRj5sKAJ4X5DhdqClEysT8eLMBfG+IXLW44mF/M3NBeVsbMAk
> 5ugH4hlyaIK2Pxh1yIHOCz1uP7yRnj8X6ASp5PxbzBTowmHLynjyka0OnEdg0pR4
> hsNvw9RyxPKPuqBTXy37SXGbp8mBmuFbQucaX7G80e8n5reCL9CvLTHKLiQ3BGdc
> KanmYQjZ7K1/FISuBpl653iiR/Kpb4bfY2x2Nl54Pxs2ueFMwskIqsfGyxU6nSPb
> Hk9OpDpJlQ14PTxZ2Tw/tvPJIhFqvQshrVD57OvQhgXrda+7o/sz1DbL5djLSAPj
> b05luaVW9U+88XgAkcNPNZfrohy3JY1EnXPY5n3M83yZZ7QPPlwxc66Nu2PBS/rM
> B0erP4t0c2tqxpMoewSmlX3Q0qm83IRET9ozSMqoEWbFYho499MR+uyTCkw1YO05
> JfHS/4o/t+z9PzHo1h2r0tqij52WcgeD4TSZ8W4MdZxMmwk6w+XOsJYDpY7eX2gt
> a6IRr5/pgzv6PLWjpXSwj1XCtQUxoZkWS7GPF5qfbBh1/t3hjRe6Hv8MwQPP0oSw
> LelvMIhii2NVvlPueuSWH46XencEQId66wTkAx02YxP84FMctw7jJl7oljb/JrQ7
> EXo9Iaaohz1ZjLSH3+Ht
> =rHnt
> -END PGP SIGNATURE-
>
>


-- 
Best regards,
Roman.

Re: L7 filter and iptables Problem

[Peter Ludikovsky]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

According to to project site [0] there hasn't been any real
development since 2013, which was a patch against the 2.6 kernel line.
That kernel line is out of support since mid-2015.

I'm afraid the string matching module would be your best bet for now.

Regards,
/peter

[0] http://l7-filter.clearos.com/

Am 01.12.2015 um 08:56 schrieb Muhammad Yousuf Khan:
> Hello,
> 
> i am using  Debian jessie and I have been trying to work with L7
> filter to block p2p but its not working
> 
> iptables -I FORWARD -m layer7 --l7proto bittorrent -j DROP iptables
> v1.4.21: Couldn't load match `layer7':No such file or directory
> 
> Try `iptables -h' or 'iptables --help' for more information.
> 
> can you guys Please help.  string match with ip tables is easy but
> i am looking to use L7 filter on jessie. all the how-tos are out
> dated. example kernel patch etc.
> 
> Please help.
> 
> Thanks, Yousuf
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQIcBAEBAgAGBQJWXd4OAAoJEM+6Ng5pbtyZAd8P/3vM3gVfiaUcVVdxsNPkRIzb
NddWvxnWwYp4DNCHRj5sKAJ4X5DhdqClEysT8eLMBfG+IXLW44mF/M3NBeVsbMAk
5ugH4hlyaIK2Pxh1yIHOCz1uP7yRnj8X6ASp5PxbzBTowmHLynjyka0OnEdg0pR4
hsNvw9RyxPKPuqBTXy37SXGbp8mBmuFbQucaX7G80e8n5reCL9CvLTHKLiQ3BGdc
KanmYQjZ7K1/FISuBpl653iiR/Kpb4bfY2x2Nl54Pxs2ueFMwskIqsfGyxU6nSPb
Hk9OpDpJlQ14PTxZ2Tw/tvPJIhFqvQshrVD57OvQhgXrda+7o/sz1DbL5djLSAPj
b05luaVW9U+88XgAkcNPNZfrohy3JY1EnXPY5n3M83yZZ7QPPlwxc66Nu2PBS/rM
B0erP4t0c2tqxpMoewSmlX3Q0qm83IRET9ozSMqoEWbFYho499MR+uyTCkw1YO05
JfHS/4o/t+z9PzHo1h2r0tqij52WcgeD4TSZ8W4MdZxMmwk6w+XOsJYDpY7eX2gt
a6IRr5/pgzv6PLWjpXSwj1XCtQUxoZkWS7GPF5qfbBh1/t3hjRe6Hv8MwQPP0oSw
LelvMIhii2NVvlPueuSWH46XencEQId66wTkAx02YxP84FMctw7jJl7oljb/JrQ7
EXo9Iaaohz1ZjLSH3+Ht
=rHnt
-END PGP SIGNATURE-

Re: OT: reply styles, family matters

[anxiousmac]

On Tuesday, 1 December 2015 16:40:05 UTC, Bob Bernstein  wrote:
> On Wed, 2 Dec 2015, Chris Bannister wrote:
> 
> >> "Please don't respond line by line. It is patronizing and 
> >> annoying."
> 
> > What did he say when you asked what he meant by this? I mean, 
> > how on earth could it possibly be patronising?
> 
> I haven't asked him yet, 
> 
> -- 
> Bob Bernstein

If I bottom posted at work, no-one would ever discover my replies. I 
occasionally interleave if a point by point response seems sensible, or if the 
joke only works that way

anxiousmac

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Sven Arvidsson]

On Tue, 2015-12-01 at 12:01 -0500, Felix Miata wrote:
> Hmmm. My Cedar is working in Jessie, and there is no firmware-amd
> -graphics
> installed. Neither do aptitude search firmware-amd-graphics or
> aptitude
> search amd-graph return anything. firmware-linux-nonfree however is
> installed.

The AMD firmware used to be in firmware-linux-nonfree. Now that is a
metapackage that depends on firmware-amd-graphics and a few others.

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5





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

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Felix Miata]

Felix Miata composed on 2015-12-01 11:50 (UTC-0500):

> Felix Miata composed on 2015-12-01 11:25 (UTC-0500):

>> Marc Shapiro composed on 2015-12-01 07:15 (UTC-0800):

>>> I will install  firmware-amd-graphics as soon as I get a chance 

>> firmware-linux-nonfree is what worked on Jessie for my Cedar and for Mart.

> Oops. Retract. I failed conscious notice of firmware-amd-graphics in Mart's 
> post.

Hmmm. My Cedar is working in Jessie, and there is no firmware-amd-graphics
installed. Neither do aptitude search firmware-amd-graphics or aptitude
search amd-graph return anything. firmware-linux-nonfree however is installed.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Felix Miata]

Felix Miata composed on 2015-12-01 11:25 (UTC-0500):

> Marc Shapiro composed on 2015-12-01 07:15 (UTC-0800):

>> I will install  firmware-amd-graphics as soon as I get a chance 

> firmware-linux-nonfree is what worked on Jessie for my Cedar and for Mart.

Oops. Retract. I failed conscious notice of firmware-amd-graphics in Mart's 
post.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: OT: reply styles, family matters

[Bob Bernstein]

On Wed, 2 Dec 2015, Chris Bannister wrote:

"Please don't respond line by line. It is patronizing and 
annoying."


What did he say when you asked what he meant by this? I mean, 
how on earth could it possibly be patronising?


I haven't asked him yet, in the interest of not muddying still 
waters. I've been thinking about his "patronizing" response and 
I believe it is an objection to the obvious clarity and 
precision that inline responses afford. Clarity and precision 
are not exactly in the ascendancy as far as cultural values are 
concerned. It is thought much more important to be "passionate" 
and "authentic," In the introductory assay of a little book of 
his from 1928, _Sceptical Essays_, Russell said


"...it is undesirable to believe a proposition for which there 
is no ground whatever for supposing it true."


Nobody anymore has the least interest in such an approach to 
life, in fact, it is deemed dangerous and probably evil in most 
of our university English departments and beyond.


However Russell's little gem of a claim describes very 
accurately what is done on email lists devoted to computing 
topics. We want to know what is the case, and why. The vast 
majority of our fellow citizens *do* find a constant focus on 
those aims quite disconcerting in any context, and, very likely, 
"patronizing." They think "How dare you subject me to 
your rules of inference and standards of factuality! What sort 
of horrible person are you?"


I'm guessing your nephew isn't subscribed to any mailing 
lists.


I doubt it.

Would I be correct in that he uses Windoze and outhouse as a 
mailer?


He uses a gmail account with "Ipad Mail".

Oh well. Thanks Chris.

--
Bob Bernstein

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Felix Miata]

Marc Shapiro composed on 2015-12-01 07:15 (UTC-0800):

> I will install  firmware-amd-graphics as soon as I get a chance 

firmware-linux-nonfree is what worked on Jessie for my Cedar and for Mart.

> (probably this evening) and report back.  Meanwhile, Felix says that he 
> never received my post with the full logs and others seem not to have 

Looks like it never reached
https://lists.debian.org/debian-user/2015/12/threads.html either, possibly
due to excessive size, or maybe pasting as attachment rather than inline.

> received them, either, by what they have posted.  For the sake of 
> keeping all of the information available for the future, I will post 

Some people think "all information" should be saved for the future. Others
don't. It's your choice. Be aware that "all information" in the case of Xorg
logs and dmesg is voluminous, and like other mailing list info, stays on the
Internet forever. As some small portion of Xorg.0.log is arguably personal,
one may not wish it to be available forever. Those concerned with noise in
archive searches also may prefer the linking method of log sharing. Little in
those logs is actually relevant to solution, and often, what is is relevant
only to the OP.

Chris Bannister's opinion how to share voluminous data is not universal. On
some other mailing lists, inclusion is explicitly frowned upon. There are no
published/official rules here (of which I'm aware, and I did look) that say
one must or must not pollute list archives with voluminous logs.
http://paste.debian.net/ and other pastebins exist for good reason. Ephemeral
need is precisely one of them. Reducing loss of privacy is another.

> them at that time, as well.  Should they be sent as attachments, or 
> inline.  I sent them as attachments last time. Could that have been the 
> problem?

At this point, what's the point? Solution has almost certainly been
determined to be missing firmware. Xorg.0.log and dmesg won't explain why
firmware was installed in Wheezy but wasn't installed in Jessie. If your
trouble continues after installing firmware, previous logs are unlikely to be
helpful to resolution.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Debian Wheezy boot messages

[Liam O'Toole]

On 2015-12-01, Brian  wrote:
> On Tue 01 Dec 2015 at 12:33:23 +, Liam O'Toole wrote:
>
>> On 2015-11-30, Klaus Jantzen  wrote:
>> > Hallo,
>> >
>> > where are the messages stored that Debain produces during booting (checking
>> > of various components, startup of e.g. postgresql, messages issued by
>> > /udev,
>> > error messages in case a routine could not be started, etc).
>> >
>> > I looked in /var/log through all logs but could not find those messages.
>> >
>> 
>> Try the bootlogd package:
>> 
>> https://packages.debian.org/wheezy/bootlogd
>
> This mail might be of interest:
>
>   https://lists.debian.org/debian-user/2015/10/msg00199.html
>
>> bootlogd is a hack and does not work properly under
>> sysvinit and not at all under systemd.

Yes, that is interesting. My own experience is that bootlogd worked as
intended in Wheezy. I don't use it in Jessie.

-- 

Liam

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Marc Shapiro]

On 12/01/2015 07:03 AM, Sven Arvidsson wrote:

On Mon, 2015-11-30 at 23:11 -0800, Marc Shapiro wrote:

In Wheezy, the graphics card seems to have been found and a depth of
24bpp is being used by RADEON(0) with a GB of graphics memory, while
in
Jessie, Screen 0 is getting deleted and the radeon module is removed.
   
Instead of RADEON(0) we see FBDEV(0), instead of 24bbp, only 16bbp is

being used.  Only 1536kB of video memory is being used and the screen
size is set to "Virtual size is 1024x768 (pitch 1024)".

I don't know enough to determine what is causing these differences,
let
alone how to correct the problem.  If someone else can figure out a
solution I would be most grateful.

Most likely missing firmware as others have suggested, check dmesg and
grep for radeon and/or drm.

I will install  firmware-amd-graphics as soon as I get a chance 
(probably this evening) and report back.  Meanwhile, Felix says that he 
never received my post with the full logs and others seem not to have 
received them, either, by what they have posted.  For the sake of 
keeping all of the information available for the future, I will post 
them at that time, as well.  Should they be sent as attachments, or 
inline.  I sent them as attachments last time. Could that have been the 
problem?


Marc

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Sven Arvidsson]

On Mon, 2015-11-30 at 23:11 -0800, Marc Shapiro wrote:
> In Wheezy, the graphics card seems to have been found and a depth of 
> 24bpp is being used by RADEON(0) with a GB of graphics memory, while
> in 
> Jessie, Screen 0 is getting deleted and the radeon module is removed.
>   
> Instead of RADEON(0) we see FBDEV(0), instead of 24bbp, only 16bbp is
> being used.  Only 1536kB of video memory is being used and the screen
> size is set to "Virtual size is 1024x768 (pitch 1024)".
> 
> I don't know enough to determine what is causing these differences,
> let 
> alone how to correct the problem.  If someone else can figure out a 
> solution I would be most grateful.

Most likely missing firmware as others have suggested, check dmesg and
grep for radeon and/or drm. 

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5





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

Re: Trying to remove "architecture i386"

[Martin Read]

On 01/12/15 08:47, Ansgar Burchardt wrote:

Do you still have any i386 packages installed? I think running

   dpkg -l "*:i386"

should list them (I don't use multiarch myself, but it works for the
native architecture and "*:all").


I can confirm on my multiarch system that the command you suggest will 
do what you intend.

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Marc Shapiro]

On 12/01/2015 04:15 AM, Chris Bannister wrote:

On Mon, Nov 30, 2015 at 05:10:33PM -0800, Marc Shapiro wrote:

On 11/30/2015 04:45 PM, Mike Kupfer wrote:

Marc Shapiro wrote:


On 11/30/2015 04:01 PM, Mike Kupfer wrote:

- Boot a Live image and see what resolution it gives you.

I can still boot into Wheezy and get 1920x1080.

I meant a Jessie Live image.

Though given that you didn't find an old xorg.conf file, the odds of the
Live image doing something different seem pretty slim.

I agree with Felix's recommendation to post information about the
graphics card and at least the Jessie X log file (having both the Jessie
and Wheezy log files would be better).

regards,
mike

I have a copy of Xorg.0.log for both Wheezy and Jessie.  How do I post them
to paste.debian.net?

Please post them to the mailing list for future info.
It's only Felix who suggests that, you've been on the list long enough
to know that logs are sent with the emails.

I have posted them to the list.  My post of Nov. 30 (yesterday) at 5:27 
PM PDT contains the full content of both log files.


Marc

Re: A stop job is running for...

[Sven Arvidsson]

On Mon, 2015-11-30 at 21:04 -0500, Jape Person wrote:
> Make remote CUPS printers available locally
> Network Time Synchronization
> 
> For several weeks I've been seeing this stop job notification for
> these 
> two items frequently when rebooting or shutting down two of my four 
> testing systems.
> 
> The first notification counts all the way up to 1 min 30 sec before
> the 
> shutdown scroll restarts. The second notification only counts for a
> few 
> seconds before terminating.
> 
> I'm a patient guy, but adding almost two minutes to almost every
> restart 
> or shutdown procedure gets a bit tedious after a while.

Yes, I have noticed this too, but with different services. So it's
probably not specific to CUPS or NTP.

Unfortunately it seems to always happen when I need to shutdown quickly
(thunderstorms). Would be great if it was possible to configure the
countdown to simply kill the service after a few seconds and proceed
with shutdown/reboot.

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5





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

Re: OT: reply styles, family matters

[Bob Bernstein]

On Tue, 1 Dec 2015, Lisi Reisz wrote:


On Tuesday 01 December 2015 08:54:27 Mart van de Wege wrote:


Why not do your correspondents the courtesy of replying in 
the style *they* want?


That's fine, so long as you are not required to reply.  And so 
long as you don't want the discussion to remain vaguely on 
track.


And, so long as you _know_ what that desired style is. I've been 
trading emails with my nephew for years with nary a peep from 
him that he was annoyed by, of all things, my email reply style. 
Last night, I guess he had just had it "up to HERE" with me and 
my pompous internet posing!


I have to think about this a bit more because I am starting to 
have it UP TO HERE with him just writing this message! 


Thanks all. I knew I could find cooler heads here than in my 
family.


--
Bob Bernstein

Re: OT: reply styles, family matters

[Chris Bannister]

On Mon, Nov 30, 2015 at 08:31:29PM -0500, Bob Bernstein wrote:
> 
> "Please don't respond line by line. It is patronizing and
> annoying."

What did he say when you asked what he meant by this? I mean, how on
earth could it possibly be patronising?

I'm guessing your nephew isn't subscribed to any mailing lists.

Would I be correct in that he uses Windoze and outhouse as a mailer?

Of course I could be completely wrong, it is just a guess, but I am
intrigued as to how he could find inline responses annoying ... unless
... his client doesn't handle it properly.

I must admit reading mail from yahoo and outhouse mailers is difficult
at the best of times, and is perhaps one reason why top posting is
preferred.

-- 
"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

Re: OT: reply styles, family matters

[Chris Bannister]

On Mon, Nov 30, 2015 at 09:27:02PM -0500, Neal P. Murphy wrote:
> I'll top-post here because I am replying to the entire message (quoted below).

Sorry to be picky, but there was nothing in the text to which you
directly replied to. 

I think personal correspondence is completely different to posting and
replying on a mailing list where it is presumed that posters are using
and familiar with a thread capable mail client.

-- 
"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

Re: Debian Wheezy boot messages

[Brian]

On Tue 01 Dec 2015 at 12:33:23 +, Liam O'Toole wrote:

> On 2015-11-30, Klaus Jantzen  wrote:
> > Hallo,
> >
> > where are the messages stored that Debain produces during booting (checking
> > of various components, startup of e.g. postgresql, messages issued by
> > /udev,
> > error messages in case a routine could not be started, etc).
> >
> > I looked in /var/log through all logs but could not find those messages.
> >
> 
> Try the bootlogd package:
> 
> https://packages.debian.org/wheezy/bootlogd

This mail might be of interest:

  https://lists.debian.org/debian-user/2015/10/msg00199.html

   > bootlogd is a hack and does not work properly under
   > sysvinit and not at all under systemd.

Re: Debian Wheezy boot messages

[Liam O'Toole]

On 2015-11-30, Klaus Jantzen  wrote:
> Hallo,
>
> where are the messages stored that Debain produces during booting (checking
> of various components, startup of e.g. postgresql, messages issued by
> /udev,
> error messages in case a routine could not be started, etc).
>
> I looked in /var/log through all logs but could not find those messages.
>

Try the bootlogd package:

https://packages.debian.org/wheezy/bootlogd

-- 

Liam

Re: Problems with Gmail IMAP on Icedove

[Liam O'Toole]

On 2015-11-30, Lisi Reisz  wrote:
> I have been trying to set up IMAP from two different accounts on Gmail in 
> Icedove: 31.8.0-1~deb7u1.  I have tired changing the password in case I had 
> got it wrong, I have retyped everything several times, I have copied and 
> pasted, I have crawled up the wall, then I suddenly started to get messages 
> from Gmail:
> 
>
> Sign-in attempt prevented
>
>
>
> Hi x,
> Someone just tried to sign in to your Google Account xx...@gmail.com
> from an app that doesn't meet modern security standards.
>
> Details:
> Monday, 30 November 2015 22:35 (GMT)We strongly recommend that you use a
> secure app, like Gmail, to access your account. All apps made by Google
> meet these security standards. Using a less secure app, on the other hand,
> could leave your account vulnerable. Learn more
>.
>
> Google stopped this sign-in attempt, but you should review your recently
> used devices:
> -
>
> I have spent an hour at least trying to enter the * details - and they 
> were fine.  Google had just decided to block me.
>
> The purpose of the exercise wasn't to access the mail, which is only 
> gibberish.  The purpose is to test setting up an IMAP account in Icedove from 
> Gmail.
>
> What do I do now?  Install Thunderbird?  Will it even work in Thunderbird?  
> Give up and tear my hair out?  Icedove isn't even mentioned on the Devices 
> and Activities page or I could tell it to accept it.  And Google would claim 
> that it is being helpful!
>
> I can use Icedove on Wheezy to fetch email from Gmail via POP3.  G.
>
> Lisi
>

Icedove 31.8.0-1~deb8u1 (Jessie) works fine. Google seem to have a
very subtle understanding of Debian version numbers.

-- 

Liam

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Chris Bannister]

On Mon, Nov 30, 2015 at 05:10:33PM -0800, Marc Shapiro wrote:
> On 11/30/2015 04:45 PM, Mike Kupfer wrote:
> >Marc Shapiro wrote:
> >
> >>On 11/30/2015 04:01 PM, Mike Kupfer wrote:
> >>>- Boot a Live image and see what resolution it gives you.
> >>I can still boot into Wheezy and get 1920x1080.
> >I meant a Jessie Live image.
> >
> >Though given that you didn't find an old xorg.conf file, the odds of the
> >Live image doing something different seem pretty slim.
> >
> >I agree with Felix's recommendation to post information about the
> >graphics card and at least the Jessie X log file (having both the Jessie
> >and Wheezy log files would be better).
> >
> >regards,
> >mike
> I have a copy of Xorg.0.log for both Wheezy and Jessie.  How do I post them
> to paste.debian.net?

Please post them to the mailing list for future info.
It's only Felix who suggests that, you've been on the list long enough
to know that logs are sent with the emails.

-- 
"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

Re: OT: reply styles, family matters

[Lisi Reisz]

On Tuesday 01 December 2015 08:54:27 Mart van de Wege wrote:
> Bob Bernstein  writes:
> > "Please don't respond line by line. It is patronizing and
> > annoying."
> >
> > I have acquired over the years a habit of carefully quoting and
> > replying to those quoted snippets. But it rubs some in my family the
> > wrong way. They don't see it as part and parcel of effective
> > communication, or as, at bottom, simply good netiquette. They feel
> > talked down to. My nephew's father had the same problem with me years
> > ago but I think I have brought him around over time so that he no
> > longer "takes it personal."
> >
> > With that as background, here is my question/request: is anyone aware
> > of a spirited defence of our ideal method of "selective quoting," (for
> > lack of a better label) one, say, that perhaps has achieved the status
> > of a "net classic?" Surely some 'net genius has dealt these
> > nay-sayers, who seem to LIKE top-posting, a solid uppercut?
>
> Why not do your correspondents the courtesy of replying in the style
> *they* want?

That's fine, so long as you are not required to reply.  And so long as you 
don't want the discussion to remain vaguely on track.

Lisi

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Mart van de Wege]

Felix Miata  writes:

> Another possibility is that Jessie provides firmware your ATI gfxcard
> requires in a separate firmware package that is not installed, or
> maybe the ATI driver package didn't get installed at all.

I manage a bunch of workstations with exactly this issue. I had to
install firmware-linux-nonfree to get X to recognise the Radeon cards in
these machines. Since firmware-linux-nonfree pulls in
firmware-amd-graphics, I suspect installing the latter will be
sufficient for OP.

Mart

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

Re: OT: reply styles, family matters

[Mart van de Wege]

Bob Bernstein  writes:

> "Please don't respond line by line. It is patronizing and
> annoying."
>
> I have acquired over the years a habit of carefully quoting and
> replying to those quoted snippets. But it rubs some in my family the
> wrong way. They don't see it as part and parcel of effective
> communication, or as, at bottom, simply good netiquette. They feel
> talked down to. My nephew's father had the same problem with me years
> ago but I think I have brought him around over time so that he no
> longer "takes it personal."
>
> With that as background, here is my question/request: is anyone aware
> of a spirited defence of our ideal method of "selective quoting," (for
> lack of a better label) one, say, that perhaps has achieved the status
> of a "net classic?" Surely some 'net genius has dealt these
> nay-sayers, who seem to LIKE top-posting, a solid uppercut?
>
Why not do your correspondents the courtesy of replying in the style
*they* want?

Mart

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

Re: Trying to remove "architecture i386"

[Ansgar Burchardt]

Sharon Kimble  writes:
> ╭
> │sudo dpkg --remove-architecture i386
> ╰
>
> which failed saying -
>
> dpkg: error: cannot remove architecture 'i386' currently in use by the 
> database
>
> How then can I remove 'i386' please, or should I just cut my losses and 
> reinstall?

Do you still have any i386 packages installed? I think running

  dpkg -l "*:i386"

should list them (I don't use multiarch myself, but it works for the
native architecture and "*:all").

Ansgar

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

[Marc Shapiro]

On 11/30/2015 11:32 PM, Felix Miata wrote:

Marc Shapiro composed on 2015-11-30 23:11 (UTC-0800):


Alright.  Knowing nothing about the inner workings of X, I can at least
look through the two log files (in my previous post) and see where they
suddenly go in very different directions.
Using the numbers down the left-hand side of the logs (I don't know what
they actually are, but they seem to be ascending, so I will use them as
markers), at 32.959 in the Wheezy log and at 2271.289 in the Jessie log
they both say:
  (++) using VT number 7
a few lines below that, in the Wheezy log:
[32.974] (II) Module fbdevhw: vendor="X.Org Foundation"
[32.974]compiled for 1.12.4, module version = 0.0.2
[32.974]ABI class: X.Org Video Driver, version 12.1
[32.975] (II) RADEON(0): TOTO SAYS fddc
[32.975] (II) RADEON(0): MMIO registers at 0xfddc: size  128KB
[32.975] (II) RADEON(0): PCI bus 1 card 0 func 0
[32.975] (II) RADEON(0): Creating default Display subsection in Screen 
section
  "Default Screen Section" for depth/fbbpp 24/32
[32.975] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[32.975] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp 
pixmaps)
[32.975] (==) RADEON(0): Default visual is TrueColor
  SKIP
[33.024] (II) RADEON(0): Detected total video RAM=1048576K, 
accessible=262144K (PCI BAR=262144K)
and in the Jessie log:
[  2271.291] (II) Module fbdevhw: vendor="X.Org Foundation"
[  2271.291]compiled for 1.16.4, module version = 0.0.2
[  2271.291]ABI class: X.Org Video Driver, version 18.0
[  2271.291] (**) FBDEV(2): claimed PCI slot 1@0:0:0
[  2271.291] (II) FBDEV(2): using default device
[  2271.291] (WW) Falling back to old probe method for vesa
[  2271.291] (EE) Screen 0 deleted because of no matching config section.
[  2271.291] (II) UnloadModule: "radeon"
[  2271.291] (EE) Screen 0 deleted because of no matching config section.
[  2271.291] (II) UnloadModule: "modesetting"
[  2271.291] (II) FBDEV(0): Creating default Display subsection in Screen 
section
  "Default Screen Section" for depth/fbbpp 16/16
[  2271.291] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16
[  2271.291] (==) FBDEV(0): RGB weight 565
[  2271.291] (==) FBDEV(0): Default visual is TrueColor
[  2271.291] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[  2271.291] (II) FBDEV(0): hardware: simple (video memory: 1536kB)
[  2271.291] (II) FBDEV(0): checking modes against framebuffer device...
[  2271.291] (II) FBDEV(0): checking modes against monitor...
[  2271.291] (--) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
[  2271.291] (**) FBDEV(0):  Built-in mode "current"
[  2271.291] (==) FBDEV(0): DPI set to (96, 96)
In Wheezy, the graphics card seems to have been found and a depth of
24bpp is being used by RADEON(0) with a GB of graphics memory, while in
Jessie, Screen 0 is getting deleted and the radeon module is removed.
Instead of RADEON(0) we see FBDEV(0), instead of 24bbp, only 16bbp is
being used.  Only 1536kB of video memory is being used and the screen
size is set to "Virtual size is 1024x768 (pitch 1024)".

FBDEV doesn't ever support 1920x1080 AFAIK. Video RAM and bpp are non-issues
here. What needs to be determined is why RADEON is not being used in Jessie.
FBDEV is a grossly inferior fallback.


I don't know enough to determine what is causing these differences, let
alone how to correct the problem.  If someone else can figure out a
solution I would be most grateful.

You haven't provided everything requested. We don't know which gfxcard you
have, which 'lspci | grep VGA' would report. Your excerpts from Xorg.0.logs
don't have other info that may be required to help, such as kernel cmdline,
which could be the reason why RADEON is not used. Another possibility is that
Jessie provides firmware your ATI gfxcard requires in a separate firmware
package that is not installed, or maybe the ATI driver package didn't get
installed at all. Read through
https://wiki.debian.org/AtiHowTo#Troubleshooting and you may not need any
more help from us.


Here is the lspci output showing the graphics card:

$ lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI 
Cedar PRO [Radeon HD 5450/6350]


My post prior to the one you quoted above has the entire contents of 
both logs.  After posting them, I saw where the logs diverged so 
radically and made another post with just the excerpts.


Marc

Re: OT: reply styles, family matters

[Nicolas George]

Le decadi 10 frimaire, an CCXXIV, Bob Bernstein a écrit :
> With that as background, here is my question/request: is anyone aware of a
> spirited defence of our ideal method of "selective quoting," (for lack of a
> better label) one, say, that perhaps has achieved the status of a "net
> classic?" Surely some 'net genius has dealt these nay-sayers, who seem to
> LIKE top-posting, a solid uppercut?

I do not have a pointer to that kind of text, but I have found this analogy
rather relevant:

When you watch a TV series episode, does it end with an announce "Previously
in $series" and the full rerun of the last episode?

Regards,

-- 
  Nicolas George