desktop May 2013

desktop@lists.fedoraproject.org

7 participants
3 discussions

Alt+Tab on screen display not disappearing
by Ryan Lerch 30 May '13

30 May '13

Just wondering if anyone else has experienced in F18 (GNOME3.6) a weird bug where the alt+tab switcher does not disappear? When it happens, i can press press alt+tab again and other switcher is displayed under (z-index wise) the one already on the screen. If i keep pressing alt+tab, these layer up also. The annoying part is that when you go to restart the shell, (with alt+f2), that overlay does not get keyboard focus, so you can't restart it from there. The only way to restart the shell is to switch to another tty, and kill the gnome-shell process with kill -9 anyone else experiencing this issue? cheers, ryanlerch

5 10

Adding open-vm-tools-desktop package to desktop group
by Ravindra Kumar 21 May '13

21 May '13

Hi, Currently, I'm maintaining open-vm-tools in Fedora. https://admin.fedoraproject.org/updates/open-vm-tools open-vm-tools provides significant functionality for VM management and helps in anything that requires co-ordination with the guest. open-vm-tools package provides a sub-package open-vm-tools-desktop. open-vm-tools-desktop is a very small package and provides integration of VM's desktop UI with host UI or remote client UI. It is essential for improved user experience of the VM UI, e.g. things like copy/paste, proper VM UI screen resolution. This package spawns a process on each user login (the process is stopped during logout). The process exits gracefully if the desktop is not running on a VMware VM. I would like to include open-vm-tools-desktop package as part of most of the desktop package groups in Fedora by default. Could you please help me with the process to make the necessary changes? FYI, I'm working with Fedora group to include open-vm-tools as part of @standard group. Thanks, Ravindra

4 6

Samba network printers unusable with default Fedora Desktop installs
by Elad Alfassa 13 May '13

13 May '13

I recently discovered that if I have a printer attached to a Windows machine (and shared via samba), it'll unusable on default install, because samba-client isn't installed by default. control-center's printers panel managed to discover the printer, but after the driver prompt dialog it gave a cryptic error message and did not install the printer. After installing samba-client, adding a samba network printer worked as expected. Therefor I suggest we add samba-client to our default installation, it's only 1.2MB. Ideally I think it should be added as a Requires in control-center's spec file, but we could add it to comps instead. If you think adding this to the default install is a bad idea, control-center should install it with packagekit whenever users tries to add a Samba printer. On a related (printing) note, I think it would also make sense to have hpijs as a default as well, to support more printers. -- -Elad Alfassa.

7 25

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop May 2013