[Bug 966237] Re: Scrolling directing is hard-coded/reversed from xinput
@Timo Yeah, I believe it's gnome, more so. It's part of a long time attitude on the part of gnome developers, constantly breaking their own software, be it simple themes, standard desktop norms, or as we have here ... mouse configurability, all against user wishes. Apparently it's fixed as reported on https://bugzilla.gnome.org/show_bug.cgi?id=682457. I'll look into it and try to report back. It took them 3 years to find a fix, and it's tentative at this point. Gees, gnome! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966237 Title: Scrolling directing is hard-coded/reversed from xinput To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/966237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984248] Re: Logging out of sessions results in a transitional black textual screen --12.10 upgrade
The screen on the model I reported has failed on me. I now use an external monitor hooked up via vga. I still get blanking but inquiries tell me that this is due to variability in card and monitor resolution tolarancy. So, I can't speak to this any longer. Now if Ubuntu recognized the monitor via DVI, I could futher provide feedback. I don't think it's a proprietary DVI as it fits a regular DVI cable (dual-link DVI is what wikipedia says). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984248 Title: Logging out of sessions results in a transitional black textual screen --12.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/984248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875375] Re: Resume fails after suspend/hibernate --post Oneiric upgrade
Both states last I recall worked on the latest release. I'm testing trusty right now but both states aren't accessible via synapse presently. I don't know if they will but expect it to be so. I'll try to dig around for the line commands ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875375 Title: Resume fails after suspend/hibernate --post Oneiric upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/875375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984248] Re: Logging out of sessions results in a transitional black textual screen --12.10 upgrade
I don't think it's a proprietary DVI (on the part of the MacBook Pro) as it fits a regular DVI cable. dual-link DVI is what wikipedia says the MacBook Pro has. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984248 Title: Logging out of sessions results in a transitional black textual screen --12.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/984248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1031621] Re: External Citizen monitor does not autoconfigure anymore
** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1031621 Title: External Citizen monitor does not autoconfigure anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1031621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047146] Re: xorg fails to configure native 1440 x 900 on LCD widescreen
I'm runing trusty and it's not an issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047146 Title: xorg fails to configure native 1440 x 900 on LCD widescreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075274] Re: Flash Plugin crashes in YouTube Fullscreen mode
Leaving nothing but the following lines in /etc/adobe/mms.cfg solved it for me. EnableLinuxHWVideoDecode=0 OverrideGPUValidation=true http://ubuntuforums.org/showthread.php?t=1985689 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075274 Title: Flash Plugin crashes in YouTube Fullscreen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/1075274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192431] Re: gnome-pie is not working!
@ Simon Schneegans Yeah, tried your ppa to no avail. Your program wants libbamf3-1 but chokes since only libbamf3-2 is available. I'm running Saucy. wajig install gnome-pie Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help resolve the situation: The following packages have unmet dependencies: gnome-pie : Depends: libbamf3-1 but it is not installable E: Unable to correct problems, you have held broken packages. wajig search libbamf3-1 mo@mc:~$ wajig search libbamf libbamf-doc - Window matching library - documentation libbamf3-2 - Window matching library - shared library libbamf3-dev - Window matching library - development files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192431 Title: gnome-pie is not working! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-pie/+bug/1192431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] Re: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU!
** Description changed: Symptoms: Excessive fan use. Ran fine with Ubuntu Natty Narwhal, but successive upgrades resulted in both fans running full shortly after bootup (regression). I justified it thinking that Ubuntu had higher requirements, until infrequent failed attempts to boot finally resulted in the on-screen posting of coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! on Raring. Now on Saucy, although without any failed boots, I find the same error by checking dmesg: dmesg | grep coretemp [ 47.314949] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! [ 47.314958] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! sudo lsmod | grep coretemp outputs coretemp 13195 0 sudo sensors -s gives no output at the moment. I do have the coretemp listed to be loaded: cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with # are ignored. lp #speedstep_centrino # kernel's job now, cpu frequency scaling #acpi_cpufreq # kernel's job now, cpu frequency scaling cpufreq_ondemand #responsive, cpu frequency scaling #cpufreq_conservative # slow, cpu frequency scaling ## Chip drivers , as per lm-sensors, sudo sensors-detect, and Psensor #coretemp lm63 ## Used by macfanctld from https://launchpad.net/~mactel-support/+archive/ppa applesmc coretemp Comments observations I do know Errata is code for defective firmware and that this has been dealt with prior http://lkml.org/lkml/2007/6/16/173 (thus this is a regression) and that I'm not alone: https://bbs.archlinux.org/viewtopic.php?id=143492 http://ww.ubuntuforums.org/showthread.php?t=814314 Interestingly, http://ubuntuforums.org/showthread.php?t=1239544 mentions in passing Intel's microcode update, which I find isn't applicable considering that my fans ran fine on Natty. I find the other suggestion, put the following into /etc/rc.local disconcerting considering that software is supposed to accommodate defective microcode and regularly does, but also that half a decade has come and gone with this issue. Still, it seems most plausible that the pertinent microcode is not loaded before the coretemp module jumps into action. WORKAROUND: add in /etc/rc.local : modprobe coretemp + and install + intel-microcode + --- ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mo 3726 F pulseaudio /dev/snd/controlC0: mo 3554 F volumeicon mo 3726 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=971dcaf3-f640-4d1c-9cb6-ea8eba0cab54 InstallationDate: Installed on 2011-09-05 (733 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Apple Computer, Inc. MacBookPro1,1 MarkForUpload: True Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=9c44e3b1-d6d1-4ca7-a621-c0142ded125a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 StagingDrivers: zram Tags: saucy staging Uname: Linux 3.11.0-4-generic i686 UpgradeStatus: Upgraded to saucy on 2013-09-01 (6 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 10/12/06 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MBP11.88Z.0055.B08.0610121325 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F425BEC8 dmi.board.vendor: Apple Computer, Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 8 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F425BEC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMBP11.88Z.0055.B08.0610121325:bd10/12/06:svnAppleComputer,Inc.:pnMacBookPro1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F425BEC8:rvrPVT:cvnAppleComputer,Inc.:ct8:cvrMac-F425BEC8: dmi.product.name: MacBookPro1,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] Re: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU!
There are two issues, a timing one and a firmware one. Thanks to http://forums.gentoo.org/viewtopic-t-573272-view-previous.html?sid=dc5a86b654f0b9d93e91e7438f8bf05c and http://www.thinkwiki.org/wiki/Intel_Core_2_Duo_%28Merom%29 I learned that the core2Duo has a microcode update and that it should be called microcode-ctl. The thing is that I have a core duo. https://wiki.archlinux.org/index.php/Microcode seems to suggest that the core duo also is due updates (despite http://www.thinkwiki.org/wiki/Intel_Core_Duo_%28Yonah%29 not being suggestive). Luckily updates are now not Windows only. wajig search microcode intel-microcode - Processor microcode firmware for Intel CPUs microcode.ctl - Intel IA32/IA64 CPU Microcode Utility (transitional package) So in Ubuntu it was microcode.ctl but is now intel-microcode. wajig install intel-microcode Despite assigning coretemp to /etc/modules I still get the following error from dmesg | grep coretemp [ 47.314949] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! [ 47.314958] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! That when I thought a timing issue might be responsible as gleaned from https://bbs.archlinux.org/viewtopic.php?pid=1117664#p1117664 or https://bbs.archlinux.org/viewtopic.php?id=143492 despite odd Arch idiosyncrasies. So as suggested at http://ubuntuforums.org/showthread.php?t=1239544 I added modprobe coretemp to /etc/rc.local, reboot and voila, dmesg | grep coretemp shows no more related errors. I solved the issue but I must say that the bug is in the OS in failing to assess the need/option and configure. Now the unsolved forum string might benefit: ww.ubuntuforums.org/showthread.php?t=814314 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
Although the last few updates in Raring introduced system freezes, I can't say they were LIRC/Atheros related. They seemed to be related to un/mounting of USB pendrives, but I didn't bother to stick around. I upgraded to avoid the problem altogether. I can say the first I recognized the kernel panic at hand was in Saucy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
I just had a kernel panic with ath9k. The odd thing about it is that the trace made mention of appleir and up funtionality despite not touching the remote. It ocurred while closing off Parole. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
And I don't have Parole configured to work with lirc. Althoug I think I had vlc running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
I recently read that Atheros can work either with ath5k or ath9k so I blacklisted the prior and enabled the latter on bootup the following way. sudo nano /etc/modprobe.d/blacklist.conf blacklist ath5k sudo nano /etc/modules ath9k Again, this allows me to start vlc with ir support enabled and only ends in a kernel panic when the remote is utilized --which is better than opening vlc with ir support and have it cause the kernel panic. All this makes me think there are two bugs here, a conflict between ath6k and lirc and the other between ath9k against lirc, the earlier being the worse since it's the most incapacitating. So presumably you can now surf wirelessly and reliably, just don't use the ir remote, still. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
There, I've identified a bug, confirmed it's reproducible and how, established the culprits involved but to summarize: identified bug: Kernel Panic --not syncing fatal exception in interrupt how it's reproducible: Start mplayer to watch a video or vlc with infrared enabled or $ irrecord -d /dev/usb/hiddev0 -H macmini output_conf_file culprits involved: lirc ath5k workaround: sudo rmmod ath5k Don't use the remote comments: The bug exists upstream The bug possibly seems to have existed since 3.8 Now I don't know what ath5k has to do with infrared but there's little doubt in my mind that there is a conflict between it and lirc functionality. Let me know if this is going to be taken care of else I'll take it upstream with the atheros and lirc people. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
OK, I think I may be onto something. The only thing that comes close to the error message are problems with wireless. Before I go further, vlc is crashing on startup because ir support is now enabled. http://forum.ubuntu-fr.org/viewtopic.php?id=1258711 makes mention of Atheros issues est incompatible avec un grand nombre de config et particulièrement avec les cartes Atheros. So I looked for an Atheros module with: lsmod | grep ath ath5k 134963 0 ath19187 1 ath5k mac80211 513247 1 ath5k cfg80211 401436 3 ath,ath5k,mac80211 After sudo rmmod ath5k I can open and run vlc (and Totem). Having done all that, I can again invoke a kernel panic by using the remote, namely with the up button, but at least it's manageable, at least as long you don't use the ir remote. According to Cara-bump on the thread quoted, Atheros issues started with kernel 3.8 or so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
I just tried linux- image-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_i386.deb last night and it has the same issue. Interestingly, vlc doesn't respond to the remote but this does not immediately cause the kernel panic, not until I startup totem, but that may have been because infrared capability was not on (on vlc). I just had a crash watching a video via vlc and I didn't even touch the remote (running on 3.11.0-8-generic). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
call trace ** Attachment added: P1010856.JPG https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+attachment/3833927/+files/P1010856.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
call trace ** Attachment added: P1010852.JPG https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+attachment/3833929/+files/P1010852.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
call trace ** Attachment added: P1010855.JPG https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+attachment/3833928/+files/P1010855.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
call traces ** Attachment added: P1010857.JPG https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+attachment/3833917/+files/P1010857.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
call trace ** Attachment added: P1010854.JPG https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+attachment/3833930/+files/P1010854.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
I reinstalled lirc lirc-x gnome-lirc-properties Considering that my previously working/etc/lirc/hardware.conf mentions /dev/usb/hiddev0 I ran the following and was able to immediately elicit a kernel panic response. irrecord -d /dev/usb/hiddev0 -H macmini output_conf_file -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
Considering that my previously working/etc/lirc/hardware.conf mentions /dev/usb/hiddev0 I ran the following and was able to immediately elicit a kernel panic response. irrecord -d /dev/usb/hiddev0 -H macmini output_conf_file and that as regular user! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
problem exists running linux- image-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_i386.deb By the way, I get the following when trying to follow: kernel-bug-exists-upstream-VERSION-NUMBER See: kernel-bug-exists-upstream-linux-image-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_i386' isn't a valid tag name. Tags must start with a letter or number and be lowercase. The characters +, - and . are also allowed after the first character. ** Tags removed: needs-upstream-testing ** 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/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
this sounds an awful lot like a bug reported last year in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066449. AND http://ubuntuforums.org/showthread.php?t=2142150 Although the latter inculpates jupiter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
Yes, my issue started with the upgrade. I still have the issue and I'm running 3.11.0-7-generic. For comparative purposes, linux- image-3.11.0-031100-generic_3.11.0-031100.201309021735_i386.deb from https://wiki.ubuntu.com/KernelMainlineBuilds (the one all the way at the bottom) has the same issue. I see that there is a newer kernel (3.12) which I may try soon. As for it being a regression, this sounds an awful lot like a bug reported last year in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066449. This one was not followed up on. It may be a long standing issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] [NEW] Kernel Panic --not syncing fatal exception in interrupt
Public bug reported: Using the infrared remote control results in a kernel panic. This is reproducible using mplayer. 1) lsb_release -rd Description:Ubuntu Saucy Salamander (development branch) Release:13.10 2) apt-cache policy linux linux: Installed: (none) Candidate: 3.11.0.4.5 Version table: 3.11.0.4.5 0 500 http://ca.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages uname -r 3.11.0-4-generic apt-cache policy mplayer mplayer: Installed: (none) Candidate: 2:1.0~rc4.dfsg1+svn34540-1ubuntu4 Version table: 2:1.0~rc4.dfsg1+svn34540-1ubuntu4 0 500 http://ca.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages 2:1.0~rc4.dfsg1+svn34540-1ubuntu2 0 100 /var/lib/dpkg/status 3) I expect to use the infrared remote successfully, without resulting in a kernel panic. 4) Audio loops like a scratched record, computer hard locks so that the keyboard becomes entirely unresponsive: no escaping to a tty, keyboard capslock doesn't light up, screen goes to tty1 and outputs Kernel Panic --not syncing fatal exception in interrupt, and SysRq-cntrl-alt-r does not reboot the computer. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic i686 ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mo 3994 F pulseaudio /dev/snd/controlC0: mo 3525 F volumeicon mo 3994 F pulseaudio /dev/snd/pcmC0D0c: mo 3994 F...m pulseaudio Date: Sat Sep 7 02:35:53 2013 HibernationDevice: RESUME=UUID=971dcaf3-f640-4d1c-9cb6-ea8eba0cab54 InstallationDate: Installed on 2011-09-05 (733 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Apple Computer, Inc. MacBookPro1,1 MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=9c44e3b1-d6d1-4ca7-a621-c0142ded125a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 SourcePackage: linux StagingDrivers: zram UpgradeStatus: Upgraded to saucy on 2013-09-01 (5 days ago) dmi.bios.date: 10/12/06 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MBP11.88Z.0055.B08.0610121325 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F425BEC8 dmi.board.vendor: Apple Computer, Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 8 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F425BEC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMBP11.88Z.0055.B08.0610121325:bd10/12/06:svnAppleComputer,Inc.:pnMacBookPro1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F425BEC8:rvrPVT:cvnAppleComputer,Inc.:ct8:cvrMac-F425BEC8: dmi.product.name: MacBookPro1,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 saucy staging ** Attachment added: lspci-vnvn.log https://bugs.launchpad.net/bugs/1222070/+attachment/3807085/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] [NEW] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU!
Public bug reported: Symptoms: Excessive fan use. Ran fine with Ubuntu Natty Narwhal, but successive upgrades resulted in both fans running full shortly after bootup (regression). I justified it thinking that Ubuntu had higher requirements, until infrequent failed attempts to boot finally resulted in the on-screen posting of coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! on Raring. Now on Saucy, although without any failed boots, I find the same error by checking dmesg: dmesg | grep coretemp [ 47.314949] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! [ 47.314958] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! sudo lsmod | grep coretemp outputs coretemp 13195 0 sudo sensors -s gives no output at the moment. I do have the coretemp listed to be loaded: cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with # are ignored. lp #speedstep_centrino # kernel's job now, cpu frequency scaling #acpi_cpufreq # kernel's job now, cpu frequency scaling cpufreq_ondemand #responsive, cpu frequency scaling #cpufreq_conservative # slow, cpu frequency scaling ## Chip drivers , as per lm-sensors, sudo sensors-detect, and Psensor #coretemp lm63 ## Used by macfanctld from https://launchpad.net/~mactel-support/+archive/ppa applesmc coretemp Comments observations I do know Errata is code for defective firmware and that this has been dealt with prior http://lkml.org/lkml/2007/6/16/173 (thus this is a regression) and that I'm not alone: https://bbs.archlinux.org/viewtopic.php?id=143492 http://ww.ubuntuforums.org/showthread.php?t=814314 Interestingly, http://ubuntuforums.org/showthread.php?t=1239544 mentions in passing Intel's microcode update, which I find isn't applicable considering that my fans ran fine on Natty. I find the other suggestion, put the following into /etc/rc.local disconcerting considering that software is supposed to accommodate defective microcode and regularly does, but also that half a decade has come and gone with this issue. Still, it seems most plausible that the pertinent microcode is not loaded before the coretemp module jumps into action. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apple macbook pro ** Attachment added: version.log https://bugs.launchpad.net/bugs/1222112/+attachment/3807318/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] Re: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU!
By the way, the other suggestion, to put modprobe coretemp into /etc/rc.local doesn't work as on reboot dmesg | grep coretemp outputs the same issue: [ 45.462182] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! [ 45.462194] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807353/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807357/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807356/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807351/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807354/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807355/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807349/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807358/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807352/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807359/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807350/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807360/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] Re: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU!
apport information ** Tags added: apport-collected saucy staging ** Description changed: Symptoms: Excessive fan use. Ran fine with Ubuntu Natty Narwhal, but successive upgrades resulted in both fans running full shortly after bootup (regression). I justified it thinking that Ubuntu had higher requirements, until infrequent failed attempts to boot finally resulted in the on-screen posting of coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! on Raring. Now on Saucy, although without any failed boots, I find the same error by checking dmesg: dmesg | grep coretemp [ 47.314949] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! [ 47.314958] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! sudo lsmod | grep coretemp outputs coretemp 13195 0 sudo sensors -s gives no output at the moment. I do have the coretemp listed to be loaded: cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with # are ignored. lp #speedstep_centrino # kernel's job now, cpu frequency scaling #acpi_cpufreq # kernel's job now, cpu frequency scaling cpufreq_ondemand #responsive, cpu frequency scaling #cpufreq_conservative # slow, cpu frequency scaling ## Chip drivers , as per lm-sensors, sudo sensors-detect, and Psensor #coretemp lm63 ## Used by macfanctld from https://launchpad.net/~mactel-support/+archive/ppa applesmc coretemp Comments observations I do know Errata is code for defective firmware and that this has been dealt with prior http://lkml.org/lkml/2007/6/16/173 (thus this is a regression) and that I'm not alone: https://bbs.archlinux.org/viewtopic.php?id=143492 http://ww.ubuntuforums.org/showthread.php?t=814314 Interestingly, http://ubuntuforums.org/showthread.php?t=1239544 mentions in passing Intel's microcode update, which I find isn't applicable considering that my fans ran fine on Natty. I find the other suggestion, put the following into /etc/rc.local disconcerting considering that software is supposed to accommodate defective microcode and regularly does, but also that half a decade has come and gone with this issue. - Still, it seems most plausible that the pertinent microcode is not - loaded before the coretemp module jumps into action. + Still, it seems most plausible that the pertinent microcode is not loaded before the coretemp module jumps into action. + --- + ApportVersion: 2.12.1-0ubuntu3 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: mo 3726 F pulseaudio + /dev/snd/controlC0: mo 3554 F volumeicon + mo 3726 F pulseaudio + DistroRelease: Ubuntu 13.10 + HibernationDevice: RESUME=UUID=971dcaf3-f640-4d1c-9cb6-ea8eba0cab54 + InstallationDate: Installed on 2011-09-05 (733 days ago) + InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) + MachineType: Apple Computer, Inc. MacBookPro1,1 + MarkForUpload: True + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=9c44e3b1-d6d1-4ca7-a621-c0142ded125a ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 + RelatedPackageVersions: + linux-restricted-modules-3.11.0-4-generic N/A + linux-backports-modules-3.11.0-4-generic N/A + linux-firmware1.113 + StagingDrivers: zram + Tags: saucy staging + Uname: Linux 3.11.0-4-generic i686 + UpgradeStatus: Upgraded to saucy on 2013-09-01 (6 days ago) + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare + dmi.bios.date: 10/12/06 + dmi.bios.vendor: Apple Computer, Inc. + dmi.bios.version: MBP11.88Z.0055.B08.0610121325 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: Mac-F425BEC8 + dmi.board.vendor: Apple Computer, Inc. + dmi.board.version: PVT + dmi.chassis.asset.tag: Asset Tag + dmi.chassis.type: 8 + dmi.chassis.vendor: Apple Computer, Inc. + dmi.chassis.version: Mac-F425BEC8 + dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMBP11.88Z.0055.B08.0610121325:bd10/12/06:svnAppleComputer,Inc.:pnMacBookPro1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F425BEC8:rvrPVT:cvnAppleComputer,Inc.:ct8:cvrMac-F425BEC8: + dmi.product.name: MacBookPro1,1 + dmi.product.version: 1.0 + dmi.sys.vendor: Apple Computer, Inc. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807348/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to:
[Bug 1222112] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807361/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807363/+files/WifiSyslog.txt ** 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/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222112] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1222112/+attachment/3807362/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222112 Title: coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222070] Re: Kernel Panic --not syncing fatal exception in interrupt
It almost goes without saying that the infrared works with LIRC. wajig show lirc Package: lirc State: installed Automatically installed: yes Version: 0.9.0-0ubuntu3 wajig show lirc-x Package: lirc-x State: installed Automatically installed: no Version: 0.9.0-0ubuntu3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222070 Title: Kernel Panic --not syncing fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986524] Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec
I get the mentioned output when X locks up (mouse movement excluded) running with a radeon x1600 video card, Gallium 0.4 on ATI RV530. I usually manage to get to tty* to see the error repeatedly posted and sometimes, with the addition of [drm:radeon_cs_chunk] *ERROR* failed to schedule IB!. Circumstances around error: To elaborate on the conditions around the time of the error, I can tell you you that I've noticed the problem when running shadows, transparency, transitions, fadings, and menu transparency via Compton, and shadows, fadings, and transparency via xcompmgr. While I write this, X is working functions properly but dmesg | garep radeon outputs: radeon :01:00.0: registered panic notifier ... [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! From there, killing the desktop session throws me back into a visually scrambled lightm, and the error continues to show up in tty1*. Doing sudo service lightdm restart (from tty*) does not alleviate the problem. I don't catch any other errors. /var/log/Xorg.0.log does not report any (after a reboot, mind you) other than complaining, Failed to load module fglrx (module does not exist, 0) twice, but it's normal --or so I've been told by a Ubuntu dev. Thoughts: Since I no longer use unity desktop and compiz but xcompmgr and compton, and I've gotten the error with both of the latter, I can assume it's not a compositor issue. I should say that I used to get compiz (and Unity) crashing all the time two years ago or so, the reason why I stopped using Unity, but I can't say I ever noticed this particular error back then. I've been happily using OB with xcompmgr for the past two years or so, untill now. I've always assumned the problems with Unity were video driver issues. So there's my two bits. Hopefully a savy dev can make sense of the source of the problem and issue a patch both locally and upstream. I'm running Raring by the way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986524 Title: radeon :02:00.0: GPU lockup CP stall for more than 1msec To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/986524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156525] Re: Back screen after wakeup
Oops, I read black screen for some reason. My problem is a hard lock. Please ignore my comments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156525 Title: Back screen after wakeup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156525] Re: Back screen after wakeup
I get the same issue on a macbook Pro intel with an ATI (Mobility) Radeon X1600 (ATI RV530/M56-P) video card with the 3. series kernel. This issue doesn't seem to have occurred with prior kernels, certainly not earilier than a week or two. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156525 Title: Back screen after wakeup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156525] Re: Back screen after wakeup
video card with the 3.8 series kernel, 3.8.0-17-generic to be exact. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156525 Title: Back screen after wakeup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156525] Re: Back screen after wakeup
I should mention that in my case, it's from the blackening of the screen due to inactivity that my laptop sometimes does not wake up from, not from closing the lid shut. As a workaround, I' ve gone to brightness and lock (gnome settings) and set Turn screen off when inactive for to Never and continued to keep the lock off (for extra measure). Here's to crossing my fingers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156525 Title: Back screen after wakeup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156525] Re: Back screen after wakeup
By the way, when the black screen occurs, my keyboard is unresponsive as I can't get my keyboard's Num Lock indicator to light up. Sysrq key combinations also fail to work (as noticed by the fact that the b combination does not result in a reboot and I don't get control over keyboard input back). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156525 Title: Back screen after wakeup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070150] Re: Intermittent black screen or low graphics mode message
I came across another fix, when changing the greeter stopped working. For those who removed Unity, removing it sometimes uninstalls unity- greeter and reinstalling it installs a whole lot of stuff some of which fixed my low resolution issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070150 Title: Intermittent black screen or low graphics mode message To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1070150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047156] Re: EDID does not allow LCD widescreen configuration
I came across another fix, when changing the greeter stopped working. For those who removed Unity, removing it sometimes uninstalls unity- greeter and reinstalling it installs a whole lot of stuff some of which fixed my low resolution issue. For some reason the other greeters don't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047156 Title: EDID does not allow LCD widescreen configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1095203] Re: low graphics mode
My fix being reinstalling unity-greeter. It installs a whole lot of stuff, one of which surely fixed my low resolution issue. For some reason I can't list the other greeters in lightdm.conf as doing so gives a low resolution message. So I'm stuck with unity-greeter, but at least I can run lightdm rather than gdm, which is flaky. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1095203 Title: low graphics mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1095203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1009321] Re: unity-greeter should depend on unity
@ Sebastien: I guess I would say that unity-greeter (or associated package) should depend on lightdm, and not unity-greeter should depend on unity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1009321 Title: unity-greeter should depend on unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1009321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070150] Re: Intermittent black screen or low graphics mode message
And don't list anything else but unity-greeter in lightdm.conf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070150 Title: Intermittent black screen or low graphics mode message To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1070150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1095203] Re: low graphics mode
I started to get the low res complaints after uninstalling Unity. You can only uninstall so many things (unity desktop, unity menu stuff ) before things get wacky (on various fronts). It took me months but I found out that removing unity components (menu, desktop, etc) using the howtos on the net sometimes uninstalls unity- greeter, which in turn causes the error. So that was my fix. The problem is that installing unity-greeter pulls in a ton of unnecessary stuff such as rhythmbox and lens packages, but that' s for another time an place. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1095203 Title: low graphics mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1095203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1009321] Re: unity-greeter should depend on unity
Sebastian: There sure is a connection. I' ve seen it myself where removing Unity (because it doesn' t run well on my machine) eventually removes unity-greeter and I start to get the low resolution error message. Reinstalling unity-greeter (which pulls in many things) results in a working lightdm (only with unity-greeter). So maybe the lightdm depends on something that gets added in along with unity- greeter. unity-greeter pulls in: wajig install unity-greeter The following NEW packages will be installed: appmenu-gtk appmenu-gtk3 appmenu-qt appmenu-qt5 compiz compiz-core compiz-gnome compiz-plugins-default freerdp-x11 gir1.2-rb-3.0 gnome-control-center-unity hud indicator-appmenu indicator-bluetooth indicator-datetime indicator-messages indicator-power indicator-printers indicator-session libcolumbus0-0 libcolumbus0-0-common libcompizconfig0 libdbusmenu-qt5 libdmapsharing-3.0-2 libfriends0 libglewmx1.8 libnux-4.0-0 libnux-4.0-common libpam-freerdp librhythmbox-core6 libtimezonemap1 libunity-core-6.0-5 libunity-misc4 lightdm-remote-session-freerdp lightdm-remote-session-uccsconfigure remote-login-service rhythmbox rhythmbox-data rhythmbox-mozilla rhythmbox-plugin-cdrecorder rhythmbox-plugin-zeitgeist rhythmbox-plugins rhythmbox-ubuntuone systemd-shim thin-client-config-agent unity unity-common unity-greeter unity-lens-applications unity-lens-files unity-lens-friends unity-lens-music unity-lens-photos unity-lens-shopping unity-lens-video unity-scope-gdrive unity-scope-musicstores unity-scope-video-remote unity-services That works, and presents me with a normal resolution lightdm. I further managed to keep lightdm running with a proper resolution by then removing the obviously unnecessary (I'm using OpenBox) from the above installed packages: wajig remove appmenu-gtk appmenu-gtk3 appmenu-qt appmenu-qt5 compiz compiz-core compiz-gnome compiz-plugins-default gnome-control-center- unity hud indicator-appmenu indicator-bluetooth indicator-datetime indicator-messages indicator-power indicator-printers indicator-session libcompizconfig0 librhythmbox-core6 libunity-core-6.0-5 libunity-misc4 rhythmbox rhythmbox-data rhythmbox-mozilla rhythmbox-plugin-cdrecorder rhythmbox-plugin-zeitgeist rhythmbox-plugins rhythmbox-ubuntuone unity unity-common unity-lens-applications unity-lens-files unity-lens-friends unity-lens-music unity-lens-photos unity-lens-shopping unity-lens-video unity-scope-gdrive unity-scope-musicstores unity-scope-video-remote unity-services So maybe the real lightdm dependency is in the remaining packages that are not accounted for, the ones not removed during the second line command (the removal of the obviously unnecessary packages). Maintainers/developers: Something to think about: maybe figure out what the needed dep is and link it in to lightdm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1009321 Title: unity-greeter should depend on unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1009321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047156] Re: EDID does not allow LCD widescreen configuration
I know this bug report has been closed but I'd still like to leave a record for myself and for any other having the same problems. @Rolf You might have been right about there being more than one issue at play here. Since reporting this, I've had to stop using lightdm because of it sending me into low graphics mode (message about running in low graphics mode in original report). I found out that lightdm's greeter is defined in /etc/lightdm/lightdm.conf and as of recent: greeter-session=unity-greeter I investigated further and realized that there is also a lightdm-gtk-greeter. I installed it and changed the above file to reflect: greeter-session=lightdm-gtk-greeter Result No more being thrown into low graphics mode. And lightdm seems less buggy than GDM. I still use ~/.xprofile as defined in my previous comment. I'm not sure if it's still helping out at the moment, but it's still there, as a fall back if things break, usually during major upgrades. No xorg.conf is being used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047156 Title: EDID does not allow LCD widescreen configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047156] Re: EDID does not allow LCD widescreen configuration
So being sent into low graphics mode would be one problem and the screen overshooting (low tolerance for defective EDID) would be another, the prior being solved and the later to be seen in 13.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047156 Title: EDID does not allow LCD widescreen configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070150] Re: Intermittent black screen or low graphics mode message
Changing the greeter invoked worked like a charm for me. I wrote about the fix in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047156 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070150 Title: Intermittent black screen or low graphics mode message To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1070150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047156] Re: EDID does not allow LCD widescreen configuration
@Rolf I'm connecting via VGA. In truth, my macbook pro has a HDMI, and it came with a HDMI to VGA adaptor. So my monitor receives a VGA signal, in the end. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047156 Title: EDID does not allow LCD widescreen configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986322] Re: Can't change layout using Unity indicator nor Gnome Control Center --12.10 upgrade
Anyway (for those that might come across this), I found a fix, my fix. 1. Open the gnome preference keyboard layout pane 2. Move the layout order, if you have more than one 3. Delete all layouts except the default one (mine was a US layout) The previous two steps have been suggested as fixes on their own (on the Ubuntu forums?). They did not work for me. I tried them together consecutively and this again did not work for me. Thus my next step. 4. Press, Reset to Defaults 5. Layout changes effectuated from both the layout pane and indicator now result in a change in layout. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986322 Title: Can't change layout using Unity indicator nor Gnome Control Center --12.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/986322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995401] Re: Ubuntu 12.04: keyboard layout does not change languages
*** This bug is a duplicate of bug 985065 *** https://bugs.launchpad.net/bugs/985065 Has anyone tried manually deleting additional layouts, leaving the default original, then pressing the default button in gnome preference's Layout pane? See my bug report and fix: https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/986322 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995401 Title: Ubuntu 12.04: keyboard layout does not change languages To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/995401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986322] Re: Can't change layout using Unity indicator nor Gnome Control Center --12.10 upgrade
6. Of course, add layouts back before attempting to change to them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986322 Title: Can't change layout using Unity indicator nor Gnome Control Center --12.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/986322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 898336] Re: tumblerd crashed with SIGSEGV in g_type_check_instance_is_a()
Replacing it might be an option as this seems to be an ongoing problem. Anyone know of a stand in? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/898336 Title: tumblerd crashed with SIGSEGV in g_type_check_instance_is_a() To manage notifications about this bug go to: https://bugs.launchpad.net/tumbler/+bug/898336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982234] Re: [region]: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()
I got the error while adding a layout. It crashed but the layout had been added,. or so one would think because it's listed, although the preview shows the same layout regardless of which one is selected --which may be a problem in of itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982234 Title: [region]: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/982234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047140] Re: lightdm overshoots physical screen size
@2vi1: Yeah, it overshoots at the bottom, too. I found two work-arounds. From memory, A. 1. select your wm, 2. tab (once if I recall), 3. press enter, then the dialogue window will change or go back to the log-in dialogue, 4. input your password if you haven't done so already and see yourself log into the desktop environment of your choice. Please feel free to correct me. B. Another work around is to uninstall unused window managers so as to make the drop down list shorter, optimizing use of screen real estate. Comment: I'd like to see this fixed, but there's two temporary solutions. Observation: I gather this is happening because the system's difficulty in determining my monitor's EDID, as reported at https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047156 Side Question: Might the system's difficulty in determining EDID drastically slow down boot up? I've run various diagnostics and my HD is fine, only one fan is out, which is noted by the Apple diagnostic. This MacBook Pro used to boot fine with prior versions of Ubuntu which didn't have this TFT issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047140 Title: lightdm overshoots physical screen size To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1047140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047140] Re: lightdm overshoots physical screen size
@2vi1: Do you have the same overshooting issue once logged into your desktop environment? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047140 Title: lightdm overshoots physical screen size To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1047140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047156] Re: EDID does not allow LCD widescreen configuration
After the system configured itself, it still boots into 1224 x 768 (4:3), which makes real estate go off-screen at the right and bottom, affecting both lightdm and the desktop environment. See my bug report at https://bugs.launchpad.net/lightdm/+bug/1047140 Solution: I've had to force the resolution with the following. xrandr --newmode 1440x900_60.00 106.47 1440 1520 1672 1904 900 901 904 932 +HSync +VSync xrandr --addmode DVI-0 1440x900_60.00 xrandr --output DVI-0 --mode 1440x900_60.00 In place of the first line, the following also has worked for me --something I just got off the net, if I recall. xrandr --newmode 1440x900_60.00 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync Now, I've had to automate it by placing that into ~/.xprofile Results: - X starts with the native mode 1440x 900 at 60 Hz, or just shy of 60, 59 if I recall. It blanks out black once or twice though. - lightdm sometimes entirely fits onto the physical screen, sometimes it doesn't. - It takes forever to reach lightdm. Might this be the EDID issue, causing a delay while Ubuntu decides how to treat my LCD screen? I've run various diagnostics and my HD is fine, only one fan is out, which is noted by the Apple diagnostic. This MacBook Pro used to boot fine with prior versions of Ubuntu which didn't have this TFT issue. Expected results: I guess it goes without saying that the expected results should be that the system should auto-configure itself so as to not require user intervention. And it should not go into an episodic and alternating blanking loop. Comments: I've had the same issue with another (LCD?) monitor on another Ubuntu 120.10 beta install, and I've had to resort to the same fix. Info to come. So I suspect that this is a LCD problem or one of just having low tolerance for defective EDID. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047156 Title: EDID does not allow LCD widescreen configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047146] Re: xorg fails to configure native 1440 x 900 on LCD widescreen
I gather this is related to the low tolerance of faulty EDID I reported in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047156 Here's what I reported therein. Solution: I've had to force the resolution with the following. xrandr --newmode 1440x900_60.00 106.47 1440 1520 1672 1904 900 901 904 932 +HSync +VSync xrandr --addmode DVI-0 1440x900_60.00 xrandr --output DVI-0 --mode 1440x900_60.00 In place of the first line, the following also has worked for me --something I just got off the net, if I recall. xrandr --newmode 1440x900_60.00 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync Now, I've had to automate it by placing that into ~/.xprofile Results: - X starts with the native mode 1440x 900 at 60 Hz, or just shy of 60, 59 if I recall. It blanks out black once or twice though. - lightdm sometimes entirely fits onto the physical screen, sometimes it doesn't. - It takes forever to reach lightdm. Expected results: I guess it goes without saying that the expected results should be that the system should auto-configure itself so as to not require user intervention. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047146 Title: xorg fails to configure native 1440 x 900 on LCD widescreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 410534] Re: gnome-settings-daemon crashed with SIGSEGV in g_slice_alloc()
I haven't noticed getting this while using pulseaudio,but I usually have vlc open and constantly watching something with audio. The only other common denominator, at least for me, is that I always get this while logged in using OpenBox. It's always after a gnome-settings-daemon error that my theme drops into something resembling Windows 95. I think what's happening is that my these support is dropped. What this has to do with pulse, is beyond me but the error always inculpates the gnome- settings-daemon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/410534 Title: gnome-settings-daemon crashed with SIGSEGV in g_slice_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/410534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
I'd say this is a bug in glib (gio) where it needs to remove the target if cancelled at the wrong place.¨ https://mail.gnome.org/archives/gvfs-list/2009-April/msg8.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048421] [NEW] empathy: Error contacting the Account Manager
Public bug reported: Problem: I've got accounts setup properly, facebook IM and gmail. I know they work because I access the accounts with other IM clients using the same credentials. Details: Upon starting empathy I get the following message twice: There was an error while trying to connect to the Telepathy Account Manager. The error was: Process /usr/lib/telepathy/mission-control-5 exited with status 1 The message on the roster says: You need to setup an account to see contacts here. Observation I check to see my accounts and they are most certainly there and configured. Apparently, there is a matter of dispute whether I have accounts configured or have them at all. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: empathy 3.5.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 Date: Sun Sep 9 21:02:44 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: empathy UpgradeStatus: Upgraded to quantal on 2012-08-18 (22 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048421 Title: empathy: Error contacting the Account Manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1048421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048421] Re: empathy: Error contacting the Account Manager
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048421 Title: empathy: Error contacting the Account Manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1048421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047140] [NEW] lightdm overshoots physical screen size
Public bug reported: Problem: lightdm displays excessively large Symptoms: I can't confirm change of window manager and top menu leaks over to right hand side. The screen is a LCD Citizen C19604HD that should run 1440x 900 at 60 Hz. Upon entering the desktop the session is also excessively large, 1224 x 768 (4:3) (apparently what's running in lightdm, as it offsets the same) and only allows a worse setting of 800 x 600 (4:3). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 ApportVersion: 2.5.1-0ubuntu4 Architecture: i386 Date: Thu Sep 6 23:08:10 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-08-18 (19 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047140 Title: lightdm overshoots physical screen size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1047140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047140] Re: lightdm overshoots physical screen size
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047140 Title: lightdm overshoots physical screen size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1047140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047140] Re: lightdm overshoots physical screen size
The monitor has an active display area of 410.4 mm x 256.5 mm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047140 Title: lightdm overshoots physical screen size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1047140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1031604] Re: cntrl-alt-del does not kill Xorg
Another carry over to 12.10 beta. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1031604 Title: cntrl-alt-del does not kill Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1031604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984248] Re: Logging out of sessions results in a transitional black textual screen --Precise upgrade
This again happens in 12.10 beta. It was fine till a few updates ago. This always seems to be the case in early betas until it's borked shortly before release. ** Summary changed: - Logging out of sessions results in a transitional black textual screen --Precise upgrade + Logging out of sessions results in a transitional black textual screen --12.10 upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984248 Title: Logging out of sessions results in a transitional black textual screen --12.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/984248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047140] Re: lightdm overshoots physical screen size
It's a widescreen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047140 Title: lightdm overshoots physical screen size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1047140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047146] [NEW] xorg fails to configure native 1440 x 900 on LCD widescreen
Public bug reported: The screen is a LCD Citizen C19604HD that should run 1440x 900 at 60 Hz (as per manual). Upon entering the desktop the session is also excessively large, 1224 x 768 (4:3) and only allows a worse setting of 800 x 600 (4:3). I must say, that every once in a while, Display panel will show the following available (I've tried all of them) resolutions. The problem is that they're usually not accessible. For the sake of completeness, I'll list them all, although I'm only really interested in the top one. 1440 x 900 1366 x 768 1360 x 768 1280 x 1024 1280 x 960 1280 x 800 1280 x 768 1152 x 864 1024 x 768 1024 x 576 832 x 624 800 x 600 When confronted with the black screen, I've tried editing xorg.conf, but that's resulted in black screens, even black ttys, forcing me to do the following workaround: -boot up on a live-cd, -mount the HD and -sudo rm /etc/X11/xorg.conf -reboot onto the HD ** Affects: xorg (Ubuntu) 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/1047146 Title: xorg fails to configure native 1440 x 900 on LCD widescreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047146] Re: xorg fails to configure native 1440 x 900 on LCD widescreen
Correction: Upon entering the desktop the session is also excessively large, 1024 x 768 (4:3) ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047146 Title: xorg fails to configure native 1440 x 900 on LCD widescreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047156] [NEW] EDID does not allow LCD widescreen configuration
Public bug reported: Ubuntu has new strict EDID guidelines that does not allow LCD widescreen configuration. Symptoms: Constant flickering on and off of screen content, including distortion similar to a bad tv reception. The screen is a LCD Citizen C19604HD that should run 1440x 900 at 60 Hz (as per manual), which apparently does not have proper EDID. I should note this setup had no problems prior, until tty1 started to complain about a bad EDID checksum during 12.10 beta. Fix: Attempting to set my own xorg.conf evoked a message about running in low graphics mode. It asked if I wanted to (re)configure. I confirmed, after which I no longer needed xorg,conf, nor presumably Option IgnoreEDID on in xorg.conf which made xorg sessions usable. What should happen The system should be self-healing. The user should not have to grapple with xorg.conf (for hours or days on end with unfamiliar concepts [EDID] and work-arounds), and even less after all that time and effort just to have the system say, Hey, I don't like what you're doing. Here, let me do it.. This (self-repair) hook should be invoked sooner in the trouble shooting process. See related problem about https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047146 ** Affects: xorg (Ubuntu) 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/1047156 Title: EDID does not allow LCD widescreen configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047146] Re: xorg fails to configure native 1440 x 900 on LCD widescreen
My video card is a Radeon X1600, Gallium 0.4 on ATI RV530 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047146 Title: xorg fails to configure native 1440 x 900 on LCD widescreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022224] Re: tumblerd crashed with SIGSEGV in g_type_check_instance_is_a()
It happens to me when downloading a file from Firefox passed onto a line command downloader. The problem is not with Firefox or the downloader but as I recall with tumbler daemon, tumblerd if I recall, whose job it is to create images to downloaded files. Steps to reproduce -Download media files and you have a case where the daemon is constantly recreating the image to the file because it thinks the growing file is a new file and in need of a new image, constantly. This takes up about 100 of cpu and has been a problem for some years now. -And no it cr@ps out instead of almost freezing the desktop. And improvement, I wold say. tumblerd needs to be rethought. Work-around Close the file browser, that is presumably opened to the folder where the media file is being downloaded to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/104 Title: tumblerd crashed with SIGSEGV in g_type_check_instance_is_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tumbler/+bug/104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1031604] Re: cntrl-alt-del does not kill Xorg
This bug is still existent in 12.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1031604 Title: cntrl-alt-del does not kill Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1031604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1031593] Re: ATM/phone-style number pad fails to implement
This bug is still existent in 12.10 beta. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1031593 Title: ATM/phone-style number pad fails to implement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnomekbd/+bug/1031593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986322] Re: Can't change layout using Unity indicator nor Gnome Control Center --Precise upgrade
This is a selected excerpt taken from a related bug reported by moi. I intended to copy pertinent info over but must have never gotten it. I'd also hoped that it was noticed and taken care upstream but seeing now that 12.10 still has issues with changing layouts, here it is. 1) Changing the layout in unity's applet does not change it in X. /etc/default/keyboard shows the following, even if layouts are repositioned in Keyboard Layout in System Settings. XKBMODEL=pc104 XKBLAYOUT=us XKBVARIANT=intl XKBOPTIONS=terminate:ctrl_alt_bksp 2) lightdm takes to the change, at least if it's done via Keyboard Layout. 3) X doesn't take to the change even if it's done via Keyboard Layout. Clearly there is a conflict between /etc/default/keyboard and Keyboard Layout. I would assume a workaround to be to run the following: 1. sudo dpkg-reconfigure keyboard-configuration 2. and then to edit /etc/default/keyboard to coincide with the input into the previous routine (pkg-reconfigure keyboard-configuration) See http://krisreeves.com/things-that-should-be-easy/permanently-change- keyboard-layout-on-ubuntu-server-11-10/ There are various manifestations of this bug: 1) The issue of not being able to change a layout within a session from the Unity applet, /etc/default/keyboard not keeping sync with the unity indicator. 2) And the issue of /etc/default/keyboard not keeping in sync with selections taken in Keyboard Layout, which explains why desktop sessions (X) revert to previous settings. /etc/default/keyboard seems to want to do it's own thing, regardless of what other utilities want. 3) There are also the issues of any layout chosen from dpkg-reconfigure keyboard-configuration not sticking, /etc/default/keyboard not keeping sync with dpkg-reconfigure keyboard-configuration. ** Summary changed: - Can't change layout using Unity indicator nor Gnome Control Center --Precise upgrade + Can't change layout using Unity indicator nor Gnome Control Center --12.10 upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986322 Title: Can't change layout using Unity indicator nor Gnome Control Center --12.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/986322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 918072] Re: Selecting other session in login screen doesn't do anything
It's affecting me and I'm not using a live-CD, just an ordinary HD install. In my case, I'm constantly logged back into Openbox, which I like but sometimes want back into Unity, regardless of choosing Ubuntu (Unity) in lightdm. @Newfie Sebastien: If it were a problem with the password, it would not log me into any desktop. I still get into Openbox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918072 Title: Selecting other session in login screen doesn't do anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/918072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035760] Re: guake crashed with GError in test_gconf(): No D-BUS daemon running
step 1: I log in using lightdm step 2: lay back a minute step 3: receive the error message step4: use the desktop environment as an ordinary end user for everyday purposes, (open Firefox, Thunderbird, Marlin, Openbox with tint2, SeaMonkey) step5: at some random moment latter in the session, get the (presumably the) same message again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035760 Title: guake crashed with GError in test_gconf(): No D-BUS daemon running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guake/+bug/1035760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 749550] Re: gnome-settings-daemon crashed with SIGABRT in raise()
This happens in 12.10 too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/749550 Title: gnome-settings-daemon crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/749550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 542228] Re: goldendict crashed with SIGSEGV in exit()
Yeah, I always get a crash error on start-up and asks if I want to start it up again, despite that when I check it's still running. It doesn't affect functionality, apparently, just plain annoying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/542228 Title: goldendict crashed with SIGSEGV in exit() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/goldendict/+bug/542228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041049] [NEW] update-manager can't resolve calculating an update to latest 12.10
Public bug reported: Invoking update-manager results in the following message. An unresolvable problem occurred while calculating the upgrade. Please report this bug against the 'update-manager' package and include the following error message: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. wajig update wajig upgrade wajig distupgrade also similarly fails but with the following: SystemError: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. I don't have any pinned packages, if that is what was meant in the error message. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: update-manager 1:0.169 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic i686 ApportVersion: 2.5.1-0ubuntu1 Architecture: i386 Date: Fri Aug 24 02:07:44 2012 GsettingsChanges: b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'launch-time' b'1345788435' b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'600' b'com.ubuntu.update-manager' b'window-width' b'600' InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to quantal on 2012-08-18 (5 days ago) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041049 Title: update-manager can't resolve calculating an update to latest 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1041049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041049] Re: update-manager can't resolve calculating an update to latest 12.10
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041049 Title: update-manager can't resolve calculating an update to latest 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1041049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1031581] Re: Tumblerd and Marlin use all available cpu and more
Here's a complaint (from another user) and an explanation: http://askubuntu.com/questions/89826/what-is-tumblerd Thunar apparently still has the same issue (on Precise), but Nautilus on Precise doesn't, although on 12.10 beta it (Nautlilus) does. Apparently, this is a prevalent issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1031581 Title: Tumblerd and Marlin use all available cpu and more To manage notifications about this bug go to: https://bugs.launchpad.net/marlin/+bug/1031581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1031612] Re: Unity freezes using Gallium 0.4 on ATI RV530
The issue seems to have worked itself out on Precise, and on 12.10 it's not an issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1031612 Title: Unity freezes using Gallium 0.4 on ATI RV530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1031612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
