| === brainwash_ is now known as brainwash | ||
| zleap | hi, is the xubuntu developer list still active as there is a question on the list, from a new contributor that I am not sure how to help with | 10:38 |
|---|---|---|
| Unit193 | He's referring to elementary-xfce-icon-theme changing from blue to manila. Not really sure there's much to do there, other than change the theme to another icon set. | 10:39 |
| zleap | ah ok, so can anyone help | 10:42 |
| gimzmoe | I'm trying to hunt down a way to hunt down an issue I'm having with a laptop running xubuntu 20.04. I can't catch anything funny in syslog or in dmesg, the system 'randomly' crashes to a low-power state but otherwise unresponsive without a 'long-press' power cycle. I'm trying to figure out where to look | 14:49 |
| diogenes_ | gimzmoe, maybe at RAM and swap usage first? | 14:58 |
| gimzmoe | diogenes_ system has 16GB and mostly free, swap use is 0 | 15:00 |
| gimzmoe | I did try ZFS, but I was having this problem in eith ext4 too | 15:00 |
| gimzmoe | it... smells like a hibernate/suspend thing, but I don't know where to find evidence of it in the logs | 15:15 |
| gimzmoe | however, all the suspend/hibernate .targets are disabled so ... doesn't seem to be that | 15:33 |
| tomreyn | gimzmoe: would you like to post a systemd-journal (using journalctl) for a session which ended this way? | 15:43 |
| tomreyn | gimzmoe: if not: ensure the system is fully updated, look into bios updates, try magic sysrq in the unresponsive state, in hopes this will preserve logs (check for any after reboot) | 15:45 |
| gimzmoe | I'll check if I've updated the bios recently | 15:45 |
| tomreyn | journalctl -b | grep DMI: | 15:47 |
| tomreyn | ^ would tell you the current bios version | 15:47 |
| gimzmoe | clever, 2018... might be ready for an update | 15:48 |
| tomreyn | you should also stress test this system, i.e. memtest86+, cpu load testing, running manufacturers' hardware tests. | 15:48 |
| gimzmoe | interesting you mention that, I was running CPU intensive work when it errored recently. | 15:52 |
| gimzmoe | well that's something. Whatever it was it killed the laptop before anything was written to journalctl | 15:56 |
| gimzmoe | was trucking along then --Reboot-- | 16:00 |
| tomreyn | !sysrq | 16:00 |
| ubottu | In an emergency, you may be able to shutdown cleanly and reboot by holding down Alt+PrintScreen and typing slowly, in succession, S, U and B. For an explanation, see http://en.wikipedia.org/wiki/Magic_SysRq_key | 16:00 |
| bluefire | error upgrading from 20.04 to 20.10 - "could not preform immediate configuration" | 16:03 |
| tomreyn | bluefire: if you're seeking assistence with this, you'll need to provide more details. that's also so if you're trying to file a !bug report. | 16:07 |
| gimzmoe | sysbench cpu loads are not causing the same issue... maybe it's a network thing | 16:21 |
| bluefire | error upgarding from 20.04 to 20.10 - "could not preform immediate configuration". Bug #1899272 reported. Do you notice this bug? | 16:22 |
| ubottu | bug 1899272 in ubuntu-release-upgrader (Ubuntu) "upgrade to 20.10 beta from 20.04 fails immediate configuration" [Undecided,Confirmed] https://launchpad.net/bugs/1899272 | 16:22 |
| tomreyn | the person who reported this had many "Foreign: " packages installed (VarLogDistupgradeMainlog.txt), several third party repositories active, including for different ubuntu releases | 16:32 |
| tomreyn | release upgrades should be started from a supported state only. | 16:32 |
| bluefire | There is a safe workaround? | 16:34 |
| bluefire | Do i need to edit sources.list? | 16:36 |
| tomreyn | if you are not already in the middle of an upgrade, you can clean up; use pp-apurge to remove foreign / unsupported packages, package versions, and apt repositories. then use apt-forktracer to identify additional packages to remove. | 16:50 |
| tomreyn | also make sure the system is fully up to date on the source release version. | 16:51 |
| tomreyn | *ppa-purge | 16:51 |
| bluefire | The reported bug description is the same as my error message | 17:03 |
| bluefire | libc6:amd64 and libffi8ubuntu1:amd64 | 17:04 |
| xu-irc79w | hello?? | 17:39 |
| xu-irc79w | I am a old user of Xubuntu...20.04 lts | 17:39 |
| tomreyn | hi xu-irc79w, do you have a xubuntu support question? | 17:41 |
| xu-irc79w | Its speedy,light wight ,super customizable.but out of the box it,s so ugly,there is no cool wallpaper,old icon,old theme Why???can you make this gorgious.. | 17:43 |
| xu-irc79w | -_- -_- -_- </3 plz... | 17:44 |
| bluefire | Bug #1899272 - the bug description is the same as my error. | 17:44 |
| ubottu | bug 1899272 in ubuntu-release-upgrader (Ubuntu) "upgrade to 20.10 beta from 20.04 fails immediate configuration" [Undecided,Confirmed] https://launchpad.net/bugs/1899272 | 17:44 |
| bluefire | libc6:amd64 and libffi8ubuntu1:amd64 | 17:45 |
| tomreyn | bluefire: do you have a yubuntu support question? | 17:46 |
| tomreyn | *Xubuntu | 17:47 |
| bluefire | using ppa-purge is the only way to fix this? | 17:47 |
| tomreyn | ppa-purge is a utility which can help you remove packages (and package versions) provided by 3rd party apt repositories, as well as those apt repository configurations. | 17:49 |
| tomreyn | apt-forktracer is another. | 17:50 |
| tomreyn | release upgrades should be run from systems which don't have such 'foreign' packages (and package versions) installed only. | 17:50 |
| tomreyn | it *may* work without doing so, or it may not. in your case, the latter seems to apply. | 17:50 |
| bluefire | but until now i updated with ppa packages no problem. what changed? | 17:51 |
| brainwash | you created a case in which it does not update properly | 17:53 |
| bluefire | so i need to remove the ppa packages, update and add it again? | 17:55 |
| brainwash | I guess so if you don't want to rely on the brute force approach which is mentioned in the linked bug report | 17:59 |
| bluefire | ok, so i need to use ppa-purge or i can manualy remove this packages (with synaptic for example)? | 18:02 |
| brainwash | depends on how skilled you are | 18:10 |
| bluefire | i have only 3 ppa installed software that i can unistall with synaptic. i disabled the ppa in software sources, and the update failed again. there is a chance that if i uninstall this ppa software i will be able to upgrade the system? | 18:15 |
| tomreyn | install and run apt-forktracer afterwards, too, but yes, there is a chance (and no, this is not a guarantee). | 18:20 |
| bluefire | ok thank you | 18:22 |
| bluefire | i unable to upgrade from 20.04 to 20.10. bug reported: Bug #1899272. bug description is same as my error. apt-forktracer gives me: libwebp5 (0.4.4-1)retroarch (1.9.0-r202011230847-96af31bce7-109~ubuntu20.04.1) [Ubuntu: 1.7.3+dfsg1-1.1]pcsx2 (1:1.4.0-11) [Ubuntu: 1.5.0~gfc1d9aef0+dfsg-2]libwxgtk3.0-0v5 (3.0.4+dfsg-12)libopenvg1-mesa | 19:39 |
| bluefire | (10.3.2-0ubuntu0.1)multiarch-support (2.29-0ubuntu2)secureboot-db (1.6~20.04.1) [Ubuntu: 1.5]libdvdcss2 (1.2.13-0) | 19:40 |
| ubottu | bug 1899272 in ubuntu-release-upgrader (Ubuntu) "upgrade to 20.10 beta from 20.04 fails immediate configuration" [Undecided,Confirmed] https://launchpad.net/bugs/1899272 | 19:40 |
| bluefire | do i need to uninstall this packages and re-install them after upgrade? | 19:42 |
| Maik | bluebird probably | 19:44 |
| krytarik | Wrong blue*.. | 19:45 |
| Maik | But if you have such issues with upgrading I'd recommend a clean install of 20.10 instead. | 19:46 |
| bluefire | do i need to uninstall 3rd party ppa first? | 19:46 |
| bluefire | clean install is not an option for me. | 19:47 |
| Maik | Why not? | 19:47 |
| Maik | And yes, disable or remove the ppa's before upgrading | 19:48 |
| Maik | Always | 19:49 |
| bluefire | because its a massive headache for me | 19:49 |
| Maik | Hard to believe | 19:49 |
| Maik | 51162krytarikutocomplete on tablet | 19:50 |
| bluefire | if uninstalling the ppa not helps me, clean install is the only option? | 19:53 |
| Maik | If you keep running into trouble then yes | 19:54 |
| Maik | I never spend hours or days fiddling around, if it doesn't work out I simply clean install. Way faster than troubleshooting. | 19:56 |
| bluefire | whan i start the upgrade, it says "upgrade to 20.04" but the upgrade is to 20.10 | 19:57 |
| Maik | I noticed that too, probably a bug. | 19:58 |
| bluefire | ok | 19:58 |
| Maik | You will get 20.10 though | 19:59 |
| bluefire | ok | 19:59 |
| bluefire | thank you | 20:00 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!