Re: [arch-general] Chromium Favorites Bar Partially Inoperative

2016-02-01 Thread Martin S. Weber
On 2016-01-31 18:11:24, Dutch Ingraham wrote: > (...) confirm chrome on awesome "right" (or 2ndary) monitor problems: This is an awesome + multi-monitor + chromium problem, not your graphics driver. folders in the bookmark bar do not track "pressed" status or track the mouse at all. I believe it

Re: [arch-general] Cannot use monitor in 1920x1080 anymore

2015-04-05 Thread Martin S. Weber
On 2015-04-04 11:29:26, "Pedro A. López-Valencia" wrote: > On 30/03/15 06:24, Martin S. Weber wrote: > >On 2015-03-30 13:08:11, Alfredo Palhares wrote: > >>Any ideas how can I debug this problem further ? > >Have a look at X's logfile, /var/log/Xorg.log. Th

Re: [arch-general] Cannot use monitor in 1920x1080 anymore

2015-03-30 Thread Martin S. Weber
On 2015-03-30 13:08:11, Alfredo Palhares wrote: > Any ideas how can I debug this problem further ? Have a look at X's logfile, /var/log/Xorg.log. There should be messages that say the modes are being removed, and why (not enough Vram, some parameter out of range, etc.). It's likely warning or er

Re: [arch-general] syslog-ng + systemd-journald = no logs for syslog-ng

2015-02-16 Thread Martin S. Weber
On 2015-02-15 15:50:49, Leonid Isaev wrote: > TL:DR: Syslog-ng in [extra] is kind of broken, so you'll need to a few steps > to > get it to work in your environment. > > 1. (...) > 2. (...) > 3. (...) > 4. (Re)enable syslog-ng.service and restart syslog. A cookie, a mug of hot steaming morning d

Re: [arch-general] syslog-ng + systemd-journald = no logs for syslog-ng

2015-02-15 Thread Martin S. Weber
On 2015-02-15 08:34:23, Troy Engel wrote: > On Sun, Feb 15, 2015 at 3:37 AM, wrote: > > ## vanilla /etc/syslog-ng/syslog-ng.conf > > # grep -v '^#' /etc/systemd/journald.conf > > > > It sounds like syslog-ng doesn't understand where the source is - (...) In fact, you pointed me to the solution.

Re: [arch-general] Display Manager issue

2014-09-15 Thread Martin S. Weber
On 2014-09-16 07:57:33, Heiko Becker wrote: > > On 16.09.2014 07:28, Frank Zimmermann wrote: > >my DM is behaving strange. > > Can you maybe provide information which DM it is? Could be related to that. I see the same for quite a while. With Lightdm. I disabled xdm in the meantime and startx ins

Re: [arch-general] Default value of "j" in makeflags of makepkg.conf

2014-01-03 Thread Martin S. Weber
On Fri, Jan 03, 2014 at 07:06:31PM +0100, Timoth?e Ravier wrote: > On 03/01/2014 17:46, Martin S. Weber wrote: > (...) > > (...) > > Read e.g. this message from the author of SQLite and fossil about packager's > > need/want for splitting dynamic libs from pro

Re: [arch-general] Default value of "j" in makeflags of makepkg.conf

2014-01-03 Thread Martin S. Weber
On Fri, Jan 03, 2014 at 04:44:05PM +0100, Timoth?e Ravier wrote: > On 03/01/2014 16:24, Martin S. Weber wrote: > > (...) > > As far as I know, MAKE_JOBS_SAFE and 'options="!makeflags"' are > packaging "tricks" to work around an upstream bug. I

Re: [arch-general] Default value of "j" in makeflags of makepkg.conf

2014-01-03 Thread Martin S. Weber
On Sat, Jan 04, 2014 at 01:07:47AM +1000, Allan McRae wrote: > On 04/01/14 01:03, Martin S. Weber wrote: > > On Fri, Jan 03, 2014 at 03:23:24PM +0100, Thomas B?chler wrote: > >> Am 03.01.2014 15:21, schrieb Martti K?hne: > >>> You can't expect every upstream

Re: [arch-general] Default value of "j" in makeflags of makepkg.conf

2014-01-03 Thread Martin S. Weber
On Fri, Jan 03, 2014 at 03:23:24PM +0100, Thomas B?chler wrote: > Am 03.01.2014 15:21, schrieb Martti K?hne: > > You can't expect every upstream to fix their autohell to conform to > > our expectations here. > > So, we keep repeating ourselves. > > There is the !makeflags option for PKGBUILDs to