Ah, it turns out the Super key issue ended up being bug 568401, which
was an issue in the indicator-applet itself. Fortunately, this was
addressed in a Stable Release Update.
--
vnc4server fails to start; Xvnc4 no longer recognizes -extension argument
https://bugs.launchpad.net/bugs/556147
You re
On Fri, Apr 23, 2010 at 05:50:10PM -, Julien Antille wrote:
> I confirm the "Super key" being like always pressed.
> Should I open a new bug ?
Yes, please do (and report back here). Thanks.
--
Steve Beattie
http://NxNW.org/~steve/
--
vnc4server fails to start; Xvnc4 no longer recognizes -
I confirm the "Super key" being like always pressed.
Should I open a new bug ?
--
vnc4server fails to start; Xvnc4 no longer recognizes -extension argument
https://bugs.launchpad.net/bugs/556147
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
This bug was fixed in the package vnc4 - 4.1.1+xorg4.3.0-37ubuntu2
---
vnc4 (4.1.1+xorg4.3.0-37ubuntu2) lucid; urgency=low
* unix/vncserver: revert "-extension XFIXES" as it is no longer
needed (LP: #556147)
* Remaining Ubuntu changes:
- None
-- Steve BeattieMon, 05 A
@Dave
Both of these options are unknown to my Vnc4 version (
4.1.1+xorg4.3.0-37ubuntu1). Both result in an unknown option error when trying
to launch via vnc4server.
Regards, Edi
--
vnc4server fails to start; Xvnc4 no longer recognizes -extension argument
https://bugs.launchpad.net/bugs/556147
@Eduard & @sbeattie: Can you try changing the line from:
$cmd .= " -extension XFIXES";
to the following combinations, and see if one of them resolves the issue. It
would be good to get this fixes prior to the next upload:
$cmd .= " -clear_keys";
$cmd .= " -repeat";
$cmd .= " -repeat -clear_keys"
Steve: oh, thanks.
True, I can confirm that the SUPER key is always pressed. On my lucid test
system, I was only viewing so I did not recognize.
--
vnc4server fails to start; Xvnc4 no longer recognizes -extension argument
https://bugs.launchpad.net/bugs/556147
You received this bug notification
Eduard: yes, that's what the patch in the attached bzr branch does. It's
also available in package form from my ppa at
https://launchpad.net/~sbeattie/+archive/ppa/ . It causes vnc to start;
however, the vnc server is acting like the Super key is pressed all the
time, which is making it less useful
The fix is rather easy: just replace
$cmd .= " -extension XFIXES";
by
#$cmd .= " -extension XFIXES";
around line 263 in /usr/bin/vnc4server
--
vnc4server fails to start; Xvnc4 no longer recognizes -extension argument
https://bugs.launchpad.net/bugs/556147
You received this bug notification becaus
** Branch linked: lp:~sbeattie/ubuntu/lucid/vnc4/lp556147
--
vnc4server fails to start; Xvnc4 no longer recognizes -extension argument
https://bugs.launchpad.net/bugs/556147
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Backing out the change in http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/lucid/vnc4/lucid/revision/12, the only remaining (code)
dependency fixes it so that Xvnc4 will start. And it is capable of
launching a full gnome-session, as that's what I have my .vnc/xstartup
configured to do.
--
vnc
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/43204655/Dependencies.txt
--
vnc4server fails to start; Xvnc4 no longer recognizes -extension argument
https://bugs.launchpad.net/bugs/556147
You received this bug notification because you are a member of Ubuntu
Bugs, which
12 matches
Mail list logo
