New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 896035 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Nov 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

wayland_keyboard.cc check failed

Project Member Reported by rjkroege@chromium.org, Oct 16

Issue description

I built Chromium/ozone/wayland,

args.gn like so:

use_ozone = true
use_goma = true
symbol_level = 2
is_component_build = true
dcheck_always_on = true

on weston nouveau. (There is no nouveau appropriate use_XXX_minigbm= setting? Certainly it's worth updating the docs for what to do with nouveau.)

crashed like this on weston:

[121275:121275:1016/174812.677409:FATAL:wayland_keyboard.cc(77)] Check failed: success. Failed to set the XKB keyboard mapping.
#0 0x7f17445d08bd base::debug::StackTrace::StackTrace()
#1 0x7f17442cea2a base::debug::StackTrace::StackTrace()
#2 0x7f174434061b logging::LogMessage::~LogMessage()
#3 0x7f172df6fc62 ui::WaylandKeyboard::Keymap()
#4 0x7f1713caefce ffi_call_unix64
#5 0x7f1713cae93f ffi_call
#6 0x7f172dfee5d2 wl_closure_invoke
#7 0x7f172dfec2b8 dispatch_event
#8 0x7f172dfeb63c dispatch_queue
#9 0x7f172dfeb423 wl_display_dispatch_queue_pending
#10 0x7f172dfeafbe wl_display_dispatch_queue
#11 0x7f172dfeb6b2 wl_display_dispatch
#12 0x7f172df47624 ui::WaylandConnection::OnFileCanReadWithoutBlocking()
#13 0x7f174462355e base::MessagePumpLibevent::FdWatchController::OnFileCanReadWithoutBlocking()
#14 0x7f1744624e30 base::MessagePumpLibevent::OnLibeventNotification()
#15 0x7f17446779ae event_process_active
#16 0x7f1744676ff7 event_base_loop
#17 0x7f1744624faf base::MessagePumpLibevent::Run()
#18 0x7f1744364b8b base::MessageLoop::Run()
#19 0x7f174441013d base::RunLoop::Run()
#20 0x55f009a089a3 ChromeBrowserMainParts::MainMessageLoopRun()
#21 0x7f173d5af241 content::BrowserMainLoop::RunMainMessageLoopParts()
#22 0x7f173d5b7020 content::BrowserMainRunnerImpl::Run()
#23 0x7f173d5a1cee content::BrowserMain()
#24 0x7f173f6159f0 content::RunBrowserProcessMain()
#25 0x7f173f618827 content::ContentMainRunnerImpl::Run()
#26 0x7f173f60e71c content::ContentServiceManagerMainDelegate::RunEmbedderProcess()
#27 0x7f174487ac2a service_manager::Main()
#28 0x7f173f613113 content::ContentMain()
#29 0x55f0074a1246 ChromeMain
#30 0x55f0074a1152 main
#31 0x7f1717cba2b1 __libc_start_main
#32 0x55f0074a102a _start

any ideas?


 
input portion of weston.ini:

[input-method]
path=/usr/lib/weston/weston-keyboard

Labels: OS-Linux
suppressing the DCHECK by hand did not improve matters: the system was incapable of allocating a window.


Cc: jmukthavaram@chromium.org
Labels: Hotlist-DesktopUIChecked
Status: WontFix (was: Assigned)
**UI Mass traige**
We were unable to find repro steps for this bug. If you have more data to reproduce this bug or have clear repro steps, please reopen or file a new issue.
Thanks!


Sign in to add a comment