[Desktop-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
** Branch linked: lp:~gerboland/qtmir/nouveau-workaround -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mir: Confirmed Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Confirmed Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
I've an ancient NVidia box at home, can try it out. I'm attaching patches for qtubuntu/qtmir to force Qt to use single threaded GL on nouveau. ** Branch linked: lp:~gerboland/qtubuntu/nouveau-workaround -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mir: Confirmed Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Confirmed Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1553328] Re: Mir/Unity8 crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
I have Qt configured (in QtUbuntu/QtMir) to use multi-threaded GL rendering, so we're probably hitting Nouveau's limitations here. As workaround, I can add code to QtUbuntu/QtMir use single-threaded GL for Nouveau. If this is easily reproduced, can you try initctl set-env --global QSG_RENDER_LOOP=basic and see if everything is more stable? If so, the workaround should do the trick ** Changed in: qtmir (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8 crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Incomplete Status in Mir: Invalid Status in Nouveau Xorg driver: Unknown Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Incomplete Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1553328] Re: Mir/Unity8 crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
Actually, might be easier/more-reliable just to edit /etc/environment and add "QSG_RENDER_LOOP=basic" and restart. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8 crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Incomplete Status in Mir: Invalid Status in Nouveau Xorg driver: Unknown Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Incomplete Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1670717] Re: Unity8/mir working on VMware due to bypass not working
Probably also relevant: https://bugs.launchpad.net/mir/+bug/1560498 ** Tags added: unity8-desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1670717 Title: Unity8/mir working on VMware due to bypass not working Status in mesa package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Related to this bug (bug #1480755) - this is the issue preventing unity8/mir working in VMware. Bringing it out into its own issue to improve visibility. Choice quotes from previous bug: The problem is (annoyingly) that Mesa 10.5.9 on wily (Intel Haswell) returns 7 compatible EGLConfigs for EGL_ALPHA_SIZE=0 but all of them have EGL_ALPHA_SIZE == 8 set. Added a Mesa task. RAOF has suggested we should just fix Mesa. When asking for RGBA of 8880 it should provide at least one EGLConfig that is 8880 instead of always . This should be possible. It's not entirely clear why we're not getting XRGB visuals currently, but it's fixable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1670717/+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 1583088] Re: Randomly corrupt font / text / characters in Unity8
Here is what Qt is doing, on upload: https://code.woboq.org/qt5/qtdeclarative/src/quick/scenegraph/qsgdefaultdistancefieldglyphcache.cpp.html#158 It saves & restores the alignment, and assumes the default alignment of 4 for drawing. IMO Mir isn't playing along, as it changes the alignment but does not restore it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt font / text / characters in Unity8 Status in Canonical System Image: In Progress Status in Mir: Won't Fix Status in gnome-desktop package in Ubuntu: Invalid Status in mir package in Ubuntu: Won't Fix Status in qtdeclarative-opensource-src package in Ubuntu: New Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Corrupted characters in text rendering. Only happens after starting non-GL application, like GTK application or mir_demo_client_fingerpaint. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1393578] Re: Subpixel order not included in Mir display information
I've hacked qtmir to print the subpixel hint that Mir is supplying. http://pastebin.ubuntu.com/24007971/ is my output. First I run a simple qml demo shell as nested server under USC, get "0" hint. Then I run again as host server, get a hint "1 = RGB". The "Subpixel hint" output of the 2 cases do not match for me, hence the complaint. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1393578 Title: Subpixel order not included in Mir display information Status in Mir: In Progress Status in QtMir: Triaged Status in qtubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Bug description: Just capturing something mentioned by Trevinho on IRC this morning. MirDisplayOutput does not include subpixel ordering, it could and should though. The information is exposed on the drm side (drmModeSubPixel). Marking as wishlist in absence of other information. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1393578/+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 1393578] Re: Subpixel order not included in Mir display information
Just testing it now, AFAICS a nested server is not getting the correct subpixel data passed to it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1393578 Title: Subpixel order not included in Mir display information Status in Mir: In Progress Status in QtMir: Triaged Status in qtubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Bug description: Just capturing something mentioned by Trevinho on IRC this morning. MirDisplayOutput does not include subpixel ordering, it could and should though. The information is exposed on the drm side (drmModeSubPixel). Marking as wishlist in absence of other information. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1393578/+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 1536751] Re: Font/text rendering is irregular and not pixel-aligned on low DPI screens
UITK already using NativeRendering for text when GU<10. Text *might* be improved by setting Qt's DPI and sub-pixel rendering hints correctly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1536751 Title: Font/text rendering is irregular and not pixel-aligned on low DPI screens Status in Canonical System Image: Confirmed Status in fontconfig package in Ubuntu: Incomplete Status in freetype package in Ubuntu: Incomplete Status in harfbuzz package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Incomplete Status in qtdeclarative-opensource-src package in Ubuntu: New Status in ubuntu-font-family-sources package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: This is a Dell Vostro 3550 laptop with a fresh install of 16.04 and unity8 Mir session the version of qtdeclarative5-qtmir-plugin is 0.4.7+16.04.20160104-0ubuntu1 As you can see from the screenshots the text has low details and, in the case of indicators descriptions at the top, almost disappears. The text could be fixed by using Text.NativeRendering instead of Text.QtRendering for the QML labels on low dpi screens, although text doesn't seem to be the only issue here. The icons are definitely lacking detail as well (QML Image's smoothing is enabled maybe?). Also the dots of the infographic don't look like circles at all, they're missing pixels and many of them look like a C more than an O. It looks to me like something is setting the wrong resolution, because it looks quite bad. But the screenshots are 1366x768 so I think that's not the case. NOTE: Unity7 looks perfectly fine and detailed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536751/+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 1583088] Re: Randomly corrupt font / text / characters in Unity8
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt font / text / characters in Unity8 Status in Canonical System Image: Confirmed Status in gnome-desktop package in Ubuntu: Invalid Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Corrupted characters in text rendering. Only happens after starting non-GL application, like GTK application or mir_demo_client_fingerpaint. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1583088] Re: Randomly corrupt font / text / characters in Unity8
@vanvugt you were right that glPixelStorei was to blame. In ShmBuffer Mir uses glPixelStorei to change the GL_UNPACK_ALIGNMENT from 4 (that Qt set) to 1 (that Mir sets, as it is more careful about stride). Mir fails to restore the state the Qt set, which broke Qt's rendering from then on. ShmBuffer only used for clients that do not use GL to draw, so Gtk and mir demos like fingerpaint, which is why this bug was "random" Could Mir be patched to revert any GL state changes it makes, when called into by Qt? ** Changed in: unity8 (Ubuntu) Status: Confirmed => Invalid ** Changed in: qtmir (Ubuntu) Status: Confirmed => In Progress ** Changed in: qtmir (Ubuntu) Assignee: (unassigned) => Gerry Boland (gerboland) ** Description changed: - Corrupted characters in text rendering, mainly in Unity8 window - titlebars. + Corrupted characters in text rendering. - I think this is a new issue. It only started happening (on xenial - desktop) in the past month or two. + Only happens after starting non-GL application, like GTK application or + mir_demo_client_fingerpaint. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt font / text / characters in Unity8 Status in Canonical System Image: Confirmed Status in gnome-desktop package in Ubuntu: Invalid Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Corrupted characters in text rendering. Only happens after starting non-GL application, like GTK application or mir_demo_client_fingerpaint. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1583088] Re: Randomly corrupt font / text / characters in Unity8
I'm looking into this now. I took an api trace of some simple font rendering by Qt on Mir showing the problem, and executed it on my X11 session. It renders ok on X11. Reading through the apitrace, Qt seems to be doing the right thing. I suspect the mismatch we have between Mir creating a GLES context and Qt expecting a GL context is hitting us here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt font / text / characters in Unity8 Status in Canonical System Image: Confirmed Status in gnome-desktop package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Corrupted characters in text rendering, mainly in Unity8 window titlebars. I think this is a new issue. It only started happening (on xenial desktop) in the past month or two. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1583088] Re: Randomly corrupt font / text / characters in Unity8
@kgunn - yes I can reproduce it quite reliably too. No need to try the glyph cache workaround thing, I checked it and it had no impact. @duflu - Qt is rendering the text. Since Qt renders text ok in Unity7, there must be some GL configuration problem in QtMir/QtUbuntu causing this kind of issue. At the moment, I've not really dug into why. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt font / text / characters in Unity8 Status in Canonical System Image: Confirmed Status in gnome-desktop package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Corrupted characters in text rendering, mainly in Unity8 window titlebars. I think this is a new issue. It only started happening (on xenial desktop) in the past month or two. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1638929] Re: after disabling a display, enabling makes screens go black
Yeah the unity8 log makes me suspect qtmir, it deals with disabling the display ok, but enabling it doesn't yield 2 screens again ** Also affects: qtmir Importance: Undecided Status: New ** Changed in: qtmir Status: New => Confirmed ** Changed in: qtmir Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1638929 Title: after disabling a display, enabling makes screens go black Status in Canonical System Image: New Status in Light Display Manager: New Status in Mir: Incomplete Status in QtMir: Confirmed Status in lightdm package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Reproduce: turn off then turn on some display (output.used = false then output.used = true) What happens: Turning off works fine, turning it back on does not What should happen: it should work as expected USC log: http://pastebin.ubuntu.com/23420797/ Unity8 log: (see that mirserver: Disabled works fine) http://pastebin.ubuntu.com/23420803/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1638929/+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 1638929] Re: after disabling a display, enabling makes screens go black
QtMir/Unity8 is designed to deal with spanning displays - it is actually cloned displays it needs work to support! @jonas Could you give us a means to test this behaviour? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1638929 Title: after disabling a display, enabling makes screens go black Status in Canonical System Image: New Status in Light Display Manager: New Status in Mir: Incomplete Status in lightdm package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Reproduce: turn off then turn on some display (output.used = false then output.used = true) What happens: Turning off works fine, turning it back on does not What should happen: it should work as expected USC log: http://pastebin.ubuntu.com/23420797/ Unity8 log: (see that mirserver: Disabled works fine) http://pastebin.ubuntu.com/23420803/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1638929/+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 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")
Note it is only Unity8 which is mixing GL and GLES calls, clients are not doing that. Qt clients are only doing GL calls on desktop. Nothing obvious comes to mind here. It may be Qt's EGL configuration code is failing - code that QtUbuntu is using. Another consumer of that same code is the EGL backend for the XCB QPA plugin - the non-default - as usually the GLX backend is used. Could someone with a problematic system log into Unity7, and for a simple qml file, run: QT_XCB_GL_INTEGRATION=xcb_egl qmlscene ~/test.qml and see does it fail? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1620934 Title: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001") Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in QtMir: Confirmed Status in qtubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: nothing works, all apps, dash are just black windows - Ubuntu 16.10 + proposed (x86, and using Nvidia 8600GT with nouveau drivers) and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 3001" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620934/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Of course we will. We need to re-land the fix. It was reverted because it broke something else, but that's been solved now. Sorry for the delay, but it takes time to get things done just right. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1583088] Re: Randomly corrupt characters in Unity8
Also worth noting, there are env vars: QT_DEFAULT_TEXTURE_GLYPH_CACHE_WIDTH & HEIGHT to set the size of the glyph cache. Need to see what size texture Qt is creating, perhaps it is creating one too large for the hardware -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt characters in Unity8 Status in gnome-desktop package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Corrupted characters in text rendering, mainly in Unity8 window titlebars. I think this is a new issue. It only started happening (on xenial desktop) in the past month or two. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1583088/+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 1583088] Re: Randomly corrupt characters in Unity8
That would imply the distance field texture is corrupted. As a note to myself, there is a nice glyph test application in this bug: https://bugreports.qt.io/browse/QTBUG-49490 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt characters in Unity8 Status in gnome-desktop package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Corrupted characters in text rendering, mainly in Unity8 window titlebars. I think this is a new issue. It only started happening (on xenial desktop) in the past month or two. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1583088/+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 1583088] Re: Randomly corrupt characters in Unity8
If you can reproduce this relative easily, could you try setting QML_USE_GLYPHCACHE_WORKAROUND=1 for unity8. This should do the trick: stop unity8 && start unity8 QML_USE_GLYPHCACHE_WORKAROUND=1 Can also try these: QSG_DISTANCEFIELD_ANTIALIASING=subpixel-lowq or gray Need to determine if that text is being drawn by the DistanceField approach, or using the "native" rendering technique http://doc.qt.io/qt-5/qml-qtquick-text.html#renderType-prop If distance field, perhaps the contents of the distance field texture is corrupted somehow. Grabbing the contents of the texture to visually verify it is corrupt or not would be my next step. apitrace might be able to grab the texture. Else would need to write code.. ** Changed in: gnome-desktop (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt characters in Unity8 Status in gnome-desktop package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Corrupted characters in text rendering, mainly in Unity8 window titlebars. I think this is a new issue. It only started happening (on xenial desktop) in the past month or two. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1583088/+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 1393578] Re: Subpixel order not included in Mir display information
** Also affects: qtubuntu Importance: Undecided Status: New ** Changed in: qtubuntu Status: New => Triaged ** Changed in: qtubuntu Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1393578 Title: Subpixel order not included in Mir display information Status in Mir: Triaged Status in QtMir: Triaged Status in qtubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Bug description: Just capturing something mentioned by Trevinho on IRC this morning. MirDisplayOutput does not include subpixel ordering, it could and should though. The information is exposed on the drm side (drmModeSubPixel). Marking as wishlist in absence of other information. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1393578/+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 1393578] Re: Subpixel order not included in Mir display information
Adding QtMir as from Qt5.5 and later, the QPA plugin can specify the subpixel hinting to Qt's font renderer (is part of QPlatformScreen implementation). ** Also affects: qtmir Importance: Undecided Status: New ** Changed in: qtmir Status: New => Triaged ** Changed in: qtmir Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1393578 Title: Subpixel order not included in Mir display information Status in Mir: Triaged Status in QtMir: Triaged Status in xorg-server package in Ubuntu: Triaged Bug description: Just capturing something mentioned by Trevinho on IRC this morning. MirDisplayOutput does not include subpixel ordering, it could and should though. The information is exposed on the drm side (drmModeSubPixel). Marking as wishlist in absence of other information. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1393578/+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 1585942] Re: Mesa causes a segmentation fault on arm64 (wrong count of uniform locations)
arm64? Should it not be using a hybris-based driver instead of mesa?
What hardware is this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1585942
Title:
Mesa causes a segmentation fault on arm64 (wrong count of uniform
locations)
Status in mesa package in Ubuntu:
Confirmed
Bug description:
This error appeared when running unit tests for a QML app in out
Jenkins infrastructure, on arm64 only:
https://launchpadlibrarian.net/261581280/buildlog_ubuntu-yakkety-arm64
.ubuntu-system-settings-online-
accounts_0.7+16.10.20160525.1-0ubuntu1_BUILDING.txt.gz
Pasting the relevant lines here in case the link above goes away:
===
QT_PLUGIN_PATH=/usr/lib/aarch64-linux-gnu/qt5/plugins
LD_LIBRARY_PATH=/usr/lib/aarch64-linux-gnu${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
xvfb-run -s '-screen 0 640x480x24' -a dbus-test-runner -t
./tst_online_accounts_qml
DBus daemon:
unix:abstract=/tmp/dbus-2tbhBHxLZq,guid=03f9df417d619b79067a68045745ad95
task-0: Started with PID: 16930
task-0: * Start testing of online_accounts_qml *
task-0: Config: Using QtTest library 5.5.1, Qt 5.5.1
(arm64-little_endian-lp64 shared (dynamic) release build; by GCC 5.3.1 20160519)
task-0: PASS : online_accounts_qml::AccountCreationPage::initTestCase()
task-0: QWARN : online_accounts_qml::AccountCreationPage::test_fallback()
file:///dummy/path/testPlugin/Main.qml: File not found
task-0: PASS : online_accounts_qml::AccountCreationPage::test_fallback()
task-0: QWARN : online_accounts_qml::AccountCreationPage::test_flickable()
file:///dummy/path/testPlugin/Main.qml: File not found
task-0: PASS : online_accounts_qml::AccountCreationPage::test_flickable()
task-0: PASS : online_accounts_qml::AccountCreationPage::cleanupTestCase()
task-0: QWARN : online_accounts_qml::UnknownTestFunc() QEGLPlatformContext:
Failed to make temporary surface current, format not updated
task-0: PASS : online_accounts_qml::AuthorizationPage::initTestCase()
task-0: QWARN : online_accounts_qml::AuthorizationPage::test_1_one_account()
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:54:
TypeError: Cannot call method 'indexOf' of undefined
task-0: PASS : online_accounts_qml::AuthorizationPage::test_1_one_account()
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_2_add_another(with button)
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:54:
TypeError: Cannot call method 'indexOf' of undefined
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_2_add_another(with button)
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:79:23:
Unable to assign [undefined] to QString
task-0: PASS :
online_accounts_qml::AuthorizationPage::test_2_add_another(with button)
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_2_add_another(with button)
[PERFORMANCE]: Last frame took 254 ms to render.
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_2_add_another(without button)
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:54:
TypeError: Cannot call method 'indexOf' of undefined
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_2_add_another(without button)
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:79:23:
Unable to assign [undefined] to QString
task-0: PASS :
online_accounts_qml::AuthorizationPage::test_2_add_another(without button)
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_2_add_another(without button)
[PERFORMANCE]: Last frame took 210 ms to render.
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_3_many_accounts(first account)
[PERFORMANCE]: Last frame took 146 ms to render.
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_3_many_accounts(first account)
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:54:
TypeError: Cannot call method 'indexOf' of undefined
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_3_many_accounts(first account)
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:79:23:
Unable to assign [undefined] to QString
task-0: PASS :
online_accounts_qml::AuthorizationPage::test_3_many_accounts(first account)
Mesa 11.2.1 implementation error: Failed to link fixed function fragment
shader: error: count of uniform locations > MAX_UNIFORM_LOCATIONS(4294967295 >
98304)
Please report
[Desktop-packages] [Bug 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Yep. The branch has been approved, will take a while to get it landed. Note that it will be almost unusable until bug 1585723 is resolved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
@Emanuele yes I did - but only via SSH. A colleague will verify it works visually before approving -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
I've updated the attached branch with my proposed fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Using simple test apps (lp:~gerboland/+junk/openglwindow & lp:~gerboland/+junk/qquickwindow-debug), it appears that yes Qt is using OpenGL 1.4 on X for both raw GL and QtQuick apps. ./qquickwindow-debug Window format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 1, profile 0) Context format: QSurfaceFormat(version 1.4, options QFlags(0x4), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 1, profile 0) GLES: false The "Context format: ... version 1.4" the thing to look for. The EGL backend for Qt (X uses the GLX backend) is requiring OpenGl2 or greater (since that is what the Window is asking for), but the GLX backend seems to ignore that request, and just work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
/me has to stop using "Ok, " at the start of his sentences -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Ok, I suspect I have found the issue. Seems this hardware only supports OpenGL 1.4 compatibility profile. Qt's EGL code is asking for at least version 2.0, and so getting no valid context back. Could you please install "mesa-utils" package and run "glxinfo". On the hardware I have access to, I see these lines in the output: Preferred profile: compat (0x2) Max core profile version: 0.0 Max compat profile version: 1.4 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 2.0 I need to figure out why the X11 glx code is working, but the EGL code is not. I also need to understand why at least OpenGL2.0 is desired by Qt. An option is to use GLES2 on this hardware, but as the GL/GLES switch is made in Qt at compile time, that won't be straightforward either. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Ok, I figured out hte EGL issue, it was my misunderstanding. Modifying the tools to act correctly, I get this for eglinfo: http://pastebin.ubuntu.com/16686113/ and the qteglchooser correctly chooses a valid Mir EGL config. Why Qt itself cannot do this, I have yet to understand. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Ok, progress, my tools can exhibit the problem: http://pastebin.ubuntu.com/16677278/ Problems include: 1. libEGL warning: DRI3: xcb_connect failed<- should not be trying that 2. EGL version: 8.-1225087968<- this is garbage I suspect that there is an issue with EGL. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Forgot to say, that was reproduced running the qteglchooser while there was no X server running, instead just a Mir server running. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Hey Emanuele, Albert got me the data I wanted from those tools, and the results are still inconclusive. I think I need access to the hardware to make real progress on this. So there's no need to bother with the trying those tools. If you fancy a go, just to play: 1. Install build dependencies (I don't know if I have all here): sudo apt install bzr build-essential qtbase5-dev qtbase5-private-dev 2. Download the code: bzr branch lp:~gerboland/+junk/qteglchooser/ cd qteglchooser/ 3. Compile: qmake make You should get a qteglchooser binary, that you can then run as above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Hi Emanuele, you attached a branch of mine to this bug - it makes our GL/EGL managing code more robust. I had hoped it would fix this issue, but unfortunately it doesn't. That's why I didn't attach that branch to this bug. Annoyingly I don't have the hardware to hand either, so I'm flying slightly blind. I make a change, then ask someone else to test it. I'll have access to the hardware in about 2 weeks time, hopefully I'll have a breakthrough then. In the mean time, I've assembled some diagnostic applications that might help me out. If you're feeling adventurous, grab and compile lp:~gerboland/+junk/qteglchooser/ Run it with ./qteglchooser -o and ./qteglchooser -o -i and pastebin me the output. It's a tool I made to try explain how Qt is deciding which EGL configuration to use. Qt can end up jumping through many hoops figuring out a good EGL config, but also I might be using it slightly wrong (hence the -i switch). I would also appreciate if you could please grab, compile, run and pastebin me the output of lp:~gerboland/+junk/eglinfo That just prints the EGL configurations available, plus other EGL stuff. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Qt clients on Intel Pineview graphics fail to create egl context with Mir
http://paste.ubuntu.com/16357238/ the output Qt gave me for the failing eglCreateContext -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Qt clients on Intel Pineview graphics fail to create egl context with Mir Status in Mir: Invalid Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Qt clients on Intel Pineview graphics fail to create egl context with Mir
Just considering the Dash problem, the crash is a symptom of a bigger problem: seems qtubuntu is unable to choose or manage the egl config correctly. If a correct/working egl config was chosen, then this code path wouldn't be entered (which has the "delete when not created" bug seen here). The actual problem is that eglCreateContext fails with EGL_BAD_MATCH on the problem hardware. I'm experimenting with lp:~gerboland/qtubuntu /adopt-more-eglconvenience2/ which uses Qt's EGL config choosing code (that works ok on X11) in case that works. I've update this bug title/description to match. You're right that the unity8 performance problem is a separate issue. I've logged bug 1580792 to encompass that. ** Summary changed: - Unity8-dash on Intel Pineview graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"] + Qt clients on Intel Pineview graphics fail to create egl context with Mir ** Description changed: + Qt clients are failing to create an egl context when running on Intel + Pineview systems under Mir. + + eglCreateContext fails with a EGL_BAD_MATCH error code. + + When it fails, Qt tries to delete & recreate the context, which then + crashes the client (bug 1580118) + + + === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Qt clients on Intel Pineview graphics fail to create egl context with Mir Status in Mir: Invalid Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Pineview graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
Albert was able to reproduce this on his netbook. The dash issues we suspect are due to: https://bugs.launchpad.net/qtubuntu/+bug/1580124 https://bugs.launchpad.net/qtubuntu/+bug/1580118 I suspect also that the poor unity8 performance is due to a GL/GLES mismatch in unity8. Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA errors: http://paste.ubuntu.com/16344427/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Pineview graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"] Status in Mir: Invalid Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1278780] Re: apport takes too long to write crash report, appears to lock up phone
** Changed in: qtubuntu Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1278780 Title: apport takes too long to write crash report, appears to lock up phone Status in Apport: Confirmed Status in Canonical System Image: Confirmed Status in qtubuntu: Invalid Status in apport package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Confirmed Bug description: I can trigger a crash easily on my phone via bug 1262711. Other bugs are available. When that happens my phone appears to freeze. I am unable to do anything for approximately 1 to 1.5 minutes. As a user my initial gut reaction is to reboot the phone, thus losing the crash report, and wasting my time. Having the phone lock up for 1.5 minutes is a terrible user experience. Can we fix/mitigate/workaround that? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.13.2-0ubuntu2 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.13.2-0ubuntu2 Architecture: armhf CrashReports: 664:32011:110:10083:2014-02-10 15:41:18.152893384 +:2014-02-10 15:11:09.169231740 +:/var/crash/_usr_lib_arm-linux-gnueabihf_upstart-app-launch_desktop-hook.32011.crash 640:0:110:1681527:2014-02-10 15:12:10.985193887 +:2014-02-10 15:12:05.639489630 +:/var/crash/_usr_bin_powerd.0.crash 640:0:110:21384:2014-02-11 07:58:44.876281991 +:2014-02-11 07:58:44.876281991 +:/var/crash/_usr_sbin_system-image-dbus.0.crash 640:32011:110:17122318:2014-02-11 09:19:49.915478726 +:2014-02-11 09:18:20.850439824 +:/var/crash/_usr_bin_unity8.32011.crash Date: Tue Feb 11 09:20:15 2014 InstallationDate: Installed on 2014-02-11 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140211) PackageArchitecture: all ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1278780/+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 1278780] Re: apport takes too long to write crash report, appears to lock up phone
Ok, task is for Qt clients to intercept the sigsegv signal, and in a handler close the mir connection which should release all its video buffers, then re-raise segv. Would it be of interest to have all mir clients exhibit this behaviour by default? If so, should put this behaviour in "mirclient" If just for Qt, then Qtubuntu. If unity8 crashes, there is the similar issue that it will hang until apport releases it. Mir/QtMir could gain similar ability to release its buffers before coredump, which would shrink the collected core. This could again be a Mir task. QtMir's ApplicationManager will need adjusting to allow new instance of app to be launched, while the old instance is dumping core. ** Also affects: qtubuntu Importance: Undecided Status: New ** Changed in: qtubuntu Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1278780 Title: apport takes too long to write crash report, appears to lock up phone Status in Apport: Confirmed Status in Canonical System Image: Confirmed Status in qtubuntu: Confirmed Status in apport package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Confirmed Bug description: I can trigger a crash easily on my phone via bug 1262711. Other bugs are available. When that happens my phone appears to freeze. I am unable to do anything for approximately 1 to 1.5 minutes. As a user my initial gut reaction is to reboot the phone, thus losing the crash report, and wasting my time. Having the phone lock up for 1.5 minutes is a terrible user experience. Can we fix/mitigate/workaround that? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.13.2-0ubuntu2 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.13.2-0ubuntu2 Architecture: armhf CrashReports: 664:32011:110:10083:2014-02-10 15:41:18.152893384 +:2014-02-10 15:11:09.169231740 +:/var/crash/_usr_lib_arm-linux-gnueabihf_upstart-app-launch_desktop-hook.32011.crash 640:0:110:1681527:2014-02-10 15:12:10.985193887 +:2014-02-10 15:12:05.639489630 +:/var/crash/_usr_bin_powerd.0.crash 640:0:110:21384:2014-02-11 07:58:44.876281991 +:2014-02-11 07:58:44.876281991 +:/var/crash/_usr_sbin_system-image-dbus.0.crash 640:32011:110:17122318:2014-02-11 09:19:49.915478726 +:2014-02-11 09:18:20.850439824 +:/var/crash/_usr_bin_unity8.32011.crash Date: Tue Feb 11 09:20:15 2014 InstallationDate: Installed on 2014-02-11 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140211) PackageArchitecture: all ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1278780/+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 1432358] Re: Highlighted items are unreadable
*** This bug is a duplicate of bug 1283634 *** https://bugs.launchpad.net/bugs/1283634 ** This bug has been marked a duplicate of bug 1283634 Text for selected applications in Ubuntu Software Center on Ubuntu Gnome is difficult to read -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1432358 Title: Highlighted items are unreadable Status in One Hundred Papercuts: Confirmed Status in software-center package in Ubuntu: Confirmed Bug description: Highlighted items are unreadable in Ubuntu GNOME when on the Software Center. I believe it is due to the current theme associated with Ubuntu GNOME. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: software-center 13.10-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 15 09:14:44 2015 InstallationDate: Installed on 2015-03-15 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 (20141022.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1432358/+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 1364462] [NEW] [multi-monitor setup] opening ubuntu-control-center causes monitors to re-set layout
Public bug reported: Using Utopic daily. I've a Macbook Pro 8,1 connected to an external monitor via HDMI. If I open the Control Center by any means (e.g. indicators-Sound-Sound Settings) the screen flickers, in the same was as if I unplugged/plugged in my external monitor. Then some application windows which was originally on the monitor is moved to the laptop screen - Firefox Terminal frequent culprits) Note this does not happen every time, is usually only if I open Control Center after several hours of not having used it. Is very annoying! ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1364462 Title: [multi-monitor setup] opening ubuntu-control-center causes monitors to re-set layout Status in “unity-control-center” package in Ubuntu: New Bug description: Using Utopic daily. I've a Macbook Pro 8,1 connected to an external monitor via HDMI. If I open the Control Center by any means (e.g. indicators-Sound-Sound Settings) the screen flickers, in the same was as if I unplugged/plugged in my external monitor. Then some application windows which was originally on the monitor is moved to the laptop screen - Firefox Terminal frequent culprits) Note this does not happen every time, is usually only if I open Control Center after several hours of not having used it. Is very annoying! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1364462/+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 1364462] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1364462/+attachment/4193361/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1364462 Title: [multi-monitor setup] opening ubuntu-control-center causes monitors to re-set layout Status in “unity-control-center” package in Ubuntu: New Bug description: Using Utopic daily. I've a Macbook Pro 8,1 connected to an external monitor via HDMI. If I open the Control Center by any means (e.g. indicators-Sound-Sound Settings) the screen flickers, in the same was as if I unplugged/plugged in my external monitor. Then some application windows which was originally on the monitor is moved to the laptop screen - Firefox Terminal frequent culprits) Note this does not happen every time, is usually only if I open Control Center after several hours of not having used it. Is very annoying! --- ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-26 (128 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) NonfreeKernelModules: wl Package: unity-control-center 14.10.0+14.10.20140702.1-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 SystemImageInfo: Error: [Errno 2] No such file or directory Tags: utopic Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-05-23 (102 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1364462/+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 1364462] Re: [multi-monitor setup] opening ubuntu-control-center causes monitors to re-set layout
apport information ** Tags added: apport-collected utopic ** Description changed: Using Utopic daily. I've a Macbook Pro 8,1 connected to an external monitor via HDMI. If I open the Control Center by any means (e.g. indicators-Sound-Sound Settings) the screen flickers, in the same was as if I unplugged/plugged in my external monitor. Then some application windows which was originally on the monitor is moved to the laptop screen - Firefox Terminal frequent culprits) Note this does not happen every time, is usually only if I open Control Center after several hours of not having used it. Is very annoying! + --- + ApportVersion: 2.14.7-0ubuntu1 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.10 + EcryptfsInUse: Yes + InstallationDate: Installed on 2014-04-26 (128 days ago) + InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) + NonfreeKernelModules: wl + Package: unity-control-center 14.10.0+14.10.20140702.1-0ubuntu3 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 + SystemImageInfo: Error: [Errno 2] No such file or directory + Tags: utopic + Uname: Linux 3.13.0-24-generic x86_64 + UpgradeStatus: Upgraded to utopic on 2014-05-23 (102 days ago) + UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo + _MarkForUpload: True + usr_lib_unity-control-center: + activity-log-manager 0.9.7-0ubuntu14 + deja-dup 30.0-0ubuntu7 ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1364462/+attachment/4193360/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1364462 Title: [multi-monitor setup] opening ubuntu-control-center causes monitors to re-set layout Status in “unity-control-center” package in Ubuntu: New Bug description: Using Utopic daily. I've a Macbook Pro 8,1 connected to an external monitor via HDMI. If I open the Control Center by any means (e.g. indicators-Sound-Sound Settings) the screen flickers, in the same was as if I unplugged/plugged in my external monitor. Then some application windows which was originally on the monitor is moved to the laptop screen - Firefox Terminal frequent culprits) Note this does not happen every time, is usually only if I open Control Center after several hours of not having used it. Is very annoying! --- ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-26 (128 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) NonfreeKernelModules: wl Package: unity-control-center 14.10.0+14.10.20140702.1-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 SystemImageInfo: Error: [Errno 2] No such file or directory Tags: utopic Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-05-23 (102 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1364462/+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 1288332] Re: Orientation lock not available (rotation/portrait lock)
** Branch linked: lp:~gerboland/platform-api/exposeOrientation ** Branch linked: lp:~gerboland/qtubuntu/exposeOrientation ** Branch linked: lp:~gerboland/qtmir/exposeOrientation ** Branch linked: lp:~gerboland/unity8/orientationLock -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-ubuntu-touch-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1288332 Title: Orientation lock not available (rotation/portrait lock) Status in Platform API: In Progress Status in Qt integration with the Mir display server: In Progress Status in QT Ubuntu: In Progress Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “ubuntu-ui-toolkit” package in Ubuntu: Opinion Status in “unity8” package in Ubuntu: Opinion Bug description: Ubuntu Trusty r188 1. Open System Settings. 2. Try to turn on Orientation Lock. What happens: There's no such setting. https://wiki.ubuntu.com/SystemSettings#phone-quick-access: The quick access area is a group of list items at the top of the overview screen. It should always contain 'Orientation Lock'... To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1288332/+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 1288332] Re: Orientation lock not available (rotation/portrait lock)
That's my plan. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-ubuntu-touch-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1288332 Title: Orientation lock not available (rotation/portrait lock) Status in Platform API: In Progress Status in Qt integration with the Mir display server: In Progress Status in QT Ubuntu: In Progress Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “ubuntu-ui-toolkit” package in Ubuntu: Opinion Status in “unity8” package in Ubuntu: Opinion Bug description: Ubuntu Trusty r188 1. Open System Settings. 2. Try to turn on Orientation Lock. What happens: There's no such setting. https://wiki.ubuntu.com/SystemSettings#phone-quick-access: The quick access area is a group of list items at the top of the overview screen. It should always contain 'Orientation Lock'... To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1288332/+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 1288332] Re: Orientation lock not available (rotation/portrait lock)
** Changed in: qtmir Status: Triaged = In Progress ** Changed in: platform-api Assignee: (unassigned) = Gerry Boland (gerboland) ** Changed in: qtubuntu Assignee: (unassigned) = Gerry Boland (gerboland) ** Changed in: platform-api Status: New = In Progress ** Changed in: qtubuntu Status: New = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-ubuntu-touch-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1288332 Title: Orientation lock not available (rotation/portrait lock) Status in Platform API: In Progress Status in Qt integration with the Mir display server: In Progress Status in QT Ubuntu: In Progress Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “ubuntu-ui-toolkit” package in Ubuntu: Opinion Status in “unity8” package in Ubuntu: Opinion Bug description: Ubuntu Trusty r188 1. Open System Settings. 2. Try to turn on Orientation Lock. What happens: There's no such setting. https://wiki.ubuntu.com/SystemSettings#phone-quick-access: The quick access area is a group of list items at the top of the overview screen. It should always contain 'Orientation Lock'... To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1288332/+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 1288332] Re: Orientation lock not available (rotation/portrait lock)
The orientation lock value (it needs to be one of the 4 available orientations to store and recover between sessions, for example) will be stored in gsettings, written to by settings app, reset by settings app and $indicator, TBC. I agree with everything except this bit. I think the GSetting API should be a boolean, orientation lock on/off. It will be up to shell to save the last locked orientation somewhere separately, and use that if session restored. Reason I propose this is: applications are not guaranteed to know the orientation of the shell/device. Main example is tablet side-stage apps: they will be told they're portrait (as they would be on the phone), but the device is actually landscape. IMO it really makes more sense for shell to just listen for an orientation lock on/off switch, and just do the right thing. I think otherwise there's a danger USS might choose the wrong orientation for shell to lock in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-ubuntu-touch-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1288332 Title: Orientation lock not available (rotation/portrait lock) Status in Platform API: In Progress Status in Qt integration with the Mir display server: In Progress Status in QT Ubuntu: In Progress Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “ubuntu-ui-toolkit” package in Ubuntu: Opinion Status in “unity8” package in Ubuntu: Opinion Bug description: Ubuntu Trusty r188 1. Open System Settings. 2. Try to turn on Orientation Lock. What happens: There's no such setting. https://wiki.ubuntu.com/SystemSettings#phone-quick-access: The quick access area is a group of list items at the top of the overview screen. It should always contain 'Orientation Lock'... To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1288332/+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 901164] Re: Dash - Update the Dash card view so that the implementation conforms to the attached designs
** Changed in: unity-2d Assignee: Gerry Boland (gerboland) = (unassigned) ** Changed in: unity-2d Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/901164 Title: Dash - Update the Dash card view so that the implementation conforms to the attached designs Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in Unity 2D: Won't Fix Status in “unity” package in Ubuntu: Fix Released Bug description: A 'card view' is currently used in the Gwibber lens, and also in some other 3rd party lenses. Update this view so that the shape, size and positioning of all elements exactly matches the attached designs. If the images in the card view are a mix of square and landscape icons, the text composed to the right of the icon should consist of: - 1 'header' line. Text automatically bold, lens has no control over styling - 3 'body' lines. Text regular style, only control the lens has over styling is the ability to make specific words or letters bold If the images in the card view are *only* landscape icons (e.g. in the Video Lens), the text composed to the right of the icon should consist of: - 1 'header' line. Text automatically bold, lens has no control over styling - 2 'body' lines. Text regular style, only control the lens has over styling is the ability to make specific words or letters bold To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/901164/+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 893966] Re: Dash - Update category header keyboard navigation focus state
** Changed in: unity-2d Assignee: Gerry Boland (gerboland) = (unassigned) ** Changed in: unity-2d Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/893966 Title: Dash - Update category header keyboard navigation focus state Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in Unity 2D: Won't Fix Status in “unity” package in Ubuntu: Fix Released Bug description: When using keyboard navigation of the dash, category headings only highlight the See X more results string when focussed. In cases when this string is not there (say 1-4 results), there is no visual indication of when this element gets focus. Steps to Repro 1. Open Dash 2. Perform a search where one of the categories has few enough elements to not be collapsible. 3. Hit down to highlight this Category Header. Expected Result Visual indication that this header is focussed Actual Result No visual indication. -- Desired resolution: see https://chinstrap.canonical.com/~sabdfl/12_04/desktop_and_netbook/dash/lens_category_header_select_v1-2.png for details of desired resolution. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/893966/+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 1008918] Re: wrong display in dashboard after first time clicking the dashboard button
** Changed in: unity-2d Assignee: Gerry Boland (gerboland) = (unassigned) ** Changed in: unity-2d Status: In Progress = Won't Fix ** Changed in: unity-2d (Ubuntu) Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity, dp-unity2d https://bugs.launchpad.net/bugs/1008918 Title: wrong display in dashboard after first time clicking the dashboard button Status in Unity 2D: Won't Fix Status in “unity” package in Ubuntu: Invalid Status in “unity-2d” package in Ubuntu: Won't Fix Status in “unity” source package in Quantal: Invalid Bug description: Daily build ISO version: Jun 4 18:37 quantal-desktop-amd64.iso Jun 4 18:39 quantal-desktop-i386.iso Description: 1. Install the iso in some virtual machine 2. After the installation,login the system, and click the dashboard button 3. the dashbaord will be displayed with some words : there is nothing matching your search. it's not right, the recent apps, recent files... should be displayed in the dashboard instead of the words. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/1008918/+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 928145] Re: When using option switch between windows of same desktop (Bias alt-tab to prefer windows on the current viewport) if multi-window app is open pressing alt-tab w
This is highly irritating. Steps to repro: 1. Have 2 firefox windows open, and 1 terminal. Firefox window 1 is focused. 2. Hit Alt-` to switch to Firefox window 2 3. Hit Alt-Tab. Expected result Terminal is in front Actual Result Firefox window 1 in front Since Alt-Tab is the app switcher, and Alt-backtick is in-app window switching, this behaviour is totally wrong. I'm re-opening this bug. ** Changed in: unity Status: Incomplete = New ** Changed in: unity (Ubuntu) Status: Incomplete = Opinion ** Changed in: unity (Ubuntu) Status: Opinion = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/928145 Title: When using option switch between windows of same desktop (Bias alt- tab to prefer windows on the current viewport) if multi-window app is open pressing alt-tab will start from the same app. Status in Ayatana Design: New Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Normally, when you press alt-tab, you will be switched to app you've used last before current app (so you can switch between two apps with pressing alt-tab just once). When using option Bias alt-tab to prefer windows on the current viewport, if multi-window app is open pressing alt-tab will start from the same app. So to switch to another app you need to press alt- tab-tab. That's really annoying. Please fix that. Thanks. Video: http://dl.dropbox.com/u/865508/unity-bug-alt-tab.ogv p.s.: I'm using ubuntu 11.10 and unity 5 from ppa http://ppa.launchpad.net/unity-team/staging/ubuntu/ To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/928145/+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 998285] Re: Tapping alt-tab switches between windows of the same application sometimes
Annoys me too. My steps to repro: 1. Open 2 instances of QtCreator one instance of firefox (make all maximized for clarity's sake) 2. Alt-Tab away to firefox 3. Alt-Tab to QtCreator1 4. Alt-backtick to QtCreator2 5. Alt-Tab Expected result Firefox should be focused window Actual result I'm looking at QtCreator1 This behaviour breaks the paradigm of Alt-Tab between applications, and Alt-` between application windows. ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/998285 Title: Tapping alt-tab switches between windows of the same application sometimes Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Normally, tapping alt-tab switches between applications, and tapping alt-` switches between windows of the front-most application. However, if the two front-most windows are from the same application, then alt- tab will switch between these windows instead, instead of moving to the second-front-most application. Hence, in this case, alt-tab duplicates the action of alt-`. Here is an example: 1) create the stack with two nautilus windows at the top, e.g. Nautilus window 1 (N1), Nautilus window 2 (N2), and Firefox window (F1) (but you can use any applications). Create the stack either by [clicking F1, N2, N1] or [switching to Nautilus with alt-tab, then alt-` to the other Nautilus window]. 2) Tap alt-tab. What happens: I switch to the other nautilus window. What I expected: to switch to the other application (i.e. Firefox). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.12-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat May 12 10:17:21 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-04-29 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/998285/+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 786831] Re: Pulseaudio uses 5% CPU when doing nothing
I get up to and over 9% CPU usage when I've no sound playing application
open - but I was playing sounds previously. Using perf, it appeared most
CPU time being spent in kernel. strace gave me this output repeated
continually:
ppoll([{fd=5, events=POLLIN}, {fd=22, events=POLLIN|POLLOUT}, {fd=49,
events=POLLIN}, {fd=50, events=POLLIN}, {fd=48, events=POLLIN}, {fd=47,
events=POLLIN}, {fd=10, events=POLLIN}, {fd=40, events=POLLIN}, {fd=35,
events=POLLIN}, {fd=4, events=POLLIN}, {fd=42, events=POLLIN}, {fd=18,
events=POLLIN}, {fd=21, events=POLLIN}, {fd=39, events=POLLIN}, {fd=38,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=36, events=POLLIN}, {fd=17,
events=POLLIN}, {fd=34, events=POLLIN}, {fd=33, events=POLLIN}, {fd=32,
events=POLLIN}, {fd=31, events=POLLIN|POLLERR|POLLHUP}, {fd=31, events=0},
{fd=25, events=POLLIN}, {fd=28, events=POLLIN}, {fd=16,
events=POLLIN|POLLERR|POLLHUP}, {fd=16, events=0}, {fd=15, events=POLLIN},
{fd=14, events=POLLIN}, {fd=8, events=POLLIN}, {fd=7, events=POLLIN}], 31,
NULL, NULL, 8) = 1 ([{fd=22, revents=POLLIN|POLLOUT}])
write(6, W, 1)= 1
recvmsg(22, {msg_name(0)=NULL,
msg_iov(1)=[{\0\0\0\20\0\0\0\0\0\0\0\0\0\0\0\0\200\0\0\0, 20}],
msg_controllen=32, {cmsg_len=28, cmsg_level=SOL_SOCKET,
cmsg_type=SCM_CREDENTIALS{pid=3937, uid=1000, gid=1000}}, msg_flags=0}, 0) = 20
write(6, W, 1)= 1
sendto(22,
\0\0\0\30\377\377\377\377\0\0\0\0\0\0\0\0\0\0\0\0L\0\0\0?L\377\377\377\377L\0...,
44, MSG_NOSIGNAL, NULL, 0) = 44
write(6, W, 1)= 1
read(5, WWW, 10) = 3
ppoll([{fd=5, events=POLLIN}, {fd=22, events=POLLIN|POLLOUT}, {fd=49,
events=POLLIN}, {fd=50, events=POLLIN}, {fd=48, events=POLLIN}, {fd=47,
events=POLLIN}, {fd=10, events=POLLIN}, {fd=40, events=POLLIN}, {fd=35,
events=POLLIN}, {fd=4, events=POLLIN}, {fd=42, events=POLLIN}, {fd=18,
events=POLLIN}, {fd=21, events=POLLIN}, {fd=39, events=POLLIN}, {fd=38,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=36, events=POLLIN}, {fd=17,
events=POLLIN}, {fd=34, events=POLLIN}, {fd=33, events=POLLIN}, {fd=32,
events=POLLIN}, {fd=31, events=POLLIN|POLLERR|POLLHUP}, {fd=31, events=0},
{fd=25, events=POLLIN}, {fd=28, events=POLLIN}, {fd=16,
events=POLLIN|POLLERR|POLLHUP}, {fd=16, events=0}, {fd=15, events=POLLIN},
{fd=14, events=POLLIN}, {fd=8, events=POLLIN}, {fd=7, events=POLLIN}], 31,
NULL, NULL, 8) = 1 ([{fd=22, revents=POLLIN|POLLOUT}])
write(6, W, 1)= 1
recvmsg(22, {msg_name(0)=NULL,
msg_iov(1)=[{\0\0\0\33\3\1\312\204\0002\0(\0\0\4\250, 16}],
msg_controllen=32, {cmsg_len=28, cmsg_level=SOL_SOCKET,
cmsg_type=SCM_CREDENTIALS{pid=3937, uid=1000, gid=1000}}, msg_flags=0}, 0) = 16
write(6, W, 1)= 1
sendto(19, \1\0\0\0\0\0\0\0, 8, MSG_NOSIGNAL, NULL, 0) = -1 ENOTSOCK (Socket
operation on non-socket)
write(19, \1\0\0\0\0\0\0\0, 8)= 8
sendto(22,
\0\0\0\17\377\377\377\377\0\0\0\0\0\0\0\0\0\0\0\0L\0\0\0VL\377\377\377\377L\0...,
35, MSG_NOSIGNAL, NULL, 0) = 35
write(6, W, 1)= 1
read(5, WWW, 10) = 3
What is PA continually polling??
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/786831
Title:
Pulseaudio uses 5% CPU when doing nothing
Status in “pulseaudio” package in Ubuntu:
Confirmed
Bug description:
Binary package hint: pulseaudio
Pulseaudio is using five-percent CPU, with no sound playing and the
inputs muted. This is eating the battery:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
1601 sladen20 0 175m 23m 21m S5 0.8 3:11.78 pulseaudio
clock_gettime(CLOCK_MONOTONIC, {17605, 365566885}) = 0
ppoll([{fd=4, events=POLLIN}, {fd=39, events=POLLIN|POLLOUT}, {fd=40,
events=POLLIN}, {fd=38, events=POLLIN}, {fd=35, events=POLLIN}, {fd=21,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=37, events=POLLIN}, {fd=36,
events=POLLIN}, {fd=27, events=POLLIN}, {fd=7, events=POLLIN}, {fd=20,
events=POLLIN}, {fd=26, events=POLLIN}, {fd=34, events=POLLIN}, {fd=33,
events=POLLIN}, {fd=32, events=POLLIN}, {fd=31, events=POLLIN}, {fd=30,
events=POLLIN}, {fd=29, events=POLLIN|POLLERR|POLLHUP}, {fd=29, events=0},
{fd=22, events=POLLIN}, {fd=25, events=POLLIN}, {fd=16, events=POLLIN}, {fd=19,
events=POLLIN}, {fd=15, events=POLLIN|POLLERR|POLLHUP}, {fd=15, events=0},
{fd=14, events=POLLIN}, {fd=13, events=POLLIN}, {fd=6, events=POLLIN}], 29, {3,
91527000}, NULL, 8) = 1 ([{fd=39, revents=POLLIN|POLLOUT}], left {3, 91511007})
clock_gettime(CLOCK_MONOTONIC, {17605, 367958597}) = 0
recvmsg(39, {msg_name(0)=NULL,
msg_iov(1)=[{\0\0\0\20\0\0\0\0\0\0\0\0\0\0\0\0\200\0\0\0, 20}],
msg_controllen=24, {cmsg_len=24, cmsg_level=SOL_SOCKET,
[Desktop-packages] [Bug 1220458] Re: [xmir] [intel] Mir fails to start
Probably not the same issue, but as of 0.1.2+14.04.20131128.1-0ubuntu2, xmir fails to start for me. Had to disable xmir to start. Can't find any obvious error in a log file, suggestions? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1220458 Title: [xmir] [intel] Mir fails to start Status in Mir: Triaged Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: The hilarity begins at 48.37s after which Mir never recovers and failure is piled upon failure, not to mention the mirth leading up to that point. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1220458/+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 1262719] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1262719/+attachment/3932611/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1262719 Title: Crash if trying to compress contents of a directory mounted in nautilus via sftp Status in “file-roller” package in Ubuntu: New Bug description: Steps to repro: 1. in Nautilus, do File-Connect to Server and enter connection details to a remote SFTP server 2. Mount the newly created SFTP server directory 3. Navigate into the SFTP share, select a bunch of files 4. Right click and select Compress 5. File roller appears, the status bar flickers up to 100% and then crashes. --- ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-06-17 (185 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True NonfreeKernelModules: wl Package: file-roller 3.10.2.1-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Tags: trusty Uname: Linux 3.12.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2013-11-13 (36 days ago) UserGroups: adm autopilot cdrom dip fuse lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1262719/+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 1262719] [NEW] Crash if trying to compress contents of a directory mounted in nautilus via sftp
Public bug reported: Steps to repro: 1. in Nautilus, do File-Connect to Server and enter connection details to a remote SFTP server 2. Mount the newly created SFTP server directory 3. Navigate into the SFTP share, select a bunch of files 4. Right click and select Compress 5. File roller appears, the status bar flickers up to 100% and then crashes. --- ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-06-17 (185 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True NonfreeKernelModules: wl Package: file-roller 3.10.2.1-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Tags: trusty Uname: Linux 3.12.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2013-11-13 (36 days ago) UserGroups: adm autopilot cdrom dip fuse lpadmin plugdev sambashare sbuild sudo ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected trusty ** Tags added: apport-collected trusty ** Description changed: Steps to repro: 1. in Nautilus, do File-Connect to Server and enter connection details to a remote SFTP server 2. Mount the newly created SFTP server directory 3. Navigate into the SFTP share, select a bunch of files 4. Right click and select Compress 5. File roller appears, the status bar flickers up to 100% and then crashes. + --- + ApportVersion: 2.12.7-0ubuntu2 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2013-06-17 (185 days ago) + InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) + MarkForUpload: True + NonfreeKernelModules: wl + Package: file-roller 3.10.2.1-0ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 + Tags: trusty + Uname: Linux 3.12.0-5-generic x86_64 + UpgradeStatus: Upgraded to trusty on 2013-11-13 (36 days ago) + UserGroups: adm autopilot cdrom dip fuse lpadmin plugdev sambashare sbuild sudo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1262719 Title: Crash if trying to compress contents of a directory mounted in nautilus via sftp Status in “file-roller” package in Ubuntu: New Bug description: Steps to repro: 1. in Nautilus, do File-Connect to Server and enter connection details to a remote SFTP server 2. Mount the newly created SFTP server directory 3. Navigate into the SFTP share, select a bunch of files 4. Right click and select Compress 5. File roller appears, the status bar flickers up to 100% and then crashes. --- ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-06-17 (185 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True NonfreeKernelModules: wl Package: file-roller 3.10.2.1-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Tags: trusty Uname: Linux 3.12.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2013-11-13 (36 days ago) UserGroups: adm autopilot cdrom dip fuse lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1262719/+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 1262719] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1262719/+attachment/3932612/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1262719 Title: Crash if trying to compress contents of a directory mounted in nautilus via sftp Status in “file-roller” package in Ubuntu: New Bug description: Steps to repro: 1. in Nautilus, do File-Connect to Server and enter connection details to a remote SFTP server 2. Mount the newly created SFTP server directory 3. Navigate into the SFTP share, select a bunch of files 4. Right click and select Compress 5. File roller appears, the status bar flickers up to 100% and then crashes. --- ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-06-17 (185 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True NonfreeKernelModules: wl Package: file-roller 3.10.2.1-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Tags: trusty Uname: Linux 3.12.0-5-generic x86_64 UpgradeStatus: Upgraded to trusty on 2013-11-13 (36 days ago) UserGroups: adm autopilot cdrom dip fuse lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1262719/+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 1257547] [NEW] [bcm5974] Apple touchpad fails to respond, dmesg contains multiple mesages of form: bcm5974: bad trackpad package, length: 8
Public bug reported: Have Apple Macbook pro 8,1. With Trusty devel, very occasionally (i.e. twice in the last 3 weeks) my trackpad has completely stopped functioning for no reason I can determine. From then on, dmesg is full of these messages: bcm5974: bad trackpad package, length: 8 Removing and re-loading the bcm5974 kernel module fixes the problem. Sorry I've no better information to supply. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1257547 Title: [bcm5974] Apple touchpad fails to respond, dmesg contains multiple mesages of form: bcm5974: bad trackpad package, length: 8 Status in “xorg-server” package in Ubuntu: New Bug description: Have Apple Macbook pro 8,1. With Trusty devel, very occasionally (i.e. twice in the last 3 weeks) my trackpad has completely stopped functioning for no reason I can determine. From then on, dmesg is full of these messages: bcm5974: bad trackpad package, length: 8 Removing and re-loading the bcm5974 kernel module fixes the problem. Sorry I've no better information to supply. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1257547/+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 1088410] Re: Can't enter special characters in Dash search field
Ok thanks for clarifying, bug re-assigned. ** Also affects: unity Importance: Undecided Status: New ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-2d Status: New = Invalid ** Changed in: unity-2d (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity, dp-unity2d https://bugs.launchpad.net/bugs/1088410 Title: Can't enter special characters in Dash search field Status in Unity: New Status in Unity 2D: Invalid Status in “unity” package in Ubuntu: New Status in “unity-2d” package in Ubuntu: Invalid Bug description: I cannot enter the characters æ, ø and å in the search field in the Dash. Thus I can't search for Danishly named files. Ubuntu 12.04.1 LTS unity: Installed: 5.18.0-0ubuntu1 Candidate: 5.18.0-0ubuntu1 Version table: *** 5.18.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.10.0-0ubuntu6 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages Rant: I honestly can't fathom how Canonical could ship a beta product and call it a LTS release. This computer was supposded to have been my work computer (a System76 laptop). Now I waste time on working around, and reporting, grave bugs in Ubuntu/Unity. Bugs that doesn't seem to get fixed. This is unbelieveable, and I must admit that I have lost all love of Canonical and Ubuntu because of this. I feel let down. My only hope for a stable OS now is elementary OS. They have promised to ship only when they have something that actually works. These are the bugs I have reported so far: https://bugs.launchpad.net/unity/+bug/1069339 https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/1069107 https://bugs.launchpad.net/unity/+bug/1069342 https://bugs.launchpad.net/unity/+bug/1069344 https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1071506 plus this bug To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1088410/+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 1039052] [NEW] Volume at 100% for startup sound. If headphones in, makes ears bleed
Public bug reported: Hardware: Macbook Pro 8,1 Generic headphones Steps to Repro: 1. Have volume at comfortable level for listening to music via headphones 2. Log out of current session 3. View lightdm login screen 4. Rip headphones out of ears as volume of startup jingle at 100% ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1039052 Title: Volume at 100% for startup sound. If headphones in, makes ears bleed Status in “lightdm” package in Ubuntu: New Bug description: Hardware: Macbook Pro 8,1 Generic headphones Steps to Repro: 1. Have volume at comfortable level for listening to music via headphones 2. Log out of current session 3. View lightdm login screen 4. Rip headphones out of ears as volume of startup jingle at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1039052/+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 923410] Re: HUD - closing a window with Alt+F4 opens the hud
I believe this is fixed in Unity 2D 5.12, as released in Precise. Marking as fixed released. If anyone disagrees, please re-open. ** Changed in: unity-2d (Ubuntu) Status: In Progress = Fix Released ** Changed in: unity-2d Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity, dp-unity2d https://bugs.launchpad.net/bugs/923410 Title: HUD - closing a window with Alt+F4 opens the hud Status in Ayatana Design: Fix Committed Status in Compiz Core: Fix Released Status in Unity: Fix Released Status in Unity 2D: Fix Released Status in Unity Distro Priority: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity-2d” package in Ubuntu: Fix Released Bug description: Closing a window with the Alt+F4 shortcut closes the window, but also opens the hud. This doesn't always happen, but nearly all of the time. --- Desired solution: The HUD should only show on Alt RELEASE. In other words, tap-and-release-alt should show the HUD, together with three-finger-tap-on-window in touch environments. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/923410/+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 935871] Re: dragging a window bar to maximise is broken
** Changed in: unity-2d Status: New = Confirmed ** Also affects: metacity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-2d Importance: Undecided = Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/935871 Title: dragging a window bar to maximise is broken Status in Unity 2D: Confirmed Status in “metacity” package in Ubuntu: New Bug description: Dragging the window bar down unmaximizes. if you drag back up without letting go, it re-maximizes. If you let go it doesn't work. Unity-2d 4.12.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/935871/+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 992928] Re: Alt-Backtick Keyboard Shortcut is Hardcoded
In Unity 2D, this setting is defined in gconf in /apps/metacity/global_keybindings/switch_group It appears the option in the gnome control center is not reporting this correctly. ** Changed in: unity-2d Status: New = Triaged ** Changed in: unity-2d Importance: Undecided = Low ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/992928 Title: Alt-Backtick Keyboard Shortcut is Hardcoded Status in Unity 2D: Triaged Status in “gnome-control-center” package in Ubuntu: New Bug description: Unity has hard coded the Alt-Backtick [`] keyboard shortcut, and it grabs it before it is passed to firefox browser. I'm using a plugin that require Alt-Backtick and it is very disruptive to have to find a workaround when Alt-Backtick is not availabel to firefox. Either, disabke or change the shortcut to some other combo, or create a way for user to assign these shortcuts. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/992928/+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 924179] Re: 12.04 unity-2d dash broken since update, opens for 1 second then crashes
** Changed in: unity-2d (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/924179 Title: 12.04 unity-2d dash broken since update, opens for 1 second then crashes Status in Unity 2D: Fix Released Status in “unity-2d” package in Ubuntu: Fix Released Bug description: Since updating I am now unable to use the dash in unity 2d at all. When you press super or click the icon it only opens once for a sec then closes and doesn't respond at all after that. The launcher works fine. --- ApportVersion: 1.91-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 12.04 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2029.1) Package: unity-2d-places 5.2.0+bzr878ubuntu0+inline PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Tags: precise running-unity Uname: Linux 3.2.0-12-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to precise on 2011-12-21 (43 days ago) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/924179/+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 942122] Re: Dash Text cursor should be 1x30px not 2x34px
** Changed in: unity-2d Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/942122 Title: Dash Text cursor should be 1x30px not 2x34px Status in Unity: Triaged Status in Unity 2D: Fix Released Status in “unity” package in Ubuntu: Triaged Bug description: The dash search field cursor should be 1x30px. Design is available in HUD mockups. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/942122/+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 889044] Re: Nautilus opening behind current window
** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/889044 Title: Nautilus opening behind current window Status in Nautilus: Invalid Status in Unity: Invalid Status in Unity 2D: Confirmed Status in “nautilus” package in Ubuntu: New Bug description: To Replicate (using unity-2d): Open Firefox Open Nautilus from launcher Close Nautilus Move Firefox window about a bit (just giving it the focus does not seem to be enough) Open Nautilus again, it opens behind firefox and the launcher icon is jiggling. The same symptom is seen with apps other than Firefox. I have put this against unity-2d as the problem is not seen on Unity 3d. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/889044/+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 982949] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of private bug 979936 ** This bug has been marked a duplicate of private bug 962647 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982949 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: in attach ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Mon Apr 16 11:52:08 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120304) ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7feaac8a84d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7feaac8a84d3) ok source 0x8(%rsi) (0x50073010f) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: libvirtd vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982949/+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 982926] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of private bug 979936 ** This bug has been marked a duplicate of private bug 962647 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982926 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: No idea what happened here... I selected a different mail folder in Thunderbird and Unity crashed. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Mon Apr 16 10:35:16 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110901) ProcCmdline: unity-2d-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fde9aa4f4d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7fde9aa4f4d3) ok source 0x8(%rsi) (0x0008) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-02-07 (68 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982926/+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 982387] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of private bug 979936 ** This bug has been marked a duplicate of private bug 962647 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982387 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: see attach ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 15 16:53:53 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120304) ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f55b2a824d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7f55b2a824d3) ok source 0x8(%rsi) (0x0008) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: libvirtd vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982387/+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 982708] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of private bug 979936 ** This bug has been marked a duplicate of private bug 962647 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982708 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: window manager crashed and restarted ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 15 18:19:42 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc2adf214d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7fc2adf214d3) ok source 0x8(%rsi) (0x0068) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() 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/ubuntu/+source/unity-2d/+bug/982708/+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 982589] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of private bug 979936 ** This bug has been marked a duplicate of private bug 962647 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982589 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Bug! ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sun Apr 15 16:23:39 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: unity-2d-shell SegvAnalysis: Segfault happened at: 0x7fa00ada24d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7fa00ada24d3) ok source 0x8(%rsi) (0x10008) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-04-03 (11 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982589/+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 982029] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of private bug 979936 ** This bug has been marked a duplicate of private bug 962647 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982029 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 apt-cache policy unity-2d unity-2d: Installed: 5.10.0-0ubuntu1 Candidate: 5.10.0-0ubuntu1 Version table: *** 5.10.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status expected behavior - no idea. this warning popped up observed behavior - no errors, I guess? less with the sigsev for sure. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sat Apr 14 18:56:10 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f02a91804d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7f02a91804d3) ok source 0x8(%rsi) (0x0008) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() 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/ubuntu/+source/unity-2d/+bug/982029/+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 981895] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of private bug 979936 ** This bug has been marked a duplicate of private bug 962647 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/981895 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Crashed, Im running firefox,gnome-terminal,transmission-torrent-client ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sat Apr 14 23:02:24 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcCmdline: unity-2d-shell ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, user) LANG=de_CH.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f2f0e2c24d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7f2f0e2c24d3) ok source 0x8(%rsi) (0x0008) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/981895/+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 981693] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of private bug 979936 ** This bug has been marked a duplicate of private bug 962647 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/981693 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Crash, im just in the Firefox on the internet and *CRASH* unity-2d crashed. Crash, ich war nur mt dem Firefox im Internet und *CRASH* unity-2d abgestürzt. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sat Apr 14 18:08:49 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcCmdline: unity-2d-shell ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, user) LANG=de_CH.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f212f9804d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7f212f9804d3) ok source 0x8(%rsi) (0x6f006300670076) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() 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/ubuntu/+source/unity-2d/+bug/981693/+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 982298] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of private bug 979936 ** This bug has been marked a duplicate of private bug 962647 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982298 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: I have some freezes, since I changed the unity version from 3d to 2d. This error is one of those. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Apr 15 14:39:02 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Mythbuntu 9.10 Karmic Koala - Release i386 (20091028.4) ProcCmdline: unity-2d-shell SegvAnalysis: Segfault happened at: 0xb68c9fed _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+29: mov0x4(%esi),%edi PC (0xb68c9fed) ok source 0x4(%esi) (0x0003) not located in a known VMA region (needed readable region)! destination %edi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/i386-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-03-24 (21 days ago) UserGroups: adm admin audio cdrom dialout fuse lpadmin mythtv netdev plugdev sambashare tape vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982298/+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 981361] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of private bug 979936 ** This bug has been marked a duplicate of private bug 962647 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/981361 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: unity crashed ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu2 Architecture: i386 Date: Fri Apr 13 21:21:47 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301) ProcCmdline: unity-2d-shell ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb69a7fed _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+29: mov0x4(%esi),%edi PC (0xb69a7fed) ok source 0x4(%esi) (0x0004) not located in a known VMA region (needed readable region)! destination %edi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/i386-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() 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/ubuntu/+source/unity-2d/+bug/981361/+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 982994] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982994 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Unity2d crashed while firefox, nautilus, libreoffice writer and evince are opened. During scrolling in pdf document. No other causes identifiable. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Mon Apr 16 12:40:26 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcCmdline: unity-2d-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9904b234dd _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+45: cmpb $0x0,0xd4(%rbp) PC (0x7f9904b234dd) ok source $0x0 ok destination 0xd4(%rbp) (0x21d8) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo XsessionErrors: (gnome-settings-daemon:1759): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed (nautilus-sendto:2525): Gtk-WARNING **: Unknown property: GtkDialog.has-separator gnome-session[1713]: WARNING: Application 'unity-2d-shell.desktop' killed by signal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982994/+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 982949] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982949 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: in attach ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Mon Apr 16 11:52:08 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120304) ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7feaac8a84d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7feaac8a84d3) ok source 0x8(%rsi) (0x50073010f) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: libvirtd vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982949/+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 982926] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982926 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: No idea what happened here... I selected a different mail folder in Thunderbird and Unity crashed. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Mon Apr 16 10:35:16 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110901) ProcCmdline: unity-2d-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fde9aa4f4d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7fde9aa4f4d3) ok source 0x8(%rsi) (0x0008) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-02-07 (68 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982926/+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 982708] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982708 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: window manager crashed and restarted ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 15 18:19:42 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc2adf214d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7fc2adf214d3) ok source 0x8(%rsi) (0x0068) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() 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/ubuntu/+source/unity-2d/+bug/982708/+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 982990] Re: Unity 2d crashed unexpectedly. unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982990 Title: Unity 2d crashed unexpectedly. unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Unity 2d was reported to have crashed after I pressed either the the alt-key or the command key - both were pressed a few times. VMware Fusion. Ubuntu 64-bit. Expected event: Opening of the run command -dialog or opening of the search-dialog. Occured event: Unity 2d was reported to have crashed. Since then: normal behaviour. Description: Ubuntu precise (development branch) Release: 12.04 -- unity-2d: Installed: 5.10.0-0ubuntu1 - ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Mon Apr 16 14:18:56 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f28368d44dd _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+45: cmpb $0x0,0xd4(%rbp) PC (0x7f28368d44dd) ok source $0x0 ok destination 0xd4(%rbp) (0x00d6) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-04-16 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982990/+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 982674] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982674 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: I think it has to do nvidia proprietary driver. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 15 15:23:01 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120403) ProcCmdline: unity-2d-shell ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f208be374dd _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+45: cmpb $0x0,0xd4(%rbp) PC (0x7f208be374dd) ok source $0x0 ok destination 0xd4(%rbp) (0x0125) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() 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/ubuntu/+source/unity-2d/+bug/982674/+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 982589] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982589 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Bug! ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sun Apr 15 16:23:39 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: unity-2d-shell SegvAnalysis: Segfault happened at: 0x7fa00ada24d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7fa00ada24d3) ok source 0x8(%rsi) (0x10008) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-04-03 (11 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982589/+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 982481] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982481 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Using a new (last night) install of 12.04 beta2 on an old machine (Sempron 2400, 512MB RAM, S3 video) and I was waiting on Ubuntu Software Center to come to the foreground (with lots of paging going on) and had a popup dialog indicate that unity-2d had crashed, and did I want to restart it? ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 ApportVersion: 2.0.1-0ubuntu3 Architecture: i386 Date: Sun Apr 15 13:48:40 2012 ExecutablePath: /usr/bin/unity-2d-shell ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x5d3ff0 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+32: cmpb $0x0,0x74(%edi) PC (0x005d3ff0) ok source $0x0 ok destination 0x74(%edi) (0x436576dd) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/i386-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-04-15 (0 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982481/+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 982387] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982387 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: see attach ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 15 16:53:53 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120304) ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f55b2a824d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7f55b2a824d3) ok source 0x8(%rsi) (0x0008) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: libvirtd vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982387/+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 982298] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982298 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: I have some freezes, since I changed the unity version from 3d to 2d. This error is one of those. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Apr 15 14:39:02 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Mythbuntu 9.10 Karmic Koala - Release i386 (20091028.4) ProcCmdline: unity-2d-shell SegvAnalysis: Segfault happened at: 0xb68c9fed _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+29: mov0x4(%esi),%edi PC (0xb68c9fed) ok source 0x4(%esi) (0x0003) not located in a known VMA region (needed readable region)! destination %edi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/i386-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-03-24 (21 days ago) UserGroups: adm admin audio cdrom dialout fuse lpadmin mythtv netdev plugdev sambashare tape vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/982298/+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 982029] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/982029 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 apt-cache policy unity-2d unity-2d: Installed: 5.10.0-0ubuntu1 Candidate: 5.10.0-0ubuntu1 Version table: *** 5.10.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status expected behavior - no idea. this warning popped up observed behavior - no errors, I guess? less with the sigsev for sure. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sat Apr 14 18:56:10 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120321) ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f02a91804d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7f02a91804d3) ok source 0x8(%rsi) (0x0008) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() 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/ubuntu/+source/unity-2d/+bug/982029/+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 981895] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/981895 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Crashed, Im running firefox,gnome-terminal,transmission-torrent-client ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sat Apr 14 23:02:24 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcCmdline: unity-2d-shell ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, user) LANG=de_CH.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f2f0e2c24d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7f2f0e2c24d3) ok source 0x8(%rsi) (0x0008) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/981895/+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 981693] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/981693 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Crash, im just in the Firefox on the internet and *CRASH* unity-2d crashed. Crash, ich war nur mt dem Firefox im Internet und *CRASH* unity-2d abgestürzt. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sat Apr 14 18:08:49 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcCmdline: unity-2d-shell ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, user) LANG=de_CH.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f212f9804d3 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+35: mov0x8(%rsi),%rbp PC (0x7f212f9804d3) ok source 0x8(%rsi) (0x6f006300670076) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() 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/ubuntu/+source/unity-2d/+bug/981693/+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 981633] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/981633 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Description: Ubuntu precise (development branch) Release: 12.04 Installed: 5.10.0-0ubuntu1 Candidate: 5.10.0-0ubuntu1 Version table: *** 5.10.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 [modified: usr/share/unity-2d/shell/Shell.qml usr/share/unity-2d/shell/common/IconTile.qml usr/share/unity-2d/shell/launcher/LauncherList.qml] ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 NonfreeKernelModules: fglrx droidcam_v4l ApportVersion: 2.0.1-0ubuntu3 Architecture: i386 CheckboxSubmission: 12b2eb69bc47cd568dfcd1e3610481a7 CheckboxSystem: b1865df84255b8716d3bcc269ff410d1 CrashCounter: 1 Date: Sat Apr 14 10:18:52 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Custom Live CD - Release i386 ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xee1ff0 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+32: cmpb $0x0,0x74(%edi) PC (0x00ee1ff0) ok source $0x0 ok destination 0x74(%edi) (0x010a) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/i386-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-03-29 (16 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/981633/+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 981393] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/981393 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: I was working in gnome-terminal and I pressed the alt key. A different thing in my environement is that I use orca. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 14 03:39:19 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f6dbcfd74dd _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+45: cmpb $0x0,0xd4(%rbp) PC (0x7f6dbcfd74dd) ok source $0x0 ok destination 0xd4(%rbp) (0x00025b99) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: libvirtd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/981393/+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 981361] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/981361 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: unity crashed ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu2 Architecture: i386 Date: Fri Apr 13 21:21:47 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301) ProcCmdline: unity-2d-shell ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb69a7fed _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+29: mov0x4(%esi),%edi PC (0xb69a7fed) ok source 0x4(%esi) (0x0004) not located in a known VMA region (needed readable region)! destination %edi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/i386-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() 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/ubuntu/+source/unity-2d/+bug/981361/+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 981318] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/981318 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Default programs repopulated themselves on the launcher. Otherwise, was idling when crash dialog came up. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Fri Apr 13 18:47:04 2012 ExecutablePath: /usr/bin/unity-2d-shell ProcCmdline: unity-2d-shell ProcEnviron: LANGUAGE=en_US: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ffe08ef74dd _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+45: cmpb $0x0,0xd4(%rbp) PC (0x7ffe08ef74dd) ok source $0x0 ok destination 0xd4(%rbp) (0x00d4) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() 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/ubuntu/+source/unity-2d/+bug/981318/+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 977925] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/977925 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Accidently opened dash home while running app (keyb shortcut?). Then tried to close it but hung. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Tue Apr 10 12:25:01 2012 ExecutablePath: /usr/bin/unity-2d-shell ProcCmdline: unity-2d-shell SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity-2d Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-03-02 (38 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/977925/+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 977372] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/977372 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: This happens when connecting a second monitor righ after waking up from suspend. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Mon Apr 9 10:23:07 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity-2d Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-04-07 (2 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/977372/+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 976079] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/976079 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Sat Apr 7 19:08:08 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: unity-2d-shell SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity-2d Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-03-23 (14 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/976079/+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 975215] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug is no longer a duplicate of bug 962647 unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/975215 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Upgraded to 12.04. Tried HUD with GIMP but it doesn't work. after that I got info about bug. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Fri Apr 6 15:49:17 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcCmdline: unity-2d-shell SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity-2d Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-04-06 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/975215/+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 962647] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 947278 *** https://bugs.launchpad.net/bugs/947278 ** This bug has been marked a duplicate of bug 947278 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/962647 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: Confirmed Bug description: see log in attach ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.7.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Thu Mar 22 23:40:20 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120304) ProcCmdline: unity-2d-shell ProcEnviron: LANG=it_IT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f109487a4dd _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+45: cmpb $0x0,0xd4(%rbp) PC (0x7f109487a4dd) ok source $0x0 ok destination 0xd4(%rbp) (0x00d6) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() 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/ubuntu/+source/unity-2d/+bug/962647/+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 981118] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 968046 *** https://bugs.launchpad.net/bugs/968046 ** This bug is no longer a duplicate of private bug 970779 ** This bug has been marked a duplicate of bug 968046 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/981118 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: non ne ho idea ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu2 Architecture: i386 CheckboxSubmission: d61f496282160f0ec92f24860d70fdd2 CheckboxSystem: b8f3ec504801f13fc208edb5c785b099 Date: Fri Apr 13 21:25:11 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu-Server 10.10 Maverick Meerkat - Release i386 (20101007) ProcCmdline: unity-2d-shell SegvAnalysis: Segfault happened at: 0xb68f77f5:mov0x8(%eax),%edi PC (0xb68f77f5) ok source 0x8(%eax) (0x2645) not located in a known VMA region (needed readable region)! destination %edi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libQtDBus.so.4 QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/i386-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to precise on 2012-04-13 (0 days ago) UserGroups: adm admin audio backup bin cdrom dialout dip fax floppy fuse gdm irc lp lpadmin mysql netdev operator plugdev root sabayon-admin sambashare saned tape users utempter video voice www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/981118/+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 980818] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
*** This bug is a duplicate of bug 968046 *** https://bugs.launchpad.net/bugs/968046 ** This bug is no longer a duplicate of private bug 970779 ** This bug has been marked a duplicate of bug 968046 unity-2d-shell crashed with SIGSEGV in ref() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/980818 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() Status in “unity-2d” package in Ubuntu: New Bug description: Wud like to report if of any help ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Fri Apr 13 15:25:56 2012 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: unity-2d-shell ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe78478cdd7:mov0x8(%rax),%r8d PC (0x7fe78478cdd7) ok source 0x8(%rax) (0x10008) not located in a known VMA region (needed readable region)! destination %r8d ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 BamfView::icon() const () from /usr/lib/libQtBamf.so.1 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0 Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/980818/+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
