[Bug 733349] Re: Minimize Application's Windows upon clicking its Launcher Icon

2013-11-09 Thread Sam Lesher
Please reconsider adding this feature.  It is the biggest factor keeping
me from embracing Unity as my daily desktop environment.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/733349

Title:
  Minimize Application's Windows upon clicking its Launcher Icon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/733349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 303304] Re: Gsynaptics doesn't show up anywhere in the XFCE system menu include

2008-12-28 Thread Sam Lesher
I'm not seeing the icon in Applications - Settings or Applications -
Settings Manager.   In the other bug, I see that a text label shows up
in Settings Manager, but I don't see it.

-- 
Gsynaptics doesn't show up anywhere in the XFCE system menu include
https://bugs.launchpad.net/bugs/303304
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 303304] [NEW] Gsynaptics doesn't show up anywhere in the XFCE system menu include

2008-11-28 Thread Sam Lesher
Public bug reported:

Binary package hint: gsynaptics

Xubuntu 8.10
gsynaptics version 0.9.14-6

What I expected to happen:  Installing the gsynaptics package from the
Universe repository should result in a Touchpad menu item under
Applications  System in the section of the XFCE applications menu that
is generated by having the system include in your menu configuration.

What happened instead:  After installing the package gsynaptics, there
is no resulting menu item anywhere in the Applications menu that is
generated by having a system menu include.   Under Gnome, the package
results in a menu item in the System  Preferences section of the menu.

** Affects: gsynaptics (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Gsynaptics doesn't show up anywhere in the XFCE system menu include
https://bugs.launchpad.net/bugs/303304
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 292867] Re: Can't lock screen on auto-login if gnome-keyring-daemon is requesting password

2008-11-26 Thread Sam Lesher
You can close this bug report.

-- 
Can't lock screen on auto-login if gnome-keyring-daemon is requesting password
https://bugs.launchpad.net/bugs/292867
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 292867] Re: Can't lock screen on auto-login if gnome-keyring-daemon is requesting password

2008-11-03 Thread Sam Lesher
I found a workaround that works for me:

Install the xlockmore package

Then, instead of using gnome-screensaver-command --lock command to
lock the screen, use xlock -mode blank.   This locks the display
immediately upon login.

-- 
Can't lock screen on auto-login if gnome-keyring-daemon is requesting password
https://bugs.launchpad.net/bugs/292867
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 292867] [NEW] Can't lock screen on auto-login if gnome-keyring-daemon is requesting password

2008-11-02 Thread Sam Lesher
Public bug reported:

8.10 Intrepid Ibex, Gnome
Background:  To facilitate VNC access to the default desktop session on 
terminal :0, I auto-login (via gdmsetup - security tab) and then immediately 
lock the screensaver with the command gnome-screensaver-command --lock.

The problem I am experiencing is that if any programs start on login
that prompt gnome-keyring-daemon to ask for a password, such as the
mail-notification application, the screensaver never locks.   This
means that if I restart my workstation remotely, it sits unlocked until
the screensaver activates or until I manually lock it.

Is there a better alternative to assure that I always have remote access
to the default session ( :0 ) on my workstation?   I would forgo auto-
login completely if I had a way to VNC to the login screen and log
myself in.  I believe there was a VNC xorg module, not sure if it still
exists or if it is currently functional (I believe it caused crashes on
Hardy).

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Description changed:

  8.10 Intrepid Ibex, Gnome
  Background:  To facilitate VNC access to the default desktop session on 
terminal :0, I auto-login (via gdmsetup - security tab) and then immediately 
lock the screensaver with the command gnome-screensaver-command --lock.
  
  The problem I am experiencing is that if any programs start on login
- that prompt gnome-keyring-daemon to ask for a password, the screensaver
- never locks.   This means that if I restart my workstation remotely, it
- sits unlocked until the screensaver activates or until I manually lock
- it.
+ that prompt gnome-keyring-daemon to ask for a password, such as the
+ mail-notification application, the screensaver never locks.   This
+ means that if I restart my workstation remotely, it sits unlocked until
+ the screensaver activates or until I manually lock it.
  
  Is there a better alternative to assure that I always have remote access
  to the default session ( :0 ) on my workstation?   I would forgo auto-
  login completely if I had a way to VNC to the login screen and log
  myself in.  I believe there was a VNC xorg module, not sure if it still
  exists or if it is currently functional (I believe it caused crashes on
  Hardy).

-- 
Can't lock screen on auto-login if gnome-keyring-daemon is requesting password
https://bugs.launchpad.net/bugs/292867
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 150592] Re: No Sound with RealTek HD Audio on Asus A7T (Alc882)

2007-11-19 Thread Sam Lesher
I have an Asus A7T as well, with ath ALC882 audio codec.  I was able to
fix my sound issue using the alsa-base package installed by default
(version 1.0.14-1ubuntu2 at the time of this writing). Here are the
steps:

A. Create a new file called “/etc/modprobe.d/snd-hda-intel.modprobe”:
$ sudo gedit /etc/modprobe.d/snd-hda-intel.modprobe

Add the following line to the file and then save it:
options snd-hda-intel model=w2jc

B. Edit the file “/etc/modprobe.d/alsa-base”:
$ sudo gedit /etc/modprobe.d/alsa-base

Add the same line to the end of this file and then save it:
options snd-hda-intel model=w2jc

C. Reboot. After I rebooted, I had sound.

-- 
No Sound with RealTek HD Audio on Asus A7T (Alc882)
https://bugs.launchpad.net/bugs/150592
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 108379] Re: Feisty - /etc/hosts.allow and /etc/hosts.deny are missing

2007-04-21 Thread Sam Lesher
** Description changed:

  Installed Feisty as a brand new installation on a formatted partition.
  
  The following two files are missing:
  
  /etc/hosts.allow
  /etc/hosts.deny
  
  These files were created by default by the Edgy installer, but are not
  created by the Feisty installer (live cd installer, official release).
  
- I found this error when installing the DenyHosts script.  It failed to
- start because the files were missing.
+ This became an issue for me when installing the DenyHosts script.  It
+ failed to start because the files were missing.

-- 
Feisty - /etc/hosts.allow and /etc/hosts.deny are missing
https://bugs.launchpad.net/bugs/108379
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 108379] Feisty - /etc/hosts.allow and /etc/hosts.deny are missing

2007-04-20 Thread Sam Lesher
Public bug reported:

Installed Feisty as a brand new installation on a formatted partition.

The following two files are missing:

/etc/hosts.allow
/etc/hosts.deny

These files were created by default by the Edgy installer, but are not
created by the Feisty installer (live cd installer, official release).

I found this error when installing the DenyHosts script.  It failed to
start because the files were missing.

** Affects: Ubuntu
 Importance: Undecided
 Status: Unconfirmed

-- 
Feisty - /etc/hosts.allow and /etc/hosts.deny are missing
https://bugs.launchpad.net/bugs/108379
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 108379] Re: Feisty - /etc/hosts.allow and /etc/hosts.deny are missing

2007-04-20 Thread Sam Lesher
** Changed in: base-installer (Ubuntu)
Sourcepackagename: None = base-installer

-- 
Feisty - /etc/hosts.allow and /etc/hosts.deny are missing
https://bugs.launchpad.net/bugs/108379
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs