Hi Hartmut,
first of all, thanks for your reply! I guess i have to save the „runeonce“ code as a new library in /usr/share/awesome/lib?
I did this, added the code you provided at the end of my rc.lua but got no effect save the tags in the panel appeared twice.
Sorry if i seem a bit clumsy, maybe i am missing something essential here.

Is it necessary to install gnome if i want to run the applet?


Thank you,
Levent


On 29.02.2012 20:17, Hartmut Bischoff wrote:

Hi,

I did the same:
Installed Ubuntu, ran gnome and installed awesome.
In Gnome, I could access the nm-applet.
Same in awesome, providing this in the rc.lua

local r = require("runonce")
r.run("nm-applet")
r.run("gnome-power-manager")
r.run("dropbox start -i")
r.run("/usr/lib/gnome-disk-utility/gdu-notification-daemon")
r.run("firefox")


where "runconce" is
-- <at> author Peter J. Kranz (Absurd-Mind, peter <at> myref.net)
-- Any questions, criticism or praise just drop me an email

local M = {}

-- get the current Pid of awesome
local function getCurrentPid()
    -- get awesome pid from pgrep
    local fpid = io.popen("pgrep -u " .. os.getenv("USER") .. " -o awesome")
    local pid = fpid:read("*n")
    fpid:close()

    -- sanity check
    if pid == nil then
        return -1
    end

    return pid
end

local function getOldPid(filename)
    -- open file
    local pidFile = io.open(filename)
    if pidFile == nil then
        return -1
    end
   
    -- read number
    local pid = pidFile:read("*n")
    pidFile:close()
       
    -- sanity check
    if pid <= 0 then
        return -1
    end
       
    return pid;
end
       
local function writePid(filename, pid)
    local pidFile = io.open(filename, "w+")
    pidFile:write(pid)
    pidFile:close()
end

local function shallExecute(oldPid, newPid)
    -- simple check if equivalent
    if oldPid == newPid then
        return false
    end

    return true
end

local function getPidFile()
    local host = io.lines("/proc/sys/kernel/hostname")()
    return awful.util.getdir("cache") .. "/awesome." .. host .. ".pid"
end

-- run Once per real awesome start (config reload works)
-- does not cover "pkill awesome && awesome"
function M.run(shellCommand)
    -- check and Execute
    if shallExecute(M.oldPid, M.currentPid) then
        awful.util.spawn_with_shell(shellCommand)
    end
end


have fun!


--
Dr. Hartmut Bischoff
Stuttgart

Hi again,
you don't need to bother anymore, i just solved the problem. I don't know if this is a bug, but it seems to be an issue with the rights administration. If i run nm-connection-editor with root permission i get the necessary menu with the option to enter my wlan-password.
Strange enough, since i already added myself to the network group, but at least it works!
Greetings,
Levent

On 29.02.2012 20:17, Hartmut Bischoff wrote:

Hi,

I did the same:
Installed Ubuntu, ran gnome and installed awesome.
In Gnome, I could access the nm-applet.
Same in awesome, providing this in the rc.lua

local r = require("runonce")
r.run("nm-applet")
r.run("gnome-power-manager")
r.run("dropbox start -i")
r.run("/usr/lib/gnome-disk-utility/gdu-notification-daemon")
r.run("firefox")


where "runconce" is
-- <at> author Peter J. Kranz (Absurd-Mind, peter <at> myref.net)
-- Any questions, criticism or praise just drop me an email

local M = {}

-- get the current Pid of awesome
local function getCurrentPid()
    -- get awesome pid from pgrep
    local fpid = io.popen("pgrep -u " .. os.getenv("USER") .. " -o awesome")
    local pid = fpid:read("*n")
    fpid:close()

    -- sanity check
    if pid == nil then
        return -1
    end

    return pid
end

local function getOldPid(filename)
    -- open file
    local pidFile = io.open(filename)
    if pidFile == nil then
        return -1
    end
   
    -- read number
    local pid = pidFile:read("*n")
    pidFile:close()
       
    -- sanity check
    if pid <= 0 then
        return -1
    end
       
    return pid;
end
       
local function writePid(filename, pid)
    local pidFile = io.open(filename, "w+")
    pidFile:write(pid)
    pidFile:close()
end

local function shallExecute(oldPid, newPid)
    -- simple check if equivalent
    if oldPid == newPid then
        return false
    end

    return true
end

local function getPidFile()
    local host = io.lines("/proc/sys/kernel/hostname")()
    return awful.util.getdir("cache") .. "/awesome." .. host .. ".pid"
end

-- run Once per real awesome start (config reload works)
-- does not cover "pkill awesome && awesome"
function M.run(shellCommand)
    -- check and Execute
    if shallExecute(M.oldPid, M.currentPid) then
        awful.util.spawn_with_shell(shellCommand)
    end
end


have fun!


--
Dr. Hartmut Bischoff
Stuttgart

On 03/01/2012 09:05 AM, Levent S.B. wrote:

Hi Hartmut,
first of all, thanks for your reply! I guess i have to save the „runeonce“ code as a new library in /usr/share/awesome/lib?
I did this, added the code you provided at the end of my rc.lua but got no effect save the tags in the panel appeared twice.
Sorry if i seem a bit clumsy, maybe i am missing something essential here.

Is it necessary to install gnome if i want to run the applet?


Thank you,
Levent

Hello Levent,

Which version of Awesome do you use? Tags appearing twice actually mean that Awesome tried to load your ~/.config/awesome/rc.lua, failed midway and then loaded /etc/xdg/awesome/rc.lua as a fallback. If your Awesome version is 3.4.11 then you should see a red box in the right top informing you what actually crashed. You can also look for errors in the file ~/.xsession-errors.

That was just FYI. I don't think adding "runonce" module to Awesome would fix your problem. And I am pretty much not sure what you can with NM but to suggest trying wicd. Wicd is better then NM because it works like a daemon (so the X session is not required for it to work - you'll have your connection as soon as system loads) and has different clients to manage it (wicd-curses - terminal client, wicd-gtk - GUI one). You'll find the daemon and clients in the Ubuntu repository.

Keep us informed about your progress,

Best regards,
Alexander

Hi Alexander,
i'm running awesome 3.4.10-1, installed from the ubuntu 11.10 amd64 repos on an ubuntu 11.10 64-bit minimal installation.
As i wrote in my last mail (i hope you got it?), i can access the menu by running sudo nm-connection-manager (without sudo it opens as well, but i'm not allowed to edit anything).
Nevertheless, i'm going to try wicd as soon as i have the time :)
Thanks for the info,
Levent


On 01.03.2012 08:50, Alexander Yakushev wrote:

On 03/01/2012 09:05 AM, Levent S.B. wrote:

Hi Hartmut,
first of all, thanks for your reply! I guess i have to save the „runeonce“ code as a new library in /usr/share/awesome/lib?
I did this, added the code you provided at the end of my rc.lua but got no effect save the tags in the panel appeared twice.
Sorry if i seem a bit clumsy, maybe i am missing something essential here.

Is it necessary to install gnome if i want to run the applet?


Thank you,
Levent

Hello Levent,

Which version of Awesome do you use? Tags appearing twice actually mean that Awesome tried to load your ~/.config/awesome/rc.lua, failed midway and then loaded /etc/xdg/awesome/rc.lua as a fallback. If your Awesome version is 3.4.11 then you should see a red box in the right top informing you what actually crashed. You can also look for errors in the file ~/.xsession-errors.

That was just FYI. I don't think adding "runonce" module to Awesome would fix your problem. And I am pretty much not sure what you can with NM but to suggest trying wicd. Wicd is better then NM because it works like a daemon (so the X session is not required for it to work - you'll have your connection as soon as system loads) and has different clients to manage it (wicd-curses - terminal client, wicd-gtk - GUI one). You'll find the daemon and clients in the Ubuntu repository.

Keep us informed about your progress,

Best regards,
Alexander

My external monitor is already set as primary (at least it is screen 1
for awesome). But my urxvts act as if they are stuck on the laptop
screen (as if there tag table contain screen.count instead of "1").
Yes, I could also disable the laptop screen but I like to keep a root
term there and a few other dedicated apps (which behave well with
awesome).