from:"Jörn Schönyan"

[Desktop-packages] [Bug 1388901] [NEW] nvidia-prime fails to switch profiles (alternatives related)

2014-11-03 Thread Jörn Schönyan

Public bug reported:

Hello everyone,

nvidia-prime has more bugs with every release! On a fresh install of
Kubuntu 14.10, I've installed nvidia-prime and nvidia-331. After the
obligatory restart, the Nvidia chip was active. Trying to switch to the
Intel profile looks like this:

joern@Aspire-V3-571G:~$ sudo prime-select intel
Info: the current alternatives in use are: ['nvidia-331', 'nvidia-331']
Info: selecting nvidia-331-prime for the intel profile
update-alternatives: /usr/lib/nvidia-331-prime/ld.so.conf wird verwendet, um 
/etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) im 
manueller Modus bereitzustellen
update-alternatives: /usr/lib/nvidia-331-prime/alt_ld.so.conf wird verwendet, 
um /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) im 
manueller Modus bereitzustellen

That is only fixable by reinstalling Mesa, everytime I want to switch.
Really annoying.

** Affects: nvidia-prime (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1388901

Title:
  nvidia-prime fails to switch profiles (alternatives related)

Status in “nvidia-prime” package in Ubuntu:
  New

Bug description:
  Hello everyone,

  nvidia-prime has more bugs with every release! On a fresh install of
  Kubuntu 14.10, I've installed nvidia-prime and nvidia-331. After the
  obligatory restart, the Nvidia chip was active. Trying to switch to
  the Intel profile looks like this:

  joern@Aspire-V3-571G:~$ sudo prime-select intel
  Info: the current alternatives in use are: ['nvidia-331', 'nvidia-331']
  Info: selecting nvidia-331-prime for the intel profile
  update-alternatives: /usr/lib/nvidia-331-prime/ld.so.conf wird verwendet, um 
/etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) im 
manueller Modus bereitzustellen
  update-alternatives: /usr/lib/nvidia-331-prime/alt_ld.so.conf wird verwendet, 
um /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) im 
manueller Modus bereitzustellen

  That is only fixable by reinstalling Mesa, everytime I want to switch.
  Really annoying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1388901/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia

2014-10-24 Thread Jörn Schönyan

barcc, that second approach won't work.

import ctypes
from ctypes import util
ctypes.CDLL(util.find_library('GL'), ctypes.RTLD_GLOBAL)

That should be better, but I can't reproduce the bug myself, likely
because it's an Optimus notebook.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/941826

Title:
  dlopen(libGL.so) resolves to mesa rather than nvidia

Status in NVIDIA Drivers Ubuntu:
  New
Status in “mesa” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “pyqt5” package in Ubuntu:
  Invalid
Status in “python-qt4” package in Ubuntu:
  Invalid

Bug description:
  I'm having trouble with a combination of NVIDIA + Python + Qt +
  Opengl.

  I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and 
errors like this these:
  QGLShader: could not create shader
  Vertex shader for simpleShaderProg (MainVertexShader 
&PositionOnlyVertexShader) failed to compile

  This is an example application triggering the problem:
  http://pastebin.com/R0aa8ejs

  The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact 
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this 
error when trying the original demo application from python-qt4-doc. Also, 
calling
  QtGui.QApplication.setGraphicsSystem("opengl")
  produces the same errors.

  I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
  provided nvidia drivers (where 12.04 includes the most recent driver
  for now). After installing the driver using the original NVidia
  installer, the applications work as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop

2014-08-13 Thread Jörn Schönyan

Please, fix this bug! It's totally annoying, every single day people ask
for it in the Ubuntu forums. Get rid of iBus or do whatever you want,
but this bug needs to be fixed ASAP!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1240198

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE="de_DE.UTF-8"
  LC_NUMERIC="de_DE.UTF-8"
  LC_TIME="de_DE.UTF-8"
  LC_COLLATE="de_DE.UTF-8"
  LC_MONETARY="de_DE.UTF-8"
  LC_MESSAGES="de_DE.UTF-8"
  LC_PAPER="de_DE.UTF-8"
  LC_NAME="de_DE.UTF-8"
  LC_ADDRESS="de_DE.UTF-8"
  LC_TELEPHONE="de_DE.UTF-8"
  LC_MEASUREMENT="de_DE.UTF-8"
  LC_IDENTIFICATION="de_DE.UTF-8"
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL="pc105"
  XKBLAYOUT="de"
  XKBVARIANT=""
  XKBOPTIONS=""

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 941826] Re: PyQt cannot compile shaders with Ubuntu's Nvidia drivers

2014-08-11 Thread Jörn Schönyan

I can confirm that bug in PyQt5/QML. I hope that it can be fixed, as I'm
working on a project for future Lubuntu versions and want to get rid of
additional dependencies (python3-opengl). Interesting: It doesn't seem
to exist on hybrid notebooks a.k.a. Optimus in combination with
bumblebee.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/941826

Title:
  PyQt cannot compile shaders with Ubuntu's Nvidia drivers

Status in NVIDIA Drivers Ubuntu:
  New
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “python-qt4” package in Ubuntu:
  Confirmed

Bug description:
  I'm having trouble with a combination of NVIDIA + Python + Qt +
  Opengl.

  I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and 
errors like this these:
  QGLShader: could not create shader
  Vertex shader for simpleShaderProg (MainVertexShader 
&PositionOnlyVertexShader) failed to compile

  This is an example application triggering the problem:
  http://pastebin.com/R0aa8ejs

  The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact 
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this 
error when trying the original demo application from python-qt4-doc. Also, 
calling
  QtGui.QApplication.setGraphicsSystem("opengl")
  produces the same errors.

  I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
  provided nvidia drivers (where 12.04 includes the most recent driver
  for now). After installing the driver using the original NVidia
  installer, the applications work as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1307648] Re: chromium 34 from proposed does not take input from keyboard in first entry point on several webpages

2014-07-25 Thread Jörn Schönyan

Yes, v35 from Utopic works fine in Trusty. I suggest an SRU, too.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1307648

Title:
  chromium 34 from proposed does not take input from keyboard in first
  entry point on several webpages

Status in “chromium-browser” package in Ubuntu:
  Confirmed

Bug description:
  To reproduce install chromium 34 from proposed with pepperflash. And
  find a site that you input some text into like indeed.com or some
  others. Then you hit the keys on the keyboard but no text is seen
  onscreen.

  I expected the text to be entering into chroumium like it is on any
  other browser. And for the text to be entered into the browser and
  transfered ot the webpage I am submitting it to.

  Instead it did not show up and indeed.com thought I did not enter anything 
even though I pressed several keys on my keyboard. 
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  chromium-browser:
Installed: 34.0.1847.116-0ubuntu1~pkg1006
Candidate: 34.0.1847.116-0ubuntu1~pkg1006
Version table:
   *** 34.0.1847.116-0ubuntu1~pkg1006 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-proposed/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   33.0.1750.152-0ubuntu1~pkg995.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu1~pkg1006
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Apr 14 11:15:07 2014
  Desktop-Session:
   DESKTOP_SESSION = Lubuntu
   XDG_CONFIG_DIRS = 
/etc/xdg/lubuntu:/etc/xdg/xdg-Lubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/etc/xdg/lubuntu:/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg:/usr/share/Lubuntu:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sdc4  
ext4  641G   61G  549G  10% /\nnone   tmpfs 4.0K 0  4.0K   
0% /sys/fs/cgroup\nudev   devtmpfs  1.9G  4.0K  1.9G   1% /dev\ntmpfs   
   tmpfs 386M  1.3M  385M   1% /run\nnone   tmpfs 5.0M 
0  5.0M   0% /run/lock\nnone   tmpfs 1.9G   17M  1.9G   1% 
/run/shm\nnone   tmpfs 100M   16K  100M   1% /run/user\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sdc4 41M  
565K   41M2% /\nnone 483K 2  483K1% 
/sys/fs/cgroup\nudev 480K   612  479K1% /dev\ntmpfs
483K   643  482K1% /run\nnone 483K 5  483K1% 
/run/lock\nnone 483K19  483K1% /run/shm\nnone 
483K13  483K1% /run/user\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-01-02 (102 days ago)
  InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha amd64 (20140101)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-04-14T10:56:12.681598

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1307648/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1312255] Re: [systemd] nvidia-prime package needs systemd unit or init.d script

2014-06-05 Thread Jörn Schönyan

Just for my interest, would fixing this bug allow to use nvidia-prime in
upstream Debian?

Best regards

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1312255

Title:
  [systemd] nvidia-prime package needs systemd unit or init.d script

Status in “nvidia-prime” package in Ubuntu:
  Triaged

Bug description:
  With systemd as pid 1

  nvidia-prime package is pulled as a dependency of nvidia-331-updates package.
  When I tried to install the nvidia-331-updates package it gave me an error of 
installation on nvidia-prime due to

  "initctl: Unable to connect to Upstart: Failed to connect to socket
  /com/ubuntu/upstart: Connection refused"

  The full terminal stdout is

  Setting up nvidia-prime (0.6.2) ...
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  invoke-rc.d: unknown initscript, /etc/init.d/nvidia-prime not found.
  dpkg: error processing package nvidia-prime (--configure):
  subprocess installed post-installation script returned error exit status 100

  and at the end

  Errors were encountered while processing:
   nvidia-prime
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  This problem didn't prevent the nvidia-331-updates package from being
  installed. Nvidia driver installed properly and have worked as it
  should after a reboot, but the nvidia-prime "didn't make it".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 24 18:37:04 2014
  InstallationDate: Installed on 2014-03-24 (31 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1312255/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1204896] Re: onboard crashes on launch

2013-10-20 Thread Jörn Schönyan

I have double-checked that, librsvg2-common was the missing dependency.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1204896

Title:
  onboard crashes on launch

Status in Onboard on-screen keyboard:
  Confirmed
Status in “onboard” package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo with a touch screen. 
  When I launch Onboard, it crashes. It usually crashes on launch but I think 
there was one time where it didn't crash until I pressed the first key. 
  While I'm on the subject, could onboard be made a bit more user-friendly and 
simple? Like the iPad?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: onboard 0.99.0~alpha1~tr1190-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
  Uname: Linux 3.10.0-5-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Thu Jul 25 08:59:51 2013
  InstallationDate: Installed on 2013-07-06 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130703)
  MarkForUpload: True
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1204896/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1204896] Re: onboard crashes on launch

2013-10-19 Thread Jörn Schönyan

It works now, with librsvg2-common - but I am not 100% sure, if that
fixed it. If you want I can set up a VM tomorrow and check that. Just
for the records, the erase.svg:

joern@joern-notebook:~$ cat /usr/share/onboard/layouts/images/erase.svg 


http://www.w3.org/1999/02/22-rdf-syntax-ns#"; 
xmlns="http://www.w3.org/2000/svg"; height="16" width="16" version="1.1" 
xmlns:cc="http://creativecommons.org/ns#"; 
xmlns:dc="http://purl.org/dc/elements/1.1/";>
 
  
   
image/svg+xml
http://purl.org/dc/dcmitype/StillImage"/>

   
  
 
 
 
 


-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1204896

Title:
  onboard crashes on launch

Status in Onboard on-screen keyboard:
  New
Status in “onboard” package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo with a touch screen. 
  When I launch Onboard, it crashes. It usually crashes on launch but I think 
there was one time where it didn't crash until I pressed the first key. 
  While I'm on the subject, could onboard be made a bit more user-friendly and 
simple? Like the iPad?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: onboard 0.99.0~alpha1~tr1190-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
  Uname: Linux 3.10.0-5-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Thu Jul 25 08:59:51 2013
  InstallationDate: Installed on 2013-07-06 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130703)
  MarkForUpload: True
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1204896/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1204896] Re: onboard crashes on launch

2013-10-15 Thread Jörn Schönyan

I tried revision 1627 from the PPA (0.99.0+1627-0ppa~saucy1). I am
running Kubuntu Saucy in VirtualBox. And it is crashing for me, too. The
output from the terminal is:

htpc@htpc-VirtualBox:~$ onboard
Traceback (most recent call last):
  File "/usr/bin/onboard", line 16, in 
ob = Onboard()
  File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 111, in 
__init__
self.init()
  File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 210, in init
self.keyboard_widget.set_startup_visibility()
  File "/usr/lib/python3/dist-packages/Onboard/KeyboardWidget.py", line 327, in 
set_startup_visibility
self.commit_transition()
  File "/usr/lib/python3/dist-packages/Onboard/KeyboardWidget.py", line 546, in 
commit_transition
self._on_transition_step()
  File "/usr/lib/python3/dist-packages/Onboard/KeyboardWidget.py", line 583, in 
_on_transition_step
window.set_visible(visible)
  File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 288, in 
set_visible
self._show_first_time()
  File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 169, in 
_show_first_time
self.pre_render_keys(*self.get_size())
  File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 178, in 
pre_render_keys
self.keyboard_widget.pre_render_keys(self, w, h)
  File "/usr/lib/python3/dist-packages/Onboard/KeyboardWidget.py", line 345, in 
pre_render_keys
self.render(context)
  File "/usr/lib/python3/dist-packages/Onboard/LayoutView.py", line 204, in 
render
item.draw_cached(context)
  File "/usr/lib/python3/dist-packages/Onboard/KeyGtk.py", line 128, in 
draw_cached
surface = self._create_key_surface(context)
  File "/usr/lib/python3/dist-packages/Onboard/KeyGtk.py", line 147, in 
_create_key_surface
self.draw(context)
  File "/usr/lib/python3/dist-packages/Onboard/KeyGtk.py", line 155, in draw
self.draw_image(context, lod)
  File "/usr/lib/python3/dist-packages/Onboard/KeyGtk.py", line 483, in 
draw_image
pixbuf = self.get_image(rect.w, rect.h)
  File "/usr/lib/python3/dist-packages/Onboard/KeyGtk.py", line 709, in 
get_image
new_from_file_at_size(filename, width, height)
gi._glib.GError: Unrecognized image file format

I don't know where I can find the log files - so I've written
print(filename) in an appropiate place. The image file mentioned is
/usr/share/onboard/layouts/images/erase.svg, I hope that helps.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1204896

Title:
  onboard crashes on launch

Status in Onboard on-screen keyboard:
  New
Status in “onboard” package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo with a touch screen. 
  When I launch Onboard, it crashes. It usually crashes on launch but I think 
there was one time where it didn't crash until I pressed the first key. 
  While I'm on the subject, could onboard be made a bit more user-friendly and 
simple? Like the iPad?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: onboard 0.99.0~alpha1~tr1190-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
  Uname: Linux 3.10.0-5-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Thu Jul 25 08:59:51 2013
  InstallationDate: Installed on 2013-07-06 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130703)
  MarkForUpload: True
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1204896/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1388901] [NEW] nvidia-prime fails to switch profiles (alternatives related)

[Desktop-packages] [Bug 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia

[Desktop-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop

[Desktop-packages] [Bug 941826] Re: PyQt cannot compile shaders with Ubuntu's Nvidia drivers

[Desktop-packages] [Bug 1307648] Re: chromium 34 from proposed does not take input from keyboard in first entry point on several webpages

[Desktop-packages] [Bug 1312255] Re: [systemd] nvidia-prime package needs systemd unit or init.d script

[Desktop-packages] [Bug 1204896] Re: onboard crashes on launch

[Desktop-packages] [Bug 1204896] Re: onboard crashes on launch

[Desktop-packages] [Bug 1204896] Re: onboard crashes on launch

9 matches

Site Navigation

Mail list logo

Footer information