[07:47] <glitchd> hello all
[07:47] <glitchd> has anyone had a problem with vlc in 18.04?
[07:55] <rud0lf> what kind of problem do you mean?
[07:55] <rud0lf> works fine to me
[07:58] <glitchd> the problem is, when you open it the ui is massively over-scaled. i figured out how to fix that problem, but now i cant play videos when right clicking and selecting play with vlc.
[07:58] <glitchd> it just spits out an error, but i can play the video if i open vlc directly and drag/drop the video file in the open vlc window.
[08:00] <glitchd> so what i did to fix the massivily over-sized ui was to rename /usr/bin/vlc to /usr/bin/vlcc, then writing a small script named vlc that called vlcc with the specific command that fixes the over-size ui.
[08:01] <rud0lf> can you pastebin the script?
[08:02] <rud0lf> and/or could you specify the error?
[08:02] <glitchd> yes 1 second
[08:02] <glitchd> *moment
[08:03] <glitchd> i have to reinstall it because i removed it to try another version
[08:04] <rud0lf> no rush
[08:08] <glitchd> rud0lf, ok ive got it reinstalled and ive got the error msg now. "Failed to change to directory “VLC media player” (No such file or directory)"
[08:08] <rud0lf> hm at launching?
[08:08] <glitchd> rud0lf, but i can open it manually and play whatever video file i want
[08:08] <glitchd> only if i try to play a video by right clicking the video and choosing "play with vlc"
[08:09] <rud0lf> link the pasted script please
[08:09] <glitchd> *open with vlc media player
[08:09] <glitchd> the script i use to get it to open normal sized?
[08:09] <rud0lf> yes
[08:09] <glitchd> ok
[08:10] <glitchd> rud0lf, https://pastebin.com/WMhZfPs3
[08:11] <rud0lf> i think you could add this line at the end of $HOME/.bashrc:
[08:11] <rud0lf> export QT_AUTO_SCREEN_SCALE_FACTOR=0
[08:11] <rud0lf> and then just change vlcc back to vlc
[08:11] <rud0lf> no script needed
[08:12] <rud0lf> i think: echo "export QT_AUTO_SCREEN_SCALE_FACTOR=0" >> ~/.bashrc
[08:12] <rud0lf> would be enough
[08:13] <glitchd> ill try that now and let you know.
[08:14] <rud0lf> now i think of it it may affect some other qt applications :S
[08:17] <glitchd> it didnt work anyways, and i removed it from the bashrc
[08:18] <rud0lf> i think you need to relogin
[08:19] <rud0lf> because it should work 100%
[08:21] <glitchd> and if it does work, are other qt applications going to be affected?
[08:22] <rud0lf> i guess so
[08:22] <rud0lf> sorry i'm out of ideas
[08:23] <rud0lf> oh i think i get it :)
[08:24] <rud0lf> hold on need to make sure on my system
[08:26] <glitchd> ok
[08:27] <rud0lf> glitchd: got it :) https://pastebin.com/fWBNtZHg
[08:27] <rud0lf> modified script
[08:28] <rud0lf> "$@" <-- pass the arguments of script to vlcc
[08:29] <rud0lf> quoted so it won't tread /home/foo/Movies/Foo Bar.mp4 as two arguments "/home/foo/Movies/Foo" and "Bar.mp4"
[08:29] <rud0lf> *treat
[08:29] <glitchd> ok ill give it a try right now
[08:31] <glitchd> it works the same as my fix did, i still cant open video files from the right click menu
[08:32] <rud0lf> uh
[08:34] <glitchd> im not really sure why its saying that when its clearly installed
[08:45] <rud0lf> glitchd: you may try this to see the dialog text that shows what arguments is vlc launched with https://pastebin.com/HFprcVUZ
[08:50] <glitchd> when using that command, it opens a text window first, vlc doesnt open until i close that window
[08:51] <rud0lf> yep but what's inside the text window?
[08:51] <glitchd> nothing, it was blank
[08:52] <rud0lf> wow
[08:52] <rud0lf> didn't expect that
[08:53] <glitchd> http://i.imgur.com/zOlbarr.png
[08:55] <rud0lf> i'm lost here
[08:56] <glitchd> thats the window that pops up when opening vlc now
[08:56] <glitchd> like i said, its blank.
[08:58] <glitchd> im gonna try getting a package from the vlc website and installing it instead of using the software center
[09:02] <glitchd> nope still the same thing
[09:11] <glitchd> im going to reinstall thx for the help
[09:59] <Pongles> Hello, I need some help. I have xubuntu on my laptop and the .xsession-errors file has appearently risen to 97.6 GiB, bring my computer to a standstill
[10:00] <Pongles> I've had to install an IRC app on my phone just to get here
[10:01] <diogenes_> Pongles, so remove those?
[10:02] <Pongles> "those"?
[10:02] <diogenes_> .xsession-errors
[10:04] <crimson_king> Pongles, at which point your computer locks up under this situation? Early in the boot process? When logging in to your account?
[10:04] <crimson_king> See if you can get to a TTY, login and delete the file from the console
[10:04] <crimson_king> login as root*
[10:05] <crimson_king> or some other user, if any
[10:05] <well_laid_lawn> using a live cd/usb to read the .xsession-errors file should help
[10:05] <well_laid_lawn> else it will happen again
[10:06] <crimson_king> Yep, that's better...
[10:07] <Pongles> It happens during normal use, it fills my SSD and so nothing else can function. I don't know what errors it contains because I don't have the ability to read files close to 100 GiB
[10:08] <Pongles> I don't have a live cd/USB as I am at work and only own 1 conputer
[10:09] <Pongles> I've restarted my laptop which has bought me some time while the next error log fills up. The errors seem to be coming from nm-applet
[10:12] <crimson_king> Pongles, try to stop NetworkManager then, see if it stops. Let's just identify where the problem comes from.
[10:12] <crimson_king> sudo systemctl stop network-manager
[10:14] <Pongles> Okay, I've stopped that
[10:14] <crimson_king> See if the .xsession-errors is still being written to...
[10:15] <Pongles> Seems it is still been written to, by mousepad now
[10:16] <Pongles> 10 error messages within the last minute
[10:16] <crimson_king> what makes you believe it's mousepad?
[10:16] <crimson_king> that is writing to it..
[10:16] <Pongles> That's the first word in the error message
[10:17] <Pongles> (mousepad:5937): GTK-WARNING ...
[10:17] <crimson_king> mousepad is open, then?
[10:18] <Pongles> Well my laptop has a mousepad, but I haven't manually opened any apps for it
[10:18] <Pongles> Oh wait, nvm I forgot that's what the pad program is called
[10:18] <Pongles> Yes, I have that open
[10:19] <crimson_king> run `top` on a terminal, see if any processes are showing unusually high CPU or memory consumption
[10:20] <Pongles> No high consumption I can see, highest CPU is under 2%, highest mem is under 1%
[10:20] <Pongles> Also seems the error file has stop being written to at such high rates
[10:23] <Pongles> I guess network-manager was the biggest issue
[10:23] <crimson_king> It seems many applications write to .xsession-errors.
[10:24] <Pongles> I'm more worried about the ones that spam xsession-errors
[10:26] <crimson_king> ok, try this... it should stop all writing to xsession-errors for now...
[10:26] <crimson_king> edit /etc/X11/Xsession
[10:26] <crimson_king> change ERRFILE to /dev/null
[10:26] <crimson_king> it will redirect all entries to xsession-errors to /dev/null
[10:28] <crimson_king> it should look like "ERRFILE=/dev/null"
[10:28] <Pongles> But then I'd get no errors, so if something else does break, I wouldn't know.
[10:28] <well_laid_lawn> +1 on that
[10:28] <crimson_king> we can then use another tool to see what was writing to it
[10:29] <crimson_king> No, wait. Sorry,
[10:29] <crimson_king> It monitors in real time
[10:29] <crimson_king> So don't do that change there.
[10:30] <crimson_king> Let me just test fatrace here...
[10:31] <crimson_king> install the package fatrace and run it as root.
[10:32] <Pongles> Done
[10:32] <Pongles> Seeing tclsh, i8kctl, and unknown
[10:32] <Pongles> And now firefox
[10:33] <crimson_king> I think `iotop` will be more useful for this
[10:33] <Pongles> Brb
[10:35] <crimson_king> Try iotop when you get back. Just install and run it.
[10:43] <Pongles> Sorry about that, my phone's connection died
[10:44] <Pongles> I have iotop running
[10:44] <crimson_king> all right. So run iotop, and when it's running, press A on the keyboard
[10:44] <crimson_king> it will show the accumulated amount of writes
[10:44] <Pongles> okay
[10:45] <crimson_king> and keep watching it for anything writing a lot.
[10:45] <Pongles> So far the only thing writing a lot is firefox
[10:45] <Pongles> but I also still have network-manager stopped
[10:46] <crimson_king> start it up, see what happens
[10:48] <Pongles> Well the first thing it did was break my irc connection
[10:48] <Pongles> maybe it knows it's time is limited
[10:49] <crimson_king> nothing on iotop?
[10:49] <crimson_king> is the file growing?
[10:49] <Pongles> nothing too much yet, but it has spammed a load in xsession-errors
[10:49] <Pongles> all duplicates of the same error
[10:49] <Pongles> just happening again and again
[10:50] <Pongles> NetworkManager has written 16k and nm-applet has written 32k
[10:51] <Pongles> It's these, just with a different set of timestamps: https://paste.ubuntu.com/p/7h92rn3hfS/
[10:51] <Pongles> happening 1-3 times a minute
[10:53] <crimson_king> Pongles, paste your journalctl, maybe there's something useful there
[10:58] <Pongles> I think this should have all the entries since last boot: https://paste.ubuntu.com/p/RY9KqGsj7W/
[11:01] <TJ-> Pongles: what's the issue? that report s missing all the important bits due to "Skilling..."
[11:01] <Pongles> Skilling?
[11:02] <TJ-> hahaha ... slaps fingers  "Skipping..."
[11:02] <TJ-> line 82 of the paste
[11:02] <Pongles> The issue is that nm-applet filled up my xsessions-error file to 97.6 GiB and I am trying to figure out how to stop it doing that without just dev/null/ing it
[11:03] <TJ-> Pongles: ouch ... well, what is it reporting ?
[11:03] <Pongles> https://paste.ubuntu.com/p/7h92rn3hfS/
[11:03] <TJ-> Pongles: presumably the same thing over and over?
[11:03] <Pongles> yep
[11:03] <Pongles> the thing in the paste, over and over
[11:03] <Pongles> multiple times a minute
[11:04] <TJ-> Pongles: show us "apt-cache policy network-manager-gnome"
[11:05] <Pongles> Here: https://paste.ubuntu.com/p/fPm2wrvhFV/
[11:08] <TJ-> Pongles: how long has the user session been active? I've got 18.04 with a session going 5 days and .xsession-errors has similar errors to yours but is only 326MB
[11:09] <Pongles> Mine has been active about an hour with a file size of 52.8 KiB, I'd say my previous session lenght was just under a week
[11:12] <TJ-> hmmm... I'd seriously doubt a week caused 97.6G of nm-applet reports. Did you actually count how many entries were from nm-applet with something like "grep nm-applet .xsession-errors.log | wc -l " ? Because I *suspect* something else may have actually dumped something BIG into that file at some point which was in the middle.
[11:12] <Pongles> No I didn't because I didn't know of anything that could read files that big
[11:12] <Pongles> and I wish you had said that 2 minutes ago before I finally deleted it.
[11:12] <TJ-> Pongles: I just did that count on mine, for the 5-day session, 30380
[11:13] <TJ-> Pongles: I'd recommend you do this count once a day and keep track of the result so we can see how fast the count increases. At the same time record the file size for each count.
[11:14] <Pongles> I am up to 470 in the last hour
[11:14] <brainwash> bug 1755305
[11:14] <TJ-> Pongles: that sounds about correct; each 'event' seems to cause 3 messages
[11:15] <Pongles> by my count, I'd be at 75670 after about a week
[11:16] <TJ-> Pongles: right ... nowhere near causing 76GB
[11:17] <TJ-> Pongles: I recall investigating this about a year ago and determining it was due to an Ubuntu specific patch.... let me see if I can find that now
[11:19] <Pongles> nm-applet wasn't the only thing I saw writting to my current .xsession-error file but it flooded out all the rest
[11:21] <TJ-> Hmmm, can't find which PC I did the work on now. However, I think it is related to the wifi side in that nm-applet is periodically updating the list of WiFi SSIDs and is updating the menu it displays when clicked on. Of course, when this menu is invisible/hidden it has no parent. Calls from applet_update_menu() I think it was
[12:41] <crimson_king> I get a prompt asking for authentication when the computer tries to suspend on idle. The screen locks after 15 minutes, and the system is supposed to suspend after 30, but that authentication prompt stops it from doing that. Any clues?
[12:43] <crimson_king> ... on both of my computers, which run Xubuntu 19.04 with the same settings.
[12:44] <crimson_king> The workaround here makes it suspend normally: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375
[12:48] <crimson_king> These are my Xfce-power-manager settings: The *screen* is set to go blank after 10 min, suspend after 12 min, shutdown after 15 min. The *system* is set to suspend after 30. *light-locker* is set to lock session when screensaver is _active_ and delay for 5 seconds; it also locks when the system suspends
[12:59] <brainwash> crimson_king: try with xfce4-screensaver instead of light-locker
[12:59] <brainwash> it's available in 19.04 and will be default in 19.10
[12:59] <crimson_king> brainwash, didn't know it was here already, i will try it
[15:49] <Pongles> So turns out it wasn't the nm-applet causing the huge .xsession-error file
[15:49] <Pongles> 5 hours after restart and it's up to 4.5 GiB
[15:50] <Pongles> If I had to guess, based on what I've seen so far. It's filled with about 4.5 GiB of this: https://paste.ubuntu.com/p/VBpvPPsbG7/
[15:51] <Pongles> I wonder if it's caused by me putting my laptop in Suspend mode while transporting it.
[15:56] <TJ-> Pongles:  glad you've pin-pointed it
[15:59] <TJ-> Pongles: apparently its from VLC
[16:00] <Pongles> I do have VLC open, and it does seem to bug out when I lock or suspend my session
[16:03] <TJ-> lots of errors reported, seems the underlying issue is hardware/drivers, but there's for example https://forum.videolan.org/viewtopic.php?t=148761
[16:04] <TJ-> and this bug about the cause https://trac.videolan.org/vlc/ticket/18708
[16:06] <Pongles> Hmm, interesting. Thanks. Your first link says that the logging can be disabled however when I check my VLC settings, the logging already isn't enabled.
[16:12] <TJ-> Pongles: there's some discussion here which seems to suggest part of the issue can be when the system does NOT have an Nvidia GPU but VLC in 'auto' hardware acceleration mode uses NVidia's VDPAU library. There's a setting workaround in that scenario suggested too. https://github.com/i-rinat/libvdpau-va-gl/issues/53
[16:12] <Pongles> I do have a Nvidia GPU though
[16:13] <Pongles> I might not have the prop drivers though.
[16:17] <andresArgentina> Hi there! I just installed Xubuntu 19.04 (before that I tried with 18.04 and 18.10) in a notebook "Bangho Cloud G". It always has 2 problems: wifi and audio. I could make the wifi works with an external USB, but I was not the same with the audio
[16:18] <andresArgentina> When I put "lspci" in the terminal I get this:
[16:18] <andresArgentina> 00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 36)00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers (rev 36)00:03.0 Multimedia controller: Intel Corporation Atom/Celeron/Pentium
[16:18] <andresArgentina> Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit (rev 36)00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 36)00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 36)00:1a.0
[16:18] <andresArgentina> Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 36)00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 36)
[16:18] <andresArgentina> ¿Can anybody give me a hand?
[18:16] <Wayward_Vagabond> So, after messing arounf trying to get an HP printer working, I seem to have broken CUPS on xubuntu 18.04.2lts
[18:16] <Wayward_Vagabond> tried reinstalling everything cups/printer related and cleared out the job that was saved, but still can't cups to start again
[19:53] <TJ-> Wayward_Vagabond: what does the service log report?