On Sat, Feb 09, 2019 at 03:56:18PM +0100, Gonzalo Pérez de Olaguer Córdoba
wrote:
> Hi KatolaZ.
>
> Just for curiosity, in case this has a simple and fast response,
> ¿Any idea why it didn't fail in rescue mode?
>
> I find it 'interesting', because AFAIK there should be no difference
> among run
On 2/9/19 4:00 PM, KatolaZ wrote:
> Just to confirm that eudev_3.2.7-6 is now in Beowulf (and in
> unstable). This should solve the issue. Please upgrade and report.
just replied to the bug that everything works as expected with newer
version.
reporting it here on the list as well.
thanks,
d.
Hi KatolaZ.
Just for curiosity, in case this has a simple and fast response,
¿Any idea why it didn't fail in rescue mode?
I find it 'interesting', because AFAIK there should be no difference
among runlevels in this case. ¿Or it should?
Thanks,
Salo.
El Sat, 9 Feb 2019 15:00:04 +0100
KatolaZ
On Sat, Feb 09, 2019 at 12:39:34PM +0100, KatolaZ wrote:
> >On Sat, Feb 09, 2019 at 01:23:11PM +0200, Dimitris via Dng wrote:
> > On 2/9/19 12:01 PM, KatolaZ wrote:
> > > What you seem to have in common is openrc (while I am on vanilla
> > > sysvinit). You should check that the udev/eudev service s
>On Sat, Feb 09, 2019 at 01:23:11PM +0200, Dimitris via Dng wrote:
> On 2/9/19 12:01 PM, KatolaZ wrote:
> > What you seem to have in common is openrc (while I am on vanilla
> > sysvinit). You should check that the udev/eudev service script is in
> > place and/or it is trying to run the correct thin
On 2/9/19 12:01 PM, KatolaZ wrote:
> What you seem to have in common is openrc (while I am on vanilla
> sysvinit). You should check that the udev/eudev service script is in
> place and/or it is trying to run the correct thing.
i think i found the problem. it's just a typo most probably.
line 5 i
On 09/02/19 at 03:00, Gonzalo Pérez de Olaguer Córdoba wrote:
>
> 'the screen' is not clear to me. I suspect it means something else that
> is not a screen, because screens are not in charge of responding to
> keyboards or mouses.
Of course they are. Their response to kb/mouse events is the ma
On Sat, Feb 09, 2019 at 01:40:16AM +0200, Dimitris via Dng wrote:
>
> > - init system
>
> openrc 0.40.3-1
>
What you seem to have in common is openrc (while I am on vanilla
sysvinit). You should check that the udev/eudev service script is in
place and/or it is trying to run the correct thing.
Hi Alessandro.
El Sat, 9 Feb 2019 00:40:41 +0100
Alessandro Selli escribió:
> On 09/02/19 at 00:13, Gonzalo Pérez de Olaguer Córdoba wrote:
> > Hi Alessandro.
> >
> > El Fri, 8 Feb 2019 21:53:44 +0100
> > Alessandro Selli escribió:
> >
> >> This afternoon I happened to be surprised I coul
On 2/9/19 1:08 AM, KatolaZ wrote:
> - DE
MATE fully upgraded (
1) only keep mate-power-manager pinned from hezeh.org/ascii due to bug
#240, and
2) mate-utils still in 1.20.1-1 (beowulf), due to unmet dependencies of
the debian package in merged -debian issue, check debian package page-.
> - sess
On 09/02/19 at 00:13, Gonzalo Pérez de Olaguer Córdoba wrote:
> Hi Alessandro.
>
> El Fri, 8 Feb 2019 21:53:44 +0100
> Alessandro Selli escribió:
>
>> This afternoon I happened to be surprised I could not use my
>> laptop's GUI because the screen was unresponsive to both keyboard and
>> mouse.
On 09/02/19 at 00:08, KatolaZ wrote:
> On Sat, Feb 09, 2019 at 12:38:06AM +0200, Dimitris via Dng wrote:
>> hey,
>>
>> On 2/8/19 10:53 PM, Alessandro Selli wrote:
>>> � I shut down the DM, started eudev manually and I could recover the GUI.
>>>
>> it was also reported in the forum today :
>> https:
On 2/9/19 1:13 AM, Gonzalo Pérez de Olaguer Córdoba wrote:
> In common situations there is no need to login from another PC.
> You can press Ctrl-Alt-F1 (handled by the kernel, not by the X system)
> to get a text console (Alt-F7 to go back to the graphics).
unforunately,
k/b is not responding to
Hi Alessandro.
El Fri, 8 Feb 2019 21:53:44 +0100
Alessandro Selli escribió:
> This afternoon I happened to be surprised I could not use my
> laptop's GUI because the screen was unresponsive to both keyboard and
> mouse. The laptop was not frozen though, a clock in the DM display was
> runni
On Sat, Feb 09, 2019 at 12:38:06AM +0200, Dimitris via Dng wrote:
> hey,
>
> On 2/8/19 10:53 PM, Alessandro Selli wrote:
> >
> > � I shut down the DM, started eudev manually and I could recover the GUI.
> >
>
> it was also reported in the forum today :
> https://dev1galaxy.org/viewtopic.php?id=
On 08/02/19 at 23:46, Alessandro Selli wrote:
>
> grep eudev /var/log/messages returned nothing, on /var/log/syslog I
> only got a few instances of:
>
> Feb 8 20:17:13 wkstn05 vmunix: [ 2.508284] udevd[213]: starting
> eudev-3.2.2
>
Sorry, this if from the second PC which does not show the i
grep eudev /var/log/messages returned nothing, on /var/log/syslog I only
got a few instances of:
Feb 8 20:17:13 wkstn05 vmunix: [ 2.508284] udevd[213]: starting
eudev-3.2.2
On 08/02/19 at 23:34, KatolaZ wrote:
> On Fri, Feb 08, 2019 at 09:53:44PM +0100, Alessandro Selli wrote:
>> Hello,
>>
hey,
On 2/8/19 10:53 PM, Alessandro Selli wrote:
>
> � I shut down the DM, started eudev manually and I could recover the GUI.
>
it was also reported in the forum today :
https://dev1galaxy.org/viewtopic.php?id=2653
and a bug report yesterday :
https://bugs.devuan.org//cgi/bugreport.cgi?bug=290
On Fri, Feb 08, 2019 at 09:53:44PM +0100, Alessandro Selli wrote:
> Hello,
>
> This afternoon I happened to be surprised I could not use my
> laptop's GUI because the screen was unresponsive to both keyboard and
> mouse. The laptop was not frozen though, a clock in the DM display was
> runn
Hello,
This afternoon I happened to be surprised I could not use my
laptop's GUI because the screen was unresponsive to both keyboard and
mouse. The laptop was not frozen though, a clock in the DM display was
running.
Logging-in from another PC I found out Xorg's log lacked any line
abou
20 matches
Mail list logo
