[Bug 92296] Re: Low quality of text rendering in Evince
The problem is fixed for me on Ubuntu Hardy 8.04 amd64 (Evince 2.22.2 with poppler 0.6.4 (cairo)) -- Low quality of text rendering in Evince https://bugs.launchpad.net/bugs/92296 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 141160] Re: When remote desktop access is disabled, vino-session will still run
Ok, wonderful. But what about Gutsy? Shouldn't we do the same for Gutsy too? -- When remote desktop access is disabled, vino-session will still run https://bugs.launchpad.net/bugs/141160 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 141160] Re: When remote desktop access is disabled, vino-session will still run
Ok, now I am sure :) I just downloaded the sources for the gnome-session package (apt-get source gnome-session). In the file gnome-session-2.20.1 /gnome-session/ChangeLog you can read: 2.7.91 2004-08-16 Mark McLoughlin <[EMAIL PROTECTED]> * Makefile.am: add gsm-remote-desktop.[ch]. * gsm-remote-desktop.[ch]: add support for activating and re-spawning the remote desktop server based on the /desktop/gnome/remote_access/enabled key. * main.c: (main): use it. -- When remote desktop access is disabled, vino-session will still run https://bugs.launchpad.net/bugs/141160 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 141160] Re: When remote desktop access is disabled, vino-session will still run
I think vino-session should be disabled, here's why: 1) > This happens because vino on Ubuntu (which was merged from debian) > is compiled with --enable-session. Without that flag, the process > responsible for start/stop the deamon is gnome-session. > So, there are two ways: > 1) patch gnome-session to watch that key and run vino-server when the key is > true. > 2) deploy its own 'watcher', called vino-session, by passing --enable-session > to configure. Please read here: http://lists.alioth.debian.org/pipermail/pkg-gnome- maintainers/2007-July/036018.html I think we don't need vino-session because gnome-session is _already_ patched to watch the GConf key. To see that do the following: a) disable vino-session (see below) b) start gconf-editor and set /desktop/gnome/remote_access/enabled as true c) result: you'll see that vino-server has been started (ps -e w | grep vino) d) now set /desktop/gnome/remote_access/enabled as false e) wait some seconds f) result: you'll see that vino-server has been killed g) another proof: if you kill vino-server (killall vino-server) you'll see that in the file .xsession-errors appears the following line: "Session manager: gsm-remote-desktop.c:107: remote desktop server died, restarting", and the file gsm-remote-desktop.c belongs to the gnome-session package. 2) In the file /usr/share/gnome/default.session vino-session has Priority=50, but for some reason gnome-session-properties reports a priority of 05, and I haven't been able to change this priority, so I think this is a bug. 3) If I use vino-session and remote desktop is enabled, when I log out from gnome and then I log in again, gnome hangs and I can only see the brown background, but no panels or icons. File .xsession-errors reports: 1198440598.912730 Session manager: gsm-remote-desktop.c:107: remote desktop server died, restarting 1198440598.916107 Session manager: gsm-remote-desktop.c:107: remote desktop server died, restarting 1198440608.837906 Session manager: gsm-remote-desktop.c:130: activation of OAFIID:GNOME_RemoteDesktopServer failed: System exception: IDL:omg.org/CORBA/COMM_FAILURE:1.0 How to disable vino-session: open /usr/share/gnome/default.session then 1) change the value of num_clients from 6 to 5 2) comment the three lines starting with 5. Your default.session should look like mine (see attachment). Now log out and log back in again. John, Sebastien, please let me know what you think. Thanks. ** Attachment added: "default.session" http://launchpadlibrarian.net/11586817/default.session -- When remote desktop access is disabled, vino-session will still run https://bugs.launchpad.net/bugs/141160 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 172444] Re: [Gutsy] Logout a session causes X-Window changes from VT7 to VT9
Oh, sorry Nicolas, you're right. I just checked again and I still have the problem about VT9, on two different machines (amd64 and i386) running gutsy. But I've noticed that, even if Xorg uses VT9 from the second login on, it works fine for me. Anyway, that procedure resolved the problem with the remote desktop, so I think I should file a bug report on vino. -- [Gutsy] Logout a session causes X-Window changes from VT7 to VT9 https://bugs.launchpad.net/bugs/172444 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 172444] Re: [Gutsy] Logout a session causes X-Window changes from VT7 to VT9
When I upgraded from Feisty to Gutsy two days ago, I had the same problem. Looking at .xsession-errors I found the following error: 1198440598.912730 Session manager: gsm-remote-desktop.c:107: remote desktop server died, restarting 1198440598.916107 Session manager: gsm-remote-desktop.c:107: remote desktop server died, restarting 1198440608.837906 Session manager: gsm-remote-desktop.c:130: activation of OAFIID:GNOME_RemoteDesktopServer failed: System exception: IDL:omg.org/CORBA/COMM_FAILURE:1.0 This led me to think it was something related with remote desktop. So I fixed the problem by disabling it (the server name is "vino-server"). To do so, run from a terminal "vino-preferences" and disable remote desktop. Now reboot and it should work. This seems to fix bug #157622 too. I hope this helps. P.S.: I think there might be a bug in vino or in the gnome-session package (since gsm-remote-desktop.c belongs to that package), so this is just a quick fix. -- [Gutsy] Logout a session causes X-Window changes from VT7 to VT9 https://bugs.launchpad.net/bugs/172444 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157622] Re: gdm hangs after login in gutsy
When I upgraded from Feisty to Gutsy two days ago, I had the same problem. Looking at .xsession-errors I found the following error: 1198440598.912730 Session manager: gsm-remote-desktop.c:107: remote desktop server died, restarting 1198440598.916107 Session manager: gsm-remote-desktop.c:107: remote desktop server died, restarting 1198440608.837906 Session manager: gsm-remote-desktop.c:130: activation of OAFIID:GNOME_RemoteDesktopServer failed: System exception: IDL:omg.org/CORBA/COMM_FAILURE:1.0 This led me to think it was something related with remote desktop. So I fixed the problem by disabling it (the server name is "vino-server"). To do so, run from a terminal "vino-preferences" and disable remote desktop. Now reboot and it should work. This seems to fix bug #172444 too. I hope this helps. P.S.: I think there might be a bug in vino or in the gnome-session package (since gsm-remote-desktop.c belongs to that package), so this is just a quick fix. -- gdm hangs after login in gutsy https://bugs.launchpad.net/bugs/157622 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 159256] Re: xchat-gnome dumps at startup.
Pedro, this problem was already reported on bug #119693 (and a solution was provided), please read the comments in that bug report. I hope this helps. -- xchat-gnome dumps at startup. https://bugs.launchpad.net/bugs/159256 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 119693] Re: xchat-gnome 0.17 crashes on startup
Hi, I'm running Ubuntu Gutsy on a i386 and I've just upgraded my installation. Unfortunately, I still have this problem with xchat-gnome 1:0.18-0ubuntu2. When I try to run the program I get: [EMAIL PROTECTED]:~$ xchat-gnome XChat CRITICAL *** default event text failed to build! Aborted (core dumped) Does anyone have the same problem? ** Attachment added: "apt-cache_show_xchat-gnome" http://launchpadlibrarian.net/9692919/apt-cache_show_xchat-gnome -- xchat-gnome 0.17 crashes on startup https://bugs.launchpad.net/bugs/119693 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 92296] Re: [Feisty] Low quality of text rendering in Evince
I can confirm this too, and the problem happens only with pdf files that use Type 3 fonts (you can check which type of fonts your document is using by pressing ALT+Enter in Evince). Just a piece of advice: if you are using Latex and the Computer Modern fonts to write your documents, make sure you use the Type 1 version of the Computer Modern fonts (also called "bluesky"), so that you won't have any problem with this bug (for example, if you're using tetex like me, just install the package tetex-extra and you're done). I hope this helps. -- [Feisty] Low quality of text rendering in Evince https://bugs.launchpad.net/bugs/92296 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs