[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens + zesty debdiff
Great, thanks Jeremy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1572331 Title: GtkPlug scaled to half the expected size on HiDPI screens + zesty debdiff Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Committed Bug description: Hi, Marmuta wrote a patch for this issue, that I applied to the gtk+3.0 package shipping currently in the development version of Ubuntu zesty. You will find the corresponding debdiff attached to this bug thread. Marmuta performed tests with org.gnome.desktop.interface scaling- factor = 2 , where few issues are left for Onboard on hidpi screens, that are not related to gtk, but rather to unity-greeter or gnome- screensaver. He did not notice any issue with scaling-factor = 1. Can a sponsor please review the debdiff? Thanks in advance. Francesco = Original description: See attached screen shot. Blue is a GtkPlug, black is a GtkSocket. Source code below. What I expect to happen is that the GtkPlug has the same size as the GtkSocket. What actually happens is that GtkPlug only covers a quarter of the area of the GtkSocket. Impact: Onboard on HiDPI displays is near unusable at login and lock screen, aka unity-greeter and gnome-screensaver. Original bug report here: https://bugs.launchpad.net/bugs/1562734. Steps to reproduce: - build plug and socket samples from below - set display scaling factor to 2 System Settings -> Display -> Scale for menu and title bars = 2 - run ./socket $(head -1 <(./plug)) -> blue GtkPlug is too small, it should cover all the black - resize the window -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's wrong again ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 01:48:50 2016 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1572331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens + zesty debdiff
The bug has reappeared, I see it on each login again. The patch was added in 3.22.5-1ubuntu2, but then apparently removed again in 3.22.6-1ubuntu1. No mention in the changelog. Have there been regressions? ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1572331 Title: GtkPlug scaled to half the expected size on HiDPI screens + zesty debdiff Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Hi, Marmuta wrote a patch for this issue, that I applied to the gtk+3.0 package shipping currently in the development version of Ubuntu zesty. You will find the corresponding debdiff attached to this bug thread. Marmuta performed tests with org.gnome.desktop.interface scaling- factor = 2 , where few issues are left for Onboard on hidpi screens, that are not related to gtk, but rather to unity-greeter or gnome- screensaver. He did not notice any issue with scaling-factor = 1. Can a sponsor please review the debdiff? Thanks in advance. Francesco = Original description: See attached screen shot. Blue is a GtkPlug, black is a GtkSocket. Source code below. What I expect to happen is that the GtkPlug has the same size as the GtkSocket. What actually happens is that GtkPlug only covers a quarter of the area of the GtkSocket. Impact: Onboard on HiDPI displays is near unusable at login and lock screen, aka unity-greeter and gnome-screensaver. Original bug report here: https://bugs.launchpad.net/bugs/1562734. Steps to reproduce: - build plug and socket samples from below - set display scaling factor to 2 System Settings -> Display -> Scale for menu and title bars = 2 - run ./socket $(head -1 <(./plug)) -> blue GtkPlug is too small, it should cover all the black - resize the window -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's wrong again ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 01:48:50 2016 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1572331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens
Upstream bug report here: https://bugzilla.gnome.org/show_bug.cgi?id=765327 ** Bug watch added: GNOME Bug Tracker #765327 https://bugzilla.gnome.org/show_bug.cgi?id=765327 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1572331 Title: GtkPlug scaled to half the expected size on HiDPI screens Status in gtk+3.0 package in Ubuntu: New Bug description: See attached screen shot. Blue is a GtkPlug, black is a GtkSocket. Source code below. What I expect to happen is that the GtkPlug has the same size as the GtkSocket. What actually happens is that GtkPlug only covers a quarter of the area of the GtkSocket. Impact: Onboard on HiDPI displays is near unusable at login and lock screen, aka unity-greeter and gnome-screensaver. Original bug report here: https://bugs.launchpad.net/bugs/1562734. Steps to reproduce: - build plug and socket samples from below - set display scaling factor to 2 System Settings -> Display -> Scale for menu and title bars = 2 - run ./socket $(head -1 <(./plug)) -> blue GtkPlug is too small, it should cover all the black - resize the window -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's wrong again ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 01:48:50 2016 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens
** Attachment added: "socket.c" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+attachment/4640244/+files/socket.c -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1572331 Title: GtkPlug scaled to half the expected size on HiDPI screens Status in gtk+3.0 package in Ubuntu: New Bug description: See attached screen shot. Blue is a GtkPlug, black is a GtkSocket. Source code below. What I expect to happen is that the GtkPlug has the same size as the GtkSocket. What actually happens is that GtkPlug only covers a quarter of the area of the GtkSocket. Impact: Onboard on HiDPI displays is near unusable at login and lock screen, aka unity-greeter and gnome-screensaver. Original bug report here: https://bugs.launchpad.net/bugs/1562734. Steps to reproduce: - build plug and socket samples from below - set display scaling factor to 2 System Settings -> Display -> Scale for menu and title bars = 2 - run ./socket $(head -1 <(./plug)) -> blue GtkPlug is too small, it should cover all the black - resize the window -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's wrong again ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 01:48:50 2016 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1572331] [NEW] GtkPlug scaled to half the expected size on HiDPI screens
Public bug reported: See attached screen shot. Blue is a GtkPlug, black is a GtkSocket. Source code below. What I expect to happen is that the GtkPlug has the same size as the GtkSocket. What actually happens is that GtkPlug only covers a quarter of the area of the GtkSocket. Impact: Onboard on HiDPI displays is near unusable at login and lock screen, aka unity-greeter and gnome-screensaver. Original bug report here: https://bugs.launchpad.net/bugs/1562734. Steps to reproduce: - build plug and socket samples from below - set display scaling factor to 2 System Settings -> Display -> Scale for menu and title bars = 2 - run ./socket $(head -1 <(./plug)) -> blue GtkPlug is too small, it should cover all the black - resize the window -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's wrong again ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 01:48:50 2016 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "layout-failure.jpg" https://bugs.launchpad.net/bugs/1572331/+attachment/4640239/+files/layout-failure.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1572331 Title: GtkPlug scaled to half the expected size on HiDPI screens Status in gtk+3.0 package in Ubuntu: New Bug description: See attached screen shot. Blue is a GtkPlug, black is a GtkSocket. Source code below. What I expect to happen is that the GtkPlug has the same size as the GtkSocket. What actually happens is that GtkPlug only covers a quarter of the area of the GtkSocket. Impact: Onboard on HiDPI displays is near unusable at login and lock screen, aka unity-greeter and gnome-screensaver. Original bug report here: https://bugs.launchpad.net/bugs/1562734. Steps to reproduce: - build plug and socket samples from below - set display scaling factor to 2 System Settings -> Display -> Scale for menu and title bars = 2 - run ./socket $(head -1 <(./plug)) -> blue GtkPlug is too small, it should cover all the black - resize the window -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's wrong again ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 01:48:50 2016 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens
build with: gcc -o plug plug.c `pkg-config --cflags --libs gtk+-3.0` gcc -o socket socket.c `pkg-config --cflags --libs gtk+-3.0` run e.g. as: ./socket $(head -1 <(./plug)) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1572331 Title: GtkPlug scaled to half the expected size on HiDPI screens Status in gtk+3.0 package in Ubuntu: New Bug description: See attached screen shot. Blue is a GtkPlug, black is a GtkSocket. Source code below. What I expect to happen is that the GtkPlug has the same size as the GtkSocket. What actually happens is that GtkPlug only covers a quarter of the area of the GtkSocket. Impact: Onboard on HiDPI displays is near unusable at login and lock screen, aka unity-greeter and gnome-screensaver. Original bug report here: https://bugs.launchpad.net/bugs/1562734. Steps to reproduce: - build plug and socket samples from below - set display scaling factor to 2 System Settings -> Display -> Scale for menu and title bars = 2 - run ./socket $(head -1 <(./plug)) -> blue GtkPlug is too small, it should cover all the black - resize the window -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's wrong again ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 01:48:50 2016 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens
** Attachment added: "gcc -o plug plug.c -O0 -g `pkg-config --cflags --libs gtk+-3.0`" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+attachment/4640243/+files/plug.c -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1572331 Title: GtkPlug scaled to half the expected size on HiDPI screens Status in gtk+3.0 package in Ubuntu: New Bug description: See attached screen shot. Blue is a GtkPlug, black is a GtkSocket. Source code below. What I expect to happen is that the GtkPlug has the same size as the GtkSocket. What actually happens is that GtkPlug only covers a quarter of the area of the GtkSocket. Impact: Onboard on HiDPI displays is near unusable at login and lock screen, aka unity-greeter and gnome-screensaver. Original bug report here: https://bugs.launchpad.net/bugs/1562734. Steps to reproduce: - build plug and socket samples from below - set display scaling factor to 2 System Settings -> Display -> Scale for menu and title bars = 2 - run ./socket $(head -1 <(./plug)) -> blue GtkPlug is too small, it should cover all the black - resize the window -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's wrong again ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 01:48:50 2016 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432428] Re: unity-panel-service crashes when clicking onboard indicator
** Also affects: at-spi2-atk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1432428 Title: unity-panel-service crashes when clicking onboard indicator Status in at-spi2-atk package in Ubuntu: New Status in onboard package in Ubuntu: New Bug description: When clicking the onboard indicator for the first time (after starting onboard), it can cause a crash of unity-panel-service. I never got crashes of unity-panel-service in connection with other indicators or applications, so I suppose it is something specific to the way how onboard creates its indicator. Apport is regularly collecting the information for this crash, but then it quietly disappears, without telling me whether the crash was automatically reported and to where. Unfortunately I don't have any references / bug report numbers etc. but I have a file _usr_lib_unity_unity-panel-service.1000.crash (13MB) that apport apparently created (I don't which format it is). I was hoping there is a chance someone here could find out more than when I report it to unity, because it happens very specifically when using onboard. How can I get more debug info, or is the crash file of any help? Ubuntu 14.10 64bit onboard 1.1.0+1949-0ppa1~utopic unity 7.3.1+14.10.20141016-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1432428/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1221397] Re: python3.3 crashed with SIGSEGV in g_object_ref()
** Also affects: at-spi2-atk (Ubuntu) Importance: Undecided Status: New ** Changed in: onboard Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1221397 Title: python3.3 crashed with SIGSEGV in g_object_ref() Status in Onboard on-screen keyboard: Invalid Status in at-spi2-atk package in Ubuntu: New Status in onboard package in Ubuntu: New Bug description: Error came up after login ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: python3.3-minimal 3.3.2-3ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.10-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sat Aug 31 17:48:57 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/python3.3 InstallationDate: Installed on 2013-08-31 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829) MarkForUpload: True ProcCmdline: python3 -cfrom\ Onboard.settings\ import\ Settings s\ =\ Settings(False) SegvAnalysis: Segfault happened at: 0x7f86f40259d1 : cmpq $0x50,(%rax) PC (0x7f86f40259d1) ok source "$0x50" ok destination "(%rax)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: python3.3 StacktraceTop: g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: python3.3 crashed with SIGSEGV in g_object_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1221397/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1219244] Re: onboard crashed with SIGSEGV in cache_process_state_changed()
Seth and the other reporters, are these segfaults still happening? The bug report and duplicates were for Ubuntu 13.10. There were no new reports past Saucy. ** Changed in: onboard (Ubuntu) Status: New => Incomplete ** Changed in: at-spi2-core (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1219244 Title: onboard crashed with SIGSEGV in cache_process_state_changed() Status in Onboard on-screen keyboard: Invalid Status in at-spi2-core package in Ubuntu: Incomplete Status in onboard package in Ubuntu: Incomplete Bug description: persistant bug, keep shutting down ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: onboard 0.99.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sat Aug 31 19:21:42 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/onboard InstallationDate: Installed on 2013-08-31 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3.3 /usr/bin/onboard SegvAnalysis: Segfault happened at: 0x7f2111376cc5 <_atspi_dbus_handle_event+789>: mov 0x50(%rdx),%rdi PC (0x7f2111376cc5) ok source "0x50(%rdx)" (0x0050) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: onboard StacktraceTop: _atspi_dbus_handle_event () from /usr/lib/x86_64-linux-gnu/libatspi.so.0 _atspi_process_deferred_messages () from /usr/lib/x86_64-linux-gnu/libatspi.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: onboard crashed with SIGSEGV in _atspi_dbus_handle_event() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1219244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1219244] Re: onboard crashed with SIGSEGV in cache_process_state_changed()
** Also affects: at-spi2-core (Ubuntu) Importance: Undecided Status: New ** Changed in: onboard Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1219244 Title: onboard crashed with SIGSEGV in cache_process_state_changed() Status in Onboard on-screen keyboard: Invalid Status in at-spi2-core package in Ubuntu: New Status in onboard package in Ubuntu: New Bug description: persistant bug, keep shutting down ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: onboard 0.99.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sat Aug 31 19:21:42 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/onboard InstallationDate: Installed on 2013-08-31 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3.3 /usr/bin/onboard SegvAnalysis: Segfault happened at: 0x7f2111376cc5 <_atspi_dbus_handle_event+789>: mov 0x50(%rdx),%rdi PC (0x7f2111376cc5) ok source "0x50(%rdx)" (0x0050) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: onboard StacktraceTop: _atspi_dbus_handle_event () from /usr/lib/x86_64-linux-gnu/libatspi.so.0 _atspi_process_deferred_messages () from /usr/lib/x86_64-linux-gnu/libatspi.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: onboard crashed with SIGSEGV in _atspi_dbus_handle_event() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1219244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
