cropped screenshots about skippy-xd HOT 18 OPEN

nvidia-drivers's X Render implementation has a bug that X Picture transformation of client window Pictures doesn't choose the correct position. You may try useNameWindowPixmap = true or includeFrame = truein my WIP patch.

from skippy-xd.

~$ lspci -nnk | grep -i vga -A3 | grep 'in use'
Kernel driver in use: radeon

is that a driver problem? should i install fglrx?

edit: can that be solved with this patch? if yes, please help me apply it...

from skippy-xd.

@foltiz:

Sorry, I have no idea why that would happen, and I've heard no issues about radeon so far. My advices above may or may not help. Have you tried them?

And I heard fglrx is more buggy than radeon...

an that be solved with this patch? if yes, please help me apply it...

No idea if the patch will help. One will typically download the raw patch and apply it with the patch -p1 < path/to/patch, then compile the program. I'm not really sure what help would you need...

from skippy-xd.

~$ patch -p1 < /home/folti/downloads/gist5696281-5ec26c4856e8916adb028efba1402d954495bc8e/skippy-xd-wip.patch
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?

The text leading up to this was:

|diff --git a/Makefile b/Makefile
|index 369ea19..52b72f8 100644
|--- a/Makefile

|+++ b/Makefile

File to patch:

...is what i get when i try to patch. what do you mean when you say "then compile the program"? how can one do that? is that stopping the daemon and starting it again or will relogin do?

from skippy-xd.

ok, i figured out i had to "~$ patch -p1 /home/folti/downloads/gist5696281-5ec26c4856e8916adb028efba1402d954495bc8e/skippy-xd-wip.patch", without "<" in front of path. but i'm not sure if it patched... i had to ctrl+c because nothing was happening five minutes and it didn't come out to prompt. did i patch it? how to know that? if i did and that behaviour is expected, how to compile, as you said?

from skippy-xd.

How did you install skippy-xd GIT in the first place?

from skippy-xd.

@foltiz:

Well, you don't seem quite on the right direction, unfortunately...

Before applying a patch you at least need to have something to patch -- that is, source code. I thought you already is building skippy-xd from source but apparently it's not the case. And unless you are using some developer-oriented distros (Gentoo, Arch, FreeBSD, etc.), it might be moderately tricky to create a building environment. So in case you don't know what I'm talking about, I would recommend you to give up right now.

Anyway, here's some brief instructions to build skippy-xd from source: (Note they aren't actually tested and I may make typos)

1. Create building environment -- A compiler (gcc/clang, typically), GNU make, and development files of Xlib (okay, which is actually a lot of packages on most distros) is what skippy-xd typically needs. Please refer to the documentation of the distro you use for more details. Some hints could be found in the control files in our PPA packages.

2. Grab our source code:

   mkdir git
   cd git
   git clone https://github.com/richardgv/skippy-xd.git
   cd skippy-xd

3. Apply the patch:

   wget https://gist.github.com/richardgv/5696281/raw/26f7ca6a577d6f81f6c0384bc73d566d24b872b2/skippy-xd-wip.patch
   patch -p1 < skippy-xd-wip.patch

4. Build it, and run:

   make
   ./skippy-xd

And no, I didn't make a typo: It's patch < XXX.patch, not patch XXX.patch. Patch is a weird app indeed! When you use patch XXX.patch, patch actually considers XXX.patch the file to be patched, and it's waiting for you to input patch content in stdin, so it slept for 5 minutes without doing anything...

from skippy-xd.

Some more building instructions are on our Wiki:
http://code.google.com/p/skippy-xd/wiki/Installation

from skippy-xd.

@landroni:

Some more building instructions are on our Wiki:
http://code.google.com/p/skippy-xd/wiki/Installation

Oops, I totally forgot we still have a wiki. :-D Don't really like its purely Debian-oriented tone, though. Maybe most Gentoo and Arch users don't need any further instructions, but those using Fedora may. Hmm, but firstly I need to finish the endless work... sigh

from skippy-xd.

Yes, it would be nice to update a bit the instructions on the wiki. :) I haven't used non-Debian distros for several years now, so my skills in this are a bit wanting right now.

from skippy-xd.

Huh, does this problem still exist?

I will close the issue if I don't see a reply in a week.

from skippy-xd.

actually, it does. I hope I don't hijack this issue. I'm having the same effect as on foltiz' screenshot. (I can't figure out whats wrong on landroni's btw).

Some windows or sometimes only parts of windows are corrupted or distorted as if there's only garbage written into them.

I'm using arch linux with the radeon driver, latest git version of skippy-xd; running openbox and xcompmgr.

from skippy-xd.

@tillmann:

actually, it does. I hope I don't hijack this issue. I'm having the same effect as on foltiz' screenshot. (I can't figure out whats wrong on landroni's btw).

Some windows or sometimes only parts of windows are corrupted or distorted as if there's only garbage written into them.

I'm using arch linux with the radeon driver, latest git version of skippy-xd; running openbox and xcompmgr.

1. Are all mapped windows (mostly, those not iconified and is in the current virtual desktop) displayed correctly? Unmapped windows will naturally not be displayed correctly as thumbnails, and with the latest version (git-281a7d5-2013-12-13) they should appear as icons/filled boxes or totally invisible.
2. Does setting useNameWindowPixmap = true (and possibly, forceNameWindowPixmap = true) in skippy-xd.rc help?
3. What does skippy-xd output? I need to know how the window stack is retrieved, and whether there's any errors skippy-xd reported.
4. Are you running it as daemon or without?
5. What does skippy-xd --help print out? I wish to verify the version you are running.

from skippy-xd.

Number 2 appears to do the trick. Thanks. There were no outputs or errors from skippy-xd btw.
(When I was reading your earlier comment with that exact solution I thought the problem was nvidia specific)

This is worth mentioning in the sample rcfile :)

from skippy-xd.

@tillmann:

I couldn't reproduce it here with nvidia-drivers-331.38, at least. Is forceNameWindowPixmap = true required for you? Are those incorrectly displayed window mapped or unmapped?

from skippy-xd.

Nope, just using useNamedWindowPixmap = true and works so far.
I don't know what mapped means. The windows are not minimized. If they are, the window silhouette appears with an icon inside. Same for windows on other desktops.

from skippy-xd.

@tillmann:

Heh, that looks an annoying issue. I don't get why XRenderCreatePicture() would fail. Thanks for the info! Let's see if there are other people encountering similar issues.

from skippy-xd.

Same problem with the RADEON driver from xorg 7.7 on Linux Mint 17

from skippy-xd.