Page 50 of 60 FirstFirst ... 404849505152 ... LastLast
Results 491 to 500 of 591

Thread: HOWTO: functional eye-candy with Avant-Window-Navigator

  1. #491
    Join Date
    Nov 2008
    Location
    India
    Beans
    162
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Question Re: HOWTO: functional eye-candy with Avant-Window-Navigator

    There is a problem with my AWN.

    It shows some white patches at regular intervals, and get fixed once I move my mouse over the AWN again. I think It is not getting automatically refreshed

    I am giving a screenshot of my problem here so that you can understand
    I am using ubuntu 8.10
    Attached Images Attached Images
    Last edited by trendyabinash; November 24th, 2008 at 03:32 AM. Reason: posted wrong screenshot
    System:-Core2Duo, 2GB RAM, 160GB SATA HD, ATI RADEON HD 5450 GPU

  2. #492
    Join Date
    Aug 2007
    Beans
    219

    Re: HOWTO: functional eye-candy with Avant-Window-Navigator

    Why does Compiz/AWN not work well with playing 3D games? Ex. I had AWN running, then I launched Tremulous, and X crashed.

  3. #493
    Join Date
    Jun 2006
    Location
    A galaxy far, far away...
    Beans
    2,800

    Re: HOWTO: functional eye-candy with Avant-Window-Navigator

    Quote Originally Posted by Changturkey View Post
    Why does Compiz/AWN not work well with playing 3D games? Ex. I had AWN running, then I launched Tremulous, and X crashed.
    That's a compiz bug. I won't go into detail as there are countless other sources of information for it (use google!), but you should always turn off compiz before you start a 3d application to avoid this sort of conflict. (note that nvidia users do not have this bug and can safely run 3d under compiz.) This bug is slated to be fixed in the near future, hopefully in time for Jaunty.
    "Whoever said sunshine brings happiness has never danced in the rain." - K. Jackson
    Exaile Media Player | Arch Linux
    Click here to have your brain eaten

  4. #494
    Join Date
    Nov 2008
    Location
    India
    Beans
    162
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: HOWTO: functional eye-candy with Avant-Window-Navigator

    Sir tell me about the white patches, what should I do to remove them????
    System:-Core2Duo, 2GB RAM, 160GB SATA HD, ATI RADEON HD 5450 GPU

  5. #495
    Join Date
    Jun 2006
    Location
    A galaxy far, far away...
    Beans
    2,800

    Re: HOWTO: functional eye-candy with Avant-Window-Navigator

    Quote Originally Posted by trendyabinash View Post
    Sir tell me about the white patches, what should I do to remove them????
    If you have an nvidia card, it's suspected to be a bug in the nvidia drivers. No known fix at this point. (See the last couple pages in this thread for a discussion of it.) If you do not have an nvidia card, then this is a bug I am not familiar with and you should file a bug against AWN on launchpad.
    "Whoever said sunshine brings happiness has never danced in the rain." - K. Jackson
    Exaile Media Player | Arch Linux
    Click here to have your brain eaten

  6. #496
    Join Date
    Jul 2006
    Location
    Greece
    Beans
    Hidden!
    Distro
    Ubuntu 13.04 Raring Ringtail

    Re: HOWTO: functional eye-candy with Avant-Window-Navigator

    The AWN works almost perfectly for me, but this "almost" is pretty big. Here are the most important issues I am facing and if you could give me a solution to at least on of them (especially the first two ones really irritate me) I would be grateful:

    - All the workspace switcher applets I have tried are presenting serious graphical issues. Fragments of previous windows, or just stupid white (or other colors) stripes remain attached to them for no obvious reason and remain there no matter what I do. It really ruins the image of the whole bar. All the rest applets don't have any similar graphical problems.

    -aMSN starts on system startup on the AWN instead of the upper Notification Area (system tray) as it should.

    -Open windows change places on the AWN when I am maximizing or minimizing them.

  7. #497
    Join Date
    Nov 2006
    Location
    Alpine, Texas
    Beans
    502
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: HOWTO: functional eye-candy with Avant-Window-Navigator

    I went to file a bug report on the nvidia/awn conflict and a bug report already exists here.

    A workaround is to move the applets to the left side of the dock and the launcher bar to the right. I haven't tried it yet, but I will this evening.

    EDIT: Apparently the workaround is very temporary and the "artifacts" begin showing up again at some point down the road. The bug report then degenerates into an argument as to whose problem this is (AWN's or nvidia's).
    Last edited by vgrisham; November 24th, 2008 at 07:56 PM.

  8. #498
    Join Date
    Aug 2007
    Beans
    219

    Re: HOWTO: functional eye-candy with Avant-Window-Navigator

    Quote Originally Posted by reacocard View Post
    That's a compiz bug. I won't go into detail as there are countless other sources of information for it (use google!), but you should always turn off compiz before you start a 3d application to avoid this sort of conflict. (note that nvidia users do not have this bug and can safely run 3d under compiz.) This bug is slated to be fixed in the near future, hopefully in time for Jaunty.
    For Intel GFX?

  9. #499
    Join Date
    Nov 2008
    Location
    India
    Beans
    162
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Question Re: HOWTO: functional eye-candy with Avant-Window-Navigator

    This is the output when I am trying to install AWN extras

    What is the solution to this? Which packages I am missing.

    Code:
    trendyabinash@abinash-desktop:~$ su
    Password: 
    root@abinash-desktop:/home/trendyabinash# cd awn
    root@abinash-desktop:/home/trendyabinash/awn# ./configure
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for a thread-safe mkdir -p... /bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether to enable maintainer-specific portions of Makefiles... no
    checking for style of include used by make... GNU
    checking for gcc... gcc
    checking for C compiler default output file name... a.out
    checking whether the C compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables... 
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking dependency style of gcc... gcc3
    checking for library containing strerror... none required
    checking for gcc... (cached) gcc
    checking whether we are using the GNU C compiler... (cached) yes
    checking whether gcc accepts -g... (cached) yes
    checking for gcc option to accept ISO C89... (cached) none needed
    checking dependency style of gcc... (cached) gcc3
    checking how to run the C preprocessor... gcc -E
    checking for grep that handles long lines and -e... /bin/grep
    checking for egrep... /bin/grep -E
    checking for ANSI C header files... yes
    checking build system type... i686-pc-linux-gnu
    checking host system type... i686-pc-linux-gnu
    checking for a sed that does not truncate output... /bin/sed
    checking for ld used by gcc... /usr/bin/ld
    checking if the linker (/usr/bin/ld) is GNU ld... yes
    checking for /usr/bin/ld option to reload object files... -r
    checking for BSD-compatible nm... /usr/bin/nm -B
    checking whether ln -s works... yes
    checking how to recognize dependent libraries... pass_all
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking dlfcn.h usability... yes
    checking dlfcn.h presence... yes
    checking for dlfcn.h... yes
    checking for g++... no
    checking for c++... no
    checking for gpp... no
    checking for aCC... no
    checking for CC... no
    checking for cxx... no
    checking for cc++... no
    checking for cl.exe... no
    checking for FCC... no
    checking for KCC... no
    checking for RCC... no
    checking for xlC_r... no
    checking for xlC... no
    checking whether we are using the GNU C++ compiler... no
    checking whether g++ accepts -g... no
    checking dependency style of g++... none
    checking for g77... no
    checking for xlf... no
    checking for f77... no
    checking for frt... no
    checking for pgf77... no
    checking for cf77... no
    checking for fort77... no
    checking for fl32... no
    checking for af77... no
    checking for xlf90... no
    checking for f90... no
    checking for pgf90... no
    checking for pghpf... no
    checking for epcf90... no
    checking for gfortran... no
    checking for g95... no
    checking for xlf95... no
    checking for f95... no
    checking for fort... no
    checking for ifort... no
    checking for ifc... no
    checking for efc... no
    checking for pgf95... no
    checking for lf95... no
    checking for ftn... no
    checking whether we are using the GNU Fortran 77 compiler... no
    checking whether  accepts -g... no
    checking the maximum length of command line arguments... 1572864
    checking command to parse /usr/bin/nm -B output from gcc object... ok
    checking for objdir... .libs
    checking for ar... ar
    checking for ranlib... ranlib
    checking for strip... strip
    checking if gcc supports -fno-rtti -fno-exceptions... no
    checking for gcc option to produce PIC... -fPIC
    checking if gcc PIC flag -fPIC works... yes
    checking if gcc static flag -static works... yes
    checking if gcc supports -c -o file.o... yes
    checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
    checking whether -lc should be explicitly linked in... no
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    configure: creating libtool
    appending configuration tag "CXX" to libtool
    appending configuration tag "F77" to libtool
    checking for gconftool-2... /usr/bin/gconftool-2
    checking for intltool >= 0.34... 0.36.2 found
    checking for perl... /usr/bin/perl
    checking for XML::Parser... ok
    checking locale.h usability... yes
    checking locale.h presence... yes
    checking for locale.h... yes
    checking for LC_MESSAGES... yes
    checking libintl.h usability... yes
    checking libintl.h presence... yes
    checking for libintl.h... yes
    checking for ngettext in libc... yes
    checking for dgettext in libc... yes
    checking for bind_textdomain_codeset... yes
    checking for msgfmt... no
    checking for python... /usr/bin/python
    checking for a version of Python >= 2.1.0... yes
    checking for the distutils Python package... yes
    checking for Python include path... -I/usr/include/python2.5
    checking for Python library path... -L/usr/lib/python2.5 -lpython2.5
    checking for Python site-packages path... ${exec_prefix}/lib/python2.5/site-packages
    checking python extra libraries...  -lpthread -ldl  -lutil
    checking python extra linking flags... -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions
    checking consistency of all components of python development environment... no
    configure: error:
      Could not link test program to Python. Maybe the main Python library has been
      installed in some non-standard library path. If so, pass it to configure,
      via the LDFLAGS environment variable.
      Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib"
      ============================================================================
       ERROR!
       You probably have to install the development version of the Python package
       for your distribution.  The exact name of this package varies among them.
      ============================================================================
               
    root@abinash-desktop:/home/trendyabinash/awn# make
    make: *** No targets specified and no makefile found.  Stop.
    root@abinash-desktop:/home/trendyabinash/awn#
    System:-Core2Duo, 2GB RAM, 160GB SATA HD, ATI RADEON HD 5450 GPU

  10. #500
    Join Date
    Jun 2006
    Location
    A galaxy far, far away...
    Beans
    2,800

    Re: HOWTO: functional eye-candy with Avant-Window-Navigator

    Quote Originally Posted by Changturkey View Post
    For Intel GFX?
    All Intel cards and also ATI cards that run on the open-source drivers, if I recall correctly.
    "Whoever said sunshine brings happiness has never danced in the rain." - K. Jackson
    Exaile Media Player | Arch Linux
    Click here to have your brain eaten

Page 50 of 60 FirstFirst ... 404849505152 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •