[Bug 387970] Re: cups asks for root password

2010-05-01 Thread John P. Richardson 
I think this is more than just a printing issue.  When trying to do
Sini's suggested workaround, I am not able to make changes to ANY user
accounts because it is asking for a root password to do so.  This is on
a clean install of 10.04.  See screenshot for visual proof.

** Attachment added: root-request-usergroups.png
   http://launchpadlibrarian.net/47035015/root-request-usergroups.png

-- 
cups asks for root password
https://bugs.launchpad.net/bugs/387970
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 296028] Re: FreeCell Soltaire Fullscreen bug

2009-01-05 Thread John P. Richardson 
Problem: Can't exit fullscreen mode in Aisleriot Solitaire (Ubuntu 8.10).
Just ran into this myself.  Reloaded one of my systems with 8.10 and installed 
all updates.  After playing a few rounds of Solitaire for the first time since 
the reload, I tried to exit full screen mode and could not.  Pressing F11 or 
clicking on the Leave Full Screen button caused the window to resize then go 
back to full screen.  Only way to exit was Alt+F4.

I logged out and logged back in as another user (my wife).  Solitaire
started in non-fullscreen/non-maximized mode.  I pressed F11, played two
hands then pressed F11 again.  Worked fine.  Logged out then logged in
as myself.  Problem still there.

Solution:
1. Open terminal.
2. Start gconf-editor (don't use sudo).
3. Navigate to Apps-Aisleriot.
4. Locate the maximized key and ensure it is unchecked.
5.  Locate the fullscreen key and ensure it is unchecked.
11. Exit gconf-editor.
12. Start Aisleriot Solitaire.  It should come up in 
non-fullscreen/non-maximized mode.

System: Homebrew
Motherboard: MSI MS7253
Video card:  VIA Chrome9 integrated in K8M890 chipset
X Version: 7.4~5ubuntu3

-- 
FreeCell Soltaire Fullscreen bug
https://bugs.launchpad.net/bugs/296028
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 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2009-01-05 Thread John P. Richardson 
And for what it's worth, the Smartparts USB picture frame in my last entry 
above works fine on the following system:
System: IBM Thinkpad A31 model 2652-XXJ
Kernel: 2.6.24-22-generic
Distro: Xubuntu 8.04 with all updates

-- 
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
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 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices

2009-01-02 Thread John P. Richardson 
More petrol for the fire...

Test Device: Smartparts PXE7 7 LCD digital picture frame
Test System 1: MSI Wind netbook running Xubuntu 8.10 kernel 2.6.27-9-generic
Test System 2: Homebrew kit running Ubuntu 8.10 kernel 2.6.27-11-generic on MSI 
MS-7253 mainboard.

When I plug the picture frame into the MSI Wind, it works brilliantly.

When I plug the picture frame into the Homebrew system, I get the same
problems as everyone else.  See the attached excerpt from dmesg.

Reducing the max sectors to 128 or 64  has no effect.  Only solution is
to sudo modprobe -r ehci_hcd each time I want to access the device.



** Attachment added: Excerpt of dmesg output for USB I/O issue
   http://launchpadlibrarian.net/20872999/dmesg-output.txt

-- 
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
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 253468] Re: [Hardy] Ejecting usb hard disk gives error and remounts

2008-08-27 Thread John P. Richardson 
This same issue occurs with me regardless of type of USB device, ie -
USB thumb drive or USB external hard drive.  This problem did not happen
in 7.10.  Seems to me that eject is being called when umount would be
more appropriate.

-- 
[Hardy] Ejecting usb hard disk gives error and remounts
https://bugs.launchpad.net/bugs/253468
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 245852] Re: nm-applet saves the wrong key

2008-08-26 Thread John P. Richardson 
I am having a very similar problem.  In my case, the only way I can
restore my network connection after a restart/shutdown is to delete the
network via Edit Wireless Networks then click on my wireless network
in the list presented by nm-applet.

Looking at the password in the details for my network in Edit Wireless
Networks shows the wrong password; it's actually my old WEP password
from before my switch to WPA with TKIP.  Changing the password and
clicking on Set Password does not save the new open.

I am running Ubunut 8.04 with nm-applet 0.6.6 with a Netgear WG311T NIC.

The only relevant info I can glean from /var/log/syslog is this:

Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) started... 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) Stage 1 of 5 
(Device Prepare) scheduled... 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) Stage 1 of 5 
(Device Prepare) started... 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) Stage 2 of 5 
(Device Configure) scheduled... 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) Stage 1 of 5 
(Device Prepare) complete. 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) Stage 2 of 5 
(Device Configure) starting... 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0/wireless): 
access point 'STARFLEET' is encrypted, but NO valid key exists.  New key 
needed. 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) New wireless 
user key requested for network 'STARFLEET'. 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) Stage 2 of 5 
(Device Configure) complete. 


Note that this is before I delete the network via Edit Wireless Networks.  
After the deletion I get this:

Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) started... 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) Stage 1 of 5 
(Device Prepare) scheduled... 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) Stage 1 of 5 
(Device Prepare) started... 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) Stage 2 of 5 
(Device Configure) scheduled... 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) Stage 1 of 5 
(Device Prepare) complete. 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) Stage 2 of 5 
(Device Configure) starting... 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0/wireless): 
access point 'STARFLEET' is encrypted, but NO valid key exists.  New key 
needed. 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) New wireless 
user key requested for network 'STARFLEET'. 
Aug 26 06:59:35 PACIFICA NetworkManager: info  Activation (ath0) Stage 2 of 5 
(Device Configure) complete. 
Aug 26 06:59:50 PACIFICA NetworkManager: info  Activation (ath0) New wireless 
user key for network 'STARFLEET' received. 
Aug 26 06:59:50 PACIFICA NetworkManager: info  Activation (ath0) Stage 1 of 5 
(Device Prepare) scheduled... 
Aug 26 06:59:50 PACIFICA NetworkManager: info  Activation (ath0) Stage 1 of 5 
(Device Prepare) started... 
Aug 26 06:59:50 PACIFICA NetworkManager: info  Activation (ath0) Stage 2 of 5 
(Device Configure) scheduled... 
Aug 26 06:59:50 PACIFICA NetworkManager: info  Activation (ath0) Stage 1 of 5 
(Device Prepare) complete. 
Aug 26 06:59:50 PACIFICA NetworkManager: info  Activation (ath0) Stage 2 of 5 
(Device Configure) starting... 
Aug 26 06:59:50 PACIFICA NetworkManager: info  Activation (ath0/wireless): 
access point 'STARFLEET' is encrypted, and a key exists.  No new key needed. 
Aug 26 06:59:51 PACIFICA NetworkManager: info  SUP: response was 'OK' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: sending command 'AP_SCAN 
1' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: response was 'OK' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: sending command 
'ADD_NETWORK' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: response was '0' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: sending command 
'SET_NETWORK 0 ssid 53544152464c454554' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: response was 'OK' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: sending command 
'SET_NETWORK 0 proto WPA' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: response was 'OK' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: sending command 
'SET_NETWORK 0 key_mgmt WPA-PSK' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: response was 'OK' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: sending command 
'SET_NETWORK 0 psk key' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: response was 'OK' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: sending command 
'SET_NETWORK 0 pairwise TKIP' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: response was 'OK' 
Aug 26 06:59:52 PACIFICA NetworkManager: info  SUP: sending command 
'SET_NETWORK 0 group TKIP' 
Aug 26 06:59:52 PACIFICA NetworkManager: info