Re: Fluxbox doesn't survive to a suspend to disk when restarted

2016-08-14 Thread Mike Larkin 
On Sun, Aug 14, 2016 at 06:16:11PM +0200, Alessandro DE LAURENZIS wrote:
> Mike,
> 
> On Fri, 12 Aug 2016 19:47:40 +0200
> Alessandro DE LAURENZIS  wrote:
> 
> > Hi Mike,
> > 
> > On 2016-08-12 18:54, Mike Larkin wrote:
> > > Shrug. Works fine here on i386 and amd64.
> > > 
> > > Do other processes crash as well? What if you leave fluxbox
> > > running? Does
> > > it eventually fail on its own without needing fluxbox-remote to
> > > trigger it?  
> > 
> > As far as I can say, no other crash, neither fluxbox nor other
> > processes (I'm currently running this session since several hours 
> > without any
> > issues).
> > 
> > Only the restart seems to trigger the misbehaviour.
> 
> Playing with gdb:
> 
> [snip]
> GNU gdb 6.3
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "amd64-unknown-openbsd6.0"...(no debugging symbols 
> found)
> 
> (gdb) run
> Starting program: /usr/local/bin/fluxbox 
> (no debugging symbols found)
> 
> Program received signal SIGTRAP, Trace/breakpoint trap.
> Cannot remove breakpoints because program is no longer writable.
> It might be running in another process.
> Further execution is probably impossible.
> 0x173fb63002b0 in ?? ()
> (gdb) quit
> The program is running.  Exit anyway? (y or n) 
> [snip]
> 
> Does it suggest anything useful?
> 

No.

> -- 
> Alessandro DE LAURENZIS
> [mailto:jus...@atlantide.t28.net]
> LinkedIn: http://it.linkedin.com/in/delaurenzis

Re: Fluxbox doesn't survive to a suspend to disk when restarted

2016-08-14 Thread Alessandro DE LAURENZIS 
Mike,

On Fri, 12 Aug 2016 19:47:40 +0200
Alessandro DE LAURENZIS  wrote:

> Hi Mike,
> 
> On 2016-08-12 18:54, Mike Larkin wrote:
> > Shrug. Works fine here on i386 and amd64.
> > 
> > Do other processes crash as well? What if you leave fluxbox
> > running? Does
> > it eventually fail on its own without needing fluxbox-remote to
> > trigger it?  
> 
> As far as I can say, no other crash, neither fluxbox nor other
> processes (I'm currently running this session since several hours 
> without any
> issues).
> 
> Only the restart seems to trigger the misbehaviour.

Playing with gdb:

[snip]
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-unknown-openbsd6.0"...(no debugging symbols 
found)

(gdb) run
Starting program: /usr/local/bin/fluxbox 
(no debugging symbols found)

Program received signal SIGTRAP, Trace/breakpoint trap.
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
0x173fb63002b0 in ?? ()
(gdb) quit
The program is running.  Exit anyway? (y or n) 
[snip]

Does it suggest anything useful?

-- 
Alessandro DE LAURENZIS
[mailto:jus...@atlantide.t28.net]
LinkedIn: http://it.linkedin.com/in/delaurenzis

Re: Fluxbox doesn't survive to a suspend to disk when restarted

2016-08-12 Thread Alessandro DE LAURENZIS 

Hi Mike,

On 2016-08-12 18:54, Mike Larkin wrote:

Shrug. Works fine here on i386 and amd64.

Do other processes crash as well? What if you leave fluxbox running? 
Does

it eventually fail on its own without needing fluxbox-remote to trigger
it?


As far as I can say, no other crash, neither fluxbox nor other
processes (I'm currently running this session since several hours 
without any

issues).

Only the restart seems to trigger the misbehaviour.

--
Alessandro DE LAURENZIS
[mailto:jus...@atlantide.t28.net]
LinkedIn: http://it.linkedin.com/in/delaurenzis

Re: Fluxbox doesn't survive to a suspend to disk when restarted

2016-08-12 Thread Mike Larkin 
On Fri, Aug 12, 2016 at 11:23:45AM +0200, Alessandro De Laurenzis wrote:
> Hi Mike,
> 
> (sorry, I'm having issues with my e-mail service...)
> 
> >I installed fluxbox and tried to repro this. It works fine here.
> >
> >Does this fail just after many ZZZs? because it looks from your dmesg that
> >you did a bunch of them. Does it fail after the first one?
> >
> >-ml
> 
> the crash is triggered after the first ZZZ, too.
> 
> -- 
> Alessandro De Laurenzis
> [mailto:sandro.delauren...@gmail.com]

Shrug. Works fine here on i386 and amd64.

Do other processes crash as well? What if you leave fluxbox running? Does
it eventually fail on its own without needing fluxbox-remote to trigger
it?

-ml

Re: Fluxbox doesn't survive to a suspend to disk when restarted

2016-08-12 Thread Alessandro De Laurenzis 
Hi Mike,

(sorry, I'm having issues with my e-mail service...)

>I installed fluxbox and tried to repro this. It works fine here.
>
>Does this fail just after many ZZZs? because it looks from your dmesg that
>you did a bunch of them. Does it fail after the first one?
>
>-ml

the crash is triggered after the first ZZZ, too.

-- 
Alessandro De Laurenzis
[mailto:sandro.delauren...@gmail.com]

Re: Fluxbox doesn't survive to a suspend to disk when restarted

2016-08-11 Thread Mike Larkin 
On Thu, Aug 11, 2016 at 09:39:33PM +0200, Alessandro DE LAURENZIS wrote:
> dmesg and pkg_info -t as requested:
> 

I installed fluxbox and tried to repro this. It works fine here.

Does this fail just after many ZZZs? because it looks from your dmesg that
you did a bunch of them. Does it fail after the first one?

-ml

> 
> OpenBSD 6.0-current (GENERIC.MP) #2345: Tue Aug  9 23:00:50 MDT 2016
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 3177906176 (3030MB)
> avail mem = 3077181440 (2934MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (73 entries)
> bios0: vendor LENOVO version "7LETD0WW (2.30 )" date 02/27/2012
> bios0: LENOVO 7735WX2
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET BOOT ASF! SSDT SSDT
> SSDT SSDT
> acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) IGBE(S4) EXP0(S4)
> EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3)
> USB3(S3) USB4(S3) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpiec0 at acpi0
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz, 2294.66 MHz
> cpu0: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR
> cpu0: 3MB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 199MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz, 2094.75 MHz
> cpu1: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR
> cpu1: 3MB 64b/line 8-way L2 cache
> cpu1: smt 0, core 1, package 0
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
> acpimcfg0 at acpi0 addr 0xf000, bus 0-63
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus -1 (AGP_)
> acpiprt2 at acpi0: bus 2 (EXP0)
> acpiprt3 at acpi0: bus 3 (EXP1)
> acpiprt4 at acpi0: bus 4 (EXP2)
> acpiprt5 at acpi0: bus 5 (EXP3)
> acpiprt6 at acpi0: bus 13 (EXP4)
> acpiprt7 at acpi0: bus 21 (PCI1)
> acpicpu0 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10),
> C1(1000@1 mwait.1), PSS
> acpicpu1 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10),
> C1(1000@1 mwait.1), PSS
> acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB4, EHC0, EHC1
> acpitz0 at acpi0: critical temperature is 127 degC
> acpitz1 at acpi0: critical temperature is 100 degC
> acpibtn0 at acpi0: LID_
> acpibtn1 at acpi0: SLPB
> "PNP0303" at acpi0 not configured
> "IBM0057" at acpi0 not configured
> tpm0 at acpi0: TPM_ addr 0xfed4/0x5000: device 0x32031114 rev 0x9
> acpibat0 at acpi0: BAT0 model "42T5264" serial  1732 type LION oem
> "Panasonic"
> acpiac0 at acpi0: AC unit online
> acpithinkpad0 at acpi0
> "PNP0C14" at acpi0 not configured
> acpidock0 at acpi0: GDCK not docked (0)
> acpivideo0 at acpi0: VID_
> acpivout0 at acpivideo0: LCD0
> acpivideo1 at acpi0: VID_
> cpu0: Enhanced SpeedStep 2294 MHz: speeds: 2101, 2100, 1600, 1200, 800 MHz
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "Intel GM965 Host" rev 0x0c
> inteldrm0 at pci0 dev 2 function 0 "Intel GM965 Video" rev 0x0c
> drm0 at inteldrm0
> intagp0 at inteldrm0
> agp0 at intagp0: aperture at 0xe000, size 0x1000
> inteldrm0: msi
> inteldrm0: 1280x800
> wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
> wsdisplay0: screen 1-5 added (std, vt100 emulation)
> "Intel GM965 Video" rev 0x0c at pci0 dev 2 function 1 not configured
> em0 at pci0 dev 25 function 0 "Intel ICH8 IGP M AMT" rev 0x03: msi, address
> 00:21:86:94:34:8e
> uhci0 at pci0 dev 26 function 0 "Intel 82801H USB" rev 0x03: apic 1 int 20
> uhci1 at pci0 dev 26 function 1 "Intel 82801H USB" rev 0x03: apic 1 int 21
> ehci0 at pci0 dev 26 function 7 "Intel 82801H USB" rev 0x03: apic 1 int 22
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> azalia0 at pci0 dev 27 function 0 "Intel 82801H HD Audio" rev 0x03: msi
> azalia0: codecs: Analog Devices AD1984, Conexant/0x2bfa, using Analog
> Devices AD1984
> audio0 at azalia0
> ppb0 at pci0 dev 28 function 0 "Intel 82801H PCIE" rev 0x03: msi
> pci1 at ppb0 bus 2
> ppb1 at pci0 dev 28 function 1 "Intel 82801H PCIE" rev 0x03: msi
> pci2 at ppb1 bus 3
> iwn0 at pci2 dev 0 function 0 "Intel Wireless WiFi Link 4965" rev 0x61: msi,
> MIMO 2T3R, MoW2, address 00:21:5c:75:a7:1d
> ppb2 at pci0 dev 28 function 2 "Intel 82801H PCIE" rev 0x03: msi
> pci3

Re: Fluxbox doesn't survive to a suspend to disk when restarted

2016-08-11 Thread Alessandro DE LAURENZIS 

dmesg and pkg_info -t as requested:


OpenBSD 6.0-current (GENERIC.MP) #2345: Tue Aug  9 23:00:50 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3177906176 (3030MB)
avail mem = 3077181440 (2934MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (73 entries)
bios0: vendor LENOVO version "7LETD0WW (2.30 )" date 02/27/2012
bios0: LENOVO 7735WX2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET BOOT ASF! SSDT 
SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) IGBE(S4) 
EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB1(S3) 
USB2(S3) USB3(S3) USB4(S3) [...]

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz, 2294.66 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR

cpu0: 3MB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz, 2094.75 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR

cpu1: 3MB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (AGP_)
acpiprt2 at acpi0: bus 2 (EXP0)
acpiprt3 at acpi0: bus 3 (EXP1)
acpiprt4 at acpi0: bus 4 (EXP2)
acpiprt5 at acpi0: bus 5 (EXP3)
acpiprt6 at acpi0: bus 13 (EXP4)
acpiprt7 at acpi0: bus 21 (PCI1)
acpicpu0 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10), 
C1(1000@1 mwait.1), PSS

acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB4, EHC0, EHC1
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at acpi0: critical temperature is 100 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"PNP0303" at acpi0 not configured
"IBM0057" at acpi0 not configured
tpm0 at acpi0: TPM_ addr 0xfed4/0x5000: device 0x32031114 rev 0x9
acpibat0 at acpi0: BAT0 model "42T5264" serial  1732 type LION oem 
"Panasonic"

acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
"PNP0C14" at acpi0 not configured
acpidock0 at acpi0: GDCK not docked (0)
acpivideo0 at acpi0: VID_
acpivout0 at acpivideo0: LCD0
acpivideo1 at acpi0: VID_
cpu0: Enhanced SpeedStep 2294 MHz: speeds: 2101, 2100, 1600, 1200, 800 
MHz

pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel GM965 Host" rev 0x0c
inteldrm0 at pci0 dev 2 function 0 "Intel GM965 Video" rev 0x0c
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xe000, size 0x1000
inteldrm0: msi
inteldrm0: 1280x800
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel GM965 Video" rev 0x0c at pci0 dev 2 function 1 not configured
em0 at pci0 dev 25 function 0 "Intel ICH8 IGP M AMT" rev 0x03: msi, 
address 00:21:86:94:34:8e
uhci0 at pci0 dev 26 function 0 "Intel 82801H USB" rev 0x03: apic 1 int 
20
uhci1 at pci0 dev 26 function 1 "Intel 82801H USB" rev 0x03: apic 1 int 
21
ehci0 at pci0 dev 26 function 7 "Intel 82801H USB" rev 0x03: apic 1 int 
22

usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 82801H HD Audio" rev 0x03: msi
azalia0: codecs: Analog Devices AD1984, Conexant/0x2bfa, using Analog 
Devices AD1984

audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801H PCIE" rev 0x03: msi
pci1 at ppb0 bus 2
ppb1 at pci0 dev 28 function 1 "Intel 82801H PCIE" rev 0x03: msi
pci2 at ppb1 bus 3
iwn0 at pci2 dev 0 function 0 "Intel Wireless WiFi Link 4965" rev 0x61: 
msi, MIMO 2T3R, MoW2, address 00:21:5c:75:a7:1d

ppb2 at pci0 dev 28 function 2 "Intel 82801H PCIE" rev 0x03: msi
pci3 at ppb2 bus 4
ppb3 at pci0 dev 28 function 3 "Intel 82801H PCIE" rev 0x03: msi
pci4 at ppb3 bus 5
ppb4 at pci0 dev 28 function 4 "Intel 82801H PCIE" rev 0x03: msi
pci5 at ppb4 bus 13
uhci2 at pci0 dev 29 function 0 "Intel 82801H USB" rev 0x03: apic 1 int 
16
uhci3 at pci0 dev 29 function 1 "Intel 82801H USB" rev 0x03: apic 1 int 
17
uhci4 at pci0 dev 29 function 2 "Intel 82801H USB" rev 0x03: apic 1 int 
18
ehci1 at pci0 dev 29 function 7 "Intel 82801H

Re: Fluxbox doesn't survive to a suspend to disk when restarted

2016-08-11 Thread Mike Larkin 
On Thu, Aug 11, 2016 at 03:10:25PM +0200, Alessandro DE LAURENZIS wrote:
> Hello,
> 
> I'm reporting this without any details because actually I do not know how to
> start a debugging...
> 
> After resuming from an hibernation, restarting Fluxbox (Restart from menu or
> issuing "fluxbox-remote -Restart") systematically crashes it, causing the
> XDM login window to appear. No core generated, nothing annotated into system
> logs / Fluxbox's log.
> 
> This is on -current, Aug 10 (same behaviour with other recent, don't know
> the situation for previous ones).
> 
> Anybody noticed the same?
> 
> All the best
> 
> -- 
> Alessandro DE LAURENZIS
> [mailto:jus...@atlantide.t28.net]
> LinkedIn: http://it.linkedin.com/in/delaurenzis
> 

dmesg and pkg_info -t please.

Re: Fluxbox doesn't survive to a suspend to disk when restarted

2016-08-11 Thread Alessandro DE LAURENZIS 

On 2016-08-11 15:23, Alessandro DE LAURENZIS wrote:

Hello David,

Does restarting Fluxbox work otherwise or the crash only happens after 
resuming?


restarting it before suspend to disk works flawlessly.

Cheers


It's worth mentioning that suspending to RAM does *not* trigger the 
crash.


--
Alessandro DE LAURENZIS
[mailto:jus...@atlantide.t28.net]
LinkedIn: http://it.linkedin.com/in/delaurenzis

Re: Fluxbox doesn't survive to a suspend to disk when restarted

2016-08-11 Thread Alessandro DE LAURENZIS 

Hello David,

Does restarting Fluxbox work otherwise or the crash only happens after 
resuming?


restarting it before suspend to disk works flawlessly.

Cheers

--
Alessandro DE LAURENZIS
[mailto:jus...@atlantide.t28.net]
LinkedIn: http://it.linkedin.com/in/delaurenzis

Re: Fluxbox doesn't survive to a suspend to disk when restarted

2016-08-11 Thread David Coppa 
On Thu, Aug 11, 2016 at 3:10 PM, Alessandro DE LAURENZIS
 wrote:
> Hello,
>
> I'm reporting this without any details because actually I do not know how to
> start a debugging...
>
> After resuming from an hibernation, restarting Fluxbox (Restart from menu or
> issuing "fluxbox-remote -Restart") systematically crashes it, causing the
> XDM login window to appear. No core generated, nothing annotated into system
> logs / Fluxbox's log.
>
> This is on -current, Aug 10 (same behaviour with other recent, don't know
> the situation for previous ones).
>
> Anybody noticed the same?

Does restarting Fluxbox work otherwise or the crash only happens after resuming?


Ciao
David
-- 
"If you try a few times and give up, you'll never get there. But if
you keep at it... There's a lot of problems in the world which can
really be solved by applying two or three times the persistence that
other people will."
-- Stewart Nelson

Fluxbox doesn't survive to a suspend to disk when restarted

2016-08-11 Thread Alessandro DE LAURENZIS 

Hello,

I'm reporting this without any details because actually I do not know 
how to start a debugging...


After resuming from an hibernation, restarting Fluxbox (Restart from 
menu or issuing "fluxbox-remote -Restart") systematically crashes it, 
causing the XDM login window to appear. No core generated, nothing 
annotated into system logs / Fluxbox's log.


This is on -current, Aug 10 (same behaviour with other recent, don't 
know the situation for previous ones).


Anybody noticed the same?

All the best

--
Alessandro DE LAURENZIS
[mailto:jus...@atlantide.t28.net]
LinkedIn: http://it.linkedin.com/in/delaurenzis