| === Elimin8r is now known as Elimin8er | ||
| === pavlushka_ is now known as pavlushka | ||
| tombusby | hi there | 19:26 |
|---|---|---|
| lotuspsychje_ | tombusby: you upgraded from wich version? | 19:26 |
| tombusby | just upgraded to 18.04 and I'm stuck in a login loop | 19:26 |
| tombusby | in the past this was caused by nvidia drivers, but those steps don't resolve now | 19:26 |
| tombusby | 16.04 | 19:26 |
| tombusby | LTS | 19:26 |
| lotuspsychje_ | tombusby: that isnt reccomended yet, bionic is still in development branch | 19:26 |
| lotuspsychje_ | tombusby: if you want to help, clean install 18.04 | 19:27 |
| tombusby | well that's pretty annoying then, given that I got a dist upgrade prompr | 19:27 |
| tombusby | *prompt | 19:27 |
| lotuspsychje_ | huh? | 19:27 |
| lotuspsychje_ | you had a window saying upgrade to bionic? | 19:28 |
| tombusby | yes | 19:28 |
| lotuspsychje_ | tombusby: can you prove this with a pic? | 19:28 |
| tombusby | It wasn't exactly the type of thing I documented for posterity, I just ran the upgrade | 19:28 |
| lotuspsychje_ | tombusby: but did you enter a dist upgrade command? | 19:29 |
| tombusby | I did it via the software update GUI | 19:29 |
| tombusby | got a prompt to update dist, so I did it | 19:29 |
| lotuspsychje_ | tombusby: that shouldnt be happening | 19:30 |
| lotuspsychje_ | tombusby: you sure it was 18.04? | 19:31 |
| tombusby | aparently not, especially since I thought I had only LTS versions enabled, so to hear that this is still development branch... that's not great | 19:31 |
| lotuspsychje_ | tombusby: can you lsb_release -a plz? | 19:31 |
| tombusby | sure, 1 mo, I'll SSH in | 19:31 |
| tombusby | No LSB modules are available. | 19:32 |
| tombusby | Distributor ID:Ubuntu | 19:32 |
| tombusby | Description:Ubuntu Bionic Beaver (development branch) | 19:32 |
| tombusby | Release:18.04 | 19:32 |
| tombusby | Codename:bionic | 19:32 |
| lotuspsychje_ | what the heck | 19:32 |
| lotuspsychje_ | tombusby: you sure you didnt enter a command youself like with -d ? | 19:32 |
| lotuspsychje_ | or messed with proposed | 19:32 |
| tombusby | so, essentially, I have to do a full reinstall is the long and short of it then? my install is knackered? | 19:32 |
| tombusby | na mate, logged in, got the prompt, ran it | 19:33 |
| lotuspsychje_ | tombusby: that should not be happening, can you bug this please | 19:33 |
| lotuspsychje_ | tombusby: you ahd 16.04.3? | 19:33 |
| lotuspsychje_ | had | 19:33 |
| tombusby | whatever the LTS version was, I'd been holding off doing an upgrade because I got log-in loops, but a previous update (non-dist) gave me login loops, I fixed that, so this time when I got the prompt to update dist, I decided why not | 19:34 |
| tombusby | but yeah it was 16.04 | 19:34 |
| lotuspsychje_ | tombusby: its supposed to upgrade in june | 19:35 |
| lotuspsychje_ | 16.04 to 18.04.1 | 19:36 |
| tombusby | I'm guessing there's no way to reliably downgrade? | 19:36 |
| lotuspsychje_ | officially LTS to LTS | 19:36 |
| lotuspsychje_ | tombusby: i think things will got scrambled now | 19:36 |
| dax | bionic isn't in meta-release-lts (or meta-release, for that matter), so I do not know of a way it'd upgrade without do-release-upgrade -d or something | 19:37 |
| tombusby | ok, no worries, well, I better get to work on fixing this then. that's all I can tell you | 19:37 |
| dax | but yes, if you're on 18.04 and want to be on something lower, the only supported method is a reinstall | 19:37 |
| lotuspsychje_ | tombusby: did you enter that -d command? | 19:37 |
| tombusby | not that I know of, just prompted and his install | 19:38 |
| tombusby | *hit | 19:38 |
| lotuspsychje_ | tombusby: you didnt mess with anything else unofficial? | 19:38 |
| tombusby | not to my knowledge. I don't like to do anything that could make my conf unstable | 19:39 |
| lotuspsychje_ | tombusby: might be interesting to see your sources.list ? | 19:39 |
| tombusby | sure | 19:39 |
| dax | i assume sources.list is just gonna be normal bionic, since the upgrader would have poked at them | 19:40 |
| lotuspsychje_ | dax: wouldnt we see his ppa's or other stuff too? | 19:40 |
| tombusby | # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to | 19:40 |
| tombusby | # newer versions of the distribution. | 19:40 |
| tombusby | deb http://pl.archive.ubuntu.com/ubuntu/ bionic main restricted | 19:40 |
| tombusby | # deb-src http://pl.archive.ubuntu.com/ubuntu/ xenial main restricted | 19:40 |
| TJ- | tombusby: was this system previsously release-upgraded from some other release to 16.04 ? | 19:40 |
| tombusby | ## Major bug fix updates produced after the final release of the | 19:40 |
| tombusby | ## distribution. | 19:40 |
| lotuspsychje_ | dax: seems like your right | 19:41 |
| dax | lotuspsychje_: sure, and I guess it's theoretically possible someone has a PPA that contains modified updater packages that point somewhere other than changelogs.ubuntu.com | 19:41 |
| dax | but that seems unlikely | 19:41 |
| lotuspsychje_ | never heared of a pre-release upgrade notify before.. | 19:41 |
| dax | 'cause they don't happen. like, i entirely believe that it happened in this case, but i am at a loss as to how | 19:42 |
| TJ- | tombusby: can you show us /etc/update-manager/meta-release | 19:43 |
| TJ- | if the URLs have been changed we don't know what was pulled | 19:43 |
| lotuspsychje_ | he should bug this | 19:43 |
| dax | lotuspsychje_: yeah, if the output from what TJ- asked for is all changelogs.ubuntu.com, i agree | 19:44 |
| tombusby | # default location for the meta-release file | 19:45 |
| tombusby | [METARELEASE] | 19:45 |
| tombusby | URI = http://changelogs.ubuntu.com/meta-release | 19:45 |
| tombusby | URI_LTS = http://changelogs.ubuntu.com/meta-release-lts | 19:45 |
| tombusby | URI_UNSTABLE_POSTFIX = -development | 19:45 |
| tombusby | URI_PROPOSED_POSTFIX = -proposed | 19:45 |
| TJ- | Also, we should check for all installed cron jobs, and the /var/log/dist-upgrade/ dir | 19:45 |
| TJ- | !paste | tom | 19:45 |
| ubottu | tom: For posting multi-line texts into the channel, please use https://paste.ubuntu.com | To post !screenshots use https://imgur.com/ !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic. | 19:45 |
| dax | (drone probably also sent you a PM with the same instructions) | 19:45 |
| dax | anyways, gonna leave this one with TJ-, seems like he's about 5 minutes ahead of me on this one | 19:46 |
| dax | (also, it's lunch time) | 19:46 |
| lotuspsychje_ | tombusby: ddi you enable proposed or so? | 19:46 |
| dax | proposed shouldn't cause this | 19:46 |
| tombusby | no worries, but I have to go really tbh. I'll put a bug report in when I get a moment. | 19:46 |
| lotuspsychje_ | dax: bon apetit mate | 19:46 |
| tombusby | and no I didn't | 19:46 |
| lotuspsychje_ | just thinking what could have triggered this | 19:46 |
| TJ- | tombusby: was the prompt in the GUI? | 19:47 |
| tombusby | just the standard one to upgrade dist | 19:47 |
| TJ- | tombusby: right, in the GUI? | 19:47 |
| tombusby | yes | 19:47 |
| TJ- | tombusby: OK, that's a clue | 19:47 |
| tombusby | but I honestly have to go guys, I've gotta take care of my son for a bit. I'm sorry to drop this on you and disappear | 19:47 |
| lotuspsychje_ | no sweat come back later & bug it okay | 19:48 |
| lotuspsychje_ | we aint see nothing yet | 19:48 |
| TJ- | if I recall correctly - I may be wrong after so long - at one time the GUI from update-manager was triggered by a file existing under /var/ somewhere... it's feasible something triggered that, but what doesn't make sense is how it knew about the new release codename/URL, since changelog. doesn't have it | 19:48 |
| lotuspsychje_ | and what does he mean from in the past this already happened lol | 19:50 |
| TJ- | "in the past" in reference to solving a log-in loop due to nvidia drivers | 19:51 |
| lotuspsychje_ | perhaps | 19:53 |
| lotuspsychje_ | its a weird story to me | 19:53 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!