Bug 426249
| Summary: | Gnome applets not displayed | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Patrick Monnerat <patrick> |
| Component: | vnc | Assignee: | Adam Tkac <atkac> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 8 | CC: | ovasik, vnasardinov |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-12-02 18:15:54 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Patrick Monnerat
2007-12-19 16:14:42 UTC
Could you please tell me if you're using gnome session on multiple servers? (for example you run standard gnome session on :0 and you try start next gnome session through Xvnc on :1) I've add the problem in both cases. For example, gdm expects login on :0 (so no session is started yet) and the single active session runs under Xvnc. I generally start Xvnc dynamically (via xinetd) with the following parameters: -inetd -once -query localhost -geometry 1024x768 -dpi 100 -depth 24 - securitytypes=none -render And XDMCP enabled in gdm gnome is not able to run on multiple servers. There's already bug for that issue (#243933). Problem may be also related to bad font configuration in Xvnc. Could you please test upcomming vnc and tell me if problem still exists? http://kojiweb.fedoraproject.org/koji/taskinfo?taskID=303169 Regards, Adam Still same problem with 4.1.2-23.1.fc8 downloaded from link above. Test method is starting Xvnc with xinetd with same parameters as above. Bug occurrence still looks random. Thanks for trying Grasping at straws here...
Patrick, do you run your Gnome under VNC with a different resolution
than you run your Gnome sessions on the console?
The reason I ask is because I have the same problem and the resolution
mismatch is the only peculiar thing about my setup, as far as I can
tell.
In my case, both the target machine (call it "work") and the client
machine (call it "home") are running F7. On my "work" machine, I have:
| $ rpm -qa 'vnc*'
| vnc-libs-4.1.2-19.fc7
| vnc-server-4.1.2-19.fc7
| vnc-4.1.2-19.fc7
When I'm physically present at my "work" machine, I run X on a
1600x1200 display. When I vnc into my "work" machine from my "home"
machine, I use a different resolution, because my "home" monitor is
not as fancy. On my "work" machine, I have:
|$ grep -vE '^#' /etc/sysconfig/vncservers | cat -s
|
|VNCSERVERS="1:vadim"
|VNCSERVERARGS[1]="-geometry 1280x1024"
Also on the "work" machine:
| $ grep -vE '^#' ~/.vnc/xstartup | awk '/[^ ]/ {print $0}'
| unset SESSION_MANAGER
| exec /etc/X11/xinit/xinitrc
| [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
| [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
| xsetroot -solid grey
| vncconfig -iconic &
| xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
| twm &
Note that I start my VNC server with
-geometry 1280x1024
even though my X server is normally configured to run with 1600x1200
The main display is at 1024x768, but is almost never used (this is a 19" server) The VNC session is generally at 1152x864. But I also had the problem with a 1024x768 session. The client is W$ RealVnc 4.1.2. This is the most used configuration, but other combinations of client/server/resolutions cause the same problem too, providing the server runs on F8. FC6 was OK, I never tested F7. However, with an up-to-date F8 (2008-03-18), the problem seems to occur much less frequently: although unidentified, I may think today the problem is not vnc-related... This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Cannot reproduce under F10. Seems to be fixed. Closing bug. |