[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
There is a fundamental difference between search (what you do when you don't know where something is) and navigate (what you do when you know exactly where something is, and want to go there). Why the gnome team have chosen to conflate them, and their mental state while doing so, is anyone's guess. But from a usability perspective, it is broken. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
It's a shame there is no way to vote for things here, and instead weight seems given to bugs with a large number of comments / activity. The current version of nautilus, which is the very core of Ubuntu, is broken. Search is not the same as navigation. I do not want to search my files when I know exactly where the file I want is - I want to go to it. There are full time Ubuntu developers. This should not be waiting for a user to contribute a patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Won't Fix Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
> Oh I see why: most of us cannot change back the status of the bug once it has been changed to "fix released" (which is stupid, too). If that is genuinely the reason (and this bug has been marked as "Fix Released" since Jan 2014, so it seems correct), then is it not time to raise a new bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 755342] Re: Samsung Xcover 271 B2710 mass storage does not mount automatically
This is with the same phone from #14 $ cd /sys/bus/usb/drivers/usb-storage/2-1.6:1.0/host7/target7:0:0/7:0:0:0 $ cat vendor Samsung $ cat model GT-S5510T $ cat rev 2.31 I couldn't find directory 'usb-storage' in /sys/usb/drivers unless I did 'DisableSwitching=1'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/755342 Title: Samsung Xcover 271 B2710 mass storage does not mount automatically Status in usb-modeswitch package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. In the interface of the Samsung Xcover 271 B2710, set it to connect as mass storage. 2. Connect it to the computer via USB cabel. Notice that it does not mount automatically. Also it does mount automatically when instead of step 1 it is set to connect to Samsung Kies or to sync with a media player. Below I provide output from dmesg and lsusb -vv. Output from dmesg as it is connected (step 2): [101332.680133] usb 2-6: new high speed USB device using ehci_hcd and address 6 [101333.630726] Initializing USB Mass Storage driver... [101333.630861] scsi5 : usb-storage 2-6:1.0 [101333.630956] usbcore: registered new interface driver usb-storage [101333.630958] USB Mass Storage support registered. Output from lsusb -vv: Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize064 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice2.06 iManufacturer 3 iProduct2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 can't get hub descriptor: Operation not permitted cannot read device status, Operation not permitted (1) Bus 006 Device 002: ID 046d:c01b Logitech, Inc. MX310 Optical Mouse Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc01b MX310 Optical Mouse bcdDevice 18.00 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 98mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 64 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN
[Desktop-packages] [Bug 1223181] Re: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging
Seems to be related to KDE bug #324438 (https://bugs.kde.org/show_bug.cgi?id=324438) which was fixed in KDE bug #329112 (https://bugs.kde.org/show_bug.cgi?id=329112). There is a patch and reference to a git commit in #329112 which claims to have fixed the problem. ** Bug watch added: KDE Bug Tracking System #329112 https://bugs.kde.org/show_bug.cgi?id=329112 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1223181 Title: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging Status in “gtk+2.0” package in Ubuntu: Confirmed Bug description: to reproduce, I open the Variables view in eclipse and step through the application. the eclipse jvm crashes with: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f3dea4082aa, pid=11567, tid=139905336198912 # # JRE version: 7.0_21-b11 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgtk-x11-2.0.so.0+0x2202aa] gtk_tree_view_get_background_area+0x8a # # Core dump written. Default location: /home/juergen/core or core.11567 # # An error report file with more information is saved as: # /home/juergen/hs_err_pid11567.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # This did not happen in ubuntu 13.04. using KDE as a desktop (installed ubuntu, installed kde packages) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk2.0-0 2.24.20-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Tue Sep 10 07:25:17 2013 InstallationDate: Installed on 2010-11-24 (1020 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True SourcePackage: gtk+2.0 UpgradeStatus: Upgraded to saucy on 2013-08-29 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
To add my voice to this bug, I installed 13.04 today, on my work computer (previously Windows 7 only), to enable me to use a variety of bash scripts to process a large number of files on an external ext3 drive. At home I have 12.10 installed. The files are images, several thousand per folder, stored in dated folders (such as 11-04-23-country_location). Now I know, for example, that I was in Belgium in May 2005, so I type '05-05' and a folder NEAR the one I want was previously highlighted, allowing me to quickly and easily find the correct folder. A related task is to go to the next, and previous, folders. Both of these uses are broken with the new search set-up. The Gnome team's total brick-walling of the furious users should give pause for thought. I simply cannot believe they have shot themselves in the foot so categorically as to make the staple piece of software, that underpins their entire user interface, so crippled. This is a far more serious usability issue than anything thrown up with the migration to Unity. I would rate it, probably, as the highest, most disruptive user interface bug I have ever come across in Ubuntu (and I've been with you since Warty). The workaround linked by M4he above is good news, but the idea of having to install a patch to get basic file-browser functionality is insane. Even more insane than firing up Mac OSX and being faced with the abomination that is Finder. Sebastian, it's great news that Ubuntu are listening, and seeing this as an issue, and I hope a proper solution is forthcoming. At what point does a frankly bizarre upstream user interface decision like this become priority #1 at Canonical? When it begins to compromise the very good work being done with Unity? When does it become worth moving a developer from Unity onto an issue like this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Invalid Status in “nautilus” package in Ubuntu: Triaged Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1070677] Re: Xorg fails to start because of Radeon Issue
Similar to item #5. Using 3.2.0-33 pae on 32 bit, cannot get X to start when using the VGA port. The DVI port does however work. Reverting back to 3.2.0-32 is a good work around. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1070677 Title: Xorg fails to start because of Radeon Issue Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed Bug description: Roughly 30% of the time I boot my system X does not start, instead I boot into a shell. Looking at the Xorg.log I see: [19.593] (EE) RADEON(0): [drm] failed to set drm interface version. [19.593] (EE) RADEON(0): Kernel modesetting setup failed [19.593] (II) UnloadModule: radeon [19.593] (II) Unloading radeon [19.593] (EE) Screen(s) found, but none have a usable configuration. [19.593] Fatal server error: [19.593] no screens found ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Uname: Linux 3.2.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Oct 24 01:40:51 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Redwood [Radeon HD 5670] [1002:68d8] (prog-if 00 [VGA controller]) Subsystem: VISIONTEK Device [1545:5670] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-UD2H ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-33-generic root=UUID=e50fd3cf-9c17-4365-845e-1eb7d14d512e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-880GMA-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd09/30/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1070677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 755342] Re: Samsung Xcover 271 B2710 mass storage does not mount automatically
Regarding comment #8. Can now confirm that usb_modeswitch is not working with Kubuntu 12.04. Changing the config file to 'DisableSwitching=1' provides a fix. Have enabled debugging (EnableLogging=1) and collected debugging information with 'DisableSwitching=0'. File is attached. ** Attachment added: usb_modeswitch.log https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/755342/+attachment/3399845/+files/usb_modeswitch.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/755342 Title: Samsung Xcover 271 B2710 mass storage does not mount automatically Status in “usb-modeswitch” package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. In the interface of the Samsung Xcover 271 B2710, set it to connect as mass storage. 2. Connect it to the computer via USB cabel. Notice that it does not mount automatically. Also it does mount automatically when instead of step 1 it is set to connect to Samsung Kies or to sync with a media player. Below I provide output from dmesg and lsusb -vv. Output from dmesg as it is connected (step 2): [101332.680133] usb 2-6: new high speed USB device using ehci_hcd and address 6 [101333.630726] Initializing USB Mass Storage driver... [101333.630861] scsi5 : usb-storage 2-6:1.0 [101333.630956] usbcore: registered new interface driver usb-storage [101333.630958] USB Mass Storage support registered. Output from lsusb -vv: Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize064 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice2.06 iManufacturer 3 iProduct2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 can't get hub descriptor: Operation not permitted cannot read device status, Operation not permitted (1) Bus 006 Device 002: ID 046d:c01b Logitech, Inc. MX310 Optical Mouse Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc01b MX310 Optical Mouse bcdDevice 18.00 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 98mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 64 Report Descriptors: **
[Desktop-packages] [Bug 741067] Re: Returning from console to guest session asks for a non-existent password
Robert, this happens in lightdm with a default 12.04 install, and is fully reproduceable. Simply switching out of and back into the guest session prompts for password. This is a re-occurance of bug 275768, recorded (and fixed) in October 2008. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/741067 Title: Returning from console to guest session asks for a non-existent password Status in “gdm-guest-session” package in Ubuntu: New Status in “lightdm” package in Ubuntu: Incomplete Bug description: Binary package hint: gdm-guest-session gdm-guest-session 0.23, gdm 2.32.0-0ubuntu12, Ubuntu Natty 1. Switch to a guest session. 2. Type Ctrl+Alt+F6 to switch to a console. 3. Type Alt+F8 to return to GDM. 4. Choose the guest session. What happens: The login screen asks you for a password for the guest session. What should happen: The login screen should not ask you for a password. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm-guest-session/+bug/741067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
