From cloud-init point of view the solution now implemented make sense:
to run it before the apt-daily-upgrade. However, I wanted to add that
there are other use cases as well such as SSM documents being executed
on instances. These can be executed in batch at any time and may also
require
Just tested the proposed gssproxy fix, and can confirm that it solved the issue
Tested on Ubuntu Focal (20.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788459
Title:
gssproxy crashes in
I can confirm this exact bug. I have the same machine (Thinkpad X1
Carbon 9th gen). However, I am running an up-to-date Fedora 34 system.
For me, changing the sleep mode to what the BIOS calls "Linux and
Windows" (apparently software suspend?) also fixes the problem. I have
not had a chance yet to
I can confirm that manual build and install of gssproxy 0.8.4 works on my
ubuntu 20.04 server.
(that version has the patch mentioned above)
gssproxy solves my original issue of rpc-svcgssd hanging on large
kerberos tickets https://bugs.launchpad.net/ubuntu/+source/nfs-
utils/+bug/1466654
The workaround as suggested it to use gssproxy
Unfortunately that also has a bug
https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466654
Manually compiling and installing the latest version of gssproxy did
solve the issue for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466654
Title:
kernel soft lockup on nfs server when using
gssproxy/focal,now 0.8.2-2 amd64 [installed]
libselinux1/focal,now 3.0-1build2 amd64 [installed,automatic]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788459
Title:
gssproxy crashes in
I couldn't get it to generate a coredump. But I ran it with valgrind
Hope this helps
valgrind -v /usr/sbin/gssproxy --interactive --debug --debug-level=3
--socket=/run/gssproxy.sock
==29249== Memcheck, a memory error detector
==29249== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et
** Attachment added: "/var/crash/_usr_sbin_gssproxy.0.crash"
https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+attachment/5507903/+files/_usr_sbin_gssproxy.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The reason we want gssproxy, and not the default rpc-gssd and rpc-
svcgssd services is that we are using active directory, and most of our
accounts are members of many groups, causing gssd to fail. This is a
known issue and is one of the things that gssproxy solves.
>>The reason we did this was
Trying to get gssproxy working with NFS (rpc-gssd and rpc-svcgssd) on Ubuntu
20.04
Following https://github.com/gssapi/gssproxy/blob/main/docs/NFS.md
/etc/gssproxy/gssproxy.conf
[gssproxy]
debug = true
debug_level = 3
/etc/gssproxy/25-nfs-server.conf
[service/nfs-server]
I think this bug describes the behaviour on
https://askubuntu.com/questions/1274365/windows-of-an-application-have-
minimum-size-and-i-cant-find-the-window-anymore
We have noticed that with several of our students on Ubuntu 20.04 with
LO 7.0.4.2
--
You received this bug notification because you
@robin Windey
I had no luck with kernel 5.10.2, try 5.9.16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
To manage
Touchpad works without workaround on
Ubuntu 20.04 with Kernel 5.9.16
Same goes for ubuntu 20.10.
Easiest way is to use the workaround, install mainline(alternative for ukuu)
install kernel 5.9.16
Reboot and relax
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Ubuntu 20.10 with kernel :
Linux legion5 5.9.16-050916-generic #202012211331 SMP Mon Dec 21 14:11:13 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
Touchpad works without any work around
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Installed ubuntu 20.10 on ARH05, the gpio workaround makes the mouse work.
Left click and right click button works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not
** Description changed:
MySQL on 20.04 has TimeoutSec set to 600 (IIRC) in the systemd script.
This has the effect of killing the MySQL process if this timeout is
reached.
IMHO this is a Very Bad Idea. A database server process should only be
force killed by a user action.
I
I'm unassigning myself as I'm not sure what the next steps are but I
believe it should be corrected by ubuntu taking the latest debian
version of the package (i.e. mysql-8.0 (8.0.22-1)) -> no ubuntu-patch
needed
** Changed in: mysql-8.0 (Ubuntu)
Assignee: Koen (koen-beek) => (unas
hmm when doing a
git clone https://salsa.debian.org/mariadb-team/mysql.git -b
mysql-8.0/debian/master
it seems it has been fixed by putting infinity to TimeoutSec (I suppose
that's the same as 0) in Debian
mysql/debian/mysql-server-8.0.mysql.service:TimeoutSec=infinity
-> seems to have been
There does not seem to be an equivalent debian bug about this issue yet
will make a patch in ubuntu and forward it to debian :
https://wiki.ubuntu.com/Debian/Bugs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(consistent with RHEL) to prevent this from happening.
--
the latest ubuntu code (based on 8.0.22) contains following mentions of
TimeoutSec
koen@hpubuntu:~/Dev/personal/ubuntu/mysql$ grep -rR TimeoutSec *
mysql-8.0-8.0.22/packaging/deb-in/mysql-packagesource-server.mysql.service.in:TimeoutSec=0
subscribed ubuntu sponsors team following this process
https://wiki.ubuntu.com/SponsorshipProcess
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900318
Title:
compliments/complements typo in
** Changed in: update-motd (Ubuntu)
Assignee: Koen (koen-beek) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900318
Title:
compliments/complements typo in package descript
Fix type in debian/control file for package description : compliments ->
complements
My first patch in a long time - beware
I followed this workflow :
https://packaging.ubuntu.com/html/fixing-a-bug.html
i.e.
- pull-lp-source update-motd hirsute
- cd update-motd-3.6/
- change control text file
I can't find "compliments" in the source package
koen@hpubuntu:~/Dev/personal/ubuntu/update-motd-3.6$ grep -irR compli *
COPYING:for enforcing compliance by third parties with this License.
I can only find the text on this page :
https://launchpad.net/ubuntu/+source/update-motd
N
nts pam_motd in libpam-modules
I can take it as my first packaging try
** Changed in: update-motd (Ubuntu)
Assignee: (unassigned) => Koen (koen-beek)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
also crashes in development release 21.10
root@koen-VirtualBox:/var/crash# ls -lrt
total 416
-rw-r- 1 root whoopsie 425471 Dez 15 18:08 _usr_bin_aide.0.crash
root@koen-VirtualBox:/var/crash# sudo dmesg | tail -n5
[ 90.657264] rfkill: input handler disabled
[ 1493.234716] aide[21779
doesn't seem like a bug to me - it works as expected
** Changed in: update-motd (Ubuntu)
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789850
Title:
error confirmed by other user : https://askubuntu.com/questions/1296526
/segmentation-fault-core-dumped-aide-init-return-code-139
** Changed in: aide (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
When installing ubuntu (20.04 and later (earlier also probably))selecting
- english (US) language
- Brussels-Belgian timezone
ubuntu selects de_BE as locale which is teh Belgian German-language
locale
in Belgium about 60% are dutch-speaking (nl_BE) and
Public bug reported:
When installing ubuntu (20.04 and later (earlier also probably))selecting
- english (US) language
- Brussels-Belgian timezone
ubuntu selects de_BE as locale which is teh Belgian German-language
locale
in Belgium about 60% are dutch-speaking (nl_BE) and 40% are french
Public bug reported:
ww
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp
Public bug reported:
I found kile missing nearly all icons in the interface (open, save,
undo, redo, ...). Also the application Icon was corrupt in the launcher.
Solutions:
apt install qt5-gtk-platformtheme:amd64 fixed the missing icons in the interface
echo 'StartupWMClass=kile' >>
I see this same behaviour regularly on systems running 18.04 as well.
Running sudo apt update makes the update process resume - no errors shown.
Without doing that the system reports that it is up to date and it
isn't, making it unsafe.
Non techy users freak out on using a command line command.
Public bug reported:
Stopped at installation.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
Tried it, no change
drwxr-xr-x 74 root root 0 Jan 31 19:00 ..
lrwxrwxrwx 1 root root 0 Jan 31 19:00 asus::lightbar ->
../../devices/platform/asus-nb-wmi/leds/asus::lightbar
lrwxrwxrwx 1 root root 0 Jan 31 19:03 asus-wireless::airplane ->
It is a fresh install never tried an older version.
I have tried the new kernel, same issue.
The asus-nb-wmi module is loaded but seems not to support this keyboard.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a
Fedora 29, same thing. Doesn't start in graphic mode. The only version that
seems to work is Linux Mint 19 at the moment.
I've added an output of inxi:
System:Host: GM501GM Kernel: 4.15.0-20-generic x86_64 bits: 64 Desktop:
Cinnamon 3.8.9
Distro: Linux Mint 19 Tara
Machine:
Ubuntu 18.10 does not work on this laptop, at least not the live version. It
blocks on the GPU.
In linux mint it works smooth, apart from the keyboard backlight.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ubuntu 18.10 does not work on this laptop, at least not the live version. It
blocks on the GPU.
In linux mint it works smooth, apart from the keyboard backlight.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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/1802652
Title:
keyboard backlight not working on Asus GM501
To manage
Public bug reported:
The keyboard lights and most of the F keys aren't working.
Kernel = 4.15.0-20-generic
System linux mint 19
ls -hal /sys/class/leds/
total 0
drwxr-xr-x 2 root root 0 Nov 10 15:47 .
drwxr-xr-x 72 root root 0 Nov 10 15:43 ..
lrwxrwxrwx 1 root root 0 Nov 10 15:43
lspci | grep -i VGA
00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c8d (rev a1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm having this issue on ubuntu conntecting my externel display using
displaylink (only when rotated)
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename: xenial
--
You received this bug notification because you are a
For me the update was also successful. Went from bios version 1.7.5 to
1.8.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730343
Title:
firmware update breaks Ubuntu
To manage notifications
Hello all,
I just tried the proposed package on 16.04 and it failed.
I took this picture with my phone:
https://www.dropbox.com/s/6r6zeadqakbtjg5/2018-01-04%2023.35.59-1.jpg?dl=0
After that screen it just continued with a regular boot.
** Tags removed: verification-needed-xenial
** Tags added:
I discovered the root cause of the issue by comparing the output of `pip
freeze` on both servers.
Apparently on the upgraded server cryptography-1.9 was installed in
`/usr/local/python2.7/dist-packages`, while overriding python-
cryptography package.
Running `sudo pip uninstall cryptography`
I experience the same issue after upgrading from 14.04.5 to 16.04.3.
Other server where 16.04.3 has been installed from fresh doesn't have
the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello, it was requested I also leave a comment here. Yesterday I
experienced this issue on Ubuntu 16.04 LTS.
I then found this github ticket:
https://github.com/rhboot/fwupdate/issues/86
Which had a workaround that got my machine working again.
I was told that "The Ubuntu archive admin needs
Same on a Dell latitude 5580 with Intel Corporation Device 24fd (rev 78)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653324
Title:
No wireless networks visible on resume from suspend. Erroneous
This seemed to be solved by some kernel upgrade.
4.10.0-35-generic #39~16.04.1-Ubuntu SMP Wed Sep 13 09:02:42 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
runs fine.
** Changed in: linux-hwe (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member
I see the same behavior as mikewiz38: via a webtest 104 Mbps download and in
the graphical interface it lists as 6Mbps.
So speed is not bad - it just looks bad (on 16.04.1 with hwe kernel 4.8.0-53)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
same here:
koenr@koenr-Latitude-5580:~$ lspci |grep -i network
02:00.0 Network controller: Intel Corporation Device 24fd (rev 78)
koenr@koenr-Latitude-5580:~$ nmcli --version
nmcli tool, versie 1.2.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Upgraded bios to Version: 1.4.3 without improvement
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694022
Title:
Dell Latitude 5580 trackpoint not working after suspend
To manage notifications
koenr@koenr-Latitude-5580:~$ xinput --list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ DLL07A8:01 044E:120B id=11 [slave pointer (2)]
⎜ ↳ DualPoint Stick
xinput --list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ DualPoint Stick id=11 [slave pointer (2)]
⎜ ↳ DLL07A8:01 044E:120B
Public bug reported:
After a fresh boot, the track point or dual point stick is working and so does
the left, right and middle button for it.
After suspend and resume, none of the above work anymore. The touchpad and
accompanied left and right button are not affected and work always perfectly.
Same on Xenial after upgrade from Trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515308
Title:
Buttons on control bar/panel are not visible
To manage notifications about this bug go to:
Purged and reinstalled: no improvement
ardesia -V
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Enabled Device in screen 2. 0x1ea3ab0: "Virtual core pointer" (Type: 0)
DEBUG: Annotation window get screen-changed event
DEBUG: Annotation window get configure event
Maybe I should have specified 'stops working' some more; in order to get
touch scroll functionality we added the touch-devices flag.
This works fine, but is this expected behavior? (Is this flag usually
required for touch scroll?)
When any USB device is then (un-)plugged the flag will stop
Public bug reported:
When using the --touch-devices= flag to enable touch support
in Chromium (or Chrome) the removal or insertion of a USB device (which
does not cause the ID of the touch device to change) causes the
functionality (finger-scrolling) to stop working until the browser/app
is
In comment #8 it's mentioned that it is not fixed in 4.4.0-22. I hope that's a
typo :-(
I have a crashing 4.4.0-21 (Thinkpad 13 with an Intel N3150 processor / HD 510
Graphics)
My workaround is installing kernel 4.6RC6
--
You received this bug notification because you are a member of Ubuntu
Importance: Undecided?!
Assigned to: Unassigned?!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572494
Title:
(xenial) installation of kde-l10n-nl ruins plasma
To manage notifications about this
I can confirm Zanna's solution for the Acer B115
apt-get install linux-image-generic-lts-xenial
linux-headers-generic-lts-xenial, resulting in kernel 4.4.0-15-generic solved
the problem.
So the 4.4.0.-13.7 and 3.19.0-56 are not ok, the 4.4.0-15-generic #31~14.04.1
is ok
--
You received this
The bug was reported for 1.4.18.
I upgraded to Ubuntu 14.04 which ships with 1.4.22 and that version
works.
Thank you for your reply. I suppose version 1.4.18 is not relevant
anymore, but I can't find a button how to close this bug :-(
--
You received this bug notification because you are a
Public bug reported:
with a dist-upgrade 14.04 upgraded from kernel 3.19.56 over 4.2.36 to
4.4.0 Both in 4.2 and in 4.4 the touchpad is not working.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-generic-lts-xenial 4.4.0.13.7
ProcVersionSignature: Ubuntu 4.4.0-13.29~14.04.1-generic
We have seen the problem now with 3 of our students , all using Acer
Travelmate B115. 2 running Ubuntu 14.04, one running Elementary OS.
** Also affects: linux-meta-lts-trusty (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
I'm wrong.
3.19.0-51 is the last version I found where the touchpad works.
All higher versions (including 3.19.0-56) are not ok
Touchpad is SYN1B7D:01 06CB:2991 and SYN1B7D:01 06CB:74D9
I don't know where the second type number comes from. The devices are Acer
B115. Acer has upgraded the
Just tested it & works for me now! Thanks!
I ran:
```
sudo unity8-lxc-setup --destroy
sudo unity8-lxc-setup
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477720
Title:
Unity8 won't install
I am affected as well. I'm on Xubuntu 14.04LTS and I use the
nvidia346.82 proprietary driver. I had tearing issues with my new
NVIDIA card. To resolve it I added the following line to
/etc/X11/xorg.conf :
Option metamodes nvidia-auto-select +0 +0 {
ForceFullCompositionPipeline = On }
The
Public bug reported:
Title says it all. Sample file below would be perfectly valid:
# Secrets for authentication using CHAP
# clientserver secret IP addresses
koen* Jekeke543 *
However, in my daily password, I use a #. So the chap-secret below gives
Public bug reported:
Title says it all. Sample file below would be perfectly valid:
# Secrets for authentication using CHAP
# clientserver secret IP addresses
koen* Jekeke543 *
However, in my daily password, I use a #. So the chap-secret below gives
apport information
** Tags added: apport-collected precise running-unity
** Description changed:
A vasco 870 reader is not recognised. It is supposed to work:
http://pcsclite.alioth.debian.org/ccid/shouldwork.html#0x1A440x0870
It is recognised on the USB-bus.
I purged and
Public bug reported:
A vasco 870 reader is not recognised. It is supposed to work:
http://pcsclite.alioth.debian.org/ccid/shouldwork.html#0x1A440x0870
It is recognised on the USB-bus.
I purged and reïnstalled pcsc-tools. I got another reader working
(cherry)
lsusb
Bus 001 Device 002: ID
I added
xinput --set-prop SYN1B7D:01 06CB:2991 UNKNOWN Synaptics ClickPad 1
xinput --set-prop SYN1B7D:01 06CB:2991 UNKNOWN Synaptics Middle Button
Timeout 0
xinput --set-prop SYN1B7D:01 06CB:2991 UNKNOWN Synaptics Soft Button Areas
734 0 561 0 0 0 0 0
to /etc/X11/Xsession.d/95synaptic (see
This is still not fixed in 14.04!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/373680
Title:
network-manager fails periodically , on backgound networks scan?
To manage notifications about this
I didn't hear anything from Tim Gardner.
What a shame - the fix is here and hundreds of users get a bad user
experience using Ubuntu, with a constantly locking laptop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
neat confirmation - it's 2015, and this bug is from 1995. Seemingly no-
one has had a need for a serial line in the last two decades :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094278
Title:
neat confirmation - it's 2015, and this bug is from 1995. Seemingly no-
one has had a need for a serial line in the last two decades :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to uucp in Ubuntu.
No, I don't know the ways to get it upstream. Suppose I could send a
message to Tim Gardner.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1369684
Title:
Elantech touchpad locks cursor when
I can confirm that this driver solves the problem.
The problem is reduced to the problem that exists in the Windows driver (being
locking for 2 seconds in stead of locking for very long or forever when
touching the touch pad with more then one finger)
--
You received this bug notification
Thanks a lot for this! I don't have a device with me to test, so I'll test it
next week. I did a diff with the current elantech file for 3.13 and there are
so many differences. It's for me not possible to tell which one solves the
problem. I think it is based on an older version of the file.
I
Hi ftoledo, did you make any progress with the elantech driver?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1369684
Title:
Elantech touchpad locks cursor when touching with 2 or more fingers
To
I ran do-release-upgrade -s on a server with software raid ; it failed
and when I agreed to send in an error report, I was pointed to this bug
as we already know about this problem. Just came here to confirm it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I can confirm the behavior in Windows. The pointer works fine, but if you touch
it with two fingers, it somewhat hangs for 1 or 2 seconds and then moves on.
It's not really disturbing. No multitouch working, but
Anyway, it's not relevant what it does in Windows. The complete locking of the
For our machines, there is no bios update published by the manufacturer
yet (don't know where else to look).
I would assume that if a device loads different firmware, it is a
different device, no?.
comparing bios versions:
our bios version
MPBYT10A.90A.0029.2014.0421.1908 with dmi.bios.date:
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1372496/+attachment/4211540/+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/1372496
Title:
Can't
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1372496/+attachment/4211543/+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/1372496
Title:
apport information
** Attachment added: NetDevice.eth0.txt
https://bugs.launchpad.net/bugs/1372496/+attachment/4211544/+files/NetDevice.eth0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: NetDevice.wlan0.txt
https://bugs.launchpad.net/bugs/1372496/+attachment/4211546/+files/NetDevice.wlan0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: IpAddr.txt
https://bugs.launchpad.net/bugs/1372496/+attachment/4211542/+files/IpAddr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372496
Title:
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1372496/+attachment/4211541/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372496
Public bug reported:
5Ghz is possible in ad-hoc mode, not in infrastructure mode (option to
select band is not offered)
tested with kernel
3.13.0-34 - firmware 22.24.8.0
3.13.0-35 - firmware 22.24.8.0
3.17.0-999 (8 september 2014) - firmware 23.214.9.0
Very occacionally there is made a
apport information
** Attachment added: NetDevice.lo.txt
https://bugs.launchpad.net/bugs/1372496/+attachment/4211545/+files/NetDevice.lo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372496
apport information
** Attachment added: NetworkManager.conf.txt
https://bugs.launchpad.net/bugs/1372496/+attachment/4211547/+files/NetworkManager.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: PciNetwork.txt
https://bugs.launchpad.net/bugs/1372496/+attachment/4211548/+files/PciNetwork.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372496
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1372496/+attachment/4211549/+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/1372496
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1372496/+attachment/4211550/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372496
Public bug reported:
Running Ubuntu 14.04.1, Unity desktop, kernel 3.13.0-35 generic on Intel
Classmate, MG Pupil 109
The touchpad is identified in dmesg as
[1.539535] mousedev: PS/2 mouse device common for all mice
[2.528608] psmouse serio4: elantech: assuming hardware version 3 (with
The problem is exactly the same with the mainline kernel (3.17-rc5)
** 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/1369684
Title:
1 - 100 of 1265 matches
Mail list logo
