screen freezes when I try to log

[BELAHCENE Abdelkader]

Hi,
Sometimes the login thru the lightdm fails. That means I log but the screen
freezes and nothing happens, no login no desktop ( using the xfce4).
When I go to the terminal ( using   CTRL+ALT+F1 ), and I log using shell,
I can start the : startx -- :1,  and access to the graphical Desktop..
Where is the problem?  in lightdm or xfce4 ??
I install lxde  and want to log with lxde,  unfortunatly, there is no menu
in the lighdm login,  to choose the manager.
I am using linuxLite 3.8
regards

Re: Some tasks very slow after upgrade from Jessie to Stretch

[Curt]

On 2018-03-01, deloptes  wrote:
> David Christensen wrote:
>
>> So, now I do the latter.  This is facilitated by, and integrated into,
>> my backup/ restore, archive, and imaging processes.  I have confidence
>> in the results.
>
> I have been updating regularly wheezy -> jessie -> stretch
>
> I never experienced any problem
>
>

Me neither and what he posits as another data point in support of his
opinion, isn't.

-- 
“When fascism comes to America, it will be wrapped in the flag and
carrying the cross.” – Sinclair Lewis, 1935, "It Can't Happen Here"

Re: printer with static ip address inaccessible from lan

[Bernd Gruber]

Can't you just plug the printer locally to a PC, change manually the PC's 
network-address to 192.168.1.x, connect to the printer and change its IP to 
192.168.2.x. Then, of course, you will loose the connection, but the printer 
will be in the desired network. Don't forget to change IP-configuration of 
your PC, and connect to the router.
Bernd


Thomas George wrote:

> The Samsung CLP-320 printer's static ip 192.168.1.139 was set about 10
> years ago to work on a lan using 192.168.1.x addresses. Last week the
> lan's router failed and was replaced with a Netgear r6700 router using
> 192.168.2.x addresses. The printer is now inaccessible from the lan.
> 
> Cups Administration says the printer address can be set using its MAC
> address:
> 
> 
>   Configuring the IP Address Using DHCP
> 
> The DHCP protocol is the usual way of setting the IP address of a
> printer on a managed network. Using the standard dhcpd(8) program
> supplied with UNIX you simply need to add a line to the /etc/dhcpd.conf
> file:
> 
> host/hostname/  {
>hardware ethernet/mac-address/;
>fixed-address/ip-address/;
> }
> 
> Make sure that the hostname you use is also listed in the /etc/hosts
> file or is registered with your DNS server.
> 
> apt-cache search dhcpd finds udhcpd. My pc's system is Debian Stretch.
> There is a file /etc/dhcp/dhclient.conf but no file /etc/dhcpd.
> 
> Is it possible to access the printer and change  its address to one in
> 192.168.2.x or to reset it to use dhcp?

Re: Some tasks very slow after upgrade from Jessie to Stretch

[Sven Hartge]

Curt  wrote:
> On 2018-03-01, deloptes  wrote:
>> David Christensen wrote:

>>> So, now I do the latter.  This is facilitated by, and integrated
>>> into, my backup/ restore, archive, and imaging processes.  I have
>>> confidence in the results.
>>
>> I have been updating regularly wheezy -> jessie -> stretch
>>
>> I never experienced any problem

> Me neither and what he posits as another data point in support of his
> opinion, isn't.

Debian in-place upgrades just work. My personal systems have been
upgraded and never reinstalled, even through several hardware up- and
sidegrades, since 1999. I also am very brave and run Unstable with daily
upgrades, so the in-place-upgrade routine is excercised very very often
on those systems.

And the systems I am responsible for at work are also mostly upgraded
and not reinstalled.

Of course the smoothness of the upgrade depends on the amount of
packages installed, the configuration of the packages and the system as
a whole.

In my experience things like upgrading Apache with many VHosts can be
quite painful and labor intensive if you don't use a templating system.
The change from Apache2.2 in Wheezy to Apache2.4 in Jessie is such a
case. 

Also if you bastardized the installation before and went against the way
the distribution does something, your experience during the upgrade will
be worse. But this is true for every Linux distribution, not Debian
alone.

So no, an in-place-upgrade is definately *not* an excercise in futility.
Only if you did something very wrong before this will be your
impression.

Grüße,
Sven

-- 
Sigmentation fault. Core dumped.

Re: Some tasks very slow after upgrade from Jessie to Stretch

[rhkramer]

On Wednesday, February 28, 2018 11:41:34 PM David Christensen wrote:

> There are two schools of thought for Debian major version upgrades:
> 
> 1.  Do an in-place upgrade.
> 
> 2.  Do a fresh install and migrate.
> 
> 
> Years ago, I tried the former.  Invariably, I ran into problems I could
> not trouble-shoot and ended up with systems that I had no confidence in.
>   Yours is just another in an unending stream of posts demonstrating
> that my experience was not unique, and still persists.  I can only
> conclude that an in-place upgrade of something as complex as a real,
> working, and productive Debian system is an exercise in futility.
> 
> 
> So, now I do the latter.  This is facilitated by, and integrated into,
> my backup/ restore, archive, and imaging processes.  I have confidence
> in the results.

+1

I'm not sure it's really an exercise in futility, but it is somewhat "scary".  
Several times I've read the upgrade notes (not sure of the right name) about 
the gotchas that you have to deal with before, during, and after the upgrade 
and decided that the hassle was just not worth it.

What I typically do is install the new OS to a new (at least new to me) 
computer and run it in parallel for some period of time until (1) I have 
confidence that everything works and until I've moved all my "real user files" 
(photos, videos, documents, ) from the old to the new.

I then start to gather the parts for my next new computer by watching places 
like Newegg, TigerDirect, ebay, and sometimes yard sales, Craigslist, and 
similar for sales and bargains.

I used to be able to get the parts for a not completely state of the art 
computer for about $200, buying the case, power supply, RAM, and hard drive 
separately (but I often buy the CPU and motherboard as a combination).

I have noticed that I don't find sales quite as good, especially on RAM, 
motherboards and CPUs, so I expect my next computer might be closer to $300 or 
slightly more.

Another possibility is to buy a "refurbished" system (I'm not sure what 
"refurbishment" gets done maybe just a good (I hope) cleaning.

Now I have cases that I happy with in terms of side (mid to small size  
towers) so I no longer look for new cases--just empty the case and put new 
parts in.

debian package for mu/mu4e 1.0

[juh]

Hi all,

is there a debian package for mu/mu4e 1.0 anywhere?

TIA
juh

Re: Using apcupsd for power failure controle

[Marc Auslander]

(Was Were is gapcmon?)
>> 
>> I've always use apcupsd which still works in stretch.  My use is pretty
>> trivial - just reports - I don't do anything automatic on power fail
>> since I can't figure out how to do anything that will always wind up
>> with my machine running when the power comes back!
>
>I think you can usually set the power-on behaviour in the BIOS (or EFI,
>presumably) - independently of the OS or any shutdown process.
>
>Richard

So here's the issue - maybe I'm missing something.

If I configure apcupsd to shutdown on power fail and the power really
stays off till the apc unit shut down, my machine will reboot on power
up.  But what if the power comes back once the daemon has started the
shutdown?

What is needed is a guaranteed power cycle from the apc unit - which
AFAIK is not an option.

So I just use the apc to cover short outages and prevent power bouncing
which I know from experience can cause damage.  When the battery goes
flat I get a hard powerfail shutdown which modern linux tollerates quite
well - yeah for journaled file systems.

Marc Auslander

Re: debian package for mu/mu4e 1.0

[Roberto C . Sánchez]

On Thu, Mar 01, 2018 at 02:59:17PM +0100, juh wrote:
> Hi all,
> 
> is there a debian package for mu/mu4e 1.0 anywhere?
> 
https://packages.debian.org/search?keywords=mu4e

-- 
Roberto C. Sánchez

Debian custom installer

[basti]

Hello,

I have to try to create a custom installer for debian cd to install over
ssh with a preseed.cfg his is working well.

Now i want to be able to start the installer immediately.

my label in txt.cfg look like

label netinstall
config ssh.cfg
menu default
default netinstall
menu label ^Install Over SSH
kernel /install.amd/vmlinuz
append auto=true vga=788 file=/cdrom/isolinux/preseed.cfg
initrd=/install.amd/initrd.gz --- quiet

my ssh.cfg looks like

cat ssh.cfg
prompt 0
timeout 3

But the timeout is not working I only see the following in attach.

Re: Some tasks very slow after upgrade from Jessie to Stretch

[John]

Slightly different issue but I am part way through an upgrade from
Whezzy to Stretch.  After the upgrade to Jessie my (headless) computer
failed to boot.  After a struggle getting keyboard and screen it
stalled after loading the kernel, probably a broken initrd file

It booted OK with  the last Whezzy kernel but I am afraid to try to
upgrade to Stretch with this suspect system.  Problem is this machine
is the interface between the LAN and the Internet so without it things
are difficult
==John ffitch

Problems with KDE in Debian Stretch

[Daniel Bareiro]

Hi all!

Some time ago I started to experience some problems in KDE. In a random
way, when I'm using any application like Firefox, Chromium or
Thunderbird, the window starts blinking incessantly and becomes
unusable. When that happens I have no choice but to close the
application and reopen it.

This also usually happens with minimized applications. The name starts
blinking in the lower bar and only stops when I click on that minimized
application. It is a somewhat annoying behavior.

This did not happen to me with Debian Jessie always using the same
hardware: a Thinkpad T530.

I would like to know if anyone had this problem and was able to solve it
in some way.

Thanks in advance.


Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature

Re: Some tasks very slow after upgrade from Jessie to Stretch

[deloptes]

John wrote:

> It booted OK with  the last Whezzy kernel but I am afraid to try to
> upgrade to Stretch with this suspect system.  Problem is this machine
> is the interface between the LAN and the Internet so without it things
> are difficult

I use serial to usb and manage reboots this way. I have server and firewall
without keyboard/display)
You can still keep the old kernel/initrd as a fall back.
>From jessie to stretch there were fewer issues (actually non for me). Check
the initrd setup (/etc/initramfs-tools/).

regards

Re: Problems with KDE in Debian Stretch

[Curt]

On 2018-03-01, Daniel Bareiro  wrote:
>
> Hi all!
>
> Some time ago I started to experience some problems in KDE. In a random
> way, when I'm using any application like Firefox, Chromium or
> Thunderbird, the window starts blinking incessantly and becomes
> unusable. When that happens I have no choice but to close the
> application and reopen it.
>
> This also usually happens with minimized applications. The name starts
> blinking in the lower bar and only stops when I click on that minimized
> application. It is a somewhat annoying behavior.
>
> This did not happen to me with Debian Jessie always using the same
> hardware: a Thinkpad T530.
>
> I would like to know if anyone had this problem and was able to solve it
> in some way.

After looking briefly on the Network, searching for "KDE window
flickering," you don't appear to be alone, from which fact a
certain comfort can be derived (and help ideas too from others in the
same blinking boat).

Your problem seems "graphical" in nature.

Maybe some aid and comfort here (if your driver's "intel"):

https://bbs.archlinux.org/viewtopic.php?pid=1595276#p1595276

> Thanks in advance.
>
>
> Kind regards,
> Daniel

-- 
“Be yourself; everyone else is already taken.”
-Oscar Wilde

bug filing question: Gnome session crashes on resume from suspend or hibernate; Nvidia driver suspected

[Peter Becich]

Hello,

I am trying to determine which package to file this bug under.

My login session is frequently lost when the computer resumes from 
suspension or hibernation.  The computer takes me to the Gnome login 
screen.  About one in two resumptions fail this way.


Debian 9.3

kernel 4.15.0-1-amd64 from the "testing" repo

also, kernel 4.14.0-0.bpo.3-amd64 from "testing"

Nvidia driver from the "testing", 384.111

Nvidia card GeForce 1060

I found only two suspicious things in `nvidia-bug-report.log.gz`, which 
was freshly generated after the bug:


[32940.892161] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by 
HW (0x0)

[32940.892198] cache: parent cpu15 should not be sleeping
[32940.892287] microcode: CPU15: patch_level=0x08001129
[32940.892650] CPU15 is up
[32940.894082] ACPI: Waking up from system sleep state S3
...
[32941.030214] nvidia :23:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000e address=0x flags=0x]

https://pastebin.com/hQhyp8kC 

and

[ 32952.583] (II) NVIDIA: Using 24576.00 MB of virtual memory for 
indirect memory

[ 32952.583] (II) NVIDIA: access.
[ 32952.586] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event 
daemon; the daemon

[ 32952.586] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 32952.586] (II) NVIDIA(0): configuration option may not be set 
correctly. When the
[ 32952.586] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA 
X driver will
[ 32952.586] (II) NVIDIA(0): try to use it to receive ACPI event 
notifications. For

[ 32952.586] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 32952.586] (II) NVIDIA(0): "AcpidSocketPath" X configuration options 
in Appendix B: X

[ 32952.586] (II) NVIDIA(0): Config Options in the README.
[ 32952.599] (II) NVIDIA(0): Setting mode 
"DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"

[ 32952.702] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 32952.702] (==) NVIDIA(0): Backing store enabled
[ 32952.702] (==) NVIDIA(0): Silken mouse enabled
[ 32952.703] (==) NVIDIA(0): DPMS enabled

I originally reported this bug on an Ubuntu thread that looked to be the 
same issue: https://bugs.launchpad.net/gnome-shell/+bug/1721428/comments/74


Should this go to "nvidia-driver", "gdm3", "xorg", or some other package?

"nvidia-driver" bugs: 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=nvidia-driver;dist=unstable


"xorg" bugs: 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=xorg;dist=unstable


"gdm3" bugs: 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=gdm3;dist=unstable



Thanks for your time,

  Peter

Re: Boot Order Change

[Dan Norton]

On Thu, 22 Feb 2018 16:41:42 -0500
Felix Miata  wrote:

> Dan Norton composed on 2018-02-22 16:05 (UTC-0500):
> 
> > Installs of both stretch and buster modify the boot order such that
> > "debian" is first under "UEFI Boot Sources". After installation, the
> > bios menu has to be edited in order to boot from DVD or CD or USB
> > drive. Also "Hard Drive" has been replaced with "debian".  
> 
> > The PC is:
> > Hewlett-Packard HP Pro 3400 Series MT/2ABF, BIOS 7.16 03/23/2012  
> 
> > Apparently it is deliberate, so what is the reason for this?  
> 
> AFAICT, it depends on the particular BIOS design and settings
> therein, how it's designed to react to what it finds in the EFI
> partition, particularly if there is more than one entry there. Brand
> name PCs tend to offer fewer BIOS options.

In case someone finds this thread in the archives; finally the reason
got through to me over on debian-boot[1]. Unlike the primary/logical
scheme with an mbr, where an installer can just write a new mbr, in the
UEFI scheme the grub code is *added* to the EFI system partition with
nothing pointing to it until the UEFI menu is changed.

[1]
https://lists.debian.org/debian-boot/2018/02/msg00460.html

Re: Using MATE's workspaces effectively

[songbird]

Liam O'Toole wrote:
> On 2018-02-28, Dominic Knight  wrote:
...
>> Maybe upscaling would help a lot here, it does when I output on hdmi,
>> with Mate that's
>> System - Preferences - look and feel - appearance 
>> then
>> fonts - detail - resolution 
>> I set mine to around 144 and leave system fonts the same and then the
>> vast majority of programs will respect that and be of a readable size
>> at high monitor resolution.
>>  
>> I guess with other desktops you could set it easily enough in an
>> .Xresources file that runs on entering X-server
>>
>> You will of course find occasional programs that completely ignore
>> this.
>>
>> Cheers,
>> Dom.
>>
>>
>
> Those misbehaving programs are probably getting their DPI information
> from the X server directly. If you start X with the '-dpi 144' switch
> then you should get consistent behaviour.
>
> For example:
>
>   startx -- -dpi 144

  i'd need to hook this up with lightdm and MATE and
i have not looked into this at all as to where it might
go, but i'll try the upscaling first and see how the
miscreants react before getting out the shotgun 
approach.

  thanks to both of you.  :)


  songbird

Re: Using MATE's workspaces effectively

[songbird]

Richard Owlett wrote:
...
> I repeat my question, which has been snipped in this thread.
>> What did you do immediately after installation to set this up?
>> What should I be reading?
>> [If it makes a difference, I use Stretch including systemd.] 

  i generally put my aliases in .bashrc for the
user in question.


  songbird

Re: Using MATE's workspaces effectively

[songbird]

Richard Owlett wrote:
...
> However, it would solve a problem that I had assumed had to be endured.
> I frequently have a workflow needing root access for which I don't find 
> "su" convenient causing me to logout as 'richard' and login as 'root' 
> and back again.

  um, i open a terminal window in one of my workspaces
and su to root and leave it there.  when i need root
access to do something i click on that workspace and
there it is ready to go.

  to get back to regular user me again i just click
on other workspace i was on before or whatever else
i want to do.

  what is hard about that?

  when i'm done working for the day i make sure all
my programs have things saved that need to be saved
and then use the root terminal to shutdown from
the command line.  next time i boot up i do have to
sign in as root again, but that isn't a major problem
to me.

...


  songbird

Re: printer with static ip address inaccessible from lan

[Thomas George]

I think this should work. For the present I have moved on to other 
tasks. The printer has a usb connection to the pc so I can print as 
needed. Others on the lan cannot use the printer.



On 03/01/2018 05:08 AM, Bernd Gruber wrote:

Can't you just plug the printer locally to a PC, change manually the PC's
network-address to 192.168.1.x, connect to the printer and change its IP to
192.168.2.x. Then, of course, you will loose the connection, but the printer
will be in the desired network. Don't forget to change IP-configuration of
your PC, and connect to the router.
Bernd


Thomas George wrote:


The Samsung CLP-320 printer's static ip 192.168.1.139 was set about 10
years ago to work on a lan using 192.168.1.x addresses. Last week the
lan's router failed and was replaced with a Netgear r6700 router using
192.168.2.x addresses. The printer is now inaccessible from the lan.

Cups Administration says the printer address can be set using its MAC
address:


   Configuring the IP Address Using DHCP

The DHCP protocol is the usual way of setting the IP address of a
printer on a managed network. Using the standard dhcpd(8) program
supplied with UNIX you simply need to add a line to the /etc/dhcpd.conf
file:

host/hostname/  {
hardware ethernet/mac-address/;
fixed-address/ip-address/;
}

Make sure that the hostname you use is also listed in the /etc/hosts
file or is registered with your DNS server.

apt-cache search dhcpd finds udhcpd. My pc's system is Debian Stretch.
There is a file /etc/dhcp/dhclient.conf but no file /etc/dhcpd.

Is it possible to access the printer and change  its address to one in
192.168.2.x or to reset it to use dhcp?

Re: Some tasks very slow after upgrade from Jessie to Stretch

[Richard Hector]

On 02/03/18 04:23, John wrote:
> Slightly different issue but I am part way through an upgrade from
> Whezzy to Stretch.  After the upgrade to Jessie my (headless) computer
> failed to boot.  After a struggle getting keyboard and screen it
> stalled after loading the kernel, probably a broken initrd file
> 
> It booted OK with  the last Whezzy kernel but I am afraid to try to
> upgrade to Stretch with this suspect system.  Problem is this machine
> is the interface between the LAN and the Internet so without it things
> are difficult
> ==John ffitch
> 

So you've got a jessie system that won't boot with the jessie kernel,
but will boot with the wheezy kernel?

While you've got the keyboard and screen handy, you could try the
jessie-backports kernel, which is more similar to the stretch kernel,
and if that works you should be ok to upgrade.

Richard




signature.asc
Description: OpenPGP digital signature

Re: Using apcupsd for power failure controle

[Richard Hector]

On 02/03/18 03:09, Marc Auslander wrote:
>> I think you can usually set the power-on behaviour in the BIOS (or EFI,
>> presumably) - independently of the OS or any shutdown process.
>>
>> Richard
> So here's the issue - maybe I'm missing something.
> 
> If I configure apcupsd to shutdown on power fail and the power really
> stays off till the apc unit shut down, my machine will reboot on power
> up.  But what if the power comes back once the daemon has started the
> shutdown?
> 
> What is needed is a guaranteed power cycle from the apc unit - which
> AFAIK is not an option.

Interesting point.

I confess I've never set up a ups for all this before, but I've read
about it ... I'm pretty sure you can instruct the ups to shut down, but
I don't know whether you can tell it to come back as soon as the power
is stable (possibly immediately).

I guess you could go more extreme, and have the ups controlled by
something else, like a battery-powered Raspberry Pi ... does the ups
listen for instructions in its 'down' state?

Richard



signature.asc
Description: OpenPGP digital signature

DIY FOSS firewall/ router

[David Christensen]

On 03/01/18 07:23, John wrote:
> Slightly different issue but I am part way through an upgrade from
> Whezzy to Stretch.  After the upgrade to Jessie my (headless) computer
> failed to boot.  After a struggle getting keyboard and screen it
> stalled after loading the kernel, probably a broken initrd file
>
> It booted OK with  the last Whezzy kernel but I am afraid to try to
> upgrade to Stretch with this suspect system.  Problem is this machine
> is the interface between the LAN and the Internet so without it things
> are difficult
> ==John ffitch

I built and ran a do-it-yourself Debian firewall/ router back in the 
day, learned iptables (or whatever), etc..  It worked, but I knew I was 
no expert and worried about security.



Then I discovered purpose-built FOSS firewall/ router distributions:

1.  I found IPCop to be the easiest to install, configure, and 
administer.  Unfortunately, the web site is down at the moment.


2.  I found pfsense to be the most sophisticated:

https://www.pfsense.org/


David

Re: LVM partitions not mounting after upgrade

[David Christensen]

On 02/28/18 07:28, Andy Pont wrote:

Hello,

Today I have upgraded the third of our three Debian servers from Jessie (8.10) 
to Stretch (9.3) and whilst the first two went without a problem the final one 
only boots to the maintenance mode prompt.

This particular server uses an Intel motherboard and has a 4 disk raid array 
(mirrored and striped) created using the BIOS in which exists (excuse the 
terminology if it isn’t quite correct) a LVM physical volume and three 
partitions (/opt, /home and /var).

When booting it sits for 90 seconds flashing messages of the form:

Start job running for dev-mapper-sdcserver/x2dvar.device
Start job running for dev-mapper-sdcserver/x2dopt.device
Start job running for dev-mapper-sdcserver/x2dhome.device

After the 90 seconds these turn into "Timed out waiting for..." messages and I 
get presented with Control-D maintenance mode prompt.

Looking in /dev there is the /dev/md126 device for the raid array but there are 
no /dev/dm-X entries and no /dev/vg_sdcserver as I see on a similar machine 
that has a similar setup.

When I try to investigate with commands such as pvcreate or vgchange, in test 
mode, then they all show messages about duplicates.

Could someone guide me how to recreate the necessary files in /dev so I can 
mount these volumes and boot the server?

Thanks,

-Andy.


https://lists.debian.org/debian-user/2018/03/msg5.html


What is "sdcserver"?  Secondary Domain Controller?


What is the model of the Intel motherboard?


Is the RAID controller on the motherboard or a card?  If card, what is 
the make and model?



What are the makes and models of the disks?


If you created the RAID10 using the BIOS, did Jesse see one physical 
disk or did you need to install additional software?



Is root on the RAID10 or on other disk(s)?


David

Re: printer with static ip address inaccessible from lan

[john doe]

On 3/2/2018 2:03 AM, Thomas George wrote:
I think this should work. For the present I have moved on to other 
tasks. The printer has a usb connection to the pc so I can print as 
needed. Others on the lan cannot use the printer.




you can share the printer using cups.
The other on the LAN would use the IP of your cups server.

--
John Doe