[Bug 1530667] [NEW] Loading pylint.elc causes emacs24 to hang for a VERY LONG TIME at startup
Public bug reported: On stock Wily. Workaround is to "emacs --no-site-file" Note the "ERROR" line below: $ sudo apt-get install emacs24 pylint Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: emacs24-bin-common emacs24-common emacs24-common-non-dfsg liblockfile-bin liblockfile1 libm17n-0 libotf0 m17n-db python-astroid python-egenix-mxdatetime python-egenix-mxtools python-logilab-common Suggested packages: emacs24-el m17n-docs python-egenix-mxdatetime-dbg python-egenix-mxdatetime-doc python-egenix-mxtools-dbg python-egenix-mxtools-doc pyro python-unittest2 The following NEW packages will be installed: emacs24 emacs24-bin-common emacs24-common emacs24-common-non-dfsg liblockfile-bin liblockfile1 libm17n-0 libotf0 m17n-db pylint python-astroid python-egenix-mxdatetime python-egenix-mxtools python-logilab-common 0 upgraded, 14 newly installed, 0 to remove and 0 not upgraded. Need to get 594 kB/22.9 MB of archives. After this operation, 106 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://us.archive.ubuntu.com/ubuntu/ wily/main python-logilab-common all 1.0.2-1 [384 kB] Get:2 http://us.archive.ubuntu.com/ubuntu/ wily/main python-astroid all 1.3.8-1 [67.8 kB] Get:3 http://us.archive.ubuntu.com/ubuntu/ wily/main python-egenix-mxtools amd64 3.2.8-1 [75.2 kB] Get:4 http://us.archive.ubuntu.com/ubuntu/ wily/main python-egenix-mxdatetime amd64 3.2.8-1 [67.3 kB] Fetched 594 kB in 1s (380 kB/s) Selecting previously unselected package liblockfile-bin. (Reading database ... 174286 files and directories currently installed.) Preparing to unpack .../liblockfile-bin_1.09-6ubuntu1_amd64.deb ... Unpacking liblockfile-bin (1.09-6ubuntu1) ... Selecting previously unselected package liblockfile1:amd64. Preparing to unpack .../liblockfile1_1.09-6ubuntu1_amd64.deb ... Unpacking liblockfile1:amd64 (1.09-6ubuntu1) ... Selecting previously unselected package libotf0:amd64. Preparing to unpack .../libotf0_0.9.13-1ubuntu1_amd64.deb ... Unpacking libotf0:amd64 (0.9.13-1ubuntu1) ... Selecting previously unselected package emacs24-common-non-dfsg. Preparing to unpack .../emacs24-common-non-dfsg_24.4+1-2_all.deb ... Unpacking emacs24-common-non-dfsg (24.4+1-2) ... Selecting previously unselected package emacs24-common. Preparing to unpack .../emacs24-common_24.5+1-1ubuntu2_all.deb ... Unpacking emacs24-common (24.5+1-1ubuntu2) ... Selecting previously unselected package emacs24-bin-common. Preparing to unpack .../emacs24-bin-common_24.5+1-1ubuntu2_amd64.deb ... Unpacking emacs24-bin-common (24.5+1-1ubuntu2) ... Selecting previously unselected package m17n-db. Preparing to unpack .../m17n-db_1.6.5-1_all.deb ... Unpacking m17n-db (1.6.5-1) ... Selecting previously unselected package libm17n-0. Preparing to unpack .../libm17n-0_1.6.4-3_amd64.deb ... Unpacking libm17n-0 (1.6.4-3) ... Selecting previously unselected package emacs24. Preparing to unpack .../emacs24_24.5+1-1ubuntu2_amd64.deb ... Unpacking emacs24 (24.5+1-1ubuntu2) ... Selecting previously unselected package python-logilab-common. Preparing to unpack .../python-logilab-common_1.0.2-1_all.deb ... Unpacking python-logilab-common (1.0.2-1) ... Selecting previously unselected package python-astroid. Preparing to unpack .../python-astroid_1.3.8-1_all.deb ... Unpacking python-astroid (1.3.8-1) ... Selecting previously unselected package pylint. Preparing to unpack .../pylint_1.3.1-3ubuntu1_all.deb ... Unpacking pylint (1.3.1-3ubuntu1) ... Selecting previously unselected package python-egenix-mxtools. Preparing to unpack .../python-egenix-mxtools_3.2.8-1_amd64.deb ... Unpacking python-egenix-mxtools (3.2.8-1) ... Selecting previously unselected package python-egenix-mxdatetime. Preparing to unpack .../python-egenix-mxdatetime_3.2.8-1_amd64.deb ... Unpacking python-egenix-mxdatetime (3.2.8-1) ... Processing triggers for man-db (2.7.4-1) ... Processing triggers for install-info (6.0.0.dfsg.1-3) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for gnome-menus (3.13.3-6ubuntu1) ... Processing triggers for desktop-file-utils (0.22-1ubuntu3) ... Processing triggers for mime-support (3.58ubuntu1) ... Setting up liblockfile-bin (1.09-6ubuntu1) ... Setting up liblockfile1:amd64 (1.09-6ubuntu1) ... Setting up libotf0:amd64 (0.9.13-1ubuntu1) ... Setting up emacs24-common-non-dfsg (24.4+1-2) ... Setting up emacs24-common (24.5+1-1ubuntu2) ... Setting up emacs24-bin-common (24.5+1-1ubuntu2) ... update-alternatives: using /usr/bin/ctags.emacs24 to provide /usr/bin/ctags (ctags) in auto mode update-alternatives: using /usr/bin/ebrowse.emacs24 to provide /usr/bin/ebrowse (ebrowse) in auto mode update-alternatives: using /usr/bin/emacsclient.emacs24 to provide /usr/bin/emacsclient (emacsclient) in auto mode update-alternatives: using /usr/bin/etags.emacs24 to provide /usr/bin/etags (etag
[Bug 1336932] Re: e1000e ethernet kernel module crash
** Package changed: gnome-shell (Ubuntu) => linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336932 Title: e1000e ethernet kernel module crash To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1336932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336932] [NEW] e1000e ethernet kernel module crash
Public bug reported: The driver is completely vanilla. Here's dmesg output from my 3.13.0 kernel: [ 595.670950] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 595.671006] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 610.864555] [ cut here ] [ 610.864583] WARNING: CPU: 6 PID: 0 at /build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() [ 610.864586] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out [ 610.864588] Modules linked in: hid_generic hidp hid ctr ccm rfcomm bnep binfmt_misc snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev serio_raw arc4 rtl8192ce snd_hda_codec_realtek rtl_pci rtlwifi btusb nvidia(POF) rtl8192c_common uvcvideo bluetooth videobuf2_vmalloc mac80211 videobuf2_memops videobuf2_core videodev snd_hda_intel cfg80211 snd_hda_codec snd_hwdep drm snd_pcm lpc_ich mei_me snd_page_alloc mei wmi thinkpad_acpi nvram snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd parport_pc soundcore mac_hid ppdev video lp parport psmouse ahci firewire_ohci e1000e sdhci_pci libahci firewire_core ptp sdhci crc_itu_t pps_core [ 610.864697] CPU: 6 PID: 0 Comm: swapper/6 Tainted: PF O 3.13.0-30-generic #54-Ubuntu [ 610.864703] Hardware name: LENOVO 2436CTO/2436CTO, BIOS G5ET33WW (1.11 ) 08/09/2012 [ 610.864706] 0009 88061dd83d98 8171a324 88061dd83de0 [ 610.864733] 88061dd83dd0 810676bd 8805f74f4000 [ 610.864739] 8805f7873e80 0001 0006 88061dd83e30 [ 610.864749] Call Trace: [ 610.864752][] dump_stack+0x45/0x56 [ 610.864778] [] warn_slowpath_common+0x7d/0xa0 [ 610.864789] [] warn_slowpath_fmt+0x4c/0x50 [ 610.864801] [] dev_watchdog+0x276/0x280 [ 610.864814] [] ? dev_graft_qdisc+0x80/0x80 [ 610.864825] [] call_timer_fn+0x36/0x100 [ 610.864833] [] ? dev_graft_qdisc+0x80/0x80 [ 610.864842] [] run_timer_softirq+0x1ef/0x2f0 [ 610.864857] [] __do_softirq+0xec/0x2c0 [ 610.864868] [] irq_exit+0x105/0x110 [ 610.864876] [] smp_apic_timer_interrupt+0x45/0x60 [ 610.864888] [] apic_timer_interrupt+0x6d/0x80 [ 610.864899][] ? cpuidle_enter_state+0x52/0xc0 [ 610.864915] [] cpuidle_idle_call+0xb9/0x1f0 [ 610.864924] [] arch_cpu_idle+0xe/0x30 [ 610.864931] [] cpu_startup_entry+0xc5/0x290 [ 610.864938] [] start_secondary+0x218/0x2c0 [ 610.864950] ---[ end trace 497fb0f2c9cd35df ]--- [ 610.864996] e1000e :00:19.0 eth0: Reset adapter unexpectedly [ 614.810625] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 654.872638] e1000e :00:19.0 eth0: Reset adapter unexpectedly [ 659.327479] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready This came out of nowhere today. Googling reveals a rash of similar bugs that were corrected in >2.6 kernels. ** Affects: linux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336932 Title: e1000e ethernet kernel module crash To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1336932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310777] Re: Setting "complex" display configurations in gnome-shell results in dead desktop space.
Here is a fully reliable work-around: cp ~/.config/___monitors.xml ~/.config/monitors.xml; dbus-send --session --print-reply --type=method_call --dest=org.gnome.Shell /org/gnome/Shell org.gnome.Shell.Eval string:'global.stage.no_clear_hint=false;'; dbus-send --session --print-reply --dest=org.gnome.SettingsDaemon /org/gnome/SettingsDaemon/XRANDR org.gnome.SettingsDaemon.XRANDR_2.ApplyConfiguration int64:0 int64:0; BG=`gsettings get org.gnome.desktop.background picture-uri`; gsettings set org.gnome.desktop.background picture-uri $BG; -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310777 Title: Setting "complex" display configurations in gnome-shell results in dead desktop space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1310777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310777] Re: Setting "complex" display configurations in gnome-shell results in dead desktop space.
** Description changed: With a multi-monitor setup, changing to a "complex" display setup -- for example, rotating one of the displays -- results in desktop space that does not redraw: 1) The desktop background is not displayed in this space. 2) Windows that are dragged through the space leave artifacts. Resetting gnome-shell does not fix the problem. Instead, it returns the displays to the default arrangement (probably another bug). - - Work-around: Change the desktop wallpaper. For some reason, this seems - to resize the drawable portion of the desktop to fit the new display - arrangement. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-shell 3.10.4-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 21 16:11:41 2014 DisplayManager: gdm GsettingsChanges: - b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" - b'org.gnome.desktop.interface' b'clock-show-date' b'true' + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2014-04-08 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140408) ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310777 Title: Setting "complex" display configurations in gnome-shell results in dead desktop space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1310777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310777] Re: Setting "complex" display configurations in gnome-shell results in dead desktop space.
Workaround FAIL. I just rebooted and the previous approach didn't work. It had been reliable across 5-10 reboots. Womp womp. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310777 Title: Setting "complex" display configurations in gnome-shell results in dead desktop space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1310777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310777] Re: Setting "complex" display configurations in gnome-shell results in dead desktop space.
Sorry, typo in my previous comment: * Make sure that all of the displays you want to use are active using xrandr. * Delete xorg.conf if it exists. * Edit ~/.config/monitors.xml **by hand** to achieve the display geometry you want. After this, don't bother with nvidia-settings, arandr, or the "Displays" dialog. * Run dbus-send --session --print-reply --dest=org.gnome.SettingsDaemon /org/gnome/SettingsDaemon/XRANDR org.gnome.SettingsDaemon.XRANDR_2.ApplyConfiguration int64:0 int64:0 to load the new monitor settings. * Run the "Background" dialog and change the background image to a solid color. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310777 Title: Setting "complex" display configurations in gnome-shell results in dead desktop space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1310777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310777] Re: Setting "complex" display configurations in gnome-shell results in dead desktop space.
My previous work-around was not 100% reliable. Here is a reliable work- around: * Make sure that all of the displays you want to use are active using xrandr. * Delete xorg.conf if it exists. * Edit ~/.config/monitors.xml **by hand** to achieve the display geometry you want. After this, don't bother with nvidia-settings, arandr, or the "Displays" dialog. * Run dbus-send --session --print-reply --dest=org.gnome.SettingsDaemon /org/gnome/SettingsDaemon/XRANDR org.gnome.SettingsDaemon.XRANDR_2.ApplyConfiguration int64:0 int64:0 to load the new monitor settings. * Run the "Background" dialog and change the background image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310777 Title: Setting "complex" display configurations in gnome-shell results in dead desktop space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1310777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310777] Re: Setting "complex" display configurations in gnome-shell results in dead desktop space.
No movement here so I sent this upstream: https://bugzilla.gnome.org/show_bug.cgi?id=729925 ** Summary changed: - Changing display configuration in gnome-shell results in "dead" desktop space. + Setting "complex" display configurations in gnome-shell results in dead desktop space. ** Bug watch added: GNOME Bug Tracker #729925 https://bugzilla.gnome.org/show_bug.cgi?id=729925 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310777 Title: Setting "complex" display configurations in gnome-shell results in dead desktop space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1310777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317688] [NEW] xdot crashes on floats in the .dot file
Public bug reported: Traceback (most recent call last): File "/usr/bin/xdot", line 4, in xdot.main() File "/usr/lib/python2.7/dist-packages/xdot.py", line 1947, in main win.open_file(args[0]) File "/usr/lib/python2.7/dist-packages/xdot.py", line 1881, in open_file self.set_dotcode(fp.read(), filename) File "/usr/lib/python2.7/dist-packages/xdot.py", line 1863, in set_dotcode if self.widget.set_dotcode(dotcode, filename): File "/usr/lib/python2.7/dist-packages/xdot.py", line 1477, in set_dotcode self.set_xdotcode(xdotcode) File "/usr/lib/python2.7/dist-packages/xdot.py", line 1497, in set_xdotcode self.graph = parser.parse() File "/usr/lib/python2.7/dist-packages/xdot.py", line 1167, in parse DotParser.parse(self) File "/usr/lib/python2.7/dist-packages/xdot.py", line 977, in parse self.parse_graph() File "/usr/lib/python2.7/dist-packages/xdot.py", line 986, in parse_graph self.parse_stmt() File "/usr/lib/python2.7/dist-packages/xdot.py", line 1032, in parse_stmt self.handle_node(id, attrs) File "/usr/lib/python2.7/dist-packages/xdot.py", line 1142, in handle_node shapes.extend(parser.parse()) File "/usr/lib/python2.7/dist-packages/xdot.py", line 625, in parse points = self.read_polygon() File "/usr/lib/python2.7/dist-packages/xdot.py", line 517, in read_polygon x, y = self.read_point() File "/usr/lib/python2.7/dist-packages/xdot.py", line 500, in read_point x = self.read_number() File "/usr/lib/python2.7/dist-packages/xdot.py", line 494, in read_number return int(self.read_code()) ValueError: invalid literal for int() with base 10: '360.25' This has been corrected in more recent versions of the software. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xdot 0.5-2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 8 18:47:25 2014 InstallationDate: Installed on 2014-04-08 (29 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140408) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xdot UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xdot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317688 Title: xdot crashes on floats in the .dot file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdot/+bug/1317688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310777] Re: Changing display configuration in gnome-shell results in "dead" desktop space.
This bug occurs when using the gnome-shell "Displays" configuration utility, arandr, and xrandr. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310777 Title: Changing display configuration in gnome-shell results in "dead" desktop space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1310777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310777] [NEW] Changing display configuration in gnome-shell results in "dead" desktop space.
Public bug reported: With a multi-monitor setup, changing to a "complex" display setup -- for example, rotating one of the displays -- results in desktop space that does not redraw: 1) The desktop background is not displayed in this space. 2) Windows that are dragged through the space leave artifacts. Resetting gnome-shell does not fix the problem. Instead, it returns the displays to the default arrangement (probably another bug). Work-around: Change the desktop wallpaper. For some reason, this seems to resize the drawable portion of the desktop to fit the new display arrangement. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-shell 3.10.4-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 21 16:11:41 2014 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2014-04-08 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140408) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310777 Title: Changing display configuration in gnome-shell results in "dead" desktop space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1310777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696215] Re: Request support for 16-bit TIFF (=compile with --with-quantum-depth=16)
Bump? There has been no movement on this issue upstream in quite some time. Can we get it moving again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696215 Title: Request support for 16-bit TIFF (=compile with --with-quantum- depth=16) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphicsmagick/+bug/696215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251000] Re: With multiple monitors arranged vertically to form a single screen, gnome-shell creates "drag barriers" and erratic resizing behavior in the top monitor.
A work-around for this issue is to set the top monitor to be the primary monitor. This causes the gnome-shell panel to move to the top monitor, thus removing the drag barriers. Resizing appears to work appropriately as well. xrandr --output --auto --output --primary --above -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251000 Title: With multiple monitors arranged vertically to form a single screen, gnome-shell creates "drag barriers" and erratic resizing behavior in the top monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1251000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251000] Re: With monitor B of a higher resolution than monitor A, "xrandr --output A --auto --output B --above A" results in 'dead space' on monitor B
It has. https://bugzilla.gnome.org/show_bug.cgi?id=663690 ** Bug watch added: GNOME Bug Tracker #663690 https://bugzilla.gnome.org/show_bug.cgi?id=663690 ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Summary changed: - With monitor B of a higher resolution than monitor A, "xrandr --output A --auto --output B --above A" results in 'dead space' on monitor B + With multiple monitors arranged vertically to form a single screen, gnome-shell creates "drag barriers" and erratic resizing behavior in the top monitor. ** Description changed: Steps: xrandr --output LVDS-0 --auto --output DP-3 --above LVDS-0 Result: xrandr -q Screen 0: minimum 8 x 8, current 2560 x 2520, maximum 16384 x 16384 VGA-0 disconnected (normal left inverted right x axis y axis) LVDS-0 connected 1920x1080+0+1440 (normal left inverted right x axis y axis) 344mm x 193mm -1920x1080 60.0*+ 50.0 + 1920x1080 60.0*+ 50.0 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm -2560x1440 60.0*+ -1920x1440 60.0 -1920x1200 60.0 -1920x1080 119.9 60.0 60.0 59.9 50.0 60.0 30.0 30.0 -1680x1050 60.0 -1600x1200 60.0 -1600x900 60.0 -1280x1024 60.0 -1280x800 59.8 -1280x720 119.9 60.0 59.9 -1024x768 60.0 -800x60060.3 -720x480 119.9 59.9 30.0 -640x48059.9 + 2560x1440 60.0*+ + 1920x1440 60.0 + 1920x1200 60.0 + 1920x1080 119.9 60.0 60.0 59.9 50.0 60.0 30.0 30.0 + 1680x1050 60.0 + 1600x1200 60.0 + 1600x900 60.0 + 1280x1024 60.0 + 1280x800 59.8 + 1280x720 119.9 60.0 59.9 + 1024x768 60.0 + 800x60060.3 + 720x480 119.9 59.9 30.0 + 640x48059.9 DP-4 disconnected (normal left inverted right x axis y axis) DP-5 disconnected (normal left inverted right x axis y axis) Problem: - In this configuration, DP-3 is indeed "above" LDVS-0 in screen space. The wallpaper is rendered appropriately and the mouse can touch all the visible parts of the screen. However, it is impossible to drag windows into the left half of DP-3. I will refer to the space where the windows can't go as "dead space." It's as if an invisible barrier prevents windows from entering the dead space when dragged. Note that this may be a window manager problem. I am on Ubuntu-GNOME 13.04. + In this configuration, DP-3 is indeed "above" LDVS-0 in screen space. The wallpaper is rendered appropriately and the mouse can touch all the visible parts of the screen. However, it is impossible to drag windows into the left half of DP-3. It's as if an invisible barrier prevents windows from entering the space. Note that this may be a window manager problem. I am on Ubuntu-GNOME 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-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 304.88 Wed Mar 27 14:26:46 PDT 2013 - GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.88 Wed Mar 27 14:26:46 PDT 2013 + GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 13 14:39:50 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: - nvidia-304, 304.88, 3.8.0-19-generic, x86_64: installed - nvidia-304, 304.88, 3.8.0-32-generic, x86_64: installed - nvidia-304, 304.88, 3.8.0-33-generic, x86_64: installed + nvidia-304, 304.88, 3.8.0-19-generic, x86_64: installed + nvidia-304, 304.88, 3.8.0-32-generic, x86_64: installed + nvidia-304, 304.88, 3.8.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:21f6] + NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Device [17aa:21f6] InstallationDate: Installed on 2013-05-10 (187 days ago) In
[Bug 1251000] Re: With monitor B of a higher resolution than monitor A, "xrandr --output A --auto --output B --above A" results in 'dead space' on monitor B
See a Redhat bug with a nice video demonstrating the problem: https://bugzilla.redhat.com/show_bug.cgi?id=981167 The claim here is that this bug is to do with the location of the Gnome Shell menu bar. ** Bug watch added: Red Hat Bugzilla #981167 https://bugzilla.redhat.com/show_bug.cgi?id=981167 ** Bug watch added: Red Hat Bugzilla #711479 https://bugzilla.redhat.com/show_bug.cgi?id=711479 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251000 Title: With monitor B of a higher resolution than monitor A, "xrandr --output A --auto --output B --above A" results in 'dead space' on monitor B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1251000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251000] Re: With monitor B of a higher resolution than monitor A, "xrandr --output A --auto --output B --above A" results in 'dead space' on monitor B
Maybe this bug has gone upstream? See https://bugzilla.redhat.com/show_bug.cgi?id=711479 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251000 Title: With monitor B of a higher resolution than monitor A, "xrandr --output A --auto --output B --above A" results in 'dead space' on monitor B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1251000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251000] Re: With monitor B of a higher resolution than monitor A, "xrandr --output A --auto --output B --above A" results in 'dead space' on monitor B
Observation: Windows can be resized into the dead space but not moved there. This would seem to suggest a window manager issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251000 Title: With monitor B of a higher resolution than monitor A, "xrandr --output A --auto --output B --above A" results in 'dead space' on monitor B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1251000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251000] Re: With monitor B of a higher resolution than monitor A, "xrandr --output A --auto --output B --above A" results in 'dead space' on monitor B
This bug can also be reproduced by creating the desired screen layout in nvidia-settings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251000 Title: With monitor B of a higher resolution than monitor A, "xrandr --output A --auto --output B --above A" results in 'dead space' on monitor B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1251000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251000] [NEW] With monitor B of a higher resolution than monitor A, "xrandr --output A --auto --output B --above A" results in 'dead space' on monitor B
Public bug reported: Steps: xrandr --output LVDS-0 --auto --output DP-3 --above LVDS-0 Result: xrandr -q Screen 0: minimum 8 x 8, current 2560 x 2520, maximum 16384 x 16384 VGA-0 disconnected (normal left inverted right x axis y axis) LVDS-0 connected 1920x1080+0+1440 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.0*+ 50.0 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 60.0*+ 1920x1440 60.0 1920x1200 60.0 1920x1080 119.9 60.0 60.0 59.9 50.0 60.0 30.0 30.0 1680x1050 60.0 1600x1200 60.0 1600x900 60.0 1280x1024 60.0 1280x800 59.8 1280x720 119.9 60.0 59.9 1024x768 60.0 800x60060.3 720x480 119.9 59.9 30.0 640x48059.9 DP-4 disconnected (normal left inverted right x axis y axis) DP-5 disconnected (normal left inverted right x axis y axis) Problem: In this configuration, DP-3 is indeed "above" LDVS-0 in screen space. The wallpaper is rendered appropriately and the mouse can touch all the visible parts of the screen. However, it is impossible to drag windows into the left half of DP-3. I will refer to the space where the windows can't go as "dead space." It's as if an invisible barrier prevents windows from entering the dead space when dragged. Note that this may be a window manager problem. I am on Ubuntu-GNOME 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-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 304.88 Wed Mar 27 14:26:46 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 13 14:39:50 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.88, 3.8.0-19-generic, x86_64: installed nvidia-304, 304.88, 3.8.0-32-generic, x86_64: installed nvidia-304, 304.88, 3.8.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f6] InstallationDate: Installed on 2013-05-10 (187 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 2436CTO MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=3d01dd4a-cca3-4e45-b38a-ae3477f3b472 ro quiet splash nox2apic usbcore.usbfs_memory_mb=1000 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET33WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET33WW(1.11):bd08/09/2012:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2436CTO dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.7-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.7-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Wed Nov 13 11:00:22 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu6.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-pp
[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
Some of my blocked processes are starting to generate stack traces from the kernel: Jul 1 08:11:43 carina kernel: [36142.699465] INFO: task chrome:2165 blocked for more than 120 seconds. Jul 1 08:11:43 carina kernel: [36142.699469] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 1 08:11:43 carina kernel: [36142.699472] chrome D 0004 0 2165 1 0x Jul 1 08:11:43 carina kernel: [36142.699477] 8804005f5e48 0086 8804005f5fd8 8804005f4000 Jul 1 08:11:43 carina kernel: [36142.699482] 00013d00 88040dfa4858 8804005f5fd8 00013d00 Jul 1 08:11:43 carina kernel: [36142.699486] 88041f982dc0 88040dfa44a0 000c0001 88040dfa44a0 Jul 1 08:11:43 carina kernel: [36142.699491] Call Trace: Jul 1 08:11:43 carina kernel: [36142.699501] [] rwsem_down_failed_common+0xcd/0x170 Jul 1 08:11:43 carina kernel: [36142.699505] [] rwsem_down_write_failed+0x13/0x20 Jul 1 08:11:43 carina kernel: [36142.699511] [] call_rwsem_down_write_failed+0x13/0x20 Jul 1 08:11:43 carina kernel: [36142.699515] [] ? down_write+0x32/0x40 Jul 1 08:11:43 carina kernel: [36142.699521] [] sys_shmdt+0x60/0x180 Jul 1 08:11:43 carina kernel: [36142.699526] [] system_call_fastpath+0x16/0x1b Jul 1 08:11:43 carina kernel: [36142.699530] INFO: task chrome:2182 blocked for more than 120 seconds. Jul 1 08:11:43 carina kernel: [36142.699532] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 1 08:11:43 carina kernel: [36142.699534] chrome D 0 2182 1 0x Jul 1 08:11:43 carina kernel: [36142.699538] 8804029f5a98 0086 8804029f5fd8 8804029f4000 Jul 1 08:11:43 carina kernel: [36142.699542] 00013d00 88041030df38 8804029f5fd8 00013d00 Jul 1 08:11:43 carina kernel: [36142.699547] 81a0b020 88041030db80 8800bf7542a8 8800bf413d00 Jul 1 08:11:43 carina kernel: [36142.699551] Call Trace: Jul 1 08:11:43 carina kernel: [36142.699567] [] ? nfs_wait_bit_uninterruptible+0x0/0x20 [nfs] Jul 1 08:11:43 carina kernel: [36142.699571] [] io_schedule+0x70/0xc0 Jul 1 08:11:43 carina kernel: [36142.699582] [] nfs_wait_bit_uninterruptible+0xe/0x20 [nfs] Jul 1 08:11:43 carina kernel: [36142.699586] [] __wait_on_bit+0x5f/0x90 Jul 1 08:11:43 carina kernel: [36142.699597] [] ? nfs_wait_bit_uninterruptible+0x0/0x20 [nfs] Jul 1 08:11:43 carina kernel: [36142.699601] [] out_of_line_wait_on_bit+0x7c/0x90 Jul 1 08:11:43 carina kernel: [36142.699606] [] ? wake_bit_function+0x0/0x50 Jul 1 08:11:43 carina kernel: [36142.699616] [] nfs_wait_on_request+0x36/0x40 [nfs] Jul 1 08:11:43 carina kernel: [36142.699628] [] nfs_try_to_update_request+0x83/0x160 [nfs] Jul 1 08:11:43 carina kernel: [36142.699640] [] nfs_writepage_setup+0x3d/0x1e0 [nfs] Jul 1 08:11:43 carina kernel: [36142.699652] [] nfs_updatepage+0x83/0x180 [nfs] Jul 1 08:11:43 carina kernel: [36142.699663] [] ? nfs_release_request+0x19/0x20 [nfs] Jul 1 08:11:43 carina kernel: [36142.699671] [] nfs_vm_page_mkwrite+0x106/0x160 [nfs] Jul 1 08:11:43 carina kernel: [36142.699676] [] do_wp_page+0x584/0x770 Jul 1 08:11:43 carina kernel: [36142.699679] [] ? touch_atime+0x5f/0x180 Jul 1 08:11:43 carina kernel: [36142.699683] [] handle_pte_fault+0x1db/0x210 Jul 1 08:11:43 carina kernel: [36142.699687] [] handle_mm_fault+0x16d/0x250 Jul 1 08:11:43 carina kernel: [36142.699691] [] do_page_fault+0x1a7/0x540 Jul 1 08:11:43 carina kernel: [36142.699696] [] ? vfs_read+0x120/0x180 Jul 1 08:11:43 carina kernel: [36142.699699] [] page_fault+0x25/0x30 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794112 Title: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client To manage notifications about this bug go to: https://bugs.launchpad.net/kerberos/+bug/794112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
Again today, the client wedged at the same time as the DHCP refresh. The client's IP did not change. Any thoughts on what could be going on here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794112 Title: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client To manage notifications about this bug go to: https://bugs.launchpad.net/kerberos/+bug/794112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
The client OS appears to be wedging at precisely the time of a DHCP refresh. I came in this morning at 10:00am and found my desktop wedged with the clock stuck at 6:01am. From the syslog: Jun 29 06:01:04 carina kernel: [70343.412331] Error: state manager encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2. Jun 29 06:01:09 carina kernel: [70348.408657] Error: state manager encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2. Jun 29 06:01:14 carina dhclient: DHCPREQUEST of 192.168.0.59 on eth0 to 192.168.0.2 port 67 Jun 29 06:01:14 carina dhclient: DHCPACK of 192.168.0.59 from 192.168.0.2 Jun 29 06:01:14 carina dhclient: bound to 192.168.0.59 -- renewal in 15298 seconds. Jun 29 06:01:14 carina kernel: [70353.404947] Error: state manager encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2. Jun 29 06:01:19 carina kernel: [70358.401192] Error: state manager encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2. Jun 29 06:01:24 carina kernel: [70363.397718] Error: state manager encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794112 Title: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client To manage notifications about this bug go to: https://bugs.launchpad.net/kerberos/+bug/794112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
Observation: rpciod, nfsiod, and nfsv4.0-svc do not respond to kill -9 under these conditions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794112 Title: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client To manage notifications about this bug go to: https://bugs.launchpad.net/kerberos/+bug/794112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
Another theory: nslcd is trying to refresh the client's kerberos ticket via LDAP. It is failing because, unlike the user principles, the nfs principles do not have LDAP entries. Should they? Or is there a way to tell the nfs clients to not use LDAP? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794112 Title: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client To manage notifications about this bug go to: https://bugs.launchpad.net/kerberos/+bug/794112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
@Steve: I have not. What would the procedure for that look like? Purge the existing nfs-utils deb, and then build and install nfs-utils from source? Is there anything I can do to further pinpoint the problem before I try that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794112 Title: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client To manage notifications about this bug go to: https://bugs.launchpad.net/kerberos/+bug/794112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
I'm super keen to try debugging this myself -- you can even assign me the bug -- if somebody will give me a little direction. Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794112 Title: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client To manage notifications about this bug go to: https://bugs.launchpad.net/kerberos/+bug/794112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
** Description changed:
Hi there!
I've configured a Natty client/server pair to authenticate over Kerberos
and LDAP and to mount user home directories via NFSv4 with sec=krb5. I
am using a slight variation on the configuration described here:
http://www.danbishop.org/2011/05/01/ubuntu-11-04-sbs-small-business-
server-setup-part-3-openldap/
Under this setup, user sessions that are left unattended for a long
period of time -- eg, when someone goes home for the night but stays
logged in -- always result in a wedged machine. What do I mean by
"wedged?" When the user returns to their session (the next morning), the
screen is sorta grayed out. Keystrokes and mouse movement fail to elicit
a reaction from the OS. I can switch to an ANSI terminal (Ctrl+Alt+F1),
but cannot log in as the offending user there; the prompt will accept a
- username and password by never return. I CAN login using my localadmin,
+ username and password but never return. I CAN login using my localadmin,
presumably because it uses UNIX authentication rather than
LDAP/Kerberos. I have heretofore been unable to recover the machine as
the localadmin, though. If localadmin attempts to sudo reboot the
machine, the reboot process starts but never finishes.
Some odd things in the server syslog:
Jun 6 07:40:15 server krb5kdc[822]: AS_REQ (7 etypes {18 17 16 23 1 3 2})
192.168.0.59: NEEDED_PREAUTH: nfs/carina.co57@co57.lan for
krbtgt/co57@co57.lan, Additional pre-authentication required
Jun 6 07:40:15 server krb5kdc[822]: AS_REQ (7 etypes {18 17 16 23 1 3 2})
192.168.0.59: ISSUE: authtime 1307360415, etypes {rep=18 tkt=18 ses=18},
nfs/carina.co57@co57.lan for krbtgt/co57@co57.lan
Jun 6 07:40:15 server krb5kdc[822]: TGS_REQ (7 etypes {18 17 16 23 1 3 2})
192.168.0.59: ISSUE: authtime 1307360415, etypes {rep=18 tkt=18 ses=18},
nfs/carina.co57@co57.lan for nfs/server.co57@co57.lan
Jun 6 07:40:15 server krb5kdc[822]: TGS_REQ (3 etypes {1 3 2}) 192.168.0.59:
ISSUE: authtime 1307360415, etypes {rep=18 tkt=18 ses=1},
nfs/carina.co57@co57.lan for nfs/server.co57@co57.lan
Jun 6 07:40:15 server nslcd[950]: [92ef4c]
nslcd_passwd_byname(nfs/carina.co57.lan): invalid user name
Jun 6 07:46:49 server slapd[836]: <= bdb_equality_candidates: (uid) not
indexed
Jun 6 07:46:49 server slapd[836]: <= bdb_equality_candidates: (cn) not
indexed
Jun 6 07:48:51 server slapd[836]: <= bdb_equality_candidates: (uidNumber)
not indexed
Jun 6 07:49:20 server slapd[836]: <= bdb_equality_candidates: (uid) not
indexed
Jun 6 07:57:07 server slapd[836]: <= bdb_equality_candidates: (uid) not
indexed
Jun 6 07:57:07 server slapd[836]: <= bdb_equality_candidates: (cn) not
indexed
Jun 6 07:59:35 server slapd[836]: <= bdb_equality_candidates: (uid) not
indexed
Jun 6 08:00:00 server slapd[836]: <= bdb_equality_candidates: (cn) not
indexed
Jun 6 08:00:01 server slapd[836]: last message repeated 3 times
And from all over the client syslog:
Jun 6 10:53:28 carina kernel: [47636.670075] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:53:33 carina kernel: [47641.666533] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:53:38 carina kernel: [47646.662437] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:53:43 carina kernel: [47651.658844] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:53:48 carina kernel: [47656.655152] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:53:53 carina kernel: [47661.651498] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:53:58 carina kernel: [47666.647829] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:03 carina kernel: [47671.644084] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:08 carina kernel: [47676.640219] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:13 carina kernel: [47681.636699] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:18 carina kernel: [47686.632981] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:23 carina kernel: [47691.629134] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:28 carina kernel: [47696.625429] Error: state manager
encountered RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:33 carina kernel: [47701.621717] Error: state manager
encountered RPCSEC_G
[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
** Also affects: kerberos Importance: Undecided Status: New ** Also affects: nfs-utils Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794112 Title: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client To manage notifications about this bug go to: https://bugs.launchpad.net/kerberos/+bug/794112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
Folks on #kerberos are saying that this bug is due to a version mismatch between the kernel and nfs-utils. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794112 Title: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/794112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
Bump? This problem is making my life miserable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794112 Title: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/794112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794112] [NEW] Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
Public bug reported:
Hi there!
I've configured a Natty client/server pair to authenticate over Kerberos
and LDAP and to mount user home directories via NFSv4 with sec=krb5. I
am using a slight variation on the configuration described here:
http://www.danbishop.org/2011/05/01/ubuntu-11-04-sbs-small-business-
server-setup-part-3-openldap/
Under this setup, user sessions that are left unattended for a long
period of time -- eg, when someone goes home for the night but stays
logged in -- always result in a wedged machine. What do I mean by
"wedged?" When the user returns to their session (the next morning), the
screen is sorta grayed out. Keystrokes and mouse movement fail to elicit
a reaction from the OS. I can switch to an ANSI terminal (Ctrl+Alt+F1),
but cannot log in as the offending user there; the prompt will accept a
username and password by never return. I CAN login using my localadmin,
presumably because it uses UNIX authentication rather than
LDAP/Kerberos. I have heretofore been unable to recover the machine as
the localadmin, though. If localadmin attempts to sudo reboot the
machine, the reboot process starts but never finishes.
Some odd things in the server syslog:
Jun 6 07:40:15 server krb5kdc[822]: AS_REQ (7 etypes {18 17 16 23 1 3 2})
192.168.0.59: NEEDED_PREAUTH: nfs/carina.co57@co57.lan for
krbtgt/co57@co57.lan, Additional pre-authentication required
Jun 6 07:40:15 server krb5kdc[822]: AS_REQ (7 etypes {18 17 16 23 1 3 2})
192.168.0.59: ISSUE: authtime 1307360415, etypes {rep=18 tkt=18 ses=18},
nfs/carina.co57@co57.lan for krbtgt/co57@co57.lan
Jun 6 07:40:15 server krb5kdc[822]: TGS_REQ (7 etypes {18 17 16 23 1 3 2})
192.168.0.59: ISSUE: authtime 1307360415, etypes {rep=18 tkt=18 ses=18},
nfs/carina.co57@co57.lan for nfs/server.co57@co57.lan
Jun 6 07:40:15 server krb5kdc[822]: TGS_REQ (3 etypes {1 3 2}) 192.168.0.59:
ISSUE: authtime 1307360415, etypes {rep=18 tkt=18 ses=1},
nfs/carina.co57@co57.lan for nfs/server.co57@co57.lan
Jun 6 07:40:15 server nslcd[950]: [92ef4c]
nslcd_passwd_byname(nfs/carina.co57.lan): invalid user name
Jun 6 07:46:49 server slapd[836]: <= bdb_equality_candidates: (uid) not indexed
Jun 6 07:46:49 server slapd[836]: <= bdb_equality_candidates: (cn) not indexed
Jun 6 07:48:51 server slapd[836]: <= bdb_equality_candidates: (uidNumber) not
indexed
Jun 6 07:49:20 server slapd[836]: <= bdb_equality_candidates: (uid) not indexed
Jun 6 07:57:07 server slapd[836]: <= bdb_equality_candidates: (uid) not indexed
Jun 6 07:57:07 server slapd[836]: <= bdb_equality_candidates: (cn) not indexed
Jun 6 07:59:35 server slapd[836]: <= bdb_equality_candidates: (uid) not indexed
Jun 6 08:00:00 server slapd[836]: <= bdb_equality_candidates: (cn) not indexed
Jun 6 08:00:01 server slapd[836]: last message repeated 3 times
And from all over the client syslog:
Jun 6 10:53:28 carina kernel: [47636.670075] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:53:33 carina kernel: [47641.666533] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:53:38 carina kernel: [47646.662437] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:53:43 carina kernel: [47651.658844] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:53:48 carina kernel: [47656.655152] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:53:53 carina kernel: [47661.651498] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:53:58 carina kernel: [47666.647829] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:03 carina kernel: [47671.644084] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:08 carina kernel: [47676.640219] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:13 carina kernel: [47681.636699] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:18 carina kernel: [47686.632981] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:23 carina kernel: [47691.629134] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:28 carina kernel: [47696.625429] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:33 carina kernel: [47701.621717] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
Jun 6 10:54:38 carina kernel: [47706.617861] Error: state manager encountered
RPCSEC_GSS session expired against NFSv4 server 192.168.0.2.
[Bug 692392] Re: [Realtek ALC268] Recording problem on Acer Aspire One (ZG5)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692392 Title: [Realtek ALC268] Recording problem on Acer Aspire One (ZG5) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692392] [NEW] [Realtek ALC268] Recording problem on Acer Aspire One (ZG5)
Public bug reported: This is a report for Ubuntu 10.10 (Maverick Meerkat). After some investigation, my intuition is that it is the result of an interaction between PulseAudio and ALSA. State #1 Fresh install sudo apt-get update && sudo apt-get upgrade Symptoms: Recording from the built-in microphone works from the Sound Recorder but not from Google Talk, Skype, etc. State #2 sudo apt-get install pavucontrol set the left and right inputs to different levels, as suggested on various forum posts Symptoms: Recording from the built-in microphone works in Google Talk for a short time (< 2s), but then dies. State #3 sudo apt-get install linux-alsa-driver-modules-$(uname -r) sudo reboot Symptoms: No change State #4 sudo apt-get purge libcanberra-pulse pulseaudio pulseaudio-esound-compat pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-udev pulseaudio-module-x11 gstreamer0.10-pulseaudio pulseaudio-utils pavucontrol sudo reboot Symptoms: No change State #5 sudo echo "options snd-hda-intel model=acer-aspire" > /etc/modprobe.d/alsa-base.conf sudo reboot Symptoms: Recording is now working in Google Talk, Skype, etc, but the result is extremely noisy. There is a loud hum/buzz in the background. Changing the input volume/gains in alsamixer causes the recording to go silent. Hope that gives you some leads! ~br ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: alsa-base 1.0.23+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7 Uname: Linux 2.6.35-23-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: br 2300 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x5854 irq 45' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,1025015b,00100101' Controls : 9 Simple ctrls : 6 Date: Sun Dec 19 19:49:07 2010 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) PackageArchitecture: all ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SelectedCard: 0 Intel HDA-Intel - HDA Intel SourcePackage: alsa-driver Symptom: audio Title: [Realtek ALC268] Recording problem dmi.bios.date: 05/09/2008 dmi.bios.vendor: Acer dmi.bios.version: v0.3114 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrv0.3114:bd05/09/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: AOA150 dmi.product.version: 1 dmi.sys.vendor: Acer ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692392 Title: [Realtek ALC268] Recording problem on Acer Aspire One (ZG5) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
