[00:16] <pcworld> what do you mean by bootloader
[00:16] <pcworld> @0brienDave
[00:23] <ObrienDave> normally the bootloader, GRUB, is installed to the MBR of the HD. you need to install it ti the USB stick if you want it to boot the system
[00:23] <ObrienDave> *it to
[00:23] <xubuntu42w> There is no updated tutorial on how to exactly partition and install a live persistent USB drive (STEP by STEP)
[00:26] <xubuntu42w> after i choose something else for example..what next
[00:26] <xubuntu42w> "something else"
[07:26] <xubuntu99w> hi all I would like to know how I can create a launcher for xfce-terminal to open a window or tab with ssh to my server similar to this gnome-terminal --disable-factory --sm-client-disable --class=remoteserver -x ssh -t serverip
[07:28] <xubuntu99w> by the way I was reading this post on askubuntu http://askubuntu.com/questions/34597/how-do-i-make-a-custom-launcher-for-terminal-applications
[07:50] <RudyValencia> Hi, is it possible to set up a key shortcut to minimize windows? I couldn't find one in the keyboard shortcuts applet.
[10:26] <synthor> heya
[10:26] <synthor> my xubuntu 14.04 ran fine with two amd graphic cards and two fullhd screens connected to each card with the propritary driver
[10:27] <synthor> this morning installed all updates and now xorg and migration processes have high cpu usage when the machine is just on the desktop
[10:27] <synthor> my mouse and keyboad hangs every few seconds and the system isn't usable at the moment
[10:28] <synthor> booting the last kernel version didn't help
[10:28] <synthor> even reinstalling/upgrading the amd driver
[10:28] <synthor> any hint?
[10:29] <synthor> it's xfce 4.10 btw
[10:55] <synthor> i remember that there was an similar xorg high cpu usage bug...seem to be triggered now again -.-
[10:56] <synthor> glad that i already have two new ssds, where i can install 14.04.3 with xfce 4.12. waste of time to get this fixed again...
[11:00] <RudyValencia> How do I set a keyboard shortcut to minimize a window?
[11:50] <ghostcube> hi, i installed 14.04.03 lts on an HP Compaq nx9030 with intel grafics adapter
[11:51] <ghostcube> dmesg gives me this error [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[11:51] <ghostcube> i tried to fix this with some help threds in arch wiki and the ubuntu community but nothing really made a difference
[11:52] <ghostcube> is there anything further known so far?  this isnt xubuntu related in general. seems to be a kernel or a driver bug.
[15:10] <jrm86> I'm having a bit of trouble with mounting an internal HDD.  Using fstab, It mounts fine in /mnt/, but won't bind to a folder in /home/username/.  I can get it to mount just fine through terminal "sudo mount /home/username/Media/".  Problem is, I'd have to do this every time I log on.  Here is the applicable lines in fstab:  http://pastebin.com/F1hRTZC9 .  Any thoughts?
[15:11] <holstein> i agree, seems like the issue would be with the fstab, then..
[15:12] <jrm86> Odd thing is the first time I changed it, I did a simple "sudo mount -a" after, and it worked fine.  On startup though, no love.
[15:12] <holstein> jrm86: i have one that i added to fstab, and, my lines dont look like that
[15:12] <holstein> well, i think you are sahying "im having issues with an internal HDD mounting".. but, you are not.. you are having issues with adding a drive to fstab, and having it mount to a location, correct?
[15:13] <jrm86> Yes.  It is currently mounted and operational in /mnt/, but it won't bind to a folder in a more convenient location for regular use
[15:13] <holstein> jrm86: i referenced https://help.ubuntu.com/community/InstallingANewHardDrive#Mount_The_Drive when i set mine up..
[15:13] <holstein> jrm86: i didnt use "bind" like that.. i just mounted it at boot, to the location i wanted
[15:14] <holstein> im not saying thats the issue.. but, i have fstab loading several drives on several different machines, to locations inside my /home.. like, ~/Media, and, my fstab looks more like at the wiki page i linked..
[15:15] <jrm86> Yeah, I've read through that page, and I've been able to mount in my home folder, but when I do, it mounts with root permissions, so I can't save to/drag and drop, etc, without altering permissions in terminal every time I log on
[15:16] <holstein> jrm86: there are direction, at at that link, to "chown" the mount point
[15:16] <mrkramps> jrm86, maybe you should change the permission
[15:16] <holstein> jrm86: my internal drive mounts, at boot, to the mount point i desire, via fstab, and has the permissions of my user.. not root.. i dont have to address it at every reboot
[15:18] <jrm86> the wiki talked about "sudo chown...".  I assumed this was to be performed in terminal.  Can those commands be added to fstab?
[15:18] <mrkramps> jrm86, afaik not
[15:18] <mrkramps> the owner of this drive is root
[15:19] <mrkramps> thus only root has r/w permission
[15:20] <mrkramps> i was wrong (as so often) …
[15:21] <genii> You have to make a folder on the root of the drive, chown that to the user you want to have use it. The root of an entire drive will always revert back to being owned by root every boot when it is detected, so changing the permissions of the entire drive only works temporarily
[15:24] <jrm86> It mounts to /mnt/ just fine.  I can read/write to it.  Problem is it won't bind to a directory in my home folder through fstab.  It has to be manually mounted via terminal after each boot (and works fine).  I've tried altering uid, gid, umask, etc in fstab, with no success.  I can mount it wherever I want, but only in /mnt/ am I able to actually use it.
[15:26] <jrm86> That's why I've tried binding the hdd's /mnt/ directory to a directory in my home folder.  It keeps the same permissions, so I can read/write at will
[15:27] <mrkramps> jrm86, you may use a link
[15:31] <holstein> jrm86: what i did was use the link i provided.. i added the lines to fstab, and tested that my drive was auto mounting to the location i wanted.. which, was in my users home
[15:31] <jrm86> Yes, I have already tried that.
[15:31] <holstein> jrm86: i then, use the command at the link, as well, to chown that directory.. giving my user permissions.. i can, now, do what you are trying. which, is hit the power button, wait for the machine to boot, and access the drive, via a directory in my users home, with read/write permissions
[15:32] <holstein> jrm86: you have tried what? what command? i used the "chown" command, at the wiki i linked, on the location.. i used it from the terminal.. its persistent..
[15:33] <jrm86> The link you provided.  I have been through that article days ago.  I've tried everything on that page.
[15:39] <holstein> but, you dont have that refelted in your current fstab..
[15:39] <holstein> oh.. gone already..
[15:45] <mrkramps> whatever
[16:34] <dudeern> has anyone ever experienced a disk mounting on boot, but from the wrong source?  For instance, internal HD "mounts" to correct location, but won't display content, and shows itself as the wrong size disk (same size as the boot disk)?
[16:35] <dudeern> sudo mount -a does not fix it, but does not show an error
[16:36] <dudeern> "sudo mount /mountpoint/" does work, however.  so it's still referencing fstab, since i only specified the destination path
[16:40] <dudeern> http://pastebin.com/F1hRTZC9
[16:52] <dudeern> I'm trying to mount an internal HDD through fstab.  Once booted and on the desktop, my machine recognizes the file path (says that HDD is in the folder where I want it), but it does not show content and it shows information about the boot partition (size, available space, etc).  Almost like it mounted the filepath, but not the drive.  "sudo mount -a" does not change it, but "sudo mount /destinationpath/" does.  The documentation on "moun
[16:52] <dudeern> t" says that if only specifying a source or destination (not both), then "mount" references fstab to mount the drive.  So fstab works, but it is not mounting correctly at boot.  Any thoughts?  Here is the applicable line from fstab:  http://pastebin.com/F1hRTZC9
[17:03] <holstein> dudeern: if i saw issues like, the drive size not reporting correctly, i would test the drive
[17:04] <holstein> dudeern: i like using gsmartcontrol
[17:05] <dudeern> it doesn't, at first, but when I run "sudo mount /mountlocation/", it mounts just fine, can read/write, and shows correct drive size
[17:05] <holstein> i would break up the steps.. i would remove the fstab entry.. test the drive, and make sure its working, and doesnt have errors. then, i would simply try mounting it, and read/write to it
[17:05] <dudeern> ok
[17:05] <holstein> *then*, after all of that is working properly, i would seperately deal with fstab, to get persistent boot.. going forward knowing that the drive is "good"..
[17:06] <dudeern> ok, I can give that a try
[17:10] <dudeern> scan turned out fine.  no errors
[17:11] <holstein> dudeern: sure.. and, the scan i like to do, takes a few hours. but, thats a good start
[17:11] <dudeern> do you want a screenshot?
[17:11] <holstein> now, i would either, do the longer scan, or, i would make it so that i can reliably mount, read/write.. and them move, after that is happening, either, in the command line, or, in the file manager
[17:12] <holstein> dudeern: no
[17:12] <holstein> dudeern: i understand. and i said, thats a good start. but, there are tests that do more. and, you still dont know if the file system is ok.. but, its really up to you how you want to proceed
[17:13] <holstein> i typically pull a drive down, and test it, at least as much as you have, and fresh format. i dont know the history of your drive.. im just noticing that, you are trying to implement fstab auto mounting at boot with read/write permissions for your user, and are not really simply able to reliable mount the drive *before* implementing that.. so, i would work with the mounting, and make sure that works, *then* move on
[17:14] <dudeern> I can mount via command line in the correct location.  I can read and write to the disk.  This disk itself behaves correctly.  The disk shows correct information about itself.
[17:14] <holstein> then, you are not having issues with mounting, or read/write.. etc.. correct?
[17:15] <holstein> the *only* issue you have is with trying to implement the auto-loading of it, in fstab? correct?
[17:16] <dudeern> correct.  When using "sudo mount /mountLocation/", it works completely fine.  The documentation for "mount" says that when specifying only a drive OR a location, it references fstab, and in practice, it works
[17:16] <dudeern> it just won't do it on boot
[17:17] <holstein> dudeern: then, i would look at my fstab.. i would look at this, and follow it more closely https://help.ubuntu.com/community/InstallingANewHardDrive#Automatic_Mount_At_Boot
[17:18] <dudeern> I have.  I've read it line by line and followed directions carefully.  I've checked other support sites and found the same information which did not help.  I'm here because I couldn't find an answer.
[17:18] <holstein> dudeern: the fstab you shared doesnt look the same, though
[17:19] <holstein> dudeern: share more details, and a volunteer may assist. your full fstab, and the filesystem information.. etc
[17:19] <dudeern> It's different because the original from the support site you suggested didn't work
[17:20] <holstein> dudeern: sure, and i understand what you are saying, but, thats literally the same guide i followed, that did work, so, i would need more details about what isnt working, and how.. such as, the fstab file
[17:20] <dudeern> I'll need a minute to copy it over
[17:22] <holstein> when you get the details together, if its slow here, and no one is answering, you can use #ubuntu, since, its not related to xubuntu or xfce..
[17:27] <dudeern> fstab:  http://pastebin.com/TLAHwzZM
[17:28] <dudeern> what else do you need?
[17:28] <holstein> also, what is the output of sudo fdisk -l
[17:29] <dudeern> fdisk:  http://pastebin.com/hvbpKSmp
[17:30] <dudeern> sdb1 what is giving me a headache
[17:30] <holstein> dudeern: /dev/sdb1            2048  3907029167  1953513560   83  Linux ..that *is* the device? correct? and its formatted to what? ext4? ext3? you did that in gparted?
[17:31] <dudeern> ext4, formatted via command-line
[17:31] <holstein> dudeern: i dont think it is "sdb1" that is giving you a headache, at all.. if you can mount that location manually.. its fstab that is the issue..
[17:32] <holstein> dudeern: you are *certain*, that, if you comment out that fstab line, and reboot the machine, you would see the drive in the filemanager, and be able to click on it, and mount, and be able to read it? and, if you use sudo mount, it'll mount, and you have read/write to it?
[17:32] <dudeern> yes
[17:33] <dudeern> i've done it many times before
[17:35] <holstein> dudeern: im not sure that it matters, but, you have a trailing "/" in your path, in your fstab.. that is not present in mine, or the guide you are referencing
[17:35] <holstein> it wouldnt hurt to, confirm the location is there.. and, reference it as "/home/jonathan/Media" rather than "/home/jonathan/Media/"
[17:35] <dudeern> I've done it manually (specifying drive AND mount location), and using fstab after boot (specifying only mount location, which forces "mount" to reference fstab)
[17:36] <dudeern> I thought about that and tried it, but it did not change the result
[17:36] <holstein> sure.. i would update that, now, though, and make it reflect the actual mountpoint
[17:37] <holstein> dudeern: right now, fstab is pointing to /home/jonathan/Media/ and not /home/jonathan/Media ... which could make the difference..
[17:38] <dudeern> ok.  I'll try it again.
[17:42] <dudeern> no change
[17:42] <holstein> when? when, rebooting? or, trying a manual command? and what errors are you getting? if any?
[17:43] <dudeern> reboot, and literally no difference.  boots up, disk shows correct file path, but no content.  manual "sudo mount /mountLocation/" command, then everything works
[17:44] <holstein> i remember *not* referring to the label, since, they can change
[17:44] <holstein> did the labels change?
[17:44] <holstein> anyways, this looks like what i would step through.. https://help.ubuntu.com/community/MountDevicesTroubleshooting
[17:45] <holstein> i do prefer by uuid..
[17:47] <dudeern> the labels did not change.  I've already referenced this link also.  This is just sending me back to troubleshooting in circles while expecting a different result.  Thanks, I appreciate your time.
[22:19] <cristi> hello
[22:19] <cristi> i have a problem
[22:19] <cristi> can anyone help ?
[22:19] <Guest17095> helo
[22:20] <Guest17095> i get no audio after some use of a fresh install xubuntu 15.4
[22:20] <Guest17095> can anyone help ?
[22:21] <Guest17095> is someone here ?
[22:23] <Guest17095> hellloooo
[22:23] <mariano> I'm having trouble installing my bluetooth keyboard on xubuntu 15.04. I had it working on xubuntu 14.04 but the tutorial I followed no longer works.
[22:24] <Guest17095> i think no one will help us here ...
[22:24] <mariano> People are probably busy or idle. It is volunteer work after all.
[22:28] <drc> mariano: I take it you have googled and found no answer for your particular situation?
[22:29] <mariano> I had, but it no longer works on 15.04 because bluez-hcidump is no longer part of 15.04 I think.
[22:30] <mariano> can I put a link of the tutorial that worked for ubuntu 14.04?
[22:32] <drc> Sure...I have no knowledge of bluetooth myself, but some who does may see it.
[22:32] <mariano> I used the following tutorial successfully in xubuntu 14.04 : http://blog.chschmid.com/?p=1537