/srv/irclogs.ubuntu.com/2020/03/09/#ubuntu+1.txt

lotuspsychjegood morning02:42
=== TheRedQueen is now known as Drone
takov751Moornimg06:13
Haxxahttp://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/current/ whats the default passwd for root?07:51
oerheksuser ubuntu pass clear?09:06
bigfoot-btw, this bug just bit me: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=90851611:11
ubottuDebian bug 908516 in evince "Apparmor profile breaks print preview" [Normal,Fixed]11:11
bigfoot-(tried to open multiple PDFs with one evince command line, evince a.pdf b.pdf c.pdf; -> a.pdf gets opened, plus error msgs for b and c -> Error launching evince file:///home/XY/.../b.pdf: Failed to execute child process “/bin/sh” (Permission denied))11:12
bigfoot-... I guess, again I won't create an Ubuntu bug report because I upgraded from 19.10 ...11:13
oerheksregression? this does not happen on 18.04 evince 3.28.4-0ubuntu1.211:16
bigfoot-didn't happen in 19.10 either.  this is a 20.04 regression.11:17
bigfoot-either way I've been told not to open bug reports from bugs observed in an upgraded system ...11:17
oerhekssure, file a bugreport.11:17
oerheksoh11:18
bigfoot-(this is not a clean 20.04 install; it has been upgraded all the way since 16.something)11:18
oerhekswell11:18
oerheksi see Focal should have  3.35.92-111:19
oerhekshttps://launchpad.net/ubuntu/+source/evince11:19
oerhekscheck yours??11:19
bigfoot-Yes, that's the one I have.11:19
bigfoot-And it's definitively an AppArmor-caused issue, I see DENIED log entries associated with my running evince.11:20
=== genii_ is now known as genii
mcphailbigfoot-: why on earth would someone ask you to avoid filing a bug report on an upgraded system?15:59
lotuspsychjemcphail: i adviced you help test devel release on a clean daily, to avoid giving the devs extra work16:01
lotuspsychje*him16:01
oerheksi never knew this rule too.16:01
mcphailBut upgrades are supported and should be tested16:01
lotuspsychjewell, we often get users here that force upgrades when they shouldnt yet, and get corrupted issues, that does not occur on clean dailys16:02
lotuspsychjeso, i advice to at least compare their issues on a clean daily16:03
mcphailYes, fair enough to compare to a clean daily. But still worth filing against the upgraded system version, referencing the behaviour on the clean daily, is it not?16:04
oerheksthe debian bugreport mentioned is invalid.16:04
oerheksregression, sure, but can you guys reproduce it?16:05
lotuspsychjeif they compare sure, but thats often not the case, they jump from non-lts release to an early devel release, thats just wrong in my opinion16:05
mcphailI'm on Mate here. Can't reproduce it on Atril, which is an evince fork, I think16:05
bigfoot-It's probably not the exact same bug, but in the same ballpark (evince trying to do something that AppArmor prevents it to do).18:57
CarlFKis there a torrent for focal? 21:37
oerheksCarlFK, nope :-(21:38
CarlFKmeh, no prob - I'm guessing if it was a problem there would be.21:38
CarlFKwhy did rsynd  do this?  http://paste.ubuntu.com/p/4pyFjkDdRY/21:39
CarlFKer, rsync.  not d.21:40
CarlFKzsync seems to be working ok, so im not fussed. 21:40
CarlFKlive, install, wifi picker - the SSIDs are alphabetical, not by power 22:00
CarlFKshould I log an issue?22:01
oerhekssounds normal?22:01
CarlFKI would expect sorted by power so that the close one was at the top of the list 22:03
FurretUberAre scripts located in /lib/systemd/system-shutdown no longer executed?22:34
FurretUberThere is one computer that has a serial port which communicates to a projector, and the command to power off the projector can't be send on reboot or kexec22:35
FurretUberThe way I had found back then (16.04) was to have one script that checks if it was a poweroff or halt that was sent. And, if yes, it would run screen to send the required command to power the projector off22:36
FurretUberNow, I'm not sure it just not work or there is some race condition or something. The script that does this is the exact same used on 16.0422:36
CarlFKFurretUber: pastebin it 22:38
FurretUberhttps://paste.ubuntu.com/p/C4BBWBnGDc/22:39
FurretUberThe sleep command was required back then because, without at least one second, the command wouldn't be sent in time for the projector22:47
CarlFKFurretUber: for systemd, you need a file that looks like this: https://salsa.debian.org/debconf-video-team/ansible/-/blob/master/roles/opsis-ingest/files/videoteam-ingest.service22:49
CarlFKyour script gets called from ExecStart=/usr/local/bin/videoteam-ingest22:50
FurretUberA service file didn't work when I tried. Because it ran on reboot and poweroff. The script I sent before is speficically for system-shutdown22:51
FurretUbersystemd-shutdown is, supposedly, the last thing that runs before the shutdown. It even has to be on this case, as the projector is the screen22:51
CarlFKoh wow, I didn't know about the "run all in this dir" thing.. https://unix.stackexchange.com/questions/347306/how-to-execute-scripts-in-usr-lib-systemd-system-shutdown-at-reboot-or-shutdow22:52
FurretUberThis is being very useful for cases where there is some special hardware that requires some setup or configuration to power off properly. At least, until 20.04 :(22:54
CarlFKFurretUber: I would ask in /j #systemd - likely get to the bottom of this sooner there, and then if they say "somethings broke, log an issue" then you know what is broken 22:55
FurretUberI will try there, thank you22:56
FurretUberThinking on that now, it's possible to query the projector if it's on or off. A while loop running until it is powered off may work...23:06

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!