Re: Keyboard not responding after exiting X

[Rodolfo Medina]

Brian  writes:

> On Mon 20 May 2019 at 21:29:44 +, Rodolfo Medina wrote:
>
>> Full-upgraded yesterday to Sid, it seems not technically possible to
>> downgrade now to Buster...
>
> I never said this was what you could do. The suggestion was to revert
> to systemd 241-3.

Yes, thanks...  But, as suggested here:

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929229


Am 19.05.19 um 21:13 schrieb S R Wright:
> Is this confined to systemd 241-4?  Will back-revving to 241-3 be a
> sufficient workaround?

It will. To satisfy dependencies, you'll need to downgrade libsystemd0
as well (and libpam-systemd, libnss-systemd, systemd-* in case you have
those installed)


it's a quite delicate issue...  After all, since I can shut off PC with
external button, I can survive with the problem until fixed...  rather than
facing such a delicate matter (so it seems to me to be).

Rodolfo

Re: Keyboard not responding after exiting X

[Brian]

On Mon 20 May 2019 at 21:29:44 +, Rodolfo Medina wrote:

> Full-upgraded yesterday to Sid, it seems not technically possible to downgrade
> now to Buster...

I never said this was what you could do. The suggestion was to revert
to systemd 241-3.

-- 
Brian.

Re: Keyboard not responding after exiting X

[Rodolfo Medina]

Brian  writes:

> On Mon 20 May 2019 at 14:50:25 +0400, Jerome BENOIT wrote:
>
>> On 20/05/2019 13:42, Rodolfo Medina wrote:
>> > Brian  writes:
>> > 
>> >> On Mon 20 May 2019 at 06:15:57 +, Rodolfo Medina wrote:
>> >>
>> >>> In order to have PDFtoMusic properly installed and work (see thread
>> >>> `PDFtoMusic installation') I had to do a full-upgrade to unstable.
>> >>> Everything is ok now except that, when logging out X (graphical
>> >>> environment, window manager), the keyboard is totally not responding so
>> >>> that I have to power off using the external button on the computer case.
>> >>> Anyone experimenting the same problem?  Please help whoever can.
>> >>
>> >> Bug #929229 and Bug #929250.
>> > 
>> > 
>> > Thanks, Brian.  So what should I do, waiting for them to be fixed and do a
>> > full-upgrade again in a few days/weeks/months...?
>> 
>> My understanding is that you play with the Sid distribution. This
>> distribution is unstable by nature, and its main purpose is to test
>> and check new packages.
>
> Indeed, and we should be grateful to Rodolfo Medina for his testing
> and reporting. It certainly made me think twice about upgrading to
> systemd 241-4.
>
>> You should rather consider to install Buster which by now can be can
>> considered quite stable.
>
> A good option I would say, if you want to get ahead of the game without
> too much hassle.


Full-upgraded yesterday to Sid, it seems not technically possible to downgrade
now to Buster...

Rodolfo

Re: Keyboard not responding after exiting X

[Brian]

On Mon 20 May 2019 at 14:15:18 -0400, Gene Heskett wrote:

> On Monday 20 May 2019 01:43:52 pm Brian wrote:
> 
> > On Mon 20 May 2019 at 10:39:39 -0400, Gene Heskett wrote:
> > > On Monday 20 May 2019 09:55:43 am Greg Wooledge wrote:
> > > > On Mon, May 20, 2019 at 09:51:35AM -0400, Gene Heskett wrote:
> > > > > Speaking of buster, which should be going public around 1 June,
> > > > > what will be the apt command line sequences to do the actual
> > > > > update to buster?
> > > >
> > > > The release notes are still being written, but:
> > > >
> > > > https://www.debian.org/releases/buster/amd64/release-notes/ch-upgr
> > > >adin g.en.html
> > >
> > > looks like it could be rough. Maybe I should get yet another drive
> > > and do a fresh install...  That way I'd have a fallback just by
> > > switching sata cables around.
> >
> > What is "rough" about
> >
> > 1. Alter sources.list
> > 2. apt update
> > 3. apt upgrde
> > 4. apt full-upgrade ?
> >
> > If it was any simpler, there would be complaints that upgrading from
> > one Debian version to another is too smooth. :)
> >
> > There is a school of thought which maintains that a reininstallation
> > is preferable to an upgrade when there is a new stable. You appear to
> > belong to this school, which is fine.
> 
> But there are probably 400+ additions to the stretch install 
> I did 2 weeks ago. For starters, trinity r14.0.6 has been installed.
> 
> What becomes of those?

That's *your* problem. trinity isn't part of Debian. As for the other 399+
additions; who knows where they came from.

Hvaing said that, I would expect Debian to cope with an idiosyncratic
installation to the best of its ability. But it cannot work wonders.
 
> Since it doesn't seem possible to sandbox jail N-M sufficiently 
> (and debian put dependencies back in it so it cannot be removed without 
> destroying the whole system) to keep it from tearing down a perfectly 
> working STATICly defined network and replaceing resolv.conf with only a 
> # comment, will the dist-upgrade just ignore the chattr +i's scattered 
> about or will it die as soon as its destroyed the network? Then my 
> fallback boot will be several generations old, with enough changes to 
> ext4 to make it dangerous to mount the new for repairs.
> 
> This is why I generally install on a new drive. Then I at least have a 
> working fallback install so I can email or browse for answers.

A new buster install is probably your best option.

-- 
Brian.

Re: Keyboard not responding after exiting X

[Gene Heskett]

On Monday 20 May 2019 01:43:52 pm Brian wrote:

> On Mon 20 May 2019 at 10:39:39 -0400, Gene Heskett wrote:
> > On Monday 20 May 2019 09:55:43 am Greg Wooledge wrote:
> > > On Mon, May 20, 2019 at 09:51:35AM -0400, Gene Heskett wrote:
> > > > Speaking of buster, which should be going public around 1 June,
> > > > what will be the apt command line sequences to do the actual
> > > > update to buster?
> > >
> > > The release notes are still being written, but:
> > >
> > > https://www.debian.org/releases/buster/amd64/release-notes/ch-upgr
> > >adin g.en.html
> >
> > looks like it could be rough. Maybe I should get yet another drive
> > and do a fresh install...  That way I'd have a fallback just by
> > switching sata cables around.
>
> What is "rough" about
>
> 1. Alter sources.list
> 2. apt update
> 3. apt upgrde
> 4. apt full-upgrade ?
>
> If it was any simpler, there would be complaints that upgrading from
> one Debian version to another is too smooth. :)
>
> There is a school of thought which maintains that a reininstallation
> is preferable to an upgrade when there is a new stable. You appear to
> belong to this school, which is fine.

But there are probably 400+ additions to the stretch install 
I did 2 weeks ago. For starters, trinity r14.0.6 has been installed.

What becomes of those?

Since it doesn't seem possible to sandbox jail N-M sufficiently 
(and debian put dependencies back in it so it cannot be removed without 
destroying the whole system) to keep it from tearing down a perfectly 
working STATICly defined network and replaceing resolv.conf with only a 
# comment, will the dist-upgrade just ignore the chattr +i's scattered 
about or will it die as soon as its destroyed the network? Then my 
fallback boot will be several generations old, with enough changes to 
ext4 to make it dangerous to mount the new for repairs.

This is why I generally install on a new drive. Then I at least have a 
working fallback install so I can email or browse for answers.

Thanks Brian.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Keyboard not responding after exiting X

[Brian]

On Mon 20 May 2019 at 10:39:39 -0400, Gene Heskett wrote:

> On Monday 20 May 2019 09:55:43 am Greg Wooledge wrote:
> 
> > On Mon, May 20, 2019 at 09:51:35AM -0400, Gene Heskett wrote:
> > > Speaking of buster, which should be going public around 1 June, what
> > > will be the apt command line sequences to do the actual update to
> > > buster?
> >
> > The release notes are still being written, but:
> >
> > https://www.debian.org/releases/buster/amd64/release-notes/ch-upgradin
> >g.en.html
> 
> looks like it could be rough. Maybe I should get yet another drive and do 
> a fresh install...  That way I'd have a fallback just by switching sata 
> cables around.

What is "rough" about

1. Alter sources.list
2. apt update
3. apt upgrde
4. apt full-upgrade ?

If it was any simpler, there would be complaints that upgrading from
one Debian version to another is too smooth. :)

There is a school of thought which maintains that a reininstallation
is preferable to an upgrade when there is a new stable. You appear to
belong to this school, which is fine.

-- 
Brian.

Re: Keyboard not responding after exiting X

[Gene Heskett]

On Monday 20 May 2019 09:55:43 am Greg Wooledge wrote:

> On Mon, May 20, 2019 at 09:51:35AM -0400, Gene Heskett wrote:
> > Speaking of buster, which should be going public around 1 June, what
> > will be the apt command line sequences to do the actual update to
> > buster?
>
> The release notes are still being written, but:
>
> https://www.debian.org/releases/buster/amd64/release-notes/ch-upgradin
>g.en.html

Thanks.

looks like it could be rough. Maybe I should get yet another drive and do 
a fresh install...  That way I'd have a fallback just by switching sata 
cables around.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Keyboard not responding after exiting X

[Brian]

On Mon 20 May 2019 at 09:51:35 -0400, Gene Heskett wrote:

> On Monday 20 May 2019 09:36:54 am Brian wrote:
> [...]
> > > You should rather consider to install Buster which by now can be can
> > > considered quite stable.
> >
> > A good option I would say, if you want to get ahead of the game
> > without too much hassle.
> 
> Speaking of buster, which should be going public around 1 June, what will 
> be the apt command line sequences to do the actual update to buster?

https://www.debian.org/releases/testing/i386/release-notes/

-- 
Brian.

Re: Keyboard not responding after exiting X

[Greg Wooledge]

On Mon, May 20, 2019 at 09:51:35AM -0400, Gene Heskett wrote:
> Speaking of buster, which should be going public around 1 June, what will 
> be the apt command line sequences to do the actual update to buster?

The release notes are still being written, but:

https://www.debian.org/releases/buster/amd64/release-notes/ch-upgrading.en.html

Re: Keyboard not responding after exiting X

[Gene Heskett]

On Monday 20 May 2019 09:36:54 am Brian wrote:
[...]
> > You should rather consider to install Buster which by now can be can
> > considered quite stable.
>
> A good option I would say, if you want to get ahead of the game
> without too much hassle.

Speaking of buster, which should be going public around 1 June, what will 
be the apt command line sequences to do the actual update to buster?

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Keyboard not responding after exiting X

[Brian]

On Mon 20 May 2019 at 14:50:25 +0400, Jerome BENOIT wrote:

> On 20/05/2019 13:42, Rodolfo Medina wrote:
> > Brian  writes:
> > 
> >> On Mon 20 May 2019 at 06:15:57 +, Rodolfo Medina wrote:
> >>
> >>> In order to have PDFtoMusic properly installed and work (see thread
> >>> `PDFtoMusic installation') I had to do a full-upgrade to unstable.
> >>> Everything is ok now except that, when logging out X (graphical 
> >>> environment,
> >>> window manager), the keyboard is totally not responding so that I have to
> >>> power off using the external button on the computer case.  Anyone
> >>> experimenting the same problem?  Please help whoever can.
> >>
> >> Bug #929229 and Bug #929250.
> > 
> > 
> > Thanks, Brian.  So what should I do, waiting for them to be fixed and do a
> > full-upgrade again in a few days/weeks/months...?
> 
> My understanding is that you play with the Sid distribution. This
> distribution is unstable by nature, and its main purpose is to test
> and check new packages.

Indeed, and we should be grateful to Rodolfo Medina for his testing
and reporting. It certainly made me think twice about upgrading to
systemd 241-4.

> You should rather consider to install Buster which by now can be can
> considered quite stable.

A good option I would say, if you want to get ahead of the game without
too much hassle.

-- 
Brian.

Re: Keyboard not responding after exiting X

[Jerome BENOIT]

On 20/05/2019 13:42, Rodolfo Medina wrote:
> Brian  writes:
> 
>> On Mon 20 May 2019 at 06:15:57 +, Rodolfo Medina wrote:
>>
>>> In order to have PDFtoMusic properly installed and work (see thread
>>> `PDFtoMusic installation') I had to do a full-upgrade to unstable.
>>> Everything is ok now except that, when logging out X (graphical environment,
>>> window manager), the keyboard is totally not responding so that I have to
>>> power off using the external button on the computer case.  Anyone
>>> experimenting the same problem?  Please help whoever can.
>>
>> Bug #929229 and Bug #929250.
> 
> 
> Thanks, Brian.  So what should I do, waiting for them to be fixed and do a
> full-upgrade again in a few days/weeks/months...?

My understanding is that you play with the Sid distribution. This distribution 
is unstable by nature,
and its main purpose is to test and check new packages.
You should rather consider to install Buster which by now can be can considered 
quite stable.

hth,
Jerome


> 
> Rodolfo
> 




signature.asc
Description: OpenPGP digital signature

Re: Keyboard not responding after exiting X

[Brian]

On Mon 20 May 2019 at 09:42:33 +, Rodolfo Medina wrote:

> Brian  writes:
> 
> > On Mon 20 May 2019 at 06:15:57 +, Rodolfo Medina wrote:
> >
> >> In order to have PDFtoMusic properly installed and work (see thread
> >> `PDFtoMusic installation') I had to do a full-upgrade to unstable.
> >> Everything is ok now except that, when logging out X (graphical 
> >> environment,
> >> window manager), the keyboard is totally not responding so that I have to
> >> power off using the external button on the computer case.  Anyone
> >> experimenting the same problem?  Please help whoever can.
> >
> > Bug #929229 and Bug #929250.
> 
> Thanks, Brian.  So what should I do, waiting for them to be fixed and do a
> full-upgrade again in a few days/weeks/months...?

Revert to 241-3, which is in testing? See advice in #929229.

-- 
Brian.

Re: Keyboard not responding after exiting X

[Rodolfo Medina]

Brian  writes:

> On Mon 20 May 2019 at 06:15:57 +, Rodolfo Medina wrote:
>
>> In order to have PDFtoMusic properly installed and work (see thread
>> `PDFtoMusic installation') I had to do a full-upgrade to unstable.
>> Everything is ok now except that, when logging out X (graphical environment,
>> window manager), the keyboard is totally not responding so that I have to
>> power off using the external button on the computer case.  Anyone
>> experimenting the same problem?  Please help whoever can.
>
> Bug #929229 and Bug #929250.


Thanks, Brian.  So what should I do, waiting for them to be fixed and do a
full-upgrade again in a few days/weeks/months...?

Rodolfo

Re: Keyboard not responding after exiting X

[Brian]

On Mon 20 May 2019 at 06:15:57 +, Rodolfo Medina wrote:

> In order to have PDFtoMusic properly installed and work (see thread 
> `PDFtoMusic
> installation') I had to do a full-upgrade to unstable.  Everything is ok now
> except that, when logging out X (graphical environment, window manager), the
> keyboard is totally not responding so that I have to power off using the
> external button on the computer case.  Anyone experimenting the same problem?
> Please help whoever can.

Bug #929229 and Bug #929250.

-- 
Brian.

Keyboard not responding after exiting X

[Rodolfo Medina]

Hi all.

In order to have PDFtoMusic properly installed and work (see thread `PDFtoMusic
installation') I had to do a full-upgrade to unstable.  Everything is ok now
except that, when logging out X (graphical environment, window manager), the
keyboard is totally not responding so that I have to power off using the
external button on the computer case.  Anyone experimenting the same problem?
Please help whoever can.

Thanks,

Rodolfo