# Piston application panics on Raspberry Pi

**URL:** <https://discourse.piston.rs/t/piston-application-panics-on-raspberry-pi/156>\
**Category:** Uncategorized\
**Created:** [August 7, 2018, 9:43pm UTC](https://discourse.piston.rs/t/piston-application-panics-on-raspberry-pi/156 "2018-08-07T21:43:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wezm](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.piston.rs/wezm/32/33_2.png) [@wezm](https://discourse.piston.rs/u/wezm)\
**Post date:** [August 7, 2018, 9:43pm UTC](https://discourse.piston.rs/t/piston-application-panics-on-raspberry-pi/156/1 "2018-08-07T21:43:16Z")

</div>

I have built a small application with Piston to show a slideshow of photos from my Flickr photostream:

> **[wezm/WallFlower](https://github.com/wezm/WallFlower/tree/rust)**
>
> A wall appliance. Contribute to wezm/WallFlower development by creating an account on GitHub.

The goal is to have it run on a SBC like a Raspberry Pi. It runs fine on desktop Linux machines but when running on an actual Raspberry Pi 3 it panics somewhere in [`gfx_graphics::back_end::Gfx2d<R>>::new`](https://github.com/PistonDevelopers/gfx_graphics/blob/master/src/back_end.rs#L189). The error is not especially helpful as even a debug build lacks a line number for where the error occurs and there’s a number of `unwrap`s in `Gfx2d::new`.

I was wondering if the error made more sense to anyone else or if anyone had any experience or tips running Piston projects on a Raspberry Pi.

```auto
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: DescriptorInit(PixelExport("Target0", None))', libcore/result.rs:945:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::panicking::default_hook::{{closure}}
             at libstd/sys_common/backtrace.rs:71
   2: std::panicking::rust_panic_with_hook
             at libstd/panicking.rs:227
             at libstd/panicking.rs:511
   3: std::panicking::continue_panic_fmt
             at libstd/panicking.rs:426
   4: rust_begin_unwind
             at libstd/panicking.rs:337
   5: core::panicking::panic_fmt
             at libcore/panicking.rs:92
   6: core::result::unwrap_failed
   7: <gfx_graphics::back_end::Gfx2d<R>>::new
   8: wallflower::main
   9: std::rt::lang_start::{{closure}}
  10: main
  11: __libc_start_main

```