** Changed in: udev (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410022
Title:
Touchpad cannot work after LID close/open due to wrong key mapping
To manage
Public bug reported:
I installed Ubutnu 16.04 LTS on my HP 705 G2 all-in-one machine. It is
an AMD kaveri graphic based platform. After installation is done my
screen is dark (but still can see something on it so I can file this
bug). The brightness is malfunction.
ProblemType: Bug
@Mathieu,
Thanks for your patch, I just found the same root cause as your. The
mobile_helper_get_icon does not return icon file name and result in 'nm-
no-connection' is always used on indicator menu:
#ifdef WITH_APPINDICATOR
if (INDICATOR_ENABLED (applet)) {
/* FIXME: We
Public bug reported:
I have a DELL WWAN module (DW5580) on my platform. Normally it could be
detect and used in Ubuntu 16.04 daily image. However it is sometimes
unusable and can not be detected.
After debugging, we found there is an upstream patch that can fix the
issue:
Public bug reported:
In previous Ubuntu release, I am able to switch to console/ttys while
installing the system. However it is impossible to switch console/ttys
on 16.04 daily images.
Steps to reproduce the issue:
1) Choose 'Install Ubuntu' option in DVD boot menu.
2) After Ubiquity brings up,
I have some problem on my platform.
I can connect to another PC without problems, however when I press the 'Browse
file' it has no response.
By the away. I can get file list by using obexftp -b -c /
-l, and download file with obexftp option.
--
You received this bug notification because you
If we skip 'oem-config-remove-gtk', then process could be finished and
desktop can be started.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1552621
Title:
Can't login to desktop autometically
Public bug reported:
Can't play video correctly.
Run command:
gst-launch-1.0 playbin uri=file:///usr/share/example-
content/Ubuntu_Free_Culture_Showcase/How fast.ogg video-
sink=autocluttersink
will show green rectangle.
Similar bug can be found here:
** Project changed: ubiquity => ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1552621
Title:
Can't login to desktop autometically after oem-config is finished on
OEM mode
To
** Also affects: ubiquity
Importance: Undecided
Status: New
** Package changed: ubiquity (Ubuntu) => oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1552621
Title:
Can't login
Public bug reported:
Normally system should be able to switch to login screen after oem-
config is finished. However on OEM mode the system stops with black
screen after oem-config is finished.
This bug can be reproduced on Xenial daily image.
Steps:
1) Boot into OEM mode (EFI) and install the
@Adam
Install unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu3 on my ASUS
P452L platform, this issue is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454950
Title:
It needs to press
Update:
Install unity-settings-daemon 15.04.1+15.04.20150408-0ubuntu1.1 on ASUS
P452L platform, this issue is fixed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Sebastien,
Thanks for your help, I will watch -propose for the update :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454950
Title:
It needs to press touchpad hotkey twice to re-enable
Hi Lars,
I built packages from your branch and tested them on the target
platform. The issue has been fixed.
Would you please back port it to 14.04 trusty (I tested it on 15.10
wily)?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Sebastien
I reply my comment on the same issue of:
https://bugzilla.gnome.org/show_bug.cgi?id=741523
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454950
Title:
It needs to press touchpad hotkey
I compiled gnome-settings-daemon 3.17.1 (from github) on 15.04 wily and
run gsd-test-mouse on the platform, the issue still exists. The gsd-
testmouse log file is attached.
** Attachment added: gsd-test-mouse.log
By the way, this issue can be reproduced on 15.04 Wily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454950
Title:
It needs to press touchpad hotkey twice to re-enable touchpad
To manage
@Sebastien,
I check with the latest gnome-settings-daemon 3.17.1 from github, the
ensure_touchpad_active functions is completely rewritten,
static void
ensure_touchpad_active (GsdMouseManager *manager)
{
GList *devices, *l;
gboolean state;
state = get_touchpad_enabled
@Ara
1) I haven't tried it on Wily, but I checked the u-s-d source in Wily. Because
ensure_touchpad_active is still exists and does not have any change, I think
this issue can be reproduced.
2) Currently I only have ASUS machine that has touchpad disabled key.
Besides, it there has a second
I add some debug message in unity-settings-daemon/plugins/mouse module, and run
tests.
Here are my founds:
1-a) Press Fn+F9, function touchpad_callback disables the touchpad.
1-b) However after touchpad is disabled, device_removed_cb is invoked, and it
then calls ensure_touchpad_active.
1-c)
Public bug reported:
I have a laptop: ASUS P452L and it has a hotkey (Fn+F9) to disable touchpad
function.
I found when I use the hotkey to disable the touchpat and then I have to press
the hotkey
twice to re-enable it.
This is symptom cannot be found if:
1) using Kubuntu.
2) plug the usb
@Rober,
I think they are different.
I found there is a solution that can fix the issue.
https://wiki.archlinux.org/index.php/Touchpad_Synaptics#Xorg.log.0_shows_SynPS.2F2_Synaptics_touchpad_can_not_grab_event_device.2C_errno.3D16
I have add GrabEventDevice=0 option to xorg.conf and it works
Unity 7.2.4+14.04.20141217-0ubuntu1 is now available on trusty-update,
after some tests I confirmed this issue has been fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1398287
Title:
Unity
Public bug reported:
The touchpad cannot working after LID close/open on HP Presario CQ45
machines.
The reproduce steps:
1) Boot into Ubuntu 14.04
2) Close LID
3) Open LID
Result: The mouse cursor cannot move.
I also found if I do close/open LID again, the mouse cursor can works
again.
After
** Changed in: oem-priority
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1399096
Title:
Touchpad lost function after switch from guest to user account
To manage
@Andrea
Thanks for your help and patch.
@janitor
Will this package be available on -trusty ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1398287
Title:
Unity 14.04 Lock button sometimes takes
Public bug reported:
Reproduce steps:
1) Change account to guest by click guest account on the menu.
2) Change account to user again
3) Touchpad lost its function.
When the touchpad becomes malfunction, there are some messages in
/var/log/Xorg.0.log
[ 282.908] (WW) synaptics: SynPS/2
@Dimitri
Sorry for no response such a long time.
Q: Why do you require USB key removal ahead of interacting with GUI
restart dialog?
We can not expect when user removes the USB key. In this case, user
removes the USB key before pressing the 'restart' button and result in
fails. Can we have a
I have installed and verified the intel-gpu-tools 1.3-0ubuntu2.1 on
target machine, the issue is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316454
Title:
intel_reg_dumper crashed with
@Timo
Will it be back ported to trusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316454
Title:
intel_reg_dumper crashed with SIGABRT in __libc_start_main()
To manage notifications about
Public bug reported:
Machine: HP Probook
Webcam: HP HD Webcam
OS Ver. Ubuntu 14.04 LTS
Architecture: amd64
Symptom:
The HP Probook has an HP HD Webcam and it supports various resolutions. Most of
them work fine, however, 960x540 has black preview and there is an error
message: Ther was an
** Description changed:
The intel_reg_dumper raise SIGABRT on Intel ValleyView Gen7 [8086:0f31]
platform.
# sudo intel_reg_dumper
Gen2/3 Ranges are not supported. Please use unsafe access. (Core dump)
+
+ OS version: Ubuntu 14.04 LTS (Trusty)
** Description changed:
The
** Description changed:
+ An error dialog will be shown after user login to the desktop environment.
+ The error is :
+
The intel_reg_dumper raise SIGABRT on Intel ValleyView Gen7 [8086:0f31]
platform.
+
+ This issue can be reproduced by running the command:
# sudo intel_reg_dumper
Attach error dialog snapshot.
** Attachment added: intel_reg_dump_error_message.jpg
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1316454/+attachment/4112042/+files/intel_reg_dump_error_message.jpg
--
You received this bug notification because you are a member of Ubuntu
** Changed in: oem-priority
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316454
Title:
intel_reg_dumper crashed with SIGABRT in __libc_start_main()
To manage
The intel_reg_dump of intel-gpu-tools v1.6 works fine.
** Also affects: xserver-xorg-video-intel
Importance: Undecided
Status: New
** Project changed: xserver-xorg-video-intel = oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
The intel_reg_dumper raise SIGABRT on Intel ValleyView Gen7 [8086:0f31]
platform.
# sudo intel_reg_dumper
Gen2/3 Ranges are not supported. Please use unsafe access. (Core dump)
** Affects: oem-priority
Importance: Undecided
Status: New
** Affects:
Public bug reported:
System can't restart if user removes usb key and press restart after
installation is done.
Step:
1) Install Ubuntu from USB key
2) Installation is done and Installation is complete. You need to start the
computer in order to use the new installation. has shown.
3) Remove
Attach syslog for client and server side.
The wpa_supplication debug output (-ddd option) is enabled.
** Attachment added: syslog.wpa.tgz
https://bugs.launchpad.net/oem-priority/+bug/1032433/+attachment/4029646/+files/syslog.wpa.tgz
--
You received this bug notification because you are a
syslog of comment #21
** Attachment added: syslog.wpa.client.trusty
https://bugs.launchpad.net/oem-priority/+bug/1032433/+attachment/4030075/+files/syslog.wpa.client.trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The same issue can be reproduced on Trusty (14.04)
The attachment is the syslog on same platform but is installed with
trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
Title:
Using
Public bug reported:
There might be race condition between plymouth-splash and plymouth-stop.
Normally the calling sequence should be:
plymouth
...
plymouth-splash
...
plymouth-stop
On the fail unit it looks like:
plymouth
...
plymouth-stop
...
plymouth-splash
Therefore the splash screen can't
Attach logs.
Config WiFi adhoc network and set WEP key to 1234567890abc.
The connection can't be established.
Logs are attached (server/client side dmesg output and syslog)
** Attachment added: wifi_adhoc_log.tgz
Hi Colin,
I have verified ubiquity 2.10.28 on my platform and the issue cannot be
reproduced any more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197766
Title:
Different partition layout after
Hi Stéphane Graber,
I saw your words but I found the partman-auto in ubiquity-2.10.26 is
still 101ubuntu2, not 101ubuntu2.2. Has 101ubuntu2 integrated to
ubiquity?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Colin
I hace verified the patch , and the partition layout now looks the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197766
Title:
Different partition layout after recovery with keep
The passed BIOS versions are 203 and 207.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1187233
Title:
Grub2 fails on ASUS X201E with secure boot is enabled
To manage notifications about this bug
@Steve
I tested saucy 20130912 build on ASUS X200CA with secure boot enabled.
Now ubuntu can be successfully boot and install on this platform.
The grub version is 2.00-18ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We have the same problem on the platfrom runs with Ubuntu 12.04.2 with
quantal backported.
I reviewed the raring patch from
https://launchpad.net/ubuntu/+source/xorg-server/2:1.13.2-0ubuntu3 and tried to
backport it to 12.04.2.
It looks work fine on our platfrom.
** Patch added:
@James,
Update log files.
I use '1234567890abc' as wep key, here are the fail logs of client/server both
sides.
Note, I aslo tested the key in hex format ( 31323334353637383930616263 ), it
failed too. The logs are attached.
--
You received this bug notification because you are a member of
Test environment:
HP laptop runs ubuntu-12.04.2 as client side
ASUS laptop runs ubuntu-12.04.2 as server side.
Set password 12345 in the server side and then use client to connect the server.
If the security type is set to WEP40/128 bit Key, the result is success ( see
attach disk-recipe and all preseed config files.
** Attachment added: preseed-recipes.tgz
https://bugs.launchpad.net/oem-priority/+bug/1197766/+attachment/3753949/+files/preseed-recipes.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I used similar steps of Hao-Ran Liu's and tested them in original Ubuntu
12.04.2 precise environment. The 'Lock scree' entry will occur once in
10 times. With upgrade lightdm to 1.2.3-0ubuntu2.3, I ran about 30 times
but it did not happen anymore.
--
You received this bug notification because
partman log
** Attachment added: partman log
https://bugs.launchpad.net/oem-priority/+bug/1197766/+attachment/3747480/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197766
Title:
@Dmitrijs
I tested your patch and it cause another problem.
In the stage 2 (create target partition and install software), ubiquity
prompted an error dialog of No root file system is defined.
The ubiquity debug log and partman log are attached.
** Attachment added: ubiquity debug log
Here I attached a patch file for gnome-control-center 3.4.2
This patch is based on
https://mail.gnome.org/archives/commits-list/2012-November/msg02131.html with
some fixes. I have checked it makes bluetooth to be off in airplane mode.
** Patch added:
@Brian
The release of Ubuntu is 12.04.2 and the version of ubiquity is 2.10.24
** Changed in: partman-auto (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I use ubuntu-13.04 image to create a bootable usb stick.
Copy shimx64.efi to USB:/EFI/ubuntu/BOOTX64.EFI,
Enter setup mode and run LockDown.efi to import keys.
Add boot entry and assign USB/EFI/ubuntu/BOOTX64.EFI, and then boot to this
entry.
I finally got the same result of #13.
Is there any
@ara
I have tried to apply the patch to 3.4.2 and got some errors:
franz@callisto:/tmp/gnome-cc/gnome-control-center-3.4.2$ patch -p1
~/Downloads/gnome-control-center.patch
patching file panels/network/Makefile.am
Hunk #1 succeeded at 31 (offset -14 lines).
patching file
@Steve
We have run LockDown.efi and then enable secure boot.
The errors are attached in the picture.
** Attachment added: 17 下午2:50:10.jpeg
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1187233/+attachment/3739636/+files/17%20%E4%B8%8B%E5%8D%882%3A50%3A10.jpeg
--
You received this
@Steve,
Please help me check if my steps are correct.
note: The platform runs Ubuntu-12.04.2 for ASUS image.
BOOT the platform to non-secure mode
1. copy LockDown.efi to /boot/efi/ EFI partition mount point
2. copy shimx64.efi to /boot/efi/EFI/ubuntu/BOOTX64.EFI
3. reboot and change to
Public bug reported:
When using ubuntu-recovery to recover the system,
The partition layout is different when keeping home partition.
consider disk-recipe:
100 150 200 free
$iflabel{ gpt }
$reusemethod{ }
method{ efi }
format{ } .
128 512 256 ext2
@colin
I rewrite a new patch that:
1. add --function-key option to read function key and set to hotkey
environment variable.
2. grub reads hotkey environment variable and boot to the entry at the
start.
3. add GRUB_HIDDEN_TIMEOUT_KEY variable in /etc/default/grub
Note: Currently we
Public bug reported:
Summery:
I downloaded images from ubuntu.com and use usb-creator-gtk to create
bootable usb.
Then use the usb key to boot on my ASUS X201E laptop and it is always failed
to boot to OS.
These images are all failed:
ubuntu-12.04.2-desktop-amd64.iso
** Also affects: grub
Importance: Undecided
Status: New
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Colin, @Hsin-Yi
I have done a new patch that adds 100ms delay and checks hotkey in:
file: ${src}/grub-core/normal/menu.c
...
/* If timeout is 0, drawing is pointless (and ugly). */
if (grub_menu_get_timeout () == 0)
{
*auto_boot = 1;
return default_entry;
}
...
With this
67 matches
Mail list logo
