[blfs-support] Fsarchiver password problem(solved)

2020-06-12 Thread Cliff McDiarmid via blfs-support
Right.  Solved the problem.  The permissions were altered(somehow) on sudo.  
Should be: -rwsr-xr-x 1 root root.
 
Sorry about the mail wrong format.
 
Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Fsarchiver password problem

2020-06-12 Thread Cliff McDiarmid via blfs-support
Hi

I don't know whether anyone has experience of running this software on LFS.

On my latest LFS I can not get Fsarchiver to accept the root password and hence I can not see my existing partitions in the software. If I run it from a terminal to get readout I get:

sh: /home//root/.local/share/.en.nfo: No such file or directory
ccrypt: could not read key from /home//root/.local/share/.en.nfo: No such file or directory
chown: invalid user: ‘/root’
chmod: cannot access '/home//root/.config/qt-fsarchiver': No such file or directory
QIODevice::write (QFile, "/home//root/.config/qt-fsarchiver/version.txt"): device not open

This software runs fine on an earlier LFS.  I'm missing something here, but what is it, I'm not aware that ccryp is involved in this software?

 

thanks

Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] Older GCC install

2020-05-19 Thread Cliff McDiarmid via blfs-support
>>Sent: Sunday, May 17, 2020 at 1:09 AM
>From: "Don Cross via blfs-support" 
>To: "BLFS Support List" 
>Cc: "Don Cross" 
>Subject: Re: [blfs-support] Older GCC install

>On Sat, May 16, 2020 at 5:30 PM Cliff McDiarmid via blfs-support 
>mailto:blfs-support@lists.linuxfromscratch.org]>
> wrote:
> Okay thanks Don. I'm trying to compile Gnucash 3.10 which has not been a 
> problem in the past. The dependencies at present stress the use of GCC 8.0

>This occurs with GCC 8.4 as you can see, but also with 9.2

>Wow, not just C errors, but C++ errors!  As a guy who has been working with 
>C++ daily since 1989, I feel your pain. I agree with others here. If you can 
>do some linker-fu to get an existing binary running on your system, that's 
>>probably a lot easier.
 
>But if the binary thing doesn't work out, and you want to try building the 
>source, read on...
 
>Those errors with std::replace and std::find suggest that the affected cpp 
>files (e.g. gnucash/import-export/csv-imp/assistant-csv-price-import.cpp) need 
>the following added :
 
>#include 
 
>I would try putting that right above the #include  in that file, but 
>after the "*/" that ends the comment block. You will no doubt have to go 
>through several rounds of building and fixing things like this.
 
Wonderful Don!  Had to alter four or five .cpp files and rebuild to get Gnucash 
to compile with the addition suggested.  I now have a working program.  Many 
thanks.

regards

Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] Older GCC install

2020-05-17 Thread Cliff McDiarmid via blfs-support
Sent: Saturday, May 16, 2020 at 10:42 PM
From: "Bruce Dubbs via blfs-support" 
To: blfs-support@lists.linuxfromscratch.org
Cc: "Bruce Dubbs" 
Subject: Re: [blfs-support] Older GCC install
On 5/16/20 4:30 PM, Cliff McDiarmid via blfs-support wrote:
>
> Sent: Saturday, May 16, 2020 at 3:13 PM
> From: "Bruce Dubbs via blfs-support" 
> To: blfs-support@lists.linuxfromscratch.org
> Cc: "Bruce Dubbs" 
> Subject: Re: [blfs-support] Older GCC install
> On 5/16/20 6:39 AM, Cliff McDiarmid via blfs-support wrote:
>>> Sent: Saturday, May 16, 2020 at 12:11 AM
>>> From: "Don Cross via blfs-support" 
>>> To: "BLFS Support List" 
>>> Cc: "Don Cross" 
>>> Subject: Re: [blfs-support] Older GCC install
>>
>>> On Fri, May 15, 2020 at 6:00 PM Cliff McDiarmid via blfs-support 
>>> mailto:blfs-support@lists.linuxfromscratch.org]>
>>>  wrote:
>>
>>> I need to install an older GCC to compile a particular piece of software.   
>>> At present I'm using GCC 9.2(recent LFS).
>>> I've managed to compile 8.4 and it works, but I need 8.1.
>>
>>> As a long-time C programmer, I'm curious why you need an older C compiler.
>>
>> Okay thanks Don. I'm trying to compile Gnucash 3.10 which has not been a 
>> problem in the past. The dependencies at present stress the use of GCC 8.0
>>
>>> If I knew what problem gcc 8.4 is causing, maybe I could help get it 
>>> working, so you don't need to compile 8.1. I'm willing to give it a shot if 
>>> I had more details.
>>
>> I've compiled Gnucash 3.10 with GCC 8.1 abeit on another LFS(older).
>
>> Copy the binary from the old system to the new one? Would be a lot
>> easier than trying to rebuild it.
>
> First thing I tried Bruce.  Doesn't work. It's not finding libraries.

>Use ldd on the executable to find out what libraries it wants.
>Generally libraries would be something like:

>libx.so.3 -> libx.so.333
>libx.so.312

>A different version of the library would then be
>libx.so.2 -> libx.so.222
>libx.so.222

>These can be installed side by side.
>The libx.so file is only used by the linker when building and generally
>would point to the most recent version.

Thanks Bruce but it's a no go.  Managed to supply all libraries needed 
including about eight links. In the end though I had symbols missing - it got 
messy.

Going with Don's advice now and trying to alter code.

cliff



-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] Older GCC install

2020-05-16 Thread Cliff McDiarmid via blfs-support
>Sent: Saturday, May 16, 2020 at 12:57 PM
>From: "Thomas Trepl" 
>To: "BLFS Support List" 
>Cc: "Cliff McDiarmid" 
>Subject: Re: [blfs-support] Older GCC install
>Am Samstag, den 16.05.2020, 13:39 +0200 schrieb Cliff McDiarmid via
>blfs-support:
> > Sent: Saturday, May 16, 2020 at 12:11 AM
> > From: "Don Cross via blfs-support" 
> > To: "BLFS Support List" 
> > Cc: "Don Cross" 
> > Subject: Re: [blfs-support] Older GCC install
> > On Fri, May 15, 2020 at 6:00 PM Cliff McDiarmid via blfs-support 
> > mailto:blfs-support@lists.linuxfromscratch.org]>
> >  wrote:
> > I need to install an older GCC to compile a particular piece of software. 
> > At present I'm using GCC 9.2(recent LFS).
> > I've managed to compile 8.4 and it works, but I need 8.1.
>
> > As a long-time C programmer, I'm curious why you need an older C compiler.
>
> Okay thanks Don. I'm trying to compile Gnucash 3.10 which has not been a 
> problem in the past. The dependencies at present stress the use of GCC 8.0
>
> > If I knew what problem gcc 8.4 is causing, maybe I could help get it 
> > working, so you don't need to compile 8.1. I'm willing to give it a shot if 
> > I had more details.
>
> I've compiled Gnucash 3.10 with GCC 8.1 abeit on another LFS(older).
>
> On my newer LFS it fails with GCC 9.2 AND 8.4 which as I mentioned I got 
> working on the same system. I hope you're still with me.
>
> Anyway.. the errors that the compilers are producing, with Gnucash, look like 
> compiler errors. Not missing libraries or fuctions etc. They are substantial 
> and I could mail them if you can help.

>What are those errors?

Thanks Thomas

/home/cliffhanger/Downloads/gnucash-3.10/gnucash/import-export/csv-imp/assistant-csv-price-import.cpp:
 In function ‘void 
csv_price_imp_preview_settings_text_inserted_cb(GtkEditable*, gchar*, gint, 
gint*, CsvImpPriceAssist*)’:
/home/cliffhanger/Downloads/gnucash-3.10/gnucash/import-export/csv-imp/assistant-csv-price-import.cpp:270:10:
 error: ‘replace’ is not a member of ‘std’
 std::replace (mod_txt.begin(), mod_txt.end(), '[', '(');
  ^~~
/home/cliffhanger/Downloads/gnucash-3.10/gnucash/import-export/csv-imp/assistant-csv-price-import.cpp:271:10:
 error: ‘replace’ is not a member of ‘std’
 std::replace (mod_txt.begin(), mod_txt.end(), ']', ')');
  ^~~
/home/cliffhanger/Downloads/gnucash-3.10/gnucash/import-export/csv-imp/assistant-csv-price-import.cpp:
 In member function ‘void 
CsvImpPriceAssist::preview_reparse_col_type(GncPricePropType)’:
/home/cliffhanger/Downloads/gnucash-3.10/gnucash/import-export/csv-imp/assistant-csv-price-import.cpp:1196:41:
 error: no matching function for call to 
‘find(std::vector::iterator, 
std::vector::iterator, GncPricePropType&)’
 column_types.end(), type);
 ^
In file included from /opt/gcc/include/c++/8.4.0/bits/locale_facets.h:48,
 from /opt/gcc/include/c++/8.4.0/bits/basic_ios.h:37,
 from /opt/gcc/include/c++/8.4.0/ios:44,
 from /opt/gcc/include/c++/8.4.0/ostream:38,
 from /opt/gcc/include/c++/8.4.0/iostream:39,
 from 
/home/cliffhanger/Downloads/gnucash-3.10/libgnucash/engine/gnc-numeric.hpp:27,
 from 
/home/cliffhanger/Downloads/gnucash-3.10/gnucash/import-export/csv-imp/gnc-imp-props-price.hpp:43,
 from 
/home/cliffhanger/Downloads/gnucash-3.10/gnucash/import-export/csv-imp/gnc-imp-settings-csv-price.hpp:39,
 from 
/home/cliffhanger/Downloads/gnucash-3.10/gnucash/import-export/csv-imp/assistant-csv-price-import.cpp:55:
/opt/gcc/include/c++/8.4.0/bits/streambuf_iterator.h:368:5: note: candidate: 
‘template typename 
__gnu_cxx::__enable_if::__value, 
std::istreambuf_iterator<_CharT> >::__type 
std::find(std::istreambuf_iterator<_CharT>, std::istreambuf_iterator<_CharT>, 
const _CharT2&)’
 find(istreambuf_iterator<_CharT> __first,
 ^~~~
/opt/gcc/include/c++/8.4.0/bits/streambuf_iterator.h:368:5: note:   template 
argument deduction/substitution failed:
/home/cliffhanger/Downloads/gnucash-3.10/gnucash/import-export/csv-imp/assistant-csv-price-import.cpp:1196:41:
 note:   ‘__gnu_cxx::__normal_iterator >’ is not derived from 
‘std::istreambuf_iterator<_CharT>’
 column_types.end(), type);
 ^
/home/cliffhanger/Downloads/gnucash-3.10/gnucash/import-export/csv-imp/assistant-csv-price-import.cpp:
 In member function ‘void CsvImpPriceAssist::preview_refresh_table()’:
/home/cliffhanger/Downloads/gnucash-3.10/gnucash/import-export/csv-imp/assistant-csv-price-import

Re: [blfs-support] Older GCC install

2020-05-16 Thread Cliff McDiarmid via blfs-support

Sent: Saturday, May 16, 2020 at 3:13 PM
From: "Bruce Dubbs via blfs-support" 
To: blfs-support@lists.linuxfromscratch.org
Cc: "Bruce Dubbs" 
Subject: Re: [blfs-support] Older GCC install
On 5/16/20 6:39 AM, Cliff McDiarmid via blfs-support wrote:
>> Sent: Saturday, May 16, 2020 at 12:11 AM
>> From: "Don Cross via blfs-support" 
>> To: "BLFS Support List" 
>> Cc: "Don Cross" 
>> Subject: Re: [blfs-support] Older GCC install
>
>> On Fri, May 15, 2020 at 6:00 PM Cliff McDiarmid via blfs-support 
>> mailto:blfs-support@lists.linuxfromscratch.org]>
>>  wrote:
>
>> I need to install an older GCC to compile a particular piece of software.   
>> At present I'm using GCC 9.2(recent LFS).
>> I've managed to compile 8.4 and it works, but I need 8.1.
>
>> As a long-time C programmer, I'm curious why you need an older C compiler.
>
> Okay thanks Don. I'm trying to compile Gnucash 3.10 which has not been a 
> problem in the past. The dependencies at present stress the use of GCC 8.0
>
>> If I knew what problem gcc 8.4 is causing, maybe I could help get it 
>> working, so you don't need to compile 8.1. I'm willing to give it a shot if 
>> I had more details.
>
> I've compiled Gnucash 3.10 with GCC 8.1 abeit on another LFS(older).

>Copy the binary from the old system to the new one? Would be a lot
>easier than trying to rebuild it.

First thing I tried Bruce.  Doesn't work.  It's not finding libraries.

Cliff


 
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] Older GCC install

2020-05-16 Thread Cliff McDiarmid via blfs-support
>Sent: Saturday, May 16, 2020 at 12:11 AM
>From: "Don Cross via blfs-support" 
>To: "BLFS Support List" 
>Cc: "Don Cross" 
>Subject: Re: [blfs-support] Older GCC install

>On Fri, May 15, 2020 at 6:00 PM Cliff McDiarmid via blfs-support 
>mailto:blfs-support@lists.linuxfromscratch.org]>
> wrote:

>I need to install an older GCC to compile a particular piece of software.   At 
>present I'm using GCC 9.2(recent LFS).
>I've managed to compile 8.4 and it works, but I need 8.1.
 
>As a long-time C programmer, I'm curious why you need an older C compiler. 

Okay thanks Don.  I'm trying to compile Gnucash 3.10 which has not been a 
problem in the past.  The dependencies at present stress the use of GCC 8.0

>If I knew what problem gcc 8.4 is causing, maybe I could help get it working, 
>so you don't need to compile 8.1. I'm willing to give it a shot if I had more 
>details.

I've compiled Gnucash 3.10 with GCC 8.1 abeit on another LFS(older).  

On my newer LFS it fails with GCC 9.2 AND 8.4 which as I mentioned I got 
working on the same system.   I hope you're still with me.

Anyway.. the errors that the compilers are producing, with Gnucash, look like 
compiler errors.  Not missing libraries or fuctions etc.  They are substantial 
and I could mail them if you can help.

thanks again

Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Older GCC install

2020-05-15 Thread Cliff McDiarmid via blfs-support
Hi

 

I need to install an older GCC to compile a particular piece of software.   At present I'm using GCC 9.2(recent LFS).

 

I've managed to compile 8.4 and it works, but I need 8.1.

 

I'm getting the following error with 8.1, any help or pointers would be appreciated.

 




libtool: link: (cd ".libs" && rm -f "libitm.so.1" && ln -s "libitm.so.1.0.0" "libitm.so.1")
libtool: link: (cd ".libs" && rm -f "libitm.so" && ln -s "libitm.so.1.0.0" "libitm.so")
libtool: link: ar rc .libs/libitm.a  aatree.o alloc.o alloc_c.o alloc_cpp.o barrier.o beginend.o clone.o eh_cpp.o local.o query.o retry.o rwlock.o useraction.o util.o sjlj.o tls.o method-serial.o method-gl.o method-ml.o x86_sse.o x86_avx.o futex.o
libtool: link: ranlib .libs/libitm.a
libtool: link: ( cd ".libs" && rm -f "libitm.la" && ln -s "../libitm.la" "libitm.la" )
make[4]: Leaving directory '/home/cliffhanger/Downloads/gcc-8.2.0/build/x86_64-pc-linux-gnu/libitm'
make[3]: Leaving directory '/home/cliffhanger/Downloads/gcc-8.2.0/build/x86_64-pc-linux-gnu/libitm'
make[2]: Leaving directory '/home/cliffhanger/Downloads/gcc-8.2.0/build/x86_64-pc-linux-gnu/libitm'
make[1]: Leaving directory '/home/cliffhanger/Downloads/gcc-8.2.0/build'
make: *** [Makefile:907: all] Error 2

 

This is the earliest hint of the error

 



 

Thanks

 

Cliff

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Gnome not starting(SOLVED)

2020-03-22 Thread Cliff McDiarmid via blfs-support
>Sent: Wednesday, March 18, 2020 at 4:36 PM
>From: "Cliff McDiarmid via blfs-support" 
>
>To: "BLFS Support List" 
>Cc: "Cliff McDiarmid" 
>Subject: [blfs-support] Gnome not starting
>Sent: Tuesday, March 17, 2020 at 1:15 PM
>From: "Cliff McDiarmid via blfs-support" 
>
>To: blfs-support@lists.linuxfromscratch.org
>Cc: "Cliff McDiarmid" 
>Subject: Re: [blfs-support] Gnome not starting

>Sent: Monday, March 16, 2020 at 5:29 PM

>From: "Christopher Gregory via blfs-support" 
>
>To: blfs-support@lists.linuxfromscratch.org
>Cc: "Christopher Gregory" 
>Subject: Re: [blfs-support] Gnome not starting

> Sent: Tuesday, March 17, 2020 at 6:03 AM
> From: "Cliff McDiarmid via blfs-support" 
> 
> To: blfs-support@lists.linuxfromscratch.org
> Cc: "Cliff McDiarmid" 
> Subject: Re: [blfs-support] Gnome not starting
>
> Sent: Monday, March 16, 2020 at 12:06 AM
>
> From: "Christopher Gregory via blfs-support" 
> 
> To: blfs-support@lists.linuxfromscratch.org
> Cc: "Christopher Gregory" 
> Subject: Re: [blfs-support] Gnome not starting
>
> > Sent: Monday, March 16, 2020 at 12:49 PM
> > From: "Cliff McDiarmid via blfs-support" 
> > 
> > To: "BLFS Support List" 
> > Cc: "Cliff McDiarmid" 
> > Subject: [blfs-support] Gnome not starting
> >
> > Hi
> >
> > So something is wrong elsewhere? Please confirm systemd is okay.
> >
> > >Looks like there's something wrong in your systemd install (or on the way 
> > >gnome-session accesses
> > >it, maybe). Does the following return something?
> >
> > >gdbus introspect --system --dest org.freedesktop.systemd1 \
> > >--object-path /org/freedesktop/systemd1
> >
> > This is the output. Apologies for the length.
> >
> > >If it does, there is something wrong elsewhere. But I suspect using a
> > >non-systemd procedure on a systemd host doesn't work
> >
> > node /org/freedesktop/systemd1 {
> > interface org.freedesktop.DBus.Peer {
> > methods:
> > Ping();
> > GetMachineId(out s machine_uuid);
> > signals:
> > properties:
> > };
> > interface org.freedesktop.DBus.Introspectable {
> > methods:
> > Introspect(out s data);
> > signals:
> > properties:
> > };
> > interface org.freedesktop.DBus.Properties {
> > methods:
> > Get(in s interface,
> > in s property,
> > out v value);
> > GetAll(in s interface,
> > out a{sv} properties);
> > Set(in s interface,
> > in s property,
> > in v value);
> > signals:
> > PropertiesChanged(s interface,
> > a{sv} changed_properties,
> > as invalidated_properties);
> > properties:
> > };
> > interface org.freedesktop.systemd1.Manager {
> > methods:
> > GetUnit(in s arg_0,
> > out o arg_1);
> > GetUnitByPID(in u arg_0,
> > out o arg_1);
> > GetUnitByInvocationID(in ay arg_0,
> > out o arg_1);
> > GetUnitByControlGroup(in s arg_0,
> > out o arg_1);
> > LoadUnit(in s arg_0,
> > out o arg_1);
> > StartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > StartUnitReplace(in s arg_0,
> > in s arg_1,
> > in s arg_2,
> > out o arg_3);
> > StopUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > ReloadUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > RestartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > TryRestartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > ReloadOrRestartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > ReloadOrTryRestartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > EnqueueUnitJob(in s arg_0,
> > in s arg_1,
> > in s arg_2,
> > out u arg_3,
> > out o arg_4,
> > out s arg_5,
> > out o arg_6,
> > out s arg_7,
> > out a(uosos) arg_8);
> > KillUnit(in s arg_0,
> > in s arg_1,
> > in i arg_2);
> > CleanUnit(in s arg_0,
> > in as arg_1);
> > ResetFailedUnit(in s arg_0);
> > SetUnitProperties(in s arg_0,
> > in b arg_1,
> > in a(sv) arg_2);
> > RefUnit(in s arg_0);
> > UnrefUnit(in s arg_0);
> > StartTransientUnit(in s arg_0,
> > in s arg_1,
> > in a(sv) arg_2,
> > in a(sa(sv)) arg_3,
> > out o arg_4);
> > GetUnitProcesses(in s arg_0,
> > out a(sus) arg_1);
> > AttachProcessesToUnit(in s arg_0,
> > in s arg_1,
> > in au arg_2);
> > AbandonScope

[blfs-support] Gnome not starting

2020-03-18 Thread Cliff McDiarmid via blfs-support
Sent: Tuesday, March 17, 2020 at 1:15 PM
From: "Cliff McDiarmid via blfs-support" 

To: blfs-support@lists.linuxfromscratch.org
Cc: "Cliff McDiarmid" 
Subject: Re: [blfs-support] Gnome not starting

Sent: Monday, March 16, 2020 at 5:29 PM

From: "Christopher Gregory via blfs-support" 

To: blfs-support@lists.linuxfromscratch.org
Cc: "Christopher Gregory" 
Subject: Re: [blfs-support] Gnome not starting

> Sent: Tuesday, March 17, 2020 at 6:03 AM
> From: "Cliff McDiarmid via blfs-support" 
> 
> To: blfs-support@lists.linuxfromscratch.org
> Cc: "Cliff McDiarmid" 
> Subject: Re: [blfs-support] Gnome not starting
>
> Sent: Monday, March 16, 2020 at 12:06 AM
>
> From: "Christopher Gregory via blfs-support" 
> 
> To: blfs-support@lists.linuxfromscratch.org
> Cc: "Christopher Gregory" 
> Subject: Re: [blfs-support] Gnome not starting
>
> > Sent: Monday, March 16, 2020 at 12:49 PM
> > From: "Cliff McDiarmid via blfs-support" 
> > 
> > To: "BLFS Support List" 
> > Cc: "Cliff McDiarmid" 
> > Subject: [blfs-support] Gnome not starting
> >
> > Hi
> >
> > So something is wrong elsewhere? Please confirm systemd is okay.
> >
> > >Looks like there's something wrong in your systemd install (or on the way 
> > >gnome-session accesses
> > >it, maybe). Does the following return something?
> >
> > >gdbus introspect --system --dest org.freedesktop.systemd1 \
> > >--object-path /org/freedesktop/systemd1
> >
> > This is the output. Apologies for the length.
> >
> > >If it does, there is something wrong elsewhere. But I suspect using a
> > >non-systemd procedure on a systemd host doesn't work
> >
> > node /org/freedesktop/systemd1 {
> > interface org.freedesktop.DBus.Peer {
> > methods:
> > Ping();
> > GetMachineId(out s machine_uuid);
> > signals:
> > properties:
> > };
> > interface org.freedesktop.DBus.Introspectable {
> > methods:
> > Introspect(out s data);
> > signals:
> > properties:
> > };
> > interface org.freedesktop.DBus.Properties {
> > methods:
> > Get(in s interface,
> > in s property,
> > out v value);
> > GetAll(in s interface,
> > out a{sv} properties);
> > Set(in s interface,
> > in s property,
> > in v value);
> > signals:
> > PropertiesChanged(s interface,
> > a{sv} changed_properties,
> > as invalidated_properties);
> > properties:
> > };
> > interface org.freedesktop.systemd1.Manager {
> > methods:
> > GetUnit(in s arg_0,
> > out o arg_1);
> > GetUnitByPID(in u arg_0,
> > out o arg_1);
> > GetUnitByInvocationID(in ay arg_0,
> > out o arg_1);
> > GetUnitByControlGroup(in s arg_0,
> > out o arg_1);
> > LoadUnit(in s arg_0,
> > out o arg_1);
> > StartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > StartUnitReplace(in s arg_0,
> > in s arg_1,
> > in s arg_2,
> > out o arg_3);
> > StopUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > ReloadUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > RestartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > TryRestartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > ReloadOrRestartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > ReloadOrTryRestartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > EnqueueUnitJob(in s arg_0,
> > in s arg_1,
> > in s arg_2,
> > out u arg_3,
> > out o arg_4,
> > out s arg_5,
> > out o arg_6,
> > out s arg_7,
> > out a(uosos) arg_8);
> > KillUnit(in s arg_0,
> > in s arg_1,
> > in i arg_2);
> > CleanUnit(in s arg_0,
> > in as arg_1);
> > ResetFailedUnit(in s arg_0);
> > SetUnitProperties(in s arg_0,
> > in b arg_1,
> > in a(sv) arg_2);
> > RefUnit(in s arg_0);
> > UnrefUnit(in s arg_0);
> > StartTransientUnit(in s arg_0,
> > in s arg_1,
> > in a(sv) arg_2,
> > in a(sa(sv)) arg_3,
> > out o arg_4);
> > GetUnitProcesses(in s arg_0,
> > out a(sus) arg_1);
> > AttachProcessesToUnit(in s arg_0,
> > in s arg_1,
> > in au arg_2);
> > AbandonScope(in s arg_0);
> > GetJob(in u arg_0,
> > out o arg_1);
> > GetJobAfter(in u arg_0,
> > out a(usssoo) arg_1);
> > GetJobBefore(in u arg_0,
> > out a(usssoo) arg_1);
> > CancelJob(in u arg_0);
> > ClearJobs();
> > ResetFailed();
>

[blfs-support] Gnome not starting

2020-03-18 Thread Cliff McDiarmid via blfs-support
Sent: Tuesday, March 17, 2020 at 1:17 PM

From: "Cliff McDiarmid via blfs-support" 

To: blfs-support@lists.linuxfromscratch.org
Cc: "Cliff McDiarmid" 
Subject: Re: [blfs-support] Gnome not starting

  Sent: Monday, March 16, 2020 at 8:47 PM

From: "Pierre Labastie via blfs-support" 

To: blfs-support@lists.linuxfromscratch.org
Cc: "Pierre Labastie" 
Subject: Re: [blfs-support] Gnome not starting
Le 16/03/2020 à 18:29, Christopher Gregory via blfs-support a écrit :
>
>
>> Sent: Tuesday, March 17, 2020 at 6:03 AM
>> From: "Cliff McDiarmid via blfs-support" 
>> 
>> To: blfs-support@lists.linuxfromscratch.org
>> Cc: "Cliff McDiarmid" 
>> Subject: Re: [blfs-support] Gnome not starting
>>
>> Sent: Monday, March 16, 2020 at 12:06 AM
>>
>> From: "Christopher Gregory via blfs-support" 
>> 
>> To: blfs-support@lists.linuxfromscratch.org
>> Cc: "Christopher Gregory" 
>> Subject: Re: [blfs-support] Gnome not starting
>>
>>> Sent: Monday, March 16, 2020 at 12:49 PM
>>> From: "Cliff McDiarmid via blfs-support" 
>>> 
>>> To: "BLFS Support List" 
>>> Cc: "Cliff McDiarmid" 
>>> Subject: [blfs-support] Gnome not starting
>>>
>>> Hi
>>>
>>> So something is wrong elsewhere? Please confirm systemd is okay.
>>>
>>>> Looks like there's something wrong in your systemd install (or on the way 
>>>> gnome-session accesses
>>>> it, maybe). Does the following return something?
>>>
>>>> gdbus introspect --system --dest org.freedesktop.systemd1 \
>>>> --object-path /org/freedesktop/systemd1
>>>
>>> This is the output. Apologies for the length.
>>>
>>>> If it does, there is something wrong elsewhere. But I suspect using a
>>>> non-systemd procedure on a systemd host doesn't work
>>>
>>> node /org/freedesktop/systemd1 {
>>> interface org.freedesktop.DBus.Peer {
>>> methods:
>>> Ping();
>>> GetMachineId(out s machine_uuid);
>>> signals:
>>> properties:
>>> };
>>> interface org.freedesktop.DBus.Introspectable {
>>> methods:
>>> Introspect(out s data);
>>> signals:
>>> properties:
>>> };
>>> interface org.freedesktop.DBus.Properties {
>>> methods:
>>> Get(in s interface,
>>> in s property,
>>> out v value);
>>> GetAll(in s interface,
>>> out a{sv} properties);
>>> Set(in s interface,
>>> in s property,
>>> in v value);
>>> signals:
>>> PropertiesChanged(s interface,
>>> a{sv} changed_properties,
>>> as invalidated_properties);
>>> properties:
>>> };
>>> interface org.freedesktop.systemd1.Manager {
>>> methods:
>>> GetUnit(in s arg_0,
>>> out o arg_1);
>>> GetUnitByPID(in u arg_0,
>>> out o arg_1);
>>> GetUnitByInvocationID(in ay arg_0,
>>> out o arg_1);
>>> GetUnitByControlGroup(in s arg_0,
>>> out o arg_1);
>>> LoadUnit(in s arg_0,
>>> out o arg_1);
>>> StartUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> StartUnitReplace(in s arg_0,
>>> in s arg_1,
>>> in s arg_2,
>>> out o arg_3);
>>> StopUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> ReloadUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> RestartUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> TryRestartUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> ReloadOrRestartUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> ReloadOrTryRestartUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> EnqueueUnitJob(in s arg_0,
>>> in s arg_1,
>>> in s arg_2,
>>> out u arg_3,
>>> out o arg_4,
>>> out s arg_5,
>>> out o arg_6,
>>> out s arg_7,
>>> out a(uosos) arg_8);
>>> KillUnit(in s arg_0,
>>> in s arg_1,
>>> in i arg_2);
>>> CleanUnit(in s arg_0,
>>> in as arg_1);
>>> ResetFailedUnit(in s arg_0);
>>> SetUnitProperties(in s arg_0,
>>> in b arg_1,
>>> in a(sv) arg_2);
>>> RefUnit(in s arg_0);
>>> UnrefUnit(in s arg_0);
>>> StartTransientUnit(in s arg_0,
>>> in s arg_1,
>>> in a(sv) arg_2,
>>> in a(sa(sv)) arg_3,
>>

Re: [blfs-support] Gnome not starting

2020-03-17 Thread Cliff McDiarmid via blfs-support
  Sent: Monday, March 16, 2020 at 8:47 PM


From: "Pierre Labastie via blfs-support" 
To: blfs-support@lists.linuxfromscratch.org
Cc: "Pierre Labastie" 
Subject: Re: [blfs-support] Gnome not starting

Le 16/03/2020 à 18:29, Christopher Gregory via blfs-support a écrit :
>
>
>> Sent: Tuesday, March 17, 2020 at 6:03 AM
>> From: "Cliff McDiarmid via blfs-support" 
>> To: blfs-support@lists.linuxfromscratch.org
>> Cc: "Cliff McDiarmid" 
>> Subject: Re: [blfs-support] Gnome not starting
>>
>> Sent: Monday, March 16, 2020 at 12:06 AM
>>
>> From: "Christopher Gregory via blfs-support" 
>> To: blfs-support@lists.linuxfromscratch.org
>> Cc: "Christopher Gregory" 
>> Subject: Re: [blfs-support] Gnome not starting
>>
>>> Sent: Monday, March 16, 2020 at 12:49 PM
>>> From: "Cliff McDiarmid via blfs-support" 
>>> To: "BLFS Support List" 
>>> Cc: "Cliff McDiarmid" 
>>> Subject: [blfs-support] Gnome not starting
>>>
>>> Hi
>>>
>>> So something is wrong elsewhere? Please confirm systemd is okay.
>>>
>>>> Looks like there's something wrong in your systemd install (or on the way gnome-session accesses
>>>> it, maybe). Does the following return something?
>>>
>>>> gdbus introspect --system --dest org.freedesktop.systemd1 \
>>>> --object-path /org/freedesktop/systemd1
>>>
>>> This is the output. Apologies for the length.
>>>
>>>> If it does, there is something wrong elsewhere. But I suspect using a
>>>> non-systemd procedure on a systemd host doesn't work
>>>
>>> node /org/freedesktop/systemd1 {
>>> interface org.freedesktop.DBus.Peer {
>>> methods:
>>> Ping();
>>> GetMachineId(out s machine_uuid);
>>> signals:
>>> properties:
>>> };
>>> interface org.freedesktop.DBus.Introspectable {
>>> methods:
>>> Introspect(out s data);
>>> signals:
>>> properties:
>>> };
>>> interface org.freedesktop.DBus.Properties {
>>> methods:
>>> Get(in s interface,
>>> in s property,
>>> out v value);
>>> GetAll(in s interface,
>>> out a{sv} properties);
>>> Set(in s interface,
>>> in s property,
>>> in v value);
>>> signals:
>>> PropertiesChanged(s interface,
>>> a{sv} changed_properties,
>>> as invalidated_properties);
>>> properties:
>>> };
>>> interface org.freedesktop.systemd1.Manager {
>>> methods:
>>> GetUnit(in s arg_0,
>>> out o arg_1);
>>> GetUnitByPID(in u arg_0,
>>> out o arg_1);
>>> GetUnitByInvocationID(in ay arg_0,
>>> out o arg_1);
>>> GetUnitByControlGroup(in s arg_0,
>>> out o arg_1);
>>> LoadUnit(in s arg_0,
>>> out o arg_1);
>>> StartUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> StartUnitReplace(in s arg_0,
>>> in s arg_1,
>>> in s arg_2,
>>> out o arg_3);
>>> StopUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> ReloadUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> RestartUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> TryRestartUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> ReloadOrRestartUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> ReloadOrTryRestartUnit(in s arg_0,
>>> in s arg_1,
>>> out o arg_2);
>>> EnqueueUnitJob(in s arg_0,
>>> in s arg_1,
>>> in s arg_2,
>>> out u arg_3,
>>> out o arg_4,
>>> out s arg_5,
>>> out o arg_6,
>>> out s arg_7,
>>> out a(uosos) arg_8);
>>> KillUnit(in s arg_0,
>>> in s arg_1,
>>> in i arg_2);
>>> CleanUnit(in s arg_0,
>>> in as arg_1);
>>> ResetFailedUnit(in s arg_0);
>>> SetUnitProperties(in s arg_0,
>>> in b arg_1,
>>> in a(sv) arg_2);
>>> RefUnit(in s arg_0);
>>> UnrefUnit(in s arg_0);
>>> StartTransientUnit(in s arg_0,
>>> in s arg_1,
>>> in a(sv) arg_2,
>>> in a(sa(sv)) arg_3,
>>> out o arg_4);
>>> GetUnitProcesses(in s arg_0,
>>> out a(sus) arg_1);
>>> AttachProcessesToUnit(in s arg_0,
>>> in s arg_1,
>>> in au arg_2);
>>> AbandonScope(in s arg_0);
>>> GetJob(in u arg_0,
>

Re: [blfs-support] Gnome not starting

2020-03-17 Thread Cliff McDiarmid via blfs-support
  Sent: Monday, March 16, 2020 at 5:29 PM


From: "Christopher Gregory via blfs-support" 
To: blfs-support@lists.linuxfromscratch.org
Cc: "Christopher Gregory" 
Subject: Re: [blfs-support] Gnome not starting



> Sent: Tuesday, March 17, 2020 at 6:03 AM
> From: "Cliff McDiarmid via blfs-support" 
> To: blfs-support@lists.linuxfromscratch.org
> Cc: "Cliff McDiarmid" 
> Subject: Re: [blfs-support] Gnome not starting
>
> Sent: Monday, March 16, 2020 at 12:06 AM
>
> From: "Christopher Gregory via blfs-support" 
> To: blfs-support@lists.linuxfromscratch.org
> Cc: "Christopher Gregory" 
> Subject: Re: [blfs-support] Gnome not starting
>
> > Sent: Monday, March 16, 2020 at 12:49 PM
> > From: "Cliff McDiarmid via blfs-support" 
> > To: "BLFS Support List" 
> > Cc: "Cliff McDiarmid" 
> > Subject: [blfs-support] Gnome not starting
> >
> > Hi
> >
> > So something is wrong elsewhere? Please confirm systemd is okay.
> >
> > >Looks like there's something wrong in your systemd install (or on the way gnome-session accesses
> > >it, maybe). Does the following return something?
> >
> > >gdbus introspect --system --dest org.freedesktop.systemd1 \
> > >--object-path /org/freedesktop/systemd1
> >
> > This is the output. Apologies for the length.
> >
> > >If it does, there is something wrong elsewhere. But I suspect using a
> > >non-systemd procedure on a systemd host doesn't work
> >
> > node /org/freedesktop/systemd1 {
> > interface org.freedesktop.DBus.Peer {
> > methods:
> > Ping();
> > GetMachineId(out s machine_uuid);
> > signals:
> > properties:
> > };
> > interface org.freedesktop.DBus.Introspectable {
> > methods:
> > Introspect(out s data);
> > signals:
> > properties:
> > };
> > interface org.freedesktop.DBus.Properties {
> > methods:
> > Get(in s interface,
> > in s property,
> > out v value);
> > GetAll(in s interface,
> > out a{sv} properties);
> > Set(in s interface,
> > in s property,
> > in v value);
> > signals:
> > PropertiesChanged(s interface,
> > a{sv} changed_properties,
> > as invalidated_properties);
> > properties:
> > };
> > interface org.freedesktop.systemd1.Manager {
> > methods:
> > GetUnit(in s arg_0,
> > out o arg_1);
> > GetUnitByPID(in u arg_0,
> > out o arg_1);
> > GetUnitByInvocationID(in ay arg_0,
> > out o arg_1);
> > GetUnitByControlGroup(in s arg_0,
> > out o arg_1);
> > LoadUnit(in s arg_0,
> > out o arg_1);
> > StartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > StartUnitReplace(in s arg_0,
> > in s arg_1,
> > in s arg_2,
> > out o arg_3);
> > StopUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > ReloadUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > RestartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > TryRestartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > ReloadOrRestartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > ReloadOrTryRestartUnit(in s arg_0,
> > in s arg_1,
> > out o arg_2);
> > EnqueueUnitJob(in s arg_0,
> > in s arg_1,
> > in s arg_2,
> > out u arg_3,
> > out o arg_4,
> > out s arg_5,
> > out o arg_6,
> > out s arg_7,
> > out a(uosos) arg_8);
> > KillUnit(in s arg_0,
> > in s arg_1,
> > in i arg_2);
> > CleanUnit(in s arg_0,
> > in as arg_1);
> > ResetFailedUnit(in s arg_0);
> > SetUnitProperties(in s arg_0,
> > in b arg_1,
> > in a(sv) arg_2);
> > RefUnit(in s arg_0);
> > UnrefUnit(in s arg_0);
> > StartTransientUnit(in s arg_0,
> > in s arg_1,
> > in a(sv) arg_2,
> > in a(sa(sv)) arg_3,
> > out o arg_4);
> > GetUnitProcesses(in s arg_0,
> > out a(sus) arg_1);
> > AttachProcessesToUnit(in s arg_0,
> > in s arg_1,
> > in au arg_2);
> > AbandonScope(in s arg_0);
> > GetJob(in u arg_0,
> > out o arg_1);
> > GetJobAfter(in u arg_0,
> > out a(usssoo) arg_1);
> > GetJobBefore(in u arg_0,
> > out a(usssoo) arg_1);
> > CancelJob(in u arg_0);
> > ClearJobs();
> > ResetFailed();
> > ListUnits(out a(ssouso) arg_0);
> > ListUnitsFiltered(in as arg_0,
> > out a(ssouso) arg_1);
> > ListUnitsByPatterns(in as arg_0,
> > in as arg_1,
> > out a(ssouso) arg_2);
> > ListUnitsByN

Re: [blfs-support] Gnome not starting

2020-03-16 Thread Cliff McDiarmid via blfs-support
Sent: Monday, March 16, 2020 at 12:06 AM

From: "Christopher Gregory via blfs-support" 

To: blfs-support@lists.linuxfromscratch.org
Cc: "Christopher Gregory" 
Subject: Re: [blfs-support] Gnome not starting

> Sent: Monday, March 16, 2020 at 12:49 PM
> From: "Cliff McDiarmid via blfs-support" 
> 
> To: "BLFS Support List" 
> Cc: "Cliff McDiarmid" 
> Subject: [blfs-support] Gnome not starting
>
> Hi
>
> So something is wrong elsewhere? Please confirm systemd is okay.
>
> >Looks like there's something wrong in your systemd install (or on the way 
> >gnome-session accesses
> >it, maybe). Does the following return something?
>
> >gdbus introspect --system --dest org.freedesktop.systemd1 \
> >--object-path /org/freedesktop/systemd1
>
> This is the output. Apologies for the length.
>
> >If it does, there is something wrong elsewhere. But I suspect using a
> >non-systemd procedure on a systemd host doesn't work
>
> node /org/freedesktop/systemd1 {
> interface org.freedesktop.DBus.Peer {
> methods:
> Ping();
> GetMachineId(out s machine_uuid);
> signals:
> properties:
> };
> interface org.freedesktop.DBus.Introspectable {
> methods:
> Introspect(out s data);
> signals:
> properties:
> };
> interface org.freedesktop.DBus.Properties {
> methods:
> Get(in s interface,
> in s property,
> out v value);
> GetAll(in s interface,
> out a{sv} properties);
> Set(in s interface,
> in s property,
> in v value);
> signals:
> PropertiesChanged(s interface,
> a{sv} changed_properties,
> as invalidated_properties);
> properties:
> };
> interface org.freedesktop.systemd1.Manager {
> methods:
> GetUnit(in s arg_0,
> out o arg_1);
> GetUnitByPID(in u arg_0,
> out o arg_1);
> GetUnitByInvocationID(in ay arg_0,
> out o arg_1);
> GetUnitByControlGroup(in s arg_0,
> out o arg_1);
> LoadUnit(in s arg_0,
> out o arg_1);
> StartUnit(in s arg_0,
> in s arg_1,
> out o arg_2);
> StartUnitReplace(in s arg_0,
> in s arg_1,
> in s arg_2,
> out o arg_3);
> StopUnit(in s arg_0,
> in s arg_1,
> out o arg_2);
> ReloadUnit(in s arg_0,
> in s arg_1,
> out o arg_2);
> RestartUnit(in s arg_0,
> in s arg_1,
> out o arg_2);
> TryRestartUnit(in s arg_0,
> in s arg_1,
> out o arg_2);
> ReloadOrRestartUnit(in s arg_0,
> in s arg_1,
> out o arg_2);
> ReloadOrTryRestartUnit(in s arg_0,
> in s arg_1,
> out o arg_2);
> EnqueueUnitJob(in s arg_0,
> in s arg_1,
> in s arg_2,
> out u arg_3,
> out o arg_4,
> out s arg_5,
> out o arg_6,
> out s arg_7,
> out a(uosos) arg_8);
> KillUnit(in s arg_0,
> in s arg_1,
> in i arg_2);
> CleanUnit(in s arg_0,
> in as arg_1);
> ResetFailedUnit(in s arg_0);
> SetUnitProperties(in s arg_0,
> in b arg_1,
> in a(sv) arg_2);
> RefUnit(in s arg_0);
> UnrefUnit(in s arg_0);
> StartTransientUnit(in s arg_0,
> in s arg_1,
> in a(sv) arg_2,
> in a(sa(sv)) arg_3,
> out o arg_4);
> GetUnitProcesses(in s arg_0,
> out a(sus) arg_1);
> AttachProcessesToUnit(in s arg_0,
> in s arg_1,
> in au arg_2);
> AbandonScope(in s arg_0);
> GetJob(in u arg_0,
> out o arg_1);
> GetJobAfter(in u arg_0,
> out a(usssoo) arg_1);
> GetJobBefore(in u arg_0,
> out a(usssoo) arg_1);
> CancelJob(in u arg_0);
> ClearJobs();
> ResetFailed();
> ListUnits(out a(ssouso) arg_0);
> ListUnitsFiltered(in as arg_0,
> out a(ssouso) arg_1);
> ListUnitsByPatterns(in as arg_0,
> in as arg_1,
> out a(ssouso) arg_2);
> ListUnitsByNames(in as arg_0,
> out a(ssouso) arg_1);
> ListJobs(out a(usssoo) arg_0);
> Subscribe();
> Unsubscribe();
> Dump(out s arg_0);
> DumpByFileDescriptor(out h arg_0);
> Reload();
> Reexecute();
> @org.freedesktop.systemd1.Privileged("true")
> Exit();
> @org.freedesktop.systemd1.Privileged("true")
> Reboot();
> @org.freedesktop.systemd1.Privileged("true")
> PowerOff();
> @org.freedesktop.systemd1.Privileged("true")
> Halt();
> @org.freedesktop.systemd1.Privileged("true")
> KExec();
> @org.freedesktop.systemd1.Privileged("true")
> SwitchRoot(in s arg_0,
> in s arg_1);
> SetEnvironment(in as arg_0);
> UnsetEnvironment(in as arg_0);
> UnsetAndSetEnvironment(in as arg_0,
> in as arg_1);
> ListUnitFiles(out a(ss) arg_0);
> ListUnitFilesByPatterns(in as arg_0,
> in as arg_1,
> out a(ss) arg_2);
> GetUnitFileState(in s arg_0,
> out s arg_1);
> EnableUnitFiles(in as arg_0,
> in b arg_1,
> in b arg_2,
> out b arg_3,
> out a(sss) arg_4);
> DisableUnitFiles(in as arg_0,
> in b arg_1,
&

[blfs-support] Gnome not starting

2020-03-15 Thread Cliff McDiarmid via blfs-support
Hi

So something is wrong elsewhere?  Please confirm systemd is okay.

>Looks like there's something wrong in your systemd install (or on the way 
>gnome-session accesses
>it, maybe). Does the following return something?

>gdbus introspect --system --dest org.freedesktop.systemd1 \
>--object-path /org/freedesktop/systemd1

This is the output.  Apologies for the length.

>If it does, there is something wrong elsewhere. But I suspect using a
>non-systemd procedure on a systemd host doesn't work

node /org/freedesktop/systemd1 {
  interface org.freedesktop.DBus.Peer {
methods:
  Ping();
  GetMachineId(out s machine_uuid);
signals:
properties:
  };
  interface org.freedesktop.DBus.Introspectable {
methods:
  Introspect(out s data);
signals:
properties:
  };
  interface org.freedesktop.DBus.Properties {
methods:
  Get(in  s interface,
  in  s property,
  out v value);
  GetAll(in  s interface,
 out a{sv} properties);
  Set(in  s interface,
  in  s property,
  in  v value);
signals:
  PropertiesChanged(s interface,
a{sv} changed_properties,
as invalidated_properties);
properties:
  };
  interface org.freedesktop.systemd1.Manager {
methods:
  GetUnit(in  s arg_0,
  out o arg_1);
  GetUnitByPID(in  u arg_0,
   out o arg_1);
  GetUnitByInvocationID(in  ay arg_0,
out o arg_1);
  GetUnitByControlGroup(in  s arg_0,
out o arg_1);
  LoadUnit(in  s arg_0,
   out o arg_1);
  StartUnit(in  s arg_0,
in  s arg_1,
out o arg_2);
  StartUnitReplace(in  s arg_0,
   in  s arg_1,
   in  s arg_2,
   out o arg_3);
  StopUnit(in  s arg_0,
   in  s arg_1,
   out o arg_2);
  ReloadUnit(in  s arg_0,
 in  s arg_1,
 out o arg_2);
  RestartUnit(in  s arg_0,
  in  s arg_1,
  out o arg_2);
  TryRestartUnit(in  s arg_0,
 in  s arg_1,
 out o arg_2);
  ReloadOrRestartUnit(in  s arg_0,
  in  s arg_1,
  out o arg_2);
  ReloadOrTryRestartUnit(in  s arg_0,
 in  s arg_1,
 out o arg_2);
  EnqueueUnitJob(in  s arg_0,
 in  s arg_1,
 in  s arg_2,
 out u arg_3,
 out o arg_4,
 out s arg_5,
 out o arg_6,
 out s arg_7,
 out a(uosos) arg_8);
  KillUnit(in  s arg_0,
   in  s arg_1,
   in  i arg_2);
  CleanUnit(in  s arg_0,
in  as arg_1);
  ResetFailedUnit(in  s arg_0);
  SetUnitProperties(in  s arg_0,
in  b arg_1,
in  a(sv) arg_2);
  RefUnit(in  s arg_0);
  UnrefUnit(in  s arg_0);
  StartTransientUnit(in  s arg_0,
 in  s arg_1,
 in  a(sv) arg_2,
 in  a(sa(sv)) arg_3,
 out o arg_4);
  GetUnitProcesses(in  s arg_0,
   out a(sus) arg_1);
  AttachProcessesToUnit(in  s arg_0,
in  s arg_1,
in  au arg_2);
  AbandonScope(in  s arg_0);
  GetJob(in  u arg_0,
 out o arg_1);
  GetJobAfter(in  u arg_0,
  out a(usssoo) arg_1);
  GetJobBefore(in  u arg_0,
   out a(usssoo) arg_1);
  CancelJob(in  u arg_0);
  ClearJobs();
  ResetFailed();
  ListUnits(out a(ssouso) arg_0);
  ListUnitsFiltered(in  as arg_0,
out a(ssouso) arg_1);
  ListUnitsByPatterns(in  as arg_0,
  in  as arg_1,
  out a(ssouso) arg_2);
  ListUnitsByNames(in  as arg_0,
   out a(ssouso) arg_1);
  ListJobs(out a(usssoo) arg_0);
  Subscribe();
  Unsubscribe();
  Dump(out s arg_0);
  DumpByFileDescriptor(out h arg_0);
  Reload();
  Reexecute();
  @org.freedesktop.systemd1.Privileged("true")
  Exit();
  @org.freedesktop.systemd1.Privileged("true")
  Reboot();
  @org.freedesktop.systemd1.Privileged("true")
  PowerOff();
  @org.freedesktop.systemd1.Privileged("true")
  Halt();
  @org.freedesktop.systemd1.Privileged("true")
  KExec();
  @org.freedesktop.systemd1.Privileged("true")
  SwitchRoot(in  s arg_0,
 in  s arg_1);
  SetEnvironment(in  as arg_0);
  UnsetEnvironment(in  as arg_0);
  UnsetAndSetEnvironment(in  as arg_0,
 i

Re: [blfs-support] Gnome not starting

2020-03-15 Thread Cliff McDiarmid via blfs-support
Sent: Sunday, March 15, 2020 at 7:33 AM

From: "Pierre Labastie via blfs-support" 

To: blfs-support@lists.linuxfromscratch.org
Cc: "Pierre Labastie" 
Subject: Re: [blfs-support] Gnome not starting
Le 14/03/2020 à 23:46, Cliff McDiarmid via blfs-support a écrit :
> Hi
>
> Update. There was a mistake in the gnome-shell install. I reinstalled, but 
> now i have other errors/warnings:
>
> Mar 14 19:50:03 cliffhanger systemd[1]: Started Session c2 of user 
> cliffhanger.
> Mar 14 19:50:03 cliffhanger nscd[3601]: 3601 monitored file 
> `/etc/resolv.conf` changed (mtime)
> Mar 14 19:50:03 cliffhanger nscd[3601]: 3601 monitoring file 
> `/etc/resolv.conf` (6)
> Mar 14 19:50:03 cliffhanger nscd[3601]: 3601 monitoring directory `/etc` (2)
> Mar 14 19:50:03 cliffhanger dbus-daemon[3945]: [session uid=1000 pid=3943] 
> Activating service name='org.a11y.Bus' requested by ':1.0' (uid=1000 pid=3955 
> comm="/usr/libexec/gnome-session-check-accelerated ")
> Mar 14 19:50:03 cliffhanger dbus-daemon[3945]: [session uid=1000 pid=3943] 
> Successfully activated service 'org.a11y.Bus'
> Mar 14 19:50:03 cliffhanger org.a11y.Bus[3962]: dbus-daemon[3962]: Activating 
> service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=3955 
> comm="/usr/libexec/gnome-session-check-accelerated ")
> Mar 14 19:50:03 cliffhanger org.a11y.Bus[3962]: dbus-daemon[3962]: 
> Successfully activated service 'org.a11y.atspi.Registry'
> Mar 14 19:50:03 cliffhanger org.a11y.Bus[3964]: SpiRegistry daemon is running 
> with well-known name - org.a11y.atspi.Registry
> Mar 14 19:50:03 cliffhanger gnome-session[3934]: gnome-session-binary[3934]: 
> WARNING: Falling back to non-systemd startup procedure due to error: 
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
> org.freedesktop.systemd1 was not provided b>


>If you are on a systemd version of the book (I think so, since you use
>journalctl), this service "name" should be provided.

Thanks Pierrre.  Yes I am using systemd version

>Looks like there's something wrong in your systemd install (or on the way 
>gnome-session accesses
>it, maybe). Does the following return something?

>gdbus introspect --system --dest org.freedesktop.systemd1 \
>--object-path /org/freedesktop/systemd1

Yes, see attachement

>If it does, there is something wrong elsewhere. But I suspect using a
>non-systemd procedure on a systemd host doesn't work

So something is wrong eleswhere.  Can you help at all?  Is this a Mutter 
problem maybe?

Or 'JS ERROR: Error: Requiring Meta, version none: Typelib file for namespace 
'GDesktopEnums', version '3.0' not found' is this relevant?

> Mar 14 19:50:03 cliffhanger gnome-session-binary[3934]: WARNING: Falling back 
> to non-systemd startup procedure due to error: 
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
> org.freedesktop.systemd1 was not provided by any .service files
> Mar 14 19:50:03 cliffhanger gnome-keyring-daemon[3976]: couldn't access 
> control socket: /run/user/1000/keyring/control: No such file or directory
> Mar 14 19:50:03 cliffhanger gnome-keyring-d[3977]: couldn't access control 
> socket: /run/user/1000/keyring/control: No such file or directory
> Mar 14 19:50:03 cliffhanger gnome-keyring-daemon[3977]: couldn't access 
> control socket: /run/user/1000/keyring/control: No such file or directory
> Mar 14 19:50:03 cliffhanger gnome-keyring-d[3976]: couldn't access control 
> socket: /run/user/1000/keyring/control: No such file or directory
> Mar 14 19:50:03 cliffhanger gnome-keyring-daemon[3978]: couldn't access 
> control socket: /run/user/1000/keyring/control: No such file or directory
> Mar 14 19:50:03 cliffhanger gnome-keyring-d[3978]: couldn't access control 
> socket: /run/user/1000/keyring/control: No such file or directory
> Mar 14 19:50:03 cliffhanger gnome-keyring-ssh.desktop[3977]: 
> SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
> Mar 14 19:50:03 cliffhanger gnome-keyring-pkcs11.desktop[3976]: 
> SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
> Mar 14 19:50:03 cliffhanger dbus-daemon[3945]: [session uid=1000 pid=3943] 
> Activating service name='org.gtk.vfs.Daemon' requested by ':1.9' (uid=1000 
> pid=3986 comm="/usr/bin/gnome-shell ")
> Mar 14 19:50:03 cliffhanger dbus-daemon[3945]: [session uid=1000 pid=3943] 
> Successfully activated service 'org.gtk.vfs.Daemon'
> Mar 14 19:50:03 cliffhanger gnome-shell[3986]: 
> clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE 
> (device)' failed
> Mar 14 19:50:03 cliffhanger gnome-shell[3986]: 
> clutter_input_device_get_d

[blfs-support] Gnome not starting

2020-03-14 Thread Cliff McDiarmid via blfs-support
Hi

Update.  There was a mistake in the gnome-shell install.  I reinstalled, but 
now i have other errors/warnings:

Mar 14 19:50:03 cliffhanger systemd[1]: Started Session c2 of user cliffhanger.
Mar 14 19:50:03 cliffhanger nscd[3601]: 3601 monitored file `/etc/resolv.conf` 
changed (mtime)
Mar 14 19:50:03 cliffhanger nscd[3601]: 3601 monitoring file `/etc/resolv.conf` 
(6)
Mar 14 19:50:03 cliffhanger nscd[3601]: 3601 monitoring directory `/etc` (2)
Mar 14 19:50:03 cliffhanger dbus-daemon[3945]: [session uid=1000 pid=3943] 
Activating service name='org.a11y.Bus' requested by ':1.0' (uid=1000 pid=3955 
comm="/usr/libexec/gnome-session-check-accelerated ")
Mar 14 19:50:03 cliffhanger dbus-daemon[3945]: [session uid=1000 pid=3943] 
Successfully activated service 'org.a11y.Bus'
Mar 14 19:50:03 cliffhanger org.a11y.Bus[3962]: dbus-daemon[3962]: Activating 
service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=3955 
comm="/usr/libexec/gnome-session-check-accelerated ")
Mar 14 19:50:03 cliffhanger org.a11y.Bus[3962]: dbus-daemon[3962]: Successfully 
activated service 'org.a11y.atspi.Registry'
Mar 14 19:50:03 cliffhanger org.a11y.Bus[3964]: SpiRegistry daemon is running 
with well-known name - org.a11y.atspi.Registry
Mar 14 19:50:03 cliffhanger gnome-session[3934]: gnome-session-binary[3934]: 
WARNING: Falling back to non-systemd startup procedure due to error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.systemd1 was not provided b>
Mar 14 19:50:03 cliffhanger gnome-session-binary[3934]: WARNING: Falling back 
to non-systemd startup procedure due to error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.systemd1 was not provided by any .service files
Mar 14 19:50:03 cliffhanger gnome-keyring-daemon[3976]: couldn't access control 
socket: /run/user/1000/keyring/control: No such file or directory
Mar 14 19:50:03 cliffhanger gnome-keyring-d[3977]: couldn't access control 
socket: /run/user/1000/keyring/control: No such file or directory
Mar 14 19:50:03 cliffhanger gnome-keyring-daemon[3977]: couldn't access control 
socket: /run/user/1000/keyring/control: No such file or directory
Mar 14 19:50:03 cliffhanger gnome-keyring-d[3976]: couldn't access control 
socket: /run/user/1000/keyring/control: No such file or directory
Mar 14 19:50:03 cliffhanger gnome-keyring-daemon[3978]: couldn't access control 
socket: /run/user/1000/keyring/control: No such file or directory
Mar 14 19:50:03 cliffhanger gnome-keyring-d[3978]: couldn't access control 
socket: /run/user/1000/keyring/control: No such file or directory
Mar 14 19:50:03 cliffhanger gnome-keyring-ssh.desktop[3977]: 
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Mar 14 19:50:03 cliffhanger gnome-keyring-pkcs11.desktop[3976]: 
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Mar 14 19:50:03 cliffhanger dbus-daemon[3945]: [session uid=1000 pid=3943] 
Activating service name='org.gtk.vfs.Daemon' requested by ':1.9' (uid=1000 
pid=3986 comm="/usr/bin/gnome-shell ")
Mar 14 19:50:03 cliffhanger dbus-daemon[3945]: [session uid=1000 pid=3943] 
Successfully activated service 'org.gtk.vfs.Daemon'
Mar 14 19:50:03 cliffhanger gnome-shell[3986]: 
clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
Mar 14 19:50:03 cliffhanger gnome-shell[3986]: 
clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
Mar 14 19:50:03 cliffhanger gnome-shell[3986]: JS ERROR: Error: Requiring Meta, 
version none: Typelib file for namespace 'GDesktopEnums', version '3.0' not 
found
   
@resource:///org/gnome/shell/ui/environment.js:13:53
   @:1:1
Mar 14 19:50:03 cliffhanger gnome-shell[3986]: Execution of main.js threw 
exception: Script  threw an exception
Mar 14 19:50:03 cliffhanger gnome-session[3934]: gnome-session-binary[3934]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Mar 14 19:50:03 cliffhanger gnome-session-binary[3934]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
Mar 14 19:50:03 cliffhanger gnome-shell[4006]: 
clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
Mar 14 19:50:03 cliffhanger gnome-shell[4006]: 
clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
Mar 14 19:50:03 cliffhanger gnome-shell[4006]: JS ERROR: Error: Requiring Meta, 
version none: Typelib file for namespace 'GDesktopEnums', version '3.0' not 
found
   
@resource:///org/gnome/shell/ui/environment.js:13:53
   @:1:1
Mar 14 19:50:03 cliffhanger gnome-shell[4006]: Execution of main.js threw 
exception: Script  threw an exception
Mar 14 19:50:03 cliffhanger gnome-session[3934]: gnome-session-binary[3934]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Mar 14 19:50:03 cliffhanger gnome-se

[blfs-support] Gnome not starting

2020-03-14 Thread Cliff McDiarmid via blfs-support
Hi

Just completed build of latest LFS/BLFS and Gnome packages.  However i have a 
start problem with Gnome.  I'm getting the white screen with 'Opts something 
went wrong.'

I've used GDM and LightDM and am getting the same result.  Although LightDM 
does give me a login screen, before error.

The only errors in the journal as I see it is:

systemd[1]: Starting User Manager for UID 1000...
Mar 14 12:46:54 cliffhanger systemd[3888]: pam_unix(systemd-user:session): 
session opened for user cliffhanger by (uid=0)
Mar 14 12:46:54 cliffhanger wpa_supplicant[3627]: wlp68s0: 
CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Mar 14 12:46:54 cliffhanger systemd[3888]: Reached target Paths.
Mar 14 12:46:54 cliffhanger systemd[3888]: Reached target Timers.
Mar 14 12:46:54 cliffhanger systemd[3888]: Starting D-Bus User Message Bus 
Socket.
Mar 14 12:46:54 cliffhanger systemd[3888]: Listening on D-Bus User Message Bus 
Socket.
Mar 14 12:46:54 cliffhanger systemd[3888]: Reached target Sockets.
Mar 14 12:46:54 cliffhanger systemd[3888]: Reached target Basic System.
Mar 14 12:46:54 cliffhanger systemd[3888]: Reached target Main User Target.
Mar 14 12:46:54 cliffhanger systemd[3888]: Startup finished in 103ms.
Mar 14 12:46:54 cliffhanger systemd[1]: Started User Manager for UID 1000.
Mar 14 12:46:54 cliffhanger systemd[1]: Started Session c2 of user cliffhanger.
Mar 14 12:46:54 cliffhanger dbus-daemon[3907]: [session uid=1000 pid=3905] 
Activating service name='org.a11y.Bus' requested by ':1.0' (uid=1000 pid=3917 
comm="/usr/libexec/gnome-session-check-accelerated ")
Mar 14 12:46:54 cliffhanger dbus-daemon[3907]: [session uid=1000 pid=3905] 
Successfully activated service 'org.a11y.Bus'
Mar 14 12:46:54 cliffhanger org.a11y.Bus[3924]: dbus-daemon[3924]: Activating 
service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=3917 
comm="/usr/libexec/gnome-session-check-accelerated ")
Mar 14 12:46:54 cliffhanger org.a11y.Bus[3924]: dbus-daemon[3924]: Successfully 
activated service 'org.a11y.atspi.Registry'
Mar 14 12:46:54 cliffhanger org.a11y.Bus[3926]: SpiRegistry daemon is running 
with well-known name - org.a11y.atspi.Registry
Mar 14 12:46:54 cliffhanger gnome-session[3896]: gnome-session-binary[3896]: 
WARNING: Falling back to non-systemd startup procedure due to error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.systemd1 was not provided b>
Mar 14 12:46:54 cliffhanger gnome-session-binary[3896]: WARNING: Falling back 
to non-systemd startup procedure due to error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.systemd1 was not provided by any .service files
Mar 14 12:46:54 cliffhanger gnome-session[3896]: gnome-session-binary[3896]: 
WARNING: Unable to find required component 'org.gnome.Shell'
Mar 14 12:46:54 cliffhanger gnome-session-binary[3896]: WARNING: Unable to find 
required component 'org.gnome.Shell'
Mar 14 12:46:54 cliffhanger gnome-session-binary[3896]: Entering running state
Mar 14 12:46:54 cliffhanger dbus-daemon[3907]: [session uid=1000 pid=3905] 
Activating service name='org.gtk.vfs.Daemon' requested by ':1.6' (uid=1000 
pid=3934 comm="/usr/libexec/gnome-session-failed --allow-logout ")
Mar 14 12:46:54 cliffhanger dbus-daemon[3907]: [session uid=1000 pid=3905] 
Successfully activated service 'org.gtk.vfs.Daemon'
Mar 14 12:46:56 cliffhanger kernel: logitech-hidpp-device 0003:046D:400A.0004: 
HID++ 2.0 device connected.
Mar 14 12:46:56 cliffhanger upowerd[3626]: treating change event as add on 
/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.2/0003:046D:C52B.0003/0003:046D:400A.0004/power_supply/hidpp_battery_0
Mar 14 12:46:57 cliffhanger gnome-session-q[3946]: Failed to call logout: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files
Mar 14 12:46:57 cliffhanger lightdm[3876]: pam_unix(lightdm:session): session 
closed for user cliffhanger
Mar 14 12:46:57 cliffhanger systemd[1]: Stopping Session c2 of user cliffhanger.
Mar 14 12:46:57 cliffhanger dbus-daemon[3907]: [session uid=1000 pid=3905] 
Reloaded configuration
Mar 14 12:46:57 cliffhanger systemd[1]: session-c2.scope: Succeeded.
Mar 14 12:46:57 cliffhanger systemd[1]: Stopped Session c2 of user cliffhanger.
Mar 14 12:46:57 cliffhanger systemd-logind[3634]: Removed session c2.

Can someone advise me here as these seem to be warnings rather than errors.  
Would this stop the desktop loading?

thanks

Cliff

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Building GTK+ with Pango/Cairo support(SOLVED)

2020-02-25 Thread Cliff McDiarmid via blfs-support

> >On Sun, Feb 23, 2020 at 11:18:58PM +0100, Cliff McDiarmid via blfs-support 
> >wrote:>> > >> Hi>  > Can anyone help here?  I'm building Gtk+-2.24.13.  
>All dependencies have been built as per book, but I'm getting:>  >> 'Pango not 
>found. Pango built with Cairo support is required to build GTK+'>  
> According to the>> >Meson output Pango is being built with Cairo support:>  
> [...]>>> >Which version of the book?>> Version 9.0 stable>>>> 
>Just in case: was libglade installed when you built pycairo (it should be) ?>> 
>Thanks ken, but it was something simple in the end. A lot of these packages 
>install to /usr. But not to /usr/lib in some cases, but to /usr/lib64.>> 
>>Therefore the .pc files are there too. I just needed to update my 
>PKG_CONFIG_PATH env.variable.>> 
>You can see I only do these builds every year!>> Cliff

>I'm glad you solved it, but /usr/lib64 should not be in use by
>packages in the books (unless you are looking at multilib, I forget
>which libs that uses, but you would definitely need to set
>PKG_CONFIG_PATH differently for 32-bit and 64-bit if you were using
>that).

>In LFS-9.0 and 9.1 on a 64-bit machine we have ld-linux-x86-64.so.2
>and ld-lsb-x86-64.so.3 (both symlinks to /lib) and /usr/lib64 does
>not exist.

>I recall that at times we've had some cmake packages defaulting to
>/usr/lib64 unless overridden, but for everything else *in the books*
>/usr/lib64 should not exist.  Unfortunately, once it does exist,
>packages have a tendency to use it by default.  And at times (some)
>cmake packages tended to use lib64.

>As you discovered, expanding PKG_CONFIG_PATH works around this for
>most packages.

>In the packages I build I can see libdir being forced to /usr/lib in
>eudev, kmod, procps and to 'lib' in openssl (LFS) and in BLFS I see
>lua and PAM.

>For cmake book packages I currently have lib forced in libjpeg_turbo
>(and it was used by some qt packages which I have now archived), and
>also in the non-book package oiio (OpenImageIO) which uses a
>different_ variable for this - my current view on cmake is that
>although we usually have it under control in the book, for
>everything else cmake is still a vale of tears.  (Sorry, I'm still
>struggling to get blender, and what I think are the deps _I_ need,

Thanks ken.  Yes, /usr/lib64 shouldn't exist or at the least should be linked 
to /usr/lib.
Unfortunately when I built LFS to start I did it through jhalfs and this is 
apparently responsible.
I missed the problem and was late to spot it.  And yes I  agree about cmake and 
don't get me on ninja!
Come back ./configure all is forgiven.

Cliff

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Building GTK+ with Pango/Cairo support(SOLVED)

2020-02-24 Thread Cliff McDiarmid via blfs-support
>On Sun, Feb 23, 2020 at 11:18:58PM +0100, Cliff McDiarmid via blfs-support 
>wrote:

> >> Hi>  > Can anyone help here?  I'm building Gtk+-2.24.13.  All dependencies 
> >> have been built as per book, but I'm getting:>  > 
'Pango not found. Pango built with Cairo support is required to build GTK+'>  > 
According to the> 
>Meson output Pango is being built with Cairo support:>  [...]>>
>Which version of the book?>> Version 9.0 stable>>

>Just in case: was libglade installed when you built pycairo (it should be) ?

Thanks ken, but it was something simple in the end.  A lot of these packages 
install to /usr.  But not to /usr/lib in some cases, but to /usr/lib64. 

Therefore the .pc files are there too.  I just needed to update my 
PKG_CONFIG_PATH env.variable.  

You can see I only do these builds every year!

Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Building GTK+ with Pango/Cairo support

2020-02-23 Thread Cliff McDiarmid via blfs-support
>Sent: Sunday, February 23, 2020 at 10:12 PM
>From: "Cliff McDiarmid" 
>To: "BLFS Support List" 
>Subject: Building GTK+ with Pango/Cairo support

>On Sun, Feb 23, 2020 at 09:55:15PM +0100, Cliff McDiarmid via blfs-support 
>wrote:
>> Hi>  > Can anyone help here?  I'm building Gtk+-2.24.13.  All dependencies 
>> have been built as per book, but I'm getting:>  > 'Pango not found. Pango 
>> built with Cairo support is required to build GTK+'>  > According to the 
>Meson output Pango is being built with Cairo support:>  [...]

>Which version of the book?  

Version 9.0 stable

>I think I fixed this on 13th Feb by
>splitting "pycairo2" (1.18.2) into a separate module, linked from
>pygobject2 and pyGTK because the instructions needed to be manually
>read and thought about, so e.g. jhalfs failed.

Building manually

>And if you have been looking at an older version of the svn book and
>are now updating to a current version, please remember that
>gimp-2.10.16 should NOT be used because upstream reported data
>corruption and are in the process of releasing 2.10.18 (when I look
>at what I think is the main site, 2.10.18 has been shown for a few
>hours as latest, but about 45 minutes ago the link to the tarball
>still failed.

No concern here.  Not installing.

thanks  ken

Cliff
 
 
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Building GTK+ with Pango/Cairo support

2020-02-23 Thread Cliff McDiarmid via blfs-support

On Sun, Feb 23, 2020 at 09:55:15PM +0100, Cliff McDiarmid via blfs-support wrote:
>
> Hi
>  
> Can anyone help here?  I'm building Gtk+-2.24.13.  All dependencies have been built as per book, but I'm getting:
>  
> 'Pango not found. Pango built with Cairo support is required to build GTK+'
>  
> According to the Meson output Pango is being built with Cairo support:
>  
[...]
>  
> Any ideas?
>  
> thanks
>  
> Cliff

>Which version of the book?

Version 9.0 stable

>I think I fixed this on 13th Feb by
>splitting "pycairo2" (1.18.2) into a separate module, linked from
>pygobject2 and pyGTK because the instructions needed to be manually
>read and thought about, so e.g. jhalfs failed.

Building manually

>And if you have been looking at an older version of the svn book and
>are now updating to a current version, please remember that
>gimp-2.10.16 should NOT be used because upstream reported data
>corruption and are in the process of releasing 2.10.18 (when I look
>at what I think is the main site, 2.10.18 has been shown for a few
>hours as latest, but about 45 minutes ago the link to the tarball
>still failed.

No concern here.  Not installing.

thanks  ken


Cliff

 

 

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Building GTK+ with Pango/Cairo support

2020-02-23 Thread Cliff McDiarmid via blfs-support

Hi
 
Can anyone help here?  I'm building Gtk+-2.24.13.  All dependencies have been 
built as per book, but I'm getting:
 
'Pango not found. Pango built with Cairo support is required to build GTK+'
 
According to the Meson output Pango is being built with Cairo support:
 

Found pkg-config: /usr/bin/pkg-config (0.29.2)
Run-time dependency gobject-2.0 found: YES 2.62.4
Run-time dependency fribidi found: YES 1.0.5
Found CMake: /usr/bin/cmake (3.16.4)
Run-time dependency libthai found: NO (tried pkgconfig and cmake)
Run-time dependency harfbuzz found: YES 2.6.0
Run-time dependency fontconfig found: YES 2.13.1
Checking for function "FcWeightFromOpenTypeDouble" with dependency fontconfig: 
YES
Run-time dependency freetype2 found: YES 23.1.17
Run-time dependency xft found: YES 2.3.3
Run-time dependency xrender found: YES 0.9.10
Run-time dependency cairo found: YES 1.17.3
Run-time dependency cairo-ft found: YES 1.17.3
Run-time dependency cairo-win32 found: NO (tried pkgconfig and cmake)
Run-time dependency cairo-quartz found: NO (tried pkgconfig and cmake)
Run-time dependency cairo-png found: YES 1.17.3
Run-time dependency cairo-ps found: YES 1.17.3
Run-time dependency cairo-pdf found: YES 1.17.3
Run-time dependency cairo-xlib found: YES 1.17.3
 
 
Any ideas?
 
thanks
 
Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] Authentication failure when reinstalling Shadow

2020-02-11 Thread Cliff McDiarmid via blfs-support
>Sent: Tuesday, February 11, 2020 at 8:18 PM
>From: "Pierre Labastie via blfs-support" 
>
>To: blfs-support@lists.linuxfromscratch.org
>Cc: "Pierre Labastie" 
>Subject: Re: [blfs-support] Authentication failure when reinstalling Shadow
>Le 11/02/2020 à 20:19, Cliff McDiarmid via blfs-support a écrit :
> Hi
>  
> For the first time when building an LFS/BLFS system I have a problem when 
> reinstalling Shadow in Chapter 4. Security
>
> When trying to su to root from the user after logging in, I get 
> 'su.authentication failure'
>
> I have checked the following as suggested:
>
> 1. Ran the test suite from Linux Pam with no errors
>
> 2. Added the user to the wheel group.

>Just to be sure, have logged out and in after that?

Yes many times

>
> 3. Added the user to the sudoers file with ALL permissions

>Remove or comment out the %wheel line in the sudoers file. It may take
>precedence over the user one. Also, remove (or comment out) the %wheel line in
>/etc/sudoers.d/sudo, if you have installed that file. But this shouldn't
>change the behavior of "su", only of "sudo".

Done that now

>su with PAM works for me if I am in the "wheel" group. If you are able to run
>"sudo", you can type "sudo su -" if needed to become root.

I can but 'sudo su' doesn't work. I get : 

sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?

Obvious answer : No


Thanks Pierre

Cliff




-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Authentication failure when reinstalling Shadow

2020-02-11 Thread Cliff McDiarmid via blfs-support
Hi
 
For the first time when building an LFS/BLFS system I have a problem when 
reinstalling Shadow in Chapter 4. Security

When trying to su to root from the user after logging in, I get 
'su.authentication failure'

I have checked the following as suggested:

1. Ran the test suite from Linux Pam with no errors

2. Added the user to the wheel group.

3. Added the user to the sudoers file with ALL permissions

Where do I go from here?  If i reinstall Shadow without PAM I assume i go back 
to su to root from user?

If I cannot solve this could I go on?

Thanks

Cliff

 

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] GDM startup problem

2020-01-21 Thread Cliff McDiarmid via blfs-support
>Sent: Tuesday, January 21, 2020 at 1:50 AM
>From: "Christopher Gregory via blfs-support" 
>
>To: blfs-support@lists.linuxfromscratch.org
>Cc: "Christopher Gregory" 
>Subject: Re: [blfs-support] GDM startup problem

> Sent: Tuesday, January 21, 2020 at 12:11 PM
> From: "Ken Moffat via blfs-support" 
> To: "BLFS Support List" 
> Cc: "Ken Moffat" 
> Subject: Re: [blfs-support] GDM startup problem
>
> On Mon, Jan 20, 2020 at 11:01:45PM +0100, Cliff McDiarmid via blfs-support 
> wrote:
> > .Sent: Saturday, January 18, 2020 at 8:55 PM
> > >From: "Ken Moffat via blfs-support" 
> > >
> > >To: "BLFS Support List" 
> > >Cc: "Ken Moffat" 
> > >Subject: Re: [blfs-support] GDM startup problem
> > >On Sat, Jan 18, 2020 at 08:24:55PM +0100, Cliff McDiarmid via blfs-support 
> > >wrote:
> > >
> >
> > >I notice that two of those directories are from January and March
> > >2017. That suggests that the base LFS system is 8.2 or before ?
> >
> > 7.9-systemd-rc2
> >
>
> So, I can't count or have forgotten which year we are in. The
> problem with diagnosing if it is a systemd problem, or indeed a
> toolchain problem, is that everything has moved on a lot. However,
> your next response suggests otherwise.
>
> > >I don't use systemd, let alone gdm, so I can't comment on any known
> > >issues along the way - but I start to wonder if versions have got
> > >out of kilter. I have no idea what mix of packages / versions you
> > >are running, perhaps summarising (gcc, binutils, glibc, kernel
> > >headers, meson, systemd, kernel, glib, gtk3, gnome) might help if
> > >someone who uses gdm reads this.
> >
> > Correct - all the packages mentioned. The system has been running for over 
> > a year without issues.
>
> That _is_ somewhat worrying. At one time I wondered if a memory
> problem (one chip starting to fail) might be involved. I can't see
> any likely connection, but perhaps memtest86 (current) might dismiss
> that possibility. It isn't libre, and the free version defaults to
> only 4 passes (or maybe is limited to only 4), but it seems to work
> well - and better than the old memtest86+.
>
> More likely, if packages have not been updated I think it is
> possible that someone has strung vulnerabilities together. There
> have been vulnerabilities all over the place - both the kernel and
> userspace such as ghostscript and browser engines.
>
> > I had begun the build a new lfs from this one using Jhalfs. Relevant?
> >
>
> Not a likely cause of the problem, but I suppose that with a bind
> mount something in chroot might be doing this. You would need to
> ask people who use jhalfs from a session running under gdm, but only
> if you have been doing that between restoring from backup and
> hitting the problem.
>
> >
> > >Not sure if I've parsed that last sentence, so let me try what I
> > >think you are saying:
> >
> > >1. On the broken system, you changed ownership of
> > >/var/lib/gdm/.local/share to gdm:gdm (but not the .local directory
> > >itself - I have no idea what else, if anything that contains).
> >
> > Correct. Based on forum advice.
> >
> > >2. This possibly made progress, i.e. X tried to load the nvidia
> > >module but failed. I regard that as 'possible' progress because I
> > >suspect that happens after opening the log.
> >
> > Yes. The directories were accessible again, but the nvidia module fails to 
> > load.
> >
> > >3. You restored from backup. I think you are saying that this used
> > >to work for a while, even without changing perms, but now you are
> > >back to the failure to open the log ? ~Or are you back to the
> > >nvidia error
> >
> > Correct. The backup was from a working system on the 7.1.20. And back to 
> > failure to open log after maybe three reboots.
> >
>
> The only other things I suggest are that you make a note of what you
> are doing, and where you browse, to see if there is any likely
> connection.
>
> And: please read the LFS and BLFS errata - particularly the current
> 9.0 errata (we are getting better at updating that re
> vulnerabilities) but also previous versions back to 7.9 to see if
> any of your packages are mentioned.
>
> I recommend that you keep the current good backup, but also update
> vulnerable packages to the extent you are able (dependencies change,
> and some things give problems with older versions of dependencies or

Re: [blfs-support] GDM startup problem

2020-01-20 Thread Cliff McDiarmid via blfs-support
>Sent: Sunday, January 19, 2020 at 1:02 AM
>From: "Ken Moffat via blfs-support" 
>To: "BLFS Support List" 
>Cc: "Ken Moffat" 
>Subject: Re: [blfs-support] GDM startup problem

 


On Sat, Jan 18, 2020 at 09:16:50PM +0100, Cliff McDiarmid via blfs-support wrote:
> Hi
>
> The permissions from my working LFS(I've just restored it - again)
>  
>
> drwxrwx--T  6 gdm  gdm   4096 Jan 18 20:00 .
> drwxr-xr-x 31 root root  4096 Jul 10  2019 ..
> drwx--  5 gdm  gdm   4096 Apr 14  2019 .cache
> drwx--  7 gdm  gdm   4096 Apr  1  2019 .config
> -rw---  1 gdm  gdm 16 Apr  1  2019 .esd_auth
> -rw---  1 gdm  gdm  35172 Jan 18 20:00 .ICEauthority
> drwxr-xr-x  3 root root  4096 Mar 17  2019 .local
> drwx--  3 gdm  gdm   4096 Apr  1  2019 .nv
>  
> It usually fails aftre several reboots
>  
> Cliff
>  

>So, if before you logout of gdm each time, root could ls -lR those
>directories, and the .config subdirectories, and also just before
>shutting down/rebooting (perhaps do _that_ from a tty) you might be
>able to notice a change when it next fails. Obviously, *check* the
>results of 'ls -lR' and adapt the switches and arguments to
>minimally get the relevant directories and files before starting to
>use it as a matter of course.

>Of course, sod's law says you'll usually remember to run that, but
>the one time you don't will be when things go wrong.

>At the moment we don't know if gdm is somehow managing to trash
>perms when you logout, or when you use gdm to
>poweroff|reboot|hibernate, or if something else entirely unrelated
>happens to do that. If the latter, think about what ran during the
>last successful session. Maybe a bad script under su or sudo, but
>maybe something worse (someone taking advantage of a vulnerability,
>but accidentally changing the ownership back to root:root and
>therefore causing gdm to fail). Seems unlikely, but I don't know
>who you are, what browser(s) you use, how up to date they are, what
>URLs you visit, what you run, whether or not you have other local
>human users. And no, I really don't want to know more about your
>setup, I'm just trying to point out what you might need to think
>?about.

>For the moment it _looks_ like the perms are the normal problem, but
>we have no idea what you are running (beyond _some_ version of gdm,
>some version of systemd, and apparently the nvidia external kernel
>module).

>And if the perms do change, look at the whole system and compare it
>to the backup to see if anything else changed perms (binaries, libs,
>libexec). Of the "good" possibilities, either something in gdm, or
>in another regular daemon, has hit a bug, or perhaps a regular task
>(maybe cron-style) is doing the wrong thing.

>As I think I've said to you before: Good Luck - in this case I think
>you'll need it.
 

Good advice.  Many thanks

 

Cliff



-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] GDM startup problem

2020-01-20 Thread Cliff McDiarmid via blfs-support
.Sent: Saturday, January 18, 2020 at 8:55 PM
>From: "Ken Moffat via blfs-support" 
>To: "BLFS Support List" 
>Cc: "Ken Moffat" 
>Subject: Re: [blfs-support] GDM startup problem
>On Sat, Jan 18, 2020 at 08:24:55PM +0100, Cliff McDiarmid via blfs-support 
>wrote:
>
>
> >at a guess there is something wrong with that directory
> >(non-existent, or wrong owner or wrong perms). Possibly 
> >>http://www.mgreene.org/?p=302[http://www.mgreene.org/?p=302[http://www.mgreene.org/?p=302]]
>
> Thanks Ken. That's what I thought originally. Followed those suggestions as 
> part of the 'solving' but it made no difference.
>
> Reinsalled GDM. No difference.
>
> >Pasting from that, since you cannot run X (note that his log was in
> >.local/share not .local)
> >Simple solution, chown -R gdm.gdm /var/lib/gdm
>
> This time did: 'chgrp gdm /var/lib/gdm/.local/share' and 'chown gdm 
> /var/lib/gdm/.local/share'
>
> drwxrwx--T 6 gdm gdm 4096 Jan 17 22:50 .
> drwxr-xr-x 31 root root 4096 Jul 10 2019 ..
> drwx-- 6 gdm gdm 4096 Jan 18 15:34 .cache
> drwx-- 7 gdm gdm 4096 Apr 1 2019 .config
> -rw--- 1 root root 16 Apr 1 2019 .esd_auth
> -rw--- 1 root root 34826 Jan 17 00:24 .ICEauthority
> drwxr-xr-x 3 root root 4096 Mar 17 2019 .local
> drwx-- 3 gdm gdm 4096 Apr 1 2019 .nv
>

>I notice that two of those directories are from January and March
>2017. That suggests that the base LFS system is 8.2 or before ?

7.9-systemd-rc2

>I don't use systemd, let alone gdm, so I can't comment on any known
>issues along the way - but I start to wonder if versions have got
>out of kilter. I have no idea what mix of packages / versions you
>are running, perhaps summarising (gcc, binutils, glibc, kernel
>headers, meson, systemd, kernel, glib, gtk3, gnome) might help if
>someone who uses gdm reads this.

Correct - all the packages mentioned.   The system has been running for over a 
year without issues.
I had begun the build a new lfs from this one using Jhalfs.  Relevant?

> I don't get the access errors as before but now get:
>  
> (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
> [ 2.778] (EE) NVIDIA: system's kernel log for additional error 
> messages and
> [ 2.778] (EE) NVIDIA: consult the NVIDIA README for details.
> No apparent reason for this.  As mentioned have tried recovering the LFS from 
> backup but the errors return.
>  
> Cliff

>Not sure if I've parsed that last sentence, so let me try what I
>think you are saying:

>1. On the broken system, you changed ownership of
>/var/lib/gdm/.local/share to gdm:gdm (but not the .local directory
>itself - I have no idea what else, if anything that contains).

Correct. Based on forum advice.

>2. This possibly made progress, i.e. X tried to load the nvidia
>module but failed. I regard that as 'possible' progress because I
>suspect that happens after opening the log.

Yes.  The directories were accessible again, but the nvidia module fails to 
load.

>3. You restored from backup. I think you are saying that this used
>to work for a while, even without changing perms, but now you are
>back to the failure to open the log ? ~Or are you back to the
>nvidia error

Correct.  The backup was from a working system on the 7.1.20.  And back to 
failure to open log after maybe three reboots. 

>For the nvidia kernel module - had you updated the kernel since
>your last usable backup ('usable' in the sense of "I've restored
>this once and gdm worked") 

No the kernel module has been in use for the length of the system.

>Sorry, this is all outside my areas of adequacy

No worries

thanks Cliff


-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] GDM startup problem

2020-01-18 Thread Cliff McDiarmid via blfs-support
Hi

The permissions from my working LFS(I've just restored it - again)
 

drwxrwx--T  6 gdm  gdm   4096 Jan 18 20:00 .
drwxr-xr-x 31 root root  4096 Jul 10  2019 ..
drwx--  5 gdm  gdm   4096 Apr 14  2019 .cache
drwx--  7 gdm  gdm   4096 Apr  1  2019 .config
-rw---  1 gdm  gdm 16 Apr  1  2019 .esd_auth
-rw---  1 gdm  gdm  35172 Jan 18 20:00 .ICEauthority
drwxr-xr-x  3 root root  4096 Mar 17  2019 .local
drwx--  3 gdm  gdm   4096 Apr  1  2019 .nv
 
It usually fails aftre several reboots
 
Cliff
 
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] GDM startup problem

2020-01-18 Thread Cliff McDiarmid via blfs-support

On Sat, Jan 18, 2020 at 12:25:31AM +0100, Cliff McDiarmid via blfs-support 
wrote:
> Hi>> I have a problem with a LFS box at startup. I've tracked the problem to 
> GDM. The kernel starts okay then Xorg stops. I've managed to access the 
> journal and the error concerns the /var/lib/gdm dir. 
>I've been unable to solve it. And it keeps happening, i.e I have restored the 
>system from backup and after a couple of boots the error reoccurs each time 
>with a core dump. This problem 'just happened' for no >reason. This is the 
>mystery.
> Jan 17 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]: (EE)> Jan 17 
> 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]: Fatal server error:> 
> Jan 17 22:11:41 alienware-r17 /usr/libexec>
>/gdm->xsession[3795]: (EE) Cannot open log file "/var/lib/gdm/.local/

>at a guess there is something wrong with that directory
>(non-existent, or wrong owner or wrong perms).  Possibly 
>>http://www.mgreene.org/?p=302[http://www.mgreene.org/?p=302]

Thanks Ken.  That's what I thought originally.  Followed those suggestions as 
part of the 'solving' but it made no difference.

Reinsalled GDM.  No difference.

>Pasting from that, since you cannot run X (note that his log was in
>.local/share not .local)
>Simple solution, chown -R gdm.gdm /var/lib/gdm

This time did: 'chgrp gdm /var/lib/gdm/.local/share' and 'chown gdm 
/var/lib/gdm/.local/share'

drwxrwx--T  6 gdm  gdm   4096 Jan 17 22:50 .
drwxr-xr-x 31 root root  4096 Jul 10  2019 ..
drwx--  6 gdm  gdm   4096 Jan 18 15:34 .cache
drwx--  7 gdm  gdm   4096 Apr  1  2019 .config
-rw---  1 root root16 Apr  1  2019 .esd_auth
-rw---  1 root root 34826 Jan 17 00:24 .ICEauthority
drwxr-xr-x  3 root root  4096 Mar 17  2019 .local
drwx--  3 gdm  gdm   4096 Apr  1  2019 .nv

I don't get the access errors as before but now get:
 
(EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[ 2.778] (EE) NVIDIA: system's kernel log for additional error messages 
and
[ 2.778] (EE) NVIDIA: consult the NVIDIA README for details.
[ 2.779] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please 
see the
[ 2.779] (EE) NVIDIA: system's kernel log for additional error messages 
and
[ 2.779] (EE) NVIDIA: consult the NVIDIA README for details.
[ 2.779] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please 
see the
[ 2.779] (EE) NVIDIA: system's kernel log for additional error messages 
and
[ 2.779] (EE) NVIDIA: consult the NVIDIA README for details.
[ 2.779] (EE) [drm] Failed to open DRM device for (null): -2
[ 2.779] (EE) [drm] Failed to open DRM device for pci::01:00.0: -2
[ 2.780] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please 
see the
[ 2.780] (EE) NVIDIA: system's kernel log for additional error messages 
and
[ 2.780] (EE) NVIDIA: consult the NVIDIA README for details.
[ 2.780] (EE) [drm] Failed to open DRM device for (null): -2
[ 2.780] (EE) [drm] Failed to open DRM device for (null): -2
[ 2.780] (EE) No devices detected.
 
No apparent reason for this.  As mentioned have tried recovering the LFS from 
backup but the errors return.
 
Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] GDM startup problem

2020-01-17 Thread Cliff McDiarmid via blfs-support
Hi

I have a problem with a LFS box at startup.  I've tracked the problem to GDM.  
The kernel starts okay then Xorg stops.  I've managed to access the journal and 
the error concerns the /var/lib/gdm dir.

I've been unable to solve it.  And it keeps happening, i.e I have restored the 
system from backup and after a couple of boots the error reoccurs each time 
with a core dump.  This problem 'just happened' for no reason.  This is the 
mystery.

Jan 17 22:11:41 alienware-r17 gdm-launch-environment][3777]: GdmSession worker: 
watching pid 3795
Jan 17 22:11:41 alienware-r17 gdm[3756]: GdmSession: Emitting 'session-started' 
signal with pid '3795'
Jan 17 22:11:41 alienware-r17 gdm[3756]: GdmDisplay: Greeter started
Jan 17 22:11:41 alienware-r17 gdm-x-session[3795]: Enabling debugging
Jan 17 22:11:41 alienware-r17 gdm-x-session[3795]: Preparing auth file for X 
server
Jan 17 22:11:41 alienware-r17 gdm-x-session[3795]: Running X server
Jan 17 22:11:41 alienware-r17 gdm-x-session[3795]: GLib: posix_spawn avoided 
(fd close requested) (child_setup >
Jan 17 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]: (EE)
Jan 17 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]: Fatal server 
error:
Jan 17 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]: (EE) Cannot 
open log file "/var/lib/gdm/.local/>
Jan 17 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]: (EE)
Jan 17 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]: (EE)
Jan 17 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]: Please consult 
the The X.Org Foundation support
Jan 17 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]:  at 
http://wiki.x.org
Jan 17 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]:  for help.
Jan 17 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]: (EE)
Jan 17 22:11:41 alienware-r17 kernel: usb 1-9: new high-speed USB device number 
5 using xhci_hcd
Jan 17 22:11:41 alienware-r17 systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
Jan 17 22:11:41 alienware-r17 systemd[1]: Started Process Core Dump (PID 
3798/UID 0).
Jan 17 22:11:41 alienware-r17 kernel: ath10k_pci :44:00.0: unsupported HTC 
service id: 1536
Jan 17 22:11:41 alienware-r17 kernel: ath10k_pci :44:00.0: Unknown eventid: 
118809
Jan 17 22:11:41 alienware-r17 kernel: ath10k_pci :44:00.0: Unknown eventid: 
90118
Jan 17 22:11:41 alienware-r17 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp68s0: link 
is not ready
Jan 17 22:11:41 alienware-r17 gdm-launch-environment][3777]: accountsservice: 
ActUserManager: sending user-chan>
Jan 17 22:11:41 alienware-r17 gdm-launch-environment][3777]: accountsservice: 
ActUserManager: sent user-changed>
Jan 17 22:11:41 alienware-r17 gdm-launch-environment][3777]: accountsservice: 
ActUserManager: updating user gdm
Jan 17 22:11:41 alienware-r17 NetworkManager[3680]:   [1579299101.7694] 
device (wlp68s0): set-hw-addr: se>
Jan 17 22:11:41 alienware-r17 gdm-x-session[3795]: X server did not write 
display string
Jan 17 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]: Unable to run X 
server
Jan 17 22:11:41 alienware-r17 gdm-launch-environment][3777]: GdmSessionWorker: 
child (pid:3795) done (status:70)
Jan 17 22:11:41 alienware-r17 gdm-launch-environment][3777]: GdmSessionWorker: 
uninitializing PAM
Jan 17 22:11:41 alienware-r17 gdm-launch-environment][3777]: GdmSessionWorker: 
state NONE
Jan 17 22:11:41 alienware-r17 gdm[3756]: GdmSession: Emitting 'session-exited' 
signal with exit code '70'


Jan 17 22:11:41 alienware-r17 /usr/libexec/gdm-x-session[3795]: Unable to run X 
server


Can anyone help here?

Thanks Cliff

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] A EFI boot question

2019-09-15 Thread Cliff McDiarmid via blfs-support
> On 15/09/2019 17:07, Cliff McDiarmid via blfs-support wrote:
> Hi
>  
> I'm trying to boot an LFS from the an EFI partition.   The GRUB 2 EFI binary
> (grubx64.efi) is installed alone in its subdirectory of the ESP, i.e.
> /boot/EFI.  The grub configuration files are installed in /boot ON the EFI
> partition.   in the same partition I have the kernel and system.map.
>  
> My partitions
>  
> NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
> sda   8:00 931.5G  0 disk
> ├─sda18:10   128M  0 part
> ├─sda28:20  97.7G  0 part /mnt/win_data
> └─sda38:30 833.7G  0 part /mnt/linux_data
> nvme0n1 259:00 232.9G  0 disk
> ├─nvme0n1p1 259:10   200M  0 part /boot
> ├─nvme0n1p2 259:20   128M  0 part
> ├─nvme0n1p3 259:30  30.1G  0 part
> ├─nvme0n1p4 259:40  33.5G  0 part /mnt/home
> ├─nvme0n1p5 259:5051G  0 part
> ├─nvme0n1p6 259:6035G  0 part /mnt/LFS10
> └─nvme0n1p7 259:7044G  0 part /
>  
> My grub.config
>  
> # Begin /boot/grub/grub.cfg
> set default=0
> set timeout=10
> #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
> GRUB_CMDLINE_LINUX="text"
> GRUB_TERMINAL=console
> insmod ext2
> insmod gzio
> insmod part_gpt
> set root=(hd1,gpt6)
> insmod efi_gop
> insmod efi_uga
> menuentry "LFS11, Linux 4.20.8-lfs-7.9-rc2 systemd" {
>  linux /boot/lfskernel-4.20.8 root=/dev/nvme0n1p7 ro
> }
>  
> At the moment it boots okay with the above setup, but it's not accessing the
> kernel on the EFI partition.  I've tried altering the (hd1,gpt6) to
> (hd1,gpt1), but then no kernel is found anywhere. It insists on seeking the
> copy on LFS10.  If I take that copy away it won't boot again. 
>  
> Grub was installed from the nvme0n1p7 partition i.e / with the necessary 
> options.
>  

>When altering the (hd1,gpt6) to (hd1,gpt1), did you change the "linux" line to:
>linux /lfskernel-4.20.8 root=/dev/nvme0n1p7 ro
>? (remove /boot). There is not /boot directory on (hd1,gpt1).

That's it, thanks Pierre.  Missed that - of course.

Cliff

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] A EFI boot question

2019-09-15 Thread Cliff McDiarmid via blfs-support
Hi

 

I'm trying to boot an LFS from the an EFI partition.   The GRUB 2 EFI binary (grubx64.efi) is installed alone in its subdirectory of the ESP, i.e. /boot/EFI.  The grub configuration files are installed in /boot ON the EFI partition.   in the same partition I have the kernel and system.map.

 

My partitions


 

NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda   8:0    0 931.5G  0 disk
├─sda1    8:1    0   128M  0 part
├─sda2    8:2    0  97.7G  0 part /mnt/win_data
└─sda3    8:3    0 833.7G  0 part /mnt/linux_data
nvme0n1 259:0    0 232.9G  0 disk
├─nvme0n1p1 259:1    0   200M  0 part /boot
├─nvme0n1p2 259:2    0   128M  0 part
├─nvme0n1p3 259:3    0  30.1G  0 part
├─nvme0n1p4 259:4    0  33.5G  0 part /mnt/home
├─nvme0n1p5 259:5    0    51G  0 part
├─nvme0n1p6 259:6    0    35G  0 part /mnt/LFS10
└─nvme0n1p7 259:7    0    44G  0 part /

 

My grub.config

 



# Begin /boot/grub/grub.cfg
set default=0
set timeout=10

#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

GRUB_CMDLINE_LINUX="text"

GRUB_TERMINAL=console

insmod ext2
insmod gzio
insmod part_gpt
set root=(hd1,gpt6)

insmod efi_gop
insmod efi_uga

menuentry "LFS11, Linux 4.20.8-lfs-7.9-rc2 systemd" {
 linux /boot/lfskernel-4.20.8 root=/dev/nvme0n1p7 ro
}

 

At the moment it boots okay with the above setup, but it's not accessing the kernel on the EFI partition.  I've tried altering the (hd1,gpt6) to (hd1,gpt1), but then no kernel is found anywhere. It insists on seeking the copy on LFS10.  If I take that copy away it won't boot again. 

 

Grub was installed from the nvme0n1p7 partition i.e / with the necessary options.

 

Any ideas?

 

thanks

 

Cliff


 
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] Loading nvidia driver settings(Solved)

2019-06-16 Thread Cliff McDiarmid via blfs-support
>Sent: Thursday, June 13, 2019 at 2:29 AM
>From: "Christopher Gregory via blfs-support" 
>
>To: blfs-support@lists.linuxfromscratch.org
>Cc: "Christopher Gregory" 
>Subject: Re: [blfs-support] Loading nvidia driver settings

> Sent: Thursday, June 13, 2019 at 5:47 AM
> From: "Cliff McDiarmid via blfs-support" 
> 
> To: blfs-support@lists.linuxfromscratch.org
> Cc: "Cliff McDiarmid" 
> Subject: Re: [blfs-support] Loading nvidia driver settings
>
> Sent: Wednesday, June 12, 2019 at 12:58 AM
> From: "Christopher Gregory via blfs-support" 
> 
> To: blfs-support@lists.linuxfromscratch.org
> Cc: "Christopher Gregory" 
> Subject: Re: [blfs-support] Loading nvidia driver settings
>
> > Sent: Wednesday, June 12, 2019 at 7:36 AM
> > From: "Cliff McDiarmid via blfs-support" 
> > 
> > To: "BLFS Support List" 
> > Cc: "Cliff McDiarmid" 
> > Subject: [blfs-support] Loading nvidia driver settings
> >
> > Hi
> >  
> > Is there anyone out there running the nvidia driver?
> >
> > I'm trying to preserve the nvidia-settings at boot up.
> >
> > 'nvidia-settings --load-config-only' can load them from .xinit apparently, 
> > but this doesn't work.
> >
> > I've tried creating a service file for systemd and sourcing a script, with 
> > 'nvidia-settings --load-config-only', at start up but this doesn't work 
> > either.
> >
> > Checked all permissions.
> >
> > Any ideas. Apologies for abandoning nouveau.
>
> >Take a look at ArchLinux:
>
> >https://wiki.archlinux.org/index.php/NVIDIA[https://wiki.archlinux.org/index.php/NVIDIA[https://wiki.archlinux.org/index.php/NVIDIA]]
>
> >Apparently nvidia has an auto-configureation tool
>
> Thanks Christopher I understand.
>
> What I need is a method to preserve the settings from the tool so that they 
> are applied after each reboot.
>
> Or after a suspend for that maatter.

>From the Arch Linux wiki they have the following for doing exactly what you 
>require.

>You need to run the nvidia-settings tool to generate the required settings, 
>and then you need to save the results to a file:

~>.nvidia-settings-rc

>Arch mentions nothing about a service file for systemd. This needs to be 
>created as your normal user.

Thanks.  That's right it gets updated every time one makes any adjustment, but 
the corrwct way to call it is through 'nvidia-settings --load-config-only'.  

I was only trying systemd because I was desparate.  Anyway have managed to get 
the settings applied through a .desktop file in .config/autostart in Gnome 
using the above.

regards

Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] Loading nvidia driver settings

2019-06-12 Thread Cliff McDiarmid via blfs-support
Sent: Wednesday, June 12, 2019 at 12:58 AM
From: "Christopher Gregory via blfs-support" 

To: blfs-support@lists.linuxfromscratch.org
Cc: "Christopher Gregory" 
Subject: Re: [blfs-support] Loading nvidia driver settings

> Sent: Wednesday, June 12, 2019 at 7:36 AM
> From: "Cliff McDiarmid via blfs-support" 
> 
> To: "BLFS Support List" 
> Cc: "Cliff McDiarmid" 
> Subject: [blfs-support] Loading nvidia driver settings
>
> Hi
>  
> Is there anyone out there running the nvidia driver?
>
> I'm trying to preserve the nvidia-settings at boot up.
>
> 'nvidia-settings --load-config-only' can load them from .xinit apparently, 
> but this doesn't work.
>
> I've tried creating a service file for systemd and sourcing a script, with 
> 'nvidia-settings --load-config-only', at start up but this doesn't work 
> either.
>
> Checked all permissions.
>
> Any ideas. Apologies for abandoning nouveau.

>Take a look at ArchLinux:

>https://wiki.archlinux.org/index.php/NVIDIA[https://wiki.archlinux.org/index.php/NVIDIA]

>Apparently nvidia has an auto-configureation tool

Thanks Christopher I understand.  

What I need is a method to preserve the settings from the tool so that they are 
applied after each reboot.

Or after a suspend for that maatter.

Cliff





-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Loading nvidia driver settings

2019-06-11 Thread Cliff McDiarmid via blfs-support
Hi
 
Is there anyone out there running the nvidia driver?  

I'm trying to preserve the nvidia-settings at boot up.  

'nvidia-settings --load-config-only' can load them from .xinit apparently, but 
this doesn't work.

I've tried creating a service file for systemd and sourcing a script, with 
'nvidia-settings --load-config-only', at start up but this doesn't work either.

Checked all permissions.

Any ideas.   Apologies for abandoning nouveau.

thanks

Cliff




-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] Bluez and Obex daemon(Solved)

2019-05-16 Thread Cliff McDiarmid via blfs-support
>On Tuesday, May 14, 2019, Cliff McDiarmid via blfs-support 
>mailto:blfs-support@lists.linuxfromscratch.org]>
> wrote:>Sent: Tuesday, May 14, 2019 at 6:30 PM
>From: "Grover 92000 via blfs-support" 
>mailto:blfs-support@lists.linuxfromscratch.org]>
>To: "BLFS Support List" 
>mailto:blfs-support@lists.linuxfromscratch.org]>
>Cc: "Grover 92000" mailto:grover92...@gmail.com]>
>Subject: Re: [blfs-support] Bluez and Obex daemon

>On 12.5.2019. 19:17, Cliff McDiarmid via 
 
>It sounds like /etc/X11/xinit/xinitrc.d/50-systemd-user.sh isn't getting 
>sourced when you login.
>I had a similar problem when I switched to lightdm.
>When I was using lxdm I didn't have the problem. What desktop manager are you 
>using?

>Thanks for that. I'm using GDM. And it's same on the previous system where 
>Bluetooth is working, so how is 50-systemd-user.sh being sourced
>assuming this is the problem? 
 
>50-systemd-user.sh is typically sourced early  in the xorg startup by either a 
>wrapper script or the desktop manager. I don't think that the script being 
>sourced is the problem - the opposite.
>'systemctl enable --user obex' does work from a user environment, but makes no 
>difference to my problem. 
 
>I would try this. Back out all the systemd changes made and make obex globally 
>available to all users like you did originally.  Then disable gdm. Login 
>manually and create a ~/.xinitrc file with this:
 
>export GDK_BACKEND=x11
 
>if [ -d /etc/X11/xinit/xinitrc.d ]; then
  >for f in /etc/X11/xinit/xinitrc.d/?.sh
   > [ -x "$f" ] && . "$f"
>  done
>fi
 
>exec gnome-session

Thanks for that Grover, but I've found the problem.  In fact I'm moving files 
now so it's solved I feel.

The culprit was the 'org.bluez.obex.service' file.  It read:

[D-BUS Service]
Name=org.bluez.obex
Exec=/usr/false
SystemdService=dbus-org.bluez.obex.service   (don't ask me how this 
happened)

now

[D-BUS Service]
Name=org.bluez.obex
Exec=/usr/libexec/bluetooth/obexd
SystemdService=dbus-org.bluez.obex.service

I'm still getting errors from 'systemctl status bluetooth' and from the journal 
such as:

Unable to get io data for Object Push: getpeername: Transport endpoint is not 
connected

but as mentioned I'm able to move files.

thanks again

Cliff



 
 

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] Bluez and Obex daemon

2019-05-14 Thread Cliff McDiarmid via blfs-support
>Sent: Tuesday, May 14, 2019 at 6:30 PM
>From: "Grover 92000 via blfs-support" 
>To: "BLFS Support List" 
>Cc: "Grover 92000" 
>Subject: Re: [blfs-support] Bluez and Obex daemon

>On 12.5.2019. 19:17, Cliff McDiarmid via blfs-support wrote:
> Hi
>
> Can anyone help here?   I have previously installed Bluez for my Bluetooth 
> device and everything has worked in my LFS box.
>
> This time, in a new LFS, the obex daemon is not being loaded when I try to to 
> transfer data/pictures from phone to laptop.
>
> I have a pairing, trusted and connection, but cannot transfer.   I have 
> followed the BLFS book.
>
> 'systemctl --global is-enabled obex' - gives 'enabled'
>
> journalctl -u obexd - nothing
>
> journalctl | grep obexd - nothing
>
>
> My other LFS box gives:
>
> May 11 22:09:44 cliffhangers obexd[5690]: CONNECT(0x0), (null)(0x)
> May 11 22:09:44 cliffhangers obexd[5690]: CONNECT(0x0), (null)(0x0)
> May 11 22:09:45 cliffhangers obexd[5690]: PUT(0x2), (null)(0x)
> May 11 22:09:45 cliffhangers obexd[5690]: PUT(0x2), CONTINUE(0x10)
>
> when 'journalctl -u obexd' is run

>In one system you use -u, in other you use.  Switch obex from
>global to user service and you'll be good to go

>Thanks Armin, but sorry, I don't understand.  --global was used to start the 
>daemon.  -u was used to look at the journal for errors.

>systemctl disable obexd
>systemctl enable -u --now obexd

>Anyway.  I disabled the daemon globally and have tried to enable it for a user 
>but

>'systemctl enable -u --now obexd' gives: systemctl: invalid option -- 'u'

>'systemctl enable --now obexd' gives: Failed to enable unit: Unit file 
>obexd.service does not exist.

>'systemctl enable --user obex' gives: Failed to connect to bus: Operation not 
>permitted.  This could be my problem. A dbus problem, not present on other 
>system.
 
>It sounds like /etc/X11/xinit/xinitrc.d/50-systemd-user.sh isn't getting 
>sourced when you login.
>I had a similar problem when I switched to lightdm.
>When I was using lxdm I didn't have the problem. What desktop manager are you 
>using?

Thanks for that. I'm using GDM. And it's same on the previous system where 
Bluetooth is working, so how is 50-systemd-user.sh being sourced
assuming this is the problem?  
 
'systemctl enable --user obex' does work from a user environment, but makes no 
difference to my problem.
 
Cliff
 
 
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] Bluez and Obex daemon

2019-05-13 Thread Cliff McDiarmid via blfs-support
>Sent: Monday, May 13, 2019 at 5:06 AM
>From: "Armin K. via blfs-support" 
>To: blfs-support@lists.linuxfromscratch.org
>Cc: "Armin K." 
>Subject: Re: [blfs-support] Bluez and Obex daemon
>On 12.5.2019. 19:17, Cliff McDiarmid via blfs-support wrote:
> Hi
>
> Can anyone help here?   I have previously installed Bluez for my Bluetooth 
> device and everything has worked in my LFS box.
>
> This time, in a new LFS, the obex daemon is not being loaded when I try to to 
> transfer data/pictures from phone to laptop.
>
> I have a pairing, trusted and connection, but cannot transfer.   I have 
> followed the BLFS book.
>
> 'systemctl --global is-enabled obex' - gives 'enabled'
>
> journalctl -u obexd - nothing
>
> journalctl | grep obexd - nothing
>
>
> My other LFS box gives:
>
> May 11 22:09:44 cliffhangers obexd[5690]: CONNECT(0x0), (null)(0x)
> May 11 22:09:44 cliffhangers obexd[5690]: CONNECT(0x0), (null)(0x0)
> May 11 22:09:45 cliffhangers obexd[5690]: PUT(0x2), (null)(0x)
> May 11 22:09:45 cliffhangers obexd[5690]: PUT(0x2), CONTINUE(0x10)
>
> when 'journalctl -u obexd' is run

>In one system you use -u, in other you use.  Switch obex from
>global to user service and you'll be good to go

Thanks Armin, but sorry, I don't understand.  --global was used to start the 
daemon.  -u was used to look at the journal for errors.

>systemctl disable obexd
>systemctl enable -u --now obexd

Anyway.  I disabled the daemon globally and have tried to enable it for a user 
but

'systemctl enable -u --now obexd' gives: systemctl: invalid option -- 'u'

'systemctl enable --now obexd' gives: Failed to enable unit: Unit file 
obexd.service does not exist.

'systemctl enable --user obex' gives: Failed to connect to bus: Operation not 
permitted.  This could be my problem. A dbus problem, not present on other 
system.

Cliff


-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Bluez and Obex daemon

2019-05-12 Thread Cliff McDiarmid via blfs-support
Hi
 
Can anyone help here?   I have previously installed Bluez for my Bluetooth 
device and everything has worked in my LFS box.
 
This time, in a new LFS, the obex daemon is not being loaded when I try to to 
transfer data/pictures from phone to laptop.
 
I have a pairing, trusted and connection, but cannot transfer.   I have 
followed the BLFS book.
 
'systemctl --global is-enabled obex' - gives 'enabled'
 
journalctl -u obexd - nothing
 
journalctl | grep obexd - nothing
 
 
My other LFS box gives:
 
May 11 22:09:44 cliffhangers obexd[5690]: CONNECT(0x0), (null)(0x)
May 11 22:09:44 cliffhangers obexd[5690]: CONNECT(0x0), (null)(0x0)
May 11 22:09:45 cliffhangers obexd[5690]: PUT(0x2), (null)(0x)
May 11 22:09:45 cliffhangers obexd[5690]: PUT(0x2), CONTINUE(0x10)
 
when 'journalctl -u obexd' is run
 
Any ideas on this one?
 
thanks Cliff
 
 
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] GDM debugging ouput

2019-03-31 Thread Cliff McDiarmid via blfs-support
On 3/26/2019 5:17 PM, Cliff McDiarmid via blfs-support wrote:

> Hi I've got an new LFS that I can't start at the moment because of a fault 
> with GDM. I get a blank screen, where the only way out is with 
> Ctrl-Alt-delete.
>> Apparently one can turn debugging on through the the 'config' file. I've 
>> tried this and get nothing. How do I get logging working? Or is it the 
>> journal only?>> thanks>


>I'm not using systemd-jouranld at the moment, so I can't answer your
>question directly. Looks like daemon/gdm-launch-environment.c doesn't
>guard the greeter logging with systemd ifdefs, so probably does the
>logging itself in /var/log/gdm/greeter.log. I could be wrong on that, I
>only looked briefly, but I might be able to assist with the problem
>itself. A blank screen implies that we are not able to create a display.
>Make certain that you've built systemd with all of the recommended deps
>in BLFS, that you've updated the Linux PAM files at the end of the
>systemd page in BLFS, and double check that you've built Cairo with the
>additional flag --enable-gl (required for Wayland). If you've omitted
>>that flag, I'm not absolutely certain, but I think you'll also need to
>rebuild mutter, gnome-session, and gdm (so that "wayland" is a valid
>value for XDG_SESSION_TYPE).

Thanks.  I ended up rebuilding gnome-shell and subsequently 
/etc/pam.d/systemd-user, which wasn't right from the first build.

I can now boot into gnome from the command line using ~/.xinitrc.  GDM has yet 
to be tested.

Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] GDM debugging ouput

2019-03-27 Thread Cliff McDiarmid via blfs-support

On 3/26/2019 5:17 PM, Cliff McDiarmid via blfs-support wrote:
> Hi
>
> I've got an new LFS that I can't start at the moment because of a fault with GDM.  I get a blank screen, where the only way out is with Ctrl-Alt-delete.
>
> Apparently one can turn debugging on through the the 'config' file.  I've tried this and get nothing.  How do I get logging working?  Or is it the journal only?
>
> thanks
>

>I'm not using systemd-jouranld at the moment, so I can't answer your
>question directly. Looks like daemon/gdm-launch-environment.c doesn't
>guard the greeter logging with systemd ifdefs, so probably does the
>logging itself in /var/log/gdm/greeter.log. I could be wrong on that, I
>only looked briefly, but I might be able to assist with the problem
>itself. A blank screen implies that we are not able to create a display.
>Make certain that you've built systemd with all of the recommended deps
>in BLFS, that you've updated the Linux PAM files at the end of the
>systemd page in BLFS, and double check that you've built Cairo with the
>additional flag --enable-gl (required for Wayland). If you've omitted
>that flag, I'm not absolutely certain, but I think you'll also need to
>rebuild mutter, gnome-session, and gdm (so that "wayland" is a valid
>value for XDG_SESSION_TYPE).

 

Thanks I'm recompiling Cairo.  One thing.   I can only get it to compile with static libraries!  Is that a problem?

 

I get the following error:

 


/usr/lib/liblzo2.a(lzo2a_9x.o): relocation R_X86_64_PC32 against symbol `memset@@GLIBC_2.2.5' can not be used when making a shared object; recompile with -fPIC

 

 

thanks

 

Cliff


 

 

 

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] GDM debugging ouput

2019-03-26 Thread Cliff McDiarmid via blfs-support
Hi

I've got an new LFS that I can't start at the moment because of a fault with 
GDM.  I get a blank screen, where the only way out is with Ctrl-Alt-delete.

Apparently one can turn debugging on through the the 'config' file.  I've tried 
this and get nothing.  How do I get logging working?  Or is it the journal only?

thanks

Cliff 
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] MiniBrowser question

2019-02-23 Thread Cliff McDiarmid via blfs-support

On 2/23/19 7:40 AM, Cliff McDiarmid via blfs-support wrote:
> Hi>> The MiniBrowser that is part of WebKitGTK+.  Silly question maybe.  

Can you save websites with this browser?  I can't see how.


>I don't think you can. You can try Ctrl+S if you want, but last time I 
>checked, MiniBrowser's got no such functionality.

Thanks.  I thought I was missing something.

Cliff 
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] MiniBrowser question

2019-02-23 Thread Cliff McDiarmid via blfs-support
Hi
 
The MiniBrowser that is part of WebKitGTK+.  Silly question maybe.  Can you 
save websites with this browser?  I can't see how.
 
thanks
 
Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] twm menu not working

2019-02-09 Thread Cliff McDiarmid via blfs-support

 
 

Sent: Saturday, February 09, 2019 at 5:33 PM
From: "Ken Moffat via blfs-support" 
To: "BLFS Support List" 
Cc: "Ken Moffat" 
Subject: Re: [blfs-support] twm menu not working
On Sat, Feb 09, 2019 at 12:57:34PM +0100, Cliff McDiarmid via blfs-support 
wrote:
> Sent: Saturday, February 09, 2019 at 1:08 AM
> From: "Ken Moffat via blfs-support" 
> To: "BLFS Support List" 
> Cc: "Ken Moffat" 
> Subject: Re: [blfs-support] twm menu not working
> On Sat, Feb 09, 2019 at 01:09:11AM +0100, Cliff McDiarmid via blfs-support 
> wrote:
> > >To be clear : the mouse pointer works, but you cannot click on a
> > >window's title bar and drag it, and left or right clicks do nothing
> > >(in contexts where you expect something to happen) ?
> >  
> > Correct
> >
>
> >At the risk of being rude, can you look again at your Xorg log ?
>
> No carry on let's get this solved.
>
> > >Are you using libinput or evdev ?
> >  
> > Libinput
> >
> > >Related question : does the keyboard work, and if so, which driver
> > >did you specify for that ? (I use a British keyboard with a couple
> > >of mappings so I have to use a conf file for it, perhaps people
> > >using the default US keymap do not need a conf file).
> >
> > Yes works fine.. Looks like Libinput is handling it
> >
> > >At the risk of spreading confusion, what does it say about mouse or
> > >Mouse or MOUSE in the X log ?
>
> This looks like it:
>
> 602.981] (II) event4 - Video Bus: is tagged by udev as: Keyboard
> [ 602.981] (II) event4 - Video Bus: device is a keyboard
> [ 602.981] (II) event4 - Video Bus: device removed
> [ 603.002] (**) Option "config_info" 
> "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:01/input/input4/event4"
> [ 603.002] (II) XINPUT: Adding extended input device "Video Bus" (type: 
> KEYBOARD, id 8)
> [ 603.002] (II) event4 - Video Bus: is tagged by udev as: Keyboard
> [ 603.002] (II) event4 - Video Bus: device is a keyboard
> [ 603.002] (II) config/udev: Adding input device Lid Switch 
> (/dev/input/event0)
> [ 603.002] (II) No input driver specified, ignoring this device.
> [ 603.002] (II) This device may have been added with another device file.
> [ 603.003] (II) config/udev: Adding input device Power Button 
> (/dev/input/event1)
> [ 603.003] (**) Power Button: Applying InputClass "evdev keyboard catchall"
> [ 603.003] (**) Power Button: Applying InputClass "libinput keyboard catchall"
> [ 603.003] (II) Using input driver 'libinput' for 'Power Button'
> [ 603.003] (**) Power Button: always reports core events
> [ 603.003] (**) Option "Device" "/dev/input/event1"
> [ 603.003] (**) Option "_source" "server/udev"
> [ 603.003] (II) event1 - Power Button: is tagged by udev as: Keyboard
> [ 603.003] (II) event1 - Power Button: device is a keyboard
> [ 603.003] (II) event1 - Power Button: device removed
> [ 603.019] (**) Option "config_info" 
> "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
> [ 603.019] (II) XINPUT: Adding extended input device "Power Button" (type: 
> KEYBOARD, id 9)
> [ 603.019] (II) event1 - Power Button: is tagged by udev as: Keyboard
> [ 603.019] (II) event1 - Power Button: device is a keyboard
> [ 603.020] (II) config/udev: Adding input device Logitech M325 
> (/dev/input/event10)
> [ 603.020] (**) Logitech M325: Applying InputClass "evdev pointer catchall"
> [ 603.020] (**) Logitech M325: Applying InputClass "libinput pointer catchall"
> [ 603.020] (II) Using input driver 'libinput' for 'Logitech M325'
> [ 603.020] (**) Logitech M325: always reports core events
> [ 603.020] (**) Option "Device" "/dev/input/event10"
> [ 603.020] (**) Option "_source" "server/udev"
> [ 603.020] (II) event10 - Logitech M325: is tagged by udev as: Mouse
> [ 603.020] (II) event10 - Logitech M325: device set to 600 DPI
> [ 603.020] (II) event10 - Logitech M325: device is a pointer
> [ 603.020] (II) event10 - Logitech M325: device removed
> [ 603.044] (**) Option "config_info" 
> "udev:/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.2/0003:046D:C52B.0003/0003:046D:400A.0004/input/input12/event10"
> [ 603.044] (II) XINPUT: Adding extended input device "Logitech M325" (type: 
> MOUSE, id 10)
> [ 603.044] (**) Option "AccelerationScheme" "none"
> [ 603.044] (**) Logitech M325: (accel) selected scheme none/0
> [ 603.044] (**) Logitech

Re: [blfs-support] twm menu not working(SOLVED)

2019-02-09 Thread Cliff McDiarmid via blfs-support
Sent: Saturday, February 09, 2019 at 5:34 PM
From: "Douglas R. Reno via blfs-support" 

To: blfs-support@lists.linuxfromscratch.org
Cc: "Douglas R. Reno" 
Subject: Re: [blfs-support] twm menu not working

>On 2/8/19 9:37 AM, Cliff McDiarmid via blfs-support wrote:
 
>I'm building a new LFS.  I've got to the Xorg testing and I'm booting into the 
>three windows and clock.   

>I haven't got a left click twm menu though.  So i can't move the windwos etc.  
> 
 
>Have googled this problem with no luck.   Any ideas?
 
>Can you try installing the fonts in the Xorg Legacy Fonts page? I remember a 
>report similar to this last year that was solved by doing that.
>If so, I'll go update the book for it at my next commit.
>Thank you!

Yes that's it Douglas.  I had avoided the legacy fonts, not thinking they would 
effect TWM.

many thanks

Cliff

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] twm menu not working

2019-02-09 Thread Cliff McDiarmid via blfs-support
Sent: Saturday, February 09, 2019 at 1:08 AM
From: "Ken Moffat via blfs-support" 
To: "BLFS Support List" 
Cc: "Ken Moffat" 
Subject: Re: [blfs-support] twm menu not working
On Sat, Feb 09, 2019 at 01:09:11AM +0100, Cliff McDiarmid via blfs-support 
wrote:
> >To be clear : the mouse pointer works, but you cannot click on a
> >window's title bar and drag it, and left or right clicks do nothing
> >(in contexts where you expect something to happen) ?
>  
> Correct
>

>At the risk of being rude, can you look again at your Xorg log ?

No carry on let's get this solved.

> >Are you using libinput or evdev ?
>  
> Libinput
>
> >Related question : does the keyboard work, and if so, which driver
> >did you specify for that ? (I use a British keyboard with a couple
> >of mappings so I have to use a conf file for it, perhaps people
> >using the default US keymap do not need a conf file).
>
> Yes works fine.. Looks like Libinput is handling it
>
> >At the risk of spreading confusion, what does it say about mouse or
> >Mouse or MOUSE in the X log ?

This looks like it:

   602.981] (II) event4  - Video Bus: is tagged by udev as: Keyboard
[   602.981] (II) event4  - Video Bus: device is a keyboard
[   602.981] (II) event4  - Video Bus: device removed
[   603.002] (**) Option "config_info" 
"udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:01/input/input4/event4"
[   603.002] (II) XINPUT: Adding extended input device "Video Bus" (type: 
KEYBOARD, id 8)
[   603.002] (II) event4  - Video Bus: is tagged by udev as: Keyboard
[   603.002] (II) event4  - Video Bus: device is a keyboard
[   603.002] (II) config/udev: Adding input device Lid Switch 
(/dev/input/event0)
[   603.002] (II) No input driver specified, ignoring this device.
[   603.002] (II) This device may have been added with another device file.
[   603.003] (II) config/udev: Adding input device Power Button 
(/dev/input/event1)
[   603.003] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   603.003] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[   603.003] (II) Using input driver 'libinput' for 'Power Button'
[   603.003] (**) Power Button: always reports core events
[   603.003] (**) Option "Device" "/dev/input/event1"
[   603.003] (**) Option "_source" "server/udev"
[   603.003] (II) event1  - Power Button: is tagged by udev as: Keyboard
[   603.003] (II) event1  - Power Button: device is a keyboard
[   603.003] (II) event1  - Power Button: device removed
[   603.019] (**) Option "config_info" 
"udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[   603.019] (II) XINPUT: Adding extended input device "Power Button" (type: 
KEYBOARD, id 9)
[   603.019] (II) event1  - Power Button: is tagged by udev as: Keyboard
[   603.019] (II) event1  - Power Button: device is a keyboard
[   603.020] (II) config/udev: Adding input device Logitech M325 
(/dev/input/event10)
[   603.020] (**) Logitech M325: Applying InputClass "evdev pointer catchall"
[   603.020] (**) Logitech M325: Applying InputClass "libinput pointer catchall"
[   603.020] (II) Using input driver 'libinput' for 'Logitech M325'
[   603.020] (**) Logitech M325: always reports core events
[   603.020] (**) Option "Device" "/dev/input/event10"
[   603.020] (**) Option "_source" "server/udev"
[   603.020] (II) event10 - Logitech M325: is tagged by udev as: Mouse
[   603.020] (II) event10 - Logitech M325: device set to 600 DPI
[   603.020] (II) event10 - Logitech M325: device is a pointer
[   603.020] (II) event10 - Logitech M325: device removed
[   603.044] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.2/0003:046D:C52B.0003/0003:046D:400A.0004/input/input12/event10"
[   603.044] (II) XINPUT: Adding extended input device "Logitech M325" (type: 
MOUSE, id 10)
[   603.044] (**) Option "AccelerationScheme" "none"
[   603.044] (**) Logitech M325: (accel) selected scheme none/0
[   603.044] (**) Logitech M325: (accel) acceleration factor: 2.000
[   603.044] (**) Logitech M325: (accel) acceleration threshold: 4
[   603.044] (II) event10 - Logitech M325: is tagged by udev as: Mouse
[   603.044] (II) event10 - Logitech M325: device set to 600 DPI
[   603.044] (II) event10 - Logitech M325: device is a pointer
[   603.045] (II) config/udev: Adding input device Logitech M325 
(/dev/input/mouse0)
[   603.045] (II) No input driver specified, ignoring this device.
[   603.045] (II) This device may have been added with another device file.
[   603.045] (II) config/udev: Adding input device Integrated_Webcam_FHD: 
Integrat (/dev/input/event12)




Thanks Ken

Cliff


-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] twm menu not working

2019-02-08 Thread Cliff McDiarmid via blfs-support

>On Fri, Feb 08, 2019 at 10:48:04PM +0100, Cliff McDiarmid via blfs-support 
>wrote:
> > lHi
> > I'm building a new LFS.  I've got to the Xorg testing and I'm booting
> > into the three windows and clock.   I haven't got a left click twm menu
> > though.  So i can't move the windwos etc.
> > Have googled this problem with no luck.   Any ideas?
>
> >What input drivers did you install?
>
> All of them
>
> >Check /var/log/Xorg.0.log for error messages.
>
> None
>
> thanks cliff
>To be clear : the mouse pointer works, but you cannot click on a
>window's title bar and drag it, and left or right clicks do nothing
>(in contexts where you expect something to happen) ?
 
Correct

>Are you using libinput or evdev ?
 
Libinput

>Related question : does the keyboard work, and if so, which driver
>did you specify for that ? (I use a British keyboard with a couple
>of mappings so I have to use a conf file for it, perhaps people
>using the default US keymap do not need a conf file).

Yes works fine.. Looks like Libinput is handling it

>At the risk of spreading confusion, what does it say about mouse or
>Mouse or MOUSE in the X log ?

Mouse is added at the beginning from /usr/share/X11/xorg.conf.d

>I put that qualification because after looking at one of my logs to
>see what it say, there were a *lot* of messages, some of the later
>messages implying it was ignored - in fact, the earlier messages
>were what mattered in that case. I think the noise in that case was
>because of the conf file from libinput.

Mine is the same a lot of early messages about ignoring.  But working 
nonetheless.

thanks

Cliff

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] twm menu not working

2019-02-08 Thread Cliff McDiarmid via blfs-support
>Sent: Friday, February 08, 2019 at 5:35 PM
>From: "Bruce Dubbs via blfs-support" 
>To: blfs-support@lists.linuxfromscratch.org
>Cc: "Bruce Dubbs" 
>Subject: Re: [blfs-support] twm menu not working
>On 02/08/2019 09:37 AM, Cliff McDiarmid via blfs-support wrote:
> lHi
> I'm building a new LFS.  I've got to the Xorg testing and I'm booting
> into the three windows and clock.   I haven't got a left click twm menu
> though.  So i can't move the windwos etc.
> Have googled this problem with no luck.   Any ideas?

>What input drivers did you install?

All of them

>Check /var/log/Xorg.0.log for error messages.

None

thanks cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] twm menu not working

2019-02-08 Thread Cliff McDiarmid via blfs-support
>Sent: Friday, February 08, 2019 at 4:33 PM
>From: "Pierre Labastie via blfs-support" 
>
>To: blfs-support@lists.linuxfromscratch.org
>Cc: "Pierre Labastie" 
>Subject: Re: [blfs-support] twm menu not working
>On 08/02/2019 16:37, Cliff McDiarmid via blfs-support wrote:
> lHi
>  
> I'm building a new LFS.  I've got to the Xorg testing and I'm booting into the
> three windows and clock.   I haven't got a left click twm menu though.  So i
> can't move the windwos etc.   
>  
> Have googled this problem with no luck.   Any ideas?
 

>Not sure exactly what is your problem

I have three windows and a clock as say.  But i cannot move them or resize as i 
have no twm menu which is usually there by left click.  I have nothing - left 
or right click.


Do the windows have "decoration"

yes fine 


>(toolbar, a thin frame around them, etc). If not, it may be that twm did not
>start. I've seen that sometimes: the reason is that twm needs xorg-legacy 
>fonts...

>If it is something else, you may want to type alt-ctrl-f1, to look at any
>error message

No error messages

thanks Cliff

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] twm menu not working

2019-02-08 Thread Cliff McDiarmid via blfs-support

>Sent: Friday, February 08, 2019 at 3:46 PM

>From: "Richard via blfs-support" 
>To: "Cliff McDiarmid via blfs-support" 
>
>Cc: Richard 
>Subject: Re: [blfs-support] twm menu not working

>On 02/08/2019 10:37 AM, Cliff McDiarmid via blfs-support wrote:

>Hi
 
>I'm building a new LFS.  I've got to the Xorg testing and I'm booting into the 
>three windows and clock.   I haven't got a left click twm menu though.  So i 
>can't move the windwos etc.   
 

>Have googled this problem with no luck.   Any ideas?
 
>thanksCliff   I use twm and on my system it is a right-click menu.
>But a left-click moves windows, as you said.

Thanks Richard, but i'm not getting any menus left OR right click.   I'm stuck 
with overlapping windows and can't move them!

Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] twm menu not working

2019-02-08 Thread Cliff McDiarmid via blfs-support
lHi
 

I'm building a new LFS.  I've got to the Xorg testing and I'm booting into the three windows and clock.   I haven't got a left click twm menu though.  So i can't move the windwos etc.   

 


Have googled this problem with no luck.   Any ideas?

 

thanks
Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Openvpn client failing at startup

2018-12-09 Thread Cliff McDiarmid via blfs-support
On 12/9/2018 11:52 AM, Cliff McDiarmid via blfs-support wrote:
> Hi   I know VPN is not covered in BLFS, but I'm hoping someone can
> help here.   This appears a systemd problem with chroot?  I don't
> understand.   When starting the service file for the openvpn client I
> get:   

>Do you need to chroot in your VPN config? 

Not that I'm aware of. E.g.

remote uk-man.privatevpn.com 1194 udp
nobind
dev tun

# Options
tun-ipv6
remote-cert-tls server
client
comp-lzo
persist-key
persist-tun
verb 3

# Crypto
cipher AES-128-GCM
auth SHA256
auth-user-pass

>Does the same conf work when started manually? 

Yes, E.g. openvpn --config PrivatVPN-UK-Manchester-TUN-1194.ovpn


>This is an openvpn-client error, so probably need to
>examine the client log. 

>systemd is only reporting the error that the
>client throws.

Ok.  Will go on the look.  Not in usual place.

Thanks

Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] Openvpn client failing at startup

2018-12-09 Thread Cliff McDiarmid via blfs-support

Hi
 
I know VPN is not covered in BLFS, but I'm hoping someone can help here.
 
This appears a systemd problem with chroot?  I don't understand.
 
When starting the service file for the openvpn client I get:
 

● openvpn-client@service.service - OpenVPN tunnel for service
   Loaded: loaded (/lib/systemd/system/openvpn-client@.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Sun 2018-12-09 16:55:10 GMT; 4s ago
 Docs: man:openvpn(8)
   https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage
   https://community.openvpn.net/openvpn/wiki/HOWTO
  Process: 6204 ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind 
--config %i.conf (code=exited, status=210/C
 Main PID: 6204 (code=exited, status=210/CHROOT)
Dec 09 16:55:10 cliffhangers systemd[1]: Starting OpenVPN tunnel for service...
Dec 09 16:55:10 cliffhangers systemd[6204]: openvpn-client@service.service: 
Failed at step CHROOT spawning /usr/sbin/o
Dec 09 16:55:10 cliffhangers systemd[1]: openvpn-client@service.service: Main 
process exited, code=exited, status=210/
Dec 09 16:55:10 cliffhangers systemd[1]: Failed to start OpenVPN tunnel for 
service.
Dec 09 16:55:10 cliffhangers systemd[1]: openvpn-client@service.service: Unit 
entered failed state.
Dec 09 16:55:10 cliffhangers systemd[1]: openvpn-client@service.service: Failed 
with result 'exit-code'

Thanks 

Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] GPM not working on Thinkpad

2018-09-25 Thread Cliff McDiarmid via blfs-support
Sent: Tuesday, September 25, 2018 at 5:35 AM
From: "DJ Lucas via blfs-support" 
To: "BLFS Support List" 
Cc: "DJ Lucas" 
Subject: Re: [blfs-support] GPM not working on Thinkpad

On 09/21/2018 03:38 AM, Cliff McDiarmid via blfs-support wrote:
> Hi
>
> I've tried all the settings it seems and googled this problem, but I can't 
> get the cut and paste function working in a console on an old Thinkpad using 
> the touchpad.  Can anyone help here?
>
> cat /proc/bus/input/devices gives:
>
> I: Bus=0011 Vendor=0002 Product=0007 Version=2cb1
> N: Name="SynPS/2 Synaptics TouchPad"
> P: Phys=isa0060/serio1/input0
> S: Sysfs=/devices/platform/i8042/serio1/input/input6
> U: Uniq=
> H: Handlers=mouse0 event5
> B: PROP=1
> B: EV=b
> B: KEY=6420 0 3 0 0 0 0 0 0 0 0
> B: ABS=1103
>
> So my /etc/systemd/system/gpm.service.d/99-user.conf reads:
>
> ExecStart=/usr/sbin/gpm -m /dev/input/mouse0 -t imps2 - or
>
> ExecStart=/usr/sbin/gpm -m /dev/input/mouse0 - or
>
> ExecStart=/usr/sbin/gpm -m /dev/input/event5


>If there are physical buttons, it should simply be a two button paste.
>If it's one of those new fangdangled ones where there is no physical
>buttons, you can try -t synps2. Can also try different finger
>combinations with the imps2 type. Also, how about -m /dev/input/mice?
>Failing those, maybe emulation is dependent on gestures in the hardware,
>maybe try a two finger click/double tap (make sure there is a gap).
>After that, I'm out of ideas. Please let us know if any of the above
>helps as it will likely help somebody else as well.

Right I have it now.  I have gone over to the libinput system that Gnome and 
others are using, that handles all events.  Albeit with slightly less control.  
The synaptic driver has gone.  I now have cut and paste using the left touch 
button to select and then paste with both buttons together.  The touchpad is on 
the old T40.

many thanks

Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] GPM not working on Thinkpad

2018-09-22 Thread Cliff McDiarmid via blfs-support
Hi

I'll rephrase this question

Does anyone out there using LFS with a Synaptics trackpad have the cut and 
paste facility of GPM working on that trackpad?

If so, what does the configuration file look like for GPM?

thanks

Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] GPM not working on Thinkpad

2018-09-21 Thread Cliff McDiarmid via blfs-support
Sent: Friday, September 21, 2018 at 3:50 PM
From: "Cliff McDiarmid" 
To: "martyn vidler" 
Subject: Re: [blfs-support] GPM not working on Thinkpad
Sent: Friday, September 21, 2018 at 1:05 PM
From: "martyn vidler" 
To: "BLFS Support List" 
Cc: "Cliff McDiarmid" 
Subject: Re: [blfs-support] GPM not working on Thinkpad

On 21 Sep 2018 11:14, "Cliff McDiarmid via blfs-support" 
mailto:blfs-support@lists.linuxfromscratch.org]>
 wrote:Hi

>>but I can't get the cut and paste function working in a console on an old 
>>Thinkpad using the touchpad.
>>I should add that this is only for the trackpad/touchpad. If I plug a mouse 
>>in I can cut and paste at will.

On Fri, 21 Sep 2018 11:31 martyn vidler, 
mailto:spiky0...@gmail.com]> wrote:
>>It's been awhile since i needed to use gpm, but it's a combonation of using a 
>>button as well. I think you put cursor at begining of text, hold a button 
>>(might be both) and drag cursor over text

>>Ok just tried it on a laptop, left mouse drag to copy, right mouse paste

Thanks Martyn, but I'm aware of how to cut and paste with GPM. The issue is 
with cutting and pasting from a TRACKPAD with GPM, which in this case won't 
work.
As I mentioned if I plug a mouse in then it's fine, I can cut and paste.

Cliff
 

 
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] GPM not working on Thinkpad

2018-09-21 Thread Cliff McDiarmid via blfs-support
 
 

Sent: Friday, September 21, 2018 at 3:50 PM
From: "Cliff McDiarmid" 
To: "martyn vidler" 
Subject: Re: [blfs-support] GPM not working on Thinkpad

Sent: Friday, September 21, 2018 at 1:05 PM
From: "martyn vidler" 
To: "BLFS Support List" 
Cc: "Cliff McDiarmid" 
Subject: Re: [blfs-support] GPM not working on Thinkpad

On 21 Sep 2018 11:14, "Cliff McDiarmid via blfs-support"  wrote:Hi

>>but I can't get the cut and paste function working in a console on an old Thinkpad using the touchpad.
>>I should add that this is only for the trackpad/touchpad. If I plug a mouse in I can cut and paste at will.

On Fri, 21 Sep 2018 11:31 martyn vidler,  wrote:
>>It's been awhile since i needed to use gpm, but it's a combonation of using a button as well. I think you put cursor at begining of text, hold a button (might be both) and drag cursor over text

>>Ok just tried it on a laptop, left mouse drag to copy, right mouse paste

Thanks Martyn, but I'm aware of how to cut and paste with GPM. The issue is with cutting and pasting from a TRACKPAD with GPM, which in this case won't work.
As I mentioned if I plug a mouse in then it's fine, I can cut and paste.

Cliff
 

 



-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] GPM not working on Thinkpad

2018-09-21 Thread Cliff McDiarmid via blfs-support
Hi

>>but I can't get the cut and paste function working in a console on an old 
>>Thinkpad using the touchpad.

I should add that this is only for the trackpad/touchpad.  If I plug a mouse in 
I can cut and paste at will.
 
thanks
 
Cliff
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-support] GPM not working on Thinkpad

2018-09-21 Thread Cliff McDiarmid via blfs-support
Hi
 
I've tried all the settings it seems and googled this problem, but I can't get 
the cut and paste function working in a console on an old Thinkpad using the 
touchpad.  Can anyone help here?
 
cat /proc/bus/input/devices gives:
 
I: Bus=0011 Vendor=0002 Product=0007 Version=2cb1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input6
U: Uniq=
H: Handlers=mouse0 event5
B: PROP=1
B: EV=b
B: KEY=6420 0 3 0 0 0 0 0 0 0 0
B: ABS=1103
 
So my /etc/systemd/system/gpm.service.d/99-user.conf reads:

ExecStart=/usr/sbin/gpm -m /dev/input/mouse0 -t imps2 - or

ExecStart=/usr/sbin/gpm -m /dev/input/mouse0 - or

ExecStart=/usr/sbin/gpm -m /dev/input/event5

Nothing works - any ideas?

thanks Cliff

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page