rationale: * vinagre's UI doesn't allow me to manually enter a server to connect to, instead it forces me to use a "network search" that of course doesn't return anything. (it doesn't have a problem accepting a manually provided server when starting from the console though) * it doesn't handle keyboard layouts properly when connecting to OSXVnc (now Vine Server, a VNC server for Mac OSX) * it is bloated compared to tigervnc (almost 5MB for vinagre compared to 660KB for tigervnc) the main problem that makes it useless at least for me is the keyboard problem. The UI problem can be workarounded by launching it via commandline (but I wonder what the designers of the UI did smoke^H^H^H^H^H^H^H^H^H were thinking when they made the entry box disabled for text-input, they don't have a problem when the user manually enters a ssh-connection address)
Component: Installer => New RPM package request
CC: (none) => sysadmin-bugsComponent: New RPM package request => Release (media or process)
sorry bugzilla is sometimes bogus :/
Assignee: bugsquad => mageia
ping - there was requests on the mailinglist as to what packages to remove/replace to free some diskspace on the live-isos. Here you have one! (admittedly a small gain, but anyway..)
CC: sysadmin-bugs => (none)Assignee: mageia => bugsquad
Source RPM: (none) => dralmive
Source RPM: dralmive => draklive
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
As this bug applies to the live iso content, it should remain as a cauldron bug.
Keywords: NEEDINFO => (none)CC: (none) => davidwhodgins
This is one of 8 hyper-stale bugs and enhancement requests (other than package requests) that are now being closed as old. Each of them * is still assigned to BugSquad instead of to a maintainer * did not see any action since June 2012 If this one is still valid, then please reopen it. In that case: don't be shocked that I closed it: There is more chance it'll get fixed after it's wrongly closed and then reopened again (because of the mails Bugzilla sends to many packagers etc. when there is some action in a bug), than when nothing happens in this report for some more years :-)
Status: NEW => RESOLVEDResolution: (none) => OLD