| === alex_c is now known as alexandros_c | ||
| === brainwash_ is now known as brainwash | ||
| ironhoof | This is likely a common question, I am using an HDMI output as a main monitor, the native resolution is 1360x768, have a few that can do it, but just this one machine tries and I get a response from the screen, unsupported resolution and or refresh rate. | 11:12 |
|---|---|---|
| ironhoof | How can I get around tihs? | 11:13 |
| ironhoof | this* | 11:13 |
| ironhoof | all are running xubuntu 20.04 | 11:14 |
| ironhoof | Would it be possible to compare files form the different machines and correct it? | 11:18 |
| ironhoof | from* | 11:18 |
| xu-help31w | I have a problem with the xfce panel. When I boot the panel is corrupted (wrong colors at places, right colors at places). I have to logout and login again in order to correct this... Does someone here know the phenomenon? | 13:54 |
| brainwash | xu-help31w: maybe a screenshot could help | 14:00 |
| brainwash | xu-help31w: restarting the panel (xfce4-panel -r) could work as workaround | 14:01 |
| xu-help31w | @brainwash https://postimg.cc/MvT531NH | 14:07 |
| brainwash | my guess is that xfce4-panel is somehow started before xfsettinsd (the process that applies theme settings) | 14:09 |
| xu-help31w | @brainwash xfce4-panel -r did the trick, but I would like to know what is causing it and how to get rid of the bug for goo... | 14:10 |
| brainwash | is it a restored session? | 14:10 |
| brainwash | or do you always start a clean session? | 14:10 |
| xu-help31w | what do you mean with restored session? | 14:10 |
| brainwash | a session that restores opened windows from the previous session | 14:11 |
| xu-help31w | if I get it right, it's only on new sessions. always at new start.. | 14:12 |
| xu-help31w | I nevere restore sessions | 14:12 |
| brainwash | do you have autologin enabled? | 14:12 |
| xu-help31w | no | 14:12 |
| brainwash | mmh | 14:12 |
| xu-help31w | but i have an ecrypted home partition on a separate drive... which I mounted post-installation... | 14:13 |
| brainwash | you could check the session log (~/.xsession-errors) for related messages | 14:13 |
| xu-help31w | and I have the impression that it has to do with it, only I can't figure out how... I am not htat savvy in these things | 14:13 |
| brainwash | possible | 14:14 |
| brainwash | to me it looks like some timing issue | 14:14 |
| brainwash | meaning that things are started in different order on startup | 14:14 |
| xu-help31w | HAT SHOULD i LOOK FOR? | 14:15 |
| xu-help31w | what | 14:15 |
| brainwash | error messages I guess | 14:15 |
| brainwash | warning messages can be probably ignored | 14:16 |
| brainwash | or share the content here | 14:16 |
| brainwash | note that, it may contain personal info | 14:17 |
| xu-help31w | I found this right at the start: | 14:17 |
| xu-help31w | (xfce4-session:2674): xfce4-session-WARNING **: 15:03:08.749: xfsm_manager_load_session: Something wrong with /home/oo/.cache/sessions/xfce4-session-noMacGo:0, Does it exist? Permissions issue? | 14:17 |
| brainwash | this indicates that it's indeed a clean session | 14:19 |
| xu-help31w | ok | 14:19 |
| xu-help31w | Here is the file: https://ufile.io/0kxo7hik | 14:26 |
| brainwash | xu-help31w: many Theme parsing error lines | 14:31 |
| xu-help31w | yeah, i see... what can i dop about it? | 14:32 |
| brainwash | well, I would check if the problem is present when using another theme | 14:33 |
| brainwash | Greybird or Adwaita | 14:33 |
| brainwash | those are usually well maintained | 14:34 |
| xu-help31w | you mean: change theme, reboot and check? | 14:34 |
| xu-help31w | and if it still happens? | 14:34 |
| brainwash | exactly | 14:35 |
| xu-help31w | didn't happen | 14:39 |
| xu-help31w | so it has to do with the theme, am I right? | 14:39 |
| brainwash | I think so | 14:39 |
| xu-help31w | hould I change the theme or can I fix this somehow? | 14:39 |
| brainwash | on top of that, I wouldn't want to use a theme that spams my log :) | 14:39 |
| brainwash | the log messages tell you what parts are broken | 14:40 |
| brainwash | maybe you can fix those, but ideally you should report them to the theme author | 14:40 |
| brainwash | assuming the theme is still maintained | 14:41 |
| xu-help31w | thanks a lothelpd a lot | 14:41 |
| xu-help31w | will look into that | 14:41 |
| brainwash | you're welcome | 14:41 |
| === alex_c is now known as alexandros_c | ||
| xu-help80w | Have been using Xubuntu for around 5 years now. Since upgrading to 20.04 LTS I run into problems regarding the screen saver. It appears to be disregarding when I disable it. I disabled it in first place as when e.g. using firefox to watch netflix, the screen would go blank and lock after 15min. Enabling "presentation mode" did not help, so I | 21:18 |
| xu-help80w | deactivated the screen saver. But even then, it still blank the screen after a while. Have seen this on two different laptops (Dell Latitude and Sony Vaio). Problem would not show up on the same Dell Latitude computer type using Ubuntu 20.04. | 21:18 |
| gnrp | xu-help80w: I guess it is a power saving setting? | 21:24 |
| gnrp | when you go to energy management (don't know the exact translation) in the settings, and then to display settings, does this correspond to the timeouts you experience? | 21:24 |
| Maik | yep, think so too^^ | 21:24 |
| xu-help80w | I had the same idea, it did correspond. Have changed the times there, no effect. Then I disabled it (as I wrote, it is disabled now). But it still turns off the screen. So annoying. | 21:26 |
| xu-help80w | I mean the window "Xfce Power Manager", tab "Display", "Display Power Management" button is disabled. | 21:27 |
| gnrp | xu-help80w: Could it be inactivity? | 21:45 |
| gnrp | ah, no, there you cannot do it | 21:45 |
| gnrp | I could also imagine you have a gpu driver doing that | 21:45 |
| gnrp | did you restart after changing that setting? | 21:45 |
| xu-help80w | I have found that activating display power management and setting the blank time to 1 minute, the screen would go blank after 1 min, that seems to work fine. Enabling "presentation mode" would disable going blank. | 21:47 |
| gnrp | I actually have no clue where these settings are applied, i.e., what controls those | 21:47 |
| gnrp | ah, ok | 21:48 |
| xu-help80w | But my problem is there seems to be another (a different) process making the screen go blank after 15 min. No idea why this is. This did not happen in 18.04 LTS | 21:48 |
| xu-help80w | I also found that using vlc to watch files and using its setting "disable screensaver" prevents the screen going blank. However, when watching netflix in firefox the screen goes blank after 15min, even when the "Display management" in the Xfce power manager is disabled. | 21:55 |
| lostogre | Hello. Is is possible to upgrade xununtu 18.04 to 20.04? I had read that it wasn't due to a change from xfce to lxde. | 22:57 |
| guiverc | lostogre, Xubuntu 18.04 & 20.04 are both XFCE.. Lubuntu switched from LXDE in 18.04 to LXQt in 18.10 & later, that change won't impact Xubuntu/XFCE users | 23:02 |
| lostogre | guiverc: Thanks. I appreciate it. | 23:02 |
| guiverc | the change within XFCE was from GTK2 to GTK3; that should be invisible to users (it was a great job by Xubuntu/XFCE devs!) | 23:02 |
| lostogre | guiverc: cool. | 23:03 |
| guiverc | fyi: the change to GTK3 does mean scaling & other things are now exist (Xfce 4.16).. 19.10/20.04 were more GTK3 switch.. many newer features found in groovy/hirsute... & subsequent b/c of GTK3 switch | 23:09 |
| lostogre | nice | 23:11 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!