[Bug 876105] Re: Remote Desktop Viewer (vinagre) does not remember passwords
Update. It only seems to remember it as long as I dont close vinagre. If I disconnect and reconnect, it remembers the password, but if I close vinagre, it still forgets the password. *sigh* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876105 Title: Remote Desktop Viewer (vinagre) does not remember passwords To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/876105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876105] Re: Remote Desktop Viewer (vinagre) does not remember passwords
I got bit by this. I fixed it by removing $HOME/.vnc/passwd after that, vinagre remembers passwords correctly again. Not sure why this works, since vinagre doesn't recreate the file, but it fixed the problem for me. Give it a try and see if it works for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876105 Title: Remote Desktop Viewer (vinagre) does not remember passwords To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/876105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778682] [NEW] mdadm/raid1 breaks suspend to ram natty
Public bug reported:
Upon upgrading from maverick to natty, suspend to ram broke on my
system.
When I suspend the system, it starts to suspend, but does not power all
the way down. The CPU fans keep running, and the display remains
active, but no keyboard or mouse activity is accepted. The only way out
of it is to reset/power cycle the machine. I tried suspending with
pm_trace active, but nothing useful was captured in the dmesg after
reset.
I booted the natty livecd, and ran checkbox through the
suspend_30_cycles test while running from the livecd. This test passed.
I suspected the nvidia driver initially, but ruled it out after
reproducing the problem with the nvidia module unloaded. So that left
some other difference between the livecd running kernel and my installed
system.I booted the livecd again, and reproduced the problem by
installing the mdadm package and activating RAID1 devices.
To reproduce:
boot livecd, drop to console
apt-get install mdadm
mdadm --auto-detect
cat /proc/mdstat # verify that the devices were detected
pm-suspend
and here the system hangs. I did this 5 times in a row and it hung
every single time.
Obviously it was in the middle of a reconstruct on the RAID1 device each
time, but I do not think that matters. It hangs on the installed
system even if there is no reconstruction running.
I don't know how to further dig into this, but I will be happy to
provide more information.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.42
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mschout1896 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfb20 irq 44'
Mixer name : 'Realtek ALC888'
Components : 'HDA:10ec0888,8086d608,0011'
Controls : 26
Simple ctrls : 15
Date: Fri May 6 13:37:38 2011
HibernationDevice: RESUME=UUID=6a0de2fd-c2e1-4853-8077-4e10e0b3854e
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
LANGUAGE=en_US:en
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic
root=/dev/mapper/vg00-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-2.6.38-8-generic N/A
linux-backports-modules-2.6.38-8-generic N/A
linux-firmware1.52
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 03/18/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PRG3110H.86A.0071.2010.0318.1704
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG31PR
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD97573-302
dmi.chassis.type: 3
dmi.modalias:
dmi:bvnIntelCorp.:bvrPRG3110H.86A.0071.2010.0318.1704:bd03/18/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-302:cvn:ct3:cvr:
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug natty running-unity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778682
Title:
mdadm/raid1 breaks suspend to ram natty
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778682] Re: mdadm/raid1 breaks suspend to ram natty
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778682 Title: mdadm/raid1 breaks suspend to ram natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778682] Re: mdadm/raid1 breaks suspend to ram natty
Just to clarify a few things on this: 1) my system suspended fine in maverick. 2) if running from the natty livecd, suspend works fine. It only fails if you have activated the raid devices (via mdadm --auto-detect). I verified that pm-suspend worked after installing mdadm, and it does. It only fails after activating the md devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778682 Title: mdadm/raid1 breaks suspend to ram natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771905] Re: No logo at boot on nvidia card
Similar situation here. was getting only a purple screen since upgrade to natty. I removed the plymouth fixes that I had applied in maverick and now I get the text plymouth, but its wierd.. the text mode only takes up the top left corner of my screen because it's (apparently) booting in the correct resolution. I still do not get the graphical plymouth on startup, only on shutdown. To get the text plymouth here is what I did: in /etc/default/grub: removed nomodeset video=uvesafb:mode_option=1680x1050-24,mtrr=3,scroll=ywrap from GRUB_CMDLINE_LINUX removed line: GRUB_GFXMODE=1680x1050 in /etc/initramfs-tools/modules: removed line: uvesafb mode_option=1680x1050-24@60 mtrr=3 scroll=ywrap then ran update-grub After this I get a text plymouth, but its tiny, and only takes up the upper-left corner of my screen because apparently the machine is booting in normal resolution, but is not using the graphical plymouth. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771905 Title: No logo at boot on nvidia card -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
