Debian Jessie systemd autologin xfce4 polkit permission fix

9 06 2014

Recently things have changed in regard to policies and the way one logs in.

If your one of the few, like me, who doesn’t use a *dm for login and has suffered the polkit hassle of no suspend/hibernate or shutdown/reboot with Xfce4, there is a simple fix.

Parse a ‘– vt1’ to startx. In your .bashrc or .bash_profile, use the line,

[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx -- vt1

Advertisements




efibootmgr not working as intended.

24 05 2013

I just had a problem where efibootmgr wouldn’t save new boot entries and fail silently.

Running strace efibootmgr, it was saying “no space left on device”

I wont go into details of what’s happening but there’s an easy solution with kernel 3.9 and up.

Launch into the efi shell and add the option “efi_no_storage_paranoia” to your boot options.

Once the system is up and running like normal, you shouldn’t have a problem with efibootmgr anymore.

PROTIP: Add “efi_no_storage_paranoia” to your startup.nsh





Debian systemd autologin without a display manager

28 11 2012

UPDATE:

Create the directory:
sudo mkdir /etc/systemd/system/getty@tty1.service.d

Create file:
sudo vim /etc/systemd/system/getty@tty1.service.d/autologin.conf

Insert:
[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin <username> --noclear %I 38400 linux

ORIGINAL:

I just upgraded Wheezy to systemd which broke my autologin. It’s an easy fix.

Edit the file: ‘/etc/systemd/system/getty.target.wants/getty@tty1.service’

and find the line: ‘ExecStart=-/sbin/agetty %I 38400’

and change to: ‘ExecStart=-/sbin/agetty –noclear -a USERNAME %I 38400’

The –noclear is optional, it prevents the screen from clearing out the console messages.

wiki.debian.org/systemd





rebuilding a mythtv recorded shows database

22 07 2010

Ok, so late one night I decided to upgrade my MythTV server… Yeah, I was bored with my insomnia.. 😉

I’ve kept it with Debian stable throughout the years but this time I wanted to give it lvm and ext4 (squeeze) and decided to jump into testing instead of pining it.

It had been awhile since I backed up my database and yes, I backed up everything to and external HDD but var.. After all, I did want a fresh install and it was late at night. 😛

Well the new installation went well and myth was working nicely but without my recordings that are on a separate drive under xfs. Sure it recorded new shows but bugger it, I wanted my old ones back.. My music and photos came back nicely after I rdiff’d my /home partition but my recordings!!???

Well this is what I did to recover them, google wasn’t so nice this time. 😉

This is on Debian but should give you a rough idea if on another *nix

First off, create a fresh database:

$ cd /usr/share/mythtv/sql

mysql -u root -p < mc.sql

Then restore your backup: 😉
This should work fine if your .mythtv/backuprc is present.

/usr/share/mythtv/mythconverg_restore.pl --filename /path/to/your/<mythtvbackupdir>/mythconverg-xxxxxxxxx.sql.gz

So now we have a working db up until your last backup but what about the rest of the recordings?

Thanks to Greg Froese you’ll find a perl script in /usr/share/doc/mythtv-backend/contrib/recovery/ called myth.rebuilddatabase.pl.gz

gunzip it, chmod 700 myth.re…

Run that with the options you require, I needed –pass and –dir but if you have a default setup you should be fine without any extra options.

As it goes through your recordings, it’ll prompt you for info on the ones it finds that aren’t already in the db. Although you can manually enter the details, which can be a bugger if you can’t remember what it was from the file name, “2099_20100523230000.mpg”,
I found it easier just to “enter” my way through the script and use myth itself, to fill in the blanks.

First off play the file so you can remember what it was exactly then press “M”, -> “recording options”, -> “change recording title” then fill in the title and subtitle for it.

Rinse and repeat.

You’ll now have your Myth back like nothing had gone wrong. 😉

PS. I wrote this down late at night the following night so I might of missed something.. 😛 Let us know if I have. 🙂





Debian lenny with emerald themes for compiz-fusion

11 01 2009

This assumes that you already have Compiz-fusion installed and are after that little extra.

First off, you’ll need to grab the emerald sources, which can be found here:

http://releases.compiz-fusion.org/0.7.6/emerald-0.7.6.tar.bz2

Do your normal unpack, cd, ./configure, make, make install.

That will work but there’s a small tweak needed to get it running. It places the needed libraries into /usr/local/lib.

Check to see that the path is in /etc/ld.so.conf.d/libc.conf. If it is, good, if not, add it. Then run ldconfig as root. It will update the paths and all should be working after that. Check with emerald –replace.





Wine Steam game links

17 10 2008

I recently setup Steam within wine to enjoy hl2 again. All is good except when I notice Trackmania Forever on the main Steam page as a free download. Try as I might the little clicky install thingy wouldn’t do its job.

Having a sniff around, I came across this, comment #2. http://bugs.winehq.org/show_bug.cgi?id=15263

Basically from your browser of choice goto http://store.steampowered.com/

Navigate to the game your after, click on the purchase/install link and that should open up a small popup window asking whether or not you have steam installed. Right click anywhere within that window and choose “view page source”.

Now your after a chunk of code that looks something like this:

<td
        width="260" height="115"
	align="center"
	class="gotSteam_yes" onmouseover="this.className='gotSteam_yes_ovr';" onmouseout="this.className='gotSteam_yes';"
	onclick="opener.location.href='steam://run/11020'; window.close();"
	>Yes, I already have<br>Steam installed!
</td>

The bit that we find interesting is this, “opener.location.href=’steam://run/11020′;

Open that location through wine as noted within the original comment or through Playonlinux like this

playonlinux --run Steam steam://run/11020




Moving from Nvidia to Ati on Linux

19 12 2007

Being a gamer, I use the proprietary Linux drivers and with the recent Ati activity, have found cause to move over.
I’ve just finished my first move and found a few gotchas along the way. Here is a method to avoid them.

1.) Remove the nvidia driver.

As root, run sh NVIDIA-Linux---pkg.run --uninstall

2.) Install the ati driver in the same manner you would a nvidia one. You can get them from here

3.) If all went well, you’ll still need to edit your xorg.conf. Although the ati install had edited it, it still left behind the nvidia parts and didn’t fix the nvidia tweaks.

In Section “Module”, add
Load "GLcore"
Load "dri"

They were removed with the nvidia install.

In Section “Screen”, I found that no modes had been entered.. :/

ie. Modes “1200×1024” “1024×768”

Lastly, you’ll need to re-add the Section “DRI”,

Section "DRI"
Group 100
Mode 0660
EndSection

This assumes your a member of the group users, if not edit /etc/group