[PLUG] Xubuntu 20.04 Install Issue

[Dick Steffens]

I am trying to install Xubuntu 20.04 on a Lenovo Ideapad 330. The base 
install worked fine. It asked me if I wanted to install updates. I said 
yes. It proceeded to do that for a lot of minutes (I was reading news on 
another computer, so I don't know exactly how long). At some point the 
screen went blank. I waited for another long bit of minutes and tried 
moving the mouse, thinking it might be a screen saver issue, but with no 
results. I can see the mouse pointer, but get no response to clicks. I 
powered down and back up. The screen shows the Lenovo splash image, then 
the xubuntu logo with the arc chasing around in a circle, then the list 
of journal recovery stuff, then a blank screen with the clock in the 
upper right hand corner, and then a blank screen with the mouse pointer.


Any ideas on where to start to look to solve this one?

--
Regards,

Dick Steffens

[PLUG] Can't print from Chromium

[John Jason Jordan]

The printer is a Brother HL-2280-DW connected as 192.168.1.25. I can
ping it, so the connection is good. I can print to it from any computer
and from any program except Chromium. When I print from Chromium I look
at the GUI print queue for the printer, and no print jobs appear. In
other words, the problem is that Chromium is not even sending the print
job. A print job appears in the queue when I print from anything else.

I've poked all over Chromium's settings looking for some permissions or
restrictions issue, but I can't find anything. And Chromium obviously
has no problem accessing the network. It's just printing that doesn't
work. And I mean that it won't print from any web page. If I copy the
URL of a Chromium web page and paste it into Firefox, then the page
prints fine. Why would Chromium refuse to print?

Re: [PLUG] Whitespace in Ubuntu 22.04 rsyslog.conf

[Paul Heinlein]

On Tue, 13 Sep 2022, Tomas Kuchta wrote:


On Tue, Sep 13, 2022, 13:34 Paul Heinlein  wrote:


Just an FYI:

At work, we use a puppet template to generate /etc/rsyslog.conf on all
our *nix machines. That template was failing on the first Ubuntu 22.04
host we tried to integrate with our puppet configs.

In short, certain directives that encountered two spaces between
directive and setting would fail, e.g.,

$FileOwner  syslog
$FileGroup  adm

Replacing the two spaces with a single space fixed the problem.

I scoured the changelogs but couldn't find evidence that this is an
intentional change.
.



Could this be UTF issue in rsyslog config parser/regexp?

I have been encountering strange invisible simple parsing issues recently.
If this is related, I usually resolve them by replacing [ \t] or \s or \S
with [[:space:]] patterns and it often helps.


I piped the offending lines through "od -a" and they were reported as 
standard "sp" spaces. If it's a UTF-8 issue, I can't see how I fixed 
it.


--
Paul Heinlein
heinl...@madboa.com
45°22'48" N, 122°35'36" W

Re: [PLUG] Whitespace in Ubuntu 22.04 rsyslog.conf

[Galen Seitz]

On 9/13/22 10:48, Tomas Kuchta wrote:

On Tue, Sep 13, 2022, 13:34 Paul Heinlein  wrote:


Just an FYI:

At work, we use a puppet template to generate /etc/rsyslog.conf on all
our *nix machines. That template was failing on the first Ubuntu 22.04
host we tried to integrate with our puppet configs.

In short, certain directives that encountered two spaces between
directive and setting would fail, e.g.,

$FileOwner  syslog
$FileGroup  adm

Replacing the two spaces with a single space fixed the problem.

I scoured the changelogs but couldn't find evidence that this is an
intentional change.
.



Could this be UTF issue in rsyslog config parser/regexp?

I have been encountering strange invisible simple parsing issues recently.
If this is related, I usually resolve them by replacing [ \t] or \s or \S
with [[:space:]] patterns and it often helps.

I wish to know a way of color coding ascii and unicode in text/logs to make
it visible what is one byte versus multi-byte characters. It will likely
get settled over time.



This will never be settled.




galen
--
Galen Seitz
gal...@seitzassoc.com

Re: [PLUG] Whitespace in Ubuntu 22.04 rsyslog.conf

[Tomas Kuchta]

On Tue, Sep 13, 2022, 13:34 Paul Heinlein  wrote:

> Just an FYI:
>
> At work, we use a puppet template to generate /etc/rsyslog.conf on all
> our *nix machines. That template was failing on the first Ubuntu 22.04
> host we tried to integrate with our puppet configs.
>
> In short, certain directives that encountered two spaces between
> directive and setting would fail, e.g.,
>
> $FileOwner  syslog
> $FileGroup  adm
>
> Replacing the two spaces with a single space fixed the problem.
>
> I scoured the changelogs but couldn't find evidence that this is an
> intentional change.
> .


Could this be UTF issue in rsyslog config parser/regexp?

I have been encountering strange invisible simple parsing issues recently.
If this is related, I usually resolve them by replacing [ \t] or \s or \S
with [[:space:]] patterns and it often helps.

I wish to know a way of color coding ascii and unicode in text/logs to make
it visible what is one byte versus multi-byte characters. It will likely
get settled over time.

Hope this helps, Tomas

>

[PLUG] Whitespace in Ubuntu 22.04 rsyslog.conf

[Paul Heinlein]

Just an FYI:

At work, we use a puppet template to generate /etc/rsyslog.conf on all 
our *nix machines. That template was failing on the first Ubuntu 22.04 
host we tried to integrate with our puppet configs.


In short, certain directives that encountered two spaces between 
directive and setting would fail, e.g.,


$FileOwner  syslog
$FileGroup  adm

Replacing the two spaces with a single space fixed the problem.

I scoured the changelogs but couldn't find evidence that this is an 
intentional change.


--
Paul Heinlein
heinl...@madboa.com
45°22'48" N, 122°35'36" W