[Bug 1410022] Re: Touchpad cannot work after LID close/open due to wrong key mapping
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1410022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587744] [NEW] Screen is dark and brightness cannot adjust.
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 DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jun 1 03:02:00 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] (rev d7) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Kaveri [Radeon R7 Graphics] [103c:805c] InstallationDate: Installed on 2016-06-01 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP EliteOne 705 G2 23-in Touch AiO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=4b6b12fb-1689-40f1-9cb7-adc76b80245b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2016 dmi.bios.vendor: HP dmi.bios.version: N16 Ver. 02.12 dmi.board.name: 805C dmi.board.vendor: HP dmi.board.version: KBC Version 05.22 dmi.chassis.asset.tag: MXL6123GLK dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN16Ver.02.12:bd05/05/2016:svnHP:pnHPEliteOne705G223-inTouchAiO:pvr:rvnHP:rn805C:rvrKBCVersion05.22:cvnHP:ct13:cvr: dmi.product.name: HP EliteOne 705 G2 23-in Touch AiO dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jun 1 03:00:27 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 xserver.video_driver: radeon ** Affects: amd Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial ** Package changed: xorg (Ubuntu) => amd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587744 Title: Screen is dark and brightness cannot adjust. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1587744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571574] Re: 3G (WWAN) icon missing in network-manager-applet
@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 rely on the fact that VPN icon gets drawn later
and therefore
* wins but we cannot currently set a combined pixmap made of
both the link
* icon and the VPN icon.
*/
if (icon_name == NULL && layer == ICON_LAYER_LINK)
icon_name = "nm-no-connection";
if (icon_name != NULL && g_strcmp0 (app_indicator_get_icon
(applet->app_indicator), icon_name) != 0)
app_indicator_set_icon_full (applet->app_indicator,
icon_name, applet->tip);
return;
}
#endif /* WITH_APPINDICATOR */
I will install the update from -propose for test if it is available.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571574
Title:
3G (WWAN) icon missing in network-manager-applet
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1571574/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567796] [NEW] It is sometimes unable to found DELL WWAN module.
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: https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8a386218690aeff7e2c923a14f91da7bbc046ed2 Please merge the fix to modem manager to fix the issue. Ubuntu Xenial (daily image) Release: 16.04 modemmanager: Installed: 1.4.12-1ubuntu1 Candidate: 1.4.12-1ubuntu1 Version table: *** 1.4.12-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 a upstream patch that can fix the + After debugging, we found there is an upstream patch that can fix the issue: https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8a386218690aeff7e2c923a14f91da7bbc046ed2 Please merge the fix to modem manager to fix the issue. Ubuntu Xenial (daily image) Release: 16.04 modemmanager: - Installed: 1.4.12-1ubuntu1 - Candidate: 1.4.12-1ubuntu1 - Version table: - *** 1.4.12-1ubuntu1 500 - 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.4.12-1ubuntu1 + Candidate: 1.4.12-1ubuntu1 + Version table: + *** 1.4.12-1ubuntu1 500 + 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567796 Title: It is sometimes unable to found DELL WWAN module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1567796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567194] [NEW] Unable to switch to console/ttys from ubiquity
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, press Ctrl-Alt-F1 3) Black screen, no prompt is shown Ubuntu Xenial (daily image) Release: 16.04 ubiquity: Installed: 2.21.53 Candidate: 2.21.53 Version table: *** 2.21.53 0 500 http://archive.ubuntu.com/ubuntu/ xenial/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567194 Title: Unable to switch to console/ttys from ubiquity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1567194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562822] Re: Bluetooth Browse Files... not working
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562822 Title: Bluetooth Browse Files... not working To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1562822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1552621] Re: Can't login to desktop autometically after oem-config is finished on OEM mode
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 after oem-config is finished on OEM mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1552621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554929] [NEW] Autocluttersink shows green rectange
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: https://bugzilla.redhat.com/show_bug.cgi?id=1279040 https://bugzilla.gnome.org/show_bug.cgi?id=762764 ** Affects: clutter-gst-2.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 - --videosink=autocluttersink + 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: + Similar bug can be found here: - https://bugzilla.redhat.com/show_bug.cgi?id=1279040 - https://bugzilla.gnome.org/show_bug.cgi?id=762764 + https://bugzilla.redhat.com/show_bug.cgi?id=1279040 + https://bugzilla.gnome.org/show_bug.cgi?id=762764 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554929 Title: Autocluttersink shows green rectange To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter-gst-2.0/+bug/1554929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1552621] Re: Can't login to desktop autometically after oem-config is finished on OEM mode
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1552621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1552621] Re: Can't login to desktop autometically after oem-config is finished on OEM mode
** 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 to desktop autometically after oem-config is finished on OEM mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1552621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1552621] [NEW] Can't login to desktop autometically after oem-config is finished on OEM mode
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 system
2) Restart system, click "Prepare for shipping to end user" and reboot system.
3) oem-config starts, enter user information
4) Black screen.
I found there has race condition between oem-config-* scripts.
First, please watch the code pieces I found in the oem-config-firstboot
for try in $(seq 1 $TRY); do
CODE=0
if [ "$FRONTEND" = debconf_ui ]; then
plymouth quit || true
LANG=en_US.UTF-8 FRONTEND="$FRONTEND" \
/usr/sbin/oem-config-wrapper $DEBUG $AUTOMATIC --only \
2>>/var/log/oem-config.log \
|| CODE=$?
else
FRONTEND="$FRONTEND" \
/usr/bin/ubiquity-dm vt7 :0 oem \
/usr/sbin/oem-config-wrapper $DEBUG $AUTOMATIC --only || CODE=$?
fi
if [ "$CODE" -eq 0 ]; then
# Remove the temporary OEM configuration user, if possible
# and desired.
RET="$(echo GET oem-config/remove | debconf-communicate)"
if [ "${RET#* }" = true ] && getent passwd oem >/dev/null; then
pkill -u oem || true
userdel --force --remove oem || true
fi
/bin/systemctl set-default graphical.target || true
/bin/systemctl --no-block isolate graphical.target || true
exit 0
and oem-config-wrapper:
#! /bin/sh
# Run oem-config, plus other things that need to run after it in X.
set -e
LANG=en_US.UTF-8 oem-config "$@"
# 'set -e' will cause us to exit if oem-config fails. Otherwise:
# Don't run again.
rm -f /var/lib/oem-config/run
# Cleanup from anything the early command prepared
RET="$(echo GET oem-config/late_command | debconf-communicate)" || true
if [ "${RET%% *}" = 0 ]; then
command="${RET#* }"
log-output sh -c "$command" || true
fi
RET="$(echo GET oem-config/remove | debconf-communicate)"
if [ "${RET#* }" = true ]; then
#debconf crashes with this set (LP: #641478)
unset DBUS_SESSION_BUS_ADDRESS
#mandb postinst doesn't like not knowing the locale
if [ -r /etc/default/locale ]; then
. /etc/default/locale
export LANG LANGUAGE
fi
# We're about to pull the rug out from under our own feet, so this
# has to run very late.
case $FRONTEND in
debconf_ui)
export DEBIAN_FRONTEND=dialog
oem-config-remove || true
;;
gtk_ui)
oem-config-remove-gtk || true
;;
kde_ui)
export DEBIAN_FRONTEND=kde
oem-config-remove || true
;;
esac
fi
The /usr/sbin/oem-config-wrapper calls oem-config for bring up UI for
user and runs oem-config-remove-gtk to remove all ubiquity packages at
the end.
Because of oem-config-remove-gtk removes all ubiquity packages, the oem-
config-firstboot can't run remaining commands. Therefore session can't
switch to graphical and results in black screen.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
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.
Steps:
1) Boot into OEM mode (EFI) and install the system
2) Restart system, click "Prepare for shipping to end user" and reboot system.
3) oem-config starts, enter user information
- 4) Black screen.
+ 4) Black screen.
I found there has race condition between oem-config-* scripts.
First, please watch the code pieces I found in the oem-config-firstboot
for try in $(seq 1 $TRY); do
- CODE=0
- if [ "$FRONTEND" = debconf_ui ]; then
- plymouth quit || true
- LANG=en_US.UTF-8 FRONTEND="$FRONTEND" \
- /usr/sbin/oem-config-wrapper $DEBUG $AUTOMATIC --only \
- 2>>/var/log/oem-config.log \
- || CODE=$?
- else
- FRONTEND="$FRONTEND" \
- /usr/bin/ubiquity-dm vt7 :0 oem \
- /usr/sbin/oem-config-wrapper $DEBUG $AUTOMATIC --only
|| CODE=$?
- fi
- if [ "$CODE" -eq 0 ]; then
- # Remove the temporary OEM configuration user, if possible
- # and desired.
- RET="$(echo GET oem-config/remove | debconf-communicate)"
- if [ "${RET#* }" = true ] && getent passwd oem >/dev/null; then
- pkill -u oem || true
- userdel --force --remove oem || true
- fi
- /bin/systemctl set-default graphical.target || true
- /bin/systemctl --no-block isolate graphical.target || true
- exit 0
+ CODE=0
+ if [ "$FRONTEND" = debconf_ui ]; then
+ plymouth quit || true
+ LANG=en_US.UTF-8 FRONTEND="$FRONTEND" \
+ /usr/sbin/oem-config-wrapper $DEBUG $AUTOMATIC --only \
+ 2>>/var/log/oem-config.log \
+ || CODE=$?
+ else
+ FRONTEND="$FRONTEND" \
+ /usr/bin/ubiquity-dm vt7 :0 oem \
+ /usr/sbin/oem-config-wrapper
[Bug 1454950] Re: It needs to press touchpad hotkey twice to re-enable touchpad
@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 touchpad hotkey twice to re-enable touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1454950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454950] Re: It needs to press touchpad hotkey twice to re-enable touchpad
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 Ubuntu. https://bugs.launchpad.net/bugs/1454950 Title: It needs to press touchpad hotkey twice to re-enable touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1454950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454950] Re: It needs to press touchpad hotkey twice to re-enable touchpad
@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 touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1454950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454950] Re: It needs to press touchpad hotkey twice to re-enable touchpad
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 Ubuntu. https://bugs.launchpad.net/bugs/1454950 Title: It needs to press touchpad hotkey twice to re-enable touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1454950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454950] Re: It needs to press touchpad hotkey twice to re-enable touchpad
@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 twice to re-enable touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1454950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454950] Re: It needs to press touchpad hotkey twice to re-enable touchpad
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 https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1454950/+attachment/4411898/+files/gsd-test-mouse.log -- 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 notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1454950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454950] Re: It needs to press touchpad hotkey twice to re-enable touchpad
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 notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1454950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454950] Re: It needs to press touchpad hotkey twice to re-enable touchpad
@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 (manager);
if (state) {
devices = get_disabled_touchpads
(manager-priv-device_manager);
for (l = devices; l != NULL; l = l-next) {
int device_id;
device_id = GPOINTER_TO_INT (l-data);
set_touchpad_enabled (device_id);
}
g_list_free (devices);
} else {
devices = gdk_device_manager_list_devices
(manager-priv-device_manager,
GDK_DEVICE_TYPE_SLAVE);
for (l = devices; l != NULL; l = l-next) {
GdkDevice *device = l-data;
if (device_is_ignored (manager, device))
continue;
if (xdevice_is_libinput (gdk_x11_device_get_id
(device)))
continue;
if (gdk_device_get_source (device) !=
GDK_SOURCE_TOUCHPAD)
continue;
set_touchpad_disabled (device);
}
g_list_free (devices);
}
set_disable_w_typing (manager, state);
}
I have not check if the behaviour is changed, the latest g-s-d source
requires many updates to make it works.
--
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 notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1454950/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454950] Re: It needs to press touchpad hotkey twice to re-enable touchpad
@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 pointer device (usb mouse), this issue won't happen. -- 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 notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1454950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454950] Re: It needs to press touchpad hotkey twice to re-enable touchpad
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) The ensure_touchpad_active checks if toucpad is the only one pointer device on the platform, it will make touchpad always enabled. 1-d) However ensure_touchpad_active only changes the gsettings entries but leave the device disabled. * Press Fn+F9 to disable touchpad === 1st TOUCHPAD HOTKEY TRIGGER START === (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG touchpad_callback ENTER === (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: +++(1) gsettings KEY_TOUCHPAD_ENABLED value: 0 (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: Trying to set device disabled for ETPS/2 Elantech Touchpad (12) (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: Disabled device ETPS/2 Elantech Touchpad (12) (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: +++(2) KEY_TOUCHPAD_ENABLED, value=0 +++ (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG touchpad_callback EXIT === (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG device_removed_cb ENTER === (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG ensure_touchpad_active ENTER ===, gsettings key: 0 (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG touchpad_callback ENTER === (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: +++(2) KEY_TOUCHPAD_ENABLED, value=1 +++ (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG touchpad_callback EXIT === (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG ensure_touchpad_active EXIT ===, gsettings key: 1 (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG device_removed_cb EXIT === === 1st TOUCHPAD HOTKEY TRIGGER END === 2-a) Press Fn+F9 again the touchpad is still disabled. 2-b) The gsettings KEY_TOUCHPAD_ENABLED is set to 0 (FALSE), I think it is changed by usd-media-key. 2-c) I think because device is removed from the list, nothing happend in this stage. * Press Fn+F9 to enable touchpad === 2nd TOUCHPAD HOTKEY TRIGGER START === (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG touchpad_callback ENTER === (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: +++(2) KEY_TOUCHPAD_ENABLED, value=0 +++ (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG touchpad_callback EXIT === === 2nd TOUCHPAD HOTKEY TRIGGER END === 3-a) Press Fn+F9 again, the gsettings KEY_TOUCHPAD_ENABLED is set to 1(TRUE), it should be set by usd-media-key 3-b) The touchpad_callback eanbles touchpad. * Press Fn+F9 to enable touchpad === 3rd TOUCHPAD HOTKEY TRIGGER START === (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG touchpad_callback ENTER === (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: +++(2) KEY_TOUCHPAD_ENABLED, value=1 +++ (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: @@@ set_toucpad_enabled :12 @@@ (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: Trying to set device enabled for 12 (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: Enabled device 12 (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG touchpad_callback EXIT === (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG device_added_cb ENTER === (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: setting handedness on ETPS/2 Elantech Touchpad (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: setting tap to click on ETPS/2 Elantech Touchpad (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: setting motion on ETPS/2 Elantech Touchpad (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: Setting accel -1/-1, threshold -1 for device 'ETPS/2 Elantech Touchpad' (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: setting tap to click on ETPS/2 Elantech Touchpad (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: setting edge scroll on ETPS/2 Elantech Touchpad (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: setting horiz scroll on ETPS/2 Elantech Touchpad (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: Trying to set normal scroll for ETPS/2 Elantech Touchpad (lt-usd-test-mouse:16396): mouse-plugin-DEBUG: === DEBUG device_added_cb EXIT === === 3rd TOUCHPAD HOTKEY TRIGGER END === According to my analysis, the touchpad disable hotkey should work fine if ensure_touchpad_active does nothing. I looks the changelog in unity-settings-daemon, this function is added because of the issue: https://bugzilla.gnome.org/show_bug.cgi?id=685941 I think users should be able to disable the touchpad if there has control keys. Should we keep ensure_touchpad_active this function? ** Bug watch added: GNOME Bug Tracker #685941
[Bug 1454950] [NEW] It needs to press touchpad hotkey twice to re-enable touchpad
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 mouse (any port is ok) Because it can't be reproduced in Kubuntu, I think it should be an issue of unity-settings-daemon. Platform: ASUS P451L Ubuntu: 14.04-LTS Unity-setting-daemon version: 14.04.0+14.04.20140606-0ubuntu2 Touchpad vendor: Elantech Note: This issue can be reproduced in Ubuntu 15.04. ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1454950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399096] Re: Touchpad lost function after switch from guest to user account
@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 fine now. Mouse cursor now can move after session is changed. ** Changed in: oem-priority 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/1399096 Title: Touchpad lost function after switch from guest to user account To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1399096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1398287] Re: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen
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 14.04 Lock button sometimes takes 30~60s to enter lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1398287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1410022] [NEW] Touchpad cannot work after LID close/open due to wrong key mapping
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 analysis, when the LID is closed kbc emits an event (D8) and udev remapping it to F21 (touchpad toggle event). When X server receives the event, it disables touchpad. However there is no corresponding event triggered after LID is opened thus X server does not enable the touchpad and results in this issue. Currently udev keymaping for presarion CQ is: # Presario keyboard:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*Presario*CQ*:pvr* KEYBOARD_KEY_d8=f21 KEYBOARD_KEY_d9=f21 I think it should be changed to: # Presario keyboard:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*Presario*CQ*:pvr* KEYBOARD_KEY_d8=!f23 # touchpad off KEYBOARD_KEY_d9=!f22 # touchpad on ** Affects: udev (Ubuntu) Importance: Undecided Status: New -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1410022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399096] Re: Touchpad lost function after switch from guest to user account
** 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 notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1399096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1398287] Re: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen
@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 30~60s to enter lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1398287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399096] [NEW] Touchpad lost function after switch from guest to user account
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 Synaptics TouchPad: can't grab event device, errno=16 [ 282.940] [dix] couldn't enable device 11 [ 282.940] setversion 1.4 failed: Permission denied ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-synaptics 1.7.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-41.69stella1-generic 3.13.11.10 Uname: Linux 3.13.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Dec 4 02:25:41 2014 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-neihu-trusty-amd64-20141125-0 DistroCodename: trusty DistroVariant: ubuntu InstallationDate: Installed on 2014-12-04 (0 days ago) InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 20141125-01:45 Lsusb: Bus 001 Device 003: ID 0bda:5776 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-41-generic root=UUID=f7c1e040-6471-4e14-9e77-bb406b63fad3 ro quiet splash video.use_native_backlight=1 radeon.modeset=0 nouveau.modeset=0 vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd10/28/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097F12005F1620100:rvnHewlett-Packard:rn2211:rvr86.45:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 097F12005F1620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1stella3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Dec 4 02:21:16 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1399096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308828] Re: System can't restart if user removes usb key and presses 'Restart'
@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 safety procedure for this behaviour? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308828 Title: System can't restart if user removes usb key and presses 'Restart' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1308828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()
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 SIGABRT in __libc_start_main() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1316454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()
@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 this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1316454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326624] [NEW] Error playing video from webcam
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 error playing video from the webcam shown in the cheese.
Diagnose:
According to some tests, the root cause results from the JPEG processing in
libv4l-0,
The source of v4l-utils-1.0.1/lib/libv4lconvert/jpeg.c, 377:
/* We don't want any padding as that may overflow our dest */
if (width % (8 * h_samp) || height % (8 * v_samp)) {
V4LCONVERT_ERR(
resolution is not a multiple of dctsize);
errno = EIO;
return -1;
}
Because 540 is not a multiple of 8, so it fails.
I tried other video capture apps and set to the same resolution 960x540
and MJPEG format, the issue can be reproduced. But if the format changes
to YUYV, it works fine (preview/capture).
** Affects: cheese
Importance: Undecided
Status: New
** Affects: oem-priority
Importance: High
Status: New
** Also affects: cheese
Importance: Undecided
Status: New
** Package changed: cheese (Ubuntu) = oem-priority
** 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/1326624
Title:
Error playing video from webcam
To manage notifications about this bug go to:
https://bugs.launchpad.net/cheese/+bug/1326624/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()
** 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 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) + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2014-05-02 (0 days ago) + InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 20140502-08:19 -- 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 this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1316454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()
** 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 Gen2/3 Ranges are not supported. Please use unsafe access. (Core dump) DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-05-02 (0 days ago) InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 20140502-08:19 -- 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 this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1316454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()
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 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 this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1316454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()
** 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 notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1316454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1316454 Title: intel_reg_dumper crashed with SIGABRT in __libc_start_main() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1316454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316454] [NEW] intel_reg_dumper crashed with SIGABRT in __libc_start_main()
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: intel-gpu-tools (Ubuntu) Importance: Undecided Status: New ** Attachment added: _usr_bin_intel_reg_dumper.0.crash https://bugs.launchpad.net/bugs/1316454/+attachment/4106082/+files/_usr_bin_intel_reg_dumper.0.crash -- 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 this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1316454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308828] [NEW] System can't restart if user removes usb key and presses 'Restart'
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 USB key 4) Press 'Restart' button on the message box result: System can't restart automatically. Please note, this issue can be also reproduced on Ubuntu 14.04. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: ubiquity Importance: Undecided Status: New ** 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/1308828 Title: System can't restart if user removes usb key and presses 'Restart' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1308828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032433] Re: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1032433 Title: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1032433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032433] Re: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
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. https://bugs.launchpad.net/bugs/1032433 Title: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1032433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032433] Re: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
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 WEP 128-bit Passphrase, Ad-hoc connection cannot be established To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1032433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293906] [NEW] plymouth-splash can't be displayed due to race condition with plymouth-stop
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 be displayed. The timing that plymouth-splash would be executed relies on these conditions: (ref: /etc/init/plymouth-splash.conf) 1) plymouth should be executed and, 2) graphics-device-added or drm-device-added event has been emitted. Condition 1 is always satisfied, so the possible reason of why plymouth- splash is not executed might be the graphic takes too many time to initial. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: plymouth Importance: Undecided Status: New ** Also affects: plymouth Importance: Undecided Status: New ** Package changed: plymouth (Ubuntu) = oem-priority ** Tags removed: 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/1293906 Title: plymouth-splash can't be displayed due to race condition with plymouth-stop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1293906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032433] Re: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
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 https://bugs.launchpad.net/oem-priority/+bug/1032433/+attachment/3978230/+files/wifi_adhoc_log.tgz -- 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 WEP 128-bit Passphrase, Ad-hoc connection cannot be established To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1032433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197766] Re: Different partition layout after recovery with keep home partition
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 recovery with keep home partition To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1197766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197766] Re: Different partition layout after recovery with keep home partition
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. https://bugs.launchpad.net/bugs/1197766 Title: Different partition layout after recovery with keep home partition To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1197766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197766] Re: Different partition layout after recovery with keep home partition
@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 home partition To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1197766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187233] Re: Grub2 fails on ASUS X201E with secure boot is enabled
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 go to: https://bugs.launchpad.net/grub/+bug/1187233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187233] Re: Grub2 fails on ASUS X201E with secure boot is enabled
@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. https://bugs.launchpad.net/bugs/1187233 Title: Grub2 fails on ASUS X201E with secure boot is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1187233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982889] Re: X trying to start before plymouth has finished using the drm driver
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: drm_device_keep_trying.patch https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/982889/+attachment/3810546/+files/drm_device_keep_trying.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032433] Re: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
@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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1032433 Title: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1032433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032433] Re: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
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 adhoc/success/syslog.client.log adhoc/success/syslog.server.log) If the type is set to WEP-128 passphrase, the result is failed (see adhoc/fail/syslog.client.log adhoc/fail/syslog.server.log) The logs are attached in the tarball. ** Attachment added: adhoc.tar.gz https://bugs.launchpad.net/oem-priority/+bug/1032433/+attachment/3753048/+files/adhoc.tar.gz -- 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 WEP 128-bit Passphrase, Ad-hoc connection cannot be established To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1032433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197766] Re: Different partition layout after recovery with keep home partition
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 Ubuntu. https://bugs.launchpad.net/bugs/1197766 Title: Different partition layout after recovery with keep home partition To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1197766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951000] Re: disable guest session screen lock using gsettings
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951000 Title: disable guest session screen lock using gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/951000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197766] Re: Different partition layout after recovery with keep home partition
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: Different partition layout after recovery with keep home partition To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1197766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197766] Re: Different partition layout after recovery with keep home partition
@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 https://bugs.launchpad.net/oem-priority/+bug/1197766/+attachment/3747479/+files/debug -- 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 home partition To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1197766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059449] Re: Set Airplane Mode On, Bluetooth still work properly .
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: fix_bluetooth_wrong_state_airplane_mode.patch https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1059449/+attachment/3745218/+files/fix_bluetooth_wrong_state_airplane_mode.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059449 Title: Set Airplane Mode On, Bluetooth still work properly . To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1059449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197766] Re: Different partition layout after recovery with keep home partition
@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. https://bugs.launchpad.net/bugs/1197766 Title: Different partition layout after recovery with keep home partition To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1197766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187233] Re: Grub2 fails on ASUS X201E with secure boot is enabled
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 wrong in my steps? -- 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 go to: https://bugs.launchpad.net/grub/+bug/1187233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059449] Re: Set Airplane Mode On, Bluetooth still work properly .
@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 panels/network/cc-network-panel.c Hunk #1 succeeded at 50 with fuzz 2 (offset 12 lines). Hunk #2 succeeded at 84 (offset 15 lines). Hunk #3 FAILED at 209. Hunk #4 succeeded at 2300 (offset 1642 lines). Hunk #5 succeeded at 3366 with fuzz 2 (offset 2344 lines). Hunk #6 FAILED at 1094. 2 out of 6 hunks FAILED -- saving rejects to file panels/network/cc-network-panel.c.rej patching file panels/network/rfkill-glib.c patching file panels/network/rfkill-glib.h patching file panels/network/rfkill.h -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059449 Title: Set Airplane Mode On, Bluetooth still work properly . To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1059449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187233] Re: Grub2 fails on ASUS X201E with secure boot is enabled
@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 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 go to: https://bugs.launchpad.net/grub/+bug/1187233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187233] Re: Grub2 fails on ASUS X201E with secure boot is enabled
@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 secure mode in BIOS 5. boot 6. failed (Secure Boot Violation, see the picture) ** Attachment added: 5 下午4:30:42.jpeg https://bugs.launchpad.net/oem-priority/+bug/1187233/+attachment/3725619/+files/5%20%E4%B8%8B%E5%8D%884%3A30%3A42.jpeg -- 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 go to: https://bugs.launchpad.net/grub/+bug/1187233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197766] [NEW] Different partition layout after recovery with keep home partition
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
$defaultignore{ }
method{ format }
format{ }
use_filesystem{ }
filesystem{ ext2 }
mountpoint{ /boot } .
32000 1 32000 $default_filesystem
$lvmok{ }
method{ format }
format{ }
use_filesystem{ }
reserved_for_root{ 1 }
$default_filesystem{ }
mountpoint{ / } .
8000 512 8000 linux-swap
$lvmok{ }
method{ swap }
format{ } .
500 1 -1 $default_filesystem
$lvmok{ }
$reusemethod{ }
method{ format }
format{ }
use_filesystem{ }
$default_filesystem{ }
label{ User_Data }
mountpoint{ /home } .
In this case, we want to build this layout in a 320G hard disk and keep the
home partition.
If we recover system WITHOUT keeping home partition, the partition layout looks
like:
Model: ATA ST320LT012-9WS14 (scsi)
Disk /dev/sda: 320072933376B
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Number Start EndSize File system Name
Flags
17408B20479B 3072B Free Space
1 20480B9743B 99979264B fat32 EFI System
Partition boot
2 9744B 411791B402048Bfat32 Recovery
Partition
3 411792B 3611791B 320B ext4
4 3611792B 4411791B 80Blinux-swap(v1)
5 4411792B 320072916479B 275972914688B ext4Ubuntu Home
Partition
But if we recovery system WITH keeping home partition, the partition layout
looks like:
Model: ATA ST320LT012-9WS14 (scsi)
Disk /dev/sda: 320072933376B
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Number Start EndSize File system Name
Flags
17408B 20479B 3072B Free Space
1 20480B 9743B 99979264B fat32 EFI System
Partition boot
2 9744B 411791B402048Bfat32 Recovery
Partition
4 411792B42073001983B 37973000192B ext4
6 42073001984B 4411791B 2026999808Blinux-swap(v1)
5 4411792B 320072916479B 275972914688B ext4Ubuntu
Home Partition
The behavior is abnormal.
According to my test, partman thinks the necessary space is
100+32000+8000 while the home partition is kept. And I discovered that
partman knows EFI partition has $reusemethod option and the partition
exists but it still adds the partition size to total. So the total need
(40100m) is not equal to total free (4M) and then partman use
alternative recipe instead. This is the root cause of why partition
layout is different.
--
recipe.sh line: 187~ 209
foreach_partition () {
local - doing IFS pcount last partition
doing=$1
pcount=$(echo $scheme | wc -l)
last=no
IFS=$NL
for partition in $scheme; do
restore_ifs
[ $pcount -gt 1 ] || last=yes
set -- $partition
eval $doing
pcount=$(($pcount - 1))
done
}
min_size () {
local size
size=0
foreach_partition '
size=$(($size + $1))'
echo $size
}
These codes are used for calculate total recipe size, and I can't find
any expression deals with $reusemethod.
** Affects: oem-priority
Importance: Critical
Status: New
** Affects: partman-auto
Importance: Undecided
Status: New
** Also affects: partman-auto
Importance: Undecided
Status: New
** Package changed: partman-auto (Ubuntu) = oem-priority
** Summary changed:
- Different partition layout after recover with keep home partition
+ Different partition layout after recovery with keep home partition
--
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 home partition
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1197766/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178618] Re: --hotkey option does not work when the menu is hidden
@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 only support one hotkey. ** Patch added: ubuntu_quiet_hotkey.patch https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1178618/+attachment/3701890/+files/ubuntu_quiet_hotkey.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178618 Title: --hotkey option does not work when the menu is hidden To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1178618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187233] [NEW] Grub2 fails on ASUS X201E with secure boot is enabled
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 ubuntu-12.10-desktop-amd64.iso ubuntu-13.04-desktop-amd64.iso I also enabled grub2 debug message, and found they all fail on: loader/i386/efi/linux.c:69: Asking shim to verify kernel signature. The BIOS revision of ASUS X201E is 209 which can be downloaded from official ASUS website. Additionally, Win8 and Fedora-18 can be booted and installed on this platform. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1187233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187233] Re: Grub2 fails on ASUS X201E with secure boot is enabled
** 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 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 go to: https://bugs.launchpad.net/grub/+bug/1187233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178618] Re: --hotkey option does not work when the menu is hidden
@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 patch, we only have to set --hotkey f9 to menuentry, and users can
press f9 to enter recovery mode even grub runs in quiet mode.
** Patch added: ubuntu_quiet_hotkey.patch
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1178618/+attachment/3688381/+files/ubuntu_quiet_hotkey.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178618
Title:
--hotkey option does not work when the menu is hidden
To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1178618/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
