[Bug 1660041] Re: wrong keyboard layout in gdm
It seems that gdm doesn't load user preferences before login. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1660041 Title: wrong keyboard layout in gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1660041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1660041] Re: wrong keyboard layout in gdm
I found this issue happens in some cases after doing that procedure. My environment: Ubuntu Gnome 17.04 Japanese (JP) keyboard layout Precondition: All Settings > Language Support Then configure Japanese and then click "Apply System-Wide". OK: 1. Logged in state 2. Lock screen (Super + L) 3. Unlock screen 4. Password approved due to correct(JP) keyboard layout Wrong: 1. Logged in state 2. Logout 3. Attempt to login 4. Password rejected due to wrong(US) keyboard layout Wrong: 1. Start computer with automatic-login disable 2. Attempt to login 3. Password rejected due to wrong(US) keyboard layout -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1660041 Title: wrong keyboard layout in gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1660041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1660041] Re: wrong keyboard layout in gdm
>However, in 17.10 it appears you can go to: > All Settings > Language Support >Then configure your preferred language and then click "Apply System-Wide". Thanks for the information. I tried that with Ubuntu 17.04 and a Japanese keyboard, it works. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1660041 Title: wrong keyboard layout in gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1660041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1660041] Re: wrong keyboard layout in gdm
** Tags added: zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1660041 Title: wrong keyboard layout in gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1660041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1510769] [NEW] app icon is old
Public bug reported: New icon shows on Gnome. However, old icon shows on Unity. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: totem 3.16.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 28 11:56:37 2015 InstallationDate: Installed on 2015-09-23 (34 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: totem UpgradeStatus: Upgraded to wily on 2015-10-25 (3 days ago) ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1510769 Title: app icon is old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1510769/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1015658] Re: eog doesn't take focus when started from nautilus
** Summary changed: - oeg doesn't take focus when started from nautilus + eog doesn't take focus when started from nautilus -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1015658 Title: eog doesn't take focus when started from nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1015658/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1275368] [NEW] gnome-control-center.real crashed with SIGSEGV
Public bug reported: gnome-control-center.real crashed with SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu50 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sun Feb 2 08:19:23 2014 Disassembly: => 0x7f8f4f145414: Cannot access memory at address 0x7f8f4f145414 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2014-02-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140201) ProcCmdline: /usr/bin/gnome-control-center.real region layouts ProcEnviron: LANGUAGE=ja PATH=(custom, user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8f4f145414: Cannot access memory at address 0x7f8f4f145414 PC (0x7f8f4f145414) ok Stack memory exhausted (SP below stack segment) SP (0x7f8f2c44fc10) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: gnome-control-center.real crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1275368 Title: gnome-control-center.real crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1275368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1275295] [NEW] gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock()
Public bug reported: ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu50 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 2 03:08:08 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2014-02-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140201) ProcCmdline: /usr/bin/gnome-control-center.real info ProcEnviron: LANGUAGE=ja PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fbc10786414 <__GI___pthread_mutex_lock+4>:mov 0x10(%rdi),%esi PC (0x7fbc10786414) ok source "0x10(%rdi)" (0x20d8) not located in a known VMA region (needed readable region)! destination "%esi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66 ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so start_thread (arg=0x7fbbedb83700) at pthread_create.c:312 Title: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public ** Description changed: - Description: Ubuntu Trusty Tahr (development branch) - Release: 14.04 - gnome-control-center: - インストールされているバージョン: 1:3.6.3-0ubuntu50 - 候補: 1:3.6.3-0ubuntu50 - バージョンテーブル: - *** 1:3.6.3-0ubuntu50 0 - 500 http://jp.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - 100 /var/lib/dpkg/status - ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu50 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 2 03:08:08 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2014-02-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140201) ProcCmdline: /usr/bin/gnome-control-center.real info ProcEnviron: - LANGUAGE=ja - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=ja_JP.UTF-8 - SHELL=/bin/bash + LANGUAGE=ja + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ja_JP.UTF-8 + SHELL=/bin/bash SegvAnalysis: - Segfault happened at: 0x7fbc10786414 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%esi - PC (0x7fbc10786414) ok - source "0x10(%rdi)" (0x20d8) not located in a known VMA region (needed readable region)! - destination "%esi" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7fbc10786414 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%esi + PC (0x7fbc10786414) ok + source "0x10(%rdi)" (0x20d8) not located in a known VMA region (needed readable region)! + destination "%esi" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: - __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66 - ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so - ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so - ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so - start_thread (arg=0x7fbbedb83700) at pthread_create.c:312 + __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66 + ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so + ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so + ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so + start_thread (arg=0x7fbbedb83700) at pthread_create.c:312 Title: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1275295 Title: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1275295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 321870] Re: internal data stream error in totem
I palyed .mpg file,and it occured. Ubuntu 13.10 64bit Linux 3.11.0-14-generic totem 3.8.2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/321870 Title: internal data stream error in totem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-ugly0.10/+bug/321870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 321870] Re: internal data stream error in totem
I played .mpg file, and it occured. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/321870 Title: internal data stream error in totem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-ugly0.10/+bug/321870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 321870] Re: internal data stream error in totem
I can reproduce it. Error message: "internal data stream error" ** (totem:25828): CRITICAL **: gst_video_decoder_allocate_output_frame: assertion 'frame->output_buffer == NULL' failed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/321870 Title: internal data stream error in totem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-ugly0.10/+bug/321870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs