[Desktop-packages] [Bug 1668429] Re: X apps (LibreOffice, Thunderbird) fail to launch with failure to open display (no Xmir is running)
*qt5 apps I mean -- 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/1668429 Title: X apps (LibreOffice, Thunderbird) fail to launch with failure to open display (no Xmir is running) Status in Canonical System Image: Fix Released Status in gtk+3.0 package in Ubuntu: Invalid Status in libertine package in Ubuntu: Invalid Status in ubuntu-app-launch package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Bug description: Feb 27 iso build of zesty, clean u8 exploration repro: 1) open app drawer, find the thunderbird app 2) click on icon to launch 3) window closes immediately not a very useful journal log http://pastebin.ubuntu.com/24080860/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668429/+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 1668429] Re: X apps (LibreOffice, Thunderbird) fail to launch with failure to open display (no Xmir is running)
With that "fix", now qt5 are unusable as they go under XMir. -- 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/1668429 Title: X apps (LibreOffice, Thunderbird) fail to launch with failure to open display (no Xmir is running) Status in Canonical System Image: Fix Released Status in gtk+3.0 package in Ubuntu: Invalid Status in libertine package in Ubuntu: Invalid Status in ubuntu-app-launch package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Bug description: Feb 27 iso build of zesty, clean u8 exploration repro: 1) open app drawer, find the thunderbird app 2) click on icon to launch 3) window closes immediately not a very useful journal log http://pastebin.ubuntu.com/24080860/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668429/+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 1670390] Re: Desktop applications don't get properly resized when launched in staged mode
@vanvugt Could you please explain why you invalidated the gtk+3.0 bug? ** Changed in: qtubuntu (Ubuntu) Status: New => Invalid ** Changed in: gtk+3.0 (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1670390 Title: Desktop applications don't get properly resized when launched in staged mode Status in Canonical System Image: In Progress Status in QtMir: In Progress Status in gtk+3.0 package in Ubuntu: New Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: Invalid Status in unity8 package in Ubuntu: In Progress Bug description: Steps to reproduce the issue: 1 - Put unity8 in staged mode 2 - Launch a desktop application like kate or qtcreator Expected outcome: The launched application takes up the entire stage area Actual outcome: The launched application starts with some windowed size it wanted to have, not filling the entire stage area. As if launched in desktop mode. Comments: Leaving staged mode and going back into it again gets the application to resize correctly and fill the entire stage area. Going from desktop to staged mode while the desktop application is already running also works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670390/+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 1670390] Re: Desktop applications don't get properly resized when launched in staged mode
With gtk+ apps, when they get launched the ask for a resize. If in tablet/phone mode unity8 will deny/ignore it, but gtk thinks the resize was successful and renders as if its window had the size it requested (that's with the qtmir and unity8 branches attached to this bug) ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1670390 Title: Desktop applications don't get properly resized when launched in staged mode Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: In Progress Bug description: Steps to reproduce the issue: 1 - Put unity8 in staged mode 2 - Launch a desktop application like kate or qtcreator Expected outcome: The launched application takes up the entire stage area Actual outcome: The launched application starts with some windowed size it wanted to have, not filling the entire stage area. As if launched in desktop mode. Comments: Leaving staged mode and going back into it again gets the application to resize correctly and fill the entire stage area. Going from desktop to staged mode while the desktop application is already running also works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670390/+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 1669432] Re: [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode
The second issue is bug 1670390. As for the crashes you mention, please be more specific (with a step-by- step use case), preferably in a separate bug report. ** Changed in: unity8 (Ubuntu) Status: In Progress => Incomplete ** Changed in: gtk+3.0 (Ubuntu) Status: New => Invalid -- 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/1669432 Title: [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: ubuntu 17.04 unity8 [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode turn desktop mode off, and now launch random apps and see how it behave kate, the icon bar don't quite works, try to hover or click on the new document, open etc icons. only works on the buttom side of the icons, probably the hitboxes or something are wrong, same with tiled. some gtk apps don't even resize to fullscreen (gnome-mines), and if you click on the menu icon the apps just crash etc To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669432/+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 1669432] Re: [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode
This is the first bug: Bug 1670361 -- 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/1669432 Title: [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: New Status in unity8 package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: ubuntu 17.04 unity8 [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode turn desktop mode off, and now launch random apps and see how it behave kate, the icon bar don't quite works, try to hover or click on the new document, open etc icons. only works on the buttom side of the icons, probably the hitboxes or something are wrong, same with tiled. some gtk apps don't even resize to fullscreen (gnome-mines), and if you click on the menu icon the apps just crash etc To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669432/+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 1669432] Re: [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode
Anyway, will investigate the one about kate toolbar buttons. -- 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/1669432 Title: [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: New Status in unity8 package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: ubuntu 17.04 unity8 [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode turn desktop mode off, and now launch random apps and see how it behave kate, the icon bar don't quite works, try to hover or click on the new document, open etc icons. only works on the buttom side of the icons, probably the hitboxes or something are wrong, same with tiled. some gtk apps don't even resize to fullscreen (gnome-mines), and if you click on the menu icon the apps just crash etc To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669432/+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 1669432] Re: [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode
Looks like you have multiple bugs in a single report. Not good. ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Daniel d'Andrada (dandrader) ** Changed in: unity8 (Ubuntu) Status: New => In Progress -- 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/1669432 Title: [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: New Status in unity8 package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: ubuntu 17.04 unity8 [unity8] qt/gtk apps don't quite work in fullscreen/tablet mode turn desktop mode off, and now launch random apps and see how it behave kate, the icon bar don't quite works, try to hover or click on the new document, open etc icons. only works on the buttom side of the icons, probably the hitboxes or something are wrong, same with tiled. some gtk apps don't even resize to fullscreen (gnome-mines), and if you click on the menu icon the apps just crash etc To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669432/+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
Re: [Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")
On 13/09/2016 08:49, Gerry Boland wrote: > 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? It works fine. -- 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 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")
qtbase-opensource-src did get a new release on september 3rd. But xenial stable-phone-overlay and yakkety seem to be carrying the very same qt version, so scrap my theory from comment #30... -- 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: Invalid 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 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")
Maybe the culprit is different Qt versions between xenial and yakkety? -- 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: Invalid 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 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")
This only happens in yakkety. The same qtmir, qtubuntu and unity8 runs fine in xenial. Lost a couple of hours on this issue yesterday and my "solution" was to reboot my test laptop into a xenial partition so I could unblock myself. -- 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: Invalid 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 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir
** Branch unlinked: lp:~dandrader/qtmir/cursorConfinement -- 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/1590099 Title: Need to support pointer confinement in Mir and toolkits using Mir Status in Canonical System Image: Fix Committed Status in Mir: Fix Released Status in MirAL: Triaged Status in libsdl2 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Triaged Bug description: We need to support pointer confinement set by the client. This way we can generate relative mouse events on a surface without the cursor being able to leave the edge of the window. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590099/+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 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir
** Branch linked: lp:~unity-team/qtmir/cursorConfinement -- 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/1590099 Title: Need to support pointer confinement in Mir and toolkits using Mir Status in Canonical System Image: Fix Committed Status in Mir: Fix Released Status in MirAL: Triaged Status in libsdl2 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Triaged Bug description: We need to support pointer confinement set by the client. This way we can generate relative mouse events on a surface without the cursor being able to leave the edge of the window. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590099/+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
Re: [Desktop-packages] [Bug 1536751] Re: Font/text rendering is irregular and not pixel-aligned on low DPI screens
On 13/07/2016 06:45, Daniel van Vugt wrote: > The second part of the problem is that Unity8 (especially in the > indicator pulldown) failing to apply a nice hinting setting to make the > glyph curves aligned to pixel boundaries more often. So a glyph that > should be represented as one pixel thickness is rendered as two half > pixels in greyscale, which is ugly. > About the indicators: do you see blurry text only *while* you're dragging it down or do you see it also afterwards, when its fully extended? -- 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 QtMir: New 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 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/qtmir/+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 1501346] Re: Unity8 never shows app window if preceded by a splash screen
** Changed in: qtmir (Ubuntu) Status: Confirmed => Fix Released ** Changed in: qtmir Status: Confirmed => Fix Released ** Changed in: unity8 (Ubuntu) Status: Opinion => Fix Released -- 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/1501346 Title: Unity8 never shows app window if preceded by a splash screen Status in Canonical Pocket Desktop: Fix Released Status in QtMir: Fix Released Status in qtmir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: I'm trying to run Gimp in a Vivid + overlay PPA Unity 8 desktop session using Xmir from the overlay PPA with the '-rootless -flatten' Xmir options. Gimp fails to start in this situation. I've attached the application and unity8 log files. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1501346/+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 1501346] Re: Unity8 never shows app window if preceded by a splash screen
unity8 now supports applications with multiple top-level surfaces (shown as windows in unity8). I suppose that might have fixed this bug -- 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/1501346 Title: Unity8 never shows app window if preceded by a splash screen Status in Canonical Pocket Desktop: Incomplete Status in QtMir: Incomplete Status in qtmir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: I'm trying to run Gimp in a Vivid + overlay PPA Unity 8 desktop session using Xmir from the overlay PPA with the '-rootless -flatten' Xmir options. Gimp fails to start in this situation. I've attached the application and unity8 log files. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1501346/+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 1517615] Re: Need to disable "--enable-hardware-cursor=true" option in unity-system-compositor
I think that will just make unity-system-compositor fallback to using a "software", GL, cursor instead. But then in Mir's innards it might simply behave better (ie, obey to unity8 orders to get mir cursor hidden) than the hardware cursor implementation. -- 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/1517615 Title: Need to disable "--enable-hardware-cursor=true" option in unity- system-compositor Status in lightdm package in Ubuntu: Confirmed Status in lightdm source package in Vivid: Confirmed Bug description: Recently, Unity 8 provides its own cursor, so we no longer need the "--enable-hardware-cursor=true" option in unity-system-compositor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1517615/+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 1517615] Re: Need to disable "--enable-hardware-cursor=true" option in unity-system-compositor
After talking about it over IRC, my understanding in comment #3 is wrong as the parameter does not mean that. So please ignore comment #3 -- 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/1517615 Title: Need to disable "--enable-hardware-cursor=true" option in unity- system-compositor Status in lightdm package in Ubuntu: Confirmed Status in lightdm source package in Vivid: Confirmed Bug description: Recently, Unity 8 provides its own cursor, so we no longer need the "--enable-hardware-cursor=true" option in unity-system-compositor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1517615/+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: In Progress = Fix Released ** Changed in: qtubuntu Status: In Progress = Fix Released ** Changed in: platform-api Status: In Progress = Fix Released ** Changed in: unity8 (Ubuntu) Status: Opinion = Fix Released -- 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: Fix Released Status in Qt integration with the Mir display server: Fix Released Status in QT Ubuntu: Fix Released Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu: Fix Released Status in “qtmir” package in Ubuntu: Fix Released Status in “qtubuntu” 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: Fix Released 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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
I confirm that the Qt from https://launchpad.net/~canonical-x/+archive/x-staging does XISelectEvents on the master pointer (instead of the touchscreen slave device, as previously) and that the resulting behavior of the xserver is good. Ie., touch ownership mechanics work properly and mouse pointer emluation from touch events keeps working as well. -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in X.Org X server: Unknown Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
Qt still XISelectEvents my N-Trig Pen stylus and N-Trig Pen eraser slave devices though. But thankfully no events come from them and thus peace is maintained :) ** Changed in: unity (Ubuntu) Status: In Progress = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in X.Org X server: Unknown Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
Took the liberty of correcting the bug title as unity does keep getting touch events. It's the xserver mouse pointer emulation from touch events that breaks badly. ** Also 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. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in “unity” package in Ubuntu: In Progress Status in “xorg-server” package in Ubuntu: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
xserver packages I used to take the logs above. ** Attachment added: xserver debian packages with detailed logging of input events https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/+attachment/4106288/+files/xorg_debug_packages.zip -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in “unity” package in Ubuntu: In Progress Status in “xorg-server” package in Ubuntu: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
Attaching detailed xserver log. The following steps were taken: 1- sudo restart lightdm (to restart the X server. so that de have a clean slate) 2- run a very simple qml app with qmlscene 3- tapped on that qmlscene window (touch id 1) 4- tapped on the desktop area (nautilus) (touch id 2) 5- sudo stop lightdm From the logs you can see that no pointer emulation was done for touch id 2 because xserver still thinks that touch id 1 is active. ** Attachment added: xorg_debug.zip https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/+attachment/4106287/+files/xorg_debug.zip -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in “unity” package in Ubuntu: In Progress Status in “xorg-server” package in Ubuntu: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
Excerpt from #xorg-devel: dandrader daniels, I've the following situation: clientX has a XISelectEvents(TouchBegin|Update|End, childWindowA, slaveDevice1); clientY has a XIPassiveGrabDevice(TouchBegin|Update|End|Ownership, rootWindow, AllMasterDevices) daniels, when a touch reaches xserver, it sends touch events to both clientX and clientY daniels dandrader: yes, events are delivered separately thorough master and slaves - i'd recommend not using slaves for anything at all dandrader daniels, but I believe it should send only to clientY, and only once clientY rejects the touch sequence should clientX finally start receiving the touch events (replayed), right? daniels dandrader: if both clients were listening on a master device, then you'd be right dandrader daniels, hmm got it. so what I'm seeing is the expected behavior then and I should modify clientX to select events on AllMasterDevices instead of on slaveDevice1 daniels, is that it? daniels dandrader: exactly So we have two problems here: 1- touch ownership mechanics won't work in our situation as Qt is talking directly to the slave devices whereas unity7 is talking to the master devices. 2- the xserver bug described in my previous comments where it gets confused with such situation and ends up with a borked internal state which ruins mouse pointer emulation So if we could avoid the situation in item 1 (by changing either Qt or unity7/Open Input Fw Grail code) we might (have to try it out to see) circumvent the bug in item 2. -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in “unity” package in Ubuntu: In Progress Status in “xorg-server” package in Ubuntu: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
Is there a specific reason for calling XISelectEvents() for each slave vs using XIAllMasterDevices in QXcbConnection::xi2Select() in Qt? Would have to dig into Qt code to tell that. But my guess is that because it exposes QTouchDevice objects to applications. For every QTouchEvent you can get the QTouchDevice from where it came from. But it might be that it could work with XIAllMasterDevices just as well. -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in “unity” package in Ubuntu: In Progress Status in “xorg-server” package in Ubuntu: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
And here's the upstream bug I reported: https://bugs.freedesktop.org/show_bug.cgi?id=78345 ** Bug watch added: freedesktop.org Bugzilla #78345 https://bugs.freedesktop.org/show_bug.cgi?id=78345 -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in “unity” package in Ubuntu: In Progress Status in “xorg-server” package in Ubuntu: New Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1298727] Re: Xorg crashed with SIGABRT in point_on_screen()
Might have the same root cause as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701 -- 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/1298727 Title: Xorg crashed with SIGABRT in point_on_screen() Status in “xorg-server” package in Ubuntu: Confirmed Status in “xorg-server” source package in Trusty: Confirmed Bug description: Running fresh trusty, happy to help debug. TEST CASE: Note: Reproducible on a desktop with a touch screen 1. Open gallery-app preloaded with picture 2. Open a picture 3 Switch between picture with touch gestures ACTUAL RESULT After switching between pictures back and forth, this crash occurs ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Mar 26 14:25:20 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00b9] InstallationDate: Installed on 2014-03-05 (22 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64+mac (20131016.1) MachineType: Apple Inc. MacBookPro5,5 ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic root=UUID=a18b6891-4a66-4d53-bad1-f576bb46ef99 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () miPointerSetPosition () ?? () ?? () ?? () SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: Xorg crashed with SIGABRT in miPointerSetPosition() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP55.88Z.00AC.B03.0906151708 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F2268AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8: dmi.product.name: MacBookPro5,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Mar 27 20:52:01 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1298727/+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 1197897] [NEW] gnome-control-center crashed with SIGSEGV in gnome_control_center_show()
Public bug reported: I was trying to open the Time Date settings. Nothing happens. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu29 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Thu Jul 4 13:58:51 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-06-26 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130626) MarkForUpload: True ProcCmdline: gnome-control-center indicator-datetime SegvAnalysis: Segfault happened at: 0x7f6fe11552b8 gnome_control_center_show+24: mov 0x40(%rdx),%rdi PC (0x7f6fe11552b8) ok source 0x40(%rdx) (0xaaea) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center Stacktrace: #0 0x7f6fe11552b8 in gnome_control_center_show () No symbol table info available. #1 0x7f6fe115258e in _start () No symbol table info available. StacktraceTop: gnome_control_center_show () _start () Title: gnome-control-center crashed with SIGSEGV in gnome_control_center_show() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup27.3.1-0ubuntu1 gnome-control-center-signon 0.1.7~daily13.06.18-0ubuntu1 gnome-control-center-unity 1.3daily13.06.14.1-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy ** Information type changed from Private to Public -- 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/1197897 Title: gnome-control-center crashed with SIGSEGV in gnome_control_center_show() Status in “gnome-control-center” package in Ubuntu: New Bug description: I was trying to open the Time Date settings. Nothing happens. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu29 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Thu Jul 4 13:58:51 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-06-26 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130626) MarkForUpload: True ProcCmdline: gnome-control-center indicator-datetime SegvAnalysis: Segfault happened at: 0x7f6fe11552b8 gnome_control_center_show+24: mov 0x40(%rdx),%rdi PC (0x7f6fe11552b8) ok source 0x40(%rdx) (0xaaea) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center Stacktrace: #0 0x7f6fe11552b8 in gnome_control_center_show () No symbol table info available. #1 0x7f6fe115258e in _start () No symbol table info available. StacktraceTop: gnome_control_center_show () _start () Title: gnome-control-center crashed with SIGSEGV in gnome_control_center_show() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup27.3.1-0ubuntu1 gnome-control-center-signon 0.1.7~daily13.06.18-0ubuntu1 gnome-control-center-unity 1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1197897/+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 1194896] [NEW] eog crashed with SIGSEGV in g_type_check_instance_cast()
Public bug reported: I was looking at an SVG file. Then I clicked Edit - Preferences and started changing the Background and Transparent Parts options. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: eog 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Wed Jun 26 11:07:42 2013 ExecutablePath: /usr/bin/eog InstallationDate: Installed on 2013-06-26 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130626) MarkForUpload: True ProcCmdline: eog /tmp/DirectionalDragArea.svg SegvAnalysis: Segfault happened at: 0x7f7ba02d7fec g_type_check_instance_cast+28: mov (%rax),%rdi PC (0x7f7ba02d7fec) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: eog StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () eog_scroll_view_set_use_bg_color () g_object_set_property () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: eog crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash apport-failed-retrace saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1194896 Title: eog crashed with SIGSEGV in g_type_check_instance_cast() Status in “eog” package in Ubuntu: New Bug description: I was looking at an SVG file. Then I clicked Edit - Preferences and started changing the Background and Transparent Parts options. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: eog 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Wed Jun 26 11:07:42 2013 ExecutablePath: /usr/bin/eog InstallationDate: Installed on 2013-06-26 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130626) MarkForUpload: True ProcCmdline: eog /tmp/DirectionalDragArea.svg SegvAnalysis: Segfault happened at: 0x7f7ba02d7fec g_type_check_instance_cast+28: mov(%rax),%rdi PC (0x7f7ba02d7fec) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: eog StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () eog_scroll_view_set_use_bg_color () g_object_set_property () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: eog crashed with SIGSEGV in g_type_check_instance_cast() 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/eog/+bug/1194896/+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 1194908] [NEW] software-center crashed with signal 5
Public bug reported: Launched from the Dash and it crashed a second after its window got displayed. Wasn't able to reproduce the crash later. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: software-center 13.05-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Wed Jun 26 11:53:09 2013 Disassembly: = 0x7f3f19fd4179: Cannot access memory at address 0x7f3f19fd4179 ExecutablePath: /usr/share/software-center/software-center InstallationDate: Installed on 2013-06-26 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130626) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center Signal: 5 SourcePackage: software-center Stacktrace: #0 0x7f3f19fd4179 in ?? () No symbol table info available. Cannot access memory at address 0x7fff56bc9810 StacktraceTop: ?? () ThreadStacktrace: . Thread 8 (LWP 19333): #0 0x7f3f1bd0d05e in ?? () No symbol table info available. Cannot access memory at address 0x7f3eacedcd70 Title: software-center crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy ** Information type changed from Private to Public -- 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/1194908 Title: software-center crashed with signal 5 Status in “software-center” package in Ubuntu: New Bug description: Launched from the Dash and it crashed a second after its window got displayed. Wasn't able to reproduce the crash later. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: software-center 13.05-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Wed Jun 26 11:53:09 2013 Disassembly: = 0x7f3f19fd4179: Cannot access memory at address 0x7f3f19fd4179 ExecutablePath: /usr/share/software-center/software-center InstallationDate: Installed on 2013-06-26 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130626) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center Signal: 5 SourcePackage: software-center Stacktrace: #0 0x7f3f19fd4179 in ?? () No symbol table info available. Cannot access memory at address 0x7fff56bc9810 StacktraceTop: ?? () ThreadStacktrace: . Thread 8 (LWP 19333): #0 0x7f3f1bd0d05e in ?? () No symbol table info available. Cannot access memory at address 0x7f3eacedcd70 Title: software-center crashed with signal 5 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/software-center/+bug/1194908/+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 1164409] Re: compiz crashes while opening nautilus
*** This bug is a duplicate of bug 1161916 *** https://bugs.launchpad.net/bugs/1161916 This is most likely a duplicate of bug #1161916, although there's no backtrace here to confirm this. Please see if it gets fixed after after the fix for bug #1161916 gets released. ** This bug has been marked a duplicate of bug 1161916 compiz crashed with SIGSEGV in sigc::internal::slot_call0unity::launcher::VolumeImp::Impl::Impl() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1164409 Title: compiz crashes while opening nautilus Status in “gnome-session” package in Ubuntu: New Bug description: From /var/log/syslog: Apr 4 12:17:53 utwks04035 avahi-daemon[1295]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?) Apr 4 12:17:54 utwks04035 avahi-daemon[1295]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?) Apr 4 12:21:55 utwks04035 dbus[1251]: [system] Activating service name='org.freedesktop.hostname1' (using servicehelper) Apr 4 12:21:55 utwks04035 dbus[1251]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 4 12:21:55 utwks04035 kernel: [13823.925000] traps: compiz[2255] trap stack segment ip:7fbf173ffceb sp:7fff1e7aeec0 error:0 Apr 4 12:21:55 utwks04035 gnome-session[2137]: WARNING: Application 'compiz.desktop' killed by signal 7 Apr 4 12:21:55 utwks04035 gnome-session[2137]: WARNING: App 'compiz.desktop' respawning too quickly Apr 4 12:21:55 utwks04035 gnome-session[2137]: CRITICAL: We failed, but the fail whale is dead. Sorry This problem has been happening since yesterday. Unfortunately it does not happen every time I open Nautilus. So far the crash has happened four times. Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 I assume that gnome-session is the package (but I'm not sure) gnome-session: Installed: 3.6.2-0ubuntu5 Candidate: 3.6.2-0ubuntu5 Version table: *** 3.6.2-0ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1164409/+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 1050538] Re: Cannot launch multiple calculators
It's working now. So let's mark it as fix released even though the fix was done elsewhere. ** Changed in: gcalctool (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcalctool in Ubuntu. https://bugs.launchpad.net/bugs/1050538 Title: Cannot launch multiple calculators Status in “gcalctool” package in Ubuntu: Fix Released Bug description: It's currently not possible to launch multiple calculators in Quantal. It used to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/1050538/+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 1050538] [NEW] Cannot launch multiple calculators
Public bug reported: It's currently not possible to launch multiple calculators in Quantal. It used to work. ** Affects: gcalctool (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcalctool in Ubuntu. https://bugs.launchpad.net/bugs/1050538 Title: Cannot launch multiple calculators Status in “gcalctool” package in Ubuntu: New Bug description: It's currently not possible to launch multiple calculators in Quantal. It used to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/1050538/+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 927742] Re: banshee moves to next song then stops playback
Could you check what file-types they're getting stuck on? Yesterday it happened only once, and it was on a .ogg file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/927742 Title: banshee moves to next song then stops playback Status in Banshee Music Player: New Status in “banshee” package in Ubuntu: Triaged Bug description: Ubuntu 12.04 alpha 2 banshee 2.3.4.ds-1ubuntu1 Expected: songs should play fine when moving from song to song. Actual: Sometimes (and not all the time), when banshee moves to the next song (in Random and Random-Off) the song will not play. The Icon in the toolbar is in Play mode and a Play Icon shows up in the list next to the song, but the seconds do not move, and no sounds play. After a random amount of time, it *sometimes* just starts playing the song at about the place it would if it hadn't frozen, other times I have to manually double-click the current song to get it to start, or start the next song. Pressing the Play/Pause button does nothing, but double clicking the song will play it. Because these songs *will* play I don't think it is corrupt songs, especially considering the same library worked fine with bashsee in 11.10. There is no output on the terminal (w/ no switches) when this happens. My library is mostly mp3, but a smattering of FLAC, ogg, and whatever apple sells mixed in. To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/927742/+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 927742] Re: banshee moves to next song then stops playback
I'm getting that all the time, with both Banshee and Rhythmbox. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/927742 Title: banshee moves to next song then stops playback Status in Banshee Music Player: New Status in “banshee” package in Ubuntu: Triaged Bug description: Ubuntu 12.04 alpha 2 banshee 2.3.4.ds-1ubuntu1 Expected: songs should play fine when moving from song to song. Actual: Sometimes (and not all the time), when banshee moves to the next song (in Random and Random-Off) the song will not play. The Icon in the toolbar is in Play mode and a Play Icon shows up in the list next to the song, but the seconds do not move, and no sounds play. After a random amount of time, it *sometimes* just starts playing the song at about the place it would if it hadn't frozen, other times I have to manually double-click the current song to get it to start, or start the next song. Pressing the Play/Pause button does nothing, but double clicking the song will play it. Because these songs *will* play I don't think it is corrupt songs, especially considering the same library worked fine with bashsee in 11.10. There is no output on the terminal (w/ no switches) when this happens. My library is mostly mp3, but a smattering of FLAC, ogg, and whatever apple sells mixed in. To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/927742/+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 878198] Re: Difficult to grab window borders in unity-2d
@Otus Yes, check bug 953839 -- 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/878198 Title: Difficult to grab window borders in unity-2d Status in “metacity” package in Ubuntu: Triaged Status in “unity-2d” package in Ubuntu: Invalid Status in “metacity” source package in Precise: Triaged Status in “unity-2d” source package in Precise: Invalid Bug description: In unity-2d it seems that window borders are only 1 pixel wide and are therefore very difficult to grab for window resize. In 3D it seems that a shadow extends the width of the border so the problem does not occur. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity-2d 4.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Wed Oct 19 14:33:44 2011 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-2d UpgradeStatus: Upgraded to oneiric on 2011-10-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/878198/+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 331897] Re: Incorrect sorting of Processes' Memory column
In using Precise, where gnome-system-monitor version currently is 3.3.90, and this bug still occurs. This bug report should be reopened. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/331897 Title: Incorrect sorting of Processes' Memory column Status in The GNOME System Monitor: Fix Released Status in “gnome-system-monitor” package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-system-monitor For instance: 904KiB appears before 13.6MiB. Sorting should be made based on a common bytes unit meassure, not a string character sorting. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/gnome-system-monitor NonfreeKernelModules: nvidia Package: gnome-system-monitor 2.24.1-0ubuntu1 ProcEnviron: PATH=/home/username/bin:/usr/local/java/jdk/bin:/usr/local/java/jdk/jre/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor Uname: Linux 2.6.27-11-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/331897/+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
