[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise

2021-09-01 Thread Ben Fritz
> It doesn't corrupt boots. It's inconvenient. Yes, it does corrupt boot setups. I'm not sure how you can say it doesn't. I mean I guess TECHNICALLY it "only" overwrites working boot setups, with non-working boot setups; it's not actually corrupting existing files with garbage data. My

[Bug 1734808] [NEW] TortoiseHg 3.7.3 requires newer Mercurial package (3.8.n or higher)

2017-11-27 Thread Ben Fritz
Public bug reported: I am running on Xenial, and I am trying to use the TortoiseHg application installed via Synaptic. It seems impossible to install TortoiseHg in a working state from the package manager. TortoiseHg installs fine from the "universe" repository, but will not launch, giving error

[Bug 1485425] [NEW] Trying to downgrade my AMD graphics driver, got: package fglrx-updates-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/fglrx/libGL.so', which is also i

2015-08-16 Thread Ben Fritz
Public bug reported: A recent system update made my desktop graphics stop working; the proprietary driver is in use but Ubuntu is not actually using it for any sort of hardware acceleration. All the desktop effects are disabled, and there are ugly graphical artifacts on most of the buttons, which

[Bug 1475145] [NEW] package linux-image-3.13.0-57-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2015-07-16 Thread Ben Fritz
*** This bug is a duplicate of bug 1475144 *** https://bugs.launchpad.net/bugs/1475144 Public bug reported: Possibly related to my system configuration; I manually installed a 64-bit kernel in order to run 64-bit applications, although most of my installation is 32-bit. As detailed here:

[Bug 1475144] [NEW] package linux-image-3.13.0-57-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2015-07-16 Thread Ben Fritz
Public bug reported: Possibly related to my system configuration; I manually installed a 64-bit kernel in order to run 64-bit applications, although most of my installation is 32-bit. As detailed here: http://askubuntu.com/a/543663/258628 ProblemType: Package DistroRelease: Ubuntu 14.04 Package:

[Bug 1027223] Re: update-grub ignores GRUB_COLOR_NORMAL and GRUB_COLOR_HIGHLIGHT

2014-09-25 Thread Ben Fritz
I think I managed to find a satisfactory fix. Please can this get applied so I can stop doing this manually? First, in /etc/grub.d/05_debian_theme, there are several lines that call set_background_image with various values for the wallpaper. But only one of those lines sets any colors, i.e.: #

[Bug 1027223] Re: update-grub ignores GRUB_COLOR_NORMAL and GRUB_COLOR_HIGHLIGHT

2012-11-19 Thread Ben Fritz
** Changed in: grub2 (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027223 Title: update-grub ignores GRUB_COLOR_NORMAL and GRUB_COLOR_HIGHLIGHT To

[Bug 1027223] Re: update-grub ignores GRUB_COLOR_NORMAL and GRUB_COLOR_HIGHLIGHT

2012-11-18 Thread Ben Fritz
Please reopen this bug and assign it. Here's a problem description. Original post had a fix (which I am going to try after posting). Steps to reproduce 1. Install kde-grub2-config from Synaptic 2. Run the installed application 3. Go to the Appearance settings and specify a wallpaper, foreground

[Bug 1027223] Re: update-grub ignores GRUB_COLOR_NORMAL and GRUB_COLOR_HIGHLIGHT

2012-11-18 Thread Ben Fritz
I tested the fix in the original post. It did not work, until I also modified /etc/grub.d/05_debian_theme as follows: #if [ -n ${GRUB_BACKGROUND+x} ]; then # set_background_image ${GRUB_BACKGROUND} || set_default_theme # exit 0 #fi if [ -n ${GRUB_BACKGROUND+x} ]; then