[Desktop-packages] [Bug 388553] Re: Wi-Fi Protected Setup (WPS) not supported
Ran into this problem at a patients house today. I am running Ubuntu 16.04 and usually connect through my cell phone as a mobile hotspot, but there was no cell service at the location I went to. The patient has wifi in her house, but it only works with Windows 10 with WPS button on the router. Even though she gave me the password, I could not connect. Her new Verizon supplied router only wants WPS connections for some reason. Anyway, Ubuntu should really be able to do this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/388553 Title: Wi-Fi Protected Setup (WPS) not supported Status in Ayatana Design: New Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: As the title the Wi-Fi Protected Setup (WPS) is not supported by NetworkManager (but is supported by wpa_supplicant). The WPS WI-Fi standard is implementated in various newer access points and allow user to configure the access point in just a few of steps and do all configuring process very simple. Specifications: http://www.wi-fi.org/wifi-protected-setup/ To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/388553/+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 1310174] Re: "cryptsetup" should be included and installed by default in ubuntu 14.04
Problem continues in 16.04. This really should be installed by default or the error message should be useful and offer to install it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1310174 Title: "cryptsetup" should be included and installed by default in ubuntu 14.04 Status in cryptsetup package in Ubuntu: Incomplete Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: After upgrade from ubuntu 13.10 to 14.04 lts, I am unable to ulock my luks device. It gives the following error message: Error unlocking /dev/sda6: Error spawning command-line `cryptsetup luksOpen "/dev/sda6" "luks-9082ff43-d991-4bf1-8bb6-ef8452e3e11a" ': Failed to execute child process "cryptsetup" (No such file or directory) (g-exec-error-quark, 8) Then I noticed that the package "cryptsetup" was not installed in my system. "cryptsetup" should be included and installed as default in ubuntu 14.04 lts, as it was in the previous releases. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cryptsetup (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 20 13:21:55 2014 InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1310174/+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 1352374] Re: changing backlight color on saitek eclipse 2 keyboard causes mouse failure
I have tested it as you requested with the 64 bit 15.04 daily image. There is no change in behavior. The problem persists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1352374 Title: changing backlight color on saitek eclipse 2 keyboard causes mouse failure Status in xorg package in Ubuntu: Incomplete Bug description: This has apparently been ongoing for a long time. I have a Saitek Eclipse ii keyboard and I and others report that when you click the keyboard button to change the back light color, it triggers mouse events. These end up disabling the mouse, in my case Microsoft Intellimouse. Unplugging and replugging the USB cable for the keyboard resets function to normal with the default blue back light color. If you try to change the color, the problem returns. I am now running 64 bit 14.04 and the problem has been with me since at least 12.04. If I change the backlight color while the system is booting up but before the log in screen appears, I can select the color I want the keyboard to be, but if I wait till after the log in screen appears, then the mouse is non-functional when the desktop loads until I log off and back on. Here is some relevant data from a report on Ubuntu forums (http://ubuntuforums.org/showthread.php?t=2174670) about this exact problem... /dev/input/event5 bustype : BUS_USB vendor : 0x6a3 product : 0x8021 version : 273 name : "Chicony Saitek Eclipse II Keyboa" phys : "usb-:00:1d.0-1/input0" uniq : "" bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP /dev/input/event6 bustype : BUS_USB vendor : 0x6a3 product : 0x8021 version : 273 name : "Chicony Saitek Eclipse II Keyboa" phys : "usb-:00:1d.0-1/input1" uniq : "" bits ev : EV_SYN EV_KEY EV_MSC The feature that causes the problem here is the button to turn on/off/change the kb backlight color. input-events for /dev/input/event6: First press (backlight off->blue): emulates left click 19:43:40.885931: EV_MSC MSC_SCAN -16646143 19:43:40.885936: EV_KEY BTN_0 (0x100) pressed 19:43:40.885941: EV_MSC MSC_SCAN -16646140 19:43:40.885942: EV_KEY BTN_3 (0x103) released 19:43:40.885943: EV_SYN code=0 value=0 Second press (blue->red): emulates middle click 19:43:43.101984: EV_MSC MSC_SCAN -16646143 19:43:43.101989: EV_KEY BTN_0 (0x100) released 19:43:43.101992: EV_MSC MSC_SCAN -16646142 19:43:43.101992: EV_KEY BTN_1 (0x101) pressed 19:43:43.101996: EV_SYN code=0 value=0 Third press (red->purple): emulates right click 19:43:38.005865: EV_MSC MSC_SCAN -16646142 19:43:38.005869: EV_KEY BTN_1 (0x101) released 19:43:38.005871: EV_MSC MSC_SCAN -16646141 19:43:38.005872: EV_KEY BTN_2 (0x102) pressed 19:43:38.005874: EV_SYN code=0 value=0 Fourth press (purple->off) emulates ??? 19:43:39.765915: EV_MSC MSC_SCAN -16646141 19:43:39.765921: EV_KEY BTN_2 (0x102) released 19:43:39.765925: EV_MSC MSC_SCAN -1664614019 19:43:39.765926: EV_KEY BTN_3 (0x103) pressed 19:43:39.765928: EV_SYN code=0 value=0 So, the backlight changing on a keyboard act as different types of mouse clicks based on what color you switch to. Apparently this problem is also present in PCLinuxOS. Is this possibly a Udev issue? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,mousepoll,snap,move,vpswitch,regex,place,animation,session,imgpng,grid,gnomecompat,wall,resize,expo,unitymtgrabhandles,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Aug 4 09:47:36 2014 DistUpgraded: 2014-08-02 23:43:24,960 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1556] InstallationDate: Installed on 2009-11-04 (1733 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-ge
[Desktop-packages] [Bug 1352374] Re: changing backlight color on saitek eclipse 2 keyboard causes mouse failure
Status New I have updated the BIOS from version 1503 (1-16-13) to version 2501. Here is the output of your command: marty@tux:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date [sudo] password for marty: 2501 04/07/2014 marty@tux:~$ The behavior is unchanged from before the BIOS update. If I wait until the system finishes booting and I am on my desktop and attempt to change the start up color of the keyboard illumination from blue to red, I lose most mouse left and right click ability on the desktop area. I can still click the gear icon and have the system log off and log back on as long as I don't wait too long. The longer I wait to attempt the log off, the less mouse function I have until all it does is move the cursor around, but nothing is clickable. The keyboard will still function for a much longer period of time until everything becomes unresponsive. My current work around is to change the keyboard color as soon as the boot process starts to load the Linux kernel. If I wait until I am on the desktop to change the color, then I must immediately log off and back on and everything is fine as long as I don't attempt to change the color again. Any further changes of keyboard color require an immediate log off and on to keep the system stable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1352374 Title: changing backlight color on saitek eclipse 2 keyboard causes mouse failure Status in xorg package in Ubuntu: Incomplete Bug description: This has apparently been ongoing for a long time. I have a Saitek Eclipse ii keyboard and I and others report that when you click the keyboard button to change the back light color, it triggers mouse events. These end up disabling the mouse, in my case Microsoft Intellimouse. Unplugging and replugging the USB cable for the keyboard resets function to normal with the default blue back light color. If you try to change the color, the problem returns. I am now running 64 bit 14.04 and the problem has been with me since at least 12.04. If I change the backlight color while the system is booting up but before the log in screen appears, I can select the color I want the keyboard to be, but if I wait till after the log in screen appears, then the mouse is non-functional when the desktop loads until I log off and back on. Here is some relevant data from a report on Ubuntu forums (http://ubuntuforums.org/showthread.php?t=2174670) about this exact problem... /dev/input/event5 bustype : BUS_USB vendor : 0x6a3 product : 0x8021 version : 273 name : "Chicony Saitek Eclipse II Keyboa" phys : "usb-:00:1d.0-1/input0" uniq : "" bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP /dev/input/event6 bustype : BUS_USB vendor : 0x6a3 product : 0x8021 version : 273 name : "Chicony Saitek Eclipse II Keyboa" phys : "usb-:00:1d.0-1/input1" uniq : "" bits ev : EV_SYN EV_KEY EV_MSC The feature that causes the problem here is the button to turn on/off/change the kb backlight color. input-events for /dev/input/event6: First press (backlight off->blue): emulates left click 19:43:40.885931: EV_MSC MSC_SCAN -16646143 19:43:40.885936: EV_KEY BTN_0 (0x100) pressed 19:43:40.885941: EV_MSC MSC_SCAN -16646140 19:43:40.885942: EV_KEY BTN_3 (0x103) released 19:43:40.885943: EV_SYN code=0 value=0 Second press (blue->red): emulates middle click 19:43:43.101984: EV_MSC MSC_SCAN -16646143 19:43:43.101989: EV_KEY BTN_0 (0x100) released 19:43:43.101992: EV_MSC MSC_SCAN -16646142 19:43:43.101992: EV_KEY BTN_1 (0x101) pressed 19:43:43.101996: EV_SYN code=0 value=0 Third press (red->purple): emulates right click 19:43:38.005865: EV_MSC MSC_SCAN -16646142 19:43:38.005869: EV_KEY BTN_1 (0x101) released 19:43:38.005871: EV_MSC MSC_SCAN -16646141 19:43:38.005872: EV_KEY BTN_2 (0x102) pressed 19:43:38.005874: EV_SYN code=0 value=0 Fourth press (purple->off) emulates ??? 19:43:39.765915: EV_MSC MSC_SCAN -16646141 19:43:39.765921: EV_KEY BTN_2 (0x102) released 19:43:39.765925: EV_MSC MSC_SCAN -1664614019 19:43:39.765926: EV_KEY BTN_3 (0x103) pressed 19:43:39.765928: EV_SYN code=0 value=0 So, the backlight changing on a keyboard act as different types of mouse clicks based on what color you switch to. Apparently this problem is also present in PCLinuxOS. Is this possibly a Udev issue? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38
[Desktop-packages] [Bug 1352374] [NEW] changing backlight color on saitek eclipse 2 keyboard causes mouse failure
Public bug reported: This has apparently been ongoing for a long time. I have a Saitek Eclipse ii keyboard and I and others report that when you click the keyboard button to change the back light color, it triggers mouse events. These end up disabling the mouse, in my case Microsoft Intellimouse. Unplugging and replugging the USB cable for the keyboard resets function to normal with the default blue back light color. If you try to change the color, the problem returns. I am now running 64 bit 14.04 and the problem has been with me since at least 12.04. If I change the backlight color while the system is booting up but before the log in screen appears, I can select the color I want the keyboard to be, but if I wait till after the log in screen appears, then the mouse is non-functional when the desktop loads until I log off and back on. Here is some relevant data from a report on Ubuntu forums (http://ubuntuforums.org/showthread.php?t=2174670) about this exact problem... /dev/input/event5 bustype : BUS_USB vendor : 0x6a3 product : 0x8021 version : 273 name : "Chicony Saitek Eclipse II Keyboa" phys : "usb-:00:1d.0-1/input0" uniq : "" bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP /dev/input/event6 bustype : BUS_USB vendor : 0x6a3 product : 0x8021 version : 273 name : "Chicony Saitek Eclipse II Keyboa" phys : "usb-:00:1d.0-1/input1" uniq : "" bits ev : EV_SYN EV_KEY EV_MSC The feature that causes the problem here is the button to turn on/off/change the kb backlight color. input-events for /dev/input/event6: First press (backlight off->blue): emulates left click 19:43:40.885931: EV_MSC MSC_SCAN -16646143 19:43:40.885936: EV_KEY BTN_0 (0x100) pressed 19:43:40.885941: EV_MSC MSC_SCAN -16646140 19:43:40.885942: EV_KEY BTN_3 (0x103) released 19:43:40.885943: EV_SYN code=0 value=0 Second press (blue->red): emulates middle click 19:43:43.101984: EV_MSC MSC_SCAN -16646143 19:43:43.101989: EV_KEY BTN_0 (0x100) released 19:43:43.101992: EV_MSC MSC_SCAN -16646142 19:43:43.101992: EV_KEY BTN_1 (0x101) pressed 19:43:43.101996: EV_SYN code=0 value=0 Third press (red->purple): emulates right click 19:43:38.005865: EV_MSC MSC_SCAN -16646142 19:43:38.005869: EV_KEY BTN_1 (0x101) released 19:43:38.005871: EV_MSC MSC_SCAN -16646141 19:43:38.005872: EV_KEY BTN_2 (0x102) pressed 19:43:38.005874: EV_SYN code=0 value=0 Fourth press (purple->off) emulates ??? 19:43:39.765915: EV_MSC MSC_SCAN -16646141 19:43:39.765921: EV_KEY BTN_2 (0x102) released 19:43:39.765925: EV_MSC MSC_SCAN -1664614019 19:43:39.765926: EV_KEY BTN_3 (0x103) pressed 19:43:39.765928: EV_SYN code=0 value=0 So, the backlight changing on a keyboard act as different types of mouse clicks based on what color you switch to. Apparently this problem is also present in PCLinuxOS. Is this possibly a Udev issue? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,mousepoll,snap,move,vpswitch,regex,place,animation,session,imgpng,grid,gnomecompat,wall,resize,expo,unitymtgrabhandles,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Aug 4 09:47:36 2014 DistUpgraded: 2014-08-02 23:43:24,960 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1556] InstallationDate: Installed on 2009-11-04 (1733 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=59092ad5-f628-4cfa-859e-9236256eac88 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-08-03 (1 days ago) dmi.bios.date: 01/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd01/16/2013:svnTobefilledbyO.E.M
[Desktop-packages] [Bug 636311] Re: Keyboard special keys interfere with mouse
This has apparently been ongoing for a long time. I have a Saitek Eclipse ii keyboard and I and others report that when you click the keyboard button to change the back light color, it triggers mouse events. These end up disabling the mouse. Unplugging and replugging the USB cable for the keyboard resets function to normal with the default blue back light color. If you try to change the color, the problem returns. I am now running 64 bit 14.04 and the problem has been with me since at least 12.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/636311 Title: Keyboard special keys interfere with mouse Status in Release Notes for Ubuntu: Invalid Status in “xorg” package in Ubuntu: Invalid Status in “xserver-xorg-input-evdev” package in Ubuntu: Invalid Status in “xorg” source package in Maverick: Fix Released Status in “xserver-xorg-input-evdev” source package in Maverick: Invalid Status in “xorg” source package in Natty: Invalid Status in “xserver-xorg-input-evdev” source package in Natty: Invalid Bug description: Binary package hint: xorg Following an online update from Kubuntu Lucid to Maverick beta, use of almost any of the 'special' buttons on the keyboard (mail, home, documents, play/pause, volume up, zoom in...) fires a ButtonPress event (as seen by xev) for the physically left mouse button (i.e. left click with the mouse set right-handed, 'right click' if set left- handed). There is no corresponding ButtonRelease, so the computer acts as if that mouse button is held down. The ButtonPress occurs between the KeyPress and KeyRelease events of the special key. This makes the mouse essentially unusable. So far, I've not found a way to reset it besides logging off (i.e. restarting X). Hardware: - Basic Microsoft keyboard and mouse (optical wheel mouse, Digital Media Keyboard 3000) - Intel graphics (lspci says it's an 82G33/31 integrated graphics controller) Initially I thought the problem was related to kwin compositing (which also causes some problems, see bug 630632 ), but I've found it happening even with desktop effects turned off. I don't know if xorg is the best package to file this against, so if not, please point me in the right direction. == Regression details == Discovered in version: maverick Last known good version: lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/636311/+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 1319186] [NEW] browsing samba shares becomes unresponsive over time
Public bug reported: Ubuntu 14.04 64 bit nautilus version: 1:3.10.1-0ubuntu9 I have saved as bookmarks several samba shares from a Windows machine on my office network to my Ubuntu 14.04 workstations (Windows is host, Ubuntu is client). I switch to a new workspace and open the saved share. It displays normally. I switch to another workspace and open a different saved samba share. It also works normally. I then switch to a 3rd workspace where I am using various programs. If you wait 15 minutes and change back to the workspaces where the opened shares exist, they have become unresponsive. Clicking on any files or folders will will cause a delay followed by the open window becoming unresponsive with the only choice being to close the window and then reopen the share from a right click of the files menu in the launcher. The share will again open and work normally until you again change workspaces and wait about 15 minutes, after which it again becomes unresponsive. This behaviour never happend with Ubuntu 10.04 or 12.04, which I was using before. Every machine in my office which all have a fresh install of 64 bit Ubuntu 14.04 behave the same way. As an experiment, I installed Nemo on 1 of my machines and instead of becoming unresponsive, the browser window turns grey for 15 seconds, but then starts to work normally. The expected behaviour would be to have the open browser windows continue to work without delay after switching workspaces and coming back to them after a period of 15 minutes. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 13 16:45:17 2014 GsettingsChanges: InstallationDate: Installed on 2014-05-02 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1319186 Title: browsing samba shares becomes unresponsive over time Status in “nautilus” package in Ubuntu: New Bug description: Ubuntu 14.04 64 bit nautilus version: 1:3.10.1-0ubuntu9 I have saved as bookmarks several samba shares from a Windows machine on my office network to my Ubuntu 14.04 workstations (Windows is host, Ubuntu is client). I switch to a new workspace and open the saved share. It displays normally. I switch to another workspace and open a different saved samba share. It also works normally. I then switch to a 3rd workspace where I am using various programs. If you wait 15 minutes and change back to the workspaces where the opened shares exist, they have become unresponsive. Clicking on any files or folders will will cause a delay followed by the open window becoming unresponsive with the only choice being to close the window and then reopen the share from a right click of the files menu in the launcher. The share will again open and work normally until you again change workspaces and wait about 15 minutes, after which it again becomes unresponsive. This behaviour never happend with Ubuntu 10.04 or 12.04, which I was using before. Every machine in my office which all have a fresh install of 64 bit Ubuntu 14.04 behave the same way. As an experiment, I installed Nemo on 1 of my machines and instead of becoming unresponsive, the browser window turns grey for 15 seconds, but then starts to work normally. The expected behaviour would be to have the open browser windows continue to work without delay after switching workspaces and coming back to them after a period of 15 minutes. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 13 16:45:17 2014 GsettingsChanges: InstallationDate: Installed on 2014-05-02 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1319186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packag
[Desktop-packages] [Bug 509317] Re: Xorg crashed with SIGSEGV in mieqProcessDeviceEvent()
Happened on 12.10 on Oct 3 on booting a live disk. Nvidia 550 Ti 64 bit. Nuveau drivers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/509317 Title: Xorg crashed with SIGSEGV in mieqProcessDeviceEvent() Status in “xorg-server” package in Ubuntu: Fix Released Bug description: Intel 945GM, Dell Latitude D620 ProblemType: Crash Architecture: i386 AssertionMessage: x\v Date: Mon Jan 18 13:24:57 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/Xorg MachineType: Dell Inc. Latitude D620 Package: xserver-xorg-core 2:1.7.3.902-1ubuntu8 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: root=/dev/mapper/system-root ro quiet splash ProcCmdline: /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-vLYdnp/database -nolisten tcp vt7 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) LANGUAGE=en_US:en ProcVersionSignature: Ubuntu 2.6.32-10.14-generic RelatedPackageVersions: xserver-xorg 1:7.5+1ubuntu1 libgl1-mesa-glx 7.7-0ubuntu6 libdrm2 2.4.17-0ubuntu1 xserver-xorg-video-intel 2:2.9.1-1ubuntu1 xserver-xorg-video-ati N/A SegvAnalysis: Segfault happened at: 0x323e51: call 0xf49c7bb PC (0x00323e51) ok source "0xf49c7bb" (0x0f49c7bb) not located in a known VMA region (needed readable region)! SegvReason: reading unknown VMA Signal: 11 SourcePackage: xorg-server StacktraceTop: ?? () mieqProcessDeviceEvent () mieqProcessInputEvents () ProcessInputEvents () ?? () Tags: lucid Title: Xorg crashed with SIGSEGV in mieqProcessDeviceEvent() Uname: Linux 2.6.32-10-generic i686 UserGroups: dmi.bios.date: 05/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0TD761 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/16/2008:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D620 dmi.sys.vendor: Dell Inc. fglrx: Not loaded glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu architecture: i686kernel: 2.6.32-10-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/509317/+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 856810] Re: Boot hangs at "Booting system without full network configuration..."
Had this problem after upgrading 32 bit 11.04 to 11.10 in Lenovo T400 notebook. Comment #40 solved it for me. -- 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/856810 Title: Boot hangs at "Booting system without full network configuration..." Status in Linaro Ubuntu Evaluation Builds: Confirmed Status in “lightdm” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Confirmed Bug description: I installed Ubuntu 11.10 beta1 64bit on a new laptop. I rebooted and it came up nicely. After that I did "apt-get update" and "apt-get dist-upgrade" to get the most recent fixes and installed some additional software. Now I do not seem to be able to boot. Fist I see: Waiting for network configuration... Then I see: Waiting up to 60 more seconds for network configuration... And then it just hangs forever displaying the following: Booting system without full network configuration... Nothing happens after that, no matter how long I wait. However, I can switch to the console with CTRL-ALT-F1 and log in from there. The network is configured with DHCP and it works just fine from the console. I do not understand what the GUI boot display is waiting for. I installed the system using the alternate install CD to get LVM based partitions with full disk encryption. I noticed the bug #847782 and removed the "auto eth0" entry from my /etc/network/interfaces. Unfortunately that did not change anything, it still hangs forever. To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-ubuntu/+bug/856810/+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
