[Bug 70677] guidance-power-manager.py crashes on Transmeta Crusoe
Public bug reported: Binary package hint: kde-guidance-powermanager Kubuntu 6.10 (Edgy), upgraded from 6.06 using apt-get. Hardware: Fujitsu Lifebook P2120 with the following processor: $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineTMx86 cpu family : 6 model : 4 model name : Transmeta(tm) Crusoe(tm) Processor TM5800 stepping: 3 cpu MHz : 933.000 cache size : 512 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr cx8 sep cmov mmx longrun lrti up bogomips: 1872.91 When i start my KDE session, guidance-power-manager.py crashes with the attached traceback. It appears to be trying to read from /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq , which does not exist on my system. The contents of /sys/devices/system/cpu/cpu0/cpufreq/ are as follows: $ ls -lF /sys/devices/system/cpu/cpu0/cpufreq/ total 0 -r--r--r-- 1 root root 4096 2006-11-06 19:09 affected_cpus -r 1 root root 4096 2006-11-06 19:09 cpuinfo_cur_freq -r--r--r-- 1 root root 4096 2006-11-06 19:09 cpuinfo_max_freq -r--r--r-- 1 root root 4096 2006-11-06 19:09 cpuinfo_min_freq -r--r--r-- 1 root root 4096 2006-11-06 19:09 scaling_available_governors -r--r--r-- 1 root root 4096 2006-11-06 19:09 scaling_driver -rw-r--r-- 1 root root 4096 2006-11-03 09:54 scaling_governor -rw-r--r-- 1 root root 4096 2006-11-06 19:09 scaling_max_freq -rw-r--r-- 1 root root 4096 2006-11-06 19:09 scaling_min_freq (Note that i am using /usr/bin/longrun to control the power characteristics of my Transmeta processor). Looks to me as if guidance-power-manager should handle this condition more gracefully. ** Affects: kde-guidance (Ubuntu) Importance: Undecided Status: Unconfirmed -- guidance-power-manager.py crashes on Transmeta Crusoe https://launchpad.net/bugs/70677 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 70677] Re: guidance-power-manager.py crashes on Transmeta Crusoe
** Attachment added: "Traceback from guidance-power-manager.py" http://librarian.launchpad.net/4974679/guidance-power-manager-traceback.log -- guidance-power-manager.py crashes on Transmeta Crusoe https://launchpad.net/bugs/70677 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 69725] Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock
Public bug reported:
Recently upgraded from Dapper (6.06) to Edgy (6.10). My console keymap
suddenly changed from using Caps_Lock on the [Caps Lock] key to using
Shift_Lock.
I tracked it down the following lines in /usr/bin/ckbcomp:
# A hack to work around a bug in the kernel/loadkeys
if (! $acm) {
$xkbsym_table{'Caps_Lock'} = 'Shift_Lock';
$xkbsym_table{'ISO_Lock'} = 'Shift_Lock';
}
What gives? This makes my console nearly unusable; when I press '}' I
get ']', when I press '_' I get '-', etc.
My /etc/default/console-setup file (as written by the upgrade from
Dapper to Edgy):
# A configuration file for setupcon
# Change to "yes" and setupcon will explain what is being doing
VERBOSE_OUTPUT=no
# Setup these consoles. Most people do not need to change this.
ACTIVE_CONSOLES="/dev/tty[1-6]"
# Put here your encoding. Valid charmaps are: UTF-8 ARMSCII-8 CP1251
# CP1255 CP1256 GEORGIAN-ACADEMY GEORGIAN-PS IBM1133 ISIRI-3342
# ISO-8859-1 ISO-8859-2 ISO-8859-3 ISO-8859-4 ISO-8859-5 ISO-8859-6
# ISO-8859-7 ISO-8859-8 ISO-8859-9 ISO-8859-10 ISO-8859-11 ISO-8859-13
# ISO-8859-14 ISO-8859-15 ISO-8859-16 KOI8-R KOI8-U TIS-620 VISCII
CHARMAP="UTF-8"
# The codeset determines which symbols are supported by the font.
# Valid codesets are: Arabic Armenian CyrAsia CyrKoi CyrSlav Ethiopian
# Georgian Greek Hebrew Lao Lat15 Lat2 Lat38 Lat7 Thai Uni1 Uni2 Uni3
# Vietnamese. Read README.fonts for explanation.
CODESET="Lat15"
# Valid font faces are: VGA (sizes 8, 14 and 16), Terminus (sizes
# 12x6, 14, 16, 20x10, 24x12, 28x14 and 32x16), TerminusBold (sizes
# 14, 16, 20x10, 24x12, 28x14 and 32x16), TerminusBoldVGA (sizes 14
# and 16), Fixed (sizes 13, 14, 15, 16 and 18), Goha (sizes 12, 14 and
# 16), GohaClassic (sizes 12, 14 and 16).
FONTFACE="VGA"
FONTSIZE="16"
# You can also directly specify nonstandard font and ACM to load:
# FONT=/usr/local/share/funnyfonts/sarge16.psf
# ACM=/usr/local/share/consoletrans/my_special_encoding.acm
# The following variables describe your keyboard and can have the same
# values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
# in /etc/X11/xorg.conf.
XKBMODEL="pc104"
XKBLAYOUT="us"
XKBVARIANT="dvorak"
XKBOPTIONS="compose:rwin,lv3:ralt_switch"
# Do not update the following md5 sum if you change
# /etc/console-setup/boottime.kmap.gz and Debconf will not overwrite
# your custom keymap. Do not update it even if you want to make
# Debconf overwrite it. Instead simply specify the empty string as
# a md5 sum.
BOOTTIME_KMAP_MD5="57693d0f9f70248385305611a2764a2c"
** Affects: console-setup (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock
https://launchpad.net/bugs/69725
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69725] Re: Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock
** Attachment added: "My /etc/default/console-setup file (as written by the upgrade from Dapper to Edgy)" http://librarian.launchpad.net/4945568/console-setup -- Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock https://launchpad.net/bugs/69725 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75649] edgy: update-initramfs fails with 'mkinitramfs: invalid option' when given -v
Public bug reported:
Binary package hint: initramfs-tools
# update-initramfs -c -v -k `uname -r`
update-initramfs: Generating /boot/initrd.img-2.6.17-10-generic
/usr/sbin/mkinitramfs: invalid option --
/usr/sbin/mkinitramfs: invalid option -- -
Terminating...
mkinitramfs failed for /boot/initrd.img-2.6.17-10-generic
#
Problem lies in spurious double quotes around ${OPTS} when calling
mkinitramfs. Patch attached.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
edgy: update-initramfs fails with 'mkinitramfs: invalid option' when given -v
https://launchpad.net/bugs/75649
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75649] Re: edgy: update-initramfs fails with 'mkinitramfs: invalid option' when given -v
** Attachment added: "patch to fix option passing from update-initramfs to mkinitramfs" http://librarian.launchpad.net/5388339/update-initramfs.diff -- edgy: update-initramfs fails with 'mkinitramfs: invalid option' when given -v https://launchpad.net/bugs/75649 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
