I tried Fedora 35, and found the exact same behaviour (ie the boot
program recognises the keyboard, but the final linux image does not).
Jon Thackray
j...@pobox.com
0044 1223 276500 (home)
0044 7803 017991 (mobile)
0033 423354068 (France)
-- Original Message --
From: "Jon Tha
* log2 (180) hours, ie about 4 hours.
Jon Thackray
j...@pobox.com
0044 1223 276500 (home)
0044 7803 017991 (mobile)
0033 423354068 (France)
-- Original Message --
From: "Daniel van Vugt" <1930...@bugs.launchpad.net>
To: j...@pobox.com
Sent: 22/04/2022 03:00:03
Subject:
time next year, there will be no Ubuntu (or Debian I think,
given that Rapsbian doesn't work with the KVM either) distribution I can
use, as at that point 18.04 will be end of support. I shall then start
having to try and learn other distros to see if any of them have
fixed/failed to create
I don't have a "Unifying receiver". That's just the name which appears
and/or disappears when I plug in the KVM to the PC. The KVM in all cases
is directly connected to the keyboard/mouse/screen at one end, and USB
ports/HDMI at the PC end.
-- Original Message --
From: "Hui Wang" <1930.
Neither. I tested all the distros on an old machine I have which
currently runs windows 10. The distros were tested by putting the
installation on a DVD and booting from it. Here's what windows claims it
has
Device namefeit
ProcessorIntel(R) Core(TM) i7-2700K CPU @ 3.50GHz 3.50 GHz
In
Public bug reported:
I have recently acquired a acquired a desktop running ubuntu 20.04. I
have several computers and switch between them using this KVM
https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
The other machines are either running windows or u
Public bug reported:
>From a fresh installation of qmail I find
jon@frobenius:/etc/qmail/qmail-send$ ls -l supervise
lrwxrwxrwx 1 root root 29 May 21 20:17 supervise ->
/var/lib/supervise/qmail-send
jon@frobenius:/etc/qmail/qmail-send$ ls -l /var/lib/qmail/supervise/
total 12
lrwxrwxrwx 1 root
Public bug reported:
Multiple identities can be used for authentication:
1. user,,, (user)
2. Jon Thackray,,, (jon)
Choose identity to authenticate as (1-2): 2
Password:
polkit-agent-helper-1: pam_authenticate failed: Authentication failure
AUTHENTICATION FAILED ===
Error executing
I've now tried the 4.8 kernel as suggested. It booted into busybox at
initramfs, so I was unable to determine anything useful about it. I also
tried the latest 4.9 kernel. That booted, but produced continuous beeps
from the loudspeaker and neither the keyboard nor the point worked.
--
You receive
In the standard 3.13 kernels for 14.04 the touchpad wasn't supported at all.
Therefore it worked, but it was impossible to turn off its most irritating
feature which was tap to click. Most implementations at least give the
option to disable this when typing, but the default generic implementatio
Public bug reported:
First, the collected kernel version is wrong. I'm running
4.4.0-36-generic, but inside ubuntu 14.04. Anyway, the touchpad refuses
to act as a pointer mover. It will, if I let it, do tap to click (which
is the last thing I want). But, as things stand, I'm forced to use the
litt
Public bug reported:
I installed the vivd lts upgrade in order to obtain a kernel which
recognised the touchpad on my Toshiba laptop. The kernel now installs
the ALPS driver, but the touchpad is now unusable. Normal light touch
movement is simply not recognised at all. Pressing harder will get the
OK, I think I may understand why this happens. When a new user is
created, the first time emacs is run it creates .emacs.d in the user's
home directory. But, if the first time the user runs emacs is via sudo,
which is more than likely if he is configuring a system, then the
ownership on .emacs.d en
Having told it to completely remove and reinstall I can now work around
this. But I am no closer to identifying why it happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349087
Title:
emacs C-x
This has now happened to me a second time. This time I was setting up a
toshiba laptop. In the mean time I managed to set up a desktop where the
problem did not occur. So that's a 67% failure rate, down from 100%, but
now in a sample of 3.
--
You received this bug notification because you are a m
So, looking on 10.04, I find C-h v image-load-path says
image-load-path's value is
("/usr/share/emacs/23.1/etc/images/" data-directory load-path)
So, I now try on my pristine 14.04 and I find the value to be void.
Looking in /usr/share/emacs/23.1/etc/images/ I find it's a load of .xpm
files, and
says no match, which seems
to be similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465748).
Have you any suggestions as to how I can debug this? I'm not an emacs lisp
person, but if necessary I can find someone who is.
Jon Thackray
+44 1223 276500 (new)
+44 7803 017991
+33 952837
Public bug reported:
C-x m is supposed to open a *mail* window in which I can type an email
and send it. Instead, all I get is a message "Symbol's value as variable
is void: image-load-path This is a brand new install of 14.04 and new
emacs. Previous installs on earlier releases, eg 10.04, have wo
I seem to remember finding a way around it. I think the problem was that if
the system had once decided that a network was using WEP, you could never
change its min.d But I can't remember any more details. I suggest you close
this as I doubt I can reproduce it.
- Original Message -
Fro
I am able to reproduce this consistently without touching the trackpad.
All you seem to need is several login name possibilities. Click on the
top one, and the cursor appears in the password field but the pointer is
still elsewhere. Start typing the password and observe that part way
through the fo
Digging deeper, it appears that this only affects the case of trying to
connect to an existing network which has changed its security mechanism,
eg by upgrading from WEP to WPA. Attemptong to access a never before
seen network with WPA or WPA2 security works fine.
Given that NetworkManager knows w
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42903620/Dependencies.txt
** Attachment added: "Gconf.txt"
http://launchpadlibrarian.net/42903621/Gconf.txt
** Attachment added: "IfupdownConfig.txt"
http://launchpadlibrarian.net/42903622/IfupdownConfig.txt
** Attac
Public bug reported:
Binary package hint: network-manager
I have been trying to get an ASUS 1000H to connect to WPA protected
wireless networks, under UNR. I was originally using Jaunty, but though
this detects that a network requires WPA, it fails to connect. I
upgraded to karmic when it became
23 matches
Mail list logo