=== brainwash_ is now known as brainwash
=== sm0rux is now known as Guest36486
=== sm0rux_ is now known as sm0rux
[13:02] <csanyipal> Hi,
[13:05] <csanyipal> after software update when login to XFCE4 Desktop and start Chromium browser I get a DialogBox with text: a system error occurred. Would you like to report a bug now? Report the error.. Cancel
[13:07] <csanyipal> What can I do to solve this problem?
[13:09] <tomreyn> you can choose to report the issue or to ignore it, that's all the options you have there for now.
[13:09] <tomreyn> you can also make sure you have the latest updates installed.
[13:09] <csanyipal> I am sure I have the latest updates installed.
[13:09] <tomreyn> if chromium browser doesn't start up properly, you can run it from a temrinal and see what it outputs
[13:10] <csanyipal> I will try that right away.
[13:12] <csanyipal> I started Chromium from a terminal and the dialog box does not appeares. I think it appeares when I login to Desktop only.
[13:16] <csanyipal> I am not sure if I can send the report in such a case. A similar error has already occurred with other apps, and when I chose to send the report, a short message shows up later that a report could not be sent.
[13:16] <csanyipal> It was something about dbus..
[13:17] <tomreyn> if the report can't be send it's either because this was previously reported or because there was a network issue communicating with daisy.ubuntu.com:443/tcp
[13:19] <csanyipal> tomreyn: Thank you very much for explanation.
[13:19] <tomreyn> you can also review your system journal for warnings and higher priority messages: journalctl -p4 -b
[13:20] <tomreyn> 5 would be just errors
[13:20] <csanyipal> How can I now verify if the network is reachable through 443 tcp port? I have Shorewall firewall installed here.
[13:20] <tomreyn> nc -vv daisy.ubuntu.com 443    # it will either immediately say that the connection was established, or not say anything and time out after a long time.
[13:21] <tomreyn> ctrl-c to cancel
[13:21] <csanyipal> Connection to daisy.ubuntu.com 443 port [tcp/https] succeeded!
[13:21] <csanyipal> Thanks!
[13:22] <csanyipal> tomreyn: Thanks!
[13:22] <tomreyn> so that's not why reports can't be sent. then it's probably that those have already been reported.
[13:22] <csanyipal> Yes, indeed.
[13:22] <tomreyn> reviewing your system logs *may* hin on what actually fails, as may looking at the /var/crash directory.
[13:23] <tomreyn> but onless you have this on every login i would not bother.
[13:24] <csanyipal> tomreyn: I will do as you advise. Have a nice day!
[13:24] <tomreyn> you, too!
[13:25] <csanyipal> Bye!
[13:37] <sublevel> That's a useful command to learn about,  journalctl -p4 -b. Thought I had a huge amount of errors until I realised the numbers go the other way -  it's 3 for errors, not 5 :-)
[13:40] <remline> Interesting, indeed. The man page lists "emerg" (0), "alert" (1), "crit" (2), "err" (3), "warning" (4), "notice" (5), "info" (6), "debug" (7).
[13:41] <tomreyn> oops, right sublevel, thanks for pointing this out.
[13:42] <remline> My log has many of these: "random: Cannot read from /dev/random: Resource temporarily unavailable"
[13:43] <remline> (In reference to wpa_supplicant)
=== sorinello1 is now known as sorinello
=== sorinello__ is now known as sorinello
=== sorinello1 is now known as sorinello
[20:24] <kumail> cant connect libre office to google. yes i have 2 step verificarion
[20:25] <kumail> can someone help
=== sorinello1 is now known as sorinello
[21:57] <Cloaca> what is best, xubuntu or manjaro ?
[22:09] <tomreyn> yes!
[22:10] <sublevel> no!
[22:10] <tomreyn> possibly maybe!
[22:12] <tomreyn> Cloaca: we believe you are the most qualified (and also the only qualified) person to decide this - for yourself.