gillen033: For me, he was in th elven district, or w/e it's called. The area with crappy housing and drainage. I'm guessing you know that already though. I believe there are two entrances to this area. Look to both of these entrances (not doors, just open pathways), he was standing to the left/right depending on if you're entering/exiting the area. If you still can't find him, either you are bugged like you say, or maybe the time of day is wrong. I found him during the day, not sure what time.
In any case, couldn't you just go kill the Succubus? Or do you have dark thoughts on your mind . . .? Heh
The elven distric has one entrance, but it's main "street" goes in a circle back onto itself. My dark thoughts are that I want to really solve this quest. The real culprit seems to be the elve, not the succubus (the blade fragment seems to indicate so). In other words I would prefer not to sacrifice innocents just to have the quest flagged as "solved".
Anyway it's really strange. I already asked gog to tell me how can I spawn Iorveth again, hopely to solve this problem. For now I keep doing the other quests, although I'm running out of things to do before the next step on the Triss quest. Another problem I seem to have encountered is that I have killed over a hundred harpies (have gone into harpy inhabited zones at least twice), I have bought and read the book about harpies, have got the harpies traps, but can't do anything with them. When equipped in a quick slot it doesn't show and R doesn't do a thing. Near the nest I don't get any option with the mouse to "arm" the trap. So in general I cannot finish that quest either. The gameguide speaks about a "firefly bomb" which you aim and destroy the nests that way. But as I told before I have killed so many harpies I should already have whatever "knowledge" required, but I don't seem to have it. In this case I may be missing out on something, so I'm still searching and for now I can't call this a bug. But if none of the merchants won't have the diagram to the firefly bomb, I suppose I will have to call this a bug too.