| === brainwash_ is now known as brainwash | ||
| xubuntu29w | Hello, I've installed Xubuntu 18.04 on a new laptop. I had to use nomodeset in order for it to boot on the live USB. Now it has installed, I can get to the login screen fine, but after that I just have the desktop wallpaper and mouse. That's all I can see. Any ideas? | 08:27 |
|---|---|---|
| xubuntu29w | I assume this could be a graphics problem. I have an NVIDIA 1050 and integrated Intel graphics too? | 08:28 |
| diogenes_ | xubuntu29w, open a terminal ctrl+alt+t | 08:29 |
| xubuntu29w | diogenes_: on the login screen? | 08:29 |
| xubuntu29w | I'm in the process of reinstalling so will let you know once done | 08:30 |
| diogenes_ | ok | 08:31 |
| diogenes_ | xubuntu29w, btw do you have a separate /home and preserved data on it from the previous installations? | 08:32 |
| xubuntu29w | diogenes_ no, I'm using a whole disk and doing a clean install | 08:35 |
| xubuntu29w | it's a Dell G3 3779 if that helps also | 08:35 |
| diogenes_ | ok let's see what you get after the installation. | 08:36 |
| xubuntu29w | almost done:) | 08:37 |
| xubuntu29w | diogenes_ okay it has now installed, I've logged in and there's just the wallpaper showing with the mouse cursor | 08:40 |
| xubuntu29w | after logging in, I can't Ctrl Alt T | 08:41 |
| diogenes_ | ctrl+alt+f1 | 08:41 |
| xubuntu29w | Neither work at the login screen | 08:42 |
| xubuntu29w | diogenes_ f1 after logging in? | 08:42 |
| xubuntu29w | no that doesn't appear to do anything either | 08:42 |
| diogenes_ | ok go to the login screen and see the session chooser, what do you have there? xsession, xfce-session? | 08:43 |
| xubuntu29w | Xfce session and Xubuntu session | 08:43 |
| diogenes_ | which on is default? | 08:44 |
| xubuntu29w | Xubuntu is the default | 08:44 |
| diogenes_ | ok try the other one. | 08:44 |
| xubuntu29w | done so, that still doesn't work | 08:44 |
| diogenes_ | ok then reboot and at grub menu ress 'e' | 08:45 |
| diogenes_ | press* | 08:45 |
| xubuntu29w | GRUB menu doesn't come up at boot, it seems to boot straight in | 08:45 |
| xubuntu29w | Is this normal? I'll try pressing e on the keyboard | 08:45 |
| xubuntu29w | nope no GRUB menu or access to it | 08:46 |
| diogenes_ | turn off pc, then turn on again and keep the shift key pressed while it's booting, grub should be shown. | 08:47 |
| xubuntu29w | diogenes_ tried twice, still no GRUB | 08:50 |
| diogenes_ | xubuntu29w, ok then as soon as you reach the login screen try these: ctrl+alt+f1/f2/f3/f4/f5 see which one will bring you the TTY. | 08:51 |
| xubuntu29w | diogenes_ none of them wor | 08:52 |
| xubuntu29w | my keyboard works | 08:52 |
| xubuntu29w | but they don't bring up anything | 08:52 |
| diogenes_ | xubuntu29w, do you still have the installation usb? | 08:52 |
| xubuntu29w | It's not the .iso or USB as I've written this 3 times in rufus as dd, even tried an older iso of 18.04, same problem | 08:53 |
| xubuntu29w | diogenes_ yep | 08:53 |
| diogenes_ | ok boot the live usb. | 08:53 |
| xubuntu29w | diogenes_ booted, using the nomodeset option in GRUB | 08:54 |
| diogenes_ | ok now open a terminal. | 08:54 |
| xubuntu29w | ctrl alt t'd | 08:55 |
| xubuntu29w | it's open | 08:55 |
| diogenes_ | lsblk | 08:55 |
| diogenes_ | see which one is your root partition of your HDD not USB. | 08:56 |
| diogenes_ | usually /dev/sda1 | 08:56 |
| xubuntu29w | nvme0n1p1 is the disk | 08:56 |
| xubuntu29w | nvme0n1 | 08:57 |
| xubuntu29w | then a 512MB partition on nvme0np1 | 08:57 |
| xubuntu29w | and the rest of the disk is on nvme0np2 | 08:57 |
| diogenes_ | hmm did you disable secure boot in bios? | 08:57 |
| diogenes_ | ok let's try this | 08:59 |
| diogenes_ | mkdir chroot | 08:59 |
| xubuntu29w | secure boot is disabled | 08:59 |
| diogenes_ | sudo mount nvme0n1p1 chroot/ | 08:59 |
| diogenes_ | sudo mount --bind /dev chroot/dev | 08:59 |
| diogenes_ | sudo mount --bind /sys chroot/sys | 08:59 |
| diogenes_ | sudo mount --bind /proc chroot/proc | 08:59 |
| xubuntu29w | first command says mount point does not exist | 09:01 |
| xubuntu29w | "chroot/: mount point does not exist" | 09:01 |
| diogenes_ | first command is mkdir chroot | 09:02 |
| diogenes_ | then sudo mount nvme0n1p1 chroot/ | 09:02 |
| xubuntu29w | ah missed that | 09:03 |
| xubuntu29w | it's saying special device nvme0n1p1 does not exist | 09:04 |
| xubuntu29w | it shows in lsblk | 09:04 |
| diogenes_ | sudo mount /dev/nvme0n1p1 chroot/ | 09:05 |
| xubuntu29w | worked | 09:05 |
| diogenes_ | now the other 3 | 09:06 |
| diogenes_ | sudo mount --bind /dev chroot/dev ... | 09:06 |
| xubuntu29w | third doesn't work | 09:06 |
| xubuntu29w | mount point does not exist | 09:06 |
| diogenes_ | paste here what you run as the 3rd. | 09:07 |
| xubuntu29w | chroot/dev: mount point does..... | 09:07 |
| xubuntu29w | sudo mount --bind /dev chroot/dev | 09:07 |
| diogenes_ | the entire command i mean. | 09:07 |
| xubuntu29w | Debian and openSUSE have installed fine | 09:13 |
| xubuntu29w | just was having issues with NVIDIA prime | 09:13 |
| xubuntu29w | which doesn't seem to be implemented too well in Linux at this time | 09:14 |
| diogenes_ | well i use nvidia optimus too and i got no problems at all, using the oss nouveau driver instead on nvidia. | 09:14 |
| jatt | after upgrading from disco to eoan the restart and shutdown buttons are grayed out. what could be the reason? | 09:42 |
| jatt | the power manager says there is no authorization to shutdown: http://dpaste.com/197484T | 09:44 |
| Regor | how to enable links in terminal ? | 14:22 |
| sublevel | Regor: you can ctrl+click, or right click them | 14:29 |
| Kumool | depends on the terminal | 14:29 |
| sublevel | well xubuntu has a default terminal | 14:30 |
| Regor | 18.04 default | 14:30 |
| Regor | yeah.got it | 14:31 |
| Regor | actually on weechat it needs shift key with mouse enabled | 14:32 |
| sublevel | aha, I'm not surprised weechat's mouse mode affects it | 14:32 |
| Regor | yeah | 14:33 |
| sublevel | if you want to use alt+number to change weechat buffers I found out how to stop xfce4-terminal hogging that shortcut recently | 14:33 |
| Regor | yeah :) | 14:34 |
| sublevel | I'll find it for you in a bit | 14:34 |
| Regor | :) | 14:34 |
| salamanderrake | Is there a way to install the testing xubuntu 19.10 without a new install? | 14:40 |
| sublevel | Regor: here it is https://docs.xfce.org/apps/terminal/start (I'd tried commenting out those lines with no luck, setting them to "" was the key) | 14:41 |
| Regor | sublevel: thanks :D | 14:42 |
| sublevel | I wonder if my programming skills would be up to making a patch that adds a GUI preferences option | 14:43 |
| Spass | salamanderrake, if you're using 19.04 right now you could probably change the main repos from "disco" to "eoan" and full-upgrade, but don't do that on your non-testing installation, since it may cause some issues and you may end with a non-working system | 15:49 |
| Regor | how to set transmission minimized while closing the window? | 15:57 |
| Spass | Regor, minimized to tray? there's an option for that in the preferences window, Desktop tab, enable "Show Transmission icon in the notification area" | 17:29 |
| Regor | thanks i found it | 17:31 |
| ilovetrump | hello nice people | 17:41 |
| ilovetrump | i love you all | 17:41 |
| ilovetrump | how are you doing today? | 17:41 |
| swift110 | htey | 19:13 |
| sublevel | 18.04, I have my laptop set to just switch off display when lid is closed, that works as expected but if the screen is locked it goes into suspend instead. Where might I begin looking for a way to prevent that? | 19:39 |
| sublevel | Had a look at the light-locker man pages | 19:40 |
| tomreyn | hmm maybe energy settings? | 19:51 |
| sublevel | Power Manager settings? I've checked all the tabs there | 19:55 |
| tomreyn | yes that's what i meant- i don't have a better suggestion. | 19:57 |
| sublevel | perhaps it's down to systemd config, in journalctl I have systemd-logind[988]: Lid closed. then systemd-logind[988]: Suspending... | 19:58 |
| tomreyn | you can generally configure how the lid closing event is handled there | 19:58 |
| tomreyn | but i don't think it has a means to handle it differently based on whether or not the screen is locked | 19:59 |
| sublevel | Indeed, but it only seems to affect when my screen is unlocked | 19:59 |
| tomreyn | i.e. man page logind.conf(5) | 19:59 |
| sublevel | good plan | 20:00 |
| sublevel | HandleLidSwitch=ignore works and doesn't appear to break anything else, hurrah | 20:04 |
| === jmcgnh_ is now known as jmcgnh | ||
| === jmcgnh is now known as jmcgnh_ | ||
| === jmcgnh_ is now known as jmcgnh | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!