[01:53] I just installed xubuntu, and now my computer won't start [01:53] Please help [01:55] I've got a black screen with three messages [01:55] "/dev/sda1: recovering journal" [01:55] "/dev/sda1: Superblock last mount time is in the future. [01:56] "(by less than a day, probably due to the hardware clock being incorrectly set)" [01:56] "/dev/sda1: clean, 6025/15269888 files, 2040187/61049344 blocks" [02:03] How long did you leave it at that point? Is there screen flashing? You should remove 'quiet splash' from the grub boot options. [02:03] How do I do that? all I have is a blank screen [02:57] Okay so I am using xubuntu (duh) and I am having problems with xrandr, it's saying xrandr: failed to get size of gamma for output default....How do I fix this for my monitor so I can setup my two monitors [06:30] hi. for 16.04, how can I get a volume control in the panel? [06:30] i tried xfce4-goodies and xfce4-pulseaudio-plugin, neither does anything [06:31] xfce4-mixer isn't found in repos [07:49] (Answered elsewhere: volumeicon-alsa) [07:50] yeah, thanks again [07:51] Sure thing, been using it for quite a while. :) [09:28] oh thanks :) got the answer about the volume control... was thinking it yesterday totally drunk... now everything is set, more coffee. Thanks commonity. [09:28] *munity :) [11:26] hi [11:26] what can i do here? [11:27] bye [13:35] hi all, I've always used Xubuntu on my laptops for the lighter weight/performance - but on current hardware Ubuntu and Kubuntu wms run just as fast. Do you think it's reasonable to still use XFCE in 2017, just because I feel it's more distraction free? I'll still need to install some Gnome/KDE libs for certain apps. any thoughts ? [13:48] bliplap: hello, my thoughts are 1) people should use whatever they like the most 2) people are leaving IRC after they asked a question way to early [19:04] how do i do /mount -t autofs /dev/sda1 /mnt/somewhere when i want to mount a specific device by id that is listed in /lsusb, but not in thunar/disks/gparted/fdisk? [19:07] the output of /lsusb would be: Bus 002 Device 004: ID 1043:8011 name of the usb stick. but how would i integrate the device id into the mount command? [19:09] try blkid [19:09] sudo blkid [19:10] the usb stick is not listed in blkid [19:10] maybe it has no falesystem? [19:11] filesystem* [19:11] it likely has, there is data on it, probably just not recognised yet [19:11] trylsblk [19:11] lsblk [19:12] probably listed as sr0 [19:12] judging by size, and it's listed as: rom [19:13] try sudo fsck /dev/sr0 [19:13] but I doubt it's your usb [19:13] check logfiles with dmesg or journalctl [19:14] should tell you what's going on there [19:14] yes you can try dmesg | grep "sdb" (or sdc) [19:19] 1) fsck for sr0: fsck.ext2: No medium found while trying to open /dev/sr0 [19:19] 2) dmesg | grep sr0: [ 2.268982] sr 5:0:0:0: [sr0] scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray [19:19] [ 2.269133] sr 5:0:0:0: Attached scsi CD-ROM sr0 [19:19] looks like my cd rom that is not powered, but still inside the tower. [19:20] well, /lsusb clearly shows it though. i wanted to try to mount it by device ID, not a good idea that way? [19:21] journalctl - can't read anything useable from it i'm afraid [19:21] i guess you can't mount it by id [19:22] it's just vendor id and device id whereas you need uuid [19:23] does gparted show it? [19:27] no gparted does not show it, not even as unallocated. [19:27] because your system did not find any block device [19:27] install gnome-disks [19:27] then unplug and reconnect it [19:28] rather use journalctl -f , unplug and plug it back in … then check the journal output [19:28] installing gnome-disks is completely pointless for analysing this issue [19:29] gnome-disk-utility shows as installed in synaptic [19:29] drumcode303, then type in menu disks [19:30] sometimes I had more luck with gnome disks than with gparted [19:31] do i have to do ctrl+c each time the prompt doesn't bring me back to myname@myname:~$ to be able to enter the next command? [19:32] when i do journalctl -f it suspends in the air it seems, ctrl+c brings me back [19:32] drumcode303, you could use a second terminal window? [19:33] but yeah, journalctl -f follows the journal live and requires a manual exit [19:34] ahh ok i see. - want me to copy paste it in here? [19:34] no here, but use https://paste.ubuntu.com/ instead [19:34] and paste the url here [19:37] is it a problem that anyone sees my login name? :f [19:37] better erase before? [19:37] :) we can hack via ssh :) [19:38] that everyone could see* [19:38] https://paste.ubuntu.com/24532508/ [19:38] the device should be /dev/sdd [19:39] but it is lacking partions/file system [19:39] so i go? /mount -t autofs /dev/sdd /mnt/usbstick [19:40] drumcode303, your system did not find something to mount [19:41] there's somthign wrong with the usb stick [19:41] or the file system at least [19:43] i'm sure it was fat32 a year ago [19:44] have you tried mounting it with another computer or operating system? [19:44] drumcode303, if you won't find a workaround for it then, before you go to bed, put your usb stick into the fridge and in the morning try to plug it in again, rumors say it helps or, if it's a firmware failure then you can go to flashboot.ru introduce your VID and PID and see if they have the available recovery software for your device [19:44] mrkramps: no i haven't, will try that next then. [19:45] the fridge workaround sounds lovely :D [19:45] :) [19:46] thanks a lot for your great help guys! [19:46] yw [19:48] disks does recognise at least one of the sticks. [19:51] if you want to look at no.2 :)) https://paste.ubuntu.com/24532585/ [19:52] this second thumb drive is rather new (32GB) the former was very old (512MB) [19:54] mrkramps still around? [19:54] yes, researching … [19:54] awesome! [19:54] gparted error: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. [19:55] i'll try both on windows, brb 10minutes. [20:03] re [20:04] wb [20:04] ty:) [20:05] win recognises the thumb drive, offers to format it, then goes on to say that there is no device in G:/ [20:06] sounds like a hardware issue to me [20:07] other usb pen drives work though, it is just those two that don't [20:07] drumcode303, on windows you can try minitool power ecovery [20:09] can i partition them somehow anyway and waive data recovery? [20:10] drumcode303, with that software is searches for lost partitions and filesystems and recovers your data first, then you can format it [20:10] shouldn't linux be able to that as well/better? [20:11] yes, but you should know how to do that [20:11] i ran testdisk on one of the sticks a week ago, many i/o errors, but i didn't know how to proceed really. [20:13] are you referring to this? http://download.cnet.com/MiniTool-Power-Data-Recovery-Free-Edition/3000-2094_4-10561431.html [20:17] minitool power recovery [20:17] it recovers 1GB for free, what is more you have to pay [20:18] once i got away from windows, i don't really feel like going back there to fix problems with proprietary software :P [20:20] me too, but if you have to recover EXTREMELY important data, then you should, [20:20] mrkramps: any other notion from the last journalctl btw? should I just dump the thumb drives or could it be some usb issue with my hardware? [20:21] going to try a different system anyway before i retire them [20:29] i'd guess the drives are both broken [20:30] you could try some data recovery with gddrescue and running testdisk on the image [20:30] but i'd not expect much [20:31] ok tyvm :) === obscurehero_ is now known as obscurehero === bazhang_ is now known as bazhang