[Solved] Clang "-cc1" not recognized

The clang front-end "-cc1" simply does not work. I have tested with clang 3.5 and 3.6.
$ clang -cc1 --
clang: error: unknown argument: '-cc1'
clang: error: no input files
Same for some others:
clang: error: unknown argument: '-cl-kernel-arg-info'
clang: error: unknown argument: '-cl-std=CL1.2'
clang: error: unknown argument: '-triple'
Is that only me, or Archlinux's clang is acting weird?
Last edited by jiehong (2015-05-19 17:00:33)

Works for me, in the sense that it grabs stdin and tries to execute whatever I've typed when I press ctrl+d.
This cc1 switch doesn't appear to be documented in the man page though, and this page suggests that it's not supposed to be used directly:
Users should not run clang -cc1 directly, because -cc1 options are not guaranteed to be stable
Is this an X-Y problem? What are you trying to do?
I'm not sure why the -cc1 switch doesn't work for you, have you set up an alias? What does 'type clang' return?
Edit: Mod note: Moving to Programming and Scripting
Last edited by WorMzy (2015-05-19 15:12:27)

Similar Messages

[solved] Digital Camera not recognized in device-manager

My digital camera "Canon Powershot SX120 is" is not recognized by the devicemanager. I have read Digital Cameras.
$ groups
wheel storage users printadmin
The "camera"-Group isn't needed anymore and this group doesn't exist on my system.
The Powershot SX 120 has a MTP/PTP connection mode (as the manual says). But:
# mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
No raw devices found.
gphoto succeed:
$ gphoto2 --auto-detect
Modell Port
Canon PowerShot SX120 IS usb:002,019
A gphoto --summary could be found here
There is no udev-rule for this camera. If i create one while copying a rule from a similar camera from /etc/udev/rules.d/69-libmtp.rules, and store it into /etc/udev/rules.d/69-canon.rules, the device-manager shows up. My udev-rule:
# Canon PowerShot SX120AX (PTP/MTP mode)
ATTR{idVendor}=="04a9", ATTR{idProduct}=="31e0", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
The device-manager shows me only the option to open with a file-manager. Doing so will result in an error:
The file or folder udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:02.1/usb2/2-8/ do not exist.
With my udev-rule:
solid-hardware listen
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
Listening to add/remove events:
Device Added:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:02.1/usb2/2-8'
Without the active udev-rule, "solid-hardware listen" produces nothing, but
udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[5077.662572] add /devices/pci0000:00/0000:00:02.1/usb2/2-8 (usb)
KERNEL[5077.662655] add /devices/pci0000:00/0000:00:02.1/usb2/2-8/2-8:1.0 (usb)
UDEV [5077.681178] add /devices/pci0000:00/0000:00:02.1/usb2/2-8 (usb)
UDEV [5077.693035] add /devices/pci0000:00/0000:00:02.1/usb2/2-8/2-8:1.0 (usb)
Don't know what to do ... is a udev-rule necessary to bring up the message from device-manger? Or is the Camera not recognized as a mtp-device (the Camera has no such settings)? How could i figure it out?
With Digikam i could import Fotos, but i would do so with gwenview. I've tried to check it out with gwenview_importer:
$ gwenview_importer --udi '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:02.1/usb2/2-8'
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
gwenview_importer: Missing required source folder argument.
(don't care about the different udi, i took this example from a former try) but i don't know, how to find out where the "source folder" is ...
Last edited by quiqueck (2014-02-26 20:10:25)

I have solved this by making an extra udev-rule for my camera. See my adventure on forum.kde.org for details

[SOLVED]Hard Disk not recognized when installing

Hey all, I'm just starting with Arch and I've had some trouble installing it on my Acer netbook.
My first installation went well except that I had forgot to download the wireless tools so I decided to do a fresh install as I had no access to a wired connection at the time. The second installation attempt must have had some error on my part as Arch failed to start after selecting it from Grub, saying that the kernel was not available/not recognized.
Now my subsequent attempts at installing have failed because the hard disk is not recognized when running either cgdisk or cfdisk. Instead of showing my hard drive partitions after running
cfdisk /dev/sda
it shows my usb drive. If I instead use
cgdisk /dev/sda
it displays an error saying that the disk is damaged or not recognized. When I first saw this I thought my disk was failing, so I tried #! to see if it would show the same error, but it was able to recognize the entire disk and install correctly. Now, even after having the entire disk formatted as ext4 with #! installed, cgdisk is still giving me the same error about a damaged disk.
Am I doing something incorrectly or is there a fix for this? I haven't been able to find any information about this after a good while of searching.
Thanks for your help.
Last edited by Forest_Leaves (2013-03-05 08:30:24)

srs5694 wrote:The cgdisk "damaged disk" error is probably a result of the tool seeing an MBR partition table on your USB flash drive, rather than the GPT disk it's expecting. If I'm right, you should not follow s1ln7m4s7r's advice, since that will simply trash your USB flash drive!
If you mean by trashing the USB flash drive, that it will delete all data and partitions on the selected drive it is correct, because:
dd if=/dev/zero of=/dev/$disk bs=4096 count=1
- this will delete all partition-table data
sgdisk -o /dev/$disk
- this will clear out all data. This includes GPT header data, all partition definitions, and the protective MBR.
/dev/$disk
- this will make you enter ncurses-based GUID partition table (GPT) manipulator, where you can create new partitions
You should only do this if you are certain of what disk it is.
Now if when you said this, you were meaning it will became broken, then it may be a special kind of usb drive because i've donne it many times and i've not broken any.
srs5694 wrote:My guess is that either your hard disk has become /dev/sdb (this can happen in some cases; disk identifiers aren't really fixed) or you're missing a driver for your hard disk controller because you've booted a different kernel or a different initrd file. Another possibility is that there's a hardware fault -- probably a loose cable -- that's preventing the kernel from seeing the disk.
If the usb drive is not where you installed arch, then you need to find if there are more recognized drives:
lsblk | grep disk
And see the uuid of the root partition you want, and add it to your bootloader boot line:
blkid /dev/sdxx
Last edited by s1ln7m4s7r (2013-03-04 19:17:36)

[SOLVED] ssh-passphrase not recognized by ssh-agent

After an upgrade yesterday, I cannot enter my system anymore. It boots with some (rapidly passing) error messages (related to AF_UNIX) and shows me the login prompt. But fontsize isn't the one I had before, and customized keymappings of my keyboard are missing. Thus my configurations for the console have not been read.
Then I can successfully enter my login and password - but not the ssh-passphrase asked for by ssh-agent. I typed it many times, it must be correct, but is not recognized anymore. So at this point I'm stuck. I rebooted and tried fallback Arch - with the same result.
Then I chose the grub> shell during boot, and tab gave me a list of available commands. But I don't know what to do now.
So my question is:
how can I enter my system besides the ssh-passphrase problem? And if I managed to get into the system again - what might be the cause of this problem?
EDIT:
Ok, I tried to enter my pass-phrase as if I had an US keyboard (I have a German keyboard) and that worked. Now I can enter my system again, so I close this question. Maybe I will open another question soon, related to the root-cause of the problem (why my configuration isn't loaded on startup).
Last edited by 4on6 (2012-11-29 11:35:01)

After an upgrade yesterday, I cannot enter my system anymore. It boots with some (rapidly passing) error messages (related to AF_UNIX) and shows me the login prompt. But fontsize isn't the one I had before, and customized keymappings of my keyboard are missing. Thus my configurations for the console have not been read.
Then I can successfully enter my login and password - but not the ssh-passphrase asked for by ssh-agent. I typed it many times, it must be correct, but is not recognized anymore. So at this point I'm stuck. I rebooted and tried fallback Arch - with the same result.
Then I chose the grub> shell during boot, and tab gave me a list of available commands. But I don't know what to do now.
So my question is:
how can I enter my system besides the ssh-passphrase problem? And if I managed to get into the system again - what might be the cause of this problem?
EDIT:
Ok, I tried to enter my pass-phrase as if I had an US keyboard (I have a German keyboard) and that worked. Now I can enter my system again, so I close this question. Maybe I will open another question soon, related to the root-cause of the problem (why my configuration isn't loaded on startup).
Last edited by 4on6 (2012-11-29 11:35:01)

[SOLVED] Sound Card not recognized on Macbook (5,1)

Hello,
I had no problems installing Archlinux on my Macbook (5,1). In fact, the first time I followed the Wiki's instructions for installing ALSA, I could play sounds just fine. However, ever since my first restart, the ALSA daemon complains that I have no sound cards installed. lspci shows that it sees an audio device, but /sys/modules/snd no longer exists. I do not know much about useful diagnostic information for this situation, so please let me know what else could be of use.
Thank you,
Rob
Last edited by rennis250 (2009-07-28 20:58:00)

I had forgotten that I installed OSS, which caused conflicts with a previously installed copy of ALSA. Once I removed OSS completely, rebooted, and went through the ALSA setup again, I had fully working sound. This problem can be marked as solved.
--Rob

[SOLVED] Sound card not recognized

I tried following the ALSA setup guide on the Wiki to get my sound working but I don't think Arch recognizes my sound card. I found out from lshwd that the module is snd-intel8x0 so I modprobed that and snd-pcm-oss, changed the values in alsamixer, added myself to the audio group, installed alsa-utils, alsa-lib and alsa-oss and restarted everything but I still have no sound. Here's some output:
lsmod | grep '^snd'
snd_intel8x0 28700 1
snd_ac97_codec 95780 1 snd_intel8x0
snd_pcm_oss 38688 0
snd_pcm 69124 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_seq_device 6796 0
snd_mixer_oss 14592 1 snd_pcm_oss
snd_timer 19076 1 snd_pcm
snd 44516 9 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_pcm,snd_seq_device,snd_mixer_oss,snd_timer
snd_page_alloc 7816 2 snd_intel8x0,snd_pcm
ls -l /dev/snd
total 0
crw-rw---- 1 root audio 116, 0 2007-07-12 21:35 controlC0
crw-rw---- 1 root audio 116, 24 2007-07-12 21:35 pcmC0D0c
crw-rw---- 1 root audio 116, 16 2007-07-12 21:35 pcmC0D0p
crw-rw---- 1 root audio 116, 25 2007-07-12 21:35 pcmC0D1c
crw-rw---- 1 root audio 116, 26 2007-07-12 21:35 pcmC0D2c
crw-rw---- 1 root audio 116, 27 2007-07-12 21:35 pcmC0D3c
crw-rw---- 1 root audio 116, 20 2007-07-12 21:35 pcmC0D4p
crw-rw---- 1 root audio 116, 33 2007-07-12 13:02 timer
The wiki says that if you have controlC0 and pcmC0D0p in that output then the modules have been loaded properly and they are both there so I'm not sure where to go from here. Your help would be appreciated.
Last edited by Thrillhouse (2007-07-12 22:23:29)

you need to start alsa if you haven't already done so... /etc/alsa start
prolly better to run alsacoconf if you still have problems

[SOLVED] Awesome is not recognizing widgets

Hey everybody,
So this is my first (non-virtualbox) arch install. I just switched over from crunchbang. I had awesome installed on crunchbang and used that as my primary window manager. So I saved all of my configs and everything so that I could use them on arch. I got arch installed and then awesome, and awesome works well. I am using it right now. But as soon as I started trying to add widgets it wouldn't let me. Every time I restart it awesome reverts to the rc.lua in /etc/xdg... and gives me a warning message saying:
Oops, there were errors during startup!
/home/nathan/.config/awesome/rc.lua:117: attempt to call global 'widget' (a nil value)
The line it is referring to is this:
separator = widget({ type = "textbox" })
Also, all of the requires at the top currently look like this:
-- Standard awesome library
local gears = require("gears")
local awful = require("awful")
awful.rules = require("awful.rules")
require("awful.autofocus")
-- Widget and layout library
wibox = require("wibox")
-- Theme handling library
local beautiful = require("beautiful")
-- Notification library
local naughty = require("naughty")
local menubar = require("menubar")
So I tried to google and search the awesome wiki and the arch wiki for how it is done on arch. From everything I have found I am doing it correctly, but I must be missing something. One thought was that it might be a result of the most recent awesome update. I think it was on the 4th. Any ideas?
Last edited by nhare330 (2013-01-09 00:21:05)

Here it is. My rc.lua:
-- Standard awesome library
local gears = require("gears")
local awful = require("awful")
awful.rules = require("awful.rules")
require("awful.autofocus")
-- Widget and layout library
local wibox = require("wibox")
local vicious = require("vicious")
-- Theme handling library
local beautiful = require("beautiful")
-- Notification library
local naughty = require("naughty")
local menubar = require("menubar")
-- {{{ Error handling
-- Check if awesome encountered an error during startup and fell back to
-- another config (This code will only ever execute for the fallback config)
if awesome.startup_errors then
naughty.notify({ preset = naughty.config.presets.critical,
title = "Oops, there were errors during startup!",
text = awesome.startup_errors })
end
-- Handle runtime errors after startup
do
local in_error = false
awesome.connect_signal("debug::error", function (err)
-- Make sure we don't go into an endless error loop
if in_error then return end
in_error = true
naughty.notify({ preset = naughty.config.presets.critical,
title = "Oops, an error happened!",
text = err })
in_error = false
end)
end
-- {{{ Variable definitions
-- Themes define colours, icons, and wallpapers
beautiful.init("/usr/share/awesome/themes/zenburn/theme.lua")
-- This is used later as the default terminal and editor to run.
terminal = "lxterminal"
editor = os.getenv("EDITOR") or "nano"
editor_cmd = terminal .. " -e " .. editor
-- Default modkey.
-- Usually, Mod4 is the key with a logo between Control and Alt.
-- If you do not like this or do not have such a key,
-- I suggest you to remap Mod4 to another key using xmodmap or other tools.
-- However, you can use another modifier like Mod1, but it may interact with others.
modkey = "Mod4"
-- Table of layouts to cover with awful.layout.inc, order matters.
local layouts =
awful.layout.suit.floating,
awful.layout.suit.tile,
awful.layout.suit.tile.left,
awful.layout.suit.tile.bottom,
awful.layout.suit.tile.top,
awful.layout.suit.fair,
awful.layout.suit.fair.horizontal,
awful.layout.suit.spiral,
awful.layout.suit.spiral.dwindle,
awful.layout.suit.max,
awful.layout.suit.max.fullscreen,
awful.layout.suit.magnifier
-- {{{ Wallpaper
if beautiful.wallpaper then
for s = 1, screen.count() do
gears.wallpaper.maximized(beautiful.wallpaper, s, true)
end
end
-- {{{ Tags
-- Define a tag table which hold all screen tags.
tags = {
names = { "➊ ", "➋ ", "➌ ", "➍ ", "➎ ", "◌ " },
layout = { layouts[2], layouts[10], layouts[10], layouts[1], layouts[1], layouts[10]
for s = 1, screen.count() do
-- Each screen has its own tag table.
tags[s] = awful.tag(tags.names, s, tags.layout)
end
-- {{{ Menu
-- Create a laucher widget and a main menu
myawesomemenu = {
{ "manual", terminal .. " -e man awesome" },
{ "edit config", editor_cmd .. " " .. awesome.conffile },
{ "restart", awesome.restart },
{ "quit", awesome.quit }
mymainmenu = awful.menu({ items = { { "awesome", myawesomemenu, beautiful.awesome_icon },
{ "open terminal", terminal }
mylauncher = awful.widget.launcher({ image = beautiful.awesome_icon,
menu = mymainmenu })
-- Menubar configuration
menubar.utils.terminal = terminal -- Set the terminal for applications that require it
-- {{{ Wibox
-- Separator
separator = wibox.widget.textbox()
separator:set_text(" | ")
-- Spacer
spacer = wibox.widget.textbox()
spacer:set_text(" ")
-- Network usage widget
netwidget = wibox.widget.textbox()
vicious.register(netwidget, vicious.widgets.net, '${eth0 down_kb} ${eth0 up_kb}', 3)
-- Memory widget
memwidget = wibox.widget.textbox()
memwidget_t = awful.tooltip({ objects = {memwidget}, })
vicious.register(memwidget, vicious.widgets.mem,
function (widget, args)
memwidget_t:set_text(' mem: ' ..args[2].. '/' ..args[3].. 'mb \n free: ' ..args[4].. 'mb \n swap: ' ..args[5].. '% > ' ..args[6].. '/' ..args[7].. 'mb \n free: ' ..args[8].. 'mb ')
return '▣ ' ..args[1].. '%'
end, 3)
-- Cpu widget
cpuwidget = wibox.widget.textbox()
cpuwidget_t = awful.tooltip({ objects = {cpuwidget}, })
vicious.register(cpuwidget, vicious.widgets.cpu,
function (widget, args)
cpuwidget_t:set_text(' cpu0: ' ..args[2].. '% \n cpu1: ' ..args[3].. '% ')
return '◈ ' ..args[1].. '%'
end, 3)
-- Battery widget
batwidget = wibox.widget.textbox()
batwidget_t = awful.tooltip({ objects = {batwidget}, })
vicious.register(batwidget, vicious.widgets.bat,
function (widget, args)
batwidget_t:set_text(' ' ..args[3].. ' ')
return '↯ ' ..args[1].. '' ..args[2].. ''
end, 14, "BAT0")
-- Keyboard widget
kbdcfg = {}
kbdcfg.cmd = "setxkbmap"
kbdcfg.layout = { "us", "es" }
-- kbdcfg.us = "us"
-- kbdcfg.es = "es"
kbdcfg.current = 1
kbdcfg.widget = wibox.widget.textbox({ align = "right" })
kbdcfg.widget:set_text( kbdcfg.layout[kbdcfg.current] )
kbdcfg.switch = function ()
kbdcfg.current = kbdcfg.current % #(kbdcfg.layout) + 1
local t = kbdcfg.layout[kbdcfg.current]
kbdcfg.widget:set_text( t )
os.execute( kbdcfg.cmd .. t )
end
kbdcfg.widget:buttons(awful.util.table.join(
awful.button({ }, 1, function () kbdcfg.switch() end )
-- Wifi
wifiwidget = wibox.widget.textbox()
wifiwidget_t = awful.tooltip({ objects = {wifiwidget}, })
vicious.register (wifiwidget, vicious.widgets.wifi,
function (widget, args)
wifiwidget_t:set_text(' ' ..args["{ssid}"].. ' \n mode: ' ..args["{mode}"].. ' \n chan: ' ..args["{chan}"].. ' \n sign: ' ..args["{sign}"].. ' \n rate: ' ..args["{rate}"].. ' ')
-- ' \n rate: ' ..args["{rate}"].. ' \n linp: ' ..args["{linp}"]..
return '⇄ ' ..args["{link}"].. '%'
end, 7, "wlan0")
-- File System
fswidget = wibox.widget.textbox()
fswidget_t = awful.tooltip({ objects = {fswidget}, })
vicious.register(fswidget, vicious.widgets.fs,
function (widget, args)
fswidget_t:set_text('used: ' ..args["{/ used_gb}"].. '/' ..args["{/ size_gb}"].. 'gb ')
return '◕ ' ..args["{/ avail_gb}"].. 'gb'
end, 61)
-- Uptime
uptimewidget = wibox.widget.textbox()
uptimewidget_t = awful.tooltip({ objects = {uptimewidget}, })
vicious.register(uptimewidget, vicious.widgets.uptime,
function (widget, args)
uptimewidget_t:set_text(' ' ..args[1].. 'd ' ..args[2].. ':' ..args[3].. ' ')
return string.format('⇑ ' ..args[1].. 'd')
end, 61)
-- Volume Widget
volumecfg = {}
volumecfg.cardid = 0
volumecfg.channel = "Master"
volumecfg.widget = wibox.widget.textbox({ align = "right" })
-- volumecfg_t = awful.tooltip({ objects = { volumecfg.widget },})
-- volumecfg_t:set_text("volume")
-- command must start with a space!
volumecfg.mixercommand = function (command)
local fd = io.popen("amixer -c " .. volumecfg.cardid .. command)
local status = fd:read("*all")
fd:close()
local volume = string.match(status, "(%d?%d?%d)%%")
volume = string.format("% 3d", volume)
status = string.match(status, "%[(o[^%]]*)%]")
if string.find(status, "on", 1, true) then
volume = "◄ " .. volume .. ""
else
volume = "⋪ " .. volume .. ""
end
volumecfg.widget:set_text( volume )
end
volumecfg.update = function ()
volumecfg.mixercommand(" sget " .. volumecfg.channel)
end
volumecfg.up = function ()
volumecfg.mixercommand(" sset " .. volumecfg.channel .. " 1%+")
end
volumecfg.down = function ()
volumecfg.mixercommand(" sset " .. volumecfg.channel .. " 1%-")
end
volumecfg.toggle = function ()
volumecfg.mixercommand(" sset " .. volumecfg.channel .. " toggle")
end
volumecfg.widget:buttons({
button({ }, 4, function () volumecfg.up() end),
button({ }, 5, function () volumecfg.down() end),
button({ }, 1, function () volumecfg.toggle() end)
volumecfg.update()
-- Date widget
datewidget = wibox.widget.textbox()
vicious.register(datewidget, vicious.widgets.date, ' %a. %b %d, %l:%M %p ', 5)
-- Create a textclock widget
mytextclock = awful.widget.textclock({ align = "right" })
-- Calendar widget to attach to the textclock
require('calendar2')
calendar2.addCalendarToWidget(datewidget)
-- Create a textclock widget
mytextclock = awful.widget.textclock()
-- Create a wibox for each screen and add it
mywibox = {}
mypromptbox = {}
mylayoutbox = {}
mytaglist = {}
mytaglist.buttons = awful.util.table.join(
awful.button({ }, 1, awful.tag.viewonly),
awful.button({ modkey }, 1, awful.client.movetotag),
awful.button({ }, 3, awful.tag.viewtoggle),
awful.button({ modkey }, 3, awful.client.toggletag),
awful.button({ }, 4, function(t) awful.tag.viewnext(awful.tag.getscreen(t)) end),
awful.button({ }, 5, function(t) awful.tag.viewprev(awful.tag.getscreen(t)) end)
mytasklist = {}
mytasklist.buttons = awful.util.table.join(
awful.button({ }, 1, function (c)
if c == client.focus then
c.minimized = true
else
-- Without this, the following
-- :isvisible() makes no sense
c.minimized = false
if not c:isvisible() then
awful.tag.viewonly(c:tags()[1])
end
-- This will also un-minimize
-- the client, if needed
client.focus = c
c:raise()
end
end),
awful.button({ }, 3, function ()
if instance then
instance:hide()
instance = nil
else
instance = awful.menu.clients({ width=250 })
end
end),
awful.button({ }, 4, function ()
awful.client.focus.byidx(1)
if client.focus then client.focus:raise() end
end),
awful.button({ }, 5, function ()
awful.client.focus.byidx(-1)
if client.focus then client.focus:raise() end
end))
for s = 1, screen.count() do
-- Create a promptbox for each screen
mypromptbox[s] = awful.widget.prompt()
-- Create an imagebox widget which will contains an icon indicating which layout we're using.
-- We need one layoutbox per screen.
mylayoutbox[s] = awful.widget.layoutbox(s)
mylayoutbox[s]:buttons(awful.util.table.join(
awful.button({ }, 1, function () awful.layout.inc(layouts, 1) end),
awful.button({ }, 3, function () awful.layout.inc(layouts, -1) end),
awful.button({ }, 4, function () awful.layout.inc(layouts, 1) end),
awful.button({ }, 5, function () awful.layout.inc(layouts, -1) end)))
-- Create a taglist widget
mytaglist[s] = awful.widget.taglist(s, awful.widget.taglist.filter.all, mytaglist.buttons)
-- Create a tasklist widget
mytasklist[s] = awful.widget.tasklist(s, awful.widget.tasklist.filter.currenttags, mytasklist.buttons)
-- Create the wibox
mywibox[s] = awful.wibox({ position = "top", screen = s })
-- Widgets that are aligned to the left
local left_layout = wibox.layout.fixed.horizontal()
left_layout:add(mylauncher)
left_layout:add(mytaglist[s])
left_layout:add(mypromptbox[s])
-- Widgets that are aligned to the right
local right_layout = wibox.layout.fixed.horizontal()
if s == 1 then right_layout:add(wibox.widget.systray()) end
right_layout:add(mytextclock)
right_layout:add(mylayoutbox[s])
-- Now bring it all together (with the tasklist in the middle)
local layout = wibox.layout.align.horizontal()
layout:set_left(left_layout)
layout:set_middle(mytasklist[s])
layout:set_right(right_layout)
mywibox[s]:set_widget(layout)
end
-- {{{ Mouse bindings
root.buttons(awful.util.table.join(
awful.button({ }, 3, function () mymainmenu:toggle() end),
awful.button({ }, 4, awful.tag.viewnext),
awful.button({ }, 5, awful.tag.viewprev)
-- {{{ Key bindings
globalkeys = awful.util.table.join(
awful.key({ modkey, }, "Left", awful.tag.viewprev ),
awful.key({ modkey, }, "Right", awful.tag.viewnext ),
awful.key({ modkey, }, "Escape", awful.tag.history.restore),
awful.key({ modkey, }, "Down",
function ()
awful.client.focus.byidx( 1)
if client.focus then client.focus:raise() end
end),
awful.key({ modkey, }, "Up",
function ()
awful.client.focus.byidx(-1)
if client.focus then client.focus:raise() end
end),
awful.key({ modkey, }, "a", function () mymainmenu:show() end),
-- Layout manipulation
awful.key({ modkey, "Shift" }, "Down", function () awful.client.swap.byidx( 1) end),
awful.key({ modkey, "Shift" }, "Up", function () awful.client.swap.byidx( -1) end),
awful.key({ modkey, "Control" }, "Down", function () awful.screen.focus_relative( 1) end),
awful.key({ modkey, "Control" }, "Up", function () awful.screen.focus_relative(-1) end),
awful.key({ modkey, }, "u", awful.client.urgent.jumpto),
awful.key({ modkey, }, "Tab",
function ()
awful.client.focus.history.previous()
if client.focus then
client.focus:raise()
end
end),
-- Standard program
awful.key({ modkey, }, "Return", function () awful.util.spawn(terminal) end),
awful.key({ modkey, "Control" }, "r", awesome.restart),
awful.key({ modkey, "Shift" }, "q", awesome.quit),
awful.key({ modkey, }, "l", function () awful.tag.incmwfact( 0.05) end),
awful.key({ modkey, }, "h", function () awful.tag.incmwfact(-0.05) end),
awful.key({ modkey, "Shift" }, "h", function () awful.tag.incnmaster( 1) end),
awful.key({ modkey, "Shift" }, "l", function () awful.tag.incnmaster(-1) end),
awful.key({ modkey, "Control" }, "h", function () awful.tag.incncol( 1) end),
awful.key({ modkey, "Control" }, "l", function () awful.tag.incncol(-1) end),
awful.key({ modkey, }, "space", function () awful.layout.inc(layouts, 1) end),
awful.key({ modkey, "Shift" }, "space", function () awful.layout.inc(layouts, -1) end),
awful.key({ modkey, "Control" }, "n", awful.client.restore),
-- Prompt
awful.key({ modkey }, "r", function () mypromptbox[mouse.screen]:run() end),
awful.key({ modkey }, "x",
function ()
awful.prompt.run({ prompt = "Run Lua code: " },
mypromptbox[mouse.screen].widget,
awful.util.eval, nil,
awful.util.getdir("cache") .. "/history_eval")
end),
-- Menubar
awful.key({ modkey }, "p", function() menubar.show() end)
clientkeys = awful.util.table.join(
awful.key({ modkey, }, "f", function (c) c.fullscreen = not c.fullscreen end),
awful.key({ modkey, }, "w", function (c) c:kill() end),
awful.key({ modkey, "Control" }, "space", awful.client.floating.toggle ),
awful.key({ modkey, "Control" }, "Return", function (c) c:swap(awful.client.getmaster()) end),
awful.key({ modkey, }, "o", awful.client.movetoscreen ),
awful.key({ modkey, }, "t", function (c) c.ontop = not c.ontop end),
awful.key({ modkey, }, "n",
function (c)
-- The client currently has the input focus, so it cannot be
-- minimized, since minimized clients can't have the focus.
c.minimized = true
end),
awful.key({ modkey, }, "m",
function (c)
c.maximized_horizontal = not c.maximized_horizontal
c.maximized_vertical = not c.maximized_vertical
end)
-- Compute the maximum number of digit we need, limited to 9
keynumber = 0
for s = 1, screen.count() do
keynumber = math.min(9, math.max(#tags[s], keynumber))
end
-- Bind all key numbers to tags.
-- Be careful: we use keycodes to make it works on any keyboard layout.
-- This should map on the top row of your keyboard, usually 1 to 9.
for i = 1, keynumber do
globalkeys = awful.util.table.join(globalkeys,
awful.key({ modkey }, "#" .. i + 9,
function ()
local screen = mouse.screen
if tags[screen][i] then
awful.tag.viewonly(tags[screen][i])
end
end),
awful.key({ modkey, "Control" }, "#" .. i + 9,
function ()
local screen = mouse.screen
if tags[screen][i] then
awful.tag.viewtoggle(tags[screen][i])
end
end),
awful.key({ modkey, "Shift" }, "#" .. i + 9,
function ()
if client.focus and tags[client.focus.screen][i] then
awful.client.movetotag(tags[client.focus.screen][i])
end
end),
awful.key({ modkey, "Control", "Shift" }, "#" .. i + 9,
function ()
if client.focus and tags[client.focus.screen][i] then
awful.client.toggletag(tags[client.focus.screen][i])
end
end))
end
clientbuttons = awful.util.table.join(
awful.button({ }, 1, function (c) client.focus = c; c:raise() end),
awful.button({ modkey }, 1, awful.mouse.client.move),
awful.button({ modkey }, 3, awful.mouse.client.resize))
-- Set keys
root.keys(globalkeys)
-- {{{ Rules
awful.rules.rules = {
-- All clients will match this rule.
{ rule = { },
properties = { border_width = beautiful.border_width,
border_color = beautiful.border_normal,
focus = awful.client.focus.filter,
keys = clientkeys,
buttons = clientbuttons } },
{ rule = { class = "MPlayer" },
properties = { floating = true } },
{ rule = { class = "pinentry" },
properties = { floating = true } },
{ rule = { class = "gimp" },
properties = { floating = true } },
-- Set Firefox to always map on tags number 2 of screen 1.
-- { rule = { class = "Firefox" },
-- properties = { tag = tags[1][2] } },
-- {{{ Signals
-- Signal function to execute when a new client appears.
client.connect_signal("manage", function (c, startup)
-- Enable sloppy focus
c:connect_signal("mouse::enter", function(c)
if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
and awful.client.focus.filter(c) then
client.focus = c
end
end)
if not startup then
-- Set the windows at the slave,
-- i.e. put it at the end of others instead of setting it master.
-- awful.client.setslave(c)
-- Put windows in a smart way, only if they does not set an initial position.
if not c.size_hints.user_position and not c.size_hints.program_position then
awful.placement.no_overlap(c)
awful.placement.no_offscreen(c)
end
end
local titlebars_enabled = false
if titlebars_enabled and (c.type == "normal" or c.type == "dialog") then
-- Widgets that are aligned to the left
local left_layout = wibox.layout.fixed.horizontal()
left_layout:add(awful.titlebar.widget.iconwidget(c))
-- Widgets that are aligned to the right
local right_layout = wibox.layout.fixed.horizontal()
right_layout:add(awful.titlebar.widget.floatingbutton(c))
right_layout:add(awful.titlebar.widget.maximizedbutton(c))
right_layout:add(awful.titlebar.widget.stickybutton(c))
right_layout:add(awful.titlebar.widget.ontopbutton(c))
right_layout:add(awful.titlebar.widget.closebutton(c))
-- The title goes in the middle
local title = awful.titlebar.widget.titlewidget(c)
title:buttons(awful.util.table.join(
awful.button({ }, 1, function()
client.focus = c
c:raise()
awful.mouse.client.move(c)
end),
awful.button({ }, 3, function()
client.focus = c
c:raise()
awful.mouse.client.resize(c)
end)
-- Now bring it all together
local layout = wibox.layout.align.horizontal()
layout:set_left(left_layout)
layout:set_right(right_layout)
layout:set_middle(title)
awful.titlebar(c):set_widget(layout)
end
end)
client.connect_signal("focus", function(c) c.border_color = beautiful.border_focus end)
client.connect_signal("unfocus", function(c) c.border_color = beautiful.border_normal end)
http://pastebin.com/X4JdkVi0
Last edited by nhare330 (2013-01-18 13:59:40)

[Solved] a.out not recognizing the working directory

It's a little bit embarrassing because this issue doesn't seem terribly complicated, but I'm having trouble with executing the a.out file (Hello World) that gcc produces. I have to explicitly state the directory that a.out is in to run it, even though it's in the working directory. Other programs, such as Nano, recognize the working directory just fine and it is able to open files inside the working directory without having me explicitly state the full directory name.
Any help would be greatly appreciated.
Last edited by bananaman (2011-03-23 03:16:10)

The easiest and most secure way would be using the relative path to the executable:
./a.out
If you use a single directory for writing/testing your programs, you could add it to your user PATH. Not a major security risk, but if you do so, be careful what executables are in the dir.
~/.bashrc (or ~/.bash_profile):
[[ -d ~/cpp ]] && export PATH="$PATH:~/cpp"
Adding the current working directory to PATH is a security risk, so I wouldn't recommend it.
Last edited by sisco311 (2011-03-23 03:12:29)

[SOLVED] Qt Applications not recognizing japanese characters

When I run Qt applications (goldendict, anki) and open a file browser from within the application itself, file names with Japanese characters in them (醤字.txt) don't get read and the file is "invisible". I don't have any problems when I launch a file browser from the terminal or via cinnamon. I read the arch wiki page on Qt, but wasn't able to find anything that helped. Also, I have a thread about XTerm not reading Japanese characters or being able to take Japanese input, so, not sure if it's related or not. Any suggestions?
Thanks in advance!
Last edited by Bipolarbearz (2014-12-24 03:40:47)

Issue was with my locale settings. Full story here: https://bbs.archlinux.org/viewtopic.php … 0#p1486600 for anyone with the same issue.

[SOLVED] Control+V not recognized by X

I just installed Arch on my laptop yesterday (HP 8510w) but an interesting problem has popped up, Control+V doesn't work.
showkey recognises the keypress 29 (Control_L) and 46 (v), both separately and simultaneously. However, xev will only recognize them when pressed separately. So I think the issue lies with X configuration. Does anyone have a clue on how to fix this?
X11 config files
EDIT: Accidentily pressed control+V from habit and it submitted prematurely
EDIT 2: Okay, I solved it... stupid me, I shouldn't configure my computer at 2am. Anyway, I bound KeePassX autofill to the Control+V shortcut which prevented normal operation of this shortcut. Apologies for the clutter
Last edited by rickdg (2011-01-21 11:24:52)

Good question. I've got the wired extended keyboard connected to an iMac, and I get the same behavior. There's probably something to it, but your guess is as good as mine as to what that is...

Capturing through Sony HDV using firewire800 to 400 adaptor is not recognizing can any body help me solve this

I am trying to capture using firewire 800 to 400 adaptor through a Sony HDV VTR. The VTR is not recognizing can some body help me solve this problem.
I am using FCP7 and IMAC with 10.6.8 version os
I dont have a 6 pin or 400 firewire port in the system

Let's start with basics.
Does your computer recognize that there is a VTR attached?
• Open up system profiler>Hardware>FireWire. Does your machine show up?
If no, you need to figure out if the problem lies with the VTR, the cable, the adapter or your computer.
My guess is with the adapter. A number of people have expressed frustration getting fw400 device to work through fw800 ports.
If that's your problem, see if you can find an older Mac w/ fw400 ports or a dedicated fw800 to 400 cable.
good luck,
x
ps - In "locking the barn after the paddle has been lost upstream" mode, this is why non-expandable computers like the iMac are so problematic. A MacBookPro with the expresscard 34 slot or a MacPro with 3 slots can work around these kind of issues. A closed box like the iMac is a dead end. Sorry.

[solved] texlive problem - supertabular environment not recognized

Hey!
I want to use supertabular but actually it's not working… I cannot see why.
kpsewhich supertabular.sty
/usr/share/texmf-dist/tex/latex/supertabular/supertabular.sty
There shouldn't be problems with permissions also:
ls -la $(kpsewhich supertabular.sty)
-rw-r--r-- 1 root root 14K Jun 26 08:01 /usr/share/texmf-dist/tex/latex/supertabular/supertabular.sty
It should be installed inside of http://www.archlinux.org/packages/extra … atexextra/
pacman -Qs texlive-latexextra
local/texlive-latexextra 2012.26807-1 (texlive-most)
TeX Live - Large collection of add-on packages for LaTeX
So it is. I also ran
sudo texhash
several times but it's still not recognized. My LaTeX Editor is latexila from AUR if this somehow important.
Maybe someone have an idea? I'd love to hear some ideas on this since I'm confused all over…
Cheers!
Last edited by domac (2012-10-20 12:27:32)

Yes, for sure Trilby! Sorry, I don't know how to entitle this thread exactly since I don't get what goes wrong here…
Some sample file I tried to compile that failed @ line 11 where "supertabular" occurs:
http://sprunge.us/HGbH?latex
or
\documentclass[a4paper,11pt]{article}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{lmodern}
\title{foo}
\author{bar}
\begin{document}
\begin{supertabular}{rrrr}
1 & 1 & 1 & 1 \\
2 & 4 & 16 & 2 \\
3 & 9 & 81 & 6 \\
4 & 16 & 256 & 24 \\
\end{supertabular}
\end{document}
Any ideas?
EDIT: Totally forgot…
! LaTeX Error: Environment supertabular undefined.
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
l.11 egin{supertabular}
{rrrr}
This is the most helpful error I get at the moment…
Oh shit… I found the error… missing usepackage… whoupadoup! xD
Sorry for that big trouble. Marked as solved.
Last edited by domac (2012-10-20 12:27:18)

[solved] External Hard Drive Not Recognized

I bought a SATA-to-USB 2.0 external HDD enclosure today (found here), and plugged in a 320gb WD Scorpio Blue. When I first plugged it into my laptop, with Crunchbang Stalter on it, it worked perfectly. I partitioned it and everything. However, I then plugged it into my desktop with Arch on it, kernel version 3.4.4.2, and it was not recognized. lsusb returns nothing related to it, fdisk -l does nothing, and dmesg only displays "fuse init (API version 7.18)". I have tried multiple file systems, set up on my laptop, including ext4, fat32 and ntfs, with absolutely no luck. I would greatly appreciate any help.
Last edited by mjdudak (2012-07-11 15:56:32)

I was actually having the same problem with a USB to SATA adapter that only occured on my arch box. When the device was plugged in it showed the event in dmesg and then it got registered as /dev/sde. If I tried to use the mount command though it gave me some error like "could not read from inode" or something like that. After upgrading to kernel 3.4.4-4 the problem seems to have corrected its self now. Are you using systemd or udev?
Last edited by mynis01 (2012-07-10 09:01:38)

[solved] pacman mirrorlist "directive 'x' not recognized"

I'm bungling through an install and tried using reflector to get speedier mirrors. Somehow I hosed myself, as when I checked mirrorlist it was blank(!), so I recopied the back-up to /etc/pacman.d/mirrorlist. Now when I run pacman -Syy I get:
error: config file /etc/pacman.d/mirrolist, line 1: directive 'x' in repository section 'core' not recognized.
The a line saying the same holds true for extra and community. Then it tries to sync servers and says: failed to update core (no servers configured for repository), and again for extra and community. I tried to get openssh so I could go in remotely and copy the screen, but "no servers configured for repository."
Can anyone get me out of this can of worms?
Last edited by pottzie (2011-06-17 23:58:40)

x#Mirror used during installation
Server = http:/mirror.cs.vt.edu/pub/ArchLinux/$repo/os/i686
(Which now that i look at I recognize as the server i chose for the installation!)
Then, just the rest of the standard mirror list, and i uncommented the U.S. mirrors.

[Solved] After update, media keys not recognized.

After I updated today, my play, stop, forward and back keys work, but not recognized in xbindkeys -mk. My vol up, down and mute do not work and are not recognized. I also cannot ctrl+alt+backspace to restart x.
Last edited by haxit (2009-05-02 15:26:49)

Acecero wrote:
haxit wrote:I also cannot ctrl+alt+backspace to restart x.
Add this
Option "DontZap" "false"
to the "ServerFlags" Section in the xorg.conf file.
Zapping has been disabled by default with xorg-server 1.6
Thanks a lot.

[Solved] Clang "-cc1" not recognized

Similar Messages

Maybe you are looking for