[Bug 1530667] [NEW] Loading pylint.elc causes emacs24 to hang for a VERY LONG TIME at startup

2016-01-03 Thread Brian the Lion
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:

[Bug 1310777] Re: Setting complex display configurations in gnome-shell results in dead desktop space.

2014-07-02 Thread Brian the Lion
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

[Bug 1336932] [NEW] e1000e ethernet kernel module crash

2014-07-02 Thread Brian the Lion
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

[Bug 1336932] Re: e1000e ethernet kernel module crash

2014-07-02 Thread Brian the Lion
** 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:

[Bug 1310777] Re: Setting complex display configurations in gnome-shell results in dead desktop space.

2014-05-19 Thread Brian the Lion
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

[Bug 1310777] Re: Setting complex display configurations in gnome-shell results in dead desktop space.

2014-05-19 Thread Brian the Lion
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

[Bug 1310777] Re: Setting complex display configurations in gnome-shell results in dead desktop space.

2014-05-19 Thread Brian the Lion
** 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

[Bug 1310777] Re: Setting complex display configurations in gnome-shell results in dead desktop space.

2014-05-10 Thread Brian the Lion
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

[Bug 1310777] Re: Setting complex display configurations in gnome-shell results in dead desktop space.

2014-05-10 Thread Brian the Lion
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

[Bug 1317688] [NEW] xdot crashes on floats in the .dot file

2014-05-08 Thread Brian the Lion
Public bug reported: Traceback (most recent call last): File /usr/bin/xdot, line 4, in module 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

[Bug 1310777] Re: Changing display configuration in gnome-shell results in dead desktop space.

2014-04-21 Thread Brian the Lion
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

[Bug 1310777] [NEW] Changing display configuration in gnome-shell results in dead desktop space.

2014-04-21 Thread Brian the Lion
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

[Bug 696215] Re: Request support for 16-bit TIFF (=compile with --with-quantum-depth=16)

2013-11-15 Thread Brian the Lion
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

[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

2013-11-13 Thread Brian the Lion
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

[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

2013-11-13 Thread Brian the Lion
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

[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

2013-11-13 Thread Brian the Lion
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

[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

2013-11-13 Thread Brian the Lion
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

[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

2013-11-13 Thread Brian the Lion
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

[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

2013-11-13 Thread Brian the Lion
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

[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.

2013-11-13 Thread Brian the Lion
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 BOTTOM --auto --output TOP --primary --above BOTTOM --

[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client

2011-07-01 Thread Brian the Lion
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

[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client

2011-06-30 Thread Brian the Lion
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

[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client

2011-06-29 Thread Brian the Lion
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

[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client

2011-06-28 Thread Brian the Lion
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

[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client

2011-06-25 Thread Brian the Lion
@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

[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client

2011-06-25 Thread Brian the Lion
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

[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client

2011-06-24 Thread Brian the Lion
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:

[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client

2011-06-21 Thread Brian the Lion
** 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:

[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client

2011-06-20 Thread Brian the Lion
** 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

[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client

2011-06-17 Thread Brian the Lion
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

[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client

2011-06-14 Thread Brian the Lion
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

[Bug 794112] [NEW] Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client

2011-06-07 Thread Brian the Lion
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:

[Bug 692392] [NEW] [Realtek ALC268] Recording problem on Acer Aspire One (ZG5)

2010-12-19 Thread Brian the Lion
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

[Bug 692392] Re: [Realtek ALC268] Recording problem on Acer Aspire One (ZG5)

2010-12-19 Thread Brian the Lion
-- 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