It happened to me again just now. I ssh'ed to the computer and did a
reboot, but even after the ssh service had shut down, the computer was
still hung with a frozen screen saver, and I still had to do a hardware
reset in order to get it going again.
--
You received this bug notification because
Noting once again that I am still having this problem. I am worried
because no one seems to be working on it or have any idea how to work
around it (other than by disconnecting the cable from my computer to the
back of my TV when I'm not playing something on the TV screen).
--
You received this
I am still occasionally experiencing this problem (or something that
looks just like it) in 2020. In my case, the freezing happens only when
the Cinnamon screen saver is active -- the date/time on the screen saver
stops advancing, and no keys or mouse clicks will revive it -- even
selectively
Still having this problem. I'm temporarily working around it by
disconnecting the HDMI cable from the computer to the back of the TV
when I'm not actually playing something on the larger screen, but this
is clearly not acceptable as a long-term solution.
--
You received this bug notification
I don't think Compiz is relevant here. My computer isn't running Compiz
— its display manager is GDM3 as best I can tell. (ri...@richw.org, the
original reporter of this bug)
** Package changed: compiz (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of
I note this bug has been classified as affecting Compiz. However, as
best I can tell, Compiz is not running on my computer. /etc/X11
/default-display-manager on my computer contains the value
"/usr/sbin/gdm3".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Ubuntu 19.10, gdm3 3.34.1-1ubuntu1, cinnamon 4.0.10-2, cinnamon-
screensaver 4.0.3-1, nvidia-driver 435.21-0ubuntu2.
I have a TV set connected to my computer as a second monitor (for
displaying YouTube videos, etc.).
When I turn off both my main monitor and the TV for the
The ppa:openafs/stable workaround restored AFS client service to my
machine (which had been lost after I switched to the HWE kernel in early
January 2018). Currently running openafs-client
1.6.22-3~ppa0~ubuntu16.04.1.
--
You received this bug notification because you are a member of Ubuntu
The first answer (from Sebastian Marsching) on this page worked for me:
https://askubuntu.com/questions/767786/changing-network-interfaces-name-ubuntu-16-04
In brief, he recommended removing the KERNEL=="eth*" parameter from each
line in the /etc/udev/rules.d/70-persistent-net.rules file.
I am
NOT working for me (Ubuntu 14.04, iPhone 4S running iOS 7.1.2).
I'm not getting the trust loop problem, but I am getting Unhandled
Lockdown error (-20) and cannot mount the iPhone in order to upload
photos into Shotwell.
I've tried the suggestion to make the /var/lib/lockdown directory
publicly
Now that the 3.8.0 kernel in in Precise, openafs appears to be broken
again.
My uname -a output is:
Linux liberation 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 18:21:16
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
My /var/lib/dkms/openafs/1.6.1/build/make.log file includes the following
Also happening to me.
The system has an AMD FX(tm)-8150 Eight-Core Processor.
uname -r output: Linux liberation 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed
Sep 11 18:21:16 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Attaching make.log file.
** Attachment added: make.log
Version 4.1.2-dfsg-2ubuntu0.5 (from precise-proposed) works for me.
uname -a output: Linux liberation 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed
Sep 11 18:21:16 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1076603 ***
https://bugs.launchpad.net/bugs/1076603
Version 4.1.12-dfsg-2ubuntu0.5 (from precise-proposed) appears to have
fixed the problem for me. See also bug #1076603.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I just upgraded from 11.10 to 12.04, and I'm getting this error.
I was able to run squidGuard -C all and squid3 -k reconfigure by
hand without any errors. However, aptitude install squidGuard still
gives the same error.
--
You received this bug notification because you are a member of Ubuntu
The problem went away for me after I noticed my /etc/services files was
missing a line for the squid service (3128/tcp) and re-added this
line. It might be worthwhile for others still seeing this bug to check
their /etc/services files, add the squid service if it's missing, and
report whether
Also won't build in 3.5.0.9-generic on a Lenovo Thinkpad T430.
I need to run 12.10 (even though it's alpha) because earlier releases
reportedly won't work on the Thinkpad T430.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm running 12.10 (quantal) alpha 3, with gnome-session-flashback. No
window decoration with Gnome Classic. I do have window decoration with
Gnome Classic (no effects).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When I tried apt-get install -f from a command line, I got this:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
samba-common
The following
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/993660
Title:
package samba-common 2:3.5.8~dfsg-1ubuntu2.4 failed to
install/upgrade: unable to open '/etc/dhcp3/dhclient-enter-
Public bug reported:
When I tried apt-get install -f from a command line, I got this:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
samba-common
The following
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993660
Title:
package samba-common 2:3.5.8~dfsg-1ubuntu2.4 failed to
install/upgrade: unable to open '/etc/dhcp3/dhclient-enter-
*** This bug is a duplicate of bug 823775 ***
https://bugs.launchpad.net/bugs/823775
Examine your directory WITHOUT mounting the encrypted partition. That
is, look at the .Private directory which contains a bunch of
ECRYPTFS... files and directories. In your case, you'll see a mix of
I got bitten by this bug tonight. Like Dave Gross, I discovered that my
.Private directory had a bunch of empty directories with unencrypted
names in it -- corresponding to the directory names that were duplicated
(and empty) when my eCryptfs directory was mounted. I fixed the problem
by
Since you have identified a specific file which seems to be read in two
different ways, it might be useful to capture the actual content of the
file in each case (not just the md5sum values) and see if there is any
discernible pattern to the corruption (e.g., extraneous trailing nulls
in one of
I think I'm running into this bug on an Ubuntu Lucid server. I tried to
install the rsyslog package on this server, but the start / stop /
restart functions would never complete (hangs forever). In the end, I
had to abandon rsyslog and go back to sysklogd — bad solution, I need
rsyslog, but I
I tried the Natty Beta 2 live CD just now.
No difference — exact same misbehaviour as with Maverick — a connection
attempt with my home access point configured for both A and N modes
still fails with exactly the same error message that I originally
reported — but I can connect just fine if the
My original report included what I assumed were all the relevant lines
from syslog — nine lines that were repeated over and over.
If you really, really insist you can't or won't investigate the bug
without my laptop's entire syslog file, I'll see what I can do — but in
that case, can you possibly
OK, I'm attaching a (hopefully substantial) portion of the laptop's
syslog. Please let me know if this is enough.
When this syslog excerpt shows a successful connection at the end,
please note that this was after I configured my access point back to
A-only mode on its 5-GHz radio.
** Attachment
Public bug reported:
Binary package hint: network-manager
I have a Dell Latitude D620, with a builtin Intel 3945ABG wifi adapter.
I am running Maverick, and the wifi adapter is being controlled by the
iwl3945 driver.
I can connect fine to 802.11g at work, and I can also connect fine to
802.11a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/759051
Title:
Intel 3945ABG wifi can't connect at all if 802.11a and 802.11n are
both available
--
ubuntu-bugs mailing list
I believe I am still being affected by this bug. On an up-to-date
Maverick, I cannot e-mail photos from Picasa 2.7 to Thunderbird 3.1.6;
Picasa says An error occurred while creating a message compose window.
Please try again.
The version of xdg-utils installed on this box is 1.0.2+cvs20100307-1.
I appear to be affected by this bug on two Ubuntu systems (one Maverick,
one Jaunty). Picasa can no longer e-mail photos since I upgraded to
Thunderbird 3 on both systems.
--
No attachment when thunderbird 3 is set as default client.
https://bugs.launchpad.net/bugs/515386
You received this bug
I, for one, am *not* willing to sacrifice the keyboard layout indicator.
If a user is using multiple layouts, the indicator is essential, and
removing it is (IMO) a significant regression from Lucid (where the
layout indicator worked just fine).
So, then, is this a bug in gnome-settings-daemon?
From the perspective of a naive (or not-so-naive) Ubuntu user who is
probably not aware of exactly which software component is doing which
keyboard layout-related task, all they will notice is that the indicator
icon breaks when they upgrade to Maverick.
If there is some reason why the Lucid
Just on a wild guess, I launched Add to Panel and added the Indicator
Applet — and a US flag (corresponding to my currently active keyboard
layout) showed up in the panel along the top of the screen.
Although (re-)adding the indicator applet seems to have fixed the
problem, there is still the
If this bug report is invalid w/r/t the indicator application, please
advise what needs to be done in order for the problem to be addressed.
It would (IMO) by a very bad thing if this problem were to be neglected,
and if Maverick were to be released without anything being done, on
account of the
I installed a set of flag icons (us.png, etc.) in ~/.icons/flags, and I
enabled /desktop/gnome/peripherals/keyboard/indicator/showFlags in
gconf-editor, but this did no good — in fact, it made the static
keyboard icon go away entirely (replaced with a generic I can't find
any icon to display here
@divan: Could you clarify exactly how you set up your keyboard layout
indicator to show country flags?
One problem I've been having (at the same time as this random layout
switching bug) is that I am no longer seeing any indication of my
current keyboard layout at all. All I am now seeing is an
*** This bug is a duplicate of bug 531173 ***
https://bugs.launchpad.net/bugs/531173
Appears to be a duplicate of bug #531173.
** This bug has been marked a duplicate of bug 531173
New Lucid keyboard layout indicator does not indicate current layout
* You can subscribe to bug 531173 by
I see an icon that looks like a little keyboard, but it doesn't indicate
the current keyboard layout any longer (via an abbreviation like USA
or Rus) the way it used to. I can do a left-click on the icon and get
a list of radio buttons allowing me to see/change the layout, but
nothing shows the
Public bug reported:
Binary package hint: gnome-settings-daemon
I'm using multiple keyboard layouts. The current layout for the
currently active window used to be identified with an abbreviation
(e.g., USA or Rus) along the top of the screen.
When I went from Lucid to Maverick beta, however,
I haven't seen the crazy switching problem in a few days either —
though this could be because I temporarily reduced my number of keyboard
layouts to two and made a couple of other changes to my settings.
I'm much more disturbed by the apparent regression in functionality
where the indication of
Is this a duplicate of bug #630347?
--
keyboard layout switching goes crazy
https://bugs.launchpad.net/bugs/636619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
OK, thanks.
--
maverick upgrade error: /usr/share/initramfs-tools/hooks/iscan failed with
return 1
https://bugs.launchpad.net/bugs/631167
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: initramfs-tools
While attempting to upgrade a Lucid system to the Maverick beta, some
sort of error occurred during the upgrade process. When I tried to
complete the upgrade, I got errors which appear to point to a problem in
initramfs-tools. I retried
** Attachment added: output of aptitude safe-upgrade
https://bugs.launchpad.net/bugs/631167/+attachment/1547915/+files/upgrade-broken.txt
--
maverick upgrade error: /usr/share/initramfs-tools/hooks/iscan failed with
return 1
https://bugs.launchpad.net/bugs/631167
You received this bug
I also tried forcibly uninstalling initramfs-tools (using the --force-
depends option to dpkg), and then reinstalling it, but this didn't help;
the problem persists.
--
maverick upgrade error: /usr/share/initramfs-tools/hooks/iscan failed with
return 1
https://bugs.launchpad.net/bugs/631167
You
Public bug reported:
Binary package hint: apcupsd
I replaced the battery in my APC Back-UPS XS 1500 LCD last night. I
temporarily connected the data cable from the UPS to a PC running APC's
PowerChute Personal Edition utility, and I clicked the icon to update
the battery change date. But when
** Attachment added: Output of apcaccess command; note bogus BATTDATE value
https://bugs.launchpad.net/bugs/629816/+attachment/1540990/+files/apcaccess.txt
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/629816/+attachment/1540991/+files/Dependencies.txt
--
Let's all PLEASE keep it civil. We can disagree on technical or policy
issues without engaging in personal attacks (or perpetuating a toxic
atmosphere by responding in kind to what we may perceive as personal
attacks by others). Thanks.
--
[Master] Window Control buttons:
Unfortunately, Mark Shuttleworth has said (see comment #564) that this
decision is final and that no complaints or negative votes would make
any difference.
--
[Master] Window Control buttons: position/order/alignment
https://bugs.launchpad.net/bugs/532633
You received this bug notification
I've been seeing this bug in Karmic for some time now.
--
gnome-screensaver bad password timeout
https://bugs.launchpad.net/bugs/314545
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I've been seeing this bug in Karmic for a long time. Ctrl-alt-backspace
does NOT kill X. Ctrl-alt-delete does NOT reboot.
--
Unable to unlock the screensaver
https://bugs.launchpad.net/bugs/181065
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This bug (or a very similar bug) is alleged to have been fixed for Lucid
(bug #524860).
--
Unable to unlock the screensaver
https://bugs.launchpad.net/bugs/181065
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
This bug (or a very similar bug) is alleged to have been fixed for Lucid
(bug #524860).
--
gnome-screensaver bad password timeout
https://bugs.launchpad.net/bugs/314545
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Is there any way to get a fix for this bug in Karmic?
--
PulseAudio ALSA plugin opens and closes the PulseAudio sink when recovering
from underrun
https://bugs.launchpad.net/bugs/503174
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FWIW, there's a related bug (#539932) in Karmic Backports: Please
backport libasound2-plugins (source alsa-plugins).
--
PulseAudio ALSA plugin opens and closes the PulseAudio sink when recovering
from underrun
https://bugs.launchpad.net/bugs/503174
You received this bug notification because you
I still say that placement of the buttons on the left is wrong.
But if you absolutely insist on doing this, there needs to be a user-
visible option in the preferences GUI to allow someone to reposition the
buttons via a check-box. Expecting people to launch gconf-editor from
the Run Application
Also happening to me on a Dell Latitude D620. The wifi sometimes works
-- but if I disable it with the switch on the side of the machine (e.g.,
if I'm on a hard-wired network connection and don't want to go
wireless), it won't come back if I use the switch to reenable it -- even
if I
I, too, had a similar problem (with nvidia-glx-195 on a Karmic box), and
the problem cleared up after I installed linux-headers-generic-pae. I'm
now successfully running 2.6.31-16-generic-pae and nvidia-glx-195 and
seeing all 4 GB of RAM in my system.
--
Nvidia fail with DKMS on
Gfax.exe is crashing with a SIGSEGV for me on a 9.10 system.
--
gfax.exe crashed with SIGSEGV on exit
https://bugs.launchpad.net/bugs/217707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The vowel-pointed Hebrew text in the Keturah and Mezuzah articles in
the English Wikipedia look OK using Firefox 3.5.5 on Ubuntu 9.10.
--
Default Hebrew fonts in Firefox are unreadable, ugly
https://bugs.launchpad.net/bugs/23267
You received this bug notification because you are a member of
Minor correction: I did see one small flaw in the pointing of the word
קִדְּשַׁנוּ (kideshanu = sanctified us) in the Mezuzah article
(http://en.wikipedia.org/wiki/Mezuzah) -- the schwa under the daled is
shifted to the right (instead of being directly lined up with the
vertical stroke). This
Regarding RAID devices, I noticed just now that the /dev/md_dX names
don't even exist any more on my system. They were definitely there
before I upgraded from Jaunty to Karmic over the weekend.
See the DEVICE NAMES section of mdadm(8) for evidence that device file
names of the form /dev/md_dNN
The /dev/md_dNN series of device names are mentioned near the end of the
mdadm(8) man-page, in the DEVICE NAMES section.
As it turns out, these devices aren't there now -- but they did exist on
my server before I upgraded it from Jaunty to Karmic. (You'll just have
to take my word for this -- I
I think I may have found the solution (or, at least, a workaround). I
replaced all instances of device names of the form /dev/md_dX with
corresponding names of the form /dev/mdX (e.g., /dev/md_d1 - /dev/md1).
This involved editing /boot/grub/menu.lst, /etc/mdadm/mdadm.conf, and
/etc/fstab, and
A similar fix might be needed to allow booting of a system with RAID
devices identified by names of the form /dev/md_dX (instead of
/dev/mdX). See bug #486361.
--
lvm volumes fail to mount when specified as /dev/vg-name/volume
https://bugs.launchpad.net/bugs/430542
You received this bug
Public bug reported:
Binary package hint: mountall
I upgraded a server from Jaunty (9.04) to Karmic (9.10) last night.
After the upgrade, the server will no longer finish booting on its own.
It appears to hang forever in mountall (version 1.0), saying One or
more of the mounts listed in
My problem may not have been a 2.6.28-16 kernel problem after all. I
had another crash after going back to 2.6.28-15 (!!); then, I went into
the BIOS setup options and lowered the RAM speed, booted up with
2.6.28-16, and the machine has been running stably for the past three
days.
This doesn't
I have some more info about this bug. Apparently, it is not simply a
device *permissions* problem (as I had previously supposed). Rather,
there seems to be a device *locking* problem involving the gphoto2
volume monitor -- i.e., gvfs-gphoto2-volume-monitor is grabbing the
camera device and
I, too, have had several crashes on a 9.04 server (32-bit) running the
2.6.28-16 kernel. I've gone back to 2.6.28-15; too early so far to tell
whether this will fix the problem.
There have been other recent reports from people having crashes with
2.6.28-16; see, for example, the tail end of the
Has this bug really been fixed? I have a system running karmic, and I
just upgraded everything, and /usr/include/sys/timex.h (dated
2009-10-07, with definitions from linux/timex.h as of 2.6.30) still
does not contain a definition of MOD_NANO.
--
ntp FTBFS: error: 'MOD_NANO' undeclared
Has this bug really been fixed? I have a system running karmic, and I
just upgraded everything, and /usr/include/sys/timex.h (dated
2009-10-07, with definitions from linux/timex.h as of 2.6.30) still
does not contain a definition of MOD_NANO.
--
ntp FTBFS: error: 'MOD_NANO' undeclared
See my earlier comment #19 above. The problem appears to be a device
permissions problem; the solution is probably to update the udev
rules. Temporarily putting the user account in the root group (see my
comment #18) should confirm whether it really is a device permissions
problem or not.
--
I also managed to get rid of this problem, though it wasn't trivial.
After updating to 2.6.28-15, I edited /etc/mdadm/mdadm.conf with ARRAY
statements listing all my arrays (including the array for my root file
system). Then, I did dpkg-reconfigure initramfs-tools to recreate the
RAM disk image
The fact that changing group membership of a user account (see my
comment #18 above) sidesteps the problem suggests to me that the
preferred solution would be to add the right udev rules (in
/lib/udev/rules.d or /etc/udev/rules.d) to create the camera's USB
device with the correct group membership
I managed to work around this bug by adding user accounts to the root
group in /etc/group.
Yes, I do know this is a nasty, odiferous kludge, with so many horrible
security implications that I can't even count them, but my elderly mom
(who really doesn't understand the difference between Windows
I installed camera.app on a Jaunty system (via a command line, using
aptitude), and even after a restart, this -60 error still happens
when a camera is connected.
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You received this bug
As best I can tell, what you installed is absolutely identical to what I
installed.
Here is my output from aptitude show camera.app:
Package: camera.app
State: installed
Automatically installed: no
Version: 0.8.0-8build1
Priority: optional
Section: universe/graphics
Maintainer: Ubuntu MOTU
I updated to the just-released Firefox 3.0.11 -- and uninstalled the
Mouse Gestures Redox add-on -- and I am no longer seeing the right-click
bug.
--
[MASTER] right click (with button release) might activate random popup-menu-item
https://bugs.launchpad.net/bugs/187313
You received this bug
I assume the above is an extremely temporary workaround which won't
survive a reboot. Is the right solution going to involve adding
something to /lib/udev/rules.d/50-udev-default.rules or some other
/lib/udev/rules.d/* file?
--
Error initializing camera: -60: Could not lock the device
I think I may be having the same (or a related) problem. I'm trying to
convert a Jaunty server (2.6.28-11-server) to use RAID 1 using mdadm. I
believe mdadm is working because I have several RAID partitions which
get mounted out of /etc/fstab after the system has successfully booted.
But when I
This problem still exists in the Jaunty RC kernel (2.6.28-11-generic
#42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux).
IMHO, the default 32-bit desktop kernel should support 4GB (by enabling
PAE) -- or if enabling PAE creates inefficiencies when it's not needed,
then a separate
*** This bug is a duplicate of bug 74179 ***
https://bugs.launchpad.net/bugs/74179
I'm commenting here in case what I say might have an impact on whether
this bug is a duplicate of bug 74179 or not.
I'm running the Jaunty RC (2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17
01:57:59 UTC 2009
Again, I'm running the Jaunty RC (2.6.28-11-generic #42-Ubuntu SMP Fri
Apr 17 01:57:59 UTC 2009 i686 GNU/Linux) on a desktop with 4 GB. The
BIOS reports 4GB on startup, but /proc/meminfo says it sees only 2838352
kB (2.75 GB).
I tried the Grub patch suggested in bug 189269
** Attachment added: vmmon-compile-error.txt
http://launchpadlibrarian.net/25710419/vmmon-compile-error.txt
--
vmware 1.0.9 won't install in Jaunty
https://bugs.launchpad.net/bugs/363462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
After upgrading to 9.04 (desktop) RC, I attempted to install VMware
Server 1.0.9 (VMware-server-1.0.9-156507.tar.gz). The installation
failed while attempting to compile the required vmmon module. See the
attached output.
uname -a output for my system:
Linux liberation
Intending no disrespect here to the developers, I am less than happy
about the apparent decision not to try to fix this bug in Intrepid. It
was my understanding that Intrepid was supposed to be supported for
another year. Also, the conflicting reports regarding the nature and
extent of this bug
OK, understood. Could you remind me (and others) how to safely
uninstall your patched package and revert to the regular version of
same?
--
[intrepid] keyboard Repeat Keys is failing to adjust
https://bugs.launchpad.net/bugs/264196
You received this bug notification because you are a member of
Jeff, will your patch work on intrepid? I would really like a fix to
this problem ASAP, but I depend on my machine being stable and really
can't upgrade to jaunty while it's still pre-release.
--
[intrepid] keyboard Repeat Keys is failing to adjust
https://bugs.launchpad.net/bugs/264196
You
Thanks. I installed the patch in intrepid just now. It seems to work
fine, EXCEPT that the left and down arrow keys do not repeat AT ALL
(no matter how long I hold them down).
--
[intrepid] keyboard Repeat Keys is failing to adjust
https://bugs.launchpad.net/bugs/264196
You received this bug
And everyone should note that this issue also applies to desktops, since
most keyboards nowadays use USB (and may or may not come with one of
those purple USB-to-PS/2 keyboard adapters). Once I read here that the
problem was specifically affecting USB keyboards, I knew enough to try
using the
Gumby, the builtin keyboard on a laptop is hooked up (internally) to the
computer the same way as an external PS/2-style keyboard would be. This
explains why the workaround (with a kbdrate command) fixes your
laptop's internal keyboard.
Wolfwitch, when you say that the kbdrate workaround works
As best I can tell, this kbdrate command DOES NOT WORK AT ALL on my
system (Intrepid, 2.6.27-11-generic).
I have a Microsoft Digital Media Pro keyboard (configured in Keyboard
Preferences as a Generic 105-key (Intl) PC model), which I've tried
connecting to my desktop both via its native USB
I wasn't talking about trying to use the command to display current
values. When I said this 'kbdrate' command, I was referring
generically to the command (with an appropriate, but unspecified
argument list). And I'm not sure why kbdrate -r 4 -d 750 works for
you, because (as I said) it's not
And for reasons I can't explain, when I tried kbdrate -r 4 -d 750
again just now, it WORKED.
No idea why it worked this time, but not earlier.
--
[intrepid] keyboard Repeat Keys is failing to adjust
https://bugs.launchpad.net/bugs/264196
You received this bug notification because you are a
I'm still seeing this problem on a regular basis with Ubuntu 8.04 /
VMware 1.0.8.
I'm not able, at this time, to say whether the problem exists in 8.10 or
9.04.
--
VMware Server ignores interval before raising window on mouse-over
https://bugs.launchpad.net/bugs/201211
You received this bug
Not for me, it doesn't. I upgraded a new Hardy system to Intrepid
today, and it's started demanding Enter login password to unlock
keyring after doing an autologin. It wasn't doing that in 8.04.1
before I did the upgrade.
This new system was going to be for my mother, who is not very computer-
And the pam-keyring-tool workaround didn't work for me either. I was
still being prompted for the login password.
However, it looks like I was finally able to get rid of the unlock
keyring prompt by using pam-keyring-tool -c and entering an empty
password (just hit ENTER) for the new password.
1 - 100 of 139 matches
Mail list logo
