[Bug 1869267] [NEW] /etc/login.defs contains a non-ASCII character

2020-03-26 Thread Paul Nickerson
Public bug reported: 1) OS: Ubuntu 16.04.6 LTS 2) Package: login 1:4.2-3.1ubuntu5.4 amd64 from xenial-updates/main 3) After installing this package, I expect /etc/login.defs to contain only ASCII characters. 4) Instead, /etc/login.defs contains an Acute Accent (Unicode U+00B4) on line 221 in a

[Bug 1729695] Re: ASCII decode error, but not due to filenames in backup target

2018-05-11 Thread Paul Nickerson
I just installed Windows 10's April 2018 Update, and it looks like it enabled Fast Startup again. I've got Ubuntu 18.04 now, with duplicity/bionic,now 0.7.17-0ubuntu1 amd64 [installed]. And the bug remains: Traceback (innermost last): File "/usr/bin/duplicity", line 1555, in

[Bug 1760264] Re: New version of intel-microcode freezes computer

2018-03-30 Thread Paul Nickerson
For me, both intel-microcode 3.20180312.0~ubuntu17.10.1 amd64 and linux- image-4.13.0-37-generic 4.13.0-37.42 amd64 got installed at the same time. On my next boot and every boot after that, my computer would hang hard after I typed in my password at the login screen and hit enter. My cursor would

[Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

2017-11-11 Thread Paul Nickerson
Thank you, staedtler-przyborski. The workaround you link to in comment #102 worked immediately for my Brother MFC-J220 scanner, on Ubuntu 17.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707352

[Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2017-11-11 Thread Paul Nickerson
Thank you, staedtler-przyborski. The workaround you describe in comment #36 worked immediately for my Brother MFC-J220 scanner, on Ubuntu 17.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728012

[Bug 1729695] Re: ASCII decode error, but not due to filenames in backup target

2017-11-08 Thread Paul Nickerson
I thought of something that could be a change on the system. I dual boot Ubuntu and Windows. The target disk for backups is formatted as NTFS, and Windows 10 mounts it when it boots. I just checked the Windows logs, and the second to last time I booted Windows was just before the backup started

[Bug 1729695] Re: ASCII decode error, but not due to filenames in backup target

2017-11-08 Thread Paul Nickerson
I don't know why, but the backup started working again yesterday. I did not do anything to try and fix it. The only thing I can think of that changed on my system is that these packages were updated (from /var/log/dpkg.log): 2017-11-07 08:10:32 upgrade google-chrome-stable:amd64 62.0.3202.75-1

[Bug 1729695] Re: ASCII decode error, but not due to filenames in backup target

2017-11-04 Thread Paul Nickerson
Ubuntu 17.04 was fresh installed in early July 2017, and I've since upgraded to 17.10 (I did not fresh install 17.10). I did not reconfigure Deja Dup before or after that upgrade. When I did the fresh install and then set up the backup, I already had a backup directory on the secondary drive that

[Bug 1729695] [NEW] ASCII decode error, but not due to filenames in backup target

2017-11-02 Thread Paul Nickerson
Public bug reported: On Ubuntu 17.10, I have deja-dup 36.2-0ubuntu1 installed. When I run "DEJA_DUP_DEBUG=1 deja-dup", it starts a backup as soon as it opens, as expected. But the backup fails. I get the following at the end of the output. I tried uninstalling Dropbox and deleting its

[Bug 1412022] [NEW] nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel module failed to build

2015-01-17 Thread Paul Nickerson
Public bug reported: On Ubuntu 14.10, when prompted to update nvidia-331-updates-uvm to 331.113-0ubuntu0.1, this happened. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates-uvm 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname:

[Bug 1401813] Re: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build

2014-12-14 Thread Paul Nickerson
I was somehow able to get past this by removing then reinstalling all NVIDIA packages. I ran this to remove the packages: sudo apt-get remove nvidia-* sudo apt-get autoremove Then I rebooted, and then ran software-properties-gtk This brought up the Software Updates window. In the

[Bug 973933] Re: Random Reboot if I Boot with ACPI On

2014-01-01 Thread Paul Nickerson
OP here. Sorry I went off radar for a while. I tried the 20131223 daily build of Ubuntu 14.04 Trusty Tahr Desktop AMD64, and it still had the problem when I booted the live CD. My up to date install of Ubuntu 13.10 (fresh install of that version) was also still having the same problem. Seeing

[Bug 973933] Re: Random Reboot if I Boot with ACPI On

2012-04-05 Thread Paul Nickerson
I installed the kernel linux-image-3.4.0-030400rc1-generic_3.4.0-030400rc1.201203312035_amd64 from there. I can't boot fully from it in either regular or recovery mode. But, if I take out the acpi=off parameter, I still experience the random reboot, even though it doesn't reboot fully. Leaving

[Bug 973933] [NEW] Random Reboot if I Boot with ACPI On

2012-04-04 Thread Paul Nickerson
Public bug reported: If I boot up Ubuntu 11.10 without sending the apci=off parameter to the kernel in GRUB, then after not too long (usually less then 10 minutes, always less than 20) my computer will randomly reboot. It's as if I forced the computer off by pressing the power button for a few

[Bug 973933] Re: Random Reboot if I Boot with ACPI On

2012-04-04 Thread Paul Nickerson
** Attachment added: Output of lots of requested commands https://bugs.launchpad.net/bugs/973933/+attachment/3006884/+files/kernel-bug-report-pgn674.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 558872] Re: empathy accounts fail to connect after manually unlocking keyring

2010-05-02 Thread Paul Nickerson
I had this problem, and I found a work around. For those who don't want to read a lot: I set my keyring manager's password to blank, and set empathy and gwibber as startup applications. To find out how, read on. First, what I saw wrong: I did an in-place upgrade today from 9.10. I have auto