[Bug 1869267] [NEW] /etc/login.defs contains a non-ASCII character
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 comment: === Quote From File === # If set to yes, userdel will remove the user´s group if it contains no === End Quote === This causes a problem in SaltStack: https://github.com/saltstack/salt/issues/55695 SaltStack does recognize that they should do a better job at loading this file and is planning on fixing its problem. But I still question this: Should we expect /etc/login.defs to contain ASCII characters only? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: login 1:4.2-3.1ubuntu5.4 ProcVersionSignature: Ubuntu 4.4.0-1101.112-aws 4.4.208 Uname: Linux 4.4.0-1101-aws x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Mar 26 17:46:26 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869267 Title: /etc/login.defs contains a non-ASCII character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1869267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729695] Re: ASCII decode error, but not due to filenames in backup target
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
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729695
Title:
ASCII decode error, but not due to filenames in backup target
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1729695/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760264] Re: New version of intel-microcode freezes computer
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 appear on a black screen, and then it hung. I did not try downgrading intel-microcode, but I did try selecting linux-image-4.13.0-36-generic 4.13.0-36.40 amd64 in GRUB on boot. That did work. So I believe we may have found two different workarounds to the same bug, maybe. I was able to SSH into the computer from a different machine while at the login screen and run journalctl -f before I tried to log in, and that got me more log entries than were written to disk. But, I still feel like I did not get to see the final actions before the hang; they never got logged or didn't make it over the SSH tunnel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760264 Title: New version of intel-microcode freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1760264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
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 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
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 Title: Many 3rd party scanner drivers are broken by a sane change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729695] Re: ASCII decode error, but not due to filenames in backup target
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 failing. Then, the last time I booted Windows was just before the backup started working again. Ohh, here is a thing. In Windows 10, under Control Panel > Hardware and Sound > Power Options > System Settings > Shutdown settings, Fast Startup is enabled. This option must be disabled for Ubuntu to be able to reliably use the NTFS hard drives. I did have Fast Startup disabled. I'm guessing that the Fall Creators Update re-enabled it. Windows likes to do things like that. Stupid Windows. Ok, I've turned off Fast Startup again. I think we can call this bug resolved, but I don't know what I should change the status to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729695 Title: ASCII decode error, but not due to filenames in backup target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1729695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729695] Re: ASCII decode error, but not due to filenames in backup target
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 62.0.3202.89-1 2017-11-07 08:10:36 upgrade libssl1.0.0:amd64 1.0.2g-1ubuntu13 1.0.2g-1ubuntu13.2 2017-11-07 08:10:36 upgrade openssl:amd64 1.0.2g-1ubuntu13 1.0.2g-1ubuntu13.2 The backup worked again today. If it works again tomorrow, then that's three times and I'll call the problem fixed, somehow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729695 Title: ASCII decode error, but not due to filenames in backup target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1729695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729695] Re: ASCII decode error, but not due to filenames in backup target
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 my previous Ubuntu install had been using. But, I never configured this install to use that same directory; I've used a new directory with a different name from the get- go. So that shouldn't matter. Looking in the backup directory, the oldest file is dated August 2, 2017. And under scheduling I have Deja Dup configured to keep at least six months, so I think that date is the real date I first configured the backup. I have not tried configuring Deja Dup to use a new storage location since this problem started occuring. Should I try that? Also, I should note that the backup window shows the message "Creating a fresh backup to protect against backup corruption. This will take longer than normal." Wouldn't this mean that Deja Dup is not trying to create an incremental backup on top of what was backed up in Ubuntu 17.04? ** Changed in: deja-dup (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729695 Title: ASCII decode error, but not due to filenames in backup target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1729695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729695] [NEW] ASCII decode error, but not due to filenames in backup target
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 .dropbox-dist
directory, and then deja-dup crashed when trying to back up a completely
different file (but the same byte in the same position). So I don't
think this is due to any of the filenames I have in my backup target. I
also tried a few commands to find non-ASCII filenames, with no luck. I'm
not sure what else I can do to troubleshoot.
DUPLICITY: INFO 4
'home/paul/.dropbox-dist/dropbox-lnx.x86_64-38.4.27/PyQt5.QtGui.so'
DUPLICITY: . A home/paul/.dropbox-dist/dropbox-lnx.x86_64-38.4.27/PyQt5.QtGui.so
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file
/home/paul/.cache/deja-dup/1499b6292f58faddd30853ffbbfefcf6/duplicity-S72EWc-tempdir/mktemp-hYd54u-1
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file
/home/paul/.cache/deja-dup/1499b6292f58faddd30853ffbbfefcf6/duplicity-VyBN42-tempdir/mktemp-BO1DKJ-1
DUPLICITY: INFO 11
DUPLICITY: . AsyncScheduler: running task synchronously (asynchronicity
disabled)
DUPLICITY: INFO 1
DUPLICITY: . Writing duplicity-full.20171102T205615Z.vol1.difftar.gz
DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile
/home/paul/.cache/deja-dup/1499b6292f58faddd30853ffbbfefcf6/lockfile.lock
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file
/tmp/duplicity-c9BMvB-tempdir/mktemp-RtijDc-270
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file
/tmp/duplicity-c9BMvB-tempdir/mkstemp-3cxG5G-1
DUPLICITY: ERROR 30 UnicodeDecodeError
DUPLICITY: . Traceback (most recent call last):
DUPLICITY: . File "/usr/bin/duplicity", line 1546, in
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File "/usr/bin/duplicity", line 1540, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: . File "/usr/bin/duplicity", line 1391, in main
DUPLICITY: . do_backup(action)
DUPLICITY: . File "/usr/bin/duplicity", line 1510, in do_backup
DUPLICITY: . full_backup(col_stats)
DUPLICITY: . File "/usr/bin/duplicity", line 575, in full_backup
DUPLICITY: . globals.backend)
DUPLICITY: . File "/usr/bin/duplicity", line 456, in write_multivol
DUPLICITY: . (tdp, dest_filename, vol_num)))
DUPLICITY: . File
"/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 146, in
schedule_task
DUPLICITY: . return self.__run_synchronously(fn, params)
DUPLICITY: . File
"/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 172, in
__run_synchronously
DUPLICITY: . ret = fn(*params)
DUPLICITY: . File "/usr/bin/duplicity", line 455, in
DUPLICITY: . vol_num: put(tdp, dest_filename, vol_num),
DUPLICITY: . File "/usr/bin/duplicity", line 344, in put
DUPLICITY: . backend.put(tdp, dest_filename)
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/backend.py",
line 376, in inner_retry
DUPLICITY: . % exception_traceback())
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line
52, in exception_traceback
DUPLICITY: . return uexc(msg)
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line
80, in uexc
DUPLICITY: . e = unicode(e).encode('utf-8')
DUPLICITY: . UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in
position 736: ordinal not in range(128)
DUPLICITY: .
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: deja-dup 36.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 2 17:46:56 2017
InstallationDate: Installed on 2017-07-02 (123 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: deja-dup
UpgradeStatus: Upgraded to artful on 2017-10-22 (11 days ago)
** Affects: deja-dup (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729695
Title:
ASCII decode error, but not due to filenames in backup target
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1729695/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412022] [NEW] nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel module failed to build
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: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 DKMSKernelVersion: 3.16.0-30-generic Date: Sat Jan 17 12:00:45 2015 InstallationDate: Installed on 2013-11-16 (427 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-12-02 (46 days ago) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412022 Title: nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1412022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401813] Re: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build
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 Additional drivers tab, I selected 331.113 from nvidia-331-updates, and rebooted. Unity would then not run (not sure if this would happen for others). I reenabled it by running sudo apt-get install compizconfig-settings-manager ccsm And in the CompizConfig Settings Manager, I enabled the Ubuntu Unity Plugin. I still have nvidia-331-updates version 331.113-0ubuntu0.1 installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401813 Title: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1401813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973933] Re: Random Reboot if I Boot with ACPI On
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 the Andrew had good luck updating his BIOS, I looked for updates for my own board. My BIOS version was 685 A105 x64, built around October of 2011. The EVGA website listed this BIOS as version A05. The website offered version R22, released 3-13-2013, for download. I installed that (had to do it from my Windows boot), and noted that my BIOS now says it's version 685 0.22 x64 and was built 03/01/2013 14:51:21. After this, both the daily build of Ubuntu and my up to date install of Ubuntu 13.10 both run fine without any acpi flag sent to the kernel. It looks like updating my BIOS solved the bug. Should this bug ticket's status be changed to Fix Released, since a good BIOS has been released for this board? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973933 Title: Random Reboot if I Boot with ACPI On To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/973933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973933] Re: Random Reboot if I Boot with ACPI On
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 in the acpi=off prevents it from self rebooting in either mode. So, I feel confidant that the upstream kernel has not fixed the bug, and therefor I've replaced needs-upstream-testing with kernel-bug-exists-upstream and marked the ticket as Confirmed. ** Tags removed: needs-upstream-testing ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973933 Title: Random Reboot if I Boot with ACPI On To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/973933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973933] [NEW] Random Reboot if I Boot with ACPI On
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 seconds, then waited 2 seconds, then turned the computer back on. I have not noticed any trigger for the reboot; it seems completely random. I have tried these kernel parameters, but I have experienced the reboot on them all: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic In troubleshooting before I figured out acpi=off worked, I tried swapping out lots of hardware. I narrowed it down to being either my motherboard or my CPU: Motherboard: EVGA Z68 SLI (model 130-SB-E685-KR) (Intel Z68 north bridge) CPU: Intel Core i7 2600 (Sandy Bridge) Attached are outputs of lspci -vvnn and dmidecode that I ran with ACPI on, before a random reboot stopped me. Also attached are outputs from uname -a, /proc/version_signature, and lsb_release -rd. /proc/acpi did not exist when I booted with ACPI. I have the linux-image-3.0.0-18-generic package, version 3.0.0-18.31, installed, but I have had this problem with the Ubuntu 11.10 Desktop and Alternate boot CDs, too. For a story of me troubleshooting this problem, check out this thread: http://ubuntuforums.org/showthread.php?t=1942937 Let me know if you need anything else from me, or want me to try anything. I would like to have ACPI working. Thank you. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-18-generic 3.0.0-18.31 ProcVersionSignature: Ubuntu 3.0.0-18.31-generic 3.0.26 Uname: Linux 3.0.0-18-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paul 1824 F pulseaudio /dev/snd/controlC0: paul 1824 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfa60 irq 48' Mixer name : 'Realtek ALC889' Components : 'HDA:10ec0889,10ec0889,0014' Controls : 41 Simple ctrls : 23 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfa08 irq 17' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Wed Apr 4 23:20:33 2012 HibernationDevice: RESUME=UUID=671dbf57-276e-4d7e-acda-da8bd954854f InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-18-generic root=UUID=8cb7655f-2b04-43dc-984c-d395b2f16e23 ro acpi=off quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-18-generic N/A linux-backports-modules-3.0.0-18-generic N/A linux-firmware1.60.1 RfKill: SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EVGA E685 dmi.board.vendor: EVGA dmi.board.version: Cougar Point 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.:bvr4.6.4:bd10/03/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnEVGA:rnEVGAE685:rvrCougarPoint:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973933 Title: Random Reboot if I Boot with ACPI On To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/973933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973933] Re: Random Reboot if I Boot with ACPI On
** 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. https://bugs.launchpad.net/bugs/973933 Title: Random Reboot if I Boot with ACPI On To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/973933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 558872] Re: empathy accounts fail to connect after manually unlocking keyring
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 log-on enabled; did it a ways back, many Ubuntu versions ago. When I booted up, keyring manager would ask me to unlock. After typing in my password, I would notice that Indicator Applet Session had all the status options grayed out, and had no text box for typing in. In the Indicator Applet menu, there were no little white arrows on the left (which seem to appear when the relevant program is running, background or foreground). If I clicked on Chat to open Empathy, Empathy showed no contacts, and opening Edit Accounts showed they were all Offline - Status is set to offline. Gwibber seemed to work fine, once I opened it by clicking Broadcast in the Indicator Applet menu (though I did not try posting anything). However, the text box still did not appear in the Indicator Applet Session. I did not try the things the OP did to get the Empathy accounts to connect. Now, the work around: I opened up Seahorse using Applications Accessories Passwords and Encryptions Keys, right clicked Passwords: login, and changed my password to be black (it wasn't before). By the way, this is probably generally a bad idea security wise. After rebooting, the keyring manager did not pop up asking for anything, but things still looked the same. But then, clicking Chat and Broadcast in Indicator Applet made Indicator Applet Session work wonderfully, and my accounts logged in in Empathy. Then, I just set empathy and gwibber to run automatically in System Preferences Startup Applications, rebooted, and everything was awesome. Gwibber does pop up on screen when the desktop loads, but that's OK for now. -- empathy accounts fail to connect after manually unlocking keyring https://bugs.launchpad.net/bugs/558872 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
